I can detect NAT during clients REGISTER, but not the type of nat (the
mapping reutilization method it uses). That's why I tried to do that:
to send a request from an transport address and receive it from
another, so I can check the source transport address to figure out if
NAT is re-using the same mapping.<br>
<br>Thanks for your help, Iñaki.<br><br><br><div><span class="gmail_quote">2008/4/8, Iñaki Baz Castillo <<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
El Monday 07 April 2008 23:52:08 Victor Cartes escribió:<br> <br>> Thanks, Iñaki. But It is not what I really need.<br> ><br> > I need to send to an UAS a SIP Request, like OPTIONS, and tell it to send<br> > the reply to a different transport address (IP Addr + Port) than the source<br>
> address of the request.<br> <br> <br>That is not possible at all, a UAS decides where to send the reply based on<br> the "received" and "rport" values (if UAC indicated it) that the UAS<br> transport layer has set when receiving the request.<br>
<br><br> <br> > This is, basically, in order to perform NAT discovering and typing from the<br> > server.<br> <br> <br>Is not enought to analize NAT during clients REGISTER? why you need it?<br> <br><br> <br> Regards.<br>
<br> <br> <br> --<br> Iñaki Baz Castillo<br> <a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a><br> <br> _______________________________________________<br> Users mailing list<br> <a href="mailto:Users@lists.openser.org">Users@lists.openser.org</a><br>
<a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br> </blockquote></div><br>