Ping this to figure out your problem

Posts: 104 · Vonage Forum Senior Joined: Jan 31, 2004 Posts: 104

If you've been having latency or connection problems, you need to figure out how far away from Vonage's equipment in the world of IP you are. Using the TRACERT command, you can see how many router hops & the delay is to the following Vonage servers. My figures are from a Comcast cable modem service with a location in Northern VA.

146.82.161.37
This is a Global Crossing gateway (one of many). I'm 11 hops and 17 ms away.

atlas2.atlas.vonage.net
This is one of the Vonage softswitch systems which sets up your telephone calls. I'm 15 hops and 23 ms away.

tftp.vonage.net
This is the upgrade server where your MOTO or Cisco box downloads new software (not critical to making telephone calls). I'm 15 hops and 22 ms away.

> 206.165.182.24 (only for some users)
This is my local PaeTEC POP where incoming calls come from. I'm 13 hops and 20 ms away.

NOTE: At the end of TRACERT you will start to get "Request Timed Out" messages. Just take the last figures. This error occurs because you've hit a firewall/router at Vonage or Global Crossing (meaning no more public internet) which blocks TRACERT requests.

Also remember to subtract 1 from your router count IF you are using the MOTO box in front of your router (since the MOTO box will show up in your router count).

Enter your times in this poll

Posts: 9 · New Forum Member Joined: Mar 12, 2004 Posts: 9

It seems that Vonage's system is geared toward East Coast people. I reach Global Crossings in Seattle in 20ms. It then takes another 80ms to cross to NYC.

This most likely means that a call will come into Seattle. It will then get routed to NYC for processing. I will then come back to Seattle. That means 200+ms for JUST gblx.

Yikes! No wonder my forwarded calls sound like a Sat phone.

Posts: 1 · New Forum Member Joined: Feb 21, 2004 Posts: 1

I get destination unreachable on all 4 Sad

I am have trouble with incoming audio getting choppy, but when it is choppy I ask the person I am speaking to if it is choppy for them too and the reply has been so far NO.

HELP!!!!!

Posts: 18 · Posted: Sun Mar 14, 2004 9:58 pm Post subject:

146.82.161.37 11 hops 16 ms
atlas2.atlas.vonage.net 10 hops 18 ms
tftp.vonage.net 10 hops 13ms
206.165.182.24 11 hops 85ms

It is 2 hops just to my cable provider. There is is a lot of hopping here. I am in Brooklyn,NY & the Vonage server is in Weehawken, NJ Confused

Posts: 50 · Full Forum Member Joined: Mar 10, 2004 Posts: 50

This is rellay an unfair test as the up path that trace route uses and the down path may be different.

Posts: 1 · New Forum Member Joined: Mar 13, 2004 Posts: 1

146.82.161.37 - 14 hops/531 ms (?!)

atlas2.atlas.vonage.net - 12 hops/16 ms

tftp.vonage.net - 12 hops/16 ms

206.165.182.24 - 12 hops/78 ms

Posts: 47 · Posted: Mon Mar 15, 2004 7:44 am Post subject: tracert command

Do I enter this in the DOS prompt or is it the Trace Route program available on the net?

I'm running XP Pro SP 1

Posts: 47 · Posted: Mon Mar 15, 2004 7:59 am Post subject: Not good

142.82.161.37 - 16 hops/60ms

Atlas2.atlas.vonage.net - 13 hops/92ms

tftp.vonage.net - 13 hops / 60ms

206.165.182.24 - 15 hops / 105ms

this looks like trouble. Of course I don't have the ATA yet.

Posts: 16 · Vonage Forum Associate Joined: Mar 06, 2004 Posts: 16

Getting destination host unreachable. I'm on SC RoadRunner for Internet service.