Voice mail indicator & stutter dial tone no longer work on Obi202 unit using GV
CoalMinerRetired:
Quote from: rocketben on August 27, 2012, 08:15:56 pm
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:
Quote from: Mark.P on September 09, 2012, 12:08:09 pm
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:
Quote
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page