[kawaisunn]

Thank you all for the informative site! I have a Motorola VT2442 router, Vonage (sigh), and am connected to my ISP via a Motorola Canopy network. Vonage sent me a Linksys router initially but after many agonizing hours on the phone (at work!) and a dozen e-mail later I returned it for the Motorola. With the Linksys my internet connection suffered repeated timeouts and when I could complete a call it was often unintelligable to the receiving party. The situation hasn't improved much with the Motorola. My ISP has jacked my connection up to 750KBs to see if call quality went up or at least became stable, I have tried many configurations of router/home network (all wire in the house); in the five months we have had the Vonage I am beginning to regret talking my wife into it. We have no land phone line, DSL and cable internet are not options where we live. I tested my upload speed over a 3 day period, at different times of day, and all of my results were well above Vonage's stated requirements.

Any suggestions are welcome. I've wondered if the Canopy system is part of the problem.... ? I am more than happy to provide more detailed information to anyone that is willing to help me troubleshoot this!

Thanks in advance!~

[mberlant]

One thing you can check is to see if Canopy is delivering a public IP address to you or a private IP address.

You should visit Voxilla's IP checker utility and note the public address your ISP is reporting you as having. Then look on your router's status screen and make note of your router's WAN IP address. These two numbers should be the same.

If these two numbers do not match, the next test to perform is a traceroute. From a DOS window on your Windows PC, enter "tracert voxilla.com". In an environment where you have a public IP address, that IP address should show up as line 2 of your traceroute results. If you see your public IP address on line 3 of these results it means that your ISP has one NAT router between you and the public internet and you should put your ATA into your router's DMZ to reduce the number of NAT boundaries to the one that your ATA can handle. If you see your public IP address farther down the list than line 3 you will have significant trouble with any VoIP service provider unless you can convince your ISP to correct the situation.

Please let us know what you find out.

[kawaisunn]

Thank you for the lead, mberlant. A quick aside: I have been home all this week and my internet has been nearly non-functional each day from 11 am or so till 8 or 9 pm. I intended to get to the bottom of my VoIP headache but the lack of a connection has become an issue of it's own. I went out to wash my south facing antenna this afternoon (grasping straws) in the heat and it occured to me that my connection falters then drops during the hottest part of the day. Not certain if this is the cause but it does fit.

This morning I used the IP checker and compared it to tracert 's several times. The checker returned an adds. of 66.232.94.240 My connection gave up the ghost before I could reply. This tracert is from a few minutes ago...

Tracing route to voxilla.com [72.34.96.22]
over a maximum of 30 hops:

1 25 ms 19 ms 24 ms 10.10.30.1
2 22 ms 94 ms 29 ms rns-gateway.ruralnetwork.net [66.232.94.1]
3 * 19 ms 19 ms 66.232.95.1
4 48 ms 19 ms 29 ms 66.232.64.157
5 13 ms 14 ms 29 ms 66.232.64.1
6 19 ms 19 ms 19 ms p7-0.gw03.bois.eli.net [216.190.218.169]
7 28 ms 29 ms 79 ms srp2-0.cr01.bois.eli.net [208.186.20.193]
8 49 ms 40 ms 34 ms so-0-0-0--0.cr02.slkc.eli.net [207.173.114.66]
9 27 ms 34 ms 40 ms so-7-0-0--0.cr01.slkc.eli.net [207.173.115.241]

10 39 ms 44 ms 50 ms p10-0.cr01.rcrd.eli.net [207.173.114.9]
11 * 65 ms 65 ms p11-0.cr02.rcrd.eli.net [207.173.115.114]
12 617 ms 159 ms * p9-0.cr01.sntd.eli.net [207.173.114.57]
13 52 ms 49 ms 264 ms so-0-0-0--0.er01.plal.eli.net [207.173.114.138]

14 47 ms 49 ms 49 ms paix-ix.paix.ca.rcn.net [198.32.176.126]
15 48 ms 49 ms 59 ms ge5-1.aggr1.sfrn.ca.rcn.net [208.59.255.2]
16 188 ms 49 ms 54 ms 216.164.65.198
17 43 ms 64 ms 54 ms ssfca-core1-gige-1-1.race.com [64.201.96.2]
18 43 ms 44 ms 49 ms 72-34-96-22.race.com [72.34.96.22]

Trace complete.

