Specifications

5-5
Catalyst 4224 Access Gateway Switch Software Configuration Guide
OL-2031-02
Chapter 5 Configuring the Voice Interfaces
MGCP Configuration
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 or Survivable Remote Site Telephony (SRST).
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.
To configure gateway switchback, enter the following command:
Gateway(config)#ccm-manager switchback
{graceful|imm[ediate]|sch[edule-time] hh:mmm|uptime[-delay] minutes}
During switchover and switchback, Cisco CallManager maintains active
connected calls. Transient calls (calls in progress or on hold without an active
voice connection) are torn down. An exception applies for PRI interfaces that
MGCP controls, in which case both active and transient calls are torn down during
switchover and switchback. Table 5-1 describes each switchback option.