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