Connect Failed: 403 Forbidden;Token Error
turtlejay:
I just received an email stating a service offline alert. i check my dashboard and this error is showing. I attached a screen shot. Any advice? Ive tried deleting and re adding my google account three times.
Thanks
JAY
jholme004:
I too have been having a similar issue on my OBI212 -2 GV accounts, both showing “Connecting to 216.239.36.145;Token Error“. I have removed the GV lines from ObiTalk, deleted the ObiDevice from ObiTalk, removed the device from my GV account, removed ObiTalk permissions from Google, Reset my GV passwords, factory reset the obi Device, then reactivate everything - all using “incognito mode”. Calls work fine in/out of voice.Google.com and GV smartphone app. Poly insists it is a password issue (hence the password resets). I have even pulled out an old OBI202 and having THE SAME ISSUES.
I agree, a token issue is usually due to a bad password, BUT I’m wondering if, since the only way to config GV is through ObiTalk, the ObiTalk issues with activating is related to this - like not refreshing the token properly or timing out, etc. I’ve noticed most of the time in the past 4 days, when I re-add the GV lines, it shows “connected” for a minute or two before going to “Token error” or “registration Not Required”.
If anyone has any other thoughts, let us know!
Jay - if you haven’t done all of the above and need help, let me know. Historically, I’ve seen the token issue randomly occur before and the above steps have always resolved it.
-J
SteveInWA:
Quote from: jholme004 on January 19, 2021, 08:41:21 pm
I too have been having a similar issue on my OBI212 -2 GV accounts, both showing “Connecting to 216.239.36.145;Token Error“. I have removed the GV lines from ObiTalk, deleted the ObiDevice from ObiTalk, removed the device from my GV account, removed ObiTalk permissions from Google, Reset my GV passwords, factory reset the obi Device, then reactivate everything - all using “incognito mode”. Calls work fine in/out of voice.Google.com and GV smartphone app. Poly insists it is a password issue (hence the password resets). I have even pulled out an old OBI202 and having THE SAME ISSUES.
I agree, a token issue is usually due to a bad password, BUT I’m wondering if, since the only way to config GV is through ObiTalk, the ObiTalk issues with activating is related to this - like not refreshing the token properly or timing out, etc. I’ve noticed most of the time in the past 4 days, when I re-add the GV lines, it shows “connected” for a minute or two before going to “Token error” or “registration Not Required”.
If anyone has any other thoughts, let us know!
Jay - if you haven’t done all of the above and need help, let me know. Historically, I’ve seen the token issue randomly occur before and the above steps have always resolved it.
-J
Yah, the Poly person was incorrect; Google Voice on an OBiTALK device doesn't use passwords. It uses OAUTH token authentication, which only authorizes the device to access the Google Voice service on a Google account, and not access to the entire account. The problem you describe happened years ago, and was caused by a mismatch between changes Google had made on their side, and Obihai made to the firmware on their side. That particular problem was fixed long ago.
However, here are some possibilities: you said that Google Voice works "fine" on the app and the web GUI. How recently did you test it that way? Google has been suspending a lot of accounts lately, and suspension could cause your symptom. A couple of long-shot issues could also be the cause: 1) you are signed into Google account "A" on your smartphone and website, but you provisioned Google account "B" on the OBi, and there is a problem with "B". This is an easy mistake to make, since Google allows multiple accounts to be signed in on the same browser at the same time. 2) the account you're using on the OBiTALK device is not a consumer Gmail account. Google Voice for Google Workspace does not support consumer-class OBiTALK devices. Some OBiTALK devices that were on the old G Suite service might continue to work until the device is deleted and then a re-install is attempted.
Finally, at least when this happened a few years ago, when a user tried multiple times to (re)authorize a Google Voice account, Google would lock it out as a security precaution. Generally waiting a day or so would result in a successful authorization.
jholme004:
Thanks Steve. I remember that a few years ago...a nightmare!
I knew GV uses OAuth - the rep made it sound like it was me entering in the wrong password when signing in to GV. That didn’t make sense since it was successful and I could make a call, until a few minutes later.
I’ve been testing everything the past three days although this started on 1/7. Today, in a desperate attempt, I had logged out of all systems, including mobiles, and used Chrome in incognito mode. Calls could be made on account 1 via web, but I received the Token Error in the Obi. I tested both accounts, both ways. I’m a diagnostic engineer, so I made certain I was logged into the proper accounts for troubleshooting. I am using consumer GV - both accounts are gmail.com.
I was actually wondering about a lock out - is that done at a device level? Again, web and app work and I had removed the device from Google voice and ObiTalk permissions from my Google accounts just in case. I will remove the accounts from the Obi and give it a few days.
Didn’t mention this before, but definite believe this is a “Google Related” issue.. I have Anveo on SP3 and BulkVS on SP4 and both of them work flawlessly.
SteveInWA:
The lock-out would be temporary, and it is on the Google Voice back-end. There is nothing wrong with your OBiTALK devices. Given your excellent troubleshooting, and the continuing failure, it seems that there may be some corrupted information on the failing Google account. You probably can't get that fixed. Did you check and confirm that there were no OBiTALK entries on both the new Google Voice UI settings, and the old, "Legacy" GV UI settings?
Navigation
[0] Message Index
[#] Next page