High Trace Route, can anything be done

This forum includes tips for maintaining the best audio quality possible with the Ooma System. If your Ooma system is having issues with dropped calls, static audio or echo, look here for assistance.
Post Reply
JTalbert
Posts: 276
Joined: Tue Jan 12, 2010 8:37 am

High Trace Route, can anything be done

Post by JTalbert » Sun Mar 14, 2010 6:55 am

I am still having problems with my VOIP quality. I have run a trace route, and from a site that I have run it from, 17 hops which the site I have run the test from says is relatively high which can cause problems.

Also when I ran the test it seems the problem might? be with ooma. On three occasions the ping at Ooma was in an "erratic behavior" ranging from 63ms to 276ms.

Another test I ran said that a different site was acting in an erratic behavoir from 1 to 53ms

I dont have my results up still from the one for the erratic ooma behavior, but below is the one that hop 11 is erratic.

As a consumer, if we use a service that has a high hop, is there anything we can do to have the server we are trying to connect to have a more direct route path? Cox says that there is nothing they can do, which I think sounds like hogwash, but I may be wrong.

| Hop | %loss | IP Address | Node Name | Location | ms | Graph | Network |
-------------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | 0 | 205.234.111.129 | r03-8.iad.defenderhosting.com | Washington, DC, USA | 1 | + | Virtacore Systems Inc |
| 1 | 0 | 205.234.111.129 | r03-8.iad.defenderhosting.com | Washington, DC, USA | 1 | + | Virtacore Systems Inc |
| 2 | 0 | 69.65.112.25 | r01.iad.defenderhosting.com | Washington, DC, USA | 0 | + | Virtacore Systems Inc |
| 3 | 0 | 38.104.206.225 | gi7-33.ccr02.iad01.atlas.cogentco.com | Dulles, VA, USA | 0 | + | PSINet Inc. |
| 4 | 0 | 154.54.7.161 | te0-3-0-5.ccr22.dca01.atlas.cogentco.com | Washington, DC, USA | 1 | + | PSINet Inc. |
| 5 | 0 | 154.54.1.33 | te3-8.ccr02.atl01.atlas.cogentco.com | - | 13 | + | - |
| 6 | 0 | 154.54.6.138 | te3-2.ccr02.iah01.atlas.cogentco.com | Houston, TX, USA | 27 | + | - |
| 7 | 0 | 154.54.7.190 | localdomain6 localhost6 | - | 28 | + | - |
| 7 | 0 | 86.137.50.92 | host86-137-50-92.range86-137.btcentralplus.com | - | 2 | + | IP pools |
| 8 | 0 | 154.54.0.241 | te3-1.mpd02.lax01.atlas.cogentco.com | Los Angeles, CA, USA | 63 | + | - |
| 8 | 0 | 86.137.50.92 | host86-137-50-92.range86-137.btcentralplus.com | - | 2 | + | IP pools |
| 9 | 0 | 154.54.5.181 | te3-1.mpd01.sjc01.atlas.cogentco.com | San Jose, CA, USA | 75 | + | - |
| 9 | 0 | 86.137.50.92 | host86-137-50-92.range86-137.btcentralplus.com | - | 18 | -+ | IP pools |
| 10 | 0 | 69.28.158.173 | ve103.fr4.iad.llnw.net | Washington, DC, USA | 46 | + | Limelight Networks Inc. |
| 10 | 0 | 198.32.160.223 | localdomain6 localhost6 | - | 46 | + | - |
| 10 | 0 | 69.65.112.25 | r01.iad.defenderhosting.com | Washington, DC, USA | 40 | + | Virtacore Systems Inc |
| 10 | 0 | 154.54.6.106 | te4-2.mpd01.sjc03.atlas.cogentco.com | San Jose, CA, USA | 78 | +- | - |
| 10 | 0 | 86.137.50.92 | host86-137-50-92.range86-137.btcentralplus.com | - | 53 | -+-- | IP pools |
| 10 | 0 | 69.28.171.201 | tge1-2.fr3.lga.llnw.net | New York, NY, USA | 45 | + | - |
| 10 | 0 | 69.28.171.154 | tge4-1.fr4.lga.llnw.net | New York, NY, USA | 46 | + | Limelight Networks Inc. |
| 11 | 0 | 69.28.158.173 | ve103.fr4.iad.llnw.net | Washington, DC, USA | 44 | + | Limelight Networks Inc. |
| 11 | 0 | 198.32.160.223 | localdomain6 localhost6 | - | 46 | + | - |
| 11 | 0 | 38.104.138.46 | - | - | 79 | +----- | - |
| 11 | 0 | 69.65.112.25 | r01.iad.defenderhosting.com | Washington, DC, USA | 45 | + | Virtacore Systems Inc |
| 11 | 0 | 86.137.50.92 | host86-137-50-92.range86-137.btcentralplus.com | - | 27 | -+- | IP pools |
| 11 | 0 | 69.28.171.201 | tge1-2.fr3.lga.llnw.net | New York, NY, USA | 47 | + | - |
| 11 | 0 | 69.28.171.154 | tge4-1.fr4.lga.llnw.net | New York, NY, USA | 46 | + | Limelight Networks Inc. |
| 11 | 0 | 74.204.190.14 | unknown14.190.204.74.defenderhosting.com | Ashburn, VA, USA? | 120 | + | Virtacore Systems Inc |
| 12 | 0 | 66.151.144.13 | border1.pc1-bbnet1.sje005.pnap.net | San Jose, CA, USA | 74 | + | - |
| 13 | 0 | 69.28.158.173 | ve103.fr4.iad.llnw.net | Washington, DC, USA | 40 | + | Limelight Networks Inc. |
| 13 | 0 | 198.32.160.223 | localdomain6 localhost6 | - | 46 | + | - |
| 13 | 0 | 69.65.112.25 | r01.iad.defenderhosting.com | Washington, DC, USA | 40 | + | Virtacore Systems Inc |
| 13 | 0 | 74.217.77.122 | ooma-3.border1.sje005.pnap.net | San Jose, CA, USA | 76 | + | - |
| 13 | 0 | 205.234.111.129 | r03-8.iad.defenderhosting.com | Washington, DC, USA | 55 | -+ | Virtacore Systems Inc |
| 13 | 0 | 86.137.50.92 | host86-137-50-92.range86-137.btcentralplus.com | - | 34 | -+- | IP pools |
| 13 | 0 | 69.28.171.201 | tge1-2.fr3.lga.llnw.net | New York, NY, USA | 46 | + | - |
| 13 | 0 | 69.28.171.154 | tge4-1.fr4.lga.llnw.net | New York, NY, USA | 48 | + | Limelight Networks Inc. |
| 14 | 0 | 205.234.111.129 | r03-8.iad.defenderhosting.com | Washington, DC, USA | 41 | + | Virtacore Systems Inc |
| ? | 100 | ... | - | - | - | | - |
| ? | 100 | 208.83.244.145 | myxprov.ooma.com | - | - | | - |
------------------------------------------------------------------------------------------------------------------------------------------------------

