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

[Iñaki Baz Castillo]

2012/11/2 Binan AL Halabi <binanalhalabi at yahoo.com>:
>
> Hi All,
>
> If oversip uses Path extension OpenSIPS must support it.
>
> 1- Sending Path header values in 200 ok REGISTER response

Even if this is required by RFC, the fact is that it's not needed at
all for this stuff to work.


> 2- Path header files syntax must confom to Route syntax

Right.


> 3- When look up the opensips must copies the stored path header fileds into
> Route header fileds - preloaded route.
> Reference: RFC 3327

Right.



> 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).

Also right, but due the design of OverSIP (basically an Outbound EDGE
proxy) it was easier for me to always use double Record-Route and
double Path header. In Outbound (RFC 5626) the Record-Route header
added by the EDGE proxy contains a username in the URI that identifies
the client connection. For some reasons it was easier always to use
double Path.

Anyhow, consider also the case in which there are two proxies between
clients and OpenSIPS, so increasing the size of the "path" column is
required.




--
Iñaki Baz Castillo
<ibc at aliax.net>