Voice mail indicator & stutter dial tone no longer work on Obi202 unit using GV

[Studly]

About 3 days ago, on both my GV accounts set up on the Obi202, we're no longer getting notifications when we have a new voice mail waiting. I get notified through e-mail from GV, but the Obi doesn't seem to be sending out the stutter dial tone or the voice mail indicator signal on two different GV lines.

Did the firmware change about three days ago? I haven't changed anything in the Obi control panel, and made no changes to the GV settings. Prior to 3 days ago, everything worked fine. I tried rebooting the Obi, but that didn't fix it.  

Any help is appreciated!!

[pc44]

Hi Studly,

The firmware did change a few days back.  Although it is not yet visible on the Firmware Notification thread and although it did not come down automatically for me, you can access it via ***6.

Not sure if that will help, but it's a thought.  You probably also want to double-check your MWIEnable, MWIEnable2, X_VMWIEnable, X_VMWIEnable2, and MessageWaiting settings under Voice Services -> SPx Service.

pc44

[Studly]

Thanks for the tips ... I just downloaded the latest firmware, and it still doesn't work. Anyone else with the 202 unit have this problem using GV?

[OBiSupport]

We are working on a solution for this issue.  In the meantime, there is no need to make any changes to your OBi or GV configurations.

[SilverHD]

Studly:  I am having the same exact problem and admin stopped answering my mail. This started about a week ago.  Now I have to use my computer to find out if anyone called.

pc44:  I wish I understood what this means:  (MWIEnable, MWIEnable2, X_VMWIEnable, X_VMWIEnable2, and MessageWaiting settings under Voice Services -> SPx Service.)

I am glad to hear that the admin are working on a solution to this problem.  I have another phone that I was going to add but now I am leary!

[jimates]

Studly:  I am having the same exact problem and admin stopped answering my mail. This started about a week ago.  Now I have to use my computer to find out if anyone called.

pc44:  I wish I understood what this means:  (MWIEnable, MWIEnable2, X_VMWIEnable, X_VMWIEnable2, and MessageWaiting settings under Voice Services -> SPx Service.)

I am glad to hear that the admin are working on a solution to this problem.  I have another phone that I was going to add but now I am leary!

On your device or from the expert configuration in the Portal.
Go to Voice Service -> SP(x) Service -> Calling Features
and check the settings for MWIEnable & X_VMWIEnable (MessageWaitingIndicatorEnable & VoiceMailWaitingIndicatiorEnable)

[rlev]

I'm also having this issue.  The Voice mail indicator was always fragile and needed to be reset about once every month.  In the last week it stop work altogether.  Can any one shed some light on this.  I'm using GV and an obi110.

Rich

[atraum]

We are working on a solution for this issue.  In the meantime, there is no need to make any changes to your OBi or GV configurations.

Thanks for the update.  Do you know how we will be notified of the fix or will it be pushed.
Thank You

[atraum]

Just to confirm, is this something I need to activate in order for the voicemail alert to work once the "fix" is released?
http://www.obihai.com/googlevoiceFAQ.html#11
GV Voicemail Notification & Missed Calls
When you enable Google Voice voicemail notification on your OBi, you should be sure to not check the "Place missed calls in the inbox" box. Otherwise, whenever there is a missed call, the phone attached to the OBi will signal (visual and stutter dial tone) an unheard voicemail. The Missed Calls setting can be found in the Google Voice Settings: Calls tab.

[SilverHD]

Hello again: Good news!  I emailed OBi last night, asking when this would be repaired.  They updated my "firmware" and it is working fine now.  I didn't do anything.  I guess it is like they said. We have nothing wrong. They have to fix it.  I'm glad they did!  Now I'm going to work on putting my other line in.

[OBiSupport]

There is a firmware release available that addresses the voice mail (visual and stutter dial tone) alert indication on OBi devices. 

To obtain the firmware update, dial ***6 from the phone attached to your OBi device or log-in to www.obitalk.com and from the Dashboard, select the yellow triangle adjacent to the OBi device(s) you would like to update.

- Thank you -

[GregoryZ]

There is a firmware release available that addresses the voice mail (visual and stutter dial tone) alert indication on OBi devices. 

To obtain the firmware update, dial ***6 from the phone attached to your OBi device or log-in to www.obitalk.com and from the Dashboard, select the yellow triangle adjacent to the OBi device(s) you would like to update.

- Thank you -

This needs to be posted in the Topic: "Firmware / Advisories / Notifications for  Obi Porducts"

I've been getting a notice on the OBiTALK Portal, of an Update for the past few days also.

My device is an OBi100.  Does this Update effect my device? 

When I choose to manually download it, I'm seeing that the Update is the same version I already have on my device.  Is there an Error on the Portal, and it should not be showing an update for the OBi100??

If all of the notices are posted where they can be found under the one Topic "Firmware / Advisories / Notifications for  Obi Porducts" it would better serve us all.  Of course the Change Log is just as important as the Notice itself.

Many Thanks from a Happy User!

[arobatino]

There is a firmware release available that addresses the voice mail (visual and stutter dial tone) alert indication on OBi devices. 

To obtain the firmware update, dial ***6 from the phone attached to your OBi device or log-in to www.obitalk.com and from the Dashboard, select the yellow triangle adjacent to the OBi device(s) you would like to update.