If I am not mistaken my ISP is routing me through a private 10.10.30.x before their public gateway. Just as all of this morning's results the 66.232.94.240 adds. wasn't returned. Is this unusual? Your reply states " you should put your ATA into your router's DMZ ". The 10.10.30.x gateway and addss. are from the ISP's DHCP (my internal router is 192.168.15.x) Can I take this to mean I need to convince my ISP to port forward (?) my ATA thru the 10.x.x.x to a static (?) 66.232.94.x ? I am certain they would work out some solution with me. At what point/configuration, if at all, is my own DHCP and/or NAT redundant or counterproductive?

I apologize for any absurdities above! I'll take in friends' in need computers now and then for a tune up but my core home network currently consists of the VT2442, my wife's 2000pro (cough) Gateway, my 2003 Enterprise server (down because of robbed parts), my Suse/xp workstation and a couple hubs. Arguing with VoIP, and the new Houdini Internet, I have put the above (functioning as of late) nodes in many configurations. Without a baseline I cannot say what has been good for the phone and what hasn't. Anyone that cares to offer their expertise and/or opinions are appreciated!

Thanks, again, in advance.

Ks

[mberlant]

What is truly unusual is that your public address, 66.232.94.240, shows up nowhere in the traceroute. Since you have your own router distributing addresses in the 192.168.15.x range, that 10.10.30.1 address seems to be a wrongly configured Access Router at your ISP. What address does your router show as its WAN IP address? Does it show 66.232.94.240 or 10.10.30.xx?

[kawaisunn]

10.10.30.11 Scince I began service both ranges have come into play. Included is a fresh tracert.

Tracing route to voxilla.com [72.34.96.22]
over a maximum of 30 hops:

1 * * * Request timed out.
2 16 ms 14 ms 14 ms 10.10.30.1
3 * 17 ms 9 ms rns-gateway.ruralnetwork.net [66.232.94.1]
4 20 ms 19 ms 14 ms 66.232.95.1
5 21 ms 19 ms 19 ms 66.232.64.157
6 14 ms 19 ms 19 ms 66.232.64.1
7 * 18 ms 19 ms p7-0.gw03.bois.eli.net [216.190.218.169]
8 22 ms 22 ms 19 ms srp2-0.cr01.bois.eli.net [208.186.20.193]
9 32 ms 29 ms 24 ms so-0-0-0--0.cr02.slkc.eli.net [207.173.114.66]
10 * 30 ms 24 ms so-7-0-0--0.cr01.slkc.eli.net [207.173.115.241]

11 44 ms 44 ms 39 ms p10-0.cr01.rcrd.eli.net [207.173.114.9]
12 47 ms 39 ms 39 ms p11-0.cr02.rcrd.eli.net [207.173.115.114]
13 43 ms 39 ms 44 ms p9-0.cr01.sntd.eli.net [207.173.114.57]
14 53 ms 49 ms 49 ms so-0-0-0--0.er01.plal.eli.net [207.173.114.138]

15 54 ms 89 ms 44 ms paix-ix.paix.ca.rcn.net [198.32.176.126]
16 * 104 ms 234 ms ge5-1.aggr1.sfrn.ca.rcn.net [208.59.255.2]
17 47 ms 49 ms 259 ms 216.164.65.198
18 46 ms 44 ms 54 ms ssfca-core1-gige-1-1.race.com [64.201.96.2]
19 49 ms 44 ms 49 ms 72-34-96-22.race.com [72.34.96.22]

Trace complete.

C:\Program Files\Support Tools>

[kawaisunn]

Oh, and the IP check still returns 66.232.94.240

[jayw654]

does anyone know how to get into the core settings of the voip router/voip of the motorola vt2442, i did able to swidel a bit of info out of them don't know if it's that really important or what people can do with it but here goes if you have a voip vt2442 motorola, try this enter 192.168.15.1 and put this in as your user name a password @ login username: user password: tivonpw it's obvious my main goal is to unlock the box, any info i would be grateful for!!

[kawaisunn]

I've been out of town working for the last four weeks so I havn't had the opportunity to really mess with my setup or talk to my ISP. I downloaded some manuals and white papers for Canopy and thumbed through them the morning I left town. I believe the 10.10.30.xx addys are the Canopy network. The 66.232.94.xx are my ISP's. I whois'ed the 66.232.64.xx and 66.232.95.xx . They belong to a company in Boise, which is fairly close to me, and I suppose it has something specifically to do with my ISP's service.

I'm going to mail tech support at my ISP tonight and see if there is some way to get an address that's "closer" to the internet. I now have dial-up service where I'm working so I will check this thread from time to time and post what happens with my ISP. They are interested in offering VoIP service and were toying with it a little at one time but had problems with it. I think they might be game to try about anything to get mine to function well. Any suggestions worth passing along to them would be appreciated!