Hi Bogdan,<div><br></div><div>Saul is correct. The key thing is to support WebSocket transport. WebRTC is becoming quite popular and seems to be the thing of future. It is already added in asterisk (version 11 released last week) and it is being added to Kamalio. Using OverSIP and the OpenSIPS would make things just more complex specially for larger deployments.</div>
<div><br></div><div>Also, deployments that are already using opensips would want to provide WebRTC based apps and it makes a lot of sense to natively support it with opensips. Asterisk's implementation seemed quite complete. Maybe you can have a look at that.</div>
<div><br></div><div>Regards,</div><div>Ali Pey<br><br><div class="gmail_quote">On Wed, Oct 31, 2012 at 8:21 AM, Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On Oct 31, 2012, at 12:52 PM, Bogdan-Andrei Iancu wrote:<br>
<br>
> Hi Saul,<br>
><br>
> OK, aside the TCP part (which anyhow is scheduled for fixing) and some extra parsing, does supporting WebRTC imply something more on the OpenSIPS side ?<br>
><br>
<br>
</div>It requires that OpenSIPS is able to use SIP over a WebSocket transport. So OpenSIPS would need support for WebSocket. The transport behaves roughly the same as TCP, with the difference that you may only get a single SIP packet in each WebSocket segment. There are other couple of minor things, but the core of it is supporting the WebSocket transport.<br>
<br>
I didn't have the time to test OpenSIPS behind a OverSIP instance, to verify if there is anything to be fixed beforehand, but according to <a href="https://sourceforge.net/tracker/?func=detail&aid=3545859&group_id=232389&atid=1086412" target="_blank">https://sourceforge.net/tracker/?func=detail&aid=3545859&group_id=232389&atid=1086412</a> Via parsing will fail because if doesn't recognize ws and wss as valid transports. I had a look at the attached patch and it seems to solve the problem by accepting any Via transport parameter. I guess that's a good idea, so OpenSIPS would not care about any transport used in the path, as long as it doesn't need to use it, but I guess some checks would need to be done to validate if the topmost Via has a transport OpenSIPS understands. Not sure if this check is already done though.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
Regards,<br>
<br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>