GV down? (Stuck "Connecting to 216.239.36.144")

<< < (4/5) > >>

sir_rob:
There are at least two threads on this now, and so far I have no solution for my Obi202's (re-authenticate, reboot, unplug for 5 minutes, etc.).  I am guessing that there is a partial outage right now.

Marc:
That was short lived..  All 6 of my Obi devices are down again.. Connecting to 216.239.36.144

I'm guess there's a communication glitch between Obi servers and GV servers.

OBiSupport:
OBi devices registered to Google Voice services may be experiencing intermittent connection issues.  There is no need to restart/reboot the OBi device.  Service will restore on its own. 

OBiTALK device management services run completely independent from the voice services configured on the device. And except for first time configuration, said voice services are in no way dependent on OBiTALK service.

Marc:
So first, thank you for the update.

Second, so am I to understand that when in Obitalk it says for GV status "Connecting to 216..." that it doesn't mean Obi servers are connecting, but that the device itself it attempting to connect?  I knew that was the case for typical SIP services, but I was under the impression that Obi and GV had a special arrangement and since their SIP service isn't available to consumers outside using Obi devices, that there must be some sort of phone home connection.  No?

Thank you,
Marc


Quote from: OBiSupport on October 10, 2019, 10:51:49 am

OBi devices registered to Google Voice services may be experiencing intermittent connection issues.  There is no need to restart/reboot the OBi device.  Service will restore on its own. 

OBiTALK device management services run completely independent from the voice services configured on the device. And except for first time configuration, said voice services are in no way dependent on OBiTALK service.

SteveInWA:
Quote from: Marc on October 10, 2019, 11:36:16 am

So first, thank you for the update.

Second, so am I to understand that when in Obitalk it says for GV status "Connecting to 216..." that it doesn't mean Obi servers are connecting, but that the device itself it attempting to connect?  I knew that was the case for typical SIP services, but I was under the impression that Obi and GV had a special arrangement and since their SIP service isn't available to consumers outside using Obi devices, that there must be some sort of phone home connection.  No?

Thank you,
Marc


Quote from: OBiSupport on October 10, 2019, 10:51:49 am

OBi devices registered to Google Voice services may be experiencing intermittent connection issues.  There is no need to restart/reboot the OBi device.  Service will restore on its own. 

OBiTALK device management services run completely independent from the voice services configured on the device. And except for first time configuration, said voice services are in no way dependent on OBiTALK service.



It means that your OBiTALK device is trying (and failing) to connect to Google Voice.  It does not mean that it is trying to connect to OBiTALK.

Navigation

[0] Message Index

[#] Next page

[*] Previous page