Stun can work even behind symmetric NAT if the stun server was running on the same socket the SIP server is running... I hope this feature will come soon!
I can help with this.
Also, SIP don't need to use STUN to work: you can discover your IP address and port very easily by looking at the REGISTER answer or OPTIONS answer which contains the "received" and "rport" parameter.
Of course, symmetric NAT are a nightmare for RTP, but not for SIP...
tks, Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 - http://savannah.nongnu.org/projects/exosip/
On Tue, 10 Jun 2008, Iñaki Baz Castillo wrote:
El Tuesday 10 June 2008 10:44:51 Ali Jawad escribió:
Hi All
I had a lot of problems with STUN and symmetric NAT. The thing is that it does not always work with symmetric NAT. That would be mostly routers based on Linux IPTABLES.
STUN **CANNOT** work with symetric NAT. The NAT router maps the internal port with a different public port *depending* on the destination IP:port, so STUN can't work.
-- Iñaki Baz Castillo ibc@in.ilimit.es
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users