token error
Moonwalker:
Quote from: Mddd on June 12, 2021, 03:02:43 pm
Have refreshed credentials, yesterday and today. Sometimes it worked for a very short time. Other times not at all.
Quote from: Moonwalker on June 12, 2021, 02:21:28 pm
Have any of you tried refreshing your Google credentials? Delete the settings and sign in again?
That didn’t work for me until just about an hour or two ago. I refreshed the credentials, then sometime afterward I got the email and it’s now working again still. Not sure if that’s the difference for me but it could be. It could also be that whatever fix was done may take time to fully propagate to all servers. If they actually fixed it that is.
Yeah unfortunately mine is back to throwing the error again. I did say it “seemed” to be fixed, but what seems to be and what is is often not the same thing, Guess we’ll just have to wait until Google and Poly figure it out. In the meantime I recall when hardline phones sometimes went dead for days. At least we have alternate workarounds now. Back then your only choice was to get in your car and drive to whomever you wanted to talk with. Or just wait.
MSRobi:
There is nothing you can do, the problem is not with your device, it isn't with refreshing google credentials, etc. It is out of our control.
I've been up and down all day, and the easiest way for me to tell is the green lights on my Obi202 where the phone lines are plugged in. If they are green, I'm working. If not, I'm not working and get "registration not required" or "token error" on my dashboard.
Fortunately GVoice is not affected, so I can use voice.google.com with my headset and make/receive calls. I also linked my cell phone to my GVoice account a long time ago, but usually don't forward to it because forwarding to OBi202 has been bulletproof until today. Now I have my GVoice number forwarding to my cell phone.
If things get really bad, I'll look into CallCentric.
Moonwalker:
Quote from: Hoeveer on June 12, 2021, 02:38:30 pm
If this is related to Google pulling the plug on Hangouts, then we're screwed...
I has nothing to do with hangouts. Hangouts and Voice have been disconnected from each other for a long time in anticipation of Chat, which isn’t intended for calling or messaging phones at all. Voice has been designed for that from its inception. Google integrated Voice with Hangouts in the hopes of creating a one size fits all solution to communications. Technology and regulation changes killed that dream.
This is nothing more than a glitch in the authorization systems wherein Poly and Google auth systems aren’t playing well together. More than likely because of something Google changed. It’s happened before with other apps that couldn’t, or just didn’t, keep up with Google’s changes.
Moonwalker:
Quote from: MSRobi on June 12, 2021, 03:45:48 pm
There is nothing you can do, the problem is not with your device, it isn't with refreshing google credentials, etc. It is out of our control.
I've been up and down all day, and the easiest way for me to tell is the green lights on my Obi202 where the phone lines are plugged in. If they are green, I'm working. If not, I'm not working and get "registration not required" or "token error" on my dashboard.
Fortunately GVoice is not affected, so I can use voice.google.com with my headset and make/receive calls. I also linked my cell phone to my GVoice account a long time ago, but usually don't forward to it because forwarding to OBi202 has been bulletproof until today. Now I have my GVoice number forwarding to my cell phone.
If things get really bad, I'll look into CallCentric.
THIS^^^^^^^^^^^
G-Man:
While awaiting a fix between Poly-GV, I tried to place calls directly from the GV web interface using my PC and Chrome browser. For some reason the phone button icon you click to dial is greyed out (web UI).
I’m assuming this shouldn’t be related to the current Poly-GV issues because another forum stated even if Polycom devices are having issues, that using the GV app or the browser interface directly supposedly still works fine because they are unrelated to Obi devices.
However, as stated, my Dial (call) button is greyed out. So, anyone else newly experiencing this? Could this somehow still be related? Or should I treat/troubleshoot this as a separate issue? I will add that - Google recently sent me an email stating my “Linked number” will be removed unless I requested otherwise. But the wording sounded as if it would NOT affect service, and appeared to be just a house-keeping effort on unused phone numbers.
Any ideas? Is it related, unrelated? Thanks...
Navigation
[0] Message Index
[#] Next page
[*] Previous page