GV voicemail indicator

(1/3) > >>

CarlAron:
I've read several threads here and tried the recommended settings:
MWIEnable    (checked)
X_VMWIEnable (checked)
MessageWaiting (unchecked and default unchecked)

I have the latest firmware update (March 15th). I've deleted all spam, trash, and text messages in my GV account, so there are only VM in there, and yet, I still can't get VM indicator working to correctly show whether I have any unread VMs or not.

First a little background about how I'm using the Obi110, in case it's relevant.

I'm not using it to make outgoing calls at all.

I want to use GV primarily for it's filtering abilities... with GV, I can set it up so only people in my GV contacts list actually ring the GoogleChat (Obi110) line, and everyone else (telemarketers, fund raisers, etc) goes directly to voicemail.

But I'm not ready to port my main number to Google, and besides, I want outgoing calls (especially 911) to use the POTS line.

So I set up the Obi110 with a GV account on SP1, and then unchecked the box for "Make This the Primary Line to Call Out". Then on Verizon, I forwarded ALL incoming calls to my GV number.

Now, incoming calls go through Google, and Contacts come to my Obi and ring my phone, while others get GV voicemail. Outgoing calls use the POTS line and my friends and 911 will see my real Verizon caller ID.

If I don't answer, it goes to my GV voicemail box. So far so good.

However, I have two different, opposite problems with the VM indicator:

1) when a voicemail from a friend comes in, it lights up the VM indicator. I call the GV number and listen to the VM, and mark it to be "Archived" (there is no "delete" option in the dial-in VM tools on GV)... BUT the VM indicator never goes off.... I can log into the Obi and uncheck "MessageWaiting", and reboot, and it goes away, but I can't do that every time I get a voicemail! I'll never know for sure if the blinking light is really a voicemail, or just a "ghost of voicemails past".

2) when a voicemail is left by someone not in my contacts (someone who never rang my phone), the VM indicator never lights up, until another VM is left by someone on the contacts list. I can see the VM right there in GoogleVoice, but it doesn't turn on "MessageWaiting" on the Obi and my phone. I really want to see those voicemails... so that if it is a real caller, I can add them to my Contacts so they ring next time. Most telemarketing robocalls just hang up when they detect voicemail, so if a message is left, it's probably a real person who I don't have in my Contacts yet.

Anyway.... does anyone else have this combination of problems? Any Solutions?

pc44:
Hi,

I thought the Obi voicemail notification feature was strictly audio -- stutter tone.  I did not think it affected the phone's lights.  On one of my phones, the visual notification was only for new calls in the phone's caller id and not for the voicemail system.  Once I would go through the phone's caller id list, the visual notification would turn off.  Of course, each phone model may function a bit differently.

On the voicemail side of things, the audible stutter tone works for me.  But when I have archived a message, it does take some time before the Obi realizes that there are no longer any new voicemails.  This is usually not very long, but it is not instant.

Hope someone else can shed more light on this for you!  :)

P.S.  Thanks for providing a detailed and informative description of your problem and setup.  I wish more people did that when asking for forum help.

CarlAron:
Thanks... I'll look into what you say about the light and the caller ID list. If the light is linked to calls that rang the phone, but which I didn't pick up, rather than to voicemails, then it might well behave the way I described.

This is a Uniden phone, BTW.  Under "normal" use with Verizon, the light will flash when I've got a voicemail, even if the phone didn't ring (for example if the voicemail was left while I was on the line with another person), and will stop blinking after I've listened to and deleted the voicemail on Verizon... (although there is sometimes a delay in turning off the blinking).

I have an update, though. A message I left from a "non-contact" phone eventually showed up (the light on the phone started blinking)... after about 4 hours. I woke up in the middle of the night and saw the light, listened to the message, and "archived" it. The light was still blinking, but when I woke up this morning, the light was off. So in this circumstance, it behaved the way I thought it should, but with a LONG delay in changing the status of the light to match the status of VMs on GV.

CarlAron:
One more update... It seems that if I call my Google Number using the Obi SP1 line when I check Voicemail, it clears the VM indicator right away.

I still have a problem with new Voicemails not showing up on the indicator for 20 or 30 minutes, sometimes a few hours.

Is there a setting to tell the Obi to check in with Google more often to see if there is any new voicemail?

pc44:
Quote from: CarlAron on March 21, 2012, 04:42:18 pm

I still have a problem with new Voicemails not showing up on the indicator for 20 or 30 minutes, sometimes a few hours.

Does the stutter tone do the same thing?  Does it also not indicate until about 20 or 30 minutes?  I'm just trying to see if there is any difference between the audio/tone notification versus the indicator notification.

Also, I wonder if it makes any difference since you do not have this telephone set to receive calls from GV unless they are people on your contact list.  Do the same symptoms/problems occur with 'contact list callers' versus 'non-contact list callers'?

Quote from: CarlAron on March 21, 2012, 04:42:18 pm

Is there a setting to tell the Obi to check in with Google more often to see if there is any new voicemail?


I'm not really sure.  Unrelated--the only other thing that comes to mind is using a syslog setup, which would provide a bit more detailed information as to what is going on in the Obi... kind of a detailed log.

Just talking out loud here... so if anything I say sounds crazy... take it with a grain of salt and hope for input from some of the more qualified people here ;D

Navigation

[0] Message Index

[#] Next page