Firmware 1.2.0, GV and MWI

(1/4) > >>

JohnLennon:
I upgraded to the new firmware 1.2.0, enabled MWI on the portal page. I have no messages waiting (both GV web site and calling confirmed) yet the MWI blinks on my phone. If I reset the phone it comes back. What could be wrong?

Note that the MWI on this phone never failed with my Linksys ATA, correctly reporting if there were messages on either of my 2 lines (as this phone supports 2 lines).

EDIT: I even disabled the (optional) MWI for GV but it seems to be stuck and keeps coming back.

JohnLennon:
RonR,
I manage everything via the online Portal. Yes, provisioning is enabled.

In Device Configuration I select the Obi110 gear, then check:
Google Voice Voicemail Notification  [Enable Google Voice voicemail notification on your phone. (Optional)]

I enabled it, the phone reported there was a message even if none were there. It's still reporting it now after I disabled / enabled / disabled this setting - and each time the device reboots as it receives the new configuration settings.

Agate:
I'm seeing the same thing.
Stutter dialtone and MWI are stuck on even after listening to all new messages or even completely clearing the GV inbox.


I have these three settings enabled under Voice Services--> SP1 Service -->  Calling Features
MWIEnable         
X_VMWIEnable         
MessageWaiting

Provisioning is disabled for my box.

jimates:
"MessageWaiting" isn't a setting, it is a display of state.

If you do have a message waiting it will be indicated by the check next to "MessageWaiting". If not, the check will not be there. So checking that box will force the MWI momentarily, even if no message is available.

QBZappy:
jimates,


re:  "MessageWaiting"
What purpose does the selectable check box serve? Any idea?

Navigation

[0] Message Index

[#] Next page