said by thewolfman:It is the VDV22 device. I called Vonage regarding the issue, and they sent me the new device. I also connected the device to the cable modem with a wired phone and the issue still exists. I think I'll try your other suggestion and take it to my in-law's house and try it.
Time warner says the issue isn't on their end and Vonage say it is on time warner's end, here I am, stuck in the middle(great song!!).
I'm a bit leary now to invest in a different device to handle the VoIP, as I don't know if it will fix the issue. Hate the thought of going back to Verizon POTS.
The finger pointing between the ISP and the VoIP provider is pretty much SOP, no matter who is the ISP or the VoIP provider.
My earlier suggestion of using a different Vonage ATA was strictly intended for the case where you were able to determine that the Vonage box was at fault. I definitely would not invest the time or money on a different Vonage ATA unless I knew for sure that the Vonage ATA was the culprit. In my case, I was able to prove that the VDV-23 was causing my problems because I had a retired RTP300 and a VT2442 to test with. If those old ATAs had not taken up more comm rack space than I had available (and they generated too much heat to allow safe stacking), I would have just used them instead of buying the D-Link VTA-VR boxes (they are even smaller than the VDV-23 and are also safely stackable).
If I had not been able to resolve my Vonage problems, I would probably have switched to Comcast's VoIP product instead of going with AT&T POTS. I recently did try to use only cell phone access, but that did not work out very well as my only telephone service, and I reactivated my Vonage service.