token error
SteveInWA:
Quote from: PusBucket on June 13, 2021, 11:25:11 am
This didn't achieve even a temporary fix, for me.
Quote from: GeeObi on June 13, 2021, 09:10:29 am
The fix is as follows:
Use Obi expert and under Service Providers, ITSP, General:
STUNEnable checked (you must uncheck the box to the right first)
STUNserver stun.l.google.com
X_STUNServerPort 19302
For gawd's sake; ignore all alleged fixes by random users on the Internet. None of them will solve the problem, which is on the Poly/Google interface backend. You can't fix this yourself.
SteveInWA:
Quote from: TheFoxRocks on June 13, 2021, 11:21:50 am
Quote from: SteveInWA on June 12, 2021, 11:13:37 am
I reported this to Google Voice engineering staff yesterday afternoon. They have identified the problem and they are working with Poly to resolve it.
To be clear: no action on your part is necessary nor will fix it at this time. This outage is a good reminder that nobody should depend on Google Voice as their sole source of telephone service, and you can configure your OBiTALK device to use one or more other service providers, such as Callcentric or voip.ms.
I'm sorry, but I don't have any status update to report, since my Google contacts are off for the weekend. Nonetheless, it's safe to assume that they are working on it, and I will pass along any news I can get.
Hey Steve,
You have my thanks for reaching out on behalf of the community. Please know, that there are people who are thankful for people like yourself. I think people fail to appreciate after buying their OBi (or other) device that they are getting completely free service through Google Voice and expect that free service to always be perfect. I was only relying on Google Voice before. I am using mine as a business phone, I will probably follow your CallCentric guide later today so I have a viable backup. Thanks again!
Thanks for your kind words. Yeah, I have been spending most of the weekend on this, between this forum, the official Google Voice Help Community, Reddit, and chats with Google Voice staff.
As always, the "tough love" statement: Consumer Google Voice has never been intended nor recommended for business use. This a perfect example of why. Any pittance in phone bills saved by using consumer GV is quickly offset by loss of business or reputation when clients/customers can't reach you. Google does have a business-class, paid service (https://cloud.google.com/voice/) or use a reliable, proven SIP ITSP such as Callcentric, voip.ms, etc.
hkap:
My Obi200 has been having this issue since last few days.
Just for the sake of, i deleted my device from obitalk.com and reconfigured it. I am now connected to google voice service. I am not too sure if this will work for all or if this is just a temporary resolution, but would be worth a try.
Here are some high level steps:
1) Log on to ObiTalk.com
2) Click on Device Configuration on the left side.
3) Click Delete Device in Device Information tab.
4) Once the device is deleted, click Add Device.
5) Follow prompts to add obi device and configure GV service.
I am hoping this resolves the issue permanently. I will post again if my service status changes.
rpress:
A quick packet sniff shows that my Obi202 during TLS key exchange is replying "Unknown CA" to 142.250.81.205 (one of the IPs for accounts.google.com).
It looks like it's possible to install more CA certs into the Obi202 but not quite sure how to upload them.
calt:
I just tested and things are now working fine again (Los Angeles Area).
Thanks for the fix!
Navigation
[0] Message Index
[#] Next page
[*] Previous page