From my mac I have run a trace route and this is what I got.

Traceroute has started…

traceroute to myxprov.ooma.com (208.83.244.145), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 34.965 ms 2.280 ms 3.505 ms
2 xxx.xx.35.1 (xxx.xx.35.1) 1.695 ms 1.529 ms 1.676 ms
3 10.7.96.1 (10.7.96.1) 11.682 ms 11.487 ms 10.538 ms
4 ip72-xxx-223-xx.dc.dc.cox.net (72.219.xxx.xx) 11.567 ms 24.177 ms 13.208 ms
5 ip68-xxx-0-xxx.dc.dc.cox.net (68.xxx.x.xxx) 12.231 ms 14.531 ms 11.333 ms
6 ashbbrj02-as0.0.r2.as.cox.net (68.1.1.xxx) 10.587 ms 12.383 ms 21.725 ms
7 cr2-cr1.wdc005.internap.net (66.79.146.202) 94.464 ms 98.260 ms 106.628 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 lax009-phx007-832-cr2.lax009.internap.net (66.79.147.181) 114.215 ms 121.059 ms 163.567 ms
15 lax009-sje007-805-cr2.sje007.internap.net (66.79.147.5) 152.356 ms 93.412 ms 91.631 ms
16 cr1-cr2.sje007.internap.net (66.79.146.189) 92.165 ms 94.793 ms 125.476 ms
17 sje-sje007-766-core3.sje.internap.net (66.79.148.130) 134.309 ms 149.547 ms 108.850 ms
18 border1.pc1-bbnet1.sje005.pnap.net (66.151.144.13) 100.006 ms 135.444 ms 114.529 ms
19 ooma-3.border1.sje005.pnap.net (74.217.77.122) 115.675 ms 146.031 ms 119.408 ms
20 myxprov.ooma.com (208.83.244.145) 102.251 ms 110.406 ms 109.335 ms
Jeff
McLean, VA
Cox / Ooma Telo / Apple AEBS (Time Capsule) / Ooma Handset / Premier
CompTia A+ CE
MCITP: Windows 7 Enterprise

