December 12, 2017, 03:48:36 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1] 2 3 4
  Print  
Author Topic: Authentication error [fixed]  (Read 12349 times)
BigRedBrent
Newbie
*
Posts: 2



« on: August 11, 2017, 12:13:24 am »

This issue appears to be fixed now. Smiley


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.
« Last Edit: August 11, 2017, 12:29:58 pm by BigRedBrent » Logged
dvpatel
Newbie
*
Posts: 7


« Reply #1 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.
Logged
oemguy
Newbie
*
Posts: 2


« Reply #2 on: August 11, 2017, 04:55:31 am »

Same exact issue here.
Logged
goldie26
Newbie
*
Posts: 8


« Reply #3 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
Logged
Marc
Jr. Member
**
Posts: 71



« Reply #4 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.
Logged

OBi110 (stored in closet now,) OBi202 x 14, OBi1032 x 3, OBi1062 x 3
drgeoff
Hero Member & Beta Tester
*****
Posts: 2712


« Reply #5 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.
Logged
Marc
Jr. Member
**
Posts: 71



« Reply #6 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.
Logged

OBi110 (stored in closet now,) OBi202 x 14, OBi1032 x 3, OBi1062 x 3
LetsTryThatAgain
Newbie
*
Posts: 1


« Reply #7 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!
Logged
francesco
Newbie
*
Posts: 3


« Reply #8 on: August 11, 2017, 07:12:26 am »

Add me to the list. Sigh... same issue here too.
Logged
Webslinger
Full Member
***
Posts: 103


« Reply #9 on: August 11, 2017, 07:13:59 am »

Would be useful if people stated what model ATAs and firmware versions they're using.
Logged
Marc
Jr. Member
**
Posts: 71



« Reply #10 on: August 11, 2017, 07:15:41 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.
Logged

OBi110 (stored in closet now,) OBi202 x 14, OBi1032 x 3, OBi1062 x 3
Taoman
Hero Member
*****
Posts: 936


« Reply #11 on: August 11, 2017, 07:16:40 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.
« Last Edit: August 11, 2017, 07:18:18 am by Taoman » Logged
Freshmaker
Newbie
*
Posts: 3


« Reply #12 on: August 11, 2017, 07:16:56 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?
Logged
dvpatel
Newbie
*
Posts: 7


« Reply #13 on: August 11, 2017, 07:18:04 am »

I have a Obi200 with this issue.
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.
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.
Logged
dvpatel
Newbie
*
Posts: 7


« Reply #14 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.
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?
Logged
Marc
Jr. Member
**
Posts: 71



« Reply #15 on: August 11, 2017, 07:20:34 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.
Logged

OBi110 (stored in closet now,) OBi202 x 14, OBi1032 x 3, OBi1062 x 3
A_Friend
Newbie
*
Posts: 18


« Reply #16 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.
Logged
Freshmaker
Newbie
*
Posts: 3


« Reply #17 on: August 11, 2017, 07:21:48 am »

Ditto.

I run the same FW and I do not think the new FW has a fix.
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.
Logged
dvpatel
Newbie
*
Posts: 7


« Reply #18 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.

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.
Logged
Webslinger
Full Member
***
Posts: 103


« Reply #19 on: August 11, 2017, 07:23:23 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.
« Last Edit: August 11, 2017, 08:07:03 am by Webslinger » Logged
Pages: [1] 2 3 4
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC