GV and Sipgate dial plan

Support zone
tiger4020
Posts: 6
Joined: Wed Mar 07, 2012 9:42 am

GV and Sipgate dial plan

Post by tiger4020 » Wed Mar 07, 2012 9:47 am

Dear members,
i tried to search if any new dial plan is released.
I used to use this dial plan;

sys.GoogleVoiceCall("gvusername","gvpassword","sipgate#","#{req.URI.User}",".*",1)


I did not have any problems in making outgoing calls and receiving calls until August 2011.
I just connected my xlite and PAP adapter to start using it again but i just cannot dial out nor receive calls.

Please help me if the dial plan is changed or something.

Thank you in advance.

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Re: GV and Sipgate dial plan

Post by Aaron » Wed Mar 07, 2012 10:03 am

The sys.GoogleVoiceCall command should still work the same. Have you double checked that calls to your sipgate number are making it through to your sipsorcery account?

tiger4020
Posts: 6
Joined: Wed Mar 07, 2012 9:42 am

Re: GV and Sipgate dial plan

Post by tiger4020 » Wed Mar 07, 2012 10:07 am

How do i check that Aaron.

Thanks

tiger4020
Posts: 6
Joined: Wed Mar 07, 2012 9:42 am

Re: GV and Sipgate dial plan

Post by tiger4020 » Wed Mar 07, 2012 10:10 am

on X-Lite when i try to dial out it says "Temporarily Unavailable" in just one ring.

What i mean to say is. When i dial any number it would ring just once and "Temporarily Unavailable"

Thanks

carter
Posts: 14
Joined: Fri Feb 10, 2012 5:26 am

Re: GV and Sipgate dial plan

Post by carter » Wed Mar 07, 2012 11:43 am

It seems that more and more people are having problems with GV+SIPGate, which is not good.

For starters, test a few things (and before you do any of these, make sure Sipsorcery is registered on SIPGate sucessfully --- check "SIP Providers" status page)

1) Disable GV forwarding to SIPGate # but keep at least another forwarding #, use another phone to call your GV number, hear anything?
2) Enable GV forwarding to SIPGate # and disable other forwarding numbers, call again
3) Call DIRECTLY to SIPGate #...

If you have "Y" for 1) & 3) but "N" for 2), then you have a similar problem as mine
viewtopic.php?f=7&t=4006

If you have "N" for 1) or 3), then it's a different thing, check your GV or SIPGate setup.

tiger4020
Posts: 6
Joined: Wed Mar 07, 2012 9:42 am

Re: GV and Sipgate dial plan

Post by tiger4020 » Wed Mar 07, 2012 6:57 pm

hey carter thanks for the checklist. i followed it.. well my incoming calls are working now. but i still cannot make any outgoing calls. please help.

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Re: GV and Sipgate dial plan

Post by Aaron » Thu Mar 08, 2012 9:30 am

In order to give us some more information to help you with can you login to the Silverlight portal at http://www.sipsorcery.com/mainsite/Home/Portal, go to the Console tab, click connect and then try your outgoing call. You should get a bunch of log messages that you can post up here.

tiger4020
Posts: 6
Joined: Wed Mar 07, 2012 9:42 am

Re: GV and Sipgate dial plan

Post by tiger4020 » Thu Mar 08, 2012 9:46 am

@Aaron here it is.

