On 5/17/2010 6:13 AM, Tony Graziano wrote: > Port 5080 must be symettrically nat'ed to register. Just to confirm "Symmetric NAT" - sipXecs sends a request to voip.ms from 10.8.158.121 port 5080; firewall adds an entry to its NAT table and substitutes the external IP address 216.8.158.237 for 10.8.158.121 in the packets forwarded to voip.ms; voip.ms responds to 216.8.158.237 port 5080; firewall finds this entry in the NAT table and substitutes the internal IP address 10.8.158.121 for 216.8.158.237 in the packets returned to sipXecs. sipXecs sends some form of "keep alive" packets to voip.ms to maintain the NAT table entry. Correct?
SIP trunking Public Port defaults to 5060 - should this be 5080? Stricltly NAT - no "port forwarding" defined. My firewall does not do "port forwarding" - if an internal machine needs incoming access from the internet, I define a single address route like 216.8.158.225/32 to 10.8.158.225 and add rules to the firewall defining what ports and protocols are allowed over this route. To make this work, the target machine must have an eth0 address of 10.8.158.225/24 and an IP alias of 216.8.158.225/32. FreeBSD allows me to create IP aliases. Linux (CentOS 5.2) requires me to create the alias thus: eth0:0 216.8.158.225 netmask 255.255.255.255 ... I was concerned that sipXecs would see this alias as a second IP address and become confused because all the documentation says: "thou shalt not use multiple IP addresses!". -- Norman Branitsky +1 416.798.7948 Cherniak Software Development Corporation Fax: +1 416.798.0948 509-2001 Sheppard Avenue East [email protected] Toronto, ON M2J 4Z8 sip:[email protected] Canada http://www.CherniakSoftware.com _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
