Got something else to discuss that is not covered by the previous forums? Post it here!
#62172 by scg
Sun Aug 15, 2010 7:55 pm
Have you tried doing a tracert to www.whichvoip.com to see where the traffic is getting hung up? You can also get the IP address for the site by pinging it from another PC that is able to access it, and doing a tracert to the address directly. If it is a DNS problem, you will get there with the IP but not the domain name.
#63425 by roadshow
Sat Aug 28, 2010 6:09 am
I'm still having this problem, only when the ooma is connected somewhere before the computer.
Modem-PC, it works fine
Modem-OOMA-PC, doesn't work
Modem-Router-PC, works fine
Modem-OOMA-Router-PC, doesn't work
I have tried other PC's in my house and get the same results.


Here are the results of the trace:

Tracing route to whichvoip.com [74.124.194.146]
over a maximum of 30 hops:

1 24 ms 15 ms 2 ms router.belkin [192.168.2.1]
2 6 ms 3 ms 3 ms 172.27.35.1
3 23 ms 17 ms 17 ms cable-mac1-0.rochnyirn-ar402.nyroc.rr.com [69.20
7.128.1]
4 21 ms 20 ms 28 ms gig11-1-2.rochnybtn-rtr01.nyroc.rr.com [24.93.5.
41]
5 18 ms 18 ms 18 ms xe-3-2-0-0.vstlny11-rtr000.nyroc.rr.com [24.92.2
24.122]
6 25 ms 24 ms 24 ms ae1-0.albynyyf-rtr000.nyroc.rr.com [24.24.21.208
]
7 27 ms 24 ms 24 ms ae10-0.albynywav-rtr03.nyroc.rr.com [24.24.21.21
9]
8 41 ms 40 ms 52 ms xe-11-0-0.bar1.Boston1.Level3.net [4.79.0.69]
9 46 ms 65 ms 42 ms ae-0-11.bar2.Boston1.Level3.net [4.69.140.90]
10 34 ms 34 ms 36 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
11 70 ms * 38 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]

12 36 ms 35 ms 36 ms ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45]

13 98 ms 106 ms 91 ms ae-2-2.ebr4.SanJose1.Level3.net [4.69.135.185]
14 95 ms 93 ms 102 ms ae-84-84.csw3.SanJose1.Level3.net [4.69.134.250]

15 108 ms 112 ms 102 ms ae-83-83.ebr3.SanJose1.Level3.net [4.69.134.233]

16 112 ms 102 ms 112 ms ae-2-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]

17 103 ms 105 ms 126 ms ae-4-90.edge3.LosAngeles1.Level3.net [4.69.144.2
01]
18 104 ms 102 ms 106 ms cr1.lax1.us.packetexchange.net [4.71.136.2]
19 107 ms 106 ms 107 ms te4-1.cr1.lax1.us.packetexchange.net [69.174.120
.141]
20 103 ms 106 ms 118 ms 67.199.135.170
21 * * * Request timed out.
22 * * * Request timed out.
23 * *
#63467 by roadshow
Sat Aug 28, 2010 5:56 pm
I'm bumping this. I'm hoping that one of you guys might be able to look at my trace route that was in the previous reply, and give me some ideas why that address fails.
#63470 by murphy
Sat Aug 28, 2010 6:37 pm
Possibly whichvoip was down or overloaded. It is one hop past your last IP address.

4 9 ms 8 ms 6 ms te-2-4-ur01.upperdublin.pa.panjde.comcast.net [68.85.77.149]
5 9 ms 8 ms 9 ms te-2-1-ur01.lansdale.pa.panjde.comcast.net [68.86.209.161]
6 11 ms 9 ms 9 ms te-2-1-ur01.pottstown.pa.panjde.comcast.net [68.86.209.157]
7 11 ms 11 ms 11 ms te-2-1-ur01.phoenixville.pa.panjde.comcast.net [68.86.209.153]
8 11 ms 11 ms 11 ms te-8-7-ar01.coatesville.pa.panjde.comcast.net [68.86.209.149]
9 13 ms 13 ms 14 ms te-0-2-0-6-ar01.ivyland.pa.panjde.comcast.net [68.85.34.229]
10 14 ms 13 ms 14 ms pos-0-10-0-0-ar01.401nbroadst.pa.panjde.comcast.net [68.85.192.190]
11 18 ms 23 ms 18 ms pos-0-1-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.90.13]
12 34 ms 32 ms 33 ms pos-1-7-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.87.86]
13 56 ms 54 ms 54 ms pos-1-10-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.86.129]
14 88 ms 90 ms 90 ms pos-0-11-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.87.37]
15 99 ms 90 ms 90 ms 75.149.231.238
16 90 ms 90 ms 90 ms 67.199.135.170
17 90 ms 90 ms 90 ms 74.124.194.146

Trace complete.
#63475 by roadshow
Sun Aug 29, 2010 3:32 am
murphy wrote:Possibly whichvoip was down or overloaded. It is one hop past your last IP address.

4 9 ms 8 ms 6 ms te-2-4-ur01.upperdublin.pa.panjde.comcast.net [68.85.77.149]
5 9 ms 8 ms 9 ms te-2-1-ur01.lansdale.pa.panjde.comcast.net [68.86.209.161]
6 11 ms 9 ms 9 ms te-2-1-ur01.pottstown.pa.panjde.comcast.net [68.86.209.157]
7 11 ms 11 ms 11 ms te-2-1-ur01.phoenixville.pa.panjde.comcast.net [68.86.209.153]
8 11 ms 11 ms 11 ms te-8-7-ar01.coatesville.pa.panjde.comcast.net [68.86.209.149]
9 13 ms 13 ms 14 ms te-0-2-0-6-ar01.ivyland.pa.panjde.comcast.net [68.85.34.229]
10 14 ms 13 ms 14 ms pos-0-10-0-0-ar01.401nbroadst.pa.panjde.comcast.net [68.85.192.190]
11 18 ms 23 ms 18 ms pos-0-1-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.90.13]
12 34 ms 32 ms 33 ms pos-1-7-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.87.86]
13 56 ms 54 ms 54 ms pos-1-10-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.86.129]
14 88 ms 90 ms 90 ms pos-0-11-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.87.37]
15 99 ms 90 ms 90 ms 75.149.231.238
16 90 ms 90 ms 90 ms 67.199.135.170
17 90 ms 90 ms 90 ms 74.124.194.146

Trace complete.


The sight was not down. I connected to my neighbors wireless and got right through. The, I l connected to mine, and couldn't get there. My trace always stops at 67.199.135.170. I also noticed that I can't get to www.flyerie.com. the trace hangs at that same address.
How could the OOMA be preventing me from getting there? I dsconnected the OOMA last night and tried those sights again, got right in.
#63485 by southsound
Sun Aug 29, 2010 6:52 am
Really strange since many of us use the whichvoip.com speedtest to validate our connection speeds. I can't figure out why you can reach them, even after reading the entire thread - but many of us have no problem so unless ooma is only blocking some systems from access (which would be very strange), I don't think it is them.

Who is online

Users browsing this forum: No registered users and 7 guests