Thanks
Monitor 09:43:14:994: basetype=console, ipaddress=*, user=xxx, event=*, request=*, serveripaddress=*, server=*, regex=.*.
Registrar 09:44:10:027 sip1(1924): Authentication required for xxx@sipsorcery.com from tcp:117.204.133.80:57816.
BindingInProgress 09:44:25:496 sip1(1924): New binding request for xxx@sipsorcery.com from tcp:117.204.133.80:57816, expiry requested 3600s granted 3600s.
RegisterSuccess 09:44:25:527 sip1(1924): Registration successful for xxx@sipsorcery.com from tcp:117.204.133.80:57816, binding sip:xxx@192.168.0.195:58222;expiry=3600.
BindingExpired 09:44:26:074 sip1(1924): Binding expired by client for xxx@sipsorcery.com from tcp:117.204.133.80:57816.
BindingInProgress 09:44:26:636 sip1(1924): New binding request for xxx@sipsorcery.com from tcp:117.204.133.80:57816, expiry requested 3600s granted 3600s.
RegisterSuccess 09:44:26:683 sip1(1924): Registration successful for xxx@sipsorcery.com from tcp:117.204.133.80:57816, binding sip:xxx@117.204.133.80:57816;expiry=3600.
DialPlan 09:45:00:418 sip1(2168): New call from tcp:117.204.133.80:57816 successfully authenticated by digest.
DialPlan 09:45:00:434 sip1(2168): Using dialplan default for Out call to sip:18006927753@sipsorcery.com.
NewCall 09:45:00:434 sip1(2168): Executing script dial plan for call to 18006927753.
DialPlan 09:45:00:543 sip1(2168): SDP on GoogleVoiceCall call had RTP socket mangled from 192.168.0.195:23502 to 117.204.133.80:23502.
DialPlan 09:45:00:559 sip1(2168): UAS call progressing with Ringing.
DialPlan 09:45:00:559 sip1(2168): Logging into google.com for xxx@gmail.com.
DialPlan 09:45:00:793 sip1(2168): Google Voice pre-login page loaded successfully.
DialPlan 09:45:00:840 sip1(2168): GALX key LKMSN8nIrxk successfully retrieved.
DialPlan 09:45:01:871 sip1(2168): Google Voice home page loaded successfully.
DialPlan 09:45:01:918 sip1(2168): Exception on GoogleVoiceCall. Could not find _rnr_se key on your Google Voice account page, callback cannot proceed.
DialPlan 09:45:01:918 sip1(2168): Dialplan cleanup for xxx.
DialPlan 09:45:02:403 sip1(2168): Dial plan execution completed without answering and with no last failure status.
DialPlan 09:45:02:403 sip1(2168): UAS call failed with a response status of 480.
DialPlan 09:45:12:075 sip1(2168): New call from tcp:117.204.133.80:57816 successfully authenticated by digest.
DialPlan 09:45:12:090 sip1(2168): Using dialplan default for Out call to sip:18006927753@sipsorcery.com.
NewCall 09:45:12:090 sip1(2168): Executing script dial plan for call to 18006927753.
DialPlan 09:45:12:122 sip1(2168): SDP on GoogleVoiceCall call had RTP socket mangled from 192.168.0.195:39620 to 117.204.133.80:39620.
DialPlan 09:45:12:122 sip1(2168): UAS call progressing with Ringing.
DialPlan 09:45:12:122 sip1(2168): Logging into google.com for xxx@gmail.com.
DialPlan 09:45:12:184 sip1(2168): Google Voice pre-login page loaded successfully.
DialPlan 09:45:12:215 sip1(2168): GALX key yyXqyXs34Hs successfully retrieved.
DialPlan 09:45:12:981 sip1(2168): Google Voice home page loaded successfully.
DialPlan 09:45:13:012 sip1(2168): Exception on GoogleVoiceCall. Could not find _rnr_se key on your Google Voice account page, callback cannot proceed.
DialPlan 09:45:13:012 sip1(2168): Dialplan cleanup for xxx.
DialPlan 09:45:13:434 sip1(2168): Dial plan execution completed without answering and with no last failure status.
DialPlan 09:45:13:434 sip1(2168): UAS call failed with a response status of 480.
Last edited by tiger4020 on Sun Mar 11, 2012 4:10 am, edited 1 time in total.

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Re: GV and Sipgate dial plan

Post by Aaron » Thu Mar 08, 2012 9:53 am

The problem is the standard rnr_key problem that affects a lot of people.

Exception on GoogleVoiceCall. Could not find _rnr_se key on your Google Voice account page, callback cannot proceed.

For some reason some Google Voice accounts stop working with the mechanism sipsorcery uses to initiate calls most likely something to do with Google's security mechanisms.

You could try setting up a new Google Voice account and see if that works.

tiger4020
Posts: 6
Joined: Wed Mar 07, 2012 9:42 am

Re: GV and Sipgate dial plan

Post by tiger4020 » Sun Mar 11, 2012 3:42 am

Thanks Aaron for the analysis.
Is there no way out of this? other than setting up a new account..

Post Reply