It's just curious that RFC 3261 establishes that with no reliable transport protocols, if received param in via is specified, UAS should refer to that address to send the reply. But I try with some User Agents, and even when I set the received param pointing to an specific IP address, they're still sending the reply to the origin of the requests. With ports there is no such problems.<br>
<br>Greetings,<br><br>Víctor<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 Tuesday 08 April 2008 14:14:08 Victor Cartes escribió:<br> <br>> I can detect NAT during clients REGISTER, but not the type of nat (the<br> > mapping reutilization method it uses). That's why I tried to do that: to<br>
> send a request from an transport address and receive it from another, so I<br> > can check the source transport address to figure out if NAT is re-using the<br> > same mapping.<br> <br> <br>Ok, but as I said it's not possible in SIP to request that a reply goes to a<br>
different address:port than the indicated in received:rport of Via header.<br> It's the UAS who decides it based on the request Via and source ip:port from<br> where it has received the request.<br> <br> You'll need to think in other way :(<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>