August 04, 2021, 06:55:23 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Obi 202 and GV: Token error; "Registration not required", can't re-register GV  (Read 3301 times)
paul1149
Jr. Member
**
Posts: 35


« on: June 13, 2021, 05:31:11 am »

A few days a go Obi 202 stopped working. Attempts to call out bring a 'did not receive a response from provider' voice error. I thought the notices were due to power outages, but no, it's the unit.

I have a "token error". I tried to re-register with GV; then it said "registration not needed", and still wouldn't work.

I rebooted obi, router, and modem. Now I don't get the voice error, `did not receive a response from provider`, but there is no attempt at ringing the phone. And now the ObiTalk errors says: 'Connecting to 0.0.0.0;Token Error'. At least before it had a realistic-looking IP address.

Not looking good here. Any help would be greatly appreciated.
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 5405


« Reply #1 on: June 13, 2021, 05:59:27 am »

There are dozens of posts in several threads about this. No need to start another one.
Logged
paul1149
Jr. Member
**
Posts: 35


« Reply #2 on: June 13, 2021, 06:15:43 am »

I tried the only remedy I found here, which I documented above, to no avail. Not sure what else I could do.
Logged
paul1149
Jr. Member
**
Posts: 35


« Reply #3 on: June 13, 2021, 06:56:55 am »

Found a solution from a nearby thread; working thus far:

https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/h1jc58j/
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 6354



« Reply #4 on: June 13, 2021, 04:22:17 pm »


If I could post a gigantic BULLSHIT next to that guy's "solution" I would.  It's tiresome explaining WHY it's bullshit, but while harmless, it won't solve the problem, which can't be solved by any user settings.
Logged

MSRobi
Jr. Member
**
Posts: 39


« Reply #5 on: June 13, 2021, 07:53:01 pm »

If I could post a gigantic BULLSHIT next to that guy's "solution" I would.  It's tiresome explaining WHY it's bullshit, but while harmless, it won't solve the problem, which can't be solved by any user settings.

I wouldn't be too fast in declaring it bullshit.  I suspect that changing DNSServer1 to 1.1.1.1 caused a different DNS lookup to a backend server (or servers) that weren't affected, thus causing it to work on MY device (can't speak for others at different locations).

I did a few tests, and only when I used DNSServer1 "1.1.1.1", did I have full success.

I do plan on reversing the DNSServer1 and DNSServer2 settings back to the defaults tomorrow because I don't know if using 1.1.1.1 won't cause other problems longer term.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 6354



« Reply #6 on: June 13, 2021, 08:16:51 pm »

There is no harm in permanently using Google DNS:  8.8.8.8/8.8.4.4 or CloudFlare: 1.1.1.1 or Quad9 DNS:  9.9.9.9 

All are high-performance DNS with no redirects to ad sites selling domains, etc.  Pick whichever one you wish.  In fact, I recommend setting one of these DNS in your router, not at the client level.

However, none will fix the current Google Voice issue, which is digital certificate-related.

The problem should go away for all users sometime tomorrow.
Logged

MSRobi
Jr. Member
**
Posts: 39


« Reply #7 on: June 14, 2021, 04:00:47 am »

Thanks for the advice, and a big thanks for all your help in contacting the right people that could get this problem fixed.  I use Obi202 w/GVoice only, have cell phones as backups, and loving not paying a phone bill every month.

I expect problems like we had to happen intermittently...cell phone backup is good enough for me.  This forum is the best place to get info when the inevitable outages happen.

Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement