[SR-Users] Asynchronous processing increases branch count

Alex Balashov abalashov at evaristesys.com
Fri Dec 11 02:33:36 CET 2015


Normally with serial forking, the first branch ID corresponds to 
$T_branch_idx == 0, i.e.

Via: SIP/2.0/UDP;branch=z9hG4bK7f3d.57593ee3a139f0ae6c4a8a0f531e342c.0

In the event of failure, a second branch attempt has a branch index of 1 
and so on:

Via: SIP/2.0/UDP;branch=z9hG4bK7f3d.57593ee3a139f0ae6c4a8a0f531e342c.1

However, when I use asynchronous processing with t_suspend() / 
t_continue(), resuming the transaction in an rtimer process, I notice 
that the $T_branch_idx of the first branch is 1, then 2.

Where did 0 go? Is this a normal effect of TM suspend/continue?


-- Alex

Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

More information about the sr-users mailing list