OBiTALK Community

General Support => Day-to-Day Use => Topic started by: VOIP_JoeSummy on August 17, 2015, 05:42:15 PM

Title: Is it that Google Voice set-up must be done via OBITalk site
Post by: VOIP_JoeSummy on August 17, 2015, 05:42:15 PM
For security reason, I would like not to add my OBI device to the OBITalk web site, and configure Google Voice & voip.ms locally.

But to my dismay, I recently discovered that Google Voice set-up must be performed through the OBITalk web site, and devices must be listed in the OBITalk site all the time. If I do the set-up through the local web-admin interface, in a naïve way, like just filling out my Google Voice user ID and password, it just won't work.

Can someone confirm it and tell me why?

Standard SIP-based services, like voip.ms, seem can be set up locally though.
Title: Re: Is it that Google Voice set-up must be done via OBITalk site
Post by: SteveInWA on August 17, 2015, 06:28:21 PM
If you had spent any time at all reading through the forum's posts over the past two years, you'd know the answer.

Obihai updated their devices to conform to Google's more-secure authentication protocol requirement, using OAUTH 2.0.  The initial setup must be performed via the OBiTALK dashboard (portal), which handles the negotiation with Google to get your permission to access your Google account, and then receive a secure access token.  Your Google account password is never stored on Obihai's servers nor on your device, when using this method.

After you perform this procedure, you can again disable the OBiTALK service on your device if you wish, but frankly, you are being "dismayed" over nothing.

See:  http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460 (http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460) for my setup instructions.

See:  http://www.obitalk.com/forum/index.php?topic=8685.msg57331#msg57331 (http://www.obitalk.com/forum/index.php?topic=8685.msg57331#msg57331) for Robert's instructions on a hybrid approach to managing the non-OBi functions locally, while also using the portal to configure GV.