the low-down on the recent caller ID problem

Posts: 423 · Vonage Forum Evangelist Joined: Oct 03, 2005 Posts: 423

The default value for the ON_HOOK_VOLTAGE field is 48 volts, not 45. The fix was to DROP the voltage to 45, not increase. I have seen this fix a couple of cases, so it does work in some cases.

As far as a board or forum of some kind that listed all known issues and their status, well, keep dreaming. There is something a bit like that on the intranet here but it usually doesn't have many details except the 'engineering (web dev, NOC, et al) are aware and working on the problem.'

Anyway this would likely result in more calls coming in here which we don't want, because there are some informative tidbits on there that are definitely not for public consumption. Which I will sell to the highest bidder.

Just kidding!

Posts: 2257 · Posted: Wed Nov 09, 2005 3:31 pm Post subject:

ColdGin wrote:

Which I will sell to the highest bidder.

I'll start at $25. But if we all pool the money, you get a higher total amount. So why bid?

ColdGin wrote:

Just kidding!

Dangit!!!! Wink

Posts: 2257 · Posted: Wed Nov 09, 2005 3:36 pm Post subject:

ColdGin wrote:

As far as a board or forum of some kind that listed all known issues and their status, well, keep dreaming. There is something a bit like that on the intranet here but it usually doesn't have many details except the 'engineering (web dev, NOC, et al) are aware and working on the problem.'

I wouldn't even want all that. Just a synopsis of what issues are known, and common, and being worked on. A simple page with:

WRTP54G: 3 Known Issues:
1. The Router ****: We are never going to fix this and will ignore any further calls or emails to CS, just like all the calls you've made so far.
2. Caller ID not working: Introduced in 1.00.52, still around, trying to fix, (suggest a few workarounds).
3. Blue lights are too bright: Field fix available - CS can provide you with a recommended brand of Duct Tape (tm) to correct.

Smile

Posts: 122 · Posted: Wed Nov 09, 2005 6:28 pm Post subject:

ColdGin,

I found this on the other thread "Anyone else having problems with Caller ID?". Thought maybe you or someone else could review it and incorporate it into the next firmware release for the RTP-300 (if it works as it's said it does). I think kpdillon wrote it:

I have an RT300 running firmware 1.00.55 and don't have any issues with callerID. I wonder if broken callerid has anything to do with how the default ring cadence is set. I asked Vonage to originally set my default ring cadence to 0xFFFFFC000000000 which broke callerID after the first power up incoming call. I have since asked them to change my ring cadence to 0xFFFFFCC000000000. Since then both my incoming call ring length and callerID have worked flawlessly. For those having problems with callerID, I wonder if this will fix the issue. Worth a shot IMHO if you are experiencing problems with callerID and need this fixed ASAP.

Posts: 114 · Vonage Forum Senior Joined: Aug 05, 2005 Posts: 114

NateHoy wrote:

ColdGin wrote:

As far as a board or forum of some kind that listed all known issues and their status, well, keep dreaming. There is something a bit like that on the intranet here but it usually doesn't have many details except the 'engineering (web dev, NOC, et al) are aware and working on the problem.'

I wouldn't even want all that. Just a synopsis of what issues are known, and common, and being worked on. A simple page with:

WRTP54G: 3 Known Issues:
1. The Router ****: We are never going to fix this and will ignore any further calls or emails to CS, just like all the calls you've made so far.
2. Caller ID not working: Introduced in 1.00.52, still around, trying to fix, (suggest a few workarounds).
3. Blue lights are too bright: Field fix available - CS can provide you with a recommended brand of Duct Tape (tm) to correct.

Smile

Electric Tape works better Smile

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

NateHoy wrote:

skinnydude wrote:

Unfortunately 1.00.52 fixed a few very important issues so Vonage WILL NOT roll you back to 1.00.50 so don't even ask.

Can you drop a few hints as to what those issues were?

Two that it fixed for me were the short ring problem and the busy signal on remote disconnect problem. If you're not familiar with he latter, it would cause you to get a busy signal when the party at the other end of a call hung up first. It was really irritating for people using home answering machines rather than voicemail. Someone would leave a message and hang up, then the answering machine would record a loud busy signal for awhile before disconnecting.

Posts: 2257

Steve48 wrote:

NateHoy wrote:

skinnydude wrote:

Unfortunately 1.00.52 fixed a few very important issues so Vonage WILL NOT roll you back to 1.00.50 so don't even ask.

Can you drop a few hints as to what those issues were?

Two that it fixed for me were the short ring problem and the busy signal on remote disconnect problem. If you're not familiar with he latter, it would cause you to get a busy signal when the party at the other end of a call hung up first. It was really irritating for people using home answering machines rather than voicemail. Someone would leave a message and hang up, then the answering machine would record a loud busy signal for awhile before disconnecting.

I get that all the time on conference calls, if the other end disconnects me. My phone shows as connected for about 15-20 seconds, then I get a loud busy signal. Figured that was just the way Vonage worked, and since I don't have an answering machine hooked up, never thought about it much. Smile

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

Vonage isn't _supposed_ to work that way. I gather that 52 didn't fix it for you. Does it only happen on conference calls?

Posts: 2257 · Posted: Wed Nov 09, 2005 8:43 pm Post subject:

Steve48 wrote:

Vonage isn't _supposed_ to work that way. I gather that 52 didn't fix it for you. Does it only happen on conference calls?

I dunno, I generally hang up when other calls end, but occasionally I'm desperately scribbling notes or typing stuff at the end of con calls, and don't notice that the phone hasn't hung up until it starts beeping.

Not a big deal for me, like the fact that I've never had call waiting work, or any of the dozen other features that don't work perfectly. If the voice quality stays as good as it is and my WRTP54G could be a useable router, I'd be happy for $25 a month. It's not perfect, but it's not expensive either. TANSTAAFL.

Posts: 423 · Vonage Forum Evangelist Joined: Oct 03, 2005 Posts: 423

Mr. Sorento,

I don't know where you got that but I got an email about 4 hours ago from call proc relating that same fix - drop a zero off the ring cadence1 has been shown to work in some cases, although with exceptions. I have yet to try this one yet.

Nate Hoy

You are a true forum spammer, and I salute you! LOL. Yeah the 'imaginary' problem bulletin board does have some eye openers, although they are not worded like that. I wish they would though, there is no kind of emotion or comment in the issues listed. There could be an issue something like:

"WRTP54G smokes and belches blue fire when 2 calls come in at once from overseas. We were able to duplicate the issue. Calling Frank and Raj and Bengali tomorrow to investigate. Opening a P3 with Linksys."

PS I made that up...(or did I)