Verify&troubleshoot
Verify&troubleshoot
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Tasks Performed
Task 1: Show and Debug Commands to Verify the Configuration
Task 2: Shutdown and Enable the Voice Ports
Troubleshoot
Calls from PSTN are Dropped after they are Transfered Three Times
Solution
Cisco Support Community - Featured Conversations
Related Information
Introduction
This document explains some basic verification and debug steps for the Media Gateway Control
Protocol (MGCP) on Cisco routers.
Symptoms
You can potentially encounter this list of symptoms when you configure Cisco CallManager with Cisco
IOS MGCP gateways with analog Foreign Exchange Office (FXO) and Foreign Exchange Station (FXS)
ports:
The MGCP gateway does not register with Cisco CallManager. Refer to MGCP Gateway
Registration Failure with Cisco CallManager.
Caller ID does not work on FXO ports. This is because caller ID is not supported with FXO ports
when configured for MGCP. Configure the gateway in H.323 mode instead.
Overhead paging locks up FXO ports during hookflash unless users go completely off-hook.
Shut followed by No Shut resets the port. Refer to Cisco bug ID CSCef62275 (registered
customers only) . This issue is fixed in Cisco IOS® Software Release 12.3(14)T and later.
1. Configuring Cisco CallManager 3.x with IOS MGCP Gateways (Analog FXO, FXS Ports)
Prerequisites
Requirements
Components Used
This configuration was tested with Cisco CallManager 3.0, 3.1, and 3.2 and various versions of Cisco
IOS Software Release 12.2 images. The screen shots and Cisco IOS software configuration were
captured using this software, hardware and other equipment:
1 * Cisco 2610 / 2 X FXS / 2 X FXO / 1 FastEthernet 10/100 port; Cisco IOS Software Release
12.2(11)T
1 * Cisco CallManager 4.1(0.91) running on an MCS7835
2 * Analog handsets
The information in this document was created from the devices in a specific lab environment. All of the
devices used in this document started with a cleared (default) configuration. If your network is live,
make sure that you understand the potential impact of any command.
Refer to the Cisco CallManager Compatibility Matrix for recommended compatibility software versions
between Cisco CallManager and the Cisco IOS gateway.
Note: Cisco IOS Software Release 12.2(11)T or later is recommended based on the ccm-manager
command enhancements. The ccm-manager command requires Cisco IOS Software Release 12.1(5)
XM or later on all routers (Cisco 2600 and 3600) and the Cisco Voice Gateway 200 (VG200).
The 2600 and 3600 routers support MGCP if they are running Cisco IOS Software Release 12.1(3)T or
later. The release and version that you require are based on the features that you need to enable. The
Cisco CallManager server must be running version 3.0(5)a or later. The router configuration is the same
for all types of routers. The Cisco CallManager configuration is also the same for all types of routers.
The VG200 is supported by Cisco IOS Software Release 12.1(5)XM1 and later releases. The release
and version that you require are based on the features that you need to enable. Although the VG200 is
supported in earlier releases of Cisco CallManager, version 3.0(5)a or later is recommended.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Tasks Performed
These steps do not need to be performed in the order in which they appear. The show commands are
useful because they display the current status of the configuration as well as verify that the changes
that you made took effect.
show ccm-manager
This command verifies the active and redundant configured Cisco CallManager servers. It also
indicates if the gateway is currently registered with the Cisco CallManager.
Note: This show ccm-manager command output was captured in a separated environment.
psy-voice-01#show ccm-manager
MGCP Domain Name: psy-voice-01
Priority Status Host
============================================================
Primary Registered 10.89.129.211
First Backup None
Second Backup None
show mgcp
Use this command to verify the status of the router MGCP parameters. You should see the IP
address of the Cisco CallManager server that you use (10.89.129.211, in this case.) All the
other parameters are left at their default behavior in this configuration.
psy-voice-01#show mgcp
MGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONE
MGCP call-agent: 10.89.129.211 Initial protocol service is MGCP 0.1
MGCP block-newcalls DISABLED
MGCP send SGCP RSIP: forced/restart/graceful/disconnected DISABLED
MGCP quarantine mode discard/step
MGCP quarantine of persistent events is ENABLED
MGCP dtmf-relay voip codec all mode out-of-band
MGCP dtmf-relay for VoAAL2 disabled for all codec types
MGCP voip modem passthrough disabled
MGCP voaal2 modem passthrough disabled
MGCP voip modem relay: Disabled.
MGCP TSE payload: 100
MGCP T.38 Named Signalling Event (NSE) response timer: 200
MGCP Network (IP/AAL2) Continuity Test timer: 200
MGCP 'RTP stream loss' timer: 5
MGCP request timeout 500
MGCP maximum exponential request timeout 4000
MGCP gateway port: 2427, MGCP maximum waiting delay 3000
MGCP restart delay 0, MGCP vad DISABLED
MGCP rtrcac DISABLED
MGCP system resource check DISABLED
MGCP xpc-codec: DISABLED, MGCP persistent hookflash: DISABLED
MGCP persistent offhook: ENABLED, MGCP persistent onhook: DISABLED
MGCP piggyback msg ENABLED, MGCP endpoint offset DISABLED
MGCP simple-sdp DISABLED
MGCP undotted-notation DISABLED
MGCP codec type g711ulaw, MGCP packetization period 20
MGCP JB threshold lwm 30, MGCP JB threshold hwm 150
MGCP LAT threshold lwm 150, MGCP LAT threshold hwm 300
MGCP PL threshold lwm 1000, MGCP PL threshold hwm 10000
MGCP CL threshold lwm 1000, MGCP CL threshold hwm 10000
MGCP playout mode is adaptive 60, 4, 200 in msec
MGCP media (RTP) dscp: ef, MGCP signaling dscp: af31
MGCP default package: line-package
MGCP supported packages: gm-package dtmf-package trunk-package line-
package
hs-package atm-package ms-package dt-package
res-package
mt-package
MGCP Digit Map matching order: shortest match
SGCP Digit Map matching order: always left-to-right
MGCP VoAAL2 ignore-lco-codec DISABLED
MGCP T.38 Fax is ENABLED
MGCP T.38 Fax ECM is DISABLED
MGCP T.38 Fax NSF Override is DISABLED
MGCP T.38 Fax Low Speed Redundancy: 0MGCP T.38 Fax High Speed
Redundancy: 0
MGCP Upspeed payload type for G711ulaw: 0, G711alaw: 8
MGCP Dynamic payload type for G.726-16K codec
MGCP Dynamic payload type for G.726-24K codec
MGCP Dynamic payload type for G.Clear codec
Use this command to show the voice ports (endpoints) that are under MGCP control in the
router. This command verifies which voice ports have been bound to the MGCP application. This
is related to the application MGCPAPP command and the port commands that were entered
under the plain old telephone service (POTS) dial peers in the document Configuring the Cisco
IOS MGCP Gateway.
Use this command to display any active MGCP connections. The endpoint is Slot1/Module
0/Port 0. This corresponds to the MGCP Member Configuration identifier in Cisco CallManager.
This tells you which port on the router is the endpoint in the call.
Use this command to verify the current status and configuration of the voice ports on the router.
This is sample output from the show voice port command for an FXO voice port:
Note: FXO ports in loopstart mode normally disconnect calls when they detect a second battery
reversal (back to normal). Use the no battery-reversal command on FXO ports to disable this
action. If an FXO port or its peer FXS port does not support battery reversal, avoid configuring
battery-reversal or battery-reversal answer on the FXO port. On FXO ports that do not
support battery reversal, the battery-reversal command can cause unpredictable behavior,
while the battery-reversal answer command prevents calls from being answered. Use the no
battery-reversal command to ensure that battery reversal answer is disabled on FXO ports that
do not support battery reversal.
Note: This example disables battery reversal on voice port 1/1/0 on a router.
voice-port 1/1/0
no battery-reversal
This is sample output from the show voice port command for an FXS voice port:
Use this command to show statistical information related to MGCP activity on the router.
Use these commands when you experience problems that you believe are not related to
configuration errors or hardware problems. Keep an example of each debug command from a
working configuration to use for comparison when you experience problems.
Refer to Sample of Debug MGCP Packets in order to understand the meaning of the output from
the debug mgcp packet command.
Refer to Important Information on Debug Commands before you issue any of the debug
commands.
In some instances it might be necessary to shut down and then reenable the voice ports on the MGCP
gateway. If calls cannot be made over FXO ports, there is no dial tone on FXS ports, or you experience
similar problems, try this step:
psy-voice-01(config)#voice-port 1/0/0
psy-voice-0(config-voiceport)#shutdown
Both ports are out of service
psy-voice-0(config-voiceport)#
00:25:44: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1/0/1, changed
state to Administrative Shutdown
00:25:45: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1/0/0, changed
state to Administrative Shutdown
psy-voice-0(config-voiceport)#no shutdown
Both ports are in service
psy-voice-0(config-voiceport)#
00:26:03: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1/0/0,
changed state to up
00:26:03: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1/0/1,
changed state
Note: This step is known to resolve several different issues related to problems with FXS and FXO
ports.
Troubleshoot
Calls from PSTN are Dropped after they are Transfered Three Times
Calls from the PSTN to an IP phone through an MGCP gateway are dropped after they are transferred
for the third time. Calls between the IP phone inside works without this issue.
Solution
This happens when Cisco CallManager sends out an ISDN NOTIFY to the Telco and the Telco side
does not support it. After NOTIFY is received three times, the Telco might drop the call. In order to
suppress these notify messages to the PSTN, complete these steps.
1. Choose Service>Service Parameters, select the Publisher server IP address and choose the
service as CallManager.
2. Click Advanced in the Service Parameter page and search for the heading Clusterwide
Parameters (Device - PRI and MGCP Gateway).
3. Set the Enable DMS PRI Notify Message from User to Network parameter value to False and
click on Update.
Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and
collaborate with your peers. Below are just some of the most recent and relevant conversations
happening right now.
Gateway not registering after CCM... dave.king 4 Replies 8 years, 2 months ago
MGCP gateway in SRST mode, incoming... shrutid22 3 Replies 11 months, 3 weeks ago
One-way audio with NAT and MGCP Phone rmwall 1 Reply 6 years, 11 months ago
CCM 5.1 MGCP Gateway Registration... keithknowles 12 Replies 3 years, 4 months ago
Related Information