
5-4
Cisco Catalyst 4000 Access Gateway Module Installation and Configuration Note
OL-3008-01
Chapter 5 Configuring the Voice Interfaces
MGCP Configuration
• Configuring FXS and FXO Analog Ports, page 5-6
• Configuring T1-CAS E&M Emulation, page 5-7
• T1/E1 Configuration (H.323), page 5-22
• Where to Go Next, page 5-12
For more information on using MGCP with Cisco CallManager 3.0, refer to the Cisco CallManager 3.0
online help and to Configuring Cisco IP Telephony Gateways, available online at Cisco.com.
Enabling MGCP
To configure the AGM so that it can be controlled by Cisco CallManager Release 3.0 using MGCP, you
must identify the primary and any backup Cisco CallManager servers that you want to use in case the
primary server becomes unavailable. You must also configure each voice gateway as an MGCP gateway
in Cisco CallManager, as described in the Cisco CallManager Administration Guide. Finally, you must
configure the voice ports installed on your gateway. The following sections describe these procedures.
To enable generic MGCP support on a Cisco voice gateway, enter the following commands from the
global configuration mode prompt:
Gateway(config)#mgcp
Gateway(config)#mgcp call-agent hostname
where hostname identifies the Cisco CallManager server (or possibly a generic MGCP call agent).
To enable support for Cisco CallManager within MGCP, enter the following command:
Gateway(config)#ccm-manager MGCP
Cisco CallManager controls dial-plan-related configuration elements, and they should not be configured
in the Cisco voice gateway for MGCP-managed endpoints (those with application MGCPAPP in the
dial-peer statement). You should not configure any of the following elements when using MGCP:
• Destination pattern
• Session target
• Expansion numbers
• Connection PLAR/tie-line/trunk (voice port)
• codec
Note H.323 and MGCP configurations will coexist when you enable MGCP gateway fallback.
Enabling Switchover and Switchback
To identify up to two backup Cisco CallManager servers, enter the following command:
Gateway(config)#ccm-manager redundant-host hostname1 hostname2
where hostname1 identifies the first backup Cisco CallManager server using the DNS host name or
dotted decimal format, and hostname2
identifies the second backup Cisco CallManager server.
If you configure one or two backup Cisco CallManager servers, you can control how the gateway
behaves if the primary server becomes unavailable at some point and then later becomes available again:
this is called switchback.
Comentarios a estos manuales