Page 6 of 8

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 1:50 am
by bjmsam
Same error here, and Emails from Google about signing in from a new device.

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 7:30 am
by Aaron
Oops I somehow managed to deploy the fix incorrectly, only the secondary application server had the update. I've fixed it now, please try the GV calls again.

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 8:16 am
by carter
That explained my previous puzzle! Aaron, you nailed it this time.
I just did another test, 3 out of 3 worked, therefore I consider the problem fixed :D

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 8:43 am
by bjmsam
Same success here. THANK YOU!!!

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 12:32 pm
by will40
Nice job Aaron!!

I am back up and running again.

Thank you

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 2:39 pm
by hanke
Calls are working on my end as well and wish to express my thanks to the individuals in getting the Google Voice service working again.

Thank you

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 3:47 pm
by azrobert
I'm still getting the RNR error. I entered an invalid Google userid and password into my dialplan to see what would happen and I received the same messages. Why? See below.

I haven't used the GV function in a long time. When it failed a couple weeks ago, I checked the Google account activity and the sign in from SipSorcery was unknown and blocked. I marked the entry as "mine" and received a message that activity will still be logged for 2 weeks. I just checked activity again and there is an entry from yesterday saying SipSorcery was blocked, but also said "You have marked this activity as yours". I don't know if Google is still blocking SipSorcery and console log is no help because I get the same messages with invalid sign in information. Please help! Thank you

Code: Select all

DialPlan 14:47:30:079 sip1(1504): Logging into google.com for invalidID123.
DialPlan 14:47:30:220 sip1(1504): Google Voice pre-login page loaded successfully.
DialPlan 14:47:30:235 sip1(1504): GALX key WOqIQYRf2hw successfully retrieved.
DialPlan 14:47:30:235 sip1(1504): gxf key AFoagUWXgAxr21cv1tQYkEGyuYxpjbZqiA:1490021250254 successfully retrieved.
DialPlan 14:47:31:281 sip1(1504): https://accounts.google.com/ServiceLogin?service=grandcentral&passive=1209600&continue=https:%2F%2Fwww.google.com%2Fvoice%3Fgsessionid%3Dz05F3r-xWUp0Oqm2_CHEI4bm_7tZ9AUq&followup=https:%2F%2Fwww.google.com%2Fvoice%3Fgsessionid%3Dz05F3r-xWUp0Oqm2_CHEI4bm_7tZ9AUq&ltmpl=open Google Voice home page loaded successfully.
DialPlan 14:47:31:296 sip1(1504): Could not find _rnr_se key on your Google Voice account page, callback cannot proceed.
DialPlan 14:47:31:296 sip1(1504): Exception on GoogleVoiceCall. Could not find _rnr_se key on your Google Voice account page, callback cannot proceed.
DialPlan 14:47:31:296 sip1(1504): Dialplan cleanup for azrobert.
DialPlan 14:47:31:312 sip1(1504): Dial plan execution completed without answering and with no last failure status.
DialPlan 14:47:31:312 sip1(1504): Call failed with a failure status of TemporarilyUnavailable and .
DialPlan 14:47:31:312 sip1(1504): UAS call failed with a response status of 480.

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 6:30 pm
by mobilebone
azrobert wrote:I'm still getting the RNR error. I entered an invalid Google userid and password into my dialplan to see what would happen and I received the same messages. Why? See below.

I haven't used the GV function in a long time. When it failed a couple weeks ago, I checked the Google account activity and the sign in from SipSorcery was unknown and blocked. I marked the entry as "mine" and received a message that activity will still be logged for 2 weeks. I just checked activity again and there is an entry from yesterday saying SipSorcery was blocked, but also said "You have marked this activity as yours". I don't know if Google is still blocking SipSorcery and console log is no help because I get the same messages with invalid sign in information. Please help! Thank you

Code: Select all

DialPlan 14:47:30:079 sip1(1504): Logging into google.com for invalidID123.
DialPlan 14:47:30:220 sip1(1504): Google Voice pre-login page loaded successfully.
DialPlan 14:47:30:235 sip1(1504): GALX key WOqIQYRf2hw successfully retrieved.
DialPlan 14:47:30:235 sip1(1504): gxf key AFoagUWXgAxr21cv1tQYkEGyuYxpjbZqiA:1490021250254 successfully retrieved.
DialPlan 14:47:31:281 sip1(1504): https://accounts.google.com/ServiceLogin?service=grandcentral&passive=1209600&continue=https:%2F%2Fwww.google.com%2Fvoice%3Fgsessionid%3Dz05F3r-xWUp0Oqm2_CHEI4bm_7tZ9AUq&followup=https:%2F%2Fwww.google.com%2Fvoice%3Fgsessionid%3Dz05F3r-xWUp0Oqm2_CHEI4bm_7tZ9AUq&ltmpl=open Google Voice home page loaded successfully.
DialPlan 14:47:31:296 sip1(1504): Could not find _rnr_se key on your Google Voice account page, callback cannot proceed.
DialPlan 14:47:31:296 sip1(1504): Exception on GoogleVoiceCall. Could not find _rnr_se key on your Google Voice account page, callback cannot proceed.
DialPlan 14:47:31:296 sip1(1504): Dialplan cleanup for azrobert.
DialPlan 14:47:31:312 sip1(1504): Dial plan execution completed without answering and with no last failure status.
DialPlan 14:47:31:312 sip1(1504): Call failed with a failure status of TemporarilyUnavailable and .
DialPlan 14:47:31:312 sip1(1504): UAS call failed with a response status of 480.
Forget about the rnr key. Put the password back in the dial plan.

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 7:22 pm
by azrobert
mobilebone wrote: Forget about the rnr key. Put the password back in the dial plan.
I am using the GV password.

Re: GV outgoing calls not connecting again

Posted: Mon Mar 20, 2017 8:13 pm
by dov
It's working for me now as well. Thanks Aaron.

@azrobert
The log you posted is implying there's something wrong with the username and/or password.

Make sure your dialplan is back to what it was before the problems began.