token error
igor@chysiuk.com:
I don't think switching obi to cloudflare/google dns is going to help and/or it's a good idea. Judging by the error I've got, this is an issue between Obi and Google Voice API. Switching DNS and other tricks may beg us through authorization, but we'll ever know which other API limit may be reached.
I would wait and look for alternative to google voice in a meantime :)
MSRobi:
I'm still up and running this morning. I'm not quite ready to declare victory though.
drgeoff:
http://www.obitalk.com/forum/index.php?topic=18329.msg108740#msg108740
awriter:
Quote from: MSRobi on June 13, 2021, 04:08:04 am
I'm still up and running this morning. I'm not quite ready to declare victory though.
Most of us still have no service as of 6/13 a.m. Please, folks - when reporting "success" here - also include your model. 200 or 202? There does appear to be a difference.
JP1975:
I am very surprised more people are not seeing this problem resolved.
My service was interrupted 3-5 days ago, like everyone else the token error connecting to Google Cloud was showing in the dashboard.
I tried removing the device, hard reset/soft reset 3-4 times wasting a couple of hours to no prevail.
I left the unit plugged in and active.
Yesterday in the morning a call came in and it was working. I made 2-3 calls no issue all back to normal.
Other users got the service back around the same time as shown in a few posts.
The question then is why did this start working for some and not others???
With Google it is always a secret, possible they made a change that worked for some users, maybe related to the ISP used??
Anyway still working this am, problem gone.
Thank to whoever did whatever.
Obi 200/Spectrum
Navigation
[0] Message Index
[#] Next page
[*] Previous page