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

[Alex]

On Friday 22 May 2009, Bogdan-Andrei Iancu wrote:
> Alex Hermann wrote:
> > 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.
>
> For parallel forking after  lookup("location") should work - usrloc
> keeps the PATH string for each contact and accordingly push it in
> branches. Also TM module is using the PATH string separately for each
> branch it sends out.
>
> Maybe it is something I miss here, so please let me know why do you say
> that all branches are sent out via the PATH of the first contact.

That's what I observed a few months ago. It's been a while since I tried and 
noticed the failures, so maybe it is ok now, or, maybe I messed up and it 
was ok the first time. I'll check with a more current version.


Alex.