You don't need to change anything in OverSIP, just install it with default configuration and in SIPML5, change websockets server IP and port to where OverSIP is running and then from browser open the call.htm page and give account details for your OpenSIPs, as if you are connecting to OpenSIPs from a soft phone. OverSIP will handle the rest. It will receive request from SIPML5 over Websocket and forward it OpenSIPs after adding appropriate PATH and VIA headers.<div>
<br></div><div>On OpenSIPs end, you need the patch mentioned in this email thread and recompile opensips with it. Then you can receive SIP requests from OverSIPs and you can process them whatever way you want as if the requests are coming from SIP client through an intermediate SIP proxy.</div>
<div><br><div>Thank you.</div><div><br><br><div class="gmail_quote">On Thu, Aug 23, 2012 at 1:06 PM, Hadi Ams <span dir="ltr"><<a href="mailto:ln.nima.nl@gmail.com" target="_blank">ln.nima.nl@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Muhammad ,<div>Can you please briefly explain how to forward the traffic from Oversip to OpenSips ?</div><div>I am not exactly sure what to change in oversip.conf (or should I try something with proxies.conf ) and how to play with incoming traffic settings in OpenSips .</div>
<div>At the moment in outgoing "REGISTER" messages, OverSip uses the private IP address of the server in "PATH" and "VIA" headers, therefore I am not able to receive responses from the REGISTRAR.<br>
</div><div>I am using sipml5 ==> OverSips =??=> OpenSips</div><div><br><div>your help is much appreciated.</div><br><br></div><div class="HOEnZb"><div class="h5"><div>On Sunday, August 12, 2012 5:04:27 PM UTC+2, Muhammad Shahzad wrote:<blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
This patch only allows parsing of WS VIA in OpenSIPs, you still need some WS to SIP proxy like OverSIP to receive calls from WebRTC clients. So just setup OverSIP proxy and configure it to forward all traffic from WebRTC clients to OpenSIPs, and then you can do everything that OpenSIPs can do for traffic coming from a SIP end-point.<div>
<br></div><div>Thank you.</div>
</blockquote></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Muhammad Shahzad<br>-----------------------------------<br>CISCO Rich Media Communication Specialist (CRMCS)<br>CISCO Certified Network Associate (CCNA)<br>
Cell: +92 334 422 40 88<br>MSN: <a href="mailto:shari_786pk@hotmail.com">shari_786pk@hotmail.com</a><br>Email: <a href="mailto:shaheryarkh@googlemail.com">shaheryarkh@googlemail.com</a><br>
</div></div>