On Fri, Jul 17, 2009 at 12:24 PM, Tim Byng<t...@missioninc.com> wrote: > I have attached an ITSP template I created for voip.ms (with some help from > Ranga). I have been using these settings for over a month and everything is > working very well. > There are a couple of settings I'd like to talk about: > use-global-addressing > voip.ms allows hosted NAT compensation to be enabled and disabled by the end > user. By default, it is enabled and will work with this setting if > use-global-addressing is set to false. However, it is generally recommended > to only have sipXecs handle NAT, as this will usually give the best results. > That is why I recommend to set use-global-addressing to true and to set "NAT > (Network Address Translation)" on the advanced settings of the voip.ms > account to "no". I appended brief details about this to > the use-global-addressing description in the template. > itsp-proxy-address > voip.ms currently has 7 servers that can be used. Any of the servers should > work. I set the default to be sip.ca2.voip.ms (Toronto, Canada), as this is > the server I tested it with. This value can be changed to any of the other > servers. I also appended brief details about this to the itsp-proxy-address > description in the template. Here is the current voip.ms server list: > USA1 (Houston, TX): sip.us1.voip.ms (209.62.1.2) > USA2 (Dallas, TX): sip.us2.voip.ms (74.54.54.178) > USA3 (Los Angeles, CA): sip.us3.voip.ms (67.215.241.250) > USA4 (New York, NY): sip.us4.voip.ms (74.63.41.218) > UK1 (London, UK): sip.uk1.voip.ms (78.129.153.20) > CAN1 (Montreal, Canada): sip.ca1.voip.ms (67.205.74.164) > CAN2 (Toronto, Canada): sip.ca2.voip.ms (24.102.60.67) > As a side note, it would be nice if sipXecs would allow user created > templates. This has been requested in JIRA issue XX-5966. Vote if you'd like > to see this feature implemented. > Regards, > Tim
Thanks for the contribution, for the notes and for your willingness to participate in interoperability testing. I have entered an issue XX-6152 for this. The ball is the sipxconfig court to include it into the build. I will put your comments into our wiki page for sipxbridge. Ranga. > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > 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/ > -- M. Ranganathan _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/