token error
SteveInWA:
You will see "Registration not required", or you will see a bogus registration to 0.0.0.0, if you repeatedly attempt to re-register by re-booting the device. This is an anti-DOS measure. Don't keep re-trying. Just have a nice evening and look again tomorrow. You should find that the device will successfully register with no action needed on your part.
SteveInWA:
Quote from: erkme73 on June 13, 2021, 06:10:14 pm
I appreciate all you've done to try and temper frustrations Steve. Nothing like broadcasting that there is no solution, only to have the very next thread offer "advice" on front-end fixes.
What I find intriguing is that of the two 202 boxes I have (both registered to the same two GV accounts - one in the house, one in the barn), only one of them has been exhibiting this issue. The other has been working/reporting no issues solidly since all of this began.
Is the "known" issue a systemic one that should affect ALL 202s devices or is this a hit/miss kinda thing?
Google has many hundreds of servers, load balanced around the world, that support Google Voice. Some of the servers were impacted by the problem, and others were not. When you connect to a server, a load balancing algorithm picks the "best" server for you, based on several factors, including your location and distance to the servers (latency) and which servers are the least busy.
So, it is entirely possible that your devices were connected to different servers.
derrickearly:
I can make calls out, but still cannot receive calls. I have the dreaded "Registration Not Required" status.
TomForum:
Many thanks @SteveInWA!!
Still no service, but I'll continue to check it.
I assume this temporary fix should work for the issue "Connecting to 0.0.0.0" as well?
Somewhat OT, but for those that are getting status emails saying service is back--can someone please point me to the instructions to set those up? I've never once received an Obi status email nor see where to configure them.
thx
awriter:
Quote from: SteveInWA on June 13, 2021, 05:04:43 pm
Update as of 6/13 at 4:40 PM PDT:
Google Voice engineering has identified the cause of the problem and they have implemented a temporary fix. Your devices should resume working later tonight, if not already.
Again: no changes you make to your device(s) will fix this problem.
A longer-term fix will require more work on Poly's side.
Steve, made no changes per your suggestion - but just checked and I'm connected! Thanks for all your help.
Obi200/new england 10:40 pm est
Navigation
[0] Message Index
[#] Next page
[*] Previous page