Voicemail indication on the OBi110 works with Google Voice. However, it takes an hour before it updates if you delete messages online though voice.google.com; further, many times the connection will fail. Also, if someone calls and leaves a message, the OBi110 will not grab the updated voicemail data until the next hourly polling interval.
I'm wondering if there is a setting somewhere I may have missed to adjust this interval?
Also, several times the voicemail check will fail as shown below:
Syslog shows this (note I replaced the authorization key with "I_DELETED_THIS_KEY"):
09:49:38 <7> GTALKVM:Checking VM....
09:49:38 <7> GTALKVM:state changed from 0 to 1
09:49:39 <7> TCP:Connect OK(lhttpc)17
09:49:39 <7> Trying to connect ssl
09:49:39 <7> TC:ssl connected
09:49:39 <7> LHC:Server name not matching:accounts.google.com/MigrateCookie?cont
inue=https%3A%2F%2Fwww.google.com%2Faccounts%2FManageAccount&service=grandcentra
l&uberauth=I_DELETED_THIS_KEY&source=lrp vs www.google.com
09:49:39 <7> LHC:Invalid location
09:49:39 <7> GGSVC:Invalid response
09:49:39 <7> GTALKVM:Google login failed!
09:49:39 <7> GTALKVM:state changed from 1 to 2
...
09:52:40 <7> GTALKVM:Checking VM....
09:52:40 <7> GTALKVM:state changed from 2 to 1
09:52:40 <7> TCP:Connect OK(lhttpc)18
09:52:40 <7> Trying to connect ssl
09:52:41 <7> TC:ssl connected
09:52:41 <7> LHC:set Retrying:www.google.com, 0
09:52:41 <7> LHC:retrying...www.google.com
09:52:41 <7> TCP:Connect OK(lhttpc)19
09:52:41 <7> Trying to connect ssl
09:52:42 <7> TC:ssl connected
09:52:42 <7> LHC:status code:302
09:52:42 <7> TCP:Connect OK(lhttpc)20
09:52:42 <7> Trying to connect ssl
09:52:43 <7> TC:ssl connected
09:52:43 <7> LHC:set Retrying:www.google.com, 0
09:52:43 <7> LHC:retrying...www.google.com
09:52:43 <7> TCP:Connect OK(lhttpc)21
09:52:43 <7> Trying to connect ssl
09:52:44 <7> TC:ssl connected
09:52:44 <7> LHC:set Retrying:www.google.com, 0
09:52:44 <7> LHC:retrying...www.google.com
09:52:44 <7> TCP:Connect OK(lhttpc)22
09:52:44 <7> Trying to connect ssl
09:52:45 <7> TC:ssl connected
09:52:45 <7> LHC:set Retrying:www.google.com, 0
09:52:45 <7> LHC:retrying...www.google.com
09:52:45 <7> TCP:Connect OK(lhttpc)23
09:52:45 <7> Trying to connect ssl
09:52:46 <7> TC:ssl connected
09:52:46 <7> LHC:Response OK
09:52:46 <7> GTALKVM:Check VM Succ
09:52:46 <7> GTALKVM:state changed from 1 to 0
09:52:46 <7> GTALKVM:u:1 vs v:0
09:52:46 <7> GTALKVM:VM:1
...
10:52:43 <7> GTALKVM:Checking VM....
10:52:43 <7> GTALKVM:state changed from 0 to 1
10:52:44 <7> TCP:Connect OK(lhttpc)26
10:52:44 <7> Trying to connect ssl
10:52:44 <7> TC:ssl connected
10:52:45 <7> LHC:Response OK
10:52:45 <7> TCP:Connect OK(lhttpc)27
10:52:45 <7> Trying to connect ssl
10:52:45 <7> TC:ssl connected
10:52:46 <7> LHC:Response OK
10:52:46 <7> GTALKVM:Check VM Succ
10:52:46 <7> GTALKVM:state changed from 1 to 0
10:52:46 <7> GTALKVM:u:1 vs v:0
10:52:46 <7> GTALKVM:VM:1
Quote from: etc6849 on December 18, 2011, 08:11:00 AM
Voicemail indication on the OBi110 works with Google Voice. However, it takes an hour before it updates if you delete messages online though voice.google.com; further, many times the connection will fail.
I'm wondering if there is a setting somewhere I may have missed to adjust this interval?
I find that deleting messages through the Google Voice voicemail interface causes the OBi to update VMW status within a minute or two on average. It may be a Google Voice issue that deleting them through the web interface doesn't update the voicemail interface for up to an hour.
Quote from: etc6849 on December 18, 2011, 08:11:00 AM
Also, several times the voicemail check will fail as shown below:
I reported this to Obihai via email on 11/1/2011 and received the following response:
Quote
This indicated that google voicemail checking failed. This won't cause any
harm to GV service; and device would automatically retry VM checking after a
while.
This started to happen recently. Although it didn't cause any harm, we are
also looking into it and see if this type of failure can be avoided.
I've received nothing further and the problem was not fixed in the latest firmware release.
Forgot to mention that if someone calls and leaves a message, the OBi110 will not grab the updated voicemail data then either until the next hourly polling interval.
Quote from: etc6849 on December 18, 2011, 12:58:18 PM
Forgot to mention that if someone calls and leaves a message, the OBi110 will not grab the updated voicemail data then either until the next hourly polling interval.
I don't see that here. VMW indication, either coming on for new voicemail or going off after reading all voicemail, happens within a couple of minutes on average for me.
It's taking around 45-60minutes for my Panasonics to stop blinking and saying New Voice Mail. If I reboot the Obi it's fast. I have 2 Google Voice accounts setup on it, and I tested the long voice mail alert clearing with both.
Was this something that is going to be fixed as right now it's almost more annoying than useful.
Thanks for verifying that :P. I can't get it working again for some reason, even with the hour+ delay. So maybe they will come out with a fix soon as it is quite handy.
Quote from: RonR on January 05, 2012, 09:26:59 PM
Ziflin,
I haven't checked the operation of Google Voice voicemail with the OBi in quite a while as I use a local answering machine which picks up just before Google Voice voicemail does. The last time I checked, it all worked pretty smoothly with little delay. In checking at the moment, it appears the OBi and Google Voice voicemail aren't getting along.
Something is broken between Google Voice voicemail and the OBi.
Glad I found this. Now, with my landline ported to Google Voice (via T-Mobile interim stop), I can't get the voicemail indicator working properly.
If I check "Message Waiting", the indicator is on all the time. If I clear it on the phone, it comes back. If I uncheck it, I get no indicator or stutter tone.
Here are my settings:
Voice Services -> SP1 service -> MWIEnable : (checked)
Voice Services -> SP1 service -> X_VMWIEnable : (checked)
Voice Services -> SP1 service -> MessageWaiting : (unchecked) (Default unchecked)
I made sure there were no unread messages in the Trash before I tried to diagnose it.
All voicemail checking between Google Voice and OBi devices has been failing 100% of the time for many days now.
I suspect this will continue to be the case until there is a firmware update for the OBi.
Does anyone here know a viable alternative to the google voicemail in this case?
Quote from: Paulo on January 12, 2012, 04:41:45 AM
Does anyone here know a viable alternative to the google voicemail in this case?
The ONLY issue here is that GV is not triggering the Voicemail indicator on the OBi, and hence your telephones. If you do indeed get a voicemail message, GV still would notify you via email and/or text message if you have selected those options in GV. I get both, usually within a minute or so, including GV's attempt at transcribing the message.
Maybe this fw upgrade will help.
Jan 10, 2012
Enhancements & Fixes in Maintenance Release 1.3.0(2669):
- Fixed Message Waiting indicator
- Polarity Reversal not enabled by default
Quote from: lhm. on January 13, 2012, 04:36:58 AM
Maybe this fw upgrade will help.
Jan 10, 2012
Enhancements & Fixes in Maintenance Release 1.3.0(2669):
- Fixed Message Waiting indicator
- Polarity Reversal not enabled by default
I just applied the upgrade, went in after and checked MWIEnable and X_VMWIEnable and rebooted the Obi. I then left myself a message. As of 5 minutes later, no indicator is showing. I will post if one shows up.
UPDATE - no indicator has appeared.
Quote from: Rick on January 13, 2012, 04:54:23 AM
Quote from: lhm. on January 13, 2012, 04:36:58 AM
Maybe this fw upgrade will help.
Jan 10, 2012
Enhancements & Fixes in Maintenance Release 1.3.0(2669):
- Fixed Message Waiting indicator
- Polarity Reversal not enabled by default
I just applied the upgrade, went in after and checked MWIEnable and X_VMWIEnable and rebooted the Obi. I then left myself a message. As of 5 minutes later, no indicator is showing. I will post if one shows up.
OBi VM checking is still taking numerous retries before succeeding. Often, there are long timeouts, sometimes up to an hour, after a failure before another retry is attempted.
Quote from: RonR on January 13, 2012, 05:50:18 AM
OBi VM checking is still taking numerous retries before succeeding. Often, there are long timeouts, sometimes up to an hour, after a failure before another retry is attempted.
In other words, the update didn't fix the problem...
It's of concern to me that OBi is not as responsive to their customers as I would have hoped when I bought the device. They issued a firmware update last week, it did NOT resolve the problem, and they haven't communicated on these forums regarding that issue that I can see.
Given the straightforwardness of the problem - i.e. GV voicemail doesn't turn on the voicemail indicator, I was surprised that their firmware update did not fix the problem. You change the firmware, you test the fix, and it works or it does not. When it does not, you don't release it saying that it does.
If it did fix it in your tests, wouldn't it make sense to release it to users that have said they have the issue for further testing? In this case, wouldn't that have shown that it wasn't fixed?
Then, when you do release it and it doesn't fix the problem, how can you not communicate with your customer base?
While the problem isn't insurmountable, since GV sends me emails / texts when I get a message, this is a basic feature that should work. Who knows, it could be that GV changed their system and messed up OBi. Doesn't matter to me, what does matter is that I don't see OBi communicating. That is a huge problem. I'm going to ask Sherman, in a private message, to read this and respond.
New here. Got Obi110 of Amazon, hooked up to my GV and Ooma. Worked great for calling so far but the voicemail indicator does not work :( which is the main reason i bought this box... so i will wait a week so before i decide what to do with the unit.
Just wanted to subscribe to get updates...
I am seeing this problem too: google voice mail notification does not work with the current firmware: 1.3.0 (Build: 2669) . I don't know if this helps, or if any obihai representatives are reading, but I have my obi110 sending its syslog to a remote syslog server and see this in the logs when a googletalk voice mail check is attempted:
Jan 20 08:57:42 obi110 GTALKVM:Checking VM....
Jan 20 08:57:42 obi110 GTALKVM:state changed from 2 to 1
Jan 20 08:57:43 obi110 TCP:Connect OK(lhttpc)53
Jan 20 08:57:43 obi110 Trying to connect ssl
Jan 20 08:57:44 obi110 TC:ssl connected
Jan 20 08:57:45 obi110 LHC:Server name not matching:accounts.google.com/MigrateCookie?continue=https%3A%2F%2Fwww.google.com%2Faccounts%2FManageAccount&service=grandcentral&uberauth=XXXX%2C&source=lrp vs www.google.com
Jan 20 08:57:45 obi110 LHC:Invalid location
Jan 20 08:57:45 obi110 GGSVC:Invalid response
Jan 20 08:57:45 obi110 GTALKVM:Google login failed!
Still doesn't work for me either :(
I've learned that OBi is currently testing a new firmware release that may solve this problem.
Great news! If you have a contact at OBi, could you please direct them to this thread:
http://www.obitalk.com/forum/index.php?topic=2368.0
From the other firmware issue I'm having:
I use a perl script to parse the syslog data and this script logs my calls. Outbound GV call information is missing in the latest firmware build 2669.
Are there any plans to add it back? Some of us use the call data with home automation systems and other programs.
Previously (in builds 2651 and prior) I'd see something like this for an outbound call following the button presses (with SYSLOG set to level 7):
[<7> FXS:New Call:1316****657]
[<7> FXS:New State:incall]
[<7> FXS: State=incall, flags=1]
[<7> FXS:Stop Ring]
OBi pushed new firmware to me that resolved the VM problem. I suspect it will roll out soon.
Quote from: Rick on January 25, 2012, 05:04:54 PM
OBi pushed new firmware to me that resolved the VM problem. I suspect it will roll out soon.
Thanks. Looking forward to getting the new firmware.
Got the latest firmware update and set my settings as directed in many forum posts, and this still isn't quite right.
I found that the VM indicator turn OFF more dependably if I check the VM using the dial-in interface, and if I call to do that using the SP1 line which is aassociated with that Google Voice account.
However, I STILL have the problem of new voicemails not turning the indicator ON for a LONG time after the message is left. This problem seems worst if the message was left without ringing the Obi (for example if the caller is set up in Google Contacts as someone to go straight to voicemail.)