Authentication error [fixed]
Webslinger:
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.
Marc:
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 :(
Webslinger:
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.
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.
Marc:
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.
Taoman:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page