[OpenSIPS-Users] [OpenSIPS-Devel] [RELEASES] Planing OpenSIPS 1.9.0 major release

[qasimakhan at gmail.com]

VIA Parser Patch for WS & WSS:

http://sourceforge.net/tracker/?func=detail&aid=3545859&group_id=232389&atid=1086412

Regards,
Qasim


On Fri, Nov 2, 2012 at 6:43 AM, Binan AL Halabi <binanalhalabi at yahoo.com>wrote:

>
> Hi All,
>
> If oversip uses Path extension OpenSIPS must support it.
>
> 1- Sending Path header values in 200 ok REGISTER response
> 2- Path header files syntax must confom to Route syntax
> 3- When look up the opensips must copies the stored path header fileds
> into Route header fileds - preloaded route.
> Reference: RFC 3327
>
>
> Here i think adding one Route header pointing to OverSIP (second Path URI)
> is enough in simple case (UA ---- OverSIP--- OpenSIPS).
> OverSIP removes the Route header and route the request based on RURI
> (first Path URI).
>
>
>
> OpenSIPs support this
> http://www.opensips.org/html/docs/modules/devel/registrar.html#id248705
> flag "px" (path support) of save function in Registrar module.
>
> So still parsing VIA header is required to add WS and WSS. I think this
> patch is already posted.
>
>
> Binan.
>
>   ------------------------------
> *Från:* Iñaki Baz Castillo <ibc at aliax.net>
> *Till:* Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Kopia:* OpenSIPS users mailling list <users at lists.opensips.org>
> *Skickat:* torsdag, 1 november 2012 20:36
> *Ämne:* Re: [OpenSIPS-Users] [OpenSIPS-Devel] [RELEASES] Planing OpenSIPS
> 1.9.0 major release
>
> 2012/11/1 Bogdan-Andrei Iancu <bogdan at opensips.org>
> >
> > Hi Inaki,
> >
> > 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.
> >
> > 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).
>
> Right. As Saul pointed out, this scenario (which is a pure RFC 5626
> "Outbound" scenario with a Edge Proxy in front of the
> registrar/authentication-proxy) requires:
>
> - Path support in OpenSIPS for storing the Path URI(s). Note: It's
> important to increase the "path" column size in the location table.
> The current value is to small and cannot store two URI's (OverSIP adds
> double Path headers).
>
> - OpenSIPS should improve the parser of the Via transport field since
> currently it only accepts UDP, TCP, TLS and SCTP. It should also
> accept WS and WSS, but better if it accepts any token (as the RFC 3261
> BNF grammar states). Otherwise OpenSIPS will discard SIP requests
> coming from OverSIP (since the non top Via header, that created by the
> SIP WebSocket client, has "WS" as transport protocol).
>
> And nothing else at all, but the above two points are important.
>
> Regards.
>
>
>
>
>
> --
> Iñaki Baz Castillo
> <ibc at aliax.net>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20121102/d50fa3eb/attachment.htm>