OBiTALK Community

Region Specific Technical / Service Provider Support => North America - Including Google Voice, Skype, etc. => Topic started by: BigRedBrent on August 11, 2017, 12:13:24 AM

Title: Authentication error [fixed]
Post by: BigRedBrent on August 11, 2017, 12:13:24 AM
This issue appears to be fixed now. :)


This only just started and is the first time this has happened to me.


My google voice disconnected from my device with an error:

Backing Off : Authentication error


When I try to register it again I get this error:

401. That's an error.

Error: disabled_client

The OAuth client was disabled.
Title: Re: Authentication error
Post by: dvpatel on August 11, 2017, 04:12:59 AM
Same here. So I am not alone. I missed your post. I have the same issue. I tried to remove and add the line back and now I cannot add it due to the authentication issue.

Seems to be something broken between Obi and GV as my GV is fine on my cellphone.
Title: Re: Authentication error
Post by: oemguy on August 11, 2017, 04:55:31 AM
Same exact issue here.
Title: Re: Authentication error
Post by: goldie26 on August 11, 2017, 05:17:42 AM
Same issue

additionally

In my Google Voice account under
My account->"Connected apps & sites"->"Apps connected to your account" 
obivoice app has disappeared
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 06:12:41 AM
This is just a guess, but Google was going to be deactivating oath 2 (i think) and application devs have been told about this for well over a year... They had to upgrade to oath 3.  I had to do this for a couple of apps I maintain.  It's possible Obi didn't perform this upgrade and now we are all screwed.  I do believe the cutoff date was sometime this August, so timing is about right.

Anyone have a way of getting in touch with support?  I am way past my maintenance contracts on all of my devices.
Title: Re: Authentication error
Post by: drgeoff on August 11, 2017, 06:14:47 AM
http://www.obitalk.com/forum/index.php?topic=12875.0

I suggest "Do not adjust your set" and wait for Obihai and/or GV to fix whatever is broken.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 06:45:15 AM
Some additional info from the google oath error page:


401. That's an error.

Error: disabled_client

The OAuth client was disabled.

Request Details
response_type=code
redirect_uri=https://www.obitalk.com/obinet/pg/obhdev/gvtoken
client_id=565436231175-v2ed4f21arki7dt43pks0jlsujatiq2i.apps.googleusercontent.com
scope=https://www.googleapis.com/auth/googletalk https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/userinfo.profile
access_type=offline
approval_prompt=force

That's all we know.
Title: Re: Authentication error
Post by: LetsTryThatAgain on August 11, 2017, 06:48:38 AM
Add me to the list - everything was working yesterday, but today I could not make or receive any calls, and now Obitalk is no longer connected with my Google account.

Hopefully they figure this out soon!
Title: Re: Authentication error
Post by: francesco on August 11, 2017, 07:12:26 AM
Add me to the list. Sigh... same issue here too.
Title: Re: Authentication error
Post by: Webslinger on August 11, 2017, 07:13:59 AM
Would be useful if people stated what model ATAs and firmware versions they're using.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 07:15:41 AM
Quote from: Webslinger on August 11, 2017, 07:09:16 AM
Is this situation only happening for OBi110/100 users that no longer have new firmware developed?
http://blog.obihai.com/feeds/posts/default

The OBi200/202 users that I know are not having issues when using the latest firmware: http://fw.obihai.com/OBi202-3-1-1-5695EX.fw.

I have the latest firmware, 5695EX on my 202's.  This isn't just a 100/110 issue.  I have multiple 200's & 202's, GV has stopped working on all of them, as of this AM.
Title: Re: Authentication error
Post by: Taoman on August 11, 2017, 07:16:40 AM
Quote from: Webslinger on August 11, 2017, 07:13:59 AM
Would be useful if people stated what model ATAs and firmware versions they're using.
Agreed. What OBi devices are you using?

I am connecting directly with an OBi 200 with no issues. Inbound and outbound calls work fine. I've rebooted with no issues.

I also use the Simonics GV gateway with my OBi 110 without any issues.

Edit: I am using 3.1.1 (Build: 5657) fw on my OBi 200 which is still working fine with GV.
Title: Re: Authentication error
Post by: Freshmaker on August 11, 2017, 07:16:56 AM
Quote from: Webslinger on August 11, 2017, 07:09:16 AM
Is this situation only happening for OBi110/100 users that no longer have new firmware developed?
http://blog.obihai.com/feeds/posts/default

The OBi200/202 users that I know are not having issues when using firmware version 3.1.1 (Build: 5695EX): http://fw.obihai.com/OBi202-3-1-1-5695EX.fw.

