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 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.