I do also see a lot of value in sip over websocket. WebRTC is pretty much here and it makes much more sense to be able to support it on one proxy server rather than having to use OverSIP and then OpenSIPS. WebRTC seems to be very popular and the thing of tomorrow and it will be very important for a sip proxy server to support it.<div>
<br></div><div>Regards,</div><div>Ali Pey<br><br><div class="gmail_quote">On Fri, Oct 26, 2012 at 11:54 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 26, 2012, at 5:46 PM, Duane Larson wrote:<br>
<br>
> Is there any roadmap for "SIP over Websocket"? I know there is now OverSIP but wasn't sure if OpenSIPS had any plans to implement a module. Just asking since WebRTC is still evolving.<br>
><br>
<br>
</div>I personally don't see the need to do it in the 1.x series. You can use OverSIP to do protocol translation to TCP/TLS and send the call to OpenSIPS. Now, IIRC there was some problem in parsing the Via headers, because they now have a different transport parameter (ws and wss), but I think someone posted a patch already.<br>
<div class="im HOEnZb"><br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
<br>
<br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br></div>