On Monday 26 July 2010 07:02:03 Alex Balashov wrote:
On 07/26/2010 01:59 AM, Raúl Alexis Betancor Santana wrote:
On Monday 26 July 2010 06:21:56 Alex Balashov wrote:
On 07/26/2010 01:20 AM, Raúl Alexis Betancor Santana wrote:
On Monday 26 July 2010 04:32:13 Iñaki Baz Castillo wrote:
El día 26 de julio de 2010 01:07, Raúl Alexis Betancor Santana
rabs@dimension-virtual.com escribió:
any clue or example about how to work with the new branch ONLY ? ... because branch 1 works ok, I need to do changes only on branch 2
You must inspect the $ru (or $du depending the case) in onbranch_route, and take the desired action when $ru is $avp(s:followme).
Umm ... again confused ... does the execution of the cfg continues AFTER the append_branch call,just on the next line ... or it "begins" on "t_on_branch()"?
The first one.
So ... both branches continues at the same point, with the only difference that one have $ru = $avp(s:followme) ... uff ... I'll have to elavorate a little more because that point of the .cfg it's also reached with a "normal" call to $avp(s:followme) ... :-\
It might be more helpful to think of it as: execution continues right where it was in the request route, but a branch route is also later called right before the message is forwarded on the given branch, not in parallel, where certain branch-specific parameters can be tweaked at the last moment, or certain branch-specific actions taken.
I don't undestand ... so ... execution continues in the next line, just after append_branch for BOTH branches, but wenever I call t_relay ... BOTH branches will pass through on_branch_route BEFORE been forwarded?