> >From our last demo meeting a question came up that never got > answered. > > Why is NAT traversal disabled by default? > > Any takers?
Two reasons. When upgraded from 3.10 to 4.0, we want the system to retain its behavior. Given that a 3.10 didn't have NAT traversal then keeping it disabled when the system is moved to 4.0 seems like the right thing to do especially when considering that this system may be deployed behind an InGate that already solves the NAT issues. Suddenly enabling NAT traversal for such a system during an upgrade would likely confuse InGate and fail calls. The other reason is that enabling NAT traversal is not enough to get the feature working. One also has to do such things as configure the public IP address and define the local private network topology. This information cannot be guessed and has to be entered by the admin. As such, enabling NAT traversal when the pre-requisite information is not provided will cause the system to behave erratically. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
