Anyone else having trouble with Caller ID?

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

kpdillon wrote:

Firmware may have changed behavior I am guessing.

I'm pretty sure you're right. The day they pushed 52, my short ring problem went away and the caller ID problem replaced it.

Posts: 122 · Posted: Wed Oct 19, 2005 9:27 pm Post subject:

I'm going to have to correct myself from my last post (above). With the latest firmware (.50) I've got a normal ring cadence and for a while my caller ID was working without any problems. However, after a few calls or so, caller ID stops working. Phone still rings fine, but no caller ID. I have to power cycle my RTP300 in order to get caller ID to work again. This has happened twice now. Grrrrrrrrrr!!!!!!! Looking forward to that new firmware release....

Posts: 48 · Full Forum Member Joined: Sep 22, 2005 Posts: 48

I got this message in email:

Quote:

In response to your email, we will be releasing a new firmware at the end of the week that will resolve the issue with caller id. We appreciate you as a valued customer.

Posts: 34 · Vonage Forum Junior Joined: Sep 07, 2005 Posts: 34

So, did the firmware get pushed? Do we need to reset anything? Is Caller-ID resolved for most (all?) of us?

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

Haven't seen it here yet.

Posts: 12 · Vonage Forum Associate Joined: Sep 07, 2005 Posts: 12

I too got normal ring cadence but lost CID when .52 came. I called level II support who stated "the engineers are aware and are working on a solution" which I interpreted as "fixed in the next firmware, maybe..."

Actually, to be more specific, my CID is intermittent. I have 4 CID enabled sets plus one non-CID set, not to mention my modem and TiVo. Sometimes CID data will appear on a random set. Looks to be like a voltage issue (telcos commonly put line kickers in place for these problems, especially for very lengthy distances from CO to customer.)

Posts: 71 · Full Forum Member Joined: Jul 19, 2005 Posts: 71

Hi all, below is a message I posted in the Skype forum relating to CLI and a particular DECT cordless phone I use the "Dualphone" www.dualphone.net.

The problems revolves around CLI working then not working in t he UK, this sounds similar to the problem you are describing here in the US, my ATA is a linksys RTP31P2
******************

Hi All,

I have noticed a problem with CLI that might be related to the Dualphone and am interested to hear if anyone else has experienced similar.

Skype on my Dualphone is fine and one the landline side of the Dualphone I had been using a BT landline until recently.

I have been experimenting with Vonage recently so have the landline side of the Dualphone pluged into a Vonage Linksys ATA. On imcoming Vonage calls CLI is fine for a while then seems to die. If I power off the ATA or the Dualphone base it makes no difference, still no CLI. If I now plug a hardwired BT telephone into the ATA I see CLI, plug the dualpone back in and no CLI.

If I now plug my Dualphone into my BT landline and ring it I see CLI again, put the Dualphone back into the Vonage ATA and it bursts back into life again with CLI.

As you can see from above you can point the finger in either direction. The config of my Vonage ATA is correct with regard to CLI. Vonage have offered to change the ATA but I am not convinced this is the issue.

As mentioned previously I would be interested if anyone has seen problems with the Dualphone displaying CLI.

Regards,

Paul

Posts: 4 · New Forum Member Joined: Oct 24, 2005 Posts: 4

Forgive me for asking this but I am not very savvy tech person. I have been having the same issues as everyone else on this thread. Could someone explain what I will need to do once the new firmware is released? And when will I know it has been released? Thanks!

Posts: 2 · New Forum Member Joined: Jul 25, 2005 Posts: 2

My problem started about a month ago. Only on cell phone calls. It used to show the caller name but now shows wireless caller and the number. All other calls work fine now. Go figure. Rolling Eyes

Posts: 48 · Full Forum Member Joined: Sep 22, 2005 Posts: 48

I talked with a guy in tech support last night for some time. He was, as far as I know, a level 1 guy but I have to say he sounded very sure of everything he was saying. He definitely wasn't going through a script. His answers were clear and concise.

He told me several things.
1) Rolling back the firmware was a temporary solution. According to him, there is no way to make the rollback permanent on an individual basis. Basically, after the rollback there is some finite time until the system identifies an adapter with old firmware. As soon as the server recognizes the old version, it re-updates to the new one.

2) I asked him why they don't roll back anyone and he said because they told him the release of the fix is imminent.

3) Interestingly, he has no idea when the new firmware will be out. Officially, the date is still last Friday.

4) They won't allow you to change the ring cadence anymore. Apparently, although it fixes one thing it breaks another (he wouldn't say was what is breaking). Even if that's not true they aren't changing the cadences.