Connect Failed: 403 Forbidden;Token Error
jholme004:
This morning, I had the brainiac Idea of moving the Obi202 to the "New" account - might as well test EVERYTHING including my ObiTalk Account (What if somehow it was corrupt?)
Well, I should have known better - 3 hours later and I'm still trying to add it to the new ObiTalk account.
At the same time, I deleted the "Home/Line1" account from my 212, deleted it from Google Voice, and deleted the ObiTalk permissions from my Google account and re-added it as SP1. (Of Note: It took 3 tries to re-add it - the first two tries, said "Registration not required", yet never showed as a device in GV - New or Legacy) When it did get re-added, it showed "Connected". I was able to make and receive calls via SP1 on the Obi212. After 1hr, it was still connected, and I was very optimistic since that is the registration period (3600 sec). However, after 1hr 43 min, it changed to "Connect Failed: 403 Forbidden; Token Error (server=216.239.36.145; retry in 115s)", then approx 15 minutes later "Connect Failed: 403 Declined;Token Error (server=216.239.36.145; retry in 188s)". I did not make or receive any calls, change any setting in Google Voice or ObiTalk, or look at or breathe near the Obi212. Since it is a "Forbidden" error, I followed instructions from another post (http://www.obitalk.com/forum/index.php?topic=16034.0, unplugging the Obi, then checking my GV account in Chrome using Incognito mode - I could place/receive calls normally there, as I could also from my GV mobile app. After plugging the 212 back in and it powering up, SP1 then showed "Connecting to 216.239.36.145;Token Error" - back to where we were.
After this, I added the "Office/Line 2" account to SP2 (This was the one I transferred to a different GV account then transferred back). When I added it, both SP1 and sp2 showed as "Connected". I tested outgoing call on SP2 and it went through. When I then went to test SP1, I received the "..has not received a response from the service provider" intercept. When I checked on the status in ObiTalk, both were now "Connecting to 216.239.36.145;Token Error[/b]". BTW, **9-222-222-222 is successful.
I decided to capture level 7 logs - Interestingly, when the Obi restarted there were these lines, that seem to show there is an issue when connecting via SSL:
Jan 24 19:44:16 Obi212 OBI212 TC:ssl connected
Jan 24 19:44:16 Obi212 OBI212 BASESSL:Server name not matching...accounts.google.com vs google.com
Jan 24 19:44:16 Obi212 OBI212 LHC:Server verification failed!
Jan 24 19:44:16 Obi212 OBI212 GAPI:verify server error
Jan 24 19:44:16 Obi212 OBI212 TC:ssl connected
Jan 24 19:44:16 Obi212 OBI212 BASESSL:Server name not matching...accounts.google.com vs google.com
Jan 24 19:44:16 Obi212 OBI212 LHC:Server verification failed!
Jan 24 19:44:16 Obi212 OBI212 GAPI:verify server error
(I've attached the start-up logs)
After the restart, both SPs show as "Connecting to 216.239.36.145;Token Error".
@SteveInWA - Any thoughts?
jholme004:
My GV accounts started working randomly last night. This morning, Poly had sent me an emai that said:
Quote
We are working on our servers recently to improve the performance of our service. We have this KB article that is about issues that we are fixing https://www.poly.com/us/en/support/knowledge-base/kb-article-page?type=Troubleshooting__kav&lang=en_US&urlName=KB24053&t=All&k=
Your devices could be affected positively and now are working.
I’m guessing this meant this was an issue with ObiTalk? The KB doesnt quite address the GV issue, but it works.
SteveInWA:
Quote from: jholme004 on February 05, 2021, 08:21:21 pm
My GV accounts started working randomly last night. This morning, Poly had sent me an emai that said:
Quote
We are working on our servers recently to improve the performance of our service. We have this KB article that is about issues that we are fixing https://www.poly.com/us/en/support/knowledge-base/kb-article-page?type=Troubleshooting__kav&lang=en_US&urlName=KB24053&t=All&k=
Your devices could be affected positively and now are working.
I’m guessing this meant this was an issue with ObiTalk? The KB doesnt quite address the GV issue, but it works.
That KB article, and the status page, are the first useful (and encouraging) information we've seen in a very long time.
If you look at the status page. you'll see that they have made two recent upgrades, and they have another one planned for tomorrow (6 Feb). Hopefully, things will start to improve.
But more significant, is a new suggestion on how to deal with the issue. The grammar is poor, but the recommendation is: if it tells you that your code is being "sent to the server", during the 180 second countdown, but it seems to have failed (normally, it should only take a few seconds), then re-enter the same **5 xxxx code. Do not abort and start over to get a new xxxx code, unless it reaches the end of the countdown and tells you it failed. It's unclear, but repeatedly requesting new codes may just make things worse.
Navigation
[0] Message Index
[*] Previous page