I have an Obi200 with firmware 3.1.1 (Build: 5463EX) and am having the same OAuth issue. Are you saying this is a known issue that was fixed in 5695EX?
Title: Re: Authentication error
Post by: dvpatel on August 11, 2017, 07:18:04 AM
I have a Obi200 with this issue.
Quote from: Webslinger on August 11, 2017, 07:09:16 AM
Is this situation only happening for OBi110/100 users that no longer have new firmware developed?
http://blog.obihai.com/feeds/posts/default

I have a Obi200 with this issue. You might want to re-confirm that your buddies with OBi200/202 are up this morning. Several users with 200 and 202 have reported this outage. I am one FW behind and did not update the FW this morning as it seems its a issue with OBi and GV and has nothing to do with the actual FW on the device itself.
Quote from: Webslinger on August 11, 2017, 07:09:16 AM
The OBi200/202 users that I know are not having issues when using firmware version 3.1.1 (Build: 5695EX): http://fw.obihai.com/OBi202-3-1-1-5695EX.fw.
Title: Re: Authentication error
Post by: dvpatel on August 11, 2017, 07:19:19 AM
Ditto.

I run the same FW and I do not think the new FW has a fix.
Quote from: Freshmaker on August 11, 2017, 07:16:56 AM
I have an Obi200 with firmware 3.1.1 (Build: 5463EX) and am having the same OAuth issue. Are you saying this is a known issue that was fixed in 5695EX?
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 07:20:34 AM
Quote from: Taoman on August 11, 2017, 07:16:40 AM
Quote from: Webslinger on August 11, 2017, 07:13:59 AM
Would be useful if people stated what model ATAs and firmware versions they're using.
Agreed. What OBi devices are you using?

I am connecting directly with an OBi 200 with no issues. Inbound and outbound calls work fine. I've rebooted with no issues.

I also use the Simonics GV gateway with my OBi 110 without any issues.

Are you connected directly to your gvoice accounts, using the built-in oauth?  Or do you have other SPs setup also?  GV is the only service having a problem.  I have accounts with Callcentric, and a couple of other SIP services that are working without a problem.  I'm just manually selecting one of those SPs to make calls now (**(sp#), ie: **2 1-212-555-1212)

The newest firmware does NOT have a fix for this problem.  I updated 2 202's to it this AM with no change.
Title: Re: Authentication error
Post by: A_Friend on August 11, 2017, 07:20:56 AM
I have two devices, a 200 and a 202, each with different GV numbers.  Or, at least I did.  Both failing to register this morning.

The GV number assigned to the 200 is set up to ring, so no outgoing and incoming going straight to voicemail.  If this persists, I'll reroute it.  The 202 is only used for outgoing, its GV number rings to my main callcentric number

(My voip.ms and callcentric accounts are just fine, so I'm not incommunicado, just paying for outgoing calls like regular muggles.)

I run both devices with Obitalk off, so no firmware upgrades in a while.
Title: Re: Authentication error
Post by: Freshmaker on August 11, 2017, 07:21:48 AM
Quote from: dvpatel on August 11, 2017, 07:19:19 AM
Ditto.

I run the same FW and I do not think the new FW has a fix.
Quote from: Freshmaker on August 11, 2017, 07:16:56 AM
I have an Obi200 with firmware 3.1.1 (Build: 5463EX) and am having the same OAuth issue. Are you saying this is a known issue that was fixed in 5695EX?

I dialed "***6" on my phone and it says "Software update not available"...so I am assuming 5463EX is the current firmware for the Obi200.
Title: Re: Authentication error
Post by: dvpatel on August 11, 2017, 07:22:03 AM
I had 3 lines configured on my OBi 200.

Two were showing as disconnected. One was showing as connected. When I rebooted to fix the two broken ones, the one that was showing as connected started showing as disconnected.

I dropped one of the lines that was showing as disconnected. Now I cannot add it back due to the Auth error that people are getting.

Quote from: Taoman on August 11, 2017, 07:16:40 AM
Quote from: Webslinger on August 11, 2017, 07:13:59 AM
Would be useful if people stated what model ATAs and firmware versions they're using.
Agreed. What OBi devices are you using?

I am connecting directly with an OBi 200 with no issues. Inbound and outbound calls work fine. I've rebooted with no issues.

I also use the Simonics GV gateway with my OBi 110 without any issues.

Edit: I am using 3.1.1 (Build: 5657) fw on my OBi 200 which is still working fine with GV.
Title: Re: Authentication error
Post by: Webslinger on August 11, 2017, 07:23:23 AM
Quote from: Marc on August 11, 2017, 07:15:41 AM
I have the latest firmware, 5695EX on my 202's.  This isn't just a 100/110 issue.  I have multiple 200's & 202's, GV has stopped working on all of them, as of this AM.

All the OBi200/202 ATAs I see that still work with GV have the following settings disabled:

Under System Management-->Auto Provisioning

a) For Auto Firmware Update ---> disabled

