Inbound callcentric call problems

Support zone
Post Reply
pengee
Posts: 2
Joined: Wed Jan 14, 2015 12:04 am

Inbound callcentric call problems

Post by pengee » Wed Jan 14, 2015 12:29 am

I recently switched from ipkall to callcentric as ipkall has been failing to forward incoming calls off and on recently. I created a callcentric account, added it as a provider, it registers and incoming / outgoing calls are working. However, I'm having two problems which I assume have the same root cause:

1. When dialing the callcentric number the caller hears no ringtone, only silence until the call is answered. This has been tested from a couple cell phones. When calling in from a soft phone the generated ring kept going over the call after answering.

2. If the call is ended by the SIP phone on the SIPSorcery end, the other caller does not show that the call has ended and can stay on the line.

Is is that the call progression is not being sent back to callcentric or callcentric is not handling it properly? If so is this something that can be fixed on my end? Any help would be appreciated!

-- I tried to post a call log but the spam filter is not letting me.

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

Re: Inbound callcentric call problems

Post by Aaron » Fri Jan 16, 2015 10:41 am

For the first problem you can check the SIP trace to see if a 180 Ringing or 183 Session Progress response is received. Those are what tell the callee's phone to ring.

For the second problem the BYE request is not getting passed through to the other end of the call. That's an issue with the SIP signalling but without a trace I can't tell which leg.

I've fixed your forums account so you should be able to post the traces now.

pengee
Posts: 2
Joined: Wed Jan 14, 2015 12:04 am

Re: Inbound callcentric call problems

Post by pengee » Fri Jan 16, 2015 3:58 pm

Thank you, Aaron. Incoming calls show 180 -> 183 - log below. I think I've narrowed this down to a t-mobile problem as calls from google voice and verizon heard a ringback tone. Unfortunately, I'm not at home so I can't test the hangup issue but will post when I can. Do you know if these are common issue that have to be resolved with carriers sometimes?

Thanks!


DialPlan 15:51:26:999 sip1(1328): Using dialplan default for In call to sip:pengee@sipsorcery.com;rinstance=BSOZXQ.
NewCall 15:51:27:030 sip1(1328): Executing script dial plan for call to pengee.
DialPlan 15:51:27:061 sip1(1328): ** Call from "xxxxxxx Stacey" <sip:12069739575@66.193.176.xx>;tag=3630412286-437587 to pengee *
DialPlan 15:51:27:061 sip1(1328): Incoming call from 12069739575
DialPlan 15:51:27:061 sip1(1328): Commencing Dial with: pengee@local.
DialPlan 15:51:27:061 sip1(1328): Call leg is for local domain looking up bindings for pengee@sipsorcery.com for call leg pengee@local.
DialPlan 15:51:27:077 sip1(1328): 1 found for pengee@sipsorcery.com.
DialPlan 15:51:27:077 sip1(1328): ForkCall commencing call leg to sip:pengee@73.181.183.xxx:5060.
DialPlan 15:51:27:077 sip1(1328): SIPClientUserAgent Call using alternate outbound proxy of udp:67.222.131.xxx:5060.
DialPlan 15:51:27:077 sip1(1328): Switching to sip:pengee@73.181.183.xxx:5060 via udp:67.222.131.xxx:5060.
DialPlan 15:51:27:077 sip1(1328): SDP on UAC call had public IP not mangled, RTP socket 204.11.192.169:61086.
DialPlan 15:51:27:217 sip1(1328): Information response 100 Trying for sip:pengee@73.181.183.xxx:5060.
DialPlan 15:51:27:217 sip1(1328): Information response 180 Ringing for sip:pengee@73.181.183.xxx:5060.
DialPlan 15:51:27:233 sip1(1328): UAS call progressing with Ringing.
DialPlan 15:51:34:737 sip1(1328): Client call cancelled halting dial plan.
DialPlan 15:51:34:752 sip1(1328): Dialplan call was terminated by client side due to ClientCancelled.
DialPlan 15:51:34:768 sip1(1328): Cancelling all call legs for ForkCall app.
DialPlan 15:51:34:768 sip1(1328): Cancelling forwarded call leg, sending CANCEL to sip:pengee@73.181.183.xxx:5060.
DialPlan 15:51:34:784 sip1(1328): Dial command was halted by cancellation of client call after 7.71s.
DialPlan 15:51:34:799 sip1(1328): Dialplan cleanup for pengee.
DialPlan 15:51:34:815 sip1(1328): Dial plan execution completed with normal clearing.
DialPlan 15:51:34:877 sip1(1328): Response 487 Request Terminated for sip:pengee@73.181.183.xxx:5060.

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

Re: Inbound callcentric call problems

Post by Aaron » Sun Jan 18, 2015 10:10 am

I can't identify any issues from the dialplan trace but if it is a SIP signalling issue it won't show up.

A lot of people have posted about audio problems with mobile carriers over the years. It's generally due to NAT issues that prevent RTP from getting through. Mobile carriers often use double NATs which play havoc with protocols like SIP and RTSP that put the IP address they want to use for the audio in the signalling request.

If you want more gorey details you can take a look at this article http://www.sipsorcery.com/mainsite/Help/SIPAudio.

Post Reply