Inbound Calls are failing

luismgallop · ‎03-09-2016

Hello Guys I'm having a problem with my inbounds calls, I'm hearing a busy tone when I call from number 2123133960 to number 8600, however there are another calls that are established and works fine.

I attached the debug ccapi inout, debug voip dialpeer and one show running. I was looking that the disconnect cause is number 57. The gateway configure as and H323 gateway. IOS version is 15

Please someboyd coul help me,

Thanks,

Shadi Shami · ‎03-10-2016

Hello,

I went through the logs, and here is what I see:

1. Call matched an Incoming POTS dial-peer (8000) and was assigned with this ID (10471763):

Mar 9 15:16:08.643: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=8000
Mar 9 15:16:08.643: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
Mar 9 15:16:08.643: //-1/AF4D97989D60/CCAPI/cc_api_display_ie_subfields

......

Mar 9 15:16:08.643: //10471763/AF4D97989D60/CCAPI/cc_api_call_setup_ind_common:
   Set Up Event Sent;
   Call Info(Calling Number=4140408954(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=8600(TON=Unknown, NPI=Unknown))

2. The call matched an Outgoing H323 dial-peer (2) that was assigned with this ID (10471764)

Mar 9 15:16:08.651: //10471763/AF4D97989D60/CCAPI/ccCallSetupRequest:
   Calling Number=4140408954(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=8600(TON=Unknown, NPI=Unknown),
   Redirect Number=, Display Info=
   Account Number=, Final Destination Flag=TRUE,
   Guid=AF4D9798-E540-11E5-9D60-8C6813A4C4DF, Outgoing Dial-peer=2

Mar 9 15:16:08.651: //10471764/AF4D97989D60/CCAPI/ccIFCallSetupRequestPrivate:
SPI Call Setup Request Is Success; Interface Type=1, FlowMode=1

3. The 2nd leg was disconnected with Reason Code (21): Call Rejected

Mar 9 15:16:08.675: //10471764/AF4D97989D60/CCAPI/cc_api_call_disconnected:
Call Entry(Responsed=TRUE, Cause Value=21, Retry Count=0)

4. Then SIP Dial-peer was elected as Outgoing dial-peer (210) with this ID (10471767):

Guid=AF4D9798-E540-11E5-9D60-8C6813A4C4DF, Outgoing Dial-peer=210
Mar 9 15:16:08.699: //10471763/AF4D97989D60/CCAPI/cc_api_display_ie_subfields

Mar 9 15:16:08.699: //10471767/AF4D97989D60/CCAPI/ccIFCallSetupRequestPrivate:
SPI Call Setup Request Is Success; Interface Type=3, FlowMode=1

5. And this call was disconnected with reason code (57): Bearer capability not authorized

Mar 9 15:16:08.723: //10471767/AF4D97989D60/CCAPI/ccCallDisconnect:
Cause Value=57, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=57)

Which outgoing dial-peer should the call match, 2 (H323) or 210 (SIP)?

Thank you,

Shadi

luismgallop · ‎03-10-2016

Hello Shadi,

Thanks for your response.

The call must match dial-peer 2, because the dial-peer 210 is using for calls from a SIP Trunk.

Some calls are established using dial-peer 8000 and 2, as show the follow image:

Thanks for your help.

Shadi Shami · ‎03-13-2016

Hello,

In this case we need to find out why the 2nd leg got disconnected. in addition to the previous debugs, can ou please provide the following too:

debug h225 asn1

debug h245 asn1

If the GW is connected to CUCM, it would be better to collect CCM SDI/ SDL logs as well.

Thank you,

Shadi