b) For ITSP Provisioning ---> disabled

c) For OBiTalk Provisioning--->disabled

d) Voice Services-->OBiTALK Service-->Obitalk service Settings disabled


So, Obitalk.com has not able to communicate with these ATAs, after they were provisioned, and they're all using 3.1.1 (Build: 5695EX).

If you disable Obitalk service and Obitalk Provisioning you will not be able to provision Google Voice using Obitalk.com.
Title: Re: Authentication error
Post by: Webslinger on August 11, 2017, 07:24:33 AM
Quote from: Freshmaker on August 11, 2017, 07:16:56 AM
Are you saying this is a known issue that was fixed in 5695EX?

No. That's not what I'm saying. But I am saying this issue isn't affecting everyone at the time of this post.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 07:24:55 AM
Quote from: Freshmaker on August 11, 2017, 07:21:48 AM
Quote from: dvpatel on August 11, 2017, 07:19:19 AM
Ditto.

I run the same FW and I do not think the new FW has a fix.
Quote from: Freshmaker on August 11, 2017, 07:16:56 AM
I have an Obi200 with firmware 3.1.1 (Build: 5463EX) and am having the same OAuth issue. Are you saying this is a known issue that was fixed in 5695EX?

I dialed "***6" on my phone and it says "Software update not available"...so I am assuming 5463EX is the current firmware for the Obi200.

You can download 5695 from here, but it won't fix this current problem.
http://fw.obihai.com/OBi202-3-1-1-5695EX.fw (http://fw.obihai.com/OBi202-3-1-1-5695EX.fw)
Title: Re: Authentication error
Post by: Taoman on August 11, 2017, 07:26:00 AM
Quote from: Marc on August 11, 2017, 07:20:34 AM

Are you connected directly to your gvoice accounts, using the built-in oauth?  Or do you have other SPs setup also?  GV is the only service having a problem.  I have accounts with Callcentric, and a couple of other SIP services that are working without a problem.  I'm just manually selecting one of those SPs to make calls now (**(sp#), ie: **2 1-212-555-1212)

The newest firmware does NOT have a fix for this problem.  I updated 2 202's to it this AM with no change.

On my OBi200 I connect directly to GV using OAuth 2. All other SPs are configured with SIP providers. Everything is working fine for me. I've rebooted several times without issue.

I use the Simonics GV gateway on my OBi110 so I don't know if a direct GV connection on my 110 would fail or not.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 07:31:46 AM
Quote from: Taoman on August 11, 2017, 07:26:00 AM
Quote from: Marc on August 11, 2017, 07:20:34 AM

Are you connected directly to your gvoice accounts, using the built-in oauth?  Or do you have other SPs setup also?  GV is the only service having a problem.  I have accounts with Callcentric, and a couple of other SIP services that are working without a problem.  I'm just manually selecting one of those SPs to make calls now (**(sp#), ie: **2 1-212-555-1212)

The newest firmware does NOT have a fix for this problem.  I updated 2 202's to it this AM with no change.

On my OBi200 I connect directly to GV using OAuth 2. All other SPs are configured with SIP providers. Everything is working fine for me. I've rebooted several times without issue.

I use the Simonics GV gateway on my OBi110 so I don't know if a direct GV connection on my 110 would fail or not.

I'm running tests to see if any of the suggestions made so far make any difference, so far none of my 20*'s can connect to any of my GV accounts.

The 100/110 non longer supports GV b/c it doesn't have the oauth support needed.  So stick with the setup you have there and don't try configuring the 110 directly, you won't be able to do so.
Title: Re: Authentication error
Post by: Taoman on August 11, 2017, 07:37:31 AM
Quote from: Marc on August 11, 2017, 07:31:46 AM

The 100/110 non longer supports GV b/c it doesn't have the oauth support needed.  So stick with the setup you have there and don't try configuring the 110 directly, you won't be able to do so.

Not sure where you came up with that idea. The latest firmware for the 100/110 which is 1.3.0 (Build: 2886) supports Google Voice and OAuth2 just fine.
Title: Re: Authentication error
Post by: Webslinger on August 11, 2017, 07:39:56 AM
Quote from: Marc on August 11, 2017, 07:20:34 AM
Are you connected directly to your gvoice accounts, using the built-in oauth?  Or do you have other SPs setup also?

No services on the ATAs that I'm looking at, including Google Voice, are having problems. None of them, however, allow communication with Obitalk.com.

In the past, the common error was "backing off" and in some cases was related to OAuth 2.0 tokens expiring: https://developers.google.com/identity/protocols/OAuth2#expiration. The instructions posted at http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460 usually resolved those related issues in the past.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 07:43:43 AM
Quote from: Webslinger on August 11, 2017, 07:23:23 AM
Quote from: Marc on August 11, 2017, 07:15:41 AM
I have the latest firmware, 5695EX on my 202's.  This isn't just a 100/110 issue.  I have multiple 200's & 202's, GV has stopped working on all of them, as of this AM.

