token error
Taoman:
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
The purpose of a STUN server is to allow the local client to traverse your local NAT successfully. The current issue some people are experiencing is not related to any STUN setting.
Your OBi device may have connected after making a STUN setting change but I guarantee it was purely coincidental.
Taoman:
The following was recently posted on Reddit supposedly by a Google Voice engineer:
Quote
GV eng here: There is some kind of OAuth refresh token problem with some devices. We haven't been able to track it down as of yet. It seems to be only affecting some OBiTALK devices, but it's unclear why because neither us nor Polycom have rolled anything out that would do this, not that we know of at least. We are continuing to investigate, but Google has no access to the devices so there's not a lot to go on. If you have paid support from Polycom, please open a support case with them and give them the serial number of the device that is malfunctioning so they can pull its system logs.
https://www.reddit.com/r/Googlevoice/comments/nxubgn/google_voice_token_error_message_on_poly_obitalk/h1m05vh?utm_source=share&utm_medium=web2x&context=3
railpass:
Just ported my Google Voice number to a different Service Provider (Anveo). Didn't realize how dependent I'd become on the VoIP line. Hard to complain given that GV was free.
Jasmine10:
You are 100% correct, obihai.sip.google.com is just SIP realm name: http://docs.intenogroup.com/v312/en/glossary/s/sip_realm#:~:text=A%20SIP%20realm%20is%20a,as%20a%20the%20SIP%20domain.
216.239.36.145 is the real SIP registration server: obihai.telephony.goog
But before SIP registration, it needs to get OAuth token from another Google server: www.googleapis.com
If changing DNS works, it may be related to the fact that different DNS servers may return different IPs for this server.
Can anyone post the dns resolution output:
In Mac computer:
# Get answer from your ISP DNS server
dig www.googelapis.com
# Get answer from specific DNS server
dig @1.1.1.1 www.googleapis.com
Please also include your city/state.
Quote from: Taoman on June 13, 2021, 11:36:39 am
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.
lrosenman:
I got an ONLINE note from Obitalk at 13:45 CDT 2021-06-13. Thanks, @SteveInWa for reaching out to Google!
Navigation
[0] Message Index
[#] Next page
[*] Previous page