PBXes » English » Providers » RE: Voip.ms Toronto POP ip change
Print Page | Recommend to Friend | Add Thread to Favorites
Post New Thread Post Reply
Author
Post « Previous Thread | Next Thread »
ayk


Registration Date: 01.01.1970
Posts:

Voip.ms Toronto POP ip change Post Reply with Quote Edit/Delete Post Report Post to a Moderator       IP Information Go to the top of this page

Hi,

Since voip.ms changed their IP address for the Toronto POP, I haven't been able to use my phones. The phones work if I put in IP address directly but fail if I put in hostname.

Change is as follows:
code:

=====================
What are the changes?
=====================

The IP address for the host sip.ca2.voip.ms and iax2.ca2.voip.ms will be replaced November, Wednesday 25th @ 2:00 AM EST with the following IP address:


NEW IP Address: 174.137.63.202
OLD IP Address: 24.102.60.67


Please kindly check DNS cache.

Thanks.

ayking

26.11.2009 17:08 ayking is offline Search for Posts by ayking Add ayking to your Buddy List
Dia
Premium Account


Registration Date: 03.03.2006
Posts: 1443

RE: Voip.ms Toronto POP ip change Post Reply with Quote Edit/Delete Post Report Post to a Moderator       IP Information Go to the top of this page

Your message seems to be startling and confusing at the same time. Allow me to explain why.

If your phones are registering directly to PBXes how can a change in the IP of an ITSP can render your IP-phones inoperable? Can your phones call from extension to extension? If they can, then your IP-phones are working properly. If not, there must be another issue with your PBXes account.

If your phones are registering directly with the SIP Proxy of VoIP.ms the PBXes SIP Proxy is not at all in the middle.

But let's assume the phones are registering on PBXes and your VoIP.ms accounts are defined as trunks on your PBXes account. If the www4 server had a DNS cache issue, the following traceroute should have ended up on the old IP address. As you can see though, it ends up on the new IP, so that is not likely the issue.

traceroute to sip.ca2.voip.ms (174.137.63.202) from www4 (NY), 30 hops max, 40 byte packets
1 64.118.93.73 (64.118.93.73) 0.439 ms 0.479 ms 0.495 ms
2 ae0-307.nyc20.ip4.tinet.net (213.200.73.125) 0.718 ms 6.980 ms 3.013 ms
3 xe-0-2-0.nyc32.ip4.tinet.net (89.149.187.246) 0.876 ms
4 xe-2-2-0.nyc30.ip4.tinet.net (89.149.187.74) 5.226 ms 0.898 ms
5 Te-3-4.car3.NewYork1.Level3.net (4.68.110.77) 1.200 ms 0.968 ms 1.409 ms
6 ae-22-79.car2.NewYork1.Level3.net (4.68.16.68) 1.353 ms 1.433 ms 1.903 ms
7 ALLSTREAM-I.car2.NewYork1.Level3.net (4.78.166.90) 1.014 ms 1.140 ms 0.943 ms
8 ge4-2.hcap4-tor.bb.allstream.net (199.212.169.110) 17.464 ms 18.383 ms 17.528 ms
9 216.191.57.178 (216.191.57.178) 18.515 ms 17.738 ms 18.087 ms
10 colo4500-to-core-main.bgp.mountaincable.net (24.102.5.13) 17.740 ms 17.848 ms 17.950 ms
11 cn45-core.mountaincable.net (24.102.5.18) 17.599 ms 19.723 ms 18.735 ms
12 dns1-i.crtnetworks.net (174.137.63.202) 17.648 ms 17.620 ms 18.436 ms

• Is it possible the new VoIP.ms SIP Proxy requires the username to be present in the trunk's configuration, for the authentication to take place during the Invite?

26.11.2009 18:57 Diafora is offline Search for Posts by Diafora Add Diafora to your Buddy List
 
Post New Thread Post Reply
Go to:

Powered by Burning Board Lite 1.0.2 © 2001-2004 WoltLab GmbH
English Translation by Satelk