All the OBi200/202 ATAs I see that still work with GV have the following settings disabled:

Under System Management-->Auto Provisioning

a) For Auto Firmware Update ---> disabled

b) For ITSP Provisioning ---> disabled

c) For OBiTalk Provisioning--->disabled

d) Voice Services-->OBiTALK Service-->Obitalk service Settings disabled


A) Shouldn't effect anything since people are on different firmware and still experiencing these problems.
B) I have this disabled also and I don't think it effects anything unless your service provider uses it... like if they use whiteboxed versions of Obi devices.

Disabling C & D would disable one's ability to provision GV accounts.

I suspect, that as with most things Google, changes get rolled out and effect some people before others.  With so many different colos and more servers than tRump could count $'s, I suspect that if not corrected, when next Google & the Obi device refresh their oauth token, those people will find themselves in the same boat that many of us are currently wading in :(
Title: Re: Authentication error
Post by: Webslinger on August 11, 2017, 07:46:52 AM
Quote from: Marc on August 11, 2017, 07:43:43 AM

A) Shouldn't effect anything since people are on different firmware and still experiencing these problems.
B) I have this disabled also and I don't think it effects anything unless your service provider uses it... like if they use whiteboxed versions of Obi devices.


All 4 of those must be disabled if you don't want firmware updated without your permission or Obihai to communicate with your ATA. This has been confirmed elsewhere before.

Related topic can be found here: http://www.obitalk.com/forum/index.php?topic=3229.msg21623#msg21623.

The point that I'm making is that Obitalk did not communicate with the ATAs in my area that still work today.


QuoteDisabling C & D would disable one's ability to provision GV accounts.

Correct. Once provisioned, C & D do not need to be enabled for services to continue working.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 07:47:41 AM
Quote from: Taoman on August 11, 2017, 07:37:31 AM
Quote from: Marc on August 11, 2017, 07:31:46 AM

The 100/110 non longer supports GV b/c it doesn't have the oauth support needed.  So stick with the setup you have there and don't try configuring the 110 directly, you won't be able to do so.

Not sure where you came up with that idea. The latest firmware for the 100/110 which is 1.3.0 (Build: 2886) supports Google Voice and OAuth2 just fine.

My bad.  I remembered incorrectly what the EOL notice said.  Memory is a funny thing... it works until it doesn't, lol.
Title: Re: Authentication error
Post by: Taoman on August 11, 2017, 07:51:20 AM
Quote from: Marc on August 11, 2017, 07:47:41 AM

My bad.  I remembered incorrectly what the EOL notice said.  Memory is a funny thing... it works until it doesn't, lol.

May I ask your geographic location? I'm in Seattle and I'm connecting to GV via 74.125.39.41 which is in Mountain View, CA.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 08:00:31 AM
Quote from: Taoman on August 11, 2017, 07:51:20 AM
Quote from: Marc on August 11, 2017, 07:47:41 AM

My bad.  I remembered incorrectly what the EOL notice said.  Memory is a funny thing... it works until it doesn't, lol.

May I ask your geographic location? I'm in Seattle and I'm connecting to GV via 74.125.39.41 which is in Mountain View, CA.

