I set up google voice with my Obi 100 a couple days ago. Everything worked great for two days. Now everything works but the message waiting indicator. It does not come on even when I have messages. Any tips. The only thing that has changed is that I ported my landline over to google voice and that completed this morning. It was the same time that I noticed that the message waiting indicator was not working. I did try resetting the obi and deleting it from my obitalk account and then setting things up from scratch. Same results.
This worked for two days, so I know it can work. By the way I am not getting the light or the tone.
First thought, wait a day or so for things to settle in with the # port.
Thanks. I guess I am just excited about my new toy and have obsessed about it. Hopefully that works.
Well, it is still not working. Anyone have any tips?
When you setup google voice you have two options under calls for what to do with missed calls. You must have the one labeled "Place missed calls in the inbox" checked.
You also need to have an 'unread' voice mail in your 'inbox' to trigger the message waiting indicator.
I thought I had read that I needed place missed calls in the inbox unchecked. It is not checked, but it has never been checked and the message waiting indicator worked before.
I do have an unread message in the inbox.
I checked the place missed calls in the inbox box and it did not make a difference. Still not getting the message waiting indicator.
I'm testing right now. You don't need "Place missed calls in the inbox" checked. I was looking at my personal google voice config that isn't connected to an obi and apparently the default then was checked. The default on my obi connected GV account is unchecked, and i do get notifications.
Though I believe i only get notifications if a vm is left after the phone rings. I'm testing that.
o.k. There may be an issue.
Historically the VM indicator has been working on my home phone connected to the obi. I performed a test today and found it does not seem to be working anymore. I called my home number and let it ring through and left a VM.
After 15 minutes no indicator. I rebooted the obi. After another 20 minutes, no indicator. I'll see if it ever comes on.
Fixed. I put in a support request and Obi fixed it with a firmware update. Great service. Thanks Obi.
Quote from: Reelmower on January 22, 2013, 12:14:09 PM
Fixed. I put in a support request and Obi fixed it with a firmware update. Great service. Thanks Obi.
Custom one or one already available?
I have a 202 with the same issue, noticed the problem after a firmware upgrade.
New fimware fixed it! Woot! Glad they got it out quick.
For future reference on this topic, there's a field under each SPx service in an Obi -- SPx > Calling Features > MessageWaiting -- that is 'read only' (meaning you can not change it, the Obi logic changes it) and it will tell you what the Obi thinks is the correct Message Waiting state.
This is independent of the analog phone handset you are using. So if it's on and no indicator on your phone, suspect the phone or settings. If it's off and there are unread messages in GV (or any other provider) something is suspect in the Obi getting interface to the service provider.
I was going to ask someone to elaborate on what new version of the firmware you are talking about, but I now see "3.0.0(3722) for OBi202/OBi302" listed under as updated today, Jan 24.
The OP has an Obi100. What is that firmware version? Edit:2774
Is there a solution to getting this working again now that google voice is officially supported? The option to select it has disappeared since the latest firmware upgrade.
On the OBiTalk portal, go under expert configuration, voice service and select the SPn that is google voice. Uncheck OBiTalk and default settings check box on the right for MWIEnable and X_VMWIEnable. Check the boxes for these features under the values column and click submit. This works on the 1032s. Do NOT check the box for MessageWaiting or it will turn the messaging waiting indicator light on all the time.
I tried that, even enabled anonymousecallblockenable as mentioned in another thread. Placed a call and let it go to voicemail. No indicator is showing up. I will leave those options enabled anyway, perhaps it will start working again later.
I called one of my GV numbers from my cell phone and left a voice mail and my MW light on my 1032s did NOT come on. I was wrong. The stutter dial tone is not working either. I think when this was working for me I had the box checked that made the light and stutter dial tone be on all the time.
It looks like google voicemail notifications have been left out with the new authentication method. I would love to get those notifications added back if at all possible.
Quote from: BigRedBrent on September 13, 2014, 02:39:37 AM
It looks like google voicemail notifications have been left out with the new authentication method. I would love to get those notifications added back if at all possible.
Voicemail notifications are still available - you can enable the message waiting indication (MWI) function as follows:EDITED
As pointed out by Taoman further down this thread, MWI notifications no longer work with Google Voice
If you check the box for Message Waiting, the stutter dial tone sounds and message light stay lit all the time no matter if there is a voice mail or not.
Quote from: MarkObihai on September 13, 2014, 04:41:54 AM
Quote from: BigRedBrent on September 13, 2014, 02:39:37 AM
It looks like google voicemail notifications have been left out with the new authentication method. I would love to get those notifications added back if at all possible.
Voicemail notifications are still available - you can enable the message waiting indication (MWI) function as follows:
- From the OBi Dashboard, click the name of your device
- Scroll down the device configuration page and click "OBi Expert Configuration"
- At the next page click "Enter OBi Expert"
- Select "Voice Service -> SPx Service", where SPx service is the service you have GV configured on (e.g SP1)
- Scroll down until you find "MWIEnable", "X_VMWIEnable" and "MessageWaiting" - all three are grouped together in the "Calling Features" section
- Enable all these options by unchecking the "OBiTALK Settings' box then uncheck "Device Default" then check the "Value" field to enable
- Scroll to the bottom of the page and click "submit"
Your device will restart and MWI should be enabled.
I just went through this process then made a test call, left a message and it all works.
Hi Mark,
In my last post I attached an image of my OBi202's calling features section. It does not contain an entry for MessageWaiting, but I was able to select "MWIEnable" and "X_VMWIEnable". Is there a reason I am missing the MessageWaiting option on my device and what can I do to get this working.
Thanks!
I also don't have the message waiting option my OBi100 settings. My new 200 arrives Monday. I wonder if it will have this option. Just selecting the first two items just failed to work for me.
I checked my 202 and it does not have the Message Waiting option. I only see that on the 1032s and it causes the light and stutter dial ton to remain on all the time.
Quote from: ceg3 on September 13, 2014, 06:28:05 AM
I also don't have the message waiting option my OBi100 settings. My new 200 arrives Monday. I wonder if it will have this option. Just selecting the first two items just failed to work for me.
It's gone from my 200. Must have been removed in a recent firmware upgrade.
The MWI and VMWI options are there, on the Voice Service page. See my attached screenshots -- one for my 202, showing a SIP Service Provider slot and the other for my 1032, showing Google Voice as a SP.
However: Mark, the issue is that, even with these settings enabled, they have no effect on generating MWI/VMWI signals for Google Voice as a service provider.
The question to your engineers is: is this a bug that they're working on, or is it a limitation of the new access method for Google Voice?
Voicemail Notification is absent from any SP configured for Google Voice via the OBiTALK portal.
Quote from: gderf on September 13, 2014, 08:03:14 PM
Voicemail Notification is absent from any SP configured for Google Voice via the OBiTALK portal.
Which is what I just said.
Quote from: SteveInWA on September 13, 2014, 07:54:36 PM
The question to your engineers is: is this a bug that they're working on, or is it a limitation of the new access method for Google Voice?
This was posted on slickdeals by someone who emailed Obihai support asking about this issue:
QuoteObihai's official response to me regarding the message waiting indication:
"The vmail indicator (either light or stuttered tone) is no longer a feature
that is supported on the OBi with Google Voice.
You would need to check your gmail or hangouts to find out if there is
voicemail pending."
Thanks, Taoman!
Quote from: SteveInWA on September 13, 2014, 07:54:36 PM
The MWI and VMWI options are there, on the Voice Service page. See my attached screenshots -- one for my 202, showing a SIP Service Provider slot and the other for my 1032, showing Google Voice as a SP.
However: Mark, the issue is that, even with these settings enabled, they have no effect on generating MWI/VMWI signals for Google Voice as a service provider.
The question to your engineers is: is this a bug that they're working on, or is it a limitation of the new access method for Google Voice?
Steve,
In your 2nd screenshot, you also have the parameter "MessageWaiting" but I see it is not checked as Mark had in his example. If you enable that setting on the 1032, it should get the MWI working on that device. Since that option is absent from the 202, it is looking like that may be part of the problem.
Quote from: avinyc on September 13, 2014, 09:24:16 PM
Quote from: SteveInWA on September 13, 2014, 07:54:36 PM
The MWI and VMWI options are there, on the Voice Service page. See my attached screenshots -- one for my 202, showing a SIP Service Provider slot and the other for my 1032, showing Google Voice as a SP.
However: Mark, the issue is that, even with these settings enabled, they have no effect on generating MWI/VMWI signals for Google Voice as a service provider.
The question to your engineers is: is this a bug that they're working on, or is it a limitation of the new access method for Google Voice?
Steve,
In your 2nd screenshot, you also have the parameter "MessageWaiting" but I see it is not checked as Mark had in his example. If you enable that setting on the 1032, it should get the MWI working on that device. Since that option is absent from the 202, it is looking like that may be part of the problem.
No, the unchecked options with the "2" after them are to turn on the indicators on phone port 2 vs. phone port 1 (this is on an OBi 202, which has two independent RJ11 phone ports).
The test I ran was on the 1032 IP phone, which has only one phone port (the phone, itself), and it doesn't work.
As Taoman replied, Obihai has already confirmed that MWI/VMWI is no longer supported for Google Voice.
Quote from: SteveInWA on September 13, 2014, 09:43:04 PM
No, the unchecked options with the "2" after them are to turn on the indicators on phone port 2 vs. phone port 1 (this is on an OBi 202, which has two independent RJ11 phone ports).
The test I ran was on the 1032 IP phone, which has only one phone port (the phone, itself), and it doesn't work.
As Taoman replied, Obihai has already confirmed that MWI/VMWI is no longer supported for Google Voice.
Hi Steve, I wasn't referring to the parameters marked with a 2. I just noticed on the 1032 screenshot you had the 3rd parameter labeled "MessageWaiting" and it was unchecked. The 3 of them are "MWIEnable", "X_VMWIEnable" and "MessageWaiting". No matter though, as I see that Mark edited his post to say this feature is currently unavailable. I just found that a little strange that certain devices still had the old parameter for MessageWaiting and other devices like the OBi202 do not.
In any event, it appears there is no manual workaround. It is a bit confusing as the capability does exist and has worked prior to the firmware upgrade. Ooma devices do not appear affected by this problem either, so perhaps it will be fixed for us in a future update.
The "MessageWaiting" parameter is a dynamic register that actually holds the status of, well, Message Waiting! It's not a static setting. I don't know why they included in the settings page, since it is useless and misleading.
You can't make a comparison at all to your Ooma device or to a SIP VoIP provider. This issue is unique to Google Voice, which does not use the standard SIP protocol, and thus, is not sending MWI/VMWI signals the same way.
Quote from: SteveInWA on September 14, 2014, 06:12:35 PM
You can't make a comparison at all to your Ooma device or to a SIP VoIP provider. This issue is unique to Google Voice, which does not use the standard SIP protocol, and thus, is not sending MWI/VMWI signals the same way.
Does XMPP even support MWI/VMWI signaling?
I did some Google searches to try to find out and the closest I could come was this post (http://mail.jabber.org/pipermail/sip-xmpp/2008-August/000072.html) from August of 2008 which discussed it as a feature request. If XMPP doesn't support communicating those items Obihai must have been accessing that information by using the credentials (Google userid and password) that they no longer require, perhaps via a web service of some sort that requires those credentials.
That's just a guess but something other than XMPP must have been used to get message waiting status since there would be no reason to stop supporting it if it is available as part of the XMPP protocol. Or maybe Obihai is just positioning for the replacement of XMPP by Google?
I miss this feature but usually disabled it. I was looking at turning it back on though. The 202 would get SMS sent to the caller ID which was really cool unless you didn't turn it off at night.
Quote from: ramjet73 on September 14, 2014, 06:47:54 PM
Quote from: SteveInWA on September 14, 2014, 06:12:35 PM
You can't make a comparison at all to your Ooma device or to a SIP VoIP provider. This issue is unique to Google Voice, which does not use the standard SIP protocol, and thus, is not sending MWI/VMWI signals the same way.
Does XMPP even support MWI/VMWI signaling?
I did some Google searches to try to find out and the closest I could come was this post (http://mail.jabber.org/pipermail/sip-xmpp/2008-August/000072.html) from August of 2008 which discussed it as a feature request. If XMPP doesn't support communicating those items Obihai must have been accessing that information by using the credentials (Google userid and password) that they no longer require, perhaps via a web service of some sort that requires those credentials.
That's just a guess but something other than XMPP must have been used to get message waiting status since there would be no reason to stop supporting it if it is available as part of the XMPP protocol. Or maybe Obihai is just positioning for the replacement of XMPP by Google?
I really don't know how Obihai did it, and based on the number of times it broke and had to be modified over the years, it likely wasn't using something officially-supported. We'll just have to wait and see if this feature reappears over time as the two companies evolve their services.
Short version:
GV MWI (stutter tone and visual indication) is working fine on an OBI 200 SW 3.0.1 (Build: 4367) configured manually using the OBI 200 web interface and never configured in the OBITALK portal.
Long version:
I just got an OBI 200 that came with SW 3.0.1 (Build: 4367). I was an early adopter of the OBI 110 and after just updating the 110's firmware and getting forced into using the OBITALK gateway and the new Google authorization, I made sure to stay away from OBITALK and disabled firmware updates and OBITALK before letting the OBI 200 have internet access.
(Updated my OBI 110 fw from this thread Build 2872 http://www.obitalk.com/forum/index.php?topic=8482.0)
After manually setting up voip.ms, 2 GV lines and a free Callcentric DID using only the OBI200 web interface, GV voice mail indication, both stutter tone and visual indication, is working fine. I'll definitely avoid any firmware upgrades and will be one pissed off customer if they manage to force one. They shouldn't be able to unless they've left a hidden backdoor access mechanism.
I've been away from these forums since the first few months after the OBI 100/110 release and was appalled to find OBIHAI no longer allows firmware downgrades. On top of that they don't even seem to be providing release notes for many firmware versions. I can't find any info on the changes to the OBI 110 firmware I upgraded to or the firmware that came on my new OBI200.
As an early adopter of OBIHAI's products, I'm disappointed to see their focus has shifted so much. Even with their new business focus, I don't understand companies who prohibit firmware downgrades and avoid doing business with them whenever possible. No one is perfect and I won't accept downtime when a firmware release breaks something critical to me when a simple downgrade to a previous version could get me back up quickly.
Quote from: Newbie on September 15, 2014, 11:23:14 PM
After manually setting up voip.ms, 2 GV lines and a free Callcentric DID using only the OBI200 web interface, GV voice mail indication, both stutter tone and visual indication, is working fine. I'll definitely avoid any firmware upgrades and will be one pissed off customer if they manage to force one. They shouldn't be able to unless they've left a hidden backdoor access mechanism.
My understanding is that you will have to upgrade the firmware at some point or GV will just stop working since Google is now requiring the authorization method that is only supported by the new firmware.
You've essentially figured out a way to "stop the clock", and work around the new security requirements and firmware, but that is only a temporary solution. The changes in GV were initiated by Google, not Obihai, and IMO having GV support without MWI/VMWI indicators is still better than not having it at all.
Quote from: Newbie on September 15, 2014, 11:23:14 PM
Short version:
GV MWI (stutter tone and visual indication) is working fine on an OBI 200 SW 3.0.1 (Build: 4367) configured manually using the OBI 200 web interface and never configured in the OBITALK portal.
It's good to hear MWI is still working for you, however this method of connecting to GV is no longer supported.
Quote from: Newbie on September 15, 2014, 11:23:14 PM
Long version:
I just got an OBI 200 that came with SW 3.0.1 (Build: 4367). I was an early adopter of the OBI 110 and after just updating the 110's firmware and getting forced into using the OBITALK gateway and the new Google authorization, I made sure to stay away from OBITALK and disabled firmware updates and OBITALK before letting the OBI 200 have internet access.
(Updated my OBI 110 fw from this thread Build 2872 http://www.obitalk.com/forum/index.php?topic=8482.0)
I think it's important to clarify a few things here to understand why GV is implemented in the way it is and how it fits alongside Obihai's broader communication platform support:
- Obihai develops cloud managed communication devices that are sold globally to both service providers and consumers. The OBiTALK cloud is a highly-scalable device provisioning and management platform designed to operate alongside or directly integrate with service provider infrastructure.
- The devices that Obihai sell to consumers leverage this same platform but on a "micro" scale with a more friendly user interface. You can think of this as having your own (user friendly) mini service provider interface for managing up to a dozen or so devices, regardless of where they are located.
- For our consumer customers with a Google account, Obihai supports Google Voice when it is setup via the OBiTALK portal. Google only supports OBi devices authenticating with their platform using the new secure authentication method via the OBiTALK portal.
- We also support Approved Service Providers via the portal, whereby the sign up for service and service provisioning is done directly between the ITSP and the OBiTALK portal by way of API. We hope to add more Approved Service Providers in the future, both from North America and other countries around the world.
- Our devices include a comprehensive feature set to allow our customers to flexibly configure their device for their application or to their preference. One feature we include is the ability for our users to remove their device from the OBiTALK platform and manage it locally as well as manage firmware upgrades manually. Taking note of the third bullet point, GV authentication is not supported via the local UI
We always recommend our customers use the OBiTALK portal for the best supported user experience that leverages all the additional features of their device (such as approved service providers and supported GV). The vast majority of OBi owners want to set their device up via the portal and forget about it.
Quote from: Newbie on September 15, 2014, 11:23:14 PM
After manually setting up voip.ms, 2 GV lines and a free Callcentric DID using only the OBI200 web interface, GV voice mail indication, both stutter tone and visual indication, is working fine. I'll definitely avoid any firmware upgrades and will be one pissed off customer if they manage to force one. They shouldn't be able to unless they've left a hidden backdoor access mechanism.
Please ensure you've followed the guidance within the Device Admin Guide (http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf) to ensure your device operates in the desired fashion for your advanced configuration.
Quote from: Newbie on September 15, 2014, 11:23:14 PM
I've been away from these forums since the first few months after the OBI 100/110 release and was appalled to find OBIHAI no longer allows firmware downgrades. On top of that they don't even seem to be providing release notes for many firmware versions. I can't find any info on the changes to the OBI 110 firmware I upgraded to or the firmware that came on my new OBI200.
There are a number of reasons for not supporting firmware downgrades. Security, functionality and the requirements of the majority of end users is what drives this approach. This may be inconvenient for some of our power users, but we have to weigh up the good of the many over the good of the individual. It's not a simple scenario with a simple answer I'm afraid.
I'll take on-board your firmware release notes comment.
Quote from: MarkObihai on September 16, 2014, 02:07:28 AMWe always recommend our customers use the OBiTALK portal for the best supported user experience
Mark,
What is your response to the following three users who now have ostensibly damaged devices? If they had not used the portal, it is likely the devices would still be functioning for their use.
Obihai bricked my Obi110 (http://www.obitalk.com/forum/index.php?topic=8531.0)
UPDATE FAILED/INTERUPTED now obi support says i need to buy a new one. (http://www.obitalk.com/forum/index.php?topic=8568.0)
obi100 toasted after failed firmware update? Power light flashing red and green (http://www.obitalk.com/forum/index.php?topic=8569.0)
If it were just one user, you could argue that maybe they had a momentary power failure or accidentally unplugged their device while it was updating. But three? All within a week, and all making the same firmware upgrade?
My device is out of warranty and I'll not use it with the OBiTALK portal or upgrade its firmware. The new firmware removes features (ability to configure GV without OBiTALK), comes with the risk of bricking the device, and can't be downgraded if I decide I don't like it. I realize how I choose to use my device is not really relevant to you, but I post this alternate point of view so that new users are aware of the risks of your recommendations.
m.
Quote from: Mango on September 16, 2014, 06:51:07 AM
What is your response to the following three users who now have ostensibly damaged devices? If they had not used the portal, it is likely the devices would still be functioning for their use .... If it were just one user, you could argue that maybe they had a momentary power failure or accidentally unplugged their device while it was updating. But three? All within a week, and all making the same firmware upgrade?
Hi Mango,
We spend considerable time ensuring the hardware used in the manufacturing of our products is durable and as such offer a
1-year warranty on the hardware. As with any electronic device it has a finite life span and some users will experience a longer device life span than others - this could be due to the nature of the components within the device, the operating environment or other factors. While you probably wouldn't expect an appliance (or device) to last 80 years, they sometimes do (http://www.dailymail.co.uk/news/article-1248253/Pensioner-cleans-Britains-oldest-vacuum-cleaner.html) (and sometimes they don't). The long and short of it is that we could manufacture a device to "NASA Standards" but the cost of the device would be prohibitive.
In the case of a device updating and failing during a software update this could be down to a number of reasons - for example a corrupted firmware image caused by a data connectivity problem or perhaps the heightened device activity triggering a failing component to finally fail. The number of failures versus the significant number of devices updated does not, in itself, indicate a problem with the firmware update or the OBiTALK portal.
- Mark.
I'm using this thread to collect anecdotal reports of OBi1 devices failing after the firmware update.
Obi 110 not working - just red light blinking after recent GV firmware update (http://www.obitalk.com/forum/index.php?topic=8634.0)
OBI100 Stopped Working after Firmware Upgrade (http://www.obitalk.com/forum/index.php?topic=8620.0)
This user has different symptoms than the others. The device appears to work, but loses connection with either Google Voice or a SIP service provider after a time. Obihai support confirmed it is electrically damaged however.
It is interesting that so many users have experienced a corrupted firmware image or component failure with this specific firmware update. I don't recall any other firmware update that garnered such complaints.
Obi100 Alternating Red / Green (http://www.obitalk.com/forum/index.php?topic=6534.0)
Three users in this thread report issues. One had his device replaced under warranty. One can resurrect the device, but has the problem every week or so.
Three users on this forum, out of who knows how many devices sold (tens or hundreds of thousands?) is within typical statistical process control expectations. This isn't an epidemic.
If MWI is very important to you and there turns out to be no updates to fix this or work arounds. You can use the voicemail service I have created to get your MWI working again. It offers the same features as Google voice such as transcription and email/sms alerts.