token error
TheFoxRocks:
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!
PusBucket:
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
calt:
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
NO fix!
I tried these changes via OBI expert and via the built in UI of the device (local IP). Also rebooted after each change.
Still exactly the same token error!
Will undo these changes.
Taoman:
Quote from: jccpa on June 13, 2021, 08:08:17 am
NSLOOKUP cannot find obihai.sip.google.com or sip.google.com using 8.8.8.8 or 8.8.4.4 or 1.1.1.1 or ns1.google.com
*** dns.google can't find sip.google.com: Non-existent domain
So either Google shut down SIP of google voice, or the A Record was removed on purpose or by attack.
In any case, until the A record for sip.google.com is restored, no obihai.sip.google.com, no GV connection.
obihai.sip.google.com has never had an A record or SRV record. It doesn't matter. Whenever there is an OutboundProxy setting it overrides any Proxy server setting.
All SIP requests go to obihai.telephony.goog, not obihai.sip.google.com. From there it gets redirected as needed.
Look at many of the error messages people are getting:"Connecting to 216.239.36.145;Token Error"
And what does 216.239.36.145 resolve to? The OutboundProxy setting which is obihai.telephony.goog.
You're wasting your time worrying about obihai.sip.google.com.
Mickey613:
Quote from: ppan on June 13, 2021, 11:16:21 am
Quote from: GeeObi on June 13, 2021, 11:01:31 am
It should look like this:
It looks like that (but slightly different layout for me). I unchecked STUNEnable since it didn't help. See image here:
https://i.gyazo.com/ac54496c7b678553a3cbbb70beb65aa0.png
That's exactly the settings I had BEFORE making any changes. I'm still down with or without this setting change.
Navigation
[0] Message Index
[#] Next page
[*] Previous page