I'm in Vermont.  But I manage Obi devices in 10 states, although all but one are on the east coast.  The 10th is in redondo beach, ca. I don't know what IP's they were all connecting to... I'd have to go through firewall logs to figure that out :(

BTW, I've tried provisioning GV from a handful of 1032's and 1062's as well, and I get the same 401 error indicating the oauth client has been disabled.
Title: Re: Authentication error
Post by: drgeoff on August 11, 2017, 08:04:20 AM
FWIW although I don't have GV on an OBi device I do have GV on an Asterisk PBX (using Oauth2) and I can call out on that just fine.  :)
Title: Re: Authentication error
Post by: Taoman on August 11, 2017, 08:08:15 AM
Quote from: Marc on August 11, 2017, 08:00:31 AM
But I manage Obi devices in 10 states, although all but one are on the east coast. 

Yikes! Multiple OBi devices in 10 states and you're saying none of them are currently working with Google Voice?
Title: Re: Authentication error
Post by: SteveInWA on August 11, 2017, 08:08:57 AM
Folks:  I've confirmed with Obihai, that they are working on this.

There is no point whatsoever to anyone reconfiguring or upgrading firmware on the OBi devices at this time; please just stand by.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 08:09:58 AM
Quote from: drgeoff on August 11, 2017, 08:04:20 AM
FWIW although I don't have GV on an OBi device I do have GV on an Asterisk PBX (using Oauth2) and I can call out on that just fine.  :)

Same here and I am able to provision additional GV accounts on Asterisk.  I suspect this is either a political or financial dispute between Google and Obihai or simply a case of Obihai neglecting to reauthorize their domain level oauth key.  Either way we sit and wait and hope for some corrective action.
Title: Re: Authentication error
Post by: Marc on August 11, 2017, 08:11:05 AM
Quote from: SteveInWA on August 11, 2017, 08:08:57 AM
Folks:  I've confirmed with Obihai, that they are working on this.

There is no point whatsoever to anyone reconfiguring or upgrading firmware on the OBi devices at this time; please just stand by.

Thank you for the update and for communicating with Obihai about this issue, much appreciated.
Title: Re: Authentication error
Post by: melnphil on August 11, 2017, 08:16:12 AM
I'm in FL using a 202 that was working first thing this morning, then stopped working after a computer reboot.  I don't know if they are tied together or just coincidental timing.  Both my Google voice numbers show Backing Off :
Authentication error

My dad lives down the street and is using my old 110, his is still working fine.  FWIW, he has not rebooted his computer recently.  I've asked him not to until this issue seems to be straightened out, just in case.

I know the rebooting of the computer is very unlikely to be related, as both obis are connected to our routers, but thought I'd throw that out there. I don't really see a way that could be affecting a google authentication error on two different google voice accounts.    

I'm still within  the tech support period for my 202, so I submitted a help ticket, referencing how widespread this seems to be according to this forum.  
Title: Re: Authentication error
Post by: SteveInWA on August 11, 2017, 08:21:47 AM
Again:  Obihai and Google engineering teams are aware of this issue and working on it.  Do not spend any time fiddling with configuration or firmware at this time; it won't fix anything.
Title: Re: Authentication error
Post by: OBiSupport on August 11, 2017, 08:33:19 AM
Hi,

Thank you for the post.  Our team is looking into this issue and we will let you know. 


Best regards,
Obihai Technology, Inc.
Title: Re: Authentication error
Post by: dvpatel on August 11, 2017, 08:35:51 AM
Thank you for the update SteveInWA.
Title: Re: Authentication error
Post by: OBiSupport on August 11, 2017, 08:43:03 AM
Hi,

There is an issue with certain Google Voice authentications at this time, and we are working on resolving this.

Please wait for Google Voice to resolve the issue.


Thank you,
Obihai Technology
Title: Re: Authentication error
Post by: Webslinger on August 11, 2017, 08:47:50 AM
A friend rebooted his OBi202 and now he sees
"Backing Off (509s):Authentication error."

Don't reboot your ATA or IP Phone if your service is working.


Title: Re: Authentication error
Post by: Webslinger on August 11, 2017, 08:50:53 AM
Quote from: OBiSupport on August 11, 2017, 08:43:03 AM
There is an issue with certain Google Voice authentications at this time, and we are working on resolving this.

Has Obihai's client key been revoked?
Title: Re: Authentication error
Post by: SteveInWA on August 11, 2017, 08:53:01 AM
Quote from: Webslinger on August 11, 2017, 08:50:53 AM
Quote from: OBiSupport on August 11, 2017, 08:43:03 AM
There is an issue with certain Google Voice authentications at this time, and we are working on resolving this.

Has Obihai's client key been revoked?

Don't read anything into this.  Just wait for Obihai to fix it.
Title: Re: Authentication error
Post by: mhorn on August 11, 2017, 09:56:38 AM
Is there a way to be notified when the problem is resolved between Google and Obihai?  Should we just continue to follow this thread or is there some other mechanism?  

Thank you
Title: Re: Authentication error
Post by: Bayly on August 11, 2017, 10:23:00 AM
Same issue for me on Obi1062. My Obi202 is still working, but it's probably only a matter of time... Hope it's resolved soon.
Title: Re: Authentication error
Post by: spinedoc777 on August 11, 2017, 10:27:24 AM
Same issue here with my 202, sigh and I use it for my business.  Hope they fix it soon, some status reports or a report that they found the issue would be nice.
Title: Re: Authentication error
Post by: Whacky! on August 11, 2017, 10:47:15 AM
Same here!
Title: Re: Authentication error
Post by: fmcas1 on August 11, 2017, 11:01:51 AM
Thank you for the heads up...let's hope it doesn't take weeks to come back up!! :)
Title: Re: Authentication error
Post by: ctlw83 on August 11, 2017, 11:05:09 AM
Obi110 also having issue.

Confirmed running most recent firmware
Completely removed device from account.
Killed link in Google settings
Reset device
Re-registered Device
Signed out
Signed into ObiTalk using my Google account
Tried to authenticate for Google Voice
Still didn't work.  Same authentication error.
Title: Re: Authentication error
Post by: SchwannyT on August 11, 2017, 11:12:18 AM
Would this be an issue with Google's decommissioning of the Google Talk interface?  I'm using a free Google Apps account for my Google Voice connection.

