December 11, 2017, 10:11:46 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 12311 times)
Webslinger
Full Member
***
Posts: 103


« Reply #20 on: August 11, 2017, 07:24:33 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.
Logged
Marc
Jr. Member
**
Posts: 71



« Reply #21 on: August 11, 2017, 07:24:55 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.

You can download 5695 from here, but it won't fix this current problem.
http://fw.obihai.com/OBi202-3-1-1-5695EX.fw
Logged

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


« Reply #22 on: August 11, 2017, 07:26:00 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.
Logged
Marc
Jr. Member
**
Posts: 71



« Reply #23 on: August 11, 2017, 07:31:46 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.
Logged

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


« Reply #24 on: August 11, 2017, 07:37:31 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.
Logged
Webslinger
Full Member
***
Posts: 103


« Reply #25 on: August 11, 2017, 07:39:56 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.
« Last Edit: August 11, 2017, 07:44:01 am by Webslinger » Logged
Marc
Jr. Member
**
Posts: 71



« Reply #26 on: August 11, 2017, 07:43:43 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 Sad
Logged

OBi110 (stored in closet now,) OBi202 x 14, OBi1032 x 3, OBi1062 x 3
Webslinger
Full Member
***
Posts: 103


« Reply #27 on: August 11, 2017, 07:46:52 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.


Quote
Disabling 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.
« Last Edit: August 11, 2017, 08:25:13 am by Webslinger » Logged
Marc
Jr. Member
**
Posts: 71



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

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


« Reply #29 on: August 11, 2017, 07:51:20 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.
Logged
Marc
Jr. Member
**
Posts: 71



« Reply #30 on: August 11, 2017, 08:00:31 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 Sad

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

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


« Reply #31 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.  Smiley
Logged
Taoman
Hero Member
*****
Posts: 931


« Reply #32 on: August 11, 2017, 08:08:15 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?
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3946



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

Marc
Jr. Member
**
Posts: 71



« Reply #34 on: August 11, 2017, 08:09:58 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.  Smiley

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

OBi110 (stored in closet now,) OBi202 x 14, OBi1032 x 3, OBi1062 x 3
Marc
Jr. Member
**
Posts: 71



« Reply #35 on: August 11, 2017, 08:11:05 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.
Logged

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


« Reply #36 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.  
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3946



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

OBiSupport
Administrator
****
Posts: 250


« Reply #38 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.
Logged
dvpatel
Newbie
*
Posts: 7


« Reply #39 on: August 11, 2017, 08:35:51 am »

Thank you for the update SteveInWA.
Logged
Pages: 1 [2] 3 4
  Print  
 
Jump to:  

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