Indeed, onreply_route, like the other tm specific routing blocks, is
property of the transaction. No tm routing block is specific per branch,
this was the behaviour from the beginning, branch index PV is supposed
to give indication about what branch is executed.
Setting/resetting a tm routing
Seems like the reply route is a property of the transaction, and not of
each respective branch. I wouldn't call it "bug" at the moment, but
would call it a "limitation".
I second Juha's command - as soon as a branch is canceled I do not care
about any following responses and it may be useful t
I think $T_branch_idx is only available on branch_route, and besides, it
contains the current branch ID being processed so it wouldn't be useful
from replies outside the current branch.
Regards.
Carlos.
On Thu, Oct 11, 2012 at 11:48 AM, Alex Hermann wrote:
> On Thursday 11 October 2012, Carlos
On Thursday 11 October 2012, Carlos Ruiz Díaz wrote:
> I can confirm this behavior.
>
> I had a similar scenario when 2 or more branches were setup. First branch
> timed out, while second branch was being processed a reply from first
> branch arrived and handled improperly by a routing logic which
I can confirm this behavior.
I had a similar scenario when 2 or more branches were setup. First branch
timed out, while second branch was being processed a reply from first
branch arrived and handled improperly by a routing logic which was
configured for the second branch.
I isolated each respons
On Thursday 11 October 2012, Juha Heinanen wrote:
> Alex Hermann writes:
> > 1) set onreply_route to A
> > 2) relay 1st branch
> > 3) 1st branch times out, internal 408 is created
> > 4) tm send CANCEL to 1st branch
> >
> > 5) in failure route, onreply_route is set to B
> > 6) relay 2nd branch
> >
Alex Hermann writes:
> 1) set onreply_route to A
> 2) relay 1st branch
> 3) 1st branch times out, internal 408 is created
> 4) tm send CANCEL to 1st branch
>
> 5) in failure route, onreply_route is set to B
> 6) relay 2nd branch
> 7) 1st branch responds with 487, and goes into reply_route B inst
Hello,
i noticed thet in serial forking, replies to earlier branches arriving after
sending out a new branch use the onreply_route of the later branch instead of
the onreply_route set before sending the earlier branch
How to reproduce:
1) set onreply_route to A
2) relay 1st branch
3) 1st b
