VIA Parser Patch for WS & WSS:<br><br><a href="http://sourceforge.net/tracker/?func=detail&aid=3545859&group_id=232389&atid=1086412">http://sourceforge.net/tracker/?func=detail&aid=3545859&group_id=232389&atid=1086412</a><br>
<br>Regards,<br>Qasim<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 2, 2012 at 6:43 AM, Binan AL Halabi <span dir="ltr"><<a href="mailto:binanalhalabi@yahoo.com" target="_blank">binanalhalabi@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:10pt;font-family:times new roman,new york,times,serif"><div><br></div><div style="font-style:normal;font-size:13.3333px;background-color:transparent;font-family:times new roman,new york,times,serif">
Hi All,</div><div><br></div><div style="font-style:normal;font-size:13.3333px;background-color:transparent;font-family:times new roman,new york,times,serif">If oversip uses Path extension OpenSIPS must support it.</div><div>
<br></div><div>1- Sending Path header values in 200 ok REGISTER response <br></div>2- Path header files syntax must confom to Route syntax<br>3- When look up the opensips must copies the stored path header fileds into Route header fileds - preloaded route. <br>
Reference: RFC 3327 <br><br><br>Here
i think adding one Route header pointing to OverSIP (second Path URI)
is enough in simple case (UA ---- OverSIP--- OpenSIPS).<br>OverSIP removes the Route header and route the request based on RURI (first Path URI). <br> <br><br><br>OpenSIPs support this <a href="http://www.opensips.org/html/docs/modules/devel/registrar.html#id248705" target="_blank">http://www.opensips.org/html/docs/modules/devel/registrar.html#id248705</a> <br>
flag "px" (path support) of save function in Registrar module.<br><br>So still parsing VIA header is required to add WS and WSS. I think this patch is already posted.<br><br><br>Binan.<br><div><span></span></div>
<div><br></div> <div style="font-family:times new roman,new york,times,serif;font-size:10pt"> <div style="font-family:times new roman,new york,times,serif;font-size:12pt"> <div dir="ltr"> <font face="Arial"> <hr size="1">
<b><span style="font-weight:bold">Från:</span></b> Iņaki Baz Castillo <<a href="mailto:ibc@aliax.net" target="_blank">ibc@aliax.net</a>><br> <b><span style="font-weight:bold">Till:</span></b> Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>> <br>
<b><span style="font-weight:bold">Kopia:</span></b> OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>> <br> <b><span style="font-weight:bold">Skickat:</span></b> torsdag, 1 november 2012 20:36<br>
<b><span style="font-weight:bold">Ämne:</span></b> Re: [OpenSIPS-Users] [OpenSIPS-Devel] [RELEASES] Planing OpenSIPS 1.9.0 major release<br> </font> </div><div><div class="h5"> <br>
2012/11/1 Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>><br>><br>> Hi Inaki,<br>><br>> Please correct me if I'm wrong, but reading the draft and listing you guys all, I would say the right approach is to : (1) use OverSIP as gw (to extract SIP traffic from WebSocket) and (2) make OpenSIPS to support SIP traffic resulted from websocket extraction.<br>
><br>> If so, OpenSIPS has nothing to do with the WebSocket protocol itself, but only to support the extensions from the draft (like new protocols and eventually the SIP server location).<br><br>Right. As Saul pointed out, this scenario (which is a pure RFC 5626<br>
"Outbound" scenario with a Edge Proxy in front of the<br>registrar/authentication-proxy) requires:<br><br>- Path support in OpenSIPS for storing the Path URI(s). Note: It's<br>important to increase the "path" column size in the location table.<br>
The
current value is to small and cannot store two URI's (OverSIP adds<br>double Path headers).<br><br>- OpenSIPS should improve the parser of the Via transport field since<br>currently it only accepts UDP, TCP, TLS and SCTP. It should also<br>
accept WS and WSS, but better if it accepts any token (as the RFC 3261<br>BNF grammar states). Otherwise OpenSIPS will discard SIP requests<br>coming from OverSIP (since the non top Via header, that created by the<br>SIP WebSocket client, has "WS" as transport protocol).<br>
<br>And nothing else at all, but the above two points are important.<br><br>Regards.<br><br><br><br><br><br>--<br>Iņaki Baz Castillo<br><<a href="mailto:ibc@aliax.net" target="_blank">ibc@aliax.net</a>><br><br>_______________________________________________<br>
Users mailing list<br><a href="mailto:Users@lists.opensips.org" target="_blank">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>
<br><br> </div></div></div> </div> </div></div><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>
<br></blockquote></div><br></div>