MGCP Incoming calls fail

[amohammed]

Hi,

Incoming calls seem to be rejected by CUCM based on the CUCM call logs.  Outgoing calls work but incoming call don't connect.

Setup

T1 CAS MGCP to CUCM 12.5

Any ideas would be greatly appreciated.

[Jaime Valencia]

What troubleshooting have you done so far? 

What does the debugs and traces show? 

[amohammed]

Hi Jaime,

I pulled some traces from CUCM.  The only thing I saw was calls being rejected in the call logs to ext 5105.  I am migrating from 2800 to 4331 gateways.  The 2800 gateways work with CUCM 9.1.2.  The 4331 routers are connect the CUCM 12.5 via MGCP.  If i try to call in, the call does not connect, and the telco says unable to connect your call.   

[Roger Kallberg]

Any particular reason why you use MGCP? Your better off for options and flexibility if you change to use SIP as the protocol for the connection to CM from your voice gateway.

[amohammed]

Yes, most definitely, SIP is the better option.  The existing system uses MGCP and to minimize the reconfiguration, I decided to use the same but that seems to have turned out to be a bad choice.

[amohammed]

Outbound calls are no longer working.  Debug MGCP packet shows call setup failed.

[Roger Kallberg]

MGCP seems so 90-is, do yourselves a favour and reconfigure the gateway to SIP. That’s likely a faster option than trying to figure out what is wrong with MGCP.

My 2 cents.

[amohammed]

TAC says it is a T1 layer 1 or 2 problem.  The gateway is waiting for a signal from the provider.

[Valeriy Tarazanov]

This trouble can be resolved only with debug :-)

[amohammed]

The incoming call is connecting now but there is a delay of 10 -15 seconds before the auto attendant picks up.  The system plays 10-15 seconds of dial tone before the auto attendant picks up.  It is the same if we call an internal phone directly from the PSTN.

TAC took the following debug.

<---

008987: Feb 16 2020 21:05:15.577 JAM: htsp_dsp_message: SEND_SIG_STATUS: state=0xC timestamp=5658 systime=3628595  21:05:35

008988: Feb 16 2020 21:05:15.577 JAM: htsp_process_event: [0/1/0:1(1), EM_ONHOOK, E_DSP_SIG_1100]em_onhook_offhook

008989: Feb 16 2020 21:05:15.577 JAM: htsp_timer - 50 msec

008990: Feb 16 2020 21:05:15.627 JAM: htsp_process_event: [0/1/0:1(1), EM_QUALIFY_SEIZURE, E_HTSP_EVENT_TIMER]em_qualify_seizure_timeout

Digit collect :

======================

009005: Feb 16 2020 21:05:15.758 JAM: htsp_timer2 - 10000 msec

009006: Feb 16 2020 21:05:16.117 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_dsm_digit_begin_cb:

009007: Feb 16 2020 21:05:16.117 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_report_cas_digit:

   Begin Digit=8, Mode=CC_TONE_DTMF_MODE

009008: Feb 16 2020 21:05:16.117 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_dsm_digit_begin_cb:exit@480

009009: Feb 16 2020 21:05:16.117 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_process_event:

   [state:S_DC_COLLECT, event:E_VTSP_DIGIT_BEGIN]

009010: Feb 16 2020 21:05:16.117 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_process_event:

   Unexpected EVENT [E_VTSP_DIGIT_BEGIN] Received For STATE [S_DC_COLLECT];

   Previous STATE [0.1 ]

009011: Feb 16 2020 21:05:16.177 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_dsm_digit_end_cb:

009012: Feb 16 2020 21:05:16.177 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_report_cas_digit:

   End Digit=8, Mode=CC_TONE_DTMF_MODE

009013: Feb 16 2020 21:05:16.177 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_dsm_digit_end_cb:exit@615

009014: Feb 16 2020 21:05:16.177 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/vtsp_process_event:

   [state:S_DC_COLLECT, event:E_VTSP_DIGIT_END]

009015: Feb 16 2020 21:05:16.177 JAM: //-1/C5F1EA60828C/VTSP:(0/1/0:1):-1:1:1/dc_digit:

009016: Feb 16 2020 21:05:16.178 JAM: htsp_digit_ready: digit = 38

009017: Feb 16 2020 21:05:16.178 JAM: htsp_process_event: [0/1/0:1(1), EM_OFFHOOK, E_VTSP_DIGIT]em_offhook_digit_collect