ALERT GV: The Sky Has Fallen... Really

[shetu]

Looks like Google Voice GVSIP is dead again this morning.Trunks register but all calls in and out fail. Probably time to find a reputable provider.

My 3 of 2 trunks incomeing and outgoing works good. One of them incomeing not working correctly. Sometime incomeing call hits pbx sometime not.

 

[wardmundy]

Looks to have been a momentary hiccup.

 

[kdthomas]

I've been noticing since mid-day yesterday that mine will show registered, but "not available". Outbound calls will fail, while inbound calls will sometimes make it through. Sometimes its all three numbers, and others it will just be one. The trunks will show offline about 7-10 times in an hour and come back. So it's totally unstable at this point.

 

[wardmundy]

I've been noticing since mid-day yesterday that mine will show registered, but "not available". Outbound calls will fail, while inbound calls will sometimes make it through. Sometimes its all three numbers, and others it will just be one. The trunks will show offline about 7-10 times in an hour and come back. So it's totally unstable at this point.

Same thing I was seeing. Thanks.

 

[chris_c_]

@kdthomas
By any chance are your Fb phone numbers or your pbx server IP address located in the nearby geographical area of @wardmundy if they’re correlated then there’s likely work going on at the google data center serving you.

 

[kdthomas]

@kdthomas
By any chance are your Fb phone numbers or your pbx server IP address located in the nearby geographical area of @wardmundy if they’re correlated then there’s likely work going on at the google data center serving you.

I'm in California with California GV numbers. I think Ward is in South Carolina.

 

[kdthomas]

Knock on wood, but my GV trunks have all been 100% up today. Hopefully Google is done doing whatever they were doing and leave us alone for a bit.

 

[shetu]

Knock on wood, but my GV trunks have all been 100% up today. Hopefully Google is done doing whatever they were doing and leave us alone for a bit.

What is your pbx version?

 

[kdthomas]

Incredible PBX/Fax 13-13.7, but unfortunately I spoke too soon. Seems like it's now back to the up and down every 15 minutes.

 

[shetu]

Same Here (Ubuntu 18.04). May be we wait for stable version.

 

[kdthomas]

Same Here (Ubuntu 18.04). May be we wait for stable version.

It's not an issue with the platform, it's on Googles end.

 

[shetu]

How to find google voice downtime from log file?

 

[steve54301]

How to find google voice downtime from log file?

I don't think that is logged natively.

You can log it by easily modifying a bash script that Vladimir posted here:
https://pbxinaflash.com/community/t...s-to-fix-the-problem.23083/page-2#post-138722

 

[ariban]

Same thing I was seeing. Thanks.

For some reason I have one machine that I installed right after the new Google Voice sip protocol came out and on this machine incoming calls work about 99.9% of the time and outgoing will not work unless I do an End Portal restart it's using an older version of the gvsipnaf.
would you like to have access to my machine maybe you can figure out why this one works compared to all new installs I make the don't work not for incoming or outgoing.
Maybe there's something you can figure out that might help everybody I am not an expert and I don't know how to figure these things out but maybe you'll be useful for you and I'll be more than happy to give you root access to the server as I wouldn't have this program without you so you could have full access to it

 

[windpoint]

Incredible PBX 13-13 with GVSIP-NAF for CentOS/SL 6 (beta)


For instructions on obtaining refresh_tokens for your Google Voice trunks, go here. For instructions on creating routes, go here.

Add GVSIP trunks by logging into your server as root and running /root/gvsip-naf/install-gvsip. It's a 10-second install per Google Voice trunk. You'll need your refresh_token and phone number for each GVSIP trunk you wish to add.

Delete existing GVSIP trunks (#1 through #9) by running /root/gvsip-naf/del-trunk. If you need to delete trunks higher than 9, edit del-trunk and add new sections for the number of trunks you have. Always delete trunks in reverse order. We don't recommend deleting GVSIP1, but it works.

Add an Inbound Route for each of your trunks using the 10-digit DID of the GV trunk and specifying a destination for the incoming calls. Except in Enchilada version, inbound calls won't be processed until you add an incoming route.

Add an Outbound Route for each trunk (named GVSIP1 through GVSIPn. Outbound calls will fail until you add an outbound route for the trunk.

To refresh the patched version of Asterisk, copy /etc/asterisk/pjsip_custom.conf to a safe place, delete the contents of pjsip_custom.conf, rerun the installer, and then copy your version of pjsip_custom.conf back to /etc/asterisk and restart Asterisk. That way you won't lose any of your previously configured GVSIP trunks.

Is there a way get around of this? I accidentally deleted the gvsip1 and now it wont let me remove the others.
Thank you

 

[wardmundy]

Is there a way get around of this? I accidentally deleted the gvsip1 and now it wont let me remove the others.
Thank you

Simple way is just to delete /etc/asterisk/pjsip_custom.conf and restart Asterisk: amportal restart.