Vonage has caught up with the forum, I called today with these instructions from Mr. Sorrento:"Mr_Sorento wrote:For everyone with the RTP300 still having Caller ID problems, try the following:

Call up and either speak with a good CS rep or Tech Support rep and ask them to change your ring [1] cadence value to: 0xFFFFFCC000000000

Also, have them change your on-hook-voltage from 48 to 45"

and the Vonage tech said those were on this screen too as the fix. Of course, why not deploy system wide, I don't know. But it did work.

so how many ppl has this worked for? is this a home wiring only fix? how long does the fix work for? damn cid works for like one day after a reboot with the Vonage "fix" of the week. i don't think anyone has tried this fix for me yet.

Going on 2 weeks now and have had several reboots and even some updates pushed to it by Vonage and it still works like a champ!!! YAY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Try it, you'll like it!

This may depend on who you get when you call in but I think Vonage is getting enough complaints they are trying to help. My RTP300 works fine with firmware .50. I found out that their servers update you automatically if your firmware is not current. Apparently, by default their servers grab this current firmware off an FTP connection. The tech I talked to switched me to HTTP for my auto firmware update and then moved me back to firmware .50 (which works for me... CID, etc). Now, .50 is still on my RTP300. So, at a guess the firmware update via HTTP must not work (or file is not on the HTTP connection) or something because it hasn't updated back to .55 and things are working again. Not 100% but way better than .52 or .55.

Vonage has caught up with the forum, I called today with these instructions from Mr. Sorrento:"Mr_Sorento wrote:For everyone with the RTP300 still having Caller ID problems, try the following:

Call up and either speak with a good CS rep or Tech Support rep and ask them to change your ring [1] cadence value to: 0xFFFFFCC000000000

Also, have them change your on-hook-voltage from 48 to 45"

and the Vonage tech said those were on this screen too as the fix. Of course, why not deploy system wide, I don't know. But it did work.

so how many ppl has this worked for? is this a home wiring only fix? how long does the fix work for? damn cid works for like one day after a reboot with the Vonage "fix" of the week. i don't think anyone has tried this fix for me yet.

I've looked into this extensively. I've been measuring my on-hook line voltage constantly for the last two weeks or so and it's gone everywhere between 46 and 50 volts. (Currently it's at 47v.) None of those adjustments made any difference for me. Regardless of the voltage, the first incoming call showed ID and the rest didn't. In between the first and second call, the voltage did not change. The only assumption that I have is that the voltage issue is only for the house wiring problem. It's an easy assumption for me since my CID either always worked for all the phones or didn't work for any of them.

The next point is much more obvious. In version 52 and 55 of the firmware, having Vonage change the ring cadence fixed most of the CID issues. Of the ones that are left, they (mostly) reported that by connecting only one phone without house wiring, CID was OK.

It seems apparent that they two changes together should address all of the problems mentioned on this thread with just a few exceptions. There have been a few people reporting inconsistent CID (working, not working, working on half of the phones in the house...) and if the pattern holds up it seems like these inconsistencies should be addressed with voltage tweaking, rather than ring cadence, but that part is hard to know for certain.

I'm not a phone tech, but a broadband phone company with a million+ customers should know what the "standard" ring cadences and phone voltages should be. I don't know what the standards are, but I bet they've been in place for 20 years or more by know. As far as why they haven't pushed these settings to everyone with an RTP300 is anyone's guess but they may have finally adapted an "If it ain't broke don't fix it" strategy. Since there seems to be enormous inconsistency with the way these problems are being handled that philosophy might make more sense in the long run.

Well, I seem to be one of the few for which the ring cadence change and the on hook voltage change don't work. I had the Vonage CSR make these changes this morning, and since then I've had about 60% CID success.

I have a buddy who said that a Vonage CSR told him several days ago that the recommended changes are "off hook current" to 25 and "hook voltage" to 43. I guess I'll call Vonage back and have them try these settings.

On a side note, it was almost sad to hear the CSR thank me for sharing the fix with him this morning (even though it wasn't the fix in my case). He said that he continues to get calls on this issue and never knows how to help the customer deal with it.

I called CS and they weren't able to help. You need ask them to transfer to their suppervisor or level 2 tech support in New Jersey. Tech support person in NJ told me that new firmware is due out soon. There is a problem with CID when you have home wiring. Aside from the previous changes already mentioned they also changed my Off Hook Current to 29 from 23.

[quote=]Regretfully emailing Vonage is a wast of time! Commit to spending half an hour and give them a call Monday.[/quote]

Not a complete waste of time- I e-mailed three or so weeks ago and did get this reply recently - ref call id problem- I sent to Vonage around Nov 3 - (3 week reply)- sp maybe e-mailing is a waste of time cause caller id didnt work yesterday once again after I plugged in a caller ID box with ACR.