Hello,
I don't recall any change in this aspect, are the two branches going to
same destination?
Cheers,
Daniel
On 5/13/13 2:43 PM, Alex Balashov wrote:
Hello,
Has something changed about default forking behaviour in >= 4.0?
I have a scenario where INVITEs processed by the proxy first hit a
redirect server, catch a 302, and then append another branch and
iterate over one or more outbound routes.
In the past, this worked fine. After I upgraded to 4.0, I am seeing
two branches at a time on the outbound routes, after the initial
branch to the redirect server. The desired behaviour is serial
forking at all times.
tm:failure_reply_mode is set to 3, as it always has been.
Any ideas would be appreciated; thank you!
-- Alex
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
* http://asipto.com/u/katu *
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
