Connect Failed: 403 Forbidden;Token Error
jholme004:
Sadly, it is back to showing: "Connecting to 216.239.36.145;Token Error" (Still no the new account). Yes, I could make/receive calls via the Obi and the web when I sent my last reply.
I may have to keep my fingers crossed the Poly will have a solution (although I am NOT holding my breath).
I'm at whit's end on this one!
SteveInWA:
Help me by clarifying the current situation. You have two GV DIDs. Did you transfer one or both of them to two new Google accounts? If so, did they work on the new Google accounts? Did you transfer either or both of them back?
In other words, if you transferred one of the numbers to a new account, did the number work on that account? If so, did it then fail later? Please be very detailed in your description so we can try to isolate the issue.
jholme004:
Ok...
I have two GV accounts - out old home account from a different state (line1) and an office line (line 2). Initially, I had these on an Obi202, FXS 1 & 2 respectively, and have since moved to a 212, since I have a landline for home service.
Approximately two weeks ago, both went to showing “Connecting to 216.239.36.145;Token Error“. Despite the trouble shooting in the posts above, they would work for about 15 minutes when deleted and re-added then back to “Connecting to 216.239.36.145;Token Error“ and after several hours would change to "registration not required"
I followed the instructions on transferring the number. I have a third gmail.com account I use for my browser at work (We use MS Office for everything - this is NOT a GSUITE account, just a seperate account for syncing my browser across multiple work devices). Out of my irrational fear of losing the home number if something went wrong, I decided to transfer the office line, line2.
Everything went smoothly, and I could make and receive calls via the web in my "work" gmail account. I did the transfer by logging into my Line 2 account using incognito mode in Chrome, and logging into my "work" account using MS Edge, the chromium based version, "inPrivate" mode. After thr transfer was complete I did log out then log back in to each account to verify that the number no longer appeared on the "line 2" account and it did appear on the "work" account. I then re-added my factory reset Obi202 to ObiTalk then added the "work" google account (which now has my office line attached to it) to the Obi202. It was "connected" for a couple of hours. During that time, I placed and received several calls. When I noticed ObiTalk was stating “Connecting to 216.239.36.145;Token Error“ again, I got the ""no response from the service provider" intercept when attempting outbound calls and inbound calls never rang the Obi. Like before, I can make/receive calls via the webUI and smartphone app. When writing this, I noticed it has changed to "Registration not Required"
So, In short and to directly answer your questions (I was trying to be detailed above):
-I only transferred One DID (Line2/Office)
-It worked on the new account via Web UI and Obi
-It eventually stopped working on the Obi, with the same symptoms I previously had (works briefly
then “Connecting to 216.239.36.145;Token Error“ then eventually turns to "Registration not Required")
-I did not transfer it back, as my assumption would be we would have the same results.
- Yes, I am using two different Obi's. This was to verify it wasn't an issue with one of them
(Hardware/Firmware/configuration). I am doing all my testing on my Obi202. The GV accounts are NOT registered to the 212, nor do the GV accounts have permissions for the Obi212 anymore.
I'll try transferring the home/Line1 number to a new account and transferring the office/line2 back to its original tomorrow. After the above today, I am not optimistic we will see different results.
Let me know if I inadvertently left any holes.
Thanks again Steve.
jholme004:
So today, I transferred the Office/Line 2 number BACK to its original account. As before, it said "Connected" for approximately 15 minutes, then changed to “Connecting to 216.239.36.145;Token Error“.
I started thinking - I checked using two different Obis to be sure it wasn't a device issue; this is happening to two different gmail accounts and we suspected a potential account issue, so we transferred the number. For S&G's, I decided to create a *NEW* gmail account (from scratch, using Chrome Incognito mode) then chose a *NEW* number. Before I moved on, I logged into ObiTalk in MS Edge and removed the the "Office/Line2" from my Obi202 (which at that point said "Registration not required"), then did a powercycle of the Obi Device. When it came back online, I went back into edge and added the new GV number using my new GMail account. After a minute or so of "Connecting", it changed to "registration Not required". Calls to **9 222 222 222 are successful, so the Obi Device is online.
I haven't tried transferring the "Home/Line1" number, as at this point it seems futile, given 2 transfers of an existing and a brand new account yield the same results.
I'm starting to wonder if this may be a configuration issue on the ObiTalk side, along with their other issues?
jholme004:
For giggles, I added the "Home/Line1" and the "Office/Line2" accounts to the Obi202 and both went from "Connecting" to "registration not required".
Now I have SP1 (New) and SP2 (Office/Line2 xferred back to the original account) on the Obi202 and SP1 (Home/Line1) on the Obi212 saying "Registration Not Required". SP3 (Bulkvs) and SP4 (Anveo) on the 212 are showing "Registered" and both have tested working properly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page