murphy
Posts: 7166
Joined: Tue Jan 27, 2009 12:49 pm
Location: Pennsylvania

Re: High Trace Route, can anything be done

Post by murphy » Sun Mar 14, 2010 7:21 am

Something is seriously mis-configured somewhere. That bounced all over the country.

I get 22 hops and 93 ms to that address from north of Philadelphia.
The trip from the east coast to the west coast was 1 hop on the level3 backbone.
Customer since January 2009
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx

JTalbert
Posts: 276
Joined: Tue Jan 12, 2010 8:37 am

Re: High Trace Route, can anything be done

Post by JTalbert » Sun Mar 14, 2010 1:58 pm

murphy wrote:Something is seriously mis-configured somewhere. That bounced all over the country.

I get 22 hops and 93 ms to that address from north of Philadelphia.
The trip from the east coast to the west coast was 1 hop on the level3 backbone.
Do you have any problems with not hearing the party your talking to or them not being able to hear you or anything strange going on, since you on the east coast same as myself?
Jeff
McLean, VA
Cox / Ooma Telo / Apple AEBS (Time Capsule) / Ooma Handset / Premier
CompTia A+ CE
MCITP: Windows 7 Enterprise

dtalwar
Posts: 409
Joined: Thu Jul 16, 2009 8:27 pm
Location: Gold River, CA

Re: High Trace Route, can anything be done

Post by dtalwar » Sun Mar 14, 2010 2:38 pm

I agree with Murphy ... there is something seriously wrong with the way the traffic is getting routed in your case. I get 13 hops, but I'm on the West Coast. Could you try a non-Cox connection, perhaps a neighbor or a friend who is willing to let you try it out?

tommies
Posts: 862
Joined: Sun Mar 01, 2009 8:10 pm
Location: Atlanta

Re: High Trace Route, can anything be done

Post by tommies » Sun Mar 14, 2010 3:22 pm

I have 18 hops with just under 80ms from Atlanta.

Your 1st trace is absolutely crazy. You should call your isp and complain. The 2nd one with cox look ok though.
tommies

Tiger5353
Posts: 37
Joined: Thu Nov 19, 2009 7:45 am

Re: High Trace Route, can anything be done

Post by Tiger5353 » Mon Mar 15, 2010 9:50 am

There are several different ways a router makes its path determinations. Depending on which protocol its been configured to use and if the normal path is up or down it can take as many as 30 hops to get to its destination. Routers can be set to use RIP or OSPF for example and it can make a big change on how its routes traffic.

Post Reply