Google voice call back and incoming calls

Support zone
MrDoo
Posts: 23
Joined: Wed Apr 06, 2011 7:56 pm

Google voice call back and incoming calls

Postby MrDoo » Fri Oct 21, 2016 2:38 pm

If I use a DID pointing to Sipsorcery for the GV call back number, can I still use the same DID for regular incoming calls? That is, will the dialplan be ignored for GV call backs, but used normally at other times?

I don't think there are any more free DID options that can be used with GV so I want to use the DID I have for both purposes.


Assuming I can use it for both, does the DID need to point to "user@sip.sipsorcery.com" or can it point to something like "trunk.user@sip.sorcery.com" and still be used for GV call back? I'd like to apply some specific call routing for this DID.

User avatar
Aaron
Site Admin
Posts: 4550
Joined: Thu Jul 12, 2007 12:13 am

Re: Google voice call back and incoming calls

Postby Aaron » Mon Oct 24, 2016 9:21 am

MrDoo wrote:If I use a DID pointing to Sipsorcery for the GV call back number, can I still use the same DID for regular incoming calls? That is, will the dialplan be ignored for GV call backs, but used normally at other times?
Yes that should work. When a GV call is made through sipsorcery it creates a task to watch for the incoming GV callback and then bridge it. If there is no task watching for the GV callback then it will just be treated the same as a normal incoming call.

MrDoo wrote:Assuming I can use it for both, does the DID need to point to "user@sip.sipsorcery.com" or can it point to something like "trunk.user@sip.sorcery.com" and still be used for GV call back? I'd like to apply some specific call routing for this DID.
The SIP URI you use will not affect the GV callback matching so you can use whichever format you like.

MrDoo
Posts: 23
Joined: Wed Apr 06, 2011 7:56 pm

Re: Google voice call back and incoming calls

Postby MrDoo » Mon Oct 24, 2016 9:19 pm

For some reason, the call back is not being recognized:

Code: Select all

DialPlan 21:10:43:892 sip1(8364): New call from tcp:24.114.91.40:44627 successfully authenticated by digest.
DialPlan 21:10:43:939 sip1(8364): Using dialplan Main for Out call to sip:6317918378@sipsorcery.com.
NewCall 21:10:43:970 sip1(8364): Executing script dial plan for call to 6317918378.
DialPlan 21:10:44:017 sip1(8364): ** Call from "User" <sip:username-acct@sipsorcery.com>;tag=1IlUrNzorWLRU5nRcGtRYT7kc-R.MPJS to 6317918378 **
DialPlan 21:10:44:017 sip1(8364): Local time: 10/24/2016 17:10
DialPlan 21:10:44:032 sip1(8364): Executing outbound dial plan
DialPlan 21:10:44:032 sip1(8364): Attempting to call 6317918378
DialPlan 21:10:44:032 sip1(8364): Caller name: User
DialPlan 21:10:44:032 sip1(8364): Call out using SIP account: 'username-acct'
DialPlan 21:10:44:048 sip1(8364): 6317918378 US area code; Use Google Voice
DialPlan 21:10:44:048 sip1(8364): SDP on GoogleVoiceCall call had public IP not mangled, RTP socket 25.218.116.243:4024.
DialPlan 21:10:44:048 sip1(8364): UAS call progressing with Ringing.
DialPlan 21:10:44:048 sip1(8364): Logging into google.com for gvuser@gmail.com.
DialPlan 21:10:44:188 sip1(8364): Google Voice pre-login page loaded successfully.
DialPlan 21:10:44:220 sip1(8364): GALX key 12345dtoBRg successfully retrieved.
DialPlan 21:10:44:220 sip1(8364): gxf key 12345UUv3zwkhOYTKVdqgs6H3G4BUza6Ng:1234543444152 successfully retrieved.
DialPlan 21:10:46:107 sip1(8364): Google Voice home page loaded successfully.
DialPlan 21:10:46:139 sip1(8364): Call key 123459D07/WUNMNIrJAU6BCrXqg= successfully retrieved for gvuser@gmail.com, proceeding with callback.
DialPlan 21:10:46:139 sip1(4608): SIP Proxy setting application server for next call to user username as udp:67.222.131.147:5070.
DialPlan 21:10:46:747 sip1(8364): Google Voice Call to 6317918378 initiated, callback #1212xxxxxxx, phone type 1, timeout 30s.
DialPlan 21:11:16:762 sip1(8364): Google Voice Call timed out waiting for callback.
DialPlan 21:11:16:933 sip1(8364): Google Voice Call to 6317918378 was successfully cancelled.
DialPlan 21:11:16:949 sip1(8364): ** Error: can't convert nil into Fixnum
DialPlan 21:11:16:949 sip1(8364): Dialplan cleanup for username.
DialPlan 21:11:17:230 sip1(8364): Dial plan execution completed without answering and with no last failure status.
DialPlan 21:11:17:230 sip1(8364): Call failed with a failure status of TemporarilyUnavailable and .
DialPlan 21:11:17:230 sip1(8364): UAS call failed with a response status of 480.



