Google Voice Voicemail Notification feature behaving unreliably
VulcanTourist:
This is a continuation or tangent from the thread "stutter" dial tone for Google Voice message indication (http://www.obitalk.com/forum/index.php?topic=466.0). Based on advice given in that thread, I had cleared the MessageWaiting field in the Obi110's Web interface, attempting to clear a stubborn "New Voice Mail" notice on my phones that had persisted for many weeks. I also tried some other things. One of those changes made the indicators stop, but apparently it did more than just that: Now I have new voicemail sitting in Google Voice since yesterday afternoon, and the phones display no indicators of the new message, though a missed-call notice for the same call did appear on the phone. I understand now that there can be quite a delay up to an hour (which is NOT helpful, BTW), but 24 hours?
Q: Does clearing the MessageWaiting field in any way disable the Obi110's ability to trigger new-message indicators on the phone? Should the Default field be enabled?
Both of the MWIEnable and X_MWIEnable fields are still checked. I tried disabling them from the device Web page, intending to immediately enable them again, but it rejected the changes. However, when I un-checked the Google Voice Voicemail Notification field at the ObiTalk Web site, that cleared both of those fields. I re-enabled them the same way.
Q: How do I now get the phones to correctly begin displaying new-voicemail indicators again, that appear shortly when there is new voicemail and disappear shortly after removing the voicemail? The simple intuitive answer involving Google Voice Voicemail Notification doesn't seem to be the correct or at least complete one.
Q: Does using the ObiTalk Web site prevent changing anything via the Obi110 Web interface? If so, why did clearing the MessageWaiting field succeed in the first place?
Q: Are there only certain fields that are unchangeable when using ObiTalk? If so, how do I know which ones those are? Do I have to completely discontinue the convenience and easier intelligibility of the ObiTalk site in order to make everything alterable from the device Web interface? (Well, "easier intelligibility" aside from the fact that certain things don't guarantee the behavior they allege to control.)
RonR:
Quote from: VulcanTourist on September 04, 2011, 01:55:28 pm
Q: Does clearing the MessageWaiting field in any way disable the Obi110's ability to trigger new-message indicators on the phone? Should the Default field be enabled?
Both of the MWIEnable and X_MWIEnable fields are still checked. I tried disabling them from the device Web page, intending to immediately enable them again, but it rejected the changes. However, when I un-checked the Google Voice Voicemail Notification field at the ObiTalk Web site, that cleared both of those fields. I re-enabled them the same way.
There are three settings:
MWIEnable : Plays the stutter dial tone on the PHONE Port when there are new messages. It will also turn on the VMWI signal on the PHONE Port if X_VMWIEnable is checked.
X_VMWIEnable : Enables Visual Message Waiting Indication on the phone.
MessageWaiting : This is a state rather than a configuration parameter that indicates if there are any new messages. Clearing it and rebooting sometimes clears a hung state in the OBi. Default must be unchecked for this status/setting to be meaningful.
Quote from: VulcanTourist on September 04, 2011, 01:55:28 pm
Q: How do I now get the phones to correctly begin displaying new-voicemail indicators again, that appear shortly when there is new voicemail and disappear shortly after removing the voicemail? The simple intuitive answer involving Google Voice Voicemail Notification doesn't seem to be the correct or at least complete one.
It should be a simple matter of checking MWIEnable and X_VMWIEnable.
Quote from: VulcanTourist on September 04, 2011, 01:55:28 pm
Q: Does using the ObiTalk Web site prevent changing anything via the Obi110 Web interface? If so, why did clearing the MessageWaiting field succeed in the first place?
Quote from: VulcanTourist on September 04, 2011, 01:55:28 pm
Q: Are there only certain fields that are unchangeable when using ObiTalk? If so, how do I know which ones those are? Do I have to completely discontinue the convenience and easier intelligibility of the ObiTalk site in order to make everything alterable from the device Web interface? (Well, "easier intelligibility" aside from the fact that certain things don't guarantee the behavior they allege to control.)
There are settings and status in the OBi that are not accessible from the OBiTALK Web Portal.
In my opinion, the OBiTALK Web Portal is much more confusing to use and requires a lot more effort than simply configuring the OBi directly. If all you need is a simple configuration of Google Voice and you don't intend to do any more than that and don't have any problems, then the OBiTALK Web Portal is adequate. If you intend to go any further with the OBi or need to troubleshoot a problem, then it's much much simpler and faster to deal with the OBi directly. No functionality is lost if you don't use the OBiTALK Web Portal.
The rules are simple - you have to use one method or the other consistently. If you want to use the OBiTALK Web Portal, then leave Auto Provisioning in the OBi enabled and don't make any changes to the OBi directly, as they will be overwritten by the OBiTALK Web Portal shortly thereafter. If you want to configure the OBi directly, disable Auto Provisioning in the OBi and don't attempt to make any changes through the OBiTALK Web Portal as they won't be effective.
rpankoe:
I'm also having this issue. If I receive a message on Google Voice, it doesn't enable the MessageWaiting state. I never get notified with the message waiting light, or stutter tone on phones connected to the PHONE port. If I manually enable MessageWaiting state on SP1, I verified that it does work. Now how can i get it to work for my GoogleVoice account associated with SP1?
RonR:
And if you log into your OBi directly using the IP address returned by dialing ***1, the following are checked?:
Voice Services -> SP1 Service -> MWIEnable
Voice Services -> SP1 Service -> X_VMWIEnable
and Default is unchecked on?:
Voice Services -> SP1 Service -> MessageWaiting
rpankoe:
Correct. I have them all checked except MessageWaiting (which is unchecked and "default" not set)
If I manually check MessageWaiting, then it acts as if there's a message. When I uncheck, it goes away, so that part is working. I just can't get it to work when a message is left on GoogleVoice.
Navigation
[0] Message Index
[#] Next page