OBiTALK Community

Region Specific Technical / Service Provider Support => North America - Including Google Voice, Skype, etc. => Topic started by: Marc on December 25, 2020, 07:00:21 PM

Title: GV appears to be down
Post by: Marc on December 25, 2020, 07:00:21 PM
For the past few hours I've been unable to make calls via GV.  I have 7 OBi devices across two networks.  Via OBitalk, they all appear to be connected to GV.  A combination of 200/212/2182s. But when making calls, I either get a server 500 error or it rings once then not again or it rings a few times with 5 to 10 seconds between rings and then becomes a busy signal.

All devices are exhibiting the same responses.  All devices have other VoIP services connected (callcentric/Voip.ms) and those SPs are working just fine.

I have tried delete the GV connections and reconnect, to no avail, although the process of adding GV to the devices does work.

Anyone else experiencing issues?

Thanks
Title: Re: GV appears to be down
Post by: Sheffield_Steve on December 25, 2020, 07:22:21 PM
It's working OK for me!
Title: Re: GV appears to be down
Post by: Taoman on December 25, 2020, 07:59:03 PM
Multiple OBi devices with 3 GV accounts all working fine.

Any chance you're being affected by the AT&T outage due to the explosion this morning in Nashville?
Title: Re: GV appears to be down
Post by: Marc on December 26, 2020, 10:48:23 AM
Quote from: Taoman on December 25, 2020, 07:59:03 PM
Multiple OBi devices with 3 GV accounts all working fine.

Any chance you're being affected by the AT&T outage due to the explosion this morning in Nashville?

I guess anything is possible.  I'm on the east coast and have Consolidated Communications as my ISP.  Many name changes since, but this area was originally an MCI area.

I'm still having the same problem today.  I guess it's something with my ISP since everything else appears to be working as intended.
Title: Re: GV appears to be down
Post by: Marc on December 26, 2020, 05:43:54 PM
Made no change... but this evening GV is working again.  Maybe it was the ATT outage.