Regular incoming calls to the the DID seem to work as normal. The call back number is correct (I think). I tried both 212xxxxxxx and 1212xxxxxxx.

Any idea what I'm not doing right?

User avatar
Aaron
Site Admin
Posts: 4550
Joined: Thu Jul 12, 2007 12:13 am

Re: Google voice call back and incoming calls

Postby Aaron » Wed Oct 26, 2016 9:58 am

In that console trace the incoming call on your DID was not received at all. So it wasn't a problem with the callback not being matched to your outgoing GV call.

The first step is to make sure incoming calls on your DID do make it to the sipsorcery server on a standard incoming call, i.e. when you call your DID from your mobile of a PSTN line. If that works then try a GV call.

MrDoo
Posts: 23
Joined: Wed Apr 06, 2011 7:56 pm

Re: Google voice call back and incoming calls

Postby MrDoo » Wed Oct 26, 2016 3:08 pm

Yes, incoming calls do work fine and get routed to the desired SIP account:

Code: Select all

DialPlan 15:03:47:115 sip1(10028): Using dialplan default for In call to sip:trunk.ssuser@sip.sipsorcery.com.
NewCall 15:03:47:130 sip1(10028): Executing script dial plan for call to trunk.ssuser.
DialPlan 15:03:47:271 sip1(10028): ** Call from "2125553669" <sip:2125553669@44.114.41.159>;tag=as7eee93d3 to trunk.ssuser **
DialPlan 15:03:47:271 sip1(10028): Local time: 10/26/2016 11:03
DialPlan 15:03:47:380 sip1(10028): Commencing Dial with: ssuser-acct@local.
DialPlan 15:03:47:396 sip1(10028): Call leg is for local domain looking up bindings for ssuser-acct@sipsorcery.com for call leg ssuser-acct@local.
DialPlan 15:03:47:396 sip1(10028): 1 found for ssuser-acct@sipsorcery.com.
DialPlan 15:03:47:396 sip1(10028): ForkCall commencing call leg to sip:ssuser-acct@33.114.91.155:50515;transport=TLS;ob.
DialPlan 15:03:47:396 sip1(10028): SIPClientUserAgent Call using alternate outbound proxy of udp:67.222.131.147:5060.
DialPlan 15:03:47:396 sip1(10028): Switching to sip:ssuser-acct@33.222.91.155:50515 via udp:67.222.131.147:5060.
DialPlan 15:03:47:411 sip1(10028): SDP on UAC call had public IP not mangled, RTP socket 64.154.41.159:16184.
DialPlan 15:03:47:676 sip1(10028): Information response 100 Trying for sip:ssuser-acct@33.114.91.155:50515;transport=TLS;ob.
DialPlan 15:03:48:051 sip1(10028): Information response 180 Ringing for sip:ssuser-acct@33.114.91.155:50515;transport=TLS;ob.
DialPlan 15:03:48:051 sip1(10028): UAS call progressing with Ringing.
DialPlan 15:03:50:750 sip1(10028): Response 200 OK for sip:ssuser-acct@33.114.91.155:50515;transport=TLS;ob.
DialPlan 15:03:50:750 sip1(10028): SDP on UAC response had public IP not mangled, RTP socket 88.228.116.333:4000.
DialPlan 15:03:50:750 sip1(10028): Cancelling all call legs for ForkCall app.
DialPlan 15:03:50:750 sip1(10028): Answering client call with a response status of 200.
DialPlan 15:03:50:797 sip1(10028): Dial command was successfully answered in 3.40s.
DialPlan 15:03:50:797 sip1(10028): Dialplan cleanup for ssuser.
DialPlan 15:03:50:984 sip1(10028): Dial plan execution completed with normal clearing.