???
Title: Re: Authentication error
Post by: james999 on August 11, 2017, 11:21:58 AM
Ugh... brand new to this.  Just received my ObiTalk200 and set it up a couple days ago.. Setup was so easy and had it working in 5 minutes. Then this morning, feeling overly confident, I started playing with the configuration settings and it stopped working with the GV auth issue. I (logically) assumed I just messed something up. Hours later... I found this thread.  Bad timing, but at least I know it wasn't something I messed up!   :o
Title: Re: Authentication error
Post by: francesco on August 11, 2017, 11:36:16 AM
2:35PM Eastern time.. It appears that the issue is resolved now. I was able to add GV back on SP1 on my OBI200. It is configured again, and working.
Title: Re: Authentication error
Post by: SteveInWA on August 11, 2017, 11:39:05 AM
Quote from: SchwannyT on August 11, 2017, 11:12:18 AM
Would this be an issue with Google's decommissioning of the Google Talk interface?  I'm using a free Google Apps account for my Google Voice connection.

???

NO.
Title: Re: Authentication error
Post by: james999 on August 11, 2017, 11:40:53 AM
11:40am PST.  It's working again.. OBI200 w/ Google Voice
Title: Re: Authentication error
Post by: soundview on August 11, 2017, 11:48:53 AM
Confirmed ... GV is working again
Title: Re: Authentication error
Post by: fmcas1 on August 11, 2017, 12:01:08 PM
Perfect...issue has been resolved...thanks guys!
Title: Re: Authentication error [fixed]
Post by: Freshmaker on August 11, 2017, 12:27:25 PM
Can someone from Obi give a summary of what happened exactly, and what steps can/will be taken to prevent it from happening again?
Title: Re: Authentication error [fixed]
Post by: OBiSupport on August 11, 2017, 12:32:09 PM
Hi,

Google Voice authentication issues has been resolved.  Please log back into your OBiTALK account and re-authenticate / re-establish to your Google Voice account again.  Once "Connected", please proceed with test calls incoming/outgoing to ensure all calls are successful.


Best regards,
Obihai Technology, Inc.
Title: Re: Authentication error [fixed]
Post by: Webslinger on August 11, 2017, 01:08:03 PM
Quote from: Freshmaker on August 11, 2017, 12:27:25 PM
Can someone from Obi give a summary of what happened exactly, and what steps can/will be taken to prevent it from happening again?

I'm not from Obihai, but there's nothing you could have done to prevent that from happening.

As far as I can tell, Google Voice revoked Obihai's client key and then reinstated it. I could speculate about why that happened, but it would just be speculation. I think this was all done on Google's end. Obitalk.com did not communicate with devices I've been monitoring since the problem occurred and after the problem was fixed. Those devices did not require logging back into Obitalk.com and re-authenticating anything. Consequently, I don't see the solution as being anything Obihai did, technically speaking.

The following reinforces my opinion that the technical solution did not come from Obihai's end:

Quote from: OBiSupportPlease wait for Google Voice to resolve the issue.
Title: Re: Authentication error [fixed]
Post by: Mango on August 11, 2017, 04:46:45 PM
Quote from: Freshmaker on August 11, 2017, 12:27:25 PM
Can someone from Obi give a summary of what happened exactly, and what steps can/will be taken to prevent it from happening again?

Chances are we will never know exactly what happened.  As a rule, Obihai doesn't share information.  In fact I'm surprised they posted here today at all.
Title: Re: Authentication error [fixed]
Post by: SteveInWA on August 11, 2017, 05:18:48 PM
Obihai support posted here, because I escalated it to them and pointed to this thread.

Google caused the issue.  It was a one-off, won't-happen-again issue.  It was not an expired certificate or token.
I'm not able to disclose any further details.
Title: Re: Authentication error [fixed] QUESTION, FIRMWARE UPDATE
Post by: nickforum on August 12, 2017, 05:10:22 AM
I had this issue.  i had posted in one of the threads.  it is working this morning.
BUT, QUESTOIN, on FIRMWARE UPDATE related to this

yestereay, when this occurred, I searched the forum , found older threads, thinking that those fixes wer needed, and they mentioned FIRMWARE UPDATE.  So, I dialed "***6", did say firmware update available, and I did the firmware update.

BUT, had this issue never happened, I would not have thought about FIRMWARE UPDATE at ALL !! (Obi 200)

Is there a message or prompt that will AUTO-ALERT us to the fact that updates are avilable, or do we have to actually check periodically to see if one is available??
thanks
Title: Re: Authentication error [fixed]
Post by: Mango on August 12, 2017, 08:32:15 AM
No there is not.  Obihai is very secretive with firmware updates - not only when they are released, but what bugs they fix and what features they introduce.

