No sound and VT2442/2142 locks up

Posts: 3 · New Forum Member Joined: Feb 29, 2008 Posts: 3

1. San Jose
2. Comcast cable
3. 16Mb/s down, 2Mb/s up
4. Motorola SB 5120
5. Motorola VT2442 abd VT2142
6. Modem ---> Dell TrueMobile 2300 router ---> Switch ---> VT2442 (and other devices) ---> Mac
7. I have an interesting issue that has numerous symptoms. First I noticed that people would call or I'd call out and there would be no audio going either direction. This is on my VT2442. The call would complete--according to the other side, but there was no voice traffic. Later I found that the router was hung up in some fashion. The Mac connected to it on the LAN side couldn't resolve any hosts (DNS) and it also was unable to connect to the admin page at 192.168.15.1. ssh and ping also failed. Resetting the modem by removing power would correct these issues for another 12-24 hours. Calls would work, but eventually the same thing would occur.

After a couple of calls to support, Vonage is sending me another modem. Here's where it gets interesting though. I happen to also have a VT2142 because I ordered another line and got it for the cost of shipping. I switched to it to avoid the problem for now. But guess what?! The same thing happened.

Now I believe this should never happen with reasonable settings on the modem, but I did set a few things on my network and I'm wondering whether they somehow confused the modem. Because I wanted access to the single Mac behind the Vonage device, I enabled DMZ for that device. This also required setting a static DHCP address for this MAC address in the Vonage device. This allowed me to get to the Mac via file sharing, ssh, screen sharing, etc. I'm wondering whether this setting may have confused the modem so for the moment, I've turned off DMZ.

So the other interesting aspect is that I had only the occasional glitch over many months until about a week ago when this started happening once a day (or every 12-24 hours). I didn't change anything before it happened, either.

Has anyone else seen this issue or have any good or bad experience with the DMZ feature? Is it possible that one of the other folks in my house could be doing something to trip up the VT2442/2142?

8. Ran the test from a computer on the same switch as the VT2142:
Speed test statistics
---------------------
Download speed: 1058160 bps
Upload speed: 2900096 bps
Quality of service: 41 %
Download test type: socket
Upload test type: socket
Maximum download pause: 189 ms
Average download pause: 16 ms
Minimum round trip time to server: 93 ms
Average round trip time to server: 94 ms

Voip test statistics
--------------------
Jitter: you --> server: 2.5 ms
Jitter: server --> you: 8.0 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 2.1 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Number of supported Voip lines: 17
Estimated MOS score: 3.6

Thanks,
. John

Posts: 350 · Vonage Forum Evangelist Joined: Dec 04, 2005 Posts: 350

When you switched the devices did you also switch the power supply?

Posts: 832 · Vonage Forum Evangelist Joined: Jun 08, 2007 Posts: 832

Not sure what is going on with your set up but this is what works for me:

Cable Modem - - > Vonage Device - address = 192.168.15.1 (DHCP On, starting with 192.168.15.3)) - - > Router (static IP 192.168.15.2) - DHCP On assigning 192.168.55.2 to 100 allowing 192.168.55.101-254 for static IP's if you wish.

Set your DNS and gateway on the router to 192.168.15.1

Your SB 5120 probably uses 192.168.100.xxx, so stay away from that subnet in setting up your network.

With this set up, I can access everything within the network (even the cable modem (192.168.100.1) config page, the Vonage device (192.168.15.1) config page and the router (192.168.55.1) config page. I also can (via port forwarding implemented on the Vonage 2142 AND the router) access an ftp server and VNC via my public internet address.

Lastly, I have good call quality with much lower specs than you (4mb/s down, 400 kb/s up). I have been told that the vt2142 has a "built in" QOS for phone, so putting it in front allows that to operate.

Posts: 3 · New Forum Member Joined: Feb 29, 2008 Posts: 3

I was a little leery of putting the Vonage device in my main traffic path. I have a good setup with great speeds and wasn't sure I wanted to "trust" it. I may try this to see whether I get full speeds. I'll need to do some more wiring to get the phone line from where the cable modem is to where the phone is in order to try this.

With regards to the power supply, I thought to do that after the new device locked up, too. Assuming that it works well with both DMZ turned off and the new power supply, I'll try turning DMZ back on again.

I still don't think the network setup I have should cause the device to lock up.

Posts: 4777 · Vonage Forum **MVM** Joined: Aug 30, 2005 Posts: 4777

For what it's worth, your measured download speed is a far cry from what you say it should be. And your packet losses on receive are high.

Posts: 3 · New Forum Member Joined: Feb 29, 2008 Posts: 3

Well, it appears that swapping out the power supply stopped the lock-ups. I'm surprised, but glad it seems to have really been some hardware.

I'm not sure why the Voip test reports such a lower bandwidth than speedtest.dslreports.com does. I'm not running it on the path through the Vonage device.

I still move the device to be my main Broadband router and see whether my network speeds are still high and whether QoS might improve.

Posts: 111 · Vonage Forum Senior Joined: Jan 26, 2008 Posts: 111

duetjohn wrote:

I still move the device to be my main Broadband router and see whether my network speeds are still high and whether QoS might improve.

The problem with that is that if you are running a Voip test for QoS and such, the test site isn't accessing your Voip device but rather using a javascript thingy running on your computer and simualting a call from there.

Putting your Voip device in front of everything will tell you whether it is choking off the path your puter uses though, because if your results tank you know your puter's connection to the 'net is being choked off. On the other hand, if you get your ViOP device out of the picture or just plugged in to the same place as your puter is connected then it should enjoy the same QoS your machine did during the test.

Worst case scenario you might have to adjust your router's settings to allow calls to receive priority status, assuming it doesn't do it for you already, and also assuming you have a lot of other traffic that would choke off your voice bandwidth.