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

[Iñaki Baz Castillo]

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>