- Thank you -

As of August 27, the 2719 changes are still not posted at http://www.obitalk.com/forum/index.php?topic=9.0 , so the vast majority of users will not be able to find them.

[rocketben]

I'm having the opposite problem. As of a few days ago, I can't get the voicemail notification/stutter tone to go away. I set up a second google voice account and did the firmware update the same day, so I'm guessing one of those has something to do with the problem.

I have even unchecked "Google Voicemail Notification" in the configuration for both lines. Stutter tone still won't go away. I'm about to put some electrical tape over the blinking yellow lights on my phones.

[Rick]

There is a firmware release available that addresses the voice mail (visual and stutter dial tone) alert indication on OBi devices. 

To obtain the firmware update, dial ***6 from the phone attached to your OBi device or log-in to www.obitalk.com and from the Dashboard, select the yellow triangle adjacent to the OBi device(s) you would like to update.

- Thank you -

As of August 27, the 2719 changes are still not posted at http://www.obitalk.com/forum/index.php?topic=9.0 , so the vast majority of users will not be able to find them.

Amazing, isn't it?

[CoalMinerRetired]

I'm having the opposite problem. As of a few days ago, I can't get the voicemail notification/stutter tone to go away. I set up a second google voice account and did the firmware update the same day, so I'm guessing one of those has something to do with the problem.

I have even unchecked "Google Voicemail Notification" in the configuration for both lines. Stutter tone still won't go away. I'm about to put some electrical tape over the blinking yellow lights on my phones.

I'm having the same problem on an Obi202, and this is to ask if you got yours fixed?  Other than with the black electrical tape.

I updated using ***6, which moved me from 3184M to 3397. I have two GV lines and they are both doing this after the update. No unread VMMs, and in box is empty in both GV accounts.  Another curiosity, the MessageWaiting field for both these voice services, which is documented as "This is a state rather than a configuration parameter.." shows cleared, so this status field is working opposite of the signals on the physical ports.

[Mark.P]

Has anyone had direct contact/resolution with ObiSupport on the stutter dial-tone issue? My GV and Anveo accounts still have the stutter, after the firmware update,with the VM notification toggled-off.

[CoalMinerRetired]

Has anyone had direct contact/resolution with ObiSupport on the stutter dial-tone issue? My GV and Anveo accounts still have the stutter, after the firmware update,with the VM notification toggled-off.

Yes, I have. For pretty much the same case you describe. I updated firmware to the latest (in the hope of making MWI and VMWI work) and after the update reboot was getting stutter dialtone and VMWI on both phone ports, and couldn't get either either port to clear. They correctly diagnosed the issue as an unread VM in a third service provider. I cleared that, but also had to reboot twice to make the stutter DTs and VMWIs go away, explanation below.  For your possible fix, see here, note unread in Spam, Archive, Text, etc.

My take is there is still something flaky going on, they (ObiSupport) didn't completely understand the situation (seemed to dismiss that the stutter and VMWI didn't go away automatically , it took two reboots to make this go away on both ports), and in a follow up email they implied it was working correctly. I didn't pursue it because after 36 hours of stutter DT and VMWI on both ports I was happy to have it finally clear up.

The flaky part that I still think is a problem: If you have SP1 pointed to ph1, and SP2 pointed to ph2 the MWI/VMWI all seem to work as expected. However, if you have an SP3 pointed to ph1, and set MWI (but not VMWI, and not MWI2 and not VMWI2) on sp3, and you get an unread message on SP3, you will get various results: In particular, MWI and VMWI  both on on both ph and ph2 after a reboot. If you then clear the unread message, the MWI and VMWI on ph and ph2 will not go away, you have to reboot twice to clear them, one reboot clears ph, and a second reboot is needed to clear ph2.  It's the combination of having an unread message waiting and rebooting that is the root issue, form what I see. Getting and clearing an unread message on SP3 seems to correctly turn on only MWI on ph, from my experimenting. 

[CoalMinerRetired]

An update. There is clearly something still broken or flaky here.  

I did a test this AM, where I got a missed call into a GV inbox (was set this way on purpose to test) on SP1. Upon reboot the MWI and VMWI on both ph and ph2 were stuttering and flashing. The call came in on SP1 (which is pointed to ph only). Upon marking the VM read, the MWI and VMWI on ph cleared, almost immediately. However, the MWI and VMWI on ph2 did not clear (waited 5 or 10 minutes) had to do a reboot to clear 'em up. Note that MWI2 and VMWI2 on SP1 are unchecked. I'm suspicious that SP2, my third SP (pointed to ph only) is a factor. I subsequently cleared MWI from SP2, VMWI (and MWI2 and VMWI2) were not checked on SP2.

[rocketben]

I contacted obihai support, and they told me this:

Your SP2 has a pending voicemail to be cleared from the OBi point of view. Please enable the voicemail checking on SP2, and check your vmail by dialing **2+SP2-GVnumber. Once it is cleared, you can disable the voicemail checking, then it will no longer stutter.

It worked. However, about a week later, it came back. Which tells me something's not right. Also, the same procedure did not clear up the issue. I've been meaning to contact support again, just haven't gotten to it yet.