The basic problem you run into is when you separate the registrar function from the far-end NAT traversal function. <br>
<br>
I decided not to pursue the for now but was looking at using the Path
header as one possible solution. I guess there are other, simpler
solutions, depending on your SER configuration and network
architecture. <br>
<br>
As far as I can tell, most commercial SBCs are also B2BUAs so they solve the problem in a completely different way.<br>
<br>
Mark<br><br><div><span class="gmail_quote">On 9/26/05, <b class="gmail_sendername">Kevin Brennan</b> <<a href="mailto:kevin.brennan@redsquared.com">kevin.brennan@redsquared.com</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;">
We would like to use STUN as preferred NAT traversal method but for<br>those situations where STUN does not work we would offer an outbound<br>proxy (configured in user agent). We would like to keep the NAT<br>traversal proxy completely separate from SER. I wonder has anybody
<br>implemented this ? how ? and any other suggestions/feedback.<br><br>Br /Kevin Brennan.<br><br>_______________________________________________<br>Serusers mailing list<br><a href="mailto:serusers@lists.iptel.org">Serusers@iptel.org
</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://mail.iptel.org/mailman/listinfo/serusers</a><br></blockquote></div><br>