<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Hi Binan,</div><div><br></div><div>Yes the patch is there, we need to review it. Also Inaki sugested some tunings in the PATH module (to fully support websocket).</div><div><br></div><div>Thanks and regards,</div><div>Bogdan</div><div><br></div><div><br></div><div><div style="font-size:75%;color:#575757">Sent from Samsung Mobile</div></div> <br>Binan AL Halabi <binanalhalabi@yahoo.com> wrote:<br><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:10pt"><div><br></div><div class="yui_3_7_2_68_1351800503353_457" style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">Hi All,</div><div><br></div><div class="yui_3_7_2_68_1351800503353_461" style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;">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">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 size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">Från:</span></b> Iñaki Baz Castillo <ibc@aliax.net><br> <b><span style="font-weight:
bold;">Till:</span></b> Bogdan-Andrei Iancu <bogdan@opensips.org> <br><b><span style="font-weight: bold;">Kopia:</span></b> OpenSIPS users mailling list <users@lists.opensips.org> <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> <br>
2012/11/1 Bogdan-Andrei Iancu <<a ymailto="mailto:bogdan@opensips.org" href="mailto:bogdan@opensips.org">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 ymailto="mailto:ibc@aliax.net" href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br><br>_______________________________________________<br>Users mailing list<br><a ymailto="mailto:Users@lists.opensips.org" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br><br><br> </div> </div> </div></body>