If I change the GV forward to this DID (it isn't normally), then calls to my GV number are received as well. Outgoing calls still don't work. One thing I do see is Google tells me if I signed into my account from an unrecognized computer every time I make the call (I don't know why it doesn't remember the IP address). It also locates the SS IP address in Mexico for some reason. It doesn't mention blocking the login, as you can see from the original log.

MYVay
Posts: 1
Joined: Wed Oct 26, 2016 10:05 pm

Re: Google voice call back and incoming calls

Postby MYVay » Wed Oct 26, 2016 10:13 pm

I had the exact same problem and changing '1212xxxxxxx' to '+1212xxxxxxx' fixed it for me!

MrDoo wrote:For some reason, the call back is not being recognized:

Code: Select all

DialPlan 21:10:43:892 sip1(8364): New call from tcp:24.114.91.40:44627 successfully authenticated by digest.
DialPlan 21:10:43:939 sip1(8364): Using dialplan Main for Out call to sip:6317918378@sipsorcery.com.
NewCall 21:10:43:970 sip1(8364): Executing script dial plan for call to 6317918378.
DialPlan 21:10:44:017 sip1(8364): ** Call from "User" <sip:username-acct@sipsorcery.com>;tag=1IlUrNzorWLRU5nRcGtRYT7kc-R.MPJS to 6317918378 **
DialPlan 21:10:44:017 sip1(8364): Local time: 10/24/2016 17:10
DialPlan 21:10:44:032 sip1(8364): Executing outbound dial plan
DialPlan 21:10:44:032 sip1(8364): Attempting to call 6317918378
DialPlan 21:10:44:032 sip1(8364): Caller name: User
DialPlan 21:10:44:032 sip1(8364): Call out using SIP account: 'username-acct'
DialPlan 21:10:44:048 sip1(8364): 6317918378 US area code; Use Google Voice
DialPlan 21:10:44:048 sip1(8364): SDP on GoogleVoiceCall call had public IP not mangled, RTP socket 25.218.116.243:4024.
DialPlan 21:10:44:048 sip1(8364): UAS call progressing with Ringing.
DialPlan 21:10:44:048 sip1(8364): Logging into google.com for gvuser@gmail.com.
DialPlan 21:10:44:188 sip1(8364): Google Voice pre-login page loaded successfully.
DialPlan 21:10:44:220 sip1(8364): GALX key 12345dtoBRg successfully retrieved.
DialPlan 21:10:44:220 sip1(8364): gxf key 12345UUv3zwkhOYTKVdqgs6H3G4BUza6Ng:1234543444152 successfully retrieved.
DialPlan 21:10:46:107 sip1(8364): Google Voice home page loaded successfully.
DialPlan 21:10:46:139 sip1(8364): Call key 123459D07/WUNMNIrJAU6BCrXqg= successfully retrieved for gvuser@gmail.com, proceeding with callback.
DialPlan 21:10:46:139 sip1(4608): SIP Proxy setting application server for next call to user username as udp:67.222.131.147:5070.
DialPlan 21:10:46:747 sip1(8364): Google Voice Call to 6317918378 initiated, callback #1212xxxxxxx, phone type 1, timeout 30s.
DialPlan 21:11:16:762 sip1(8364): Google Voice Call timed out waiting for callback.
DialPlan 21:11:16:933 sip1(8364): Google Voice Call to 6317918378 was successfully cancelled.
DialPlan 21:11:16:949 sip1(8364): ** Error: can't convert nil into Fixnum
DialPlan 21:11:16:949 sip1(8364): Dialplan cleanup for username.
DialPlan 21:11:17:230 sip1(8364): Dial plan execution completed without answering and with no last failure status.
DialPlan 21:11:17:230 sip1(8364): Call failed with a failure status of TemporarilyUnavailable and .
DialPlan 21:11:17:230 sip1(8364): UAS call failed with a response status of 480.



Regular incoming calls to the the DID seem to work as normal. The call back number is correct (I think). I tried both 212xxxxxxx and 1212xxxxxxx.

Any idea what I'm not doing right?

MrDoo
Posts: 23
Joined: Wed Apr 06, 2011 7:56 pm

Re: Google voice call back and incoming calls

Postby MrDoo » Sun Oct 30, 2016 9:48 pm

Thanks! Adding the "+" definitely worked for the call back. But, now I'm having a new problem. Instead of recognizing the call back, it seems Sipsorcery is processing the call as a normal incoming call. In the log below, you can see a dial attempt to the device I'm using to call. In my dial plan, I have calls routed to this device for this DID. Obviously, it gets a Busy response, and the next thing is dialed according to the dial plan. The DID is pointing to "trunk.ssuser@sip.sipsorcery.com", and I use the "trunk" to route calls to this device.

Aaron, should this be happening? The log is copied starting from the point where the dial plan is waiting for the GV call back:

Code: Select all

DialPlan 21:32:28:594 sip1(5176): Google Voice home page loaded successfully.
DialPlan 21:32:28:594 sip1(5176): Call key xyzabcD07/xyzabcrxyzabcrXqg= successfully retrieved for gvuser1@gmail.com, proceeding with callback.
DialPlan 21:32:28:594 sip1(4608): SIP Proxy setting application server for next call to user ssuser as udp:67.222.131.147:5070.
DialPlan 21:32:28:984 sip1(5176): Google Voice Call to 6317918378 initiated, callback #+12125551234, phone type 1, timeout 30s.
DialPlan 21:32:29:374 sip1(4608): SIP Proxy directing incoming call for user ssuser to application server udp:67.222.131.147:5070.
DialPlan 21:32:29:452 sip1(5176): Using dialplan Main for In call to sip:trunk.ssuser@sip.sipsorcery.com.
NewCall 21:32:29:468 sip1(5176): Executing script dial plan for call to trunk.ssuser.
DialPlan 21:32:29:530 sip1(5176): ** Call from "2125557231" <sip:2125557231@66.156.41.159>;tag=as1abc1239 to trunk.ssuser **
DialPlan 21:32:29:530 sip1(5176): Local time: 10/30/2016 17:32
DialPlan 21:32:29:561 sip1(5176): Commencing Dial with: ssuser-acct@local.
DialPlan 21:32:29:561 sip1(5176): Call leg is for local domain looking up bindings for ssuser-acct@sipsorcery.com for call leg ssuser-acct@local.
DialPlan 21:32:29:577 sip1(5176): 1 found for ssuser-acct@sipsorcery.com.
DialPlan 21:32:29:577 sip1(5176): ForkCall commencing call leg to sip:ssuser-acct@55.123.41.220:41578;transport=TLS;ob.
DialPlan 21:32:29:577 sip1(5176): SIPClientUserAgent Call using alternate outbound proxy of udp:67.222.131.147:5060.
DialPlan 21:32:29:577 sip1(5176): Switching to sip:ssuser-acct@55.123.41.220:41578 via udp:67.222.131.147:5060.
DialPlan 21:32:29:577 sip1(5176): SDP on UAC call had public IP not mangled, RTP socket 64.154.41.159:12468.
DialPlan 21:32:29:811 sip1(5176): Information response 100 Trying for sip:ssuser-acct@55.123.41.220:41578;transport=TLS;ob.
DialPlan 21:32:30:092 sip1(5176): Response 486 Busy Here for sip:ssuser-acct@55.123.41.220:41578;transport=TLS;ob.
DialPlan 21:32:30:092 sip1(5176): Commencing Dial with: myvm@iptel.org.
DialPlan 21:32:30:107 sip1(5176): Attempting to locate a provider for call leg: sip:myvm@iptel.org.
DialPlan 21:32:30:107 sip1(5176): ForkCall commencing call leg to sip:myvm@iptel.org.
DialPlan 21:32:30:107 sip1(5176): Switching to sip:myvm@iptel.org:5060 via udp:67.222.131.147:5060.
DialPlan 21:32:30:107 sip1(5176): SDP on UAC call had public IP not mangled, RTP socket 64.154.41.159:12468.
DialPlan 21:32:30:326 sip1(5176): Information response 100 Trying for sip:myvm@iptel.org.
DialPlan 21:32:32:619 sip1(5176): Response 200 OK for sip:myvm@iptel.org.
DialPlan 21:32:32:619 sip1(5176): SDP on UAC response had public IP not mangled, RTP socket 212.79.111.155:28950.
DialPlan 21:32:32:619 sip1(5176): Cancelling all call legs for ForkCall app.
DialPlan 21:32:32:619 sip1(5176): Answering client call with a response status of 200.
DialPlan 21:32:32:681 sip1(5176): Dial command was successfully answered in 2.57s.
DialPlan 21:32:32:681 sip1(5176): Dialplan cleanup for ssuser.
DialPlan 21:32:33:134 sip1(5176): Dial plan execution completed with normal clearing.
DialPlan 21:32:58:999 sip1(5176): Google Voice Call timed out waiting for callback.
DialPlan 21:32:59:077 sip1(5176): Google Voice Call to 6317918378 was successfully cancelled.
DialPlan 21:32:59:093 sip1(5176): ** Error: can't convert nil into Fixnum
DialPlan 21:32:59:093 sip1(5176): Dialplan cleanup for ssuser.
DialPlan 21:32:59:420 sip1(5176): Dial plan execution completed without answering and with no last failure status.
DialPlan 21:32:59:420 sip1(5176): Call failed with a failure status of TemporarilyUnavailable and .
DialPlan 21:32:59:420 sip1(5176): UAS call failed with a response status of 480.
DialPlan 21:33:28:889 sip1(5176): Matching dialogue found for BYE to sip:Anonymous@67.222.131.147:5060 from udp:67.222.131.147:5060.


User avatar
Aaron
Site Admin
Posts: 4550
Joined: Thu Jul 12, 2007 12:13 am

Re: Google voice call back and incoming calls

Postby Aaron » Mon Oct 31, 2016 10:30 am

That incoming call should have matched your pending GV call. What do you have set for the "Callback Pattern" on your GV Provider entry? It should be ".*" without the quotes in order to match all incoming calls to your account.

MrDoo
Posts: 23
Joined: Wed Apr 06, 2011 7:56 pm

Re: Google voice call back and incoming calls

Postby MrDoo » Mon Oct 31, 2016 2:17 pm

That was it. I changed it to "*" when I was trying to debug this issue. Changing it back fixed the problem. Thanks Aaron.


Return to “Technical Support”

Who is online

Users browsing this forum: Baidu [Spider] and 1 guest