[OpenSIPS-Users] next_branch function, NAT and PATH (RFC 3327)

[Alex Hermann]

On Thursday 14 May 2009 16:40:08 Mauro Davi' wrote:
> If I call an AOR via parallel fork all goes fine...
Parallel forking seems ok, but in reality it isn't. You just don't notice 
because you use only 1 load-balancer. If the AOR has multiple contact 
registered via multiple load-balancers, all contacts use the path of the first 
contact.

>> But if I use a serial forking, when I call the next_branch function to
> handle a serial forking the INVITE from the server isn't sent to the SIP
> Proxy (the outbound proxy defined in the PATH HF of the REGISTER).
Indeed, on serial forking Path is ignored completely except for the first 
branch.

> It seems that also the received parameter isn't used... The INVITE go
> direct to the private IP of the client behind NAT...
>
> It is a mistake in my opensips configuration or it is a real BUG...
It's a bug and has been present for quite some time.

Alex.