<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Hi Ali,<br>
<br>
I have to admit I'm not really familiar with the WebRTC and what
are the requirements for this to work directly over OpenSIPS -
there is pending patch for compatibility with WebRTC (parsing and
detecting more VIA params, specific to WebRTC), but we will need
to have a clear view on what needs to be done for a complete
integration - and at that point to say if makes sense to do it or
not.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<br>
On 10/27/2012 02:41 AM, Ali Pey wrote:
<blockquote
cite="mid:CA+q4kR+G4O8F3ZanE1m+Rw+T-55qr3rwGohS0iO19C+3SJn2VA@mail.gmail.com"
type="cite">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 moz-do-not-send="true"
href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
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 moz-do-not-send="true"
href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
<a moz-do-not-send="true"
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>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a>
</pre>
</blockquote>
</body>
</html>