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.)
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.
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?
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
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.
Also, verify that these are checked:
Physical Interfaces -> PHONE Port -> MWIEnable
Physical Interfaces -> PHONE Port -> VMWIEnable
Quote from: RonR on September 07, 2011, 12:00:18 PM
Also, verify that these are checked:
Physical Interfaces -> PHONE Port -> MWIEnable
Physical Interfaces -> PHONE Port -> VMWIEnable
Yes, they are all checked also.
I just verified that's it's all working correctly in f/w version 1.3.0 (Build: 2532). The indicator on my phone (Vtech DS6321) came on within 60 seconds of leaving a mesage and it went off within 60 seconds of calling my Google Voice number and marking the message read.
I just updated to that version, but so far no luck. Anything else to try? How does GV tell the Obi that there is a new message waiting?
I don't know if it's through the XMPP connection the OBi establishes with Google Voice or through some other mechanism.
I assume you're successfully connected to Google Voice on SP1 and can make and receive calls without any problems?
Quote from: RonR on September 07, 2011, 12:22:41 PM
I don't know if it's through the XMPP connection the OBi establishes with Google Voice or through some other mechanism.
I assume you're successfully connected to Google Voice on SP1 and can make and receive calls without any problems?
Correct. No other issues. Just not being notified of the voicemails in any way. I did enable Voicemail Notification Forwarding in my GV account so that it would forward a copy of the voicemail to my YouMail account so that I would at least get that notification on my cell-phone... but the MWI on the PHONE port is still not working to advise me there.
I have email notification enabled also and it doesn't interfere with message waiting on the OBi/phone.
You may have to ask Obihai support for help as it appears you have everything configured correctly.
If you determine the cause, please let us know so others might benefit.
Quote from: RonR on September 07, 2011, 12:28:35 PM
I have email notification enabled also and it doesn't interfere with message waiting on the OBi/phone.
You may have to ask Obihai support for help as it appears you have everything configured correctly.
If you determine the cause, please let us know so others might benefit.
I'm not sure if this is the reason or not, but found this browsing the FAQs... Notice the end bold section.
If you have enabled Google 2-step verification for Gmail, please follow these instructions so that you will be able to use your OBi and Google Voice.
• Log in to your Google Account Management Settings page.
• Select the, 'Authorizing applications & sites' link.
• Create an application specific password for Google Voice.
• Use this password when you configure Google Voice as a service on your OBi device.
Please note: The Google Voice voicemail notification does not work for users who have 2-Step verification. With that, it is recommended you disable Google Voice voicemail notification on the OBi device via the OBiTALK device configuration settings for that particular OBi device.
Do you use 2-step verification? I don't have any experience with it myself. Is it something you can switch on and off?
Quote from: RonR on September 07, 2011, 06:02:14 PM
Do you use 2-step verification? I don't have any experience with it myself. Is it something you can switch on and off?
Yes, i do use it. You can turn it on/off for your whole google account. It is nice to have enabled because it only allows you to login from certain computers that you've given access. If you get to a new computer, you can have an app on your phone that you run that provides you a code so that you can login and add that computer to your trusted devices. That way someone can't hijack your account from somewhere else, even if they HAVE your password. It looks like that needs to be turned off on the google accounts to work though. I'm not sure why that is that the voicemail notification doesn't work with that. I'd think that you could assign it to be trusted. I'd be interested in finding out from Obi why that's not an option, or if they're working on it. (or ways around it)
I turned off 2-factor authentication, turned off the forwarding to the Obi (since my kids are asleep) and then called and left a message. While leaving it, I re-enabled forwarding to GoogleChat in GV so it went back to the Obi110, but it's still not working. Tomorrow when my kids are in school, I'll give it a try again with the whole system active and see what happens.
I'm now having the opposite of my original problem, and apparently the same as rpankoe: the Obi110 now no longer triggers the phones to indicate that new voice mail has arrived. Is there new firmware that fixes this? How can I be having both problems with the exact same settings?
Quote from: rpankoe on September 07, 2011, 06:07:29 PM
I'm not sure why that is that the voicemail notification doesn't work with that. I'd think that you could assign it to be trusted. I'd be interested in finding out from Obi why that's not an option, or if they're working on it. (or ways around it)
I'm also interested to hear from OBi about 2-step verification with Google. I currently do not use it because, as you said, VM notification wouldn't work. Thankfully, I don't seem to be having the problem you are having. In general, VM notification IS working for me; However, it does sometimes seem delayed / sporadic. I'm assuming that is due to Google Voice being slow in forwarding the notification but, who knows.
I contacted Obihai support directly about this and another issue, and they have made no attempt to respond in the week and a half since. YMMV, but I'm still sitting in the driveway.
I have heard of special app-specific passwords for instances when you wouldn't normally be wanting to (or able to) enter a 2-step verification code, like in smartphone apps. Maybe you'd have to do something like that with the obi...
Quote from: Randrage on September 20, 2011, 11:54:22 PM
Quote from: rpankoe on September 07, 2011, 06:07:29 PM
I'm not sure why that is that the voicemail notification doesn't work with that. I'd think that you could assign it to be trusted. I'd be interested in finding out from Obi why that's not an option, or if they're working on it. (or ways around it)
I'm also interested to hear from OBi about 2-step verification with Google. I currently do not use it because, as you said, VM notification wouldn't work. Thankfully, I don't seem to be having the problem you are having. In general, VM notification IS working for me; However, it does sometimes seem delayed / sporadic. I'm assuming that is due to Google Voice being slow in forwarding the notification but, who knows.
Did anyone ever get this working. Earlier I had it where after some amount of time it would show on my Panasonic phone that I had new voice mail. Only it would *never* turn off. I followed some of the steps here and now after leaving a new voice mail, it wont turn on.. LOL!
This feature was one reason that I just bought the OBI, so it'd be great to know how to get it to work.
I have the same problem: voicemail appears in Google Voice, email notification is sent,
but Obi110 (1.3.0 (Build: 2651)) never shows MessageWaiting checked. This did work until
a month ago or thereabouts. I can tolerate it, but my wife can not.
OBi voicemail checking is failing 100% of the time.
Obihai has been advised of the problem, but the only response so far is:
Thanks for the report. We will look into it ASAP.
-Obihai Support Team.
Hi Just checking.... I just bought OBI110 and have SP1 and SP2 connected to google voice.
My home phone is panasonic Dect 6.0 http://service.us.panasonic.com/OPERMANPDF/KXTG6431-MUL.PDF
- I have tried to manually turn on the indicator by unchecking default and then checking the box next to Voice Services>SP1 Service>MessageWaiting and the panasonic phone starts flashing.
- Note that i i did not have to disable Auto Provisioning. I thought i would have to as i made changes directly on the device and someone mentioned that the Web portal will overwrite these changes... maybe did not wait long enough or this part of the config on the device does not require disabling auto prov.
- Also, i noticed the device came from the manufacturer with the Default checked for the above MessageWiating switch (which is not in-line with the advice given in this thread. Does it matter if it is checked to default as shipped or unchecked?)
- Also, note from the panasonic manual: "You need to store the voice mail access number to activate the message alert feature for voice mail service. " Does this mean, if i ever get this feature to work automatically as it is supposed to, then it will only notify me on SP1 or SP2 but not both cause i can only store one VM # in the Panasonic phone? I think not but just making sure.
Quote from: GeorgeObi on January 16, 2012, 08:19:48 PM
I have tried to manually checking the box next to Voice Services>SP1 Service>MessageWaiting
and the panasonic phone starts flashing.
This proves the OBi is capable of turning your phone's Visual Message Windows Indication on and off.
Quote from: GeorgeObi on January 16, 2012, 08:19:48 PM
Also, note from the panasonic manual: "You need to store the voice mail access number to activate the message alert feature for voice mail service. " Does this mean, if i ever get this feature to work automatically as it is supposed to, then it will only notify me on SP1 or SP2 but not both cause i can only store one VM # in the Panasonic phone? I think not but just making sure.
I don't believe you need to store a number in the Panasonic phone in order to work with the OBi. Just enable MWIEnable & X_VMWIEnable on both SP1 and SP2.
Quote from: RonR on January 16, 2012, 08:47:55 PM
Quote from: GeorgeObi on January 16, 2012, 08:19:48 PM
I have tried to manually checking the box next to Voice Services>SP1 Service>MessageWaiting
and the panasonic phone starts flashing.
This proves the OBi is capable of turning your phone's Visual Message Windows Indication on and off.
Quote from: GeorgeObi on January 16, 2012, 08:19:48 PM
Also, note from the panasonic manual: "You need to store the voice mail access number to activate the message alert feature for voice mail service. " Does this mean, if i ever get this feature to work automatically as it is supposed to, then it will only notify me on SP1 or SP2 but not both cause i can only store one VM # in the Panasonic phone? I think not but just making sure.
I don't believe you need to store a number in the Panasonic phone in order to work with the OBi. Just enable MWIEnable & X_VMWIEnable on both SP1 and SP2.
Thank you.
Note that it has been more than one hour and the voicemail indicator is still not working. I assume it is the same for everyone or is this issue just affecting some users?
Quote from: GeorgeObi on January 16, 2012, 10:04:59 PM
Note that it has been more than one hour and the voicemail indicator is still not working. I assume it is the same for everyone or is this issue just affecting some users?
AFAIK, it's affecting everyone.
[Jan 17 00:12:44]<7> GTALKVM:Checking VM....
[Jan 17 00:12:44]<7> GTALKVM:state changed from 0 to 1
[Jan 17 00:12:44]<7> TCP:Connect OK(lhttpc)40
[Jan 17 00:12:44]<7> Trying to connect ssl
[Jan 17 00:12:45]<7> TC:ssl connected
[Jan 17 00:12:45]<7> LHC:Response OK
[Jan 17 00:12:45]<7> LHC:set Retrying:www.google.com, 1
[Jan 17 00:12:46]<7> LHC:retrying...www.google.com
[Jan 17 00:12:46]<7> TCP:Connect OK(lhttpc)41
[Jan 17 00:12:46]<7> Trying to connect ssl
[Jan 17 00:12:47]<7> TC:ssl connected
[Jan 17 00:12:47]<7> LHC:Server name not matching:accounts.google.com/MigrateCookie?continue=https%3A%2F%2Fwww.google.com%2Faccounts%2FManageAccount&service=grandcentral&uberauth=APh-3FyGFZrMIqoShFb5Ig321UXnHcT-GkuyxY5Z5rZ1RFspDy2kScOyscismmveeols5UV3Khy4Yc5neRWO1z2e2YkBEAc8VfpRyrvXiJH8O8s5froXBSOp6uZnPju2gsHvTZrWnb3Qljtqm2rhm1iDiaY2I_mamLSJEE4ZDvUFWymbrbiGvtLuF-Y1rmBubfcWZHaF-JURowDkWYDTmCg8tmvDrlW5oRZ1VJTHUMcZw8s1mef73KmOQ9Qob-e9__voGOsdktU-YBxuYIix4XcwxnSuqzKhDDG4L_penrKoKzFy6nWUV2ux-KQgUvW7Ie7_psRhxjoQSSsRheipXYrhtS0Hm4Fcjg1_fYmBcrgg6dmUeKsGEGplX5ZA1Fh593u6erCrQE3viqtyxihNCTfVAyPxTmDGnazf997sSTtXkoNMopvM9S9pf7KyWtYOQYQ5mjOVcoqtMd85kdlm98zFJCizYPZt80PNfp8jM-5bZjPq6IMeDJAXvo9i-MmgZPxLJ2PMM6Z3gZSnINB4BQ__7FnLRfSfmU1i6abGZUJ8pagiNd4tae4%2C&source=lrp vs www.google.com
[Jan 17 00:12:47]<7> LHC:Invalid location
[Jan 17 00:12:47]<7> GGSVC:Invalid response
[Jan 17 00:12:47]<7> GTALKVM:Google login failed!
[Jan 17 00:12:47]<7> GTALKVM:state changed from 1 to 2
Thank you. I sure hope they fix it soon by working something out with the google team.
Well looks like the GV voice-mail indicator worked for me. Even went off after I checked it.
Quote from: Ostracus on January 18, 2012, 02:39:42 PM
Well looks like the GV voice-mail indicator worked for me. Even went off after I checked it.
Thanks. what are the settings for the variables discussed above? Specifically, is the message waiting indicator checcked to default?
Quote from: GeorgeObi on January 18, 2012, 03:06:08 PM
what are the settings for the variables discussed above? Specifically, is the message waiting indicator checcked to default?
Voice Services -> SPx Service -> MessageWaiting is technically not a setting. It's a status indicator of whether there are currently any messages waiting, although you can force it on or off with the value checkbox followed by a reboot.
If you have Voice Services -> SPx Service -> MWIEnable checked, the OBi should uncheck the MessageWaiting Default checkbox after the next reboot so that it can display the current status.
Quote from: RonR on January 18, 2012, 04:37:09 PM
Quote from: GeorgeObi on January 18, 2012, 03:06:08 PM
what are the settings for the variables discussed above? Specifically, is the message waiting indicator checcked to default?
Voice Services -> SPx Service -> MessageWaiting is technically not a setting. It's a status indicator of whether there are currently any messages waiting, although you can force it on or off with the value checkbox followed by a reboot.
If you have Voice Services -> SPx Service -> MWIEnable checked, the OBi should uncheck the MessageWaiting Default checkbox after the next reboot so that it can display the current status.
RonR - Thank you. For some reason the MessageWaiting indicator was checked for default. I am assuming it is like this from the factory and since GV voicemail handshake is not working since i got the OBI, it was never overwritten. I manually uncheck the default and left myself a VM. Still nothing which i suppose is expected until they fix the issue. I am not sure how user Ostracus is reporting that the indicator is working for him... I thought the issue is affecting everyone.
Quote from: GeorgeObi on January 18, 2012, 11:00:18 PM
For some reason the MessageWaiting indicator was checked for default. I am assuming it is like this from the factory and since GV voicemail handshake is not working since i got the OBI, it was never overwritten. I manually uncheck the default and left myself a VM. Still nothing which i suppose is expected until they fix the issue. I am not sure how user Ostracus is reporting that the indicator is working for him... I thought the issue is affecting everyone.
It's working for me intermittently/erratically. The OBi is talking many retries to make a successful VM check and sometimes waits more than an hour to try again after a failure.
You should have:
Voice Services -> SPx Service -> MWIEnable : (checked)
Voice Services -> SPx Service -> X_VMWIEnable : (checked)
Voice Services -> SPx Service -> MessageWaiting : (unchecked + Default unchecked)
If the OBi determines there are unread messages, it should check MessageWaiting and signal the phone to set its indicator. When there are no unread messages, it should uncheck MessageWaiting and signal the phone to clear its indicator.
Quote from: RonR on January 18, 2012, 11:15:54 PM
Quote from: GeorgeObi on January 18, 2012, 11:00:18 PM
For some reason the MessageWaiting indicator was checked for default. I am assuming it is like this from the factory and since GV voicemail handshake is not working since i got the OBI, it was never overwritten. I manually uncheck the default and left myself a VM. Still nothing which i suppose is expected until they fix the issue. I am not sure how user Ostracus is reporting that the indicator is working for him... I thought the issue is affecting everyone.
It's working for me intermittently/erratically. The OBi is talking many retries to make a successful VM check and sometimes waits more than an hour to try again after a failure.
You should have:
Voice Services -> SPx Service -> MWIEnable : (checked)
Voice Services -> SPx Service -> X_VMWIEnable : (checked)
Voice Services -> SPx Service -> MessageWaiting : (unchecked + Default unchecked)
If the OBi determines there are unread messages, it should check MessageWaiting and signal the phone to set its indicator. When there are no unread messages, it should uncheck MessageWaiting and signal the phone to clear its indicator.
Now, i have the exact settings as you described. It has been 2+ hrs and my panasonic does not show the VM indicator. so no signs of life here :(
Well tried the same thing last night and it worked. Maybe people are GeoIPed to different servers, some having the issue, some not?
2012-01-20 12:16:37 Kernel.Debug 192.168.1.136 GTALKVM:Check VM Succ
There's more but the forum will not allow me to post the entire log.
Mine was not working for the past month on the phone with both options (MWI enable & VMWI enabled checked). I have panasonic phones. I tried a lot of things recommended on this thread and nothing worked
I noticed a firmware update had been posted to OBItalk yesterday and after updating the firmware the voicemail notification now works
Andy
As asd108b stated above, mine now works as well.