Just a thought... is it possible to ingore the nat flag and just rely on the existence of dst_uri to indicate a NATed UA?<br><br><div><span class="gmail_quote">On 8/29/05, <b class="gmail_sendername">Klaus Darilion</b> <
<a href="mailto:klaus.mailinglists@pernau.at">klaus.mailinglists@pernau.at</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ho Bodgan!<br><br>To use branch routes for branch-only NAT traversal also the nathelper<br>and mediaproxy functions must be adopted to work in branch routes.<br><br>regards<br>klaus<br><br>Bogdan-Andrei Iancu wrote:<br>> Hi,
<br>><br>> indeed, prior branch_route, there is only one set of flags shared by all<br>> branched - that's still unchanged.<br>><br>> regards,<br>> bogdan<br>><br>><br>> Juha Heinanen wrote:<br>
><br>>> Klaus Darilion writes:<br>>><br>>> > The nat flag which will be loaded during lookup() - will it be set<br>>> for > each branch so it can be queried in branch_route for all of the<br>
>> > registered contacts, or should I use isdsturiset() instead of<br>>> testing > for the NAT flag?<br>>><br>>> i don't think that there is any changes regarding nat flag yet. nat<br>>> flag is set if any of the contacts is behind nat. it would be nice if
<br>>> nat flag would be automatically set in branch route only if contact of<br>>> the corresponding branch is behind nat.<br>>><br>>> -- juha<br>>><br>>> _______________________________________________
<br>>> Users mailing list<br>>> <a href="mailto:Users@openser.org">Users@openser.org</a><br>>> <a href="http://openser.org/cgi-bin/mailman/listinfo/users">http://openser.org/cgi-bin/mailman/listinfo/users
</a><br>>><br>>><br>>><br>><br>><br><br><br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@openser.org">Users@openser.org</a><br><a href="http://openser.org/cgi-bin/mailman/listinfo/users">
http://openser.org/cgi-bin/mailman/listinfo/users</a><br></blockquote></div><br>