[SR-Users] 4.0 forking behaviour

[Daniel-Constantin Mierla]

Just to understand exactly:

A calls B
B redirects to C and is captured by proxy

then from proxy you have two parallel outgoing branches to C?

How you take the address of C and create the branch? uac_redirect or 
other script functions?

Cheers,
Daniel


On 5/13/13 3:26 PM, Alex Balashov wrote:
> Yes, they are identical in every way except for the .1 and .2 branch IDs.
>
> Daniel-Constantin Mierla <miconda at gmail.com> wrote:
>
>> 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
>>>
> --
> Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard.
>
> Alex Balashov - Principal
> Evariste Systems LLC
> 235 E Ponce de Leon Ave
> Suite 106
> Decatur, GA 30030
> United States
> Tel: +1-678-954-0670
> Web: http://www.evaristesys.com/, http://www.alexbalashov.com

-- 
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 *