Introduction
This document explains how to troubleshoot common Cisco IOS MGCP Gateway issues and provide an approach to solving them.
Common issues with Cisco IOS gateways
What debugs need to be collected ?
debug vpm all
debug voip vtsp all
debug mgcp packets
debug voip dialpeer all
debug voip ccapi inout
Issue 1. The MGCP gateway does not register to Cisco CallManager
right-Left#show ccm-manager
MGCP Domain Name: right-left
Priority Status Host
============================================================
Primary Registered 20.11.123.23
First Backup None
Second Backup None
Current active Call Manager: 20.11.123.23
Backhaul/Redundant link port: 2428
Failover Interval: 30 seconds
Keepalive Interval: 15 seconds
Last keepalive sent: 5w1d (elapsed time: 00:00:04)
Last MGCP traffic time: 5w1d (elapsed time: 00:00:04)
Last failover time: None
Switchback mode: Graceful
MGCP Fallback mode: Not Selected
Last MGCP Fallback start time: 00:00:00
Last MGCP Fallback end time: 00:00:00
This command verifies which voice ports have been bound to the MGCP application.
right-left#show mgcp endpoint
aaln/S1/SU0/0@right-left
aaln/S1/SU0/1@right-left
Issue 2. Caller Id issue
- Verify that Caller ID is being received at the FXO port.
<Log Snippets >
050275: Sep 13 09:49:14.499 HKG: //-1/313233343930/DSM:(0/0/0):-1/dsp_stream_mgr_destroy: .
050276: Sep 13 09:49:14.499 HKG: //-1/313233343930/DSM:(0/0/0):-1/dsm_delete_all_streams: .
050277: Sep 13 09:49:14.499 HKG: //-1/313233343930/DSM:(0/0/0):-1/dsmapi_accept_modem_passthrough_session: : dmgr: 22025EF4, active sessions 0, max sessions: 16 rejected sessions till now: 0
050278: Sep 13 09:49:14.499 HKG: [0/0/0] htsp_stop_caller_id_rx. message length 19htsp_setup_ind
050279: Sep 13 09:49:14.499 HKG: [0/0/0] get_fxo_caller_id:Caller ID received. Message type=4 length=19 checksum=98
050280: Sep 13 09:49:14.499 HKG: [0/0/0] Caller ID String 04 10 30 39 31 33 30 39 34 39 39 38 38 34 35 34 35 36 98
050281: Sep 13 09:49:14.499 HKG: [0/0/0] get_fxo_caller_id calling num=11111456 calling name= calling time=09/13 09:49
050282: Sep 13 09:49:14.499 HKG: TGRM: reg_invoke_tgrm_accept_call(1, TGRM_CALL_VOICE, TGRM_DIRECTION_IN, 0, 0, 0, 65535)
Issue 3. Pstn user gets a fast busy tone or "The number you have dialed is incorrect" message from CUCM
1. Verify the correct dial-peer selection
Dial-peer selection should always be PORT based. Correct dial-peer should be matched.
<Log Snippets >
Peer Info Type=DIALPEER_INFO_SPEECH
050184: Sep 13 09:44:02.802 HKG: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_PORT;
050185: Sep 13 09:44:02.802 HKG: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_PORT; Incoming Dial-peer=999000
In the above example based on port, incoming dial-peer 999000 is matched.
Example:
< Configuration >
dial-peer voice 9000 pots
destination-pattern .T
port 0/0/0
dial-peer voice 999000 pots
service mgcpapp
port 0/0/0
<Log Snippets >
Match Rule=DP_MATCH_ANSWER; Calling Number=98845456
050286: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
050287: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=98845456T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
050288: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Result=-1
050289: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:exit@6076
050290: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_ORIGINATE; Calling Number=98845456
050291: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:
Is Incoming=TRUE, Number Expansion=FALSE
050292: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=, Expanded String=, Calling Number=98845456T
Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH
050293: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Incoming Dial-peer=9000 Is Matched
050294: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype:exit@6076
050295: Sep 13 09:49:14.503 HKG: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=9000
In the above example the dial-peer selection is taking place based on the "destination-pattern". For the inbound calls to match
999000 pots dial-peer, we need to change the preference of dial-peer selection by having "answer-address".
Fix :
dial-peer voice 999000 pots
service mgcpapp
answer-address .
port 0/0/0
2. After the inbound dial-peer selection, verify that "MGCPAPP" is invoked .
<Log Snippets >
051685: Sep 19 10:52:38.744 HKG: //184/6120BBF78166/CCAPI/cc_process_call_setup_ind:
>>>>CCAPI handed cid 184 with tag 999000 to app "MGCPAPP"
051686: Sep 19 10:52:38.744 HKG: //184/6120BBF78166/CCAPI/ccCallSetContext:
If " MGCPAPP " is not invoked, then verify that the inbound dial-peer has "service mgcpapp" configured.
dial-peer voice 999000 pots
service mgcpapp
port 0/0/0
!
- " show mgcp " to verify the status of MGCP .
3. CSS/Partition is correctly configured for the MGCP endpoint on Cisco CallManager
Related Information
