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.
Greetings,
Víctor
2008/4/8, Iñaki Baz Castillo <ibc@in.ilimit.es>:
El Tuesday 08 April 2008 14:14:08 Victor Cartes escribió:
> 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.
Ok, but as I said it's not possible in SIP to request that a reply goes to a
different address:port than the indicated in received:rport of Via header.
It's the UAS who decides it based on the request Via and source ip:port from
where it has received the request.
You'll need to think in other way :(
--
Iñaki Baz Castillo
ibc@in.ilimit.es
_______________________________________________
Users mailing list
Users@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users