It looks like a lot of troubles to do it, at least for now. I will just
set the nat flag if any one destination requires nat travesal
processing.<br>
<br>
Thanks,<br>
Richard<br>
<br><br><div><span class="gmail_quote">On 9/26/05, <b class="gmail_sendername">Bogdan-Andrei Iancu</b> &lt;<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Richard,<br><br>if it's safe or not call add_rr_param() from branch_route is an already<br>debated subject. See:<br>&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://www.openser.org/pipermail/devel/2005-September/000573.html">http://www.openser.org/pipermail/devel/2005-September/000573.html
</a><br><br>Shortly you may not call it from failure route or from branch route<br>triggered from a failure route(so no serial forking. But you can safely<br>use it from a branch_route triggered by a request route.<br><br>
This problem will be fixed as soon as the cvs is forked for the new<br>upcoming release.<br><br>regarding the future behaviour in failure route - if you do<br>add_rr_param() in branch route, this change will not be visible in the
<br>failure_route - actually any change from branch route will not be<br>visible in failure route.<br><br>regards,<br>bogdan<br><br>Richard Z wrote:<br><br>&gt; Hi Bogdan,<br>&gt;<br>&gt; Can add_rr_param be called from branch_route? It is needed for later
<br>&gt; processing of re-INVITE.<br>&gt;<br>&gt; If SDP is different for each branch, what would it be for the failure<br>&gt; route in a serial forking senario? Is the message reverted back to its<br>&gt; original content? That brings another question... can these functions
<br>&gt; be called from failure_route?<br>&gt;<br>&gt; Thanks,<br>&gt; Richard<br>&gt;<br>&gt;<br>&gt; On 9/26/05, *Bogdan-Andrei Iancu* &lt;<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a><br>&gt; &lt;mailto:
<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>&gt;&gt; wrote:<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Hi Richard,<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; to implement per branch NAT traversal, you need several thing,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; additional to branch route:
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - per branch flags - these are available in the current<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; testing/developing branch (cvs head) - see<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; <a href="http://www.openser.org/pipermail/devel/2005-September/000515.html">http://www.openser.org/pipermail/devel/2005-September/000515.html
</a><br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - nathelper/mediaproxy functions to be allowed to be called from<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; branch route - for the moment I see no problem with doing this, but I<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; will have to double check before setting proper function allowances.
<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; regards,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; bogdan<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Richard Z wrote:<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Hi,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; I am trying to figure out how to use branch route for nat traversal.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; If a subscriber registers from multiple locations, a branch route is<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; called after lookup. For example, if locations include UAs<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; behind same<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; NAT and different NAT, i'd like to invoke any rtp/media-proxy
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; accordingly in branch_route[], . However they can't be called<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; inside a<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; branch_route. What's the best way to do this?<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Thanks,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Richard
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;------------------------------------------------------------------------<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;_______________________________________________<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;Users mailing list
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; <a href="mailto:Users@openser.org">Users@openser.org</a> &lt;mailto:<a href="mailto:Users@openser.org">Users@openser.org</a>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<a href="http://openser.org/cgi-bin/mailman/listinfo/users">
http://openser.org/cgi-bin/mailman/listinfo/users</a><br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt;<br>&gt;<br>&gt;<br><br></blockquote></div><br>