token error
Moonwalker:
Quote from: SteveInWA on June 25, 2021, 06:54:53 pm
This is a digital certificate expiration, which is standard practice across the Internet. All digital certificates have an expiry date, and that's what my announcement was about.
All I can confirm is that they are definitely working on it...up to them.
Here’s the announcement: http://www.obitalk.com/forum/index.php?topic=18430.0
In the meantime, it appears the “fix” for users is to delete their google credentials for whichever SP(1,2 or whatever) is producing the problem, then reenter them as at the first time it was set up. Hopefully that will stop the errors mentioned in this thread. No guarantees.
I’d like to extend a HUGE truckload of thanks for SteveInWA’s tireless efforts in helping us all get to the bottom of this. Thanks to you (and some nameless others whom I’d also like to thank - please pass the word), my phone is now working again, and has been for a few weeks, and I’m just waiting for the firmware update from Poly.
SteveInWA, I hope you still have some hair left. 😳😬😎
SteveInWA:
Quote from: Moonwalker on June 30, 2021, 11:10:48 am
Quote from: SteveInWA on June 25, 2021, 06:54:53 pm
This is a digital certificate expiration, which is standard practice across the Internet. All digital certificates have an expiry date, and that's what my announcement was about.
All I can confirm is that they are definitely working on it...up to them.
Here’s the announcement: http://www.obitalk.com/forum/index.php?topic=18430.0
In the meantime, it appears the “fix” for users is to delete their google credentials for whichever SP(1,2 or whatever) is producing the problem, then reenter them as at the first time it was set up. Hopefully that will stop the errors mentioned in this thread. No guarantees.
Thank you for you kind comments!
Actually, no: for the vast majority of users who were impacted by the outage, the problem was fixed remotely, and no user action is required. If a user made changes to their OBi configuration, they may have messed up their device's ability to re-authenticate to Google Voice. In that case, then yes, you would need to follow the bulleted steps in my post, here: https://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076
holtdw01:
I have followed every step 1) set DNS 2) delete and re-add device, 3) uncheck 0auth, and still get the "No registration required" on the Obitalk dashboard. In the Obi device on SP1 I get "Connect Failed: No Response (server=216.239.36.145; retry in 45s)". I have read the chatter on this forum nauseum but have not been able to identify a verified and supported solution. How frustrating. This has every sign of being a authentication problem. Looks like I will have port my number to a pay service provider again after spending four years using googlevoice through Obihia.
SteveInWA:
Quote from: holtdw01 on July 12, 2021, 11:43:19 am
I have followed every step 1) set DNS 2) delete and re-add device, 3) uncheck 0auth, and still get the "No registration required" on the Obitalk dashboard. In the Obi device on SP1 I get "Connect Failed: No Response (server=216.239.36.145; retry in 45s)". I have read the chatter on this forum nauseum but have not been able to identify a verified and supported solution. How frustrating. This has every sign of being a authentication problem. Looks like I will have port my number to a pay service provider again after spending four years using googlevoice through Obihia.
Please don't post in this thread. Your question was already addressed elsewhere in this forum.
http://www.obitalk.com/forum/index.php?topic=18338.msg109260#msg109260
lrosenman:
Based on the banner now up on obitalk.com, the new firmware is out and will be auto-updated on 8/5/2021 at 17:00 PDT. You can also do the update manually, follow the instructions linked from the banner. I updated my Obi202, no issues, and it connected back up.
Navigation
[0] Message Index
[#] Next page
[*] Previous page