If you wish you can subscribe to https://www.obitalk.com/forum/index.php?topic=9983.0 where users report new versions when they find them.
Title: Re: Authentication error [fixed]
Post by: 66michael99 on September 25, 2017, 11:05:58 AM
Quote from: Mango on August 12, 2017, 08:32:15 AM
No there is not.  Obihai is very secretive with firmware updates - not only when they are released, but what bugs they fix and what features they introduce.

If you wish you can subscribe to https://www.obitalk.com/forum/index.php?topic=9983.0 where users report new versions when they find them.

Apparently not for everybody. I updated @ 5695. Followed every excruciating detail. I'd do a complete reset but fear loosing Anveo - my pain line. Google voice simply does not authenticate.
Title: Re: Authentication error [fixed]
Post by: 66michael99 on September 25, 2017, 11:33:10 AM
"main" line.
Title: Re: Authentication error [fixed]
Post by: SteveInWA on September 25, 2017, 02:55:08 PM
Quote from: 66michael99 on September 25, 2017, 11:05:58 AM
Quote from: Mango on August 12, 2017, 08:32:15 AM
No there is not.  Obihai is very secretive with firmware updates - not only when they are released, but what bugs they fix and what features they introduce.

If you wish you can subscribe to https://www.obitalk.com/forum/index.php?topic=9983.0 where users report new versions when they find them.

Apparently not for everybody. I updated @ 5695. Followed every excruciating detail. I'd do a complete reset but fear loosing Anveo - my pain line. Google voice simply does not authenticate.

What do you mean?  "apparently not for everybody"? 
Title: Re: Authentication error [fixed]
Post by: 66michael99 on September 26, 2017, 06:24:30 AM
Quote from: SteveInWA on September 25, 2017, 02:55:08 PM
Quote from: 66michael99 on September 25, 2017, 11:05:58 AM
Quote from: Mango on August 12, 2017, 08:32:15 AM
No there is not.  Obihai is very secretive with firmware updates - not only when they are released, but what bugs they fix and what features they introduce.

If you wish you can subscribe to https://www.obitalk.com/forum/index.php?topic=9983.0 where users report new versions when they find them.

Apparently not for everybody. I updated @ 5695. Followed every excruciating detail. I'd do a complete reset but fear loosing Anveo - my pain line. Google voice simply does not authenticate.

What do you mean?  "apparently not for everybody"? 


Is it possible that google voice no longer authenticates for Canadian users? Any Canadian users who can speak to this?
Title: Re: Authentication error [fixed]
Post by: SupTeamGuy on September 26, 2017, 03:54:17 PM
For Canadian customers that wants to use Google Voice service, you must generate a gmail account and further get a phone number within the US in order to have a functioning Google Voice service.  You can either reach out to families or friends residing in the US, have them get a gmail account and a phone number then relay all info (email address and password) to you.

Once you have all those information, you can proceed with using an OBi units in Canada.  When all setups are completed, you can make frees calls within the US and Canada.  No monthly or yearly service fees to worry about.

Or, alternative is to looking into using freephoneline.ca or voip.ms.


Best,
SupTeamGuy
Title: Re: Authentication error [fixed]
Post by: 66michael99 on September 26, 2017, 11:09:36 PM

I apologize for the misunderstanding. I wasn't clear enough.

As a Canadian, I've had Google Voice forever. What I'm asking is, with this new authentication
taking place, I can not for the life of me get Google Voice working again. Or, does it even work
on the Canadian side anymore?

The only thing I haven't tried, and as others have suggested, is to reset my obi 202 or to delete it, and re-add it.
I hesitate because I do not want to screw with my primary provider Anveo - even with the backups I have.

Suggestions? Perhaps from fellow Canadians?

I know SteveinWA had a great little piece on removing/deleting it and so on. Now I can't find it.

BTW, the search function on here is not optimum.

Title: Re: Authentication error [fixed]
Post by: SteveInWA on September 26, 2017, 11:52:29 PM
Quote from: 66michael99 on September 26, 2017, 11:09:36 PM

I apologize for the misunderstanding. I wasn't clear enough.

As a Canadian, I've had Google Voice forever. What I'm asking is, with this new authentication
taking place, I can not for the life of me get Google Voice working again. Or, does it even work
on the Canadian side anymore?

The only thing I haven't tried, and as others have suggested, is to reset my obi 202 or to delete it, and re-add it.
I hesitate because I do not want to screw with my primary provider Anveo - even with the backups I have.

Suggestions? Perhaps from fellow Canadians?

I know SteveinWA had a great little piece on removing/deleting it and so on. Now I can't find it.

BTW, the search function on here is not optimum.



I'm not a Canadian, but I do love visiting your beautiful country; does that qualify me?   :D

