Just started having issues w/ gv+ipkall+ss

Support zone
Post Reply
vergara
Posts: 13
Joined: Sun Apr 01, 2012 6:44 am

Just started having issues w/ gv+ipkall+ss

Post by vergara » Wed Sep 10, 2014 2:29 am

Hi Aaron,

Service has been fine until a couple days ago, now no incoming or outgoing.

console logs (outgoing, incoming gv#, incoming ipkall#)


outgoing call:

Monitor 01:59:16:933: basetype=console, ipaddress=*, user=vxxxxxa, event=*, request=*, serveripaddress=*, server=*, regex=.*.
DialPlan 01:59:33:840 sip1(7848): New call from udp:68.32.xxx.yyy:5061 successfully authenticated by digest.
DialPlan 01:59:33:887 sip1(7848): Using dialplan Intl for Out call to sip:856xxxyyyy@sipsorcery.com.
NewCall 01:59:33:933 sip1(7848): Executing script dial plan for call to 856xxxyyyy.
DialPlan 01:59:33:980 sip1(7848): ** Call from "vergara" <sip:vxxxxxa@sipsorcery.com>;tag=486959b6399e926o0 to 8566677104 **
DialPlan 01:59:33:980 sip1(7848): Calling 1856xxxyyyy via Google Voice
DialPlan 01:59:33:980 sip1(7848): SDP on GoogleVoiceCall call had RTP socket mangled from 192.168.1.116:16438 to 68.32.xxx.yyy:16438.
DialPlan 01:59:33:980 sip1(7848): UAS call progressing with Ringing.
DialPlan 01:59:33:980 sip1(7848): Logging into google.com for exxxxxv@gmail.com.
DialPlan 01:59:34:012 sip1(7848): Google Voice pre-login page loaded successfully.
DialPlan 01:59:34:027 sip1(7848): GALX key q_nHhRLW3fc successfully retrieved.
DialPlan 01:59:35:449 sip1(7848): Google Voice home page loaded successfully.
DialPlan 01:59:35:465 sip1(7848): Call key aW5uwuQm3/C16V8ku7Zu7keIsGs= successfully retrieved for exxxxxv@gmail.com, proceeding with callback.
DialPlan 01:59:35:465 sip1(2596): SIP Proxy setting application server for next call to user vxxxxa as udp:67.222.iii.jjj:5070.
DialPlan 01:59:35:543 sip1(7848): Google Voice Call to 185xxxyyyy initiated, callback #125ipkal#3, phone type 1, timeout 30s.
DialPlan 02:00:05:543 sip1(7848): Google Voice Call timed out waiting for callback.
DialPlan 02:00:05:606 sip1(7848): Google Voice Call to 1856xxxyyyy was successfully cancelled.
DialPlan 02:00:05:606 sip1(7848): Dialplan cleanup for vxxxxxa.
DialPlan 02:00:06:090 sip1(7848): Dial plan execution completed without answering and with no last failure status.
DialPlan 02:00:06:090 sip1(7848): Call failed with a failure status of TemporarilyUnavailable and .
DialPlan 02:00:06:090 sip1(7848): UAS call failed with a response status of 480.
Registrar 02:03:48:673 sip1(10576): Authentication required for vxxxxxa@sipsorcery.com from udp:68.32.xxx.yyy:5061.
Registrar 02:03:48:766 sip1(10576): Binding update request for vxxxxxa@sipsorcery.com from udp:68.32.xxx.yyy:5061, expiry requested 3600s granted 3600s.
RegisterSuccess 02:03:48:782 sip1(10576): Registration successful for vxxxxxa@sipsorcery.com from udp:68.32.xxx.yyy:5061, binding sip:vxxxxxa@192.168.1.116:5061;expiry=3600.



incoming using gv number:

DialPlan 02:25:37:917 sip1(4888): Using dialplan Intl for In call to sip:vxxxxxa@sipsorcery.com.
NewCall 02:25:37:963 sip1(4888): Executing script dial plan for call to vxxxxxa.
DialPlan 02:25:37:995 sip1(4888): ** Call from "HADDON HTS NJ" <sip:856xxxyyy@66.54.iii.jj>;tag=as7574d81d to vxxxxxa **
DialPlan 02:25:37:995 sip1(4888): Commencing Dial with: vxxxxxa@local.
DialPlan 02:25:38:010 sip1(4888): Call leg is for local domain looking up bindings for vergara@sipsorcery.com for call leg vxxxxxa@local.
DialPlan 02:25:38:026 sip1(4888): 1 found for vxxxxxa@sipsorcery.com.
DialPlan 02:25:38:026 sip1(4888): ForkCall commencing call leg to vxxxxxa@68.32.xxx.yyy:5061.
DialPlan 02:25:38:026 sip1(4888): SIPClientUserAgent Call using alternate outbound proxy of udp:67.222.nnn.mmm:5060.
DialPlan 02:25:38:026 sip1(4888): Switching to sip:vxxxxxa@68.32.xxx.yyy:5061 via udp:67.222.nnn.mmm:5060.
DialPlan 02:25:38:026 sip1(4888): SDP on UAC call had public IP not mangled, RTP socket 66.54.iii.jj:18478.
DialPlan 02:25:56:870 sip1(4888): Client call cancelled halting dial plan.
DialPlan 02:25:56:870 sip1(4888): Dialplan call was terminated by client side due to ClientCancelled.
DialPlan 02:25:56:886 sip1(4888): Cancelling all call legs for ForkCall app.
DialPlan 02:25:56:886 sip1(4888): Cancelling forwarded call leg, sending CANCEL to sip:vxxxxxa@68.32.xxx.yyy:5061.
DialPlan 02:25:56:901 sip1(4888): Dial command was halted by cancellation of client call after 18.88s.
DialPlan 02:25:56:901 sip1(4888): Dialplan cleanup for vxxxxxa.
DialPlan 02:25:57:151 sip1(4888): Dial plan execution completed with normal clearing.



incoming using ipkall number:

Registrar 02:03:48:673 sip1(10576): Authentication required for vxxxxxa@sipsorcery.com from udp:68.32.xxx.yyy:5061.
Registrar 02:03:48:766 sip1(10576): Binding update request for vxxxxxa@sipsorcery.com from udp:68.32.xxx.yyy:5061, expiry requested 3600s granted 3600s.
RegisterSuccess 02:03:48:782 sip1(10576): Registration successful for vxxxxxa@sipsorcery.com from udp:68.32.xxx.yyy:5061, binding sip:vergara@192.168.1.116:5061;expiry=3600.
DialPlan 02:09:35:664 sip1(7848): Using dialplan Intl for In call to sip:vxxxxxa@sipsorcery.com.
NewCall 02:09:35:711 sip1(7848): Executing script dial plan for call to vxxxxxa.
DialPlan 02:09:35:773 sip1(7848): ** Call from "HADDON HTS NJ" <sip:856nnnnnnn@66.54.nnn.mm>;tag=as2b3ad3c2 to vxxxxxa **
DialPlan 02:09:35:773 sip1(7848): Commencing Dial with: vxxxxxa@local.
DialPlan 02:09:35:789 sip1(7848): Call leg is for local domain looking up bindings for vergara@sipsorcery.com for call leg vxxxxxa@local.
DialPlan 02:09:35:789 sip1(7848): 1 found for vxxxxxa@sipsorcery.com.
DialPlan 02:09:35:789 sip1(7848): ForkCall commencing call leg to sip:vxxxxxa@68.32.xxx.yyy:5061.
DialPlan 02:09:35:789 sip1(7848): SIPClientUserAgent Call using alternate outbound proxy of udp:67.222.iii.jjj:5060.
DialPlan 02:09:35:804 sip1(7848): Switching to sip:vxxxxxa@68.32.xxx.yyy:5061 via udp:67.222.iii.jjj:5060.
DialPlan 02:09:35:804 sip1(7848): SDP on UAC call had public IP not mangled, RTP socket 66.54.nnn.mm:24728.
DialPlan 02:10:08:024 sip1(7848): Dialplan cleanup for vergara.
DialPlan 02:10:08:446 sip1(7848): Dial plan execution completed without answering and a last failure status of TemporarilyUnavailable Timeout, no response from server.
DialPlan 02:10:08:446 sip1(7848): Call failed with a failure status of TemporarilyUnavailable and Timeout, no response from server.
DialPlan 02:10:08:446 sip1(7848): UAS call failed with a response status of 480 and Timeout, no response from server.


Also when I use sipsorcery.com i get service unavailable, not sure if related.

Thanks,
Ed

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

Re: Just started having issues w/ gv+ipkall+ss

Post by Aaron » Wed Sep 10, 2014 11:27 am

These type of sporadic issues between GV & ipkall have come up for a few people in the past. Generally they seem to just clear themselves up. Can you check to see if your calls are working now.

forepj
Posts: 3
Joined: Sun Sep 21, 2014 1:53 am

Re: Just started having issues w/ gv+ipkall+ss

Post by forepj » Sun Sep 21, 2014 2:02 am

I am having the exact "temporarily unavailable" error for two days now. Is it worth trying a new ipkall number? Or, just wait. Strangely this started after I opted into SMS and voice via hangouts. Any connection?

Thanks peter

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

Re: Just started having issues w/ gv+ipkall+ss

Post by Aaron » Mon Sep 22, 2014 11:53 am

There could be a connection I haven't tested enabling that option myself. But if switching to hangouts turns off the PSTN callback then that will almost certainly break the GV-sipsorcery integration.

forepj
Posts: 3
Joined: Sun Sep 21, 2014 1:53 am

Re: Just started having issues w/ gv+ipkall+ss

Post by forepj » Thu Sep 25, 2014 4:14 am

I cannot use a handset to directly dial. simply doesn't work Temporarily Unavialble error every time. If I initiate through GV web interface I can sometimes make a connection, however it takes more than thirty seconds to get a call back. tried opting out of hangouts sms/voice but am still having the same issues. not sure what else to try.

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

Re: Just started having issues w/ gv+ipkall+ss

Post by Aaron » Thu Sep 25, 2014 11:51 am

Have you tried using a free callcentric DID in place of your ipkall one? The callcentric DIDs are very reliable.

hanke
Posts: 27
Joined: Tue Oct 29, 2013 4:38 pm
Location: Ontario, Canada

Re: Just started having issues w/ gv+ipkall+ss

Post by hanke » Thu Sep 25, 2014 4:29 pm

Today 25Sept (0900 EDST) I was having problems with Google Voice calling into it and getting calls to my registered ATA with Sipsorcery. I checked everything with Sipsorcery and all was fine. I could call out from the ATA via Google Voice but whenever I called my Goolge # the call went into voicemail.

I checked my Google Voice settings and ensured no Google Hangouts were active.

After several variations of calls into Google Voice # from different sources nothing changed.

Now as of about (1200 EDST) all is working fine again.

So as to your comments Aaron, about how things seem correct themselves, it would appear Google Voice was having problems of some sort and all appears to have been corrected at this time for your information.

will40
Posts: 16
Joined: Tue Aug 09, 2011 12:34 am

Re: Just started having issues w/ gv+ipkall+ss

Post by will40 » Sun Sep 28, 2014 3:06 pm

Same issues here for past week with 6 lines. Doesn't appear to be going away.

Did anyone determine that it was IPKaller with the delay?

Thanks

Will

forepj
Posts: 3
Joined: Sun Sep 21, 2014 1:53 am

Re: Just started having issues w/ gv+ipkall+ss

Post by forepj » Mon Sep 29, 2014 1:14 am

new ipkall number cleared up my issue

will40
Posts: 16
Joined: Tue Aug 09, 2011 12:34 am

Re: Just started having issues w/ gv+ipkall+ss

Post by will40 » Mon Sep 29, 2014 10:06 pm

forepj wrote:new ipkall number cleared up my issue
That cures it instantly. Only 5 more IPKALL numbers to get.

Thanks for the tip!

Will

Post Reply