Hello, Here is my proposal for http://track.sipfoundry.org/browse/XX-7821 : Simplify NAT Traversal and "Internet Calling" configuration<http://track.sipfoundry.org/browse/XX-7821>
1. The name of "Internet Calling" is confusing. It is really to enable SIP URI dialing through external SBC. Since Paul is proposing to remove "Devices"->"SBC Routes" , I think maybe I can hijack the name of "SBC Routes" for "Internet Calling", which at least appear more intuitive to me. Anyone can come up with a better name for this feature? 2. As "NAT Traversal" and "Internet Calling" really are meant for different things, and there is no logical correlation, I propose to keep them as completely separate items/pages under "System", "Nat Traversal" and "SBC Routes" namely. 3. As there will never be a case (at least from practical perspective), you want to use external SBC for internet calling, yet use built-in Nat Traversal capability, there is no need for them to share the common configuration, that is the Intranet domain/subnets configuration. In other words, User choose to either use external SBC for internet calling, or configure to use built in NAT traversal, and Internet Calling and Nat Traversal page will have their own Intranet domain/subnets configuration, and there are no correlation between them. 4. Re-do help text. Help text for "Internet Calling" is not accurate, which also leads confusion. i.e. "Specifying an SBC is required if your network is behind a firewall or NAT device.", which is not true, as we have built-in NAT Traversal now, external SBC is not required for SIP URI calling when behind a firewall or NAT. Thoughts? Thanks Huijun
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