I haven't read or heard anything to suggest that Google Chat/XMPP is being geofenced outside the US.

You are posting a completely unrelated problem to the one this discussion thread addresses (a specific software issue that Google fixed).

Nonetheless, since you're here, I won't bully you to start your own thread.  The first thing I'd try, instead of blowing away your entire OBi configuration, would be to:
Title: Re: Authentication error [fixed]
Post by: 66michael99 on September 27, 2017, 10:35:29 AM

Yes, you are OF COURSE "allowed" to respond...

Anyway, I'm fairly tech savvy, and am able to follow directions.

(BTW, I have upgraded to 5695)

As I read yours, I kept on confirming that, yes, this is exactly
what I've been doing to get the obi 202 going. However, one thing,
after deleting/clearing the SP2 where Google Voice sits, I never reboot.

I'm wondering if that might be it...hmmm...

Will confirm once I get home...
Title: Re: Authentication error [fixed]
Post by: 66michael99 on September 27, 2017, 11:25:27 AM

So, i just tried once more to get Google Voice going on obi 202 as per your super easy instructions.

1) During the process I'm seeing "Configuring"
2) after some time (5 minutes or so) I get "Service not Configured"

I'm wondering whether "obitalk provisioning" and "ITSP Provisioning" needs tweaking (enabling/disabling) and whether "obitalk service" needs anything?

Thx...

Title: Re: Authentication error [fixed]
Post by: SteveInWA on September 27, 2017, 02:33:20 PM
If you previously disabled OBiTALK provisioning, that could be the issue, but I doubt it.  Another possibility might be if your Anveo configuration somehow locked down something, or changed something, that is interfering with Google Voice setup.

At this point, I'm going to recommend that you log into the OBiTALK dashboard, and click the button to completely delete your OBi off of your portal page.  Wait a few minutes while the LEDs blink and the device resets.  Then, unplug all the cords from the OBi to power it down.  Plug in the phone and power cords, not the Ethernet cable.  After it boots up, pick up the phone and key in ***8 then 1 to restore it to factory defaults. 

Meanwhile, open open an "incognito" or "private browsing" session on your browser (Ctrl-Shift-N for Google Chrome Browser, or Ctrl-Shift-P for Firefox or MSIE).  Log into only the one Google account that you're using with your OBi, and no others.  Press Ctrl-T to open another tab in that private window, and log back into the OBiTALK portal.

After the 202 chews on that factory restore for a good long time and finishes rebooting, then use the **5 procedure to add it back to your portal page, then set up Google Voice and see what happens (do this before attempting to set up Anveo again).  Don't make any manual or expert mode changes.
Title: Re: Authentication error [fixed]
Post by: 66michael99 on September 28, 2017, 07:17:39 AM
Quote from: SteveInWA on September 27, 2017, 02:33:20 PM
If you previously disabled OBiTALK provisioning, that could be the issue, but I doubt it.  Another possibility might be if your Anveo configuration somehow locked down something, or changed something, that is interfering with Google Voice setup.

At this point, I'm going to recommend that you log into the OBiTALK dashboard, and click the button to completely delete your OBi off of your portal page.  Wait a few minutes while the LEDs blink and the device resets.  Then, unplug all the cords from the OBi to power it down.  Plug in the phone and power cords, not the Ethernet cable.  After it boots up, pick up the phone and key in ***8 then 1 to restore it to factory defaults. 

Meanwhile, open open an "incognito" or "private browsing" session on your browser (Ctrl-Shift-N for Google Chrome Browser, or Ctrl-Shift-P for Firefox or MSIE).  Log into only the one Google account that you're using with your OBi, and no others.  Press Ctrl-T to open another tab in that private window, and log back into the OBiTALK portal.

After the 202 chews on that factory restore for a good long time and finishes rebooting, then use the **5 procedure to add it back to your portal page, then set up Google Voice and see what happens (do this before attempting to set up Anveo again).  Don't make any manual or expert mode changes.


Agreed.

It "could be" this or that, but at some point a good purging is needed. Will report back once I add obi back.

Thx...
Title: Re: Authentication error [fixed]
Post by: 66michael99 on October 02, 2017, 12:24:20 PM

SteveInWA,


As you'd suggested, I reset the OBI202. However, being the stubborn sort (terribly), I didn't quite follow your instructions "completely". I'd installed Anveo 1st and then GV in SP1 AND SP2 respectively. Otherwise, I followed you perfectly. Thanks a bunch, and God Bless...

To others, I can't stress this enough, READ INSTRUCTIONS and thank, profusely, the Pros who make our OBI lives palatable.

Thank you!
Michael
Title: Re: Authentication error [fixed]
Post by: SteveInWA on October 02, 2017, 02:29:52 PM
Glad to hear that it worked out.