Connect Failed: No Response on multiple Google Voice / Obi 508 Devices
torchredraider:
Update 3/12/2019
Obi202 offline and unable to connect to GV as of 1:15am CT.
Began diagnosis at 1:00pm, same day.
Multiple reboots via web interface and re-saving of GV credentials did not improve connection.
Replaced c.telephony.goog with obihai.telephony.goog by re-checking OBiTALK Settings in ITSP Profile A SIP menu and clicking save.
Device reconnected after 30 seconds.
Reference
dig c.telephony.goog and dig obihai.telephony.goog returned same IP address (216.239.36.144), unsure of cause
Taoman:
Quote from: torchredraider on March 12, 2019, 01:45:47 pm
Replaced c.telephony.goog with obihai.telephony.goog by re-checking OBiTALK Settings in ITSP Profile A SIP menu and clicking save.
Device reconnected after 30 seconds.
Reference
dig c.telephony.goog and dig obihai.telephony.goog returned same IP address (216.239.36.144), unsure of cause
Thanks. Your post helped me fix the same problem.
I had 2 OBi 200s connecting to the same GV account. One worked and the other gave the error message about being unable to connect to 216.239.36.144. I checked the config on the one that wasn't working and for some reason I had c.telephony.goog listed instead of obihai.telephony.goog. I made the switch and it connected immediately.
SteveInWA:
I can't speak to how the OBiTALK portal configures Google Voice on 508s, but on the 200/202 configuration, obihai.sip.google.com is automatically configured, and is the correct value. During the beta, there were a couple of other values used, but this is now the "production" value.
Unrelated to that, although 508s can use Google Voice, it is not recommended. The free, consumer version of Google Voice is neither intended nor supported for business use. Google can and does shut down accounts for abuse if it becomes aware of calling patterns associated with call center or telesales, or any other sort of business use that involves high-volume outbound calling. If that happens, you lose all of your Google Voice phone numbers. Now that Google has a paid, commercial version of Google Voice for G Suite customers, it's a good bet that they will step up enforcement.
It's best to use a 508 with one or more paid ITSPs.
MiKo:
Quote from: torchredraider on March 12, 2019, 01:45:47 pm
Update 3/12/2019
Obi202 offline and unable to connect to GV as of 1:15am CT.
Began diagnosis at 1:00pm, same day.
Multiple reboots via web interface and re-saving of GV credentials did not improve connection.
Replaced c.telephony.goog with obihai.telephony.goog by re-checking OBiTALK Settings in ITSP Profile A SIP menu and clicking save.
Device reconnected after 30 seconds.
Reference
dig c.telephony.goog and dig obihai.telephony.goog returned same IP address (216.239.36.144), unsure of cause
Thanks for this, my disconnect was resolved following this post.
BobTeatow:
Having similar problem on my OBI202 device with 2 different google voice accounts set up as SP1 and SP2 -- was working fine for I think, more than a year...
Now in last coupl'o'weeks the connection to google is going on and off a few times a day, seemingly random -- if I don't notice it, I get auto-email warnings like this from no-reply@obitalk.com :
"Service Offline Alert -- OBi Device (5004xxxxx) is Not Registered
Your voice service is not registering. This could be due to a temporary service disruption or an incorrect login credential.
In most cases, reconfiguring the voice service with the proper login credential will resolve the issue. "
I checked that obihai.telephony.goog is set. So that's not the problem...
Help!
Navigation
[0] Message Index
[*] Previous page