OBi202 + GV is suddenly dropping calls on connect and Caller ID not working
drgeoff:
Quote from: GlennA on June 11, 2021, 07:56:46 pm
there definitely appears to be a widespread problem. I received several emails today saying my service was interrupted and then that it was fixed. Now it is out. I cannot make or receive calls. The dashboard says "token error"
Yes there are already several threads about the token error that many are experiencing. This thread is about a problem specific to the OP and has is totally unrelated to "token error".
telly0:
I've experienced the same problem for the last 2 days. I've need following a reddit discussion on this. Wish there were some official statement. https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/?sort=new
azrobert:
Quote
drt44090
Here's what I managed to do to get both my Obihai devices (200 & 202) "connected" and working again. (Yes, I suffered from the "registration not required", as well as the "token", issues).
1. In the Obitalk home page, select the desired device ... and then click "OBi Expert Configuration". Confirm that you actually want to go to that screen.
2. Then click "Enter OBi Expert"
3. On the left panel, under "Production Information" select:
SYSTEM MANAGEMENT » WAN Settings → or ←
ROUTER CONFIGURATION » WAN SETTINGS (menu changes between 200 & 202)
4. You then need to unclick the check marks under "OBiTALK Settings" for:
"DefaultGateway"
"DNSServer1"
"DNSServer2"
5. The check mark of the above 3 items will switch to "Device Default"; unclick those as well.
6. Default gateway is the IP of your home/business router
DNSServer1 I set to: "1.1.1.1" and DNSServer2 I set to "8.8.8.8"
7. Save the settings and then reboot your device.
Changing the Default Gateways ... and indicating the proper DNS servers to utilize brought me back to up-and-running; hope it does the same for you!
David
Thanks to drt44090 on Reddit and telly0 for the link to the Reddit thread!
The above fixed the problem for me, but not initially. I had DNSServer1/2 set on my router. After changing my router GV connected on my OBi200 and OBi1032.
Some people on Reddit say it fixed their problem and others not.
Taoman:
Quote from: azrobert on June 12, 2021, 05:06:40 pm
The above fixed the problem for me, but not initially. I had DNSServer1/2 set on my router. After changing my router GV connected on my OBi200 and OBi1032.
How long has it remained stable for you? I've had no problem with any of my OBi devices.
I've been using 8.8.8.8 as primary and 8.8.4.4 as my secondary for quite awhile now.
azrobert:
Quote from: Taoman on June 12, 2021, 05:29:19 pm
How long has it remained stable for you? I've had no problem with any of my OBi devices.
I've been using 8.8.8.8 as primary and 8.8.4.4 as my secondary for quite awhile now.
We went to a local restaurant for a couple hours and when we came back the 1032 was still connected, but the 200 had the token error. Powering it off for about 10 minutes “fixed” the problem. A quick power cycle didn’t help. The 1032 has been up for about 4 hours.
I previously had 8.8.8.8 and 8.8.4.4 set in my router. I’m skeptical that the DNS changes fixed the problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page