Anyone else having trouble with Caller ID?

Posts: 1389 · Posted: Mon Nov 21, 2005 10:07 am Post subject:

rapster wrote:

I too have had problems with Caller ID since .52. In fact, at one point I convinced a CS tech to roll me back to .50, only to learn later that this should not have been done because .50 didn't support 911 calls. Yikes!

I've tried the voltage change idea, the ring cadence change idea, the "unplug enough phones so that only 5 devices in the house are connected to the RTP300" idea, and nothing has consistently worked. At this point, I'll get several calls in a row with Caller ID, and then the router refuses to cooperate on Caller ID for a day or two before it behaves again. So, every morning the family asks me, "Well, Dad, think Caller ID will work today?" Groan.

Of course, this is just the latest problem with my Vonage service. And I am referring to problems that go beyond the occasional dropped call. First, my original RT31P2 crapped out all of a sudden one day, taking phone service and internet access down with it. Then, after receiving the replacement RTP300, I couldn't access my employer's VPN, until I figured out after 2 weeks of playing with it that I had to move the RTP behind my DLink router. Then, I get dinged by Vonage for $99 for having failed to return the RT31P2 that was sleeping with the fishes, despite receiving no verbal or written instructions that this was necessary or how best to do it. Now, I'm dealing with the ongoing Caller ID saga.

I have friends and family ask me all the time about switching from POTS to Voip. My response is, "Are you nuts? Sure, the price is great, but unless you have the patience of a saint or want to immerse yourself in the arcane world of ring cadences and VPN passthroughs, stay right where you're at. Do you really want to live in mortal fear of firmware updates, which invariably create as many problems as they solve?"

Frankly, the only reason I don't change to a different Voip provider is my pessimistic belief that they all have problems. So why don't I go back to POTS? Right now, I'm too cheap, but they longer this goes on, the more likely I'll just throw in the towel.

You never heard that you had to return the RT31P2? I received emails daily reminding me to send it back after a week.

Posts: 30 · Vonage Forum Junior Joined: Nov 20, 2005 Posts: 30

Not a word until the charge showed up on my credit card statement.

Posts: 1389 · Posted: Mon Nov 21, 2005 12:15 pm Post subject:

rapster wrote:

Not a word until the charge showed up on my credit card statement.

That is the first I have heard of this one...I have returned 3-4 adapters and everytime I was given an RA number and repeated emails...

Posts: 23 · Vonage Forum Associate Joined: Sep 21, 2005 Posts: 23

Mr_Sorento wrote:

Regarding your intermittent problems with your phones, I too had problems with an older BellSouth caller ID box. I took it out and all is well now on both my Att and Uniden caller ID phones. Did you ever have consisent caller ID on all your phones in the past?

My ATT phone (model 972), with intermittent Vonage CID, is less than 6 months old. It is a two line phone and CID on the other POTS* line always works. So it should work with Vonage too. Anyway, I received a email from Vonage overnight that states they believe they have corrected the problem. And so far today (4 for 4) CID is working with the ATT phone. Will have to see if the streak continues.

(*OT Editorial. Based on my experience with Voip so far, it will probably be a loonnng time before I get rid of POTS. Sure Voip is nominally more economical, but only if you don't count the value of the time you spend troubleshooting. Sad

Plus I want to maintain the security factor of possessing a phone line that will work when the electrical and/or internet service is off, and is not reliant on batteries either. i.e., cell phone.)

Posts: 159 · Vonage Forum Master Joined: Aug 05, 2005 Posts: 159

JMS Wrote:

Quote:

Can anyone provide a pointer to .47 firmware?

If someone wants to provide a site for me to upload the 1.00.47 firmware I will. I just don't want to stage it on my website. Also, for whatever reason Vonage does not have this available anymore on their site. There might be a very good reason for this so if you do use 1.00.47 use it at your own risk. What kind of risk? For example being totally utterly shocked that CID works consistently with this version... Very Happy

Posts: 3198 · Posted: Mon Nov 21, 2005 3:49 pm Post subject:

I can put it up at least temporarily. pm'ing is probably a better option though.

Posts: 4 · New Forum Member Joined: Apr 17, 2005 Posts: 4

[quote="optiman"]

Mr_Sorento wrote:

My ATT phone (model 972), with intermittent Vonage CID, is less than 6 months old. It is a two line phone and CID on the other POTS* line always works. So it should work with Vonage too. Anyway, I received a email from Vonage overnight that states they believe they have corrected the problem. And so far today (4 for 4) CID is working with the ATT phone. Will have to see if the streak continues.

My CID isn't working this evening; I'm curious; is your router still running .55? If not, can you determine what Vonage might have done to "correct the problem"?

Posts: 122 · Posted: Mon Nov 21, 2005 9:55 pm Post subject:

jms,

I'm still running 1.00.55 on my RTP300 and one week later, I STILL HAVE CALLER ID!!!!!!!!!!!! YAY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Oh, back to your question....Look back several pages of this subject and you will see an earlier post from me on what to do (Call Vonage and tell them to implement the changes I've stated earlier). If they ask if you're using house wiring, tell them no and that you want the changes I've stated implemented on your RTP300. Afterwards, your caller ID should be fixed. Let me know how it goes.

Posts: 10 · Vonage Forum Associate Joined: Sep 22, 2005 Posts: 10

Hello,

Be careful if you force your adapter back to older firmwares. The latest firmware changes bring customer adapter hardware in line with the latest Vonage system changes. I believe 911 capability / compatibility is one of these changes. Some of the surface functionality may have suffered in the latest FW updates, but these are not the only changes.

Posts: 199 · Vonage Forum Master Joined: Mar 26, 2005 Posts: 199

Interesting.

I called Vonage and they gladly restored me to firmware .50. Problems went away. I started having issues again the other day. Been busy so haven't been able to check until know but I see firmware .55 is back on this router again along with my problems.

Issues:

Caller ID/Call Waiting ID
Voicemail Notification
Occasional Audio issues