Hi,<br><br><div class="gmail_quote">On Wed, May 4, 2011 at 8:33 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Wouldn't the same onreply_route be conserved for every branch? I can't see how any of our implementations would actually work if that weren't the case.<br>
</blockquote></div>
Yes, the onreply_route will be conserved for the entire transaction and all its branches -- the last t_on_reply() called will be effective.<br></blockquote><div><br>OK, thanks for the clarification. It still helps so that we can force this onreply_route only when at least one of the branches is detected to be behind NAT. <br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Seems this was forgotten when we switched to the new tm (from ser at 3.0) and these functions were not enabled for the branch_route, but there is no reason they wouldn't work there -- probably nobody was using in this way lately. I just enabled the t_on_reply() function for branch_route, just fetch the latest version from git branch 3.1 and try again.<br>
</blockquote><div><br>Thanks, I will update immediately.<br><br>Best regards,<br>Sebastian<br></div>
</div>