<br><br><div class="gmail_quote">On Mon, Jun 16, 2008 at 2:29 PM, Iñaki Baz Castillo <<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
El Monday 16 June 2008 13:45:07 escribió:<br>
<br>
Jola, ¿tal vez iba para la lista? XDDDDD<br>
<div><br>
<br>
> > If you manage clients behind NAT with no STUN you need to fix NAT in SIP<br>
> > signalling. For that you need managing rport, rewritting "Contact" header<br>
> > and so.<br>
> > Of course, if you are not the responsible of the clients you don't need<br>
> > it. :)<br>
><br>
> As i'm not responsible for the clients I always do:<br>
><br>
> setbflag(7);<br>
> force_rport();<br>
> fix_contact();<br>
><br>
> append_hf("P-hint: Route[6]: mediaproxy \r\n");<br>
> use_media_proxy();<br>
><br>
><br>
> on an INVITE, as I don't care whether they are behind NAT or not. And<br>
> on the REPLYs:<br>
><br>
> append_hf("P-hint: Onreply-route - fixcontact \r\n");<br>
> fix_contact();<br>
><br>
> if (search("^Content-Type:[ ]*application/sdp")) {<br>
> append_hf("P-hint: onreply_route|usemediaproxy \r\n");<br>
> use_media_proxy();<br>
> }; </div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
</div>You only have to "fix_contact" if the reply is a 180|183 or 2XX<br>Be careful, if you get a REDIRECT (3XX) whose information is in it "CONTACT" (who to redirect to), you'll delete the "contact"<br>
<br>
<div class="Ih2E3d"><br>
<br>
> this way if the are behind NAT or not, i'll always fix the contacts<br>
> and force mediaproxy....<br>
><br>
> do you think this is correct?<br>
<br>
</div>Have you had problems with calls getting cut off? BYE/CANCEL/ACK that didn't reach its destination?<br>
If you haven't, the it is correct ;)<br>
<div><div></div><div class="Wj3C7c"><br>
</div></div></blockquote><div> </div></div>