Cisco CallManager and Cisco IOS Interoperability Guide

Cisco Unified CallManager and Cisco IOS
Interoperability Configuration Guide

Release 12.4T
May 2006
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and
iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco
Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation,
Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ
Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing,
ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered
trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0502R)
Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

Copyright © 2003-2006, Cisco Systems, Inc.
All rights reserved.
CONTENTS
Cisco Unified CallManager and Cisco IOS Interoperability Features Roadmap 9
Contents 9
Platforms and Cisco IOS Software Images 9
Cisco Unified CallManager and Cisco IOS Interoperability Feature List 9
Overview of Cisco Unified CallManager and Cisco IOS Interoperability 13
Contents 13
Information About Cisco Unified CallManager and Cisco IOS Interoperability 13

Cisco AVVID 14
Cisco Unified CallManager Interoperability 14
MGCP Voice Gateways 14
MGCP Gateway Fallback 15
MGCP PRI Backhaul 16
MGCP BRI Backhaul 16
Multicast Music-On-Hold 16
Network Specific Facilities 16
Single-Point Configuration 16
Supplementary Services 16
Switchover (Failover) 17
Switchback 17
Tones and Cadences 17
MGCP Advantages Over H.323 17
Conferencing and Transcoding 18
Additional References 18
Related Documents 18
Standards 20
MIBs 20
RFCs 20
Technical Assistance 21
Configuring MGCP Gateway Support for Cisco Unified CallManager 23
Contents 24
Prerequisites for Configuring MGCP Gateway Support for Cisco Unified CallManager 24
Restrictions for Configuring MGCP Gateway Support for Cisco Unified CallManager 25
Information about MGCP Gateway Support for Cisco Unified CallManager 25

iii
Contents
MGCP Gateways and Cisco Unified CallManager 25
How to Configure MGCP Gateway Support for Cisco Unified CallManager 26

Enabling MGCP on Cisco IOS Gateways 27
Verifying MGCP Configuration on the Cisco IOS Gateway 29
Configuring Cisco Unified CallManager Switchover and MGCP Gateway Fallback 30
Switchover (Failover) 30
Switchback 31
MGCP Gateway Fallback 31
MGCP Gateway Registration with Cisco Unified CallManager 33
Benefits of Cisco Unified CallManager Switchover and MGCP Gateway Fallback 33
Configuring MGCP Gateway Fallback and Cisco SRST 35
Cisco SRST Description 35
Configuring MGCP Gateway Fallback and Cisco SRST 35
Enabling SRST on an MGCP Gateway 35
Verifying Cisco Unified CallManager Switchover and MGCP Gateway Fallback 37
Configuring POTS Dial Peers on MGCP Gateways 39
Restrictions for POTS Dial Peers on MGCP Gateways 39
Verifying Dial Peer Configuration for MGCP Gateways 40
Enabling Single-Point Configuration for MGCP Gateways 44
Prerequisites for Single-Point Configuration for MGCP Gateways 45
Verifying Single-Point Configuration for MGCP Gateways 46
Configuring Multicast Music-on-Hold Support for Cisco Unified CallManager 47
Prerequisites for Multicast Music-on-Hold (MOH) 47
Multicast Music-on-Hold 47
Verifying Music-on-Hold 48
Configuring MLPP Service on Cisco MGCP Gateways 49
Prerequisites 49
Restrictions 49
MLPP Overview 50
Configuring Fallback when Using MLPP on T1 CAS 51
Verifying MLPP Configuration 53
Configuration Examples for MGCP Gateway Support for Cisco CallManager 54
MGCP Gateway with T1 CAS: Example 54
MGCP Gateway with T1 PRI: Example 56
Multicast Music-on-Hold: Example 58
MLPP (Cisco 2801): Example 59
MLPP (Cisco 2621): Example 61
Where to Go Next 63

iv
Contents
Configuring Enhanced Conferencing and Transcoding for Voice Gateway Routers 65
Contents 66
Prerequisites for Conferencing and Transcoding for Voice Gateway Routers 66
Restrictions for Conferencing and Transcoding for Voice Gateway Routers 68
Information About Conferencing and Transcoding for Voice Gateway Routers 68

DSP Farms 69
DSP Farm Profiles 69
Conferencing 69
Transcoding 70
MTP 71
Conferencing and Transcoding Features on the NM-HDV2 and NM-HD-1V/2V/2VE 71
Conferencing and Transcoding Features on the NM-HDV 72
Conferencing and Transcoding Features on the Cisco 1751 and Cisco 1760 72
Allocation of DSP Resources 73
Allocation of DSP Resources Within the Voice Network Module 73
Allocation of DSP Resources Within the DSP Farm 73
Conferencing and Transcoding Session Capacities 74
NM-HDV System Capacities 75
How to Configure Conferencing and Transcoding for Voice Gateway Routers 77
Determining DSP Resource Requirements 78
Enabling SCCP on the Cisco Unified CallManager Interface 79
Configuring Enhanced Conferencing and Transcoding 80
Configuring a DSP Farm Profile 80
Associating a DSP Farm Profile to a Cisco Unified CallManager Group 83
Modifying Default Settings for SCCP Connection to Cisco Unified CallManager 85
Verifying DSP Farm Configuration 87
Troubleshooting Tips for Conferencing and Transcoding on Voice Gateway Routers 90
Troubleshooting DSP-Farm Services 91
Configuring Conferencing and Transcoding (NM-HDV) 91
Configuring the DSP Farm on the NM-HDV 91
Tuning DSP-Farm Performance on the NM-HDV 93
What to Do Next 94
Configuring Conferencing and Transcoding (PVDM-256K) 94
Prerequisites for Conferencing and Transcoding on the Cisco 1751 or Cisco 1760 94
What to Do Next 95
Configuring Out-of-Band to In-Band DTMF Relay 95
Prerequisites 96
Restrictions 96
Out-of-Band to In-Band DTMF Relay for Cisco IOS Voice Gateways 96

v
Contents
Configuration Examples for Conferencing and Transcoding 98

DSP-Farm Services on the NM-HDV2/PVDM2: Example 98
DSP-Farm Services on the NM-HDV: Example 100
Tuning DSP-Farm Services on the NM-HDV: Example 102
DSP-Farm Services on the Cisco 1760: Example 102
Dut-Band to In-Band DTMF Relay (Cisco 2801): Example 104
Out-Band to In-Band DTMF Relay (Cisco 3725): Example 106
SIP Gateway: Example 108
Where to Go Next 110
Configuring MGCP PRI Backhaul and T1 CAS Support for Cisco Unified CallManager 111
Contents 112
Prerequisites for MGCP PRI Backhaul and T1 CAS Support 112
Restrictions for MGCP PRI Backhaul and T1 CAS Support 112
Information About MGCP PRI Backhaul and T1 CAS Support 112

MGCP PRI Backhaul Overview 112
ISDN NSF in Route Patterns 113
How to Configure MGCP PRI Backhaul Support for Cisco Unified CallManager 113
Configuring MGCP PRI Backhaul on the Cisco Voice Gateway 114
Verifying MGCP PRI Backhaul Configuration 115
Configuring MGCP Gateway Support for Cisco Unified CallManager Network Specific Facilities 118
Prerequisites for MGCP Gateway Support for Cisco Unified CallManager Network Specific
Facilities 118
Verifying Configuration of MGCP Gateway Support for Cisco Unified CallManager Network Specific
Facilities 119
Configuring QSIG Supplementary Features for Cisco IOS Voice Gateways 122
Prerequisites 122
QSIG Supplementary Features for Cisco IOS Voice Gateways 123
Configuration Examples for MGCP PRI Backhaul and T1 CAS 124
MGCP PRI Backhaul and T1 CAS: Example 124
Configuring MGCP-Controlled Backhaul of BRI Signaling in Conjunction with Cisco Unified

CallManager 127
Contents 128
Prerequisites for MGCP-Controlled Backhaul of BRI Signaling 128
Restrictions for MGCP-Controlled Backhaul of BRI Signaling 129

vi
Contents
Information About MGCP-Controlled Backhaul of BRI Signaling 129

MGCP-Controlled Backhaul of BRI Signaling 129
How to Configure MGCP-Controlled Backhaul of BRI Signaling 131
Configuring the BRI Interface as an MGCP-BRI Backhaul Endpoint 131
Verifying MGCP-BRI Backhaul Configuration 132
Troubleshooting Tips for MGCP-Controlled Backhaul of BRI Signaling 134
Configuring SRTP Mode on Cisco IOS MGCP Gateways 134
Prerequisites for SRTP Mode 134
Configuration Examples for MGCP-Controlled Backhaul of BRI Signaling 135
MGCP BRI Backhaul on Cisco 3745: Example 136
MGCP BRI Backhaul on Cisco 3640: Example 139
Configuring Tone Download to MGCP Gateways 143
Contents 144
Information About Tone Download to MGCP Gateways 144

Tone Download Process for MGCP Gateways 144
Static Tones 144
Custom Tones 146
How to Configure Tone Download to MGCP Gateways 146
Verifying Globalized Cadence and Tone Configuration 147
Prerequisites 147
Configuring Customizable Tone Download to Cisco IOS MGCP Gateways 151
Prerequisites 151
Restrictions 151
Verifying Customizable Tone Download 152
Troubleshooting Tips for Customizable Tone Download 157
Configuration Examples for Tone Download to MGCP Gateways 158
Customizable Tone Download Voice-Port Configuration: Example 158
Customizable Tone Download Using Single-Point Configuration: Example 158
Configuring MCID for Cisco IOS Voice Gateways 161
Contents 162
Prerequisites for MCID for Cisco IOS Voice Gateways 162
Restrictions for MCID for Cisco IOS Voice Gateways 162
Information About MCID for Cisco IOS Voice Gateways 163

vii
Contents
MCID 163
How to Configure MCID for Cisco IOS Voice Gateways 164

Enabling the ISDN Interface to Send MCID Requests 164
Configuring MCID on the Voice Gateway (Cisco IOS Release 12.3(14)T) 165
Configuring MCID on the Voice Gateway (Cisco IOS Release 12.3(11)T) 167
Configuration Examples for MCID for Cisco IOS Voice Gateways 169
Configuring MCID in Cisco IOS Release 12.3(14)T (Cisco 2801): Example 169
Configuring MCID in Cisco IOS Release 12.3(11)T (Cisco 3745): Example 171
Configuring RSVP Agent 175
Contents 175
Prerequisites for RSVP Agent 176
Restrictions for RSVP Agent 176
Information About RSVP Agent 176

RSVP Agent 177
How to Enable the RSVP Agent on the Voice Gateway 178
Enabling RSVP in a DSP Farm Profile 178
What to Do Next 179
Verifying RSVP Agent Configuration 180
Troubleshooting the RSVP Agent 181
Configuration Examples for RSVP Agent 184
RSVP Agent: Example 184
Index

viii
Cisco Unified CallManager and Cisco IOS
Interoperability Features Roadmap
This guide provides configuration information about Cisco IOS voice features for Cisco Unified
CallManager and Cisco IOS Interoperability. This first chapter describes how to access Cisco Feature
Navigator and lists Cisco Unified CallManager and Cisco IOS Interoperability features by Cisco IOS
release.
Note For information about the full set of Cisco IOS voice features, see the entire Cisco IOS Voice
Configuration Library—including library preface, glossary, and other documents—at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/voice_c/vcl.htm.
Contents
• Platforms and Cisco IOS Software Images, page 9
• Cisco Unified CallManager and Cisco IOS Interoperability Feature List, page 9
Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image
support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on
Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at
the login dialog box and follow the instructions that appear.
Cisco Unified CallManager and Cisco IOS Interoperability

Feature List
Table 1 lists Cisco Unified CallManager and Cisco IOS Interoperability features by Cisco IOS release.
Features that are introduced in a particular release are available in that and subsequent releases.

9
Cisco Unified CallManager and Cisco IOS Interoperability Features Roadmap
Cisco Unified CallManager and Cisco IOS Interoperability Feature List
Table 1 Cisco Unified CallManager and Cisco IOS Interoperability Features
Release Features Introduced in That Release1 Feature Description Feature Documentation

12.4(6)T RSVP Agent Enables Cisco Unified CallManager “Configuring RSVP Agent” on
to provide resource reservation for page 175 of this guide.
voice and video media to ensure QoS
and call admission control (CAC).
12.3(11)T MCID for Cisco IOS Voice Gateways Supports the Malicious Call “Configuring MCID for Cisco IOS
Identification (MCID) supplementary Voice Gateways” on page 161 of
service in Cisco Unified CallManager this guide.
4.0.
MLPP for Cisco IOS Voice Gateways Supports Multilevel Precedence and “Configuring MLPP Service on
Preemption (MLPP) service, allowing Cisco MGCP Gateways” section
authorized users to preempt lower on page 49 of this guide.
priority voice calls using
Cisco Unified CallManager 4.0.
Out-of-Band to In-Band DTMF Relay RFC 2833 capability enabling DTMF “Configuring Conferencing and
for Cisco IOS Voice Gateways relay communication between SIP Transcoding (NM-HDV)” section
devices and nonSIP endpoints using on page 91 of this guide.
Cisco Unified CallManager 4.0.
QSIG Supplementary Features for Supports Q Signaling (QSIG) over “Configuring QSIG
Cisco IOS Voice Gateways PRI backhaul interfaces on MGCP Supplementary Features for Cisco
gateways to Cisco Unified IOS Voice Gateways” section on
CallManager 4.0. page 122 of this guide.
12.3(8)T Enhanced Conferencing and Enables conferencing, transcoding, “Configuring Enhanced
Transcoding for Voice Gateway and MTP support for Cisco voice Conferencing and Transcoding for
Routers gateways using the NM-HDV2 and Voice Gateway Routers” on
NM-HD high-density voice network page 65 of this guide.
modules.
12.3(4)T MGCP Gateway Support for Supports the configuration of the “Configuring MGCP Gateway
Cisco Unified CallManager Network network specific facilities (NSF) Support for Cisco Unified
Specific Facilities ISDN information element in route CallManager Network Specific
patterns for Cisco CallManager 3.3. Facilities” section on page 118 of
this guide.
Customizable Tone Download to Enables the downloading of “Configuring Tone Download to
Cisco IOS MGCP Gateways from region-specific tones and associated MGCP Gateways” on page 143 of
Cisco Unified CallManager frequencies, amplitudes, and this guide.
cadences.
12.3(2)T MGCP-Controlled Backhaul of BRI Enables the transporting of signaling “Configuring MGCP-Controlled
Signaling in Conjunction with information from remote-office Backhaul of BRI Signaling in
Cisco Unified CallManager MGCP gateways connected by ISDN Conjunction with Cisco Unified
BRI trunks to a centralized CallManager” on page 127 of this
Cisco Unified CallManager. guide.

10
Table 1 Cisco Unified CallManager and Cisco IOS Interoperability Features (continued)
Release Features Introduced in That Release1 Feature Description Feature Documentation

12.2(13)T Conferencing and Transcoding for Enables conferencing and transcoding “Configuring Enhanced
Voice Gateway Routers support for Cisco voice gateways Conferencing and Transcoding for
using NM-HDV high-density voice Voice Gateway Routers” on
network modules. page 65 of this guide.
Update to the Interworking of Adds support for the mgcp validate “Enabling MGCP on Cisco IOS
Cisco MGCP Voice Gateways and domain-name command, which Gateways” section on page 27 of
Cisco CallManager Version 3.2 checks whether the domain name or IP this guide.
address received in MGCP messages
match those on the gateway.
12.2(11)T Globalized Cadence and Tone for Enables Cisco MGCP gateways to “Configuring Tone Download to
Cisco IOS Gateways provide localized cadence and tones MGCP Gateways” on page 143 of
for Cisco CallManager 3.2, this guide.
eliminating the need for the cptone
command.
MGCP Gateway Fallback Provides basic call processing support “Configuring Cisco Unified
in H.323 mode when an MGCP CallManager Switchover and
gateway loses connectivity to all of its MGCP Gateway Fallback” section
configured Cisco Unified on page 30 of this guide.
CallManager servers.
MGCP Generic Configuration Provides single-point configuration “Enabling Single-Point
Support for Cisco CallManager using a centralized TFTP server to Configuration for MGCP
automatically download XML Gateways” section on page 44 of
configuration files to MGCP this guide.
gateways.
MGCP PRI Backhaul and T1-CAS Enables transporting of complete “Configuring MGCP PRI
Support for Cisco Unified IP-telephony signaling from an ISDN Backhaul and T1 CAS Support for
CallManager PRI interface on an MGCP gateway to Cisco Unified CallManager” on
Cisco CallManager 3.1 and 3.2. page 111 of this guide.
Multicast Music on Hold Support for Enables music streaming from a “Configuring Multicast
Cisco CallManager music-on-hold (MOH) server to Music-on-Hold Support for Cisco
callers placed on hold using an MGCP Unified CallManager” section on
gateway and Cisco CallManager 3.1 page 47 of this guide.
and 3.2.
12.1(3)T MGCP Support for Adds MGCP support to Cisco IOS “Configuring Cisco Unified
Cisco CallManager gateways to provide supplementary CallManager Switchover and
services, failover, and redundancy MGCP Gateway Fallback” section
support for Cisco CallManager 3.0. on page 30 of this guide.
1. Features that are introduced in a particular release are available in that and subsequent releases.

11

12
Overview of Cisco Unified CallManager and
Cisco IOS Interoperability
This chapter provides an overview of Cisco Unified CallManager and Cisco IOS interoperability.
Note For more information about Cisco IOS voice features, see the entire Cisco IOS Voice Configuration
Library—including library preface and glossary, feature documents, and troubleshooting
information—at
Contents
• Information About Cisco Unified CallManager and Cisco IOS Interoperability, page 13
• Additional References, page 18
Information About Cisco Unified CallManager and Cisco IOS

Interoperability
To configure a Cisco IOS voice gateway to interoperate with Cisco Unified CallManager, you should
understand the following concepts:
• Cisco AVVID, page 14
• Cisco Unified CallManager Interoperability, page 14
• MGCP Voice Gateways, page 14
• MGCP Advantages Over H.323, page 17
• Conferencing and Transcoding, page 18

13
Overview of Cisco Unified CallManager and Cisco IOS Interoperability
Information About Cisco Unified CallManager and Cisco IOS Interoperability
Cisco AVVID
Cisco voice gateway routers can be deployed in a Cisco Unified CallManager IP-telephony network
using the Cisco Architecture for Voice, Video, and Integrated Data (AVVID), a baseline infrastructure
that enables enterprises to design networks that scale to meet e-business demands for business solutions
such as e-learning and customer care.
Voice and video solutions based on Cisco AVVID include:
• Client devices such as IP phones
• Directory services
• IP-based business applications
• Network management
• Scalable call processing
• Service and support
• Video conferencing
Cisco Unified CallManager Interoperability

Cisco Unified CallManager is the software-based call-processing component of voice gateways in a VoIP
network. It extends enterprise telephony features and functions to packet telephony network devices such
as IP phones, media processing devices, VoIP gateways, and multimedia applications.
Additional data, voice, and video services such as unified messaging, multimedia conferencing,
collaborative contact centers, and interactive multimedia response systems interact through the
Cisco Unified CallManager application programming interface (API). Cisco Unified CallManager also
supports third-party applications.
Cisco IOS gateways connect AVVID networks to traditional telephone trunks or analog and digital
devices. The trunks are connected to the PSTN or existing PBX systems, legacy telephones, and voice
conference units. Cisco IOS voice gateways communicate with Cisco Unified CallManager using H.323
or Media Gateway Control Protocol (MGCP).
• In H.323 mode, the Cisco voice gateway communicates with Cisco Unified CallManager as an
intelligent gateway device.
• In MGCP mode, the Cisco voice gateway operates as a stateless client, giving Cisco Unified
CallManager full control.
MGCP Voice Gateways

Cisco Unified CallManager provides a central point of configuration, administration, and control for
MGCP voice gateways. Using Cisco IOS software, voice gateways are configured as MGCP gateways.
Cisco Unified CallManager acts as an MGCP call agent, controlling the setting up and tearing down of
connections between the endpoints in a VoIP network and endpoints in the public switched telephone
network (PSTN), while managing all dial-plan related configuration elements.
With MGCP, dial plans are configured centrally in Cisco Unified CallManager, instead of in each
gateway. All Cisco MGCP gateways in a Cisco AVVID-enabled IP telephony network can be
automatically configured by downloading XML files from Cisco Unified CallManager. Cisco MGCP

14
gateways also provide multiple levels of failover capabilities, including Survivable Remote Site
Telephony (SRST) support to prevent call-processing interruptions or dropped calls if there is a Cisco
Unified CallManager or WAN failure.
MGCP gateways support the following Cisco Unified CallManager features:
• MGCP Gateway Fallback, page 15
• MGCP PRI Backhaul, page 16
• MGCP BRI Backhaul, page 16
• Multicast Music-On-Hold, page 16
• Network Specific Facilities, page 16
• Single-Point Configuration, page 16
• Supplementary Services, page 16
• Switchover (Failover), page 17
• Switchback, page 17
• Tones and Cadences, page 17
MGCP Gateway Fallback

MGCP gateway fallback improves the reliability of PSTN interfaces in an IP-telephony network by
providing basic call processing support when an MGCP gateway loses connectivity to all of its
configured Cisco Unified CallManager servers. Each Cisco Unified CallManager server is potentially
available as a backup call agent through a prioritized list of call agents that is configured on the MGCP
gateway.
On startup, the MGCP voice gateway attempts to establish a connection to the highest order
Cisco Unified CallManager server on the configured list. If the attempt is successful, the gateway
registers itself with the primary (highest priority) call agent. If no call agent in this prioritized list is
accessible, the gateway uses its default H.323 session application (Version 2) to perform basic
call-handling functions (see Figure 1).
Figure 1 MGCP Gateway Fallback Transition to Default H.323 Session Application
Cisco Unified CallManager 2

Cisco Unified CallManager 1 (backup) Cisco Unified CallManager 3
(active) (backup)
M
M M
WAN
Gateway fallback
MGCP
application
Default application
62328
(H.323)

15
MGCP PRI Backhaul

MGCP PRI backhaul is a method for transporting complete IP telephony signaling information from an
ISDN PRI interface on an MGCP gateway to Cisco Unified CallManager through a Transmission Control
Protocol (TCP) connection. It terminates all of the ISDN PRI Layer 2 (Q.921) signaling functions on the
MGCP gateway and packages all of the ISDN PRI Layer 3 (Q.931) signaling information into packets
for transmission to Cisco Unified CallManager through an IP tunnel. This ensures the integrity of the
Q.931 signaling information that passes through the network for managing IP telephony devices.
MGCP BRI Backhaul

MGCP-controlled backhaul of BRI signaling provides service to remote-office gateways that connect by
means of ISDN BRI trunks to a centralized Cisco Unified CallManager. D-channel signaling information
is backhauled to Cisco Unified CallManager through a TCP session. All Q.931 messages are passed
through the TCP connection between the Cisco MGCP gateway and Cisco Unified CallManager. The
feature enables you to connect remote ISDN PBXs and key systems to a Cisco ISDN BRI network
termination (network side) or a PSTN Class 4/5 switch through a Cisco ISDN BRI terminal equipment
(as user side) interface.
Multicast Music-On-Hold
Multicast music-on-hold (MOH) functionality enables the streaming of music from an MOH server to
the voice interfaces of on-net and off-net callers that are placed on hold. This integrated multicast
capability is implemented through the H.323 signaling in Cisco Unified CallManager.
Network Specific Facilities

The MGCP Gateway Support for Cisco Unified CallManager Network Specific Facilities (NSF) feature
supports the use of the ISDN NSF information element in the route pattern, enabling facilities or services
to be invoked on a call-by-call basis. Without NSF configuration, you must configure associated
gateways as standalone H.323 gateways for which NSF services are configured locally within the router.
No configuration is required on the MGCP gateway to use the NSF feature.
Single-Point Configuration
When you configure MGCP gateways to interoperate with Cisco Unified CallManager, you can use a
centralized TFTP boot directory on a host device in your network to automatically download most of the
Cisco IOS configuration in an XML file. A Cisco Unified CallManager server can be concurrently
configured as a TFTP server.
The XML file is generated by using the web-based Cisco Unified CallManager graphical user interface
(GUI). When the network administrator changes the configuration information in the database,
Cisco Unified CallManager instructs the MGCP gateway to download the modified XML file.
Supplementary Services
Supplementary services include call forwarding, call hold, call transfer when the line is busy or there is
no answer, and three-party call conferencing to and from the PSTN or a private branch exchange (PBX).
• Call forwarding—Enables you to forward calls dialed from the original location to a remote location
within or across the network.

16
• Call hold—Places the handset in mute mode. The transmitter and receiver functions are disengaged
until the hold button is pressed again to reconnect the parties.
• Call transfer—Transfers a call to a third party through a preprogrammed button that produces a
recall dial tone. The receiver of the call then dials the third-party number, waits for the line to ring
and for the new called party to answer, and then hangs up.
• Three-party call conferencing—Adds a third party to a call. It is similar to the transfer function, but
rather than the call being transferred to a third party, the third party called is added to the call.
Switchover (Failover)
A Cisco MGCP gateway first connects—that is, registers—to a primary Cisco Unified CallManager. If
connection to the primary fails, the gateway registers automatically to a backup if one exists and, if that
connection also fails, to a second backup if one exists. When connection to the primary is restored, the
gateway automatically registers to the primary. Existing connections are preserved during the
switchover.
Switchback
Switchback is the process that MGCP gateways use to reestablish communication with the primary
Cisco Unified CallManager server when it becomes available after losing connectivity. Switchback
mode can occur immediately, at a specified time after the last active call ends, or after a specified length
of time. During the switchback, existing connections are preserved.
Tones and Cadences

Tones and cadences are preconfigured based on the network locale in Cisco Unified CallManager. It is
no longer necessary to configure the cptone command on the MGCP gateway. The static tone table used
for a voice port is determined by the network locale that is specified for the voice port in Cisco Unified
CallManager. The network locale for each voice port is downloaded in the gateway’s XML configuration
file.
The Customizable Tone Download to Cisco IOS MGCP Gateways from Cisco Unified CallManager
feature enables the downloading of region-specific tones and the associated frequencies, amplitudes, and
cadences in up to two custom tone files.
MGCP Advantages Over H.323

Using MGCP provides advantages over H.323, including the following:
• Centralized call-management architecture
MGCP enables external control of network signaling. Handling of Layer 3 call processing centrally
in the network is advantageous to network operators who need a high degree of control over their
networks.
• Shorter voice cut-through times
MGCP speeds voice cut-through as compared to H.323 for both initial call setup and redirects. Voice
cut-through is the time from when the called party goes offhook to when both parties are able to
receive voice from the other. Long cut-through times can prevent deployment of viable IP telephony
solutions in centralized environments.

17
Additional References
Conferencing and Transcoding

The digital-signal-processor (DSP) farm functionality on Cisco IOS gateways provides conference,
transcode, and hardware MTP capability by using DSP resources on high-density digital voice/fax
network modules such as the NM-HDV and NM-HDV2. DSP farms are configured on the voice gateway
and managed by Cisco Unified CallManager through Skinny Client Control Protocol (SCCP).
The following sections provide references for Cisco IOS Interoperability with Cisco Unified
CallManager.
Related Documents
Related Topic Document Title

Additional Cisco IOS Voice Configuration Library Cisco IOS Voice Configuration Library at
documents, including library preface and glossary http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/
123cgcr/voice_c/vcl.htm
Cisco IOS command references • Cisco IOS Debug Command Reference, Release 12.4T at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios
124/124tcr/tdb_r/index.htm
• Cisco IOS Voice Command Reference at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios
123/123tcr/123tvr/index.htm
Cisco IOS configuration examples Cisco Systems Technologies website at
http://cisco.com/en/US/tech/index.html
Note From the website, select a technology category and
subsequent hierarchy of subcategories, then click Technical
Documentation > Configuration Examples.
Cisco IOS software system messages Cisco IOS Software System Messages at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/
124sup/124sms/index.htm
Cisco IOS troubleshooting information Cisco IOS Voice Troubleshooting and Monitoring Guide at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/
123cgcr/vvfax_c/voipt_c/index.htm
Cisco Unified CallManager • Cisco Unified CallManager Administration Guide, Release
4.0(1)
• Administration and configuration
• Cisco Unified CallManager System Guide, Release 4.0(1)
• Cisco Unified CallManager Features and Services Guide,
Release 4.0(1)
• Upgrading • Upgrading Cisco Unified CallManager Release 4.0(1)

18
Related Topic Document Title

• Transcoder services and configuration • “Transcoders” chapter in the Cisco Unified CallManager
System Guide
• “Transcoder Configuration” chapter in the Cisco Unified
CallManager Administration Guide
• Voice-conference services and configuration • “Conference Bridges” chapter in Cisco Unified CallManager
System Guide, Release 4.0(1)
• “Conference Bridge Configuration” chapter in Cisco Unified
CallManager Administration Guide, Release 4.0(1)
• MCID “Malicious Caller Identification” chapter in the Cisco Unified
CallManager Features and Services Guide
• MLPP “Multilevel Precedence and Preemption” chapter in the
Cisco Unified CallManager Features and Services Guide
Fallback support for Cisco IP phones Cisco Survivable Remote Site Telephony (SRST) Version 3.0
Interface configuration Cisco IOS Interface and Hardware Component Command
Reference, Release 12.4T
IP addressing and services Cisco IOS IP Addressing Services, Release 12.4T
Routing process and routing protocols for networks Cisco IOS IP Application Services Configuration Guide,
Release 12.4T
MGCP concepts and configuration procedures Cisco IOS MGCP and Related Protocols Configuration Guide
Network module installation “Connecting Voice Network Modules” chapter in the Cisco Network
Modules Hardware Installation Guide
Hardware installation Modular Access Routers documentation

19
Standards
Standards Title
H.225 Call Signaling Protocols and Media Stream Packetization for
Packet-based Multimedia Communication Systems
H.323 Annex M.1 Tunnelling of Signalling Protocol (QSIG) in H.323
I.251.7 Malicious Call Identification (MCID)
I.255.3 Multi-Level Precedence and Preemption Service (MLPP)
ITU-T Recommendation Q.931 ISDN User-Network Interface Layer 3 specification (ITU-T
specification for signaling to establish, maintain, and clear ISDN
network connections).
Q.81.7 Malicious Call Identification (MCID)
Q.951.7 Stage 3 Description for Number Identification Supplementary
Services Using DSS 1: Malicious Call Identification (MCID)
TIA/EIA-464-B Requirements for Private Branch Exchange (PBX) Switching
Equipment
MIBs
MIBs MIBs Link
• Transcoding: To locate and download MIBs for selected platforms, Cisco IOS
releases, and feature sets, use Cisco MIB Locator found at the
– Access Environment MIB
following URL:
– CDP MIB
http://www.cisco.com/go/mibs
– Cisco Stack MIB
– DSP Management MIB
– RFC 1157 SNMP
– RFC 1213 MIB II
– RFC 1573 MIB II Interface Extensions
– RFC 1643 Ethernet MIB
– RFC 1757 Ethernet RMON
– Voice Common Interface MIB
– Voice Dial MIB
RFCs
RFCs Title
RFC 2833 RTP Payload for DTMF Digits, Telephony Tones and Telephony
Signals

20
Technical Assistance
Description Link
The Cisco Technical Support & Documentation http://www.cisco.com/techsupport
website contains thousands of pages of searchable
technical content, including links to products,
technologies, solutions, technical tips, and tools.
Registered Cisco.com users can log in from this page to
access even more content.

21

22
Configuring MGCP Gateway Support for
Cisco Unified CallManager
This chapter describes the basic tasks for configuring Cisco IOS MGCP gateways to interoperate with
Cisco Unified CallManager.
Feature History for MLPP for Cisco IOS Voice Gateways

Release Modification
12.3(8)XY This feature was introduced.
12.3(11)T This feature was integrated into Cisco IOS Release 12.3(11)T.
Feature History for MGCP Generic Configuration Support for Cisco Unified CallManager
12.2(2)XN This feature was introduced.
Feature History for Multicast Music-on-Hold

12.2(2)XN This feature was introduced.
Feature History for MGCP Support for Cisco Unified CallManager

12.1(3)T This feature was introduced for Cisco CallManager 3.0.
12.1(5)XM H.323 support was added for E1 and T1 PRI, E&M, E1-CAS, and BRI.
Analog support for MGCP and analog DID were added.
12.2(2)XA Support was added for Cisco CallManager 3.0(8).
12.2(2)XN Support was added for Cisco CallManager 3.1. New MGCP features
included ISDN PRI Backhaul and T1 CAS, Single-Point Configuration,
MGCP Gateway Fallback, and Multicast Music-on-Hold (MOH).
12.2(11)T Support was added for Cisco CallManager 3.2.

23
Configuring MGCP Gateway Support for Cisco Unified CallManager
Contents
Finding Support Information for Platforms and Cisco IOS Software Images
Note For more information about this and related Cisco IOS voice features, see the following:
• “Overview of Cisco Unified CallManager and Cisco IOS Interoperability” on page 13.
• Entire Cisco IOS Voice Configuration Library—including library preface and glossary, other feature
documents, and troubleshooting documentation—at
Contents
• Prerequisites for Configuring MGCP Gateway Support for Cisco Unified CallManager, page 24
• Restrictions for Configuring MGCP Gateway Support for Cisco Unified CallManager, page 25
• Information about MGCP Gateway Support for Cisco Unified CallManager, page 25
• How to Configure MGCP Gateway Support for Cisco Unified CallManager, page 26
• Configuration Examples for MGCP Gateway Support for Cisco CallManager, page 54
• Where to Go Next, page 63
Prerequisites for Configuring MGCP Gateway Support for

• Cisco IOS gateway is configured for VoIP.
• Voice interface card or network module is installed.
• Cisco CallManager Version 3.2 or later is used.
• Cisco Unified CallManager Version 4.0 or later is used.

24
Restrictions for Configuring MGCP Gateway Support for Cisco Unified CallManager
Restrictions for Configuring MGCP Gateway Support for

• Integrated access is not supported when you control voice traffic using MGCP and Cisco Unified
CallManager. Integrated access is when the channels on a T1 or E1 interface are divided between a
group used for voice and another group used for WAN access.
• T1 and E1 protocols, such as QSIG, E1 R2, T1 FGD, and PRI NFAS, are not supported with MGCP.
Note Any configuration update that affects MGCP should be performed during a planned maintenance
window while MGCP is disabled; otherwise updating the configuration could disrupt MGCP
functionality. Before making any configuration changes, disable MGCP using the no mgcp command.
After all configuration changes are completed, use the mgcp command to enable MGCP.
Information about MGCP Gateway Support for Cisco Unified

CallManager
To configure MGCP gateways to act under the control of Cisco Unified CallManager, you should
understand the following concept:
• MGCP Gateways and Cisco Unified CallManager, page 25
MGCP Gateways and Cisco Unified CallManager

MGCP enables the remote control and management of voice and data communications devices at the
edge of multiservice IP packet networks. Because of its centralized architecture, MGCP overcomes the
distributed configuration and administration problems inherent in the use of protocols such as H.323.
MGCP simplifies the configuration and administration of voice gateways and supports multiple
(redundant) call agents, eliminating the potential for a single point of failure in controlling the Cisco IOS
gateway in the network.
MGCP can be configured as a master or slave protocol to ensure that the gateway receives and executes
the configuration, control, and management commands that are issued by Cisco Unified CallManager.
The MGCP gateway is under the control of Cisco Unified CallManager.
MGCP uses endpoints and connections to construct a call. Endpoints are sources of or destinations for
data and can be physical or logical locations identifying a device. The voice ports on the Cisco MGCP
gateway are its endpoints. Connections can be point-to-point or multipoint. Cisco Unified CallManager
acts as the MGCP call agent, managing connections between endpoints and controlling how the Cisco
IOS gateway functions.

25
How to Configure MGCP Gateway Support for Cisco Unified CallManager
Figure 2 shows a typical MGCP gateway that is controlled by an MGCP call agent.
Figure 2 MGCP Gateway Controlled by Cisco Unified CallManager
POTS phones

(MGCP call agent)
MGCP gateway
M
PSTN
V
TCP/IP network
IP
33342
MGCP-managed endpoints
The MGCP gateway receives most of its required configuration from the call agent. To configure an
MGCP gateway, you simply identify the Cisco Unified CallManager server associated with the gateway
and identify the gateway to the call agent. The MGCP gateway handles the translation between voice
signals and the packet network and interacts with the Cisco Unified CallManager server. The server
performs signal and call processing.
How to Configure MGCP Gateway Support for Cisco Unified

CallManager
This section contains the following procedures:
• Enabling MGCP on Cisco IOS Gateways, page 27 (required)
• Verifying MGCP Configuration on the Cisco IOS Gateway, page 29 (optional)
• Configuring Cisco Unified CallManager Switchover and MGCP Gateway Fallback, page 30
(required)
• Verifying Cisco Unified CallManager Switchover and MGCP Gateway Fallback, page 37 (optional)
• Configuring POTS Dial Peers on MGCP Gateways, page 39 (required)
• Verifying Dial Peer Configuration for MGCP Gateways, page 40 (optional)
• Enabling Single-Point Configuration for MGCP Gateways, page 44 (optional)
• Verifying Single-Point Configuration for MGCP Gateways, page 46 (optional)
• Configuring Multicast Music-on-Hold Support for Cisco Unified CallManager, page 47 (optional)
• Verifying Music-on-Hold, page 48 (optional)
• Configuring MLPP Service on Cisco MGCP Gateways, page 49 (optional)
• Configuring Fallback when Using MLPP on T1 CAS, page 51 (optional)
• Verifying MLPP Configuration, page 53 (optional)

26
Enabling MGCP on Cisco IOS Gateways

Perform this task to enable MGCP on a Cisco IOS gateway to support Cisco Unified CallManager.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface ethernet slot/port
4. ip address ip-address subnetmask
5. no shutdown
6. exit
7. hostname name
8. mgcp validate domain-name
9. mgcp
10. mgcp call-agent {ip-address | host-name} [port] [service-type type] [version version-number]
11. mgcp dtmf-relay voip codec {all | low-bit-rate} mode {cisco | nse | out-of-band}
12. ccm-manager mgcp
13. exit
DETAILED STEPS
Command Purpose
Step 1 enable Enables privileged EXEC mode.
• Enter your password when prompted.
Example:
Router> enable
Step 2 configure terminal Enters global configuration mode.
Example:
Router# configure terminal
Step 3 interface ethernet slot/port Enters interface configuration mode so that you can
configure the Ethernet interface for communicating
with Cisco Unified CallManager.
Example:
Router(config)# interface ethernet 0/1 • Slot and port syntax is platform-dependent; type ?
to determine.
Step 4 ip address ip-address subnetmask Configures an IP address and subnet mask on the
router’s Ethernet interface.
Example:
Router(config-if)# ip address 10.10.2.23
255.255.255.255

27
Command Purpose
Step 5 no shutdown Activates the Ethernet port.
Example:
Router(config-if)# no shutdown
Step 6 exit Exits interface mode and enters global configuration
mode.
Example:
Router(config-if)# exit
Step 7 hostname name Assigns a unique name to a network router which
enables Cisco Unified CallManager to identify the
device.
Example:
Router(config)# hostname smith • Default device name is Router.
Step 8 mgcp validate domain-name (Optional) Verifies that the domain name or IP address
received as part of the endpoint names in the MGCP
messages match those configured on the gateway.
Example:
Router(config)# mgcp validate domain-name Note This command is enabled by default. You do
not need to enter it unless you have previously
disabled the functionality by using the
no mgcp validate domain-name command.
Step 9 mgcp Enables the MGCP protocol.
Example:
Router(config)# mgcp
Step 10 mgcp call-agent {ip-address | host-name} [port] Specifies the primary Cisco Unified CallManager
[service-type type] [version version-number] server’s IP address or domain name, and the port
gateway service type and version number.
Example:
Router(config)# mgcp call-agent 10.0.0.21 mgcp 0.1
Step 11 mgcp dtmf-relay voip codec {all | low-bit-rate} Selects the codec type and the dual tone
mode {cisco| nse | out-of-band} multifrequency (DTMF) relay services.
Example:
Router(config)# mgcp dtmf-relay voip codec all mode
cisco
Step 12 ccm-manager mgcp Enables the MGCP gateway to support Cisco Unified
CallManager.
Example:
Router(config)# ccm-manager mgcp
Step 13 exit Exits global configuration mode.
Example:
Router(config)# exit

28
Verifying MGCP Configuration on the Cisco IOS Gateway

SUMMARY STEPS
1. show running-config
2. show interfaces ethernet [number]
3. show mgcp
DETAILED STEPS
Step 1 show running-config

Use the show running-config command to verify that MGCP is enabled on the voice gateway:
Router# show running-config
...
hostname voice-3640
!
...
mgcp
mgcp call-agent 10.0.0.21 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
!
ccm-manager mgcp
!
interface Ethernet0/1
ip address 10.10.2.23 255.255.255.0
half-duplex
Step 2 show interfaces ethernet

Use the show interfaces ethernet command to verify that an Ethernet interface is configured to
communicate with the Cisco Unified CallManager server, for example:
Router# show interfaces ethernet 4/2
Ethernet4/2 is up, line protocol is up

Hardware is cxBus Ethernet, address is 0000.0c02.d0ce (bia 0000.0c02.d0ce)
Internet address is 10.10.7.1, subnet mask is 255.255.255.0
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 4:00:00
Last input 0:00:00, output 0:00:09, output hang never
Last clearing of "show interface" counters 0:56:40
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
Five minute input rate 3000 bits/sec, 4 packets/sec
Five minute output rate 0 bits/sec, 0 packets/sec
4961 packets input, 715381 bytes, 0 no buffer
Received 2014 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
567 packets output, 224914 bytes, 0 underruns
0 output errors, 168 collisions, 0 interface resets, 0 restarts
0 babbles, 2 late collision, 7 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Step 3 show mgcp

Use the show mgcp command to display the MGCP settings on the Cisco IOS gateway:
Router# show mgcp

29
MGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONE
!MGCP call agent with IP address for Cisco CallManager:
MGCP call-agent: 10.0.0.21 2427 Initial protocol service is MGCP, v. 0.1
MGCP block-newcalls DISABLED
MGCP send RSIP for SGCP is DISABLED
MGCP quarantine mode discard/step
MGCP quarantine of persistent events is ENABLED
!DTMF-relay voip codec parameters:
MGCP dtmf-relay voip codec all mode out-of-band
MGCP dtmf-relay for VoAAL2 disabled for all codec types
MGCP voip modem passthrough mode: CISCO, codec: g711ulaw, redundancy: DISABLED,
MGCP voaal2 modem passthrough mode: NSE, codec: g711ulaw
MGCP TSE payload: 0
MGCP Network (IP/AAL2) Continuity Test timer: 200
MGCP 'RTP stream loss' timer: 5
MGCP request timeout 500, MGCP request retries 3
MGCP rtp unreachable timeout 1000
MGCP gateway port: 2427, MGCP maximum waiting delay 3000
MGCP restart delay 0, MGCP vad 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 lmw 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 IP ToS low delay disabled, MGCP IP ToS high throughput disabled
MGCP IP ToS high reliability disabled, MGCP IP ToS low cost disabled
MGCP IP RTP precedence 5, MGCP signaling precedence: 3
MGCP default package: line-package
MGCP supported packages: gm-package dtmf-package trunk-package line-package
hs-package rtp-package ms-package dt-package sst-packagc-package
MGCP VoAAL2 ignore-lco-codec DISABLED
MGCP T.38 Fax is DISABLED
Note For a description of the fields displayed in this output, see the Cisco IOS Voice Command Reference.
Configuring Cisco Unified CallManager Switchover and MGCP Gateway

Fallback
This section describes how to configure Cisco Unified CallManager failover capabilities on the MGCP
gateway.
Switchover (Failover)
Cisco IOS gateways can maintain links to up to two backup Cisco Unified CallManager servers in
addition to a primary Cisco Unified CallManager. This redundancy enables a voice gateway to
switchover to a backup if the gateway loses communication with the primary. The backup server takes
control of the devices that are registered with the primary Cisco Unified CallManager. The second
backup takes control of the registered devices if both the primary and first backup Cisco Unified
CallManager fail. The gateway preserves existing connections during a switchover to a backup

30
When the primary Cisco Unified CallManager server becomes available again, control reverts to that
server. Reverting to the primary server can occur immediately, after a configurable amount of time, or
only when all connected sessions are released.
Switchback
Switchback is the process a voice gateway uses to reestablish communication with the primary
Cisco Unified CallManager server when the server becomes available again. Switchback can occur
immediately, at a specified time after the last active call ends, or after a specified length of time.
MGCP Gateway Fallback

The MGCP gateway maintains a remote connection to a centralized Cisco Unified CallManager cluster
by sending MGCP keepalive messages to the Cisco Unified CallManager server at 15-second intervals.
If the active Cisco Unified CallManager server fails to acknowledge receipt of the keepalive message
within 30 seconds, the gateway attempts to switch over to the next available Cisco Unified CallManager
server.
If none of the Cisco Unified CallManager servers respond, the gateway switches into fallback mode and
reverts to the default H.323 session application for basic call control. H.323 is a standardized
communication protocol that enables dissimilar devices to communicate with each other through use of
a common set of codecs, call setup and negotiating procedures, and basic data transport methods. The
gateway processes calls on its own using H.323 until one of the Cisco Unified CallManager connections
is restored.
Figure 3 illustrates a typical VoIP network topology in which MGCP gateway fallback is supported.
Figure 3 Typical VoIP Network Topology Supporting the MGCP Gateway Fallback Feature

Cisco Unified CallManager 2 Cisco Unified CallManager
1 3
Cisco Unified CallManager M
cluster M M
LAN
WAN
LAN LAN
MGCP/H323 MGCP/H323
Cisco Cisco
IP router router IP
IP phones IP phones
T1/E1 PRI
FXS FXO T1-CAS
POTS PBX PBX phone
Remote site A Remote site B

65634
PSTN
POTS

31
The MGCP Gateway Fallback feature provides the following functionality:

• MGCP gateway fallback support—All active MGCP analog and T1 CAS calls are maintained during
the fallback transition. Callers are unaware of the fallback transition, and the active MGCP calls are
cleared only when the communicating callers hang up. Active MGCP PRI backhaul calls are
released during fallback.
Any transient MGCP calls (that is, calls that are not in the connected state) are cleared at the onset
of the fallback transition and must be attempted again later.
• Basic connection services in fallback mode—Provides basic connection services for IP telephony
traffic that passes through the gateway. When the local MGCP gateway transitions into fallback
mode, the default H.323 session application assumes responsibility for handling new calls. Only
basic two-party voice calls are supported during the fallback period.
Except for ISDN T1 and E1 PRI calls, all the MGCP calls that are active at the time of fallback are
preserved, but transient calls are released. When a user completes (hangs up) an active MGCP call,
the MGCP application handles the on-hook event and clears all call resources.
• Rehome support—Provides a rehome function in the gateway fallback mode that detects the
restoration of a WAN TCP connection to the primary Cisco Unified CallManager server.
When the fallback mode is in effect, the affected MGCP gateway repeatedly tries to open a TCP
connection to a Cisco Unified CallManager server in the prioritized list of call agents. This process
continues until one of the Cisco Unified CallManager servers in the prioritized list responds.
The TCP open request from the MGCP gateway is honored, and the gateway reverts to MGCP mode.
The gateway sends a Restart-in-Progress (RSIP) message to begin registration with the responding
All currently active calls that are initiated and set up during the fallback period are maintained by
the default H.323 session application, except ISDN T1 and E1 PRI calls. Transient calls are released.
After rehome occurs, the new Cisco Unified CallManager assumes responsibility for controlling
new IP telephony activity.
The following types of interfaces on the gateway are supported:
• FXS analog interfaces—For connecting to the PSTN or analog phones
• FXO analog interfaces—For connecting to the PSTN or PBXs
• T1 CAS digital interfaces—For connecting to the PSTN or PBXs
• T1 and E1 PRI digital interfaces—For connecting to PBXs and central offices (COs)

32
MGCP Gateway Registration with Cisco Unified CallManager

Table 2 describes what can happen when either the gateway loses connection to the primary
Cisco Unified CallManager or the gateway also loses connection to all backup Cisco Unified
CallManager servers.
Table 2 Registration Scenarios
Terminology Connection Registration

Gateway connection to primary Cisco Unified CallManager
Failover (also called switchover) Gateway loses connection to Gateway switches over to a
primary Cisco Unified backup.
CallManager.
Switchback Gateway reconnects to primary Gateway switches back to the
Cisco Unified CallManager. primary.
Gateway connection to all Cisco Unified CallManager servers
Fallback Gateway loses connection to Gateway falls back to H.323
primary and all backup call processing.
servers.
Rehome Gateway reconnects to one of the Gateway rehomes, resuming
Cisco Unified CallManager MGCP call processing.
servers.
Any calls at the time of reregistration (even those in a transient state such as call setup) remain
undisturbed. The newly registered Cisco Unified CallManager determines the status of existing calls and
maintains or deletes them as appropriate.
Benefits of Cisco Unified CallManager Switchover and MGCP Gateway Fallback

• Eliminates a potential single point of failure in the VoIP network by allowing you to designate up to
two backup Cisco Unified CallManager servers. Your MGCP voice gateways can continue working
if the primary Cisco Unified CallManager server fails.
• Ensures greater stability in the voice network by preserving existing connections during a
switchover to a backup Cisco Unified CallManager server.
• Prevents call-processing interruptions or dropped calls in the event of a Cisco Unified CallManager
or WAN failure.
SUMMARY STEPS
1. enable
3. ccm-manager redundant-host {ip-address | DNS-name} {ip-address | DNS-name}
4. ccm-manager switchback {graceful | immediate | schedule-time hh:mm | uptime-delay minutes}
5. ccm-manager fallback-mgcp
6. call application alternate

33
7. exit
8. ccm-manager switchover-to-backup
DETAILED STEPS
Command or Action Purpose

Example:
Router> enable
Example:
Step 3 ccm-manager redundant-host {ip-address | Identifies up to two backup Cisco Unified CallManager
DNS-name} [ip-address | DNS-name] servers.
Example:
Router(config)# ccm-manager redundant-host
10.0.0.50
Step 4 ccm-manager switchback {graceful | immediate | Configures switchback mode for returning control to the
schedule-time hh:mm | uptime-delay minutes} primary Cisco Unified CallManager.
• Default is graceful.
Example:
Router(config)# ccm-manager switchback immediate
Step 5 ccm-manager fallback-mgcp Enables the MGCP fallback feature.
Example:
Router(config)# ccm-manager fallback-mgcp
Step 6 call application alternate Specifies that the default voice application takes over if
the MGCP application is not available.
Example:
Router(config)# call application alternate
Step 7 exit Exits global configuration mode and returns to privileged
EXEC mode.
Example:
Step 8 ccm-manager switchover-to-backup Manually redirects the MGCP gateway to the backup
Cisco Unified CallManager server. The switchover to the
backup Cisco Unified CallManager server occurs
Example:
Router# ccm-manager switchover-to-backup
immediately.
Note This command does not switch the gateway to the
backup Cisco Unified CallManager server if you
have set the ccm-manager switchback command
to immediate and the primary Cisco Unified
CallManager server is still running.

34
Configuring MGCP Gateway Fallback and Cisco SRST

Cisco Survivable Remote Site Telephony (SRST) provides Cisco Unified CallManager with fallback
support for Cisco IP phones that are attached to a Cisco router on your local network. Cisco SRST
enables routers to provide call-handling support for Cisco IP phones when they lose connection to
remote primary, secondary, or tertiary Cisco Unified CallManager installations or when the WAN
connection is down.
MGCP gateway fallback is a different feature than SRST, and when MGCP gateway fallback is
configured as an individual feature, it can be used by a PSTN gateway if you configure H.323 (or some
other voice application) as a backup service. To use SRST as your fallback mode on an MGCP gateway,
you must configure SRST and MGCP fallback on the same gateway. MGCP and SRST have had the
capability to be configured on the same gateway since Cisco IOS Release 12.2(11)T.
Cisco SRST Description

Cisco Unified CallManager supports Cisco IP phones at remote sites that are attached to Cisco
multiservice routers across the WAN. Prior to Cisco SRST, when the WAN connection between a router
and the Cisco Unified CallManager failed or when connectivity with Cisco Unified CallManager was
lost for some reason, Cisco Unified IP phones on the network became unusable for the duration of the
failure. Cisco SRST overcomes this problem and ensures that Cisco Unified IP phones offer continuous
(although minimal) service by providing call-handling support for Cisco Unified IP phones directly from
the Cisco SRST router. The system automatically detects a failure and uses Simple Network Auto
Provisioning (SNAP) technology to autoconfigure the branch office router to provide call processing for
Cisco Unified IP phones that are registered with the router. When the WAN link or connection to the
primary Cisco Unified CallManager is restored, call handling reverts back to the primary CiscoUnified
CallManager.
For more information on Cisco SRST, see Overview of Cisco IOS SRST.
Configuring MGCP Gateway Fallback and Cisco SRST

To make outbound calls while in SRST mode on your MGCP gateway, you must configure two fallback
commands on the MGCP gateway. These two commands allow SRST to assume control over the voice
port and over call processing on the MGCP gateway. With Cisco IOS releases prior to 12.3(14)T, you
must configure MGCP gateway fallback by using the ccm-manager fallback-mgcp and call
application alternate commands. With Cisco IOS releases after 12.3(14)T, you must configure MGCP
gateway fallback by using the ccm-manager fallback-mgcp and service commands.
Note You must configure both commands. For instance, your configuration will not work if you only configure
the ccm-manager fallback-mgcp command.
Enabling SRST on an MGCP Gateway

To use SRST as your fallback mode with an MGCP gateway, you must configure both SRST and MGCP
fallback on the same gateway. The following configuration allows SRST to assume control over the voice
port and over call processing on the MGCP gateway.

35
Restrictions
Effective with Cisco IOS Release 12.3(14)T, the call application alternate command has been replaced
by the service command. You can use the service command cin all releases after Cisco IOS Release
12.3(14)T. Both commands are reflected in Step 4.
SUMMARY STEPS
1. enable
3. ccm-manager fallback-mgcp
4. call application alternate [application name]
or
service [alternate | default] service-name location
5. exit
DETAILED STEPS

Step 1 enable Enters privileged EXEC mode. Enter your password if
prompted.
Example:
Router> enable
Example:
Step 3 ccm-manager fallback-mgcp Enables the gateway fallback feature and allows an
MGCP voice gateway to provide call processing services
through SRST or other configured applications when
Example:
Router(config)# ccm-mananger fallback-mgcp
Cisco CallManager is unavailable.

36

Step 4 call application alternate [application name] With Cisco IOS releases prior to 12.3(14)T, the call ap-
or plication alternate command specifies that the default
service [alternate|default] service-name location
voice application takes over if the MGCP application is
not available. The application-name argument is optional
Example: and indicates the name of the specific voice application to
Router(config)# call application alternate use if the application dial peer fails. If a specific applica-
or tion name is not entered, the gateway uses the DEFAULT
Router(config)# service default application.
Or
With Cisco IOS releases after 12.3(14)T, the service
command loads and configures a specific, standalone ap-
plication on a dial peer. The keywords and arguments are
as follows:
• alternate—Optional. Alternate service to use if the
service that is configured on the dial peer fails.
• default—Optional. Specifies that the default service
(“DEFAULT”) on the dial peer is used if the alternate
service fails.
• service-name—Name that identifies the voice appli-
cation.
• location—Directory and filename of the Tcl script or
VoiceXML document in URL format. For example,
flash memory (flash:filename), a TFTP (tftp://../
filename) or an HTTP server (http://../filename) are
valid locations.
Step 5 exit Exits global configuration mode and returns to privileged
EXEC mode.
Example:
Verifying Cisco Unified CallManager Switchover and MGCP Gateway Fallback

SUMMARY STEPS
2. show ccm-manager
3. show ccm-manager fallback-mgcp
DETAILED STEPS

Use the show running-config command to verify configuration of the Cisco Unified CallManager
failover options, for example:
...

37
ccm-manager switchback immediate

ccm-manager fallback-mgcp
ccm-manager redundant-host 10.0.0.50
ccm-manager mgcp
.
.
.
call application alternate DEFAULT
!
Step 2 show ccm-manager
Use the show ccm-manager command to verify the Cisco Unified CallManager failover options.
The following example shows one Cisco Unified CallManager backup server is configured. Switchback
mode is set for immediate return to the primary Cisco Unified CallManager server as soon as the server
is available.
Router# show ccm-manager
MGCP Domain Name: router.cisco.com

Total number of host: 2
Priority Status Host
===================================================
Primary Registered 10.0.0.201
First backup Backup polling 10.0.0.50
Second backup Undefined
Current active CallManager: 10.0.0.201

Current backup CallManager: 10.0.0.50
Redundant link port: 2428
Failover Interval: 30 seconds
Keepalive Interval: 15 seconds
Last keepalive sent: 00:20:18 (elapsed time: 00:00:06)
Last MGCP traffic time: 00:20:18 (elapsed time: 00:00:06)
Last switchover time: None
Switchback mode: Immediate

38
Step 3 show ccm-manager fallback-mgcp

Use the show ccm-manager fallback-mgcp command to verify whether MGCP fallback is enabled and
whether it is active or not (on or off), for example:
Router# show ccm-manager fallback-mgcp
Current active CallManager: 10.00.71.29

MGCP Fallback mode: Enabled/OFF
Last MGCP Fallback start time: 00:00:00
Last MGCP Fallback end time: 00:00:00
Note For a description of the fields displayed in these output examples, see the Cisco IOS Voice Command
Reference.
Configuring POTS Dial Peers on MGCP Gateways

Perform this task to enable the POTS dial peers on your MGCP gateway to communicate with
When you have finished this procedure, the voice gateway is ready to communicate with Cisco Unified
CallManager. It periodically sends out messages attempting to establish a connection. When the Cisco
Unified CallManager configuration is complete, the connection should automatically establish itself.
You should not have to make any further changes on the MGCP gateway.
Restrictions for POTS Dial Peers on MGCP Gateways

• All dial-plan configuration elements are controlled by Cisco Unified CallManager and should not
be configured on the MGCP gateway for MGCP-managed endpoints (that is, any endpoint with an
application mgcpapp command in its associated dial-peer).
• Do not use the destination-pattern or session target dial-peer configuration commands or the
connection voice-port configuration command on the MGCP gateway, unless you are configuring
MGCP gateway fallback. To configure MGCP gateway fallback, you must configure the H.323 dial
peers with the destination-pattern and session target dial-peer configuration commands.
• Direct inward dial (DID) is required for T1/E1 PRI dial peers.
• Do not use the application mgcpapp command in dial peers that support PRI backhaul or BRI
backhaul.
SUMMARY STEPS
1. enable
3. dial-peer voice tag pots
4. application mgcpapp
5. direct-inward-dial
6. port slot/subunit/port
7. exit

39
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 dial-peer voice tag pots Designates the specified dial peer as a POTS device and
enters dial-peer configuration mode.
Example:
Router(config)# dial-peer voice 101 pots
Step 4 application mgcpapp Enables MGCP on the dial peer.
Note Do not use this command in dial peers that support
Example: PRI backhaul or BRI backhaul.
Router(config-dial-peer)# application mgcpapp
Step 5 direct-inward-dial (Optional) Enables the direct inward dialing (DID) call
treatment for an incoming called number.
Example: • Required for T1/E1 PRI dial peers.
Router(config-dial-peer)# direct-inward-dial
Step 6 port slot/subunit/port Binds the MGCP application to the specified voice port.
• Slot and port syntax is platform-dependent; type ? to
Example: determine.
Router(config-dial-peer)# port 1/0/1
Step 7 exit Exits dial-peer configuration mode and returns to global
configuration mode.
Example:
Router(config-dial-peer)# exit
Verifying Dial Peer Configuration for MGCP Gateways

SUMMARY STEPS
2. show dial-peer voice tag
3. show voice port port

40
DETAILED STEPS

Use the show running-config command to verify the dial peer configuration.
The following example shows two Foreign Exchange Office (FXO) ports and one Foreign Exchange
Station (FXS) port that are configured to run under MGCP control. Slot numbering and port numbering
begin at 0.
! FXO port
dial-peer voice 1 pots
application mgcpapp
port 1/0/0
!
! FXO port
application mgcpapp
port 1/0/1
!
! FXS port
application mgcpapp
port 1/1/0
The following example shows a configuration on MGCP voice gateways for T1 CAS with
e&m-wink-start emulation.
ccm-manager mgcp
!
controller T1 1/0
framing esf
linecode b8zs
ds0-group 1 timeslots 1-24 type e&m-wink-start
!
voice-port 1/0:1
!
application mgcpapp
destination-pattern 91..........
port 1/0:1
The following example shows a configuration on MGCP voice gateways for FXS ports.
application mgcpapp
destination-pattern 555-1212
port 1/0/0
The following example shows a configuration on MGCP voice gateways for FXO ports.
application mgcpapp
destination-pattern 527....
prefix 527
port 1/1/1
The following example shows a configuration on MGCP gateways for VoIP calls, when the fallback
feature is used.
dial-peer voice 555 voip
application mgcpapp

41
destination pattern 555...

incoming-called-number 444...
session-target ipv4:172.20.21.8
codec g711ulaw
Note When you configure MGCP gateway fallback support, the POTS dial peer must include the
application mgcpapp command and must specify the voice port. For the default session
application to take over during fallback, you must also configure a destination pattern.
Step 2 show dial-peer voice

Use the show dial-peer voice command to verify the configuration of the POTS dial peer, for example:
Router# show dial-peer voice 1000
VoiceEncapPeer1000
information type = voice,
description = `',
tag = 1000, destination-pattern = `',
answer-address = `', preference=0,
numbering Type = `unknown'
group = 1000, Admin state is up, Operation state is down,
incoming called-number = `', connections/maximum = 0/unlimited,
DTMF Relay = disabled,
huntstop = disabled,
in bound application associated: 'mgcpapp'
out bound application associated: ''
dnis-map =
permission :both
incoming COR list:maximum capability
outgoing COR list:minimum requirement
type = pots, prefix = `',
forward-digits default
session-target = `', voice-port = `',
direct-inward-dial = disabled,
digit_strip = enabled,
register E.164 number with GK = TRUE
Connect Time = 0, Charged Units = 0,
Successful Calls=0, Failed Calls=0, Incomplete Calls=0
Accepted Calls = 0, Refused Calls = 0,
Last Disconnect Cause is "",
Last Disconnect Text is "",
Last Setup Time = 0.
Step 3 show voice port

Use the show voice port command to verify that the voice port is operational. The following is sample
output from a Cisco 3600 series router with an FXS analog voice port:
Router# show voice port 1/0/0
Foreign Exchange Office 1/0/0 Slot is 1, Sub-unit is 0, Port is 0

Type of VoicePort is FXO
Operation State is DORMANT
Administrative State is UP
No Interface Down Failure
Description is not set
Noise Regeneration is enabled
Non Linear Processing is enabled
Non Linear Mute is disabled
Non Linear Threshold is -21 dB
Music On Hold Threshold is Set to -38 dBm

42
In Gain is Set to 0 dB
Out Attenuation is Set to 3 dB
Echo Cancellation is enabled
Echo Cancellation NLP mute is disabled
Echo Cancellation NLP threshold is -21 dB
Echo Cancel Coverage is set to 8 ms
Playout-delay Mode is set to default
Playout-delay Nominal is set to 60 ms
Playout-delay Maximum is set to 200 ms
Playout-delay Minimum mode is set to default, value 40 ms
Playout-delay Fax is set to 300 ms
Connection Mode is normal
Connection Number is not set
Initial Time Out is set to 10 s
Interdigit Time Out is set to 10 s
Call Disconnect Time Out is set to 60 s
Ringing Time Out is set to 180 s
Wait Release Time Out is set to 30 s
Companding Type is u-law
Region Tone is set for US
Analog Info Follows:

Currently processing none
Maintenance Mode Set to None (not in mtc mode)
Number of signaling protocol errors are 0
Impedance is set to 600r Ohm
Station name None, Station number None
Translation profile (Incoming):
Translation profile (Outgoing):
Voice card specific Info Follows:

Signal Type is loopStart
Number Of Rings is set to 1
Supervisory Disconnect is inactive
Answer Supervision is inactive
Hook Status is On Hook
Ring Detect Status is inactive
Ring Ground Status is inactive
Tip Ground Status is inactive
Dial Type is dtmf
Digit Duration Timing is set to 100 ms
InterDigit Duration Timing is set to 100 ms
Pulse Rate Timing is set to 10 pulses/second
InterDigit Pulse Duration Timing is set to 750 ms
Percent Break of Pulse is 60 percent
GuardOut timer is 2000 ms

43
Enabling Single-Point Configuration for MGCP Gateways

When you configure MGCP gateways to support Cisco Unified CallManager, you can use a centralized
TFTP boot directory on a host device in your network to automatically download most of the
configuration in the XML files. Each MGCP gateway in your VoIP network has an associated
gateway-specific configuration that is stored in the centralized TFTP boot directory. A tailored XML file
can be created and downloaded from the TFTP server to your designated MGCP gateway. The
Cisco Unified CallManager server can be configured concurrently as a TFTP server.
When you make changes to the configuration in the database, a message is sent by Cisco Unified
CallManager to the affected MGCP gateway, instructing the gateway devices to download the new XML
configuration file. Each device has an XML parser that interprets the XML file according to its
device-specific requirements. Cisco MGCP gateways, for example, translate the content of the XML file
into specific Cisco IOS commands for local execution.
When an MGCP gateway is first started up, it is preconfigured with the following information or it
obtains the information through Dynamic Host Configuration Protocol (DHCP):
• A unique device identifier, which can be either of the following:
– Specific device name on the Cisco MGCP gateway
– MAC address of the device for gateways that are not using Cisco IOS software
• IP address of the TFTP server in the network and routing information required for access
• Sufficient information for configuration of an IP interface on the device
With this configuration information available at startup, the MGCP gateway downloads the XML file
from the TFTP server. The gateway parses the XML file, converts the information to appropriate
Cisco IOS configuration commands, and configures itself to run in the VoIP network. Finally, the
gateway registers itself with Cisco Unified CallManager using an RSIP message. At that point, the
MGCP gateway is ready for service in the network.
After a successful configuration download, the MGCP gateway saves the running configuration to
nonvolatile random-access memory (NVRAM), which updates the startup configuration. Any
manually-added configuration parameters are also saved to NVRAM if they were not previously saved.
Manually-added configuration parameters are updates to the configuration that were made using the
command-line interface (CLI). Manual configuration updates are separate from the automatic
configuration updates made during the configuration download process.
In the event of a configuration failure, the MGCP gateway attempts to restore its current configuration
by copying the startup configuration from NVRAM into the running configuration. Because this
overwrites the running configuration, any manually-added configuration parameters could be lost if they
were not saved to NVRAM before running the automatic configuration-download process.

44
Figure 4 Single-Point Configuration for Cisco MGCP Gateways
Cisco Unified CallManager cluster
M
M
M
XML file
TFTP server
IP cloud M
MGCP MGCP
Cisco router Cisco router
FXS/FXO
PRI PRI/CAS
82979
PSTN
POTS PBX PBX phone
Prerequisites for Single-Point Configuration for MGCP Gateways

• MGCP should be configured in your VoIP network through the Cisco CallManager web-based
graphical user interface (GUI).
• The IP hostname should match the gateway name that is specified in the Cisco Unified CallManager
configuration.
SUMMARY STEPS
1. enable
3. ccm-manager config server {ip-address | name}
4. ccm-manager config
5. exit

Example:
Router> enable
Example:

45

Step 3 ccm-manager config server {ip-address | Specifies the TFTP server by IP address or logical name.
name}
Example:
Router(config)# ccm-manager config server
10.10.1.10
Step 4 ccm-manager config Enables the gateway to be configured by a centralized XML
file and triggers the gateway to download a new configuration.
Example:
Router(config)# ccm-manager config
Example:
Verifying Single-Point Configuration for MGCP Gateways

SUMMARY STEPS
2. show ccm-manager config-download
DETAILED STEPS

Use the show running-config command to verify the single-point download configuration, for example:
...
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.10.1.10
ccm-manager config
!
Step 2 show ccm-manager config-download
Use the show ccm-manager config-download command to verify the download status. The output
indicates that four downloads were successful.
Router# show ccm-manager config-download
Configuration Auto-download Information

=======================================
Current version-id: {1645327B-F59A-4417-8E01-7312C61216AE}
Last config-downloaded:00:00:49
Current state: Waiting for commands
Configuration Download statistics:
Download Attempted : 4
Download Successful : 4

46
Download Failed : 0
Configuration Attempted : 1
Configuration Successful : 1
Configuration Failed(Parsing): 0
Configuration Failed(config) : 0
Last config download command: New Registration
Configuring Multicast Music-on-Hold Support for Cisco Unified CallManager

This section describes how to configure your gateway to provide music to customers on hold.
Prerequisites for Multicast Music-on-Hold (MOH)

The default router in the network for handling multicast traffic must have the following enabled:
• Multicast routing
• A multicast routing protocol, for example Protocol Independent Multicast (PIM) or Distance Vector
Multicast Routing Protocol (DVMRP)
• An IP routing protocol, for example Routing Information Protocol (RIP) or Open Shortest Path First
(OSPF)
• Cisco CallManager 3.1 or higher
Multicast Music-on-Hold
The Music-on-Hold (MOH) feature enables you to subscribe to a music streaming service when you are
using a Cisco IOS MGCP voice gateway. Music streams from an MOH server to the voice interfaces of
on-net and off-net callers that have been placed on hold. Cisco CallManager supports the capability to
place callers on hold with music supplied from a streaming multicast MOH server. This integrated
multicast capability is implemented through the H.323 signaling in Cisco CallManager.
By means of a preconfigured multicast address on the gateway, the gateway can “listen” for Real-Time
Transport Protocol (RTP) packets that are broadcast from a default router in the network and can relay
the packets to designated voice interfaces in the network. Whenever a called party places a calling party
on hold, Cisco CallManager requests the MOH server to stream RTP packets to the “on-hold” interface
through the preconfigured multicast address. In this way, RTP packets are relayed to appropriately
configured voice interfaces that have been placed on hold. When you configure a multicast address on a
gateway, the gateway sends an Internet Gateway Management Protocol (IGMP) “join” message to the
default router, indicating to the default router that the gateway is ready to receive RTP multicast packets.
Multiple MOH servers can be present in the same network, but each server must have a different Class D
IP address, and the address must be configured in Cisco CallManager and the MGCP voice gateways.

47
SUMMARY STEPS
1. enable
3. ccm-manager music-on-hold
4. ccm-manager music-on-hold bind interface
5. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 ccm-manager music-on-hold Enables music-on-hold.
Example:
Router(config)# ccm-manager music-on-hold
Step 4 ccm-manager music-on-hold bind interface (Optional) Binds the multicast MOH feature to a designated
interface.
Example:
Router(config)# ccm-manager music-on-hold bind
async
Example:
Verifying Music-on-Hold
SUMMARY STEPS
2. show ccm-manager music-on-hold
DETAILED STEPS

Use the show running-config command to verify the MOH configuration, for example:

48

...
ccm-manager mgcp
ccm-manager config
!
Step 2 show ccm-manager music-on-hold
Use the show ccm-manager music-on-hold command to display information about the currently active
MOH sessions, for example:
Router# show ccm-manager music-on-hold
Multicast RTP Packets Call Incoming

Address Port In/Out ID Protocol Interface
10.10.20.22 16256 3000/3000 1 IGMP fe0/0
Configuring MLPP Service on Cisco MGCP Gateways

Perform this task to configure the MGCP package capability for MLPP.
Note If you downloaded the default configuration file from TFTP, you do not need to manually configure
MLPP on the MGCP gateway. The MLPP configuration is contained in the default configuration.
Prerequisites
• Cisco IOS Release 12.3(11)T or later
• Cisco CallManager 4.0 or later
• DSPWare 4.0
• Telogy DSP4 (Catalyst 6000 switches)
• Preemptions and precedences should be configured in Cisco CallManager. Interfaces, dial peers,
voice ports, controllers, framing, and line codes should also be configured.
• Cisco Catalyst 6500 series and Cisco 7600 series Communication Media Module (CMM) requires
WS-SVC-CMM-6T1 port adapter.
Restrictions
• Supported only for MGCP endpoints over T1 CAS (E&M wink start) and T1 PRI (backhaul).
• Supported only by Cisco CallManager; does not work with other call agents.
• Conferenced call legs are not supported for preemption with Cisco CallManager.

49
• H.323, FXS, and FXO endpoints are not supported.

• Not supported for calls that originate or terminate in the gateway when the gateway is in H.323
fallback mode.
MLPP Overview
Multilevel Precedence and Preemption (MLPP) is a service that allows authorized users to preempt lower
priority voice calls to targeted stations or fully subscribed shared resources such as TDM trunks or
conference bridges. This capability ensures high-ranking personnel of communication to critical
organizations and personnel during network stress situations such as a national emergency. MLPP
enables the voice gateway to interoperate with other MLPP-capable networks for call preemption and
precedence. MLPP is supported only for MGCP endpoints over T1 CAS (E&M wink start) and T1 PRI
using the backhaul feature.
MLPP service applies only to the subscribers and network resources within a specific domain.
Connections and resources for a call from an MLPP subscriber are marked with a precedence level and
domain identifier. A call can only be preempted by calls of higher precedence from MLPP users in the
same domain. The Cisco CallManager or defense switched network (DSN) switch sets the maximum
precedence level of a subscriber at subscription time.
For more information about MLPP, see the “Multilevel Precedence and Preemption” chapter in the
Cisco CallManager Features and Services Guide, Release 4.0(1).
MLPP Call Treatment During Cisco CallManager Switchover or Fallback
When a Cisco CallManager server fails during the processing of an MLPP call, the call is treated as a
transient call and is dropped. The gateway releases the trunks and does a switchover to the backup
Cisco CallManager server or falls back to H.323 mode, depending on the availability of the backup
server. All currently connected MLPP calls are preserved during the switchover, switchback, or fallback
process. After the gateway reregisters with Cisco CallManager, call precedence and domain are
preserved. During fallback, an incoming MLPP call is treated as a routine priority call.
SUMMARY STEPS
1. enable
3. mgcp package-capability pre-package
4. exit

50
DETAILED STEPS

• Enter your password if prompted.
Example:
Router> enable
Example:
Step 3 mgcp package-capability pre-package Enables MLPP as an MGCP package capability type on the
voice gateway.
Example:
Router(config)# mgcp package-capability
pre-package
Step 4 exit Exits to privileged EXEC mode.
Example:
Configuring Fallback when Using MLPP on T1 CAS

When the gateway is in fallback mode, the precedence digit must be stripped from the dial string for T1
CAS calls. Perform this task to configure SRST to handle stripping the precedence digit.
Note For information on configuring digit stripping options for your specific dial plan, see the “Setting Up
Call Handling” chapter in the Cisco Survivable Remote Site Telephony Version 3.2 System
Administration Guide.
SUMMARY STEPS
1. enable
3. call-manager-fallback
4. ip source-address ip-address [port port] [any-match | strict-match]
5. max-dn max-directory-numbers
6. max-ephones max-phones
7. dialplan-pattern tag pattern extension-length length [extension-pattern extension-pattern]
[no-reg]
8. translate {called | calling} translation-rule-tag
9. end

51
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 call-manager-fallback Enters call-manager-fallback configuration mode.
Example:
Router(config)# call-manager-fallback
Step 4 ip source-address ip-address [port port] Enables the voice gateway to receive messages from the
[any-match | strict-match] Cisco IP phones through the specified IP addresses and
provides for strict IP address verification.
Example:
Router(config-cm-fallback)# ip source-address
10.10.200.23 port 2000
Step 5 max-dn max-directory-numbers Sets the maximum number of directory numbers or
virtual voice ports that can be supported by the voice
gateway. The maximum number is platform dependent.
Example:
Router(config-cm-fallback)# max-dn 12
Step 6 max-ephones max-phones Configures the maximum number of Cisco IP phones
that can be supported by the voice gateway. The
maximum number is platform dependent.
Example:
Router(config-cm-fallback)# max-ephones 10
Step 7 dialplan-pattern tag pattern extension-length Creates a global prefix that can be used to expand the
length [extension-pattern extension-pattern] abbreviated extension numbers into fully qualified E.164
[no-reg]
numbers.
Example:
Router(config-cm-fallback)# dialplan-pattern 1
[A-D].... extension-length 4
Step 8 translate {called | calling} translation-rule-tag Applies a translation rule to modify the phone number
dialed or received by any Cisco IP phone user while
Cisco CallManager fallback is active.
Example:
Router(config-cm-fallback)# translate calling 1
Step 9 end Exits to privileged EXEC mode.
Example:
Router(config-cm-fallback)# end

52
Verifying MLPP Configuration

SUMMARY STEPS
2. show mgcp
DETAILED STEPS
Step 1 Use the show running-config command to verify the configuration of the MGCP package, for example:
...
mgcp
mgcp call-agent OTHERCLUSTER 2427 service-type mgcp version 0.1
mgcp rtp unreachable timeout 1000 action notify
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
mgcp package-capability pre-package
no mgcp timer receive-rtcp
mgcp sdp simple
no mgcp validate domain-name
mgcp fax t38 inhibit
mgcp rtp payload-type g726r16 static
!
mgcp profile default
!
Step 2 Use the show mgcp command to display the MGCP configuration details, for example:
Router# show mgcp
MGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONE
MGCP call-agent: 172.18.195.147 2300 Initial protocol service is SGCP 1.5
MGCP block-newcalls DISABLED
MGCP send SGCP RSIP:forced/restart/graceful DISABLED, disconnected ENABLED
MGCP quarantine mode discard/step
MGCP quarantine of persistent events is ENABLED
MGCP dtmf-relay for VoIP disabled for all codec types
MGCP dtmf-relay voaal2 codec all
MGCP voip modem passthrough mode: NSE, codec: g711ulaw, redundancy: DISABLED,
MGCP voaal2 modem passthrough mode: NSE, codec: g711ulaw
MGCP TSE payload: 100
MGCP T.38 Named Signalling Event (NSE) response timer: 200
MGCP Network (IP/AAL2) Continuity Test timer: 3000
MGCP 'RTP stream loss' timer: 2
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 DISABLED, MGCP endpoint offset DISABLED
MGCP simple-sdp DISABLED
MGCP undotted-notation DISABLED
MGCP codec type g711ulaw, MGCP packetization period 20

53
Configuration Examples for MGCP Gateway Support for Cisco CallManager
MGCP JB threshold lwm 30, MGCP JB threshold hwm 150

MGCP LAT threshold lmw 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 IP ToS low delay disabled, MGCP IP ToS high throughput disabled
MGCP IP ToS high reliability disabled, MGCP IP ToS low cost disabled
MGCP IP RTP precedence 5, MGCP signaling precedence: 3
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 pre-package
Configuration Examples for MGCP Gateway Support for

Cisco CallManager
This section provides the following configuration examples:
• MGCP Gateway with T1 CAS: Example, page 54
• MGCP Gateway with T1 PRI: Example, page 56
• Multicast Music-on-Hold: Example, page 58
• MLPP (Cisco 2801): Example, page 59
• MLPP (Cisco 2621): Example, page 61
Note To view relevant configuration examples, go to the Cisco Systems Technologies website at
http://cisco.com/en/US/tech/index.html. From the website, select Voice > IP Telephony/VoIP, then
click Technical Documentation > Configuration Examples.
MGCP Gateway with T1 CAS: Example

The following example shows MGCP fallback configured on a voice gateway with T1 CAS.
Current configuration : 2181 bytes
!
version 12.2
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Test-3640a
!
logging rate-limit console 10 except errors
!
memory-size iomem 25
voice-card 3
!
ip subnet-zero
!
no ip domain-lookup
ip domain-name test.com

54
!
no ip dhcp-client network-discovery
frame-relay switching
mgcp
mgcp rtp unreachable timeout 1000
call rsvp-sync
!
ccm-manager mgcp
!
controller T1 3/0
framing esf
linecode b8zs
ds0-group 1 timeslots 1 type e&m-wink-start
!
controller T1 3/1
framing sf
linecode ami
!
interface FastEthernet0/0
ip address 10.0.0.21 255.255.255.224
duplex auto
speed auto
!
interface Serial0/0
ip address 10.0.0.21 255.255.255.224
encapsulation frame-relay
no keepalive
frame-relay interface-dlci 300
!
interface Serial0/1
no ip address
shutdown
clockrate 2000000
!
interface Ethernet2/0
ip address 10.0.0.21 255.255.255.224
half-duplex
!
interface TokenRing2/0
no ip address
shutdown
ring-speed 16
!
ip classless
ip route 10.0.0.21 255.255.255.0 14.0.0.1
ip route 10.0.0.21 255.255.255.0 14.0.0.1
ip route 10.0.0.21 255.255.255.0 14.0.0.1
ip route 10.0.0.21 255.255.255.0 14.0.0.1
ip route 10.0.0.21 255.255.255.255 Ethernet2/0
ip route 10.0.0.21 255.255.255.255 Ethernet2/0
no ip http server
!
snmp-server manager
!
voice-port 1/0/0
!
voice-port 1/0/1

55
!
voice-port 1/1/0
!
voice-port 1/1/1
!
voice-port 3/0:1
!
dial-peer cor custom
!
application mgcpapp
destination-pattern 4301
port 1/1/0
!
application mgcpapp
port 1/1/1
!
session target ipv4:10.0.0.21
codec g711ulaw
!
application mgcpapp
port 3/0:1
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
login
end
Note If the ccm-manager config command is enabled and you separate the MGCP and H.323 dial peers under
different tags, make sure that the MGCP dial peers are configured before the H.323 dial peers.
MGCP Gateway with T1 PRI: Example

The following example shows MGCP fallback configured on a voice gateway with T1 PRI ports.
version 12.2
no parser cache
service timestamps debug datetime msec
service timestamps log datetime msec
!
hostname voice-3640
!
!
voice-card 1
!
ip subnet-zero
!
no ip domain-lookup
!

56
mgcp
mgcp call-agent 172.16.240.124 2427 service-type mgcp version 0.1
mgcp modem passthrough voip mode cisco
!
ccm-manager redundant-host CM-B
ccm-manager mgcp
ccm-manager config server cm-a
ccm-manager config
!
controller T1 1/0
framing esf
linecode b8zs
pri-group timeslots 1-24 service mgcp
!
controller T1 1/1
framing esf
linecode b8zs
!
interface Serial1/0:23
no ip address
no logging event link-status
isdn switch-type primary-ni
isdn incoming-voice voice
isdn T306 30000
isdn bind-l3 ccm-manager
no cdp enable
!
voice-port 1/0:23
!
application mgcpapp
direct-inward-dial
port 1/0:23
!
application mgcpapp
direct-inward-dial
port 1/1:23
!
destination-pattern 16.....
direct-inward-dial
port 1/0:23
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
login
!
end
Note DID is required for T1/E1 PRI dial peers.

57
Multicast Music-on-Hold: Example

The following example shows multicast MOH configured for an MGCP voice gateway:
version 12.2
no parser cache
!
hostname voice-3640
!
!
voice-card 1
!
ip subnet-zero
!
ip domain-name test.com
!
mgcp
call rsvp-sync
!
ccm-manager mgcp
ccm-manager config
!
controller T1 2/0
framing sf
linecode ami
ds0-group 0 timeslots 1 type e&m-wink-start
!
controller T1 2/1
framing sf
linecode ami
!
ip address 10.0.0.21 255.255.255.0
no ip mroute-cache
duplex auto
speed auto
no cdp enable
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 2/0:0
!
!

58

application mgcpapp
port 1/0/0
!
application mgcpapp
port 2/0:0
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
login
!
no scheduler max-task-time
scheduler allocate 4000 4000
!
end
MLPP (Cisco 2801): Example

The following configuration includes both MLPP T1 CAS and T1 PRI.
Current configuration :1851 bytes
!
version 12.3
!
hostname 2801_router
!
boot-start-marker
boot-end-marker
!
!
no network-clock-participate wic 1
network-clock-participate wic 2
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
no aaa new-model
ip subnet-zero
ip cef
!
!
!
no ftp-server write-enable
voice-card 0
!
!
!
ccm-manager mgcp
!
!
controller T1 2/0

59
framing esf
clock source internal
linecode b8zs
!
controller T1 2/1
framing esf
linecode b8zs
pri-group timeslots 1,24 service mgcp
!
!
!
ip address 192.168.12.38 255.255.255.0
duplex auto
speed auto
!
no ip address
shutdown
duplex auto
speed auto
!
no ip address
isdn bind-l3 ccm-manager
no cdp enable
!
ip classless
ip http server
!
!
!
control-plane
!
!
voice-port 1/0
!
voice-port 1/1
!
voice-port 2/0:1
!
voice-port 2/1:23
!
mgcp
mgcp sdp simple
!
!
!
!
application mgcapp

60
port 2/0:1
!
!
line con 0
line aux 0
line vty 0 4
login
!
end
MLPP (Cisco 2621): Example

!
version 12.3
!
hostname 2621-other
!
boot-start-marker
boot system flash:c2600-ipvoice-mz
boot-end-marker
!
logging buffered 10000000 debugging
enable password lab
!
voice-card 1
!
no aaa new-model
ip subnet-zero
ip tcp synwait-time 13
!
!
ip domain name sample-vlan200.cisco.com
ip host demo 10.69.1.129
ip name-server 10.10.100.100
!
!
voice call carrier capacity active
!
!
ccm-manager mgcp
ccm-manager config server OTHER
ccm-manager config
!
!
controller T1 1/0
framing esf
crc-threshold 320
linecode b8zs
!
controller T1 1/1
framing esf
crc-threshold 320

61

linecode b8zs
!
!
ip address 10.10.200.23 255.255.255.0
duplex auto
speed auto
!
no ip address
shutdown
duplex auto
speed auto
!
ip classless
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0
ip http server
!
control-plane
!
!
call application alternate default
!
!
voice-port 1/0:1
!
voice-port 1/1:1
!
mgcp
mgcp call-agent OTHER 2427 service-type mgcp version 0.1
mgcp package-capability pre-package
mgcp sdp simple
no mgcp validate domain-name
!
!
!
!
!
application mgcpapp
port 1/0:1
!
application mgcpapp
port 1/1:1
!
preference 1
destination-pattern 100.
direct-inward-dial
port 1/0:1

62
Where to Go Next
forward-digits all
!
!
call-manager-fallback
max-conferences 4
ip source-address 10.10.200.23 port 2000
max-ephones 10
max-dn 10
dialplan-pattern 1 [A-D].... extension-length 4
translate calling 1
!
!
line con 0
exec-timeout 0 0
line aux 0
exec-timeout 0 0
no exec
transport input all
line vty 0 4
password lab
login
!
exception core-file core_2621 compress
exception region-size 65536
exception dump 10.10.100.101
!
!
end
Where to Go Next
• To configure conferencing, transcoding, and MTP support on a Cisco IOS gateway, see “Configuring
Enhanced Conferencing and Transcoding for Voice Gateway Routers” on page 65.
• To enable MGCP PRI backhaul support, see “Configuring MGCP PRI Backhaul and T1 CAS
Support for Cisco Unified CallManager” on page 111.
• To enable MGCP BRI backhaul support, see “Configuring MGCP-Controlled Backhaul of
BRI Signaling in Conjunction with Cisco Unified CallManager” on page 127.
• To download region-specific tones and their associated frequencies, amplitudes, and cadences, see
“Configuring Tone Download to MGCP Gateways” on page 143.

63
• “Cisco Unified CallManager and Cisco IOS Interoperability Features Roadmap” on
page 9—Describes how to access Cisco Feature Navigator; also lists and describes, by Cisco IOS
release, Cisco CallManager and Cisco IOS interoperability features.
• “Overview of Cisco Unified CallManager and Cisco IOS Interoperability” on page 13—Describes
basics of underlying technology and lists related documents.
• Configuring Media Gateway Control Protocol and Related Protocols—Describes MGCP concepts
and configuration procedures.
• Configuring the Cisco IOS MGCP Gateway—Describes the basics of configuring an MGCP
gateway to support Cisco CallManager.
• How to Configure MGCP with Digital PRI and Cisco CallManager—Describes how to configure
MGCP with PRI.
• MGCP Gateway Fallback Transition to Default H.323 Session Application—Describes how to
enable an MGCP gateway to fallback to an H323 session application when the WAN connection to
the primary Cisco CallManager server is lost, and no backup Cisco CallManager server is available.
• MGCP with Digital CAS and Cisco CallManager Configuration Example—Describes how to use
MGCP between a Cisco IOS gateway and a Cisco CallManager Media Convergence Server (MCS).

64
Configuring Enhanced Conferencing and
Transcoding for Voice Gateway Routers
This chapter describes the steps for enabling conferencing and transcoding support on Cisco IOS voice
gateways in a Cisco Unified CallManager network. This feature provides enhanced multiservice support
by enabling audioconference and transcode functions in voice gateway routers. Locating conference
resources in the branch reduces WAN utilization and using transcoding services reduces bandwidth
needs resulting in tangible cost savings.
Digital signal processor (DSP) farms provide conferencing and transcoding services using DSP
resources on high-density digital voice/fax network modules.
Feature History for Out-of-Band to In-Band DTMF Relay for Voice Gateway Routers
12.3(14)T Support was added for the PVDM2 on the Cisco 2800 series and
Cisco 3800 series voice gateway routers.
Feature History for Enhanced Conferencing and Transcoding for Voice Gateway Routers
12.3(8)T This feature was introduced for the NM-HDV2, NM-HD-1V, NM-HD-2V,
and NM-HD-2VE.
12.3(11)T Support was added for the PVDM2 on the Cisco 2800 series and
Cisco 3800 series voice gateway routers.
Feature History for Conferencing and Transcoding for Voice Gateway Routers
12.1(5)YH This feature was introduced for the NM-HDV-FARM on the Cisco VG200.
12.2(13)T This feature was integrated into Cisco IOS Release 12.2(13)T and support
was added for the NM-HDV on the Cisco 2600 series, Cisco 3600 series,
Cisco 3700 series, and Cisco VG200.
12.3(2)XE Support was added for the PVDM-256K on the Cisco 1751, Cisco 1751-V,
and Cisco 1760.
12.3(8)T Support for the PVDM-256K on the Cisco 1751, Cisco 1751-V, and
Cisco 1760 was integrated into Cisco IOS Release 12.3(8)T.

65
Configuring Enhanced Conferencing and Transcoding for Voice Gateway Routers
Contents
Contents
• Prerequisites for Conferencing and Transcoding for Voice Gateway Routers, page 66
• Information About Conferencing and Transcoding for Voice Gateway Routers, page 68
• How to Configure Conferencing and Transcoding for Voice Gateway Routers, page 77
• Configuration Examples for Conferencing and Transcoding, page 98
Prerequisites for Conferencing and Transcoding for Voice

Gateway Routers
DSP Resources
The router must be equipped with one or more of the following network modules or voice DSP modules
to provide DSP resources for conferencing, transcoding, and hardware MTP services:
• NM-HD-1V
• NM-HD-2V
• NM-HD-2VE
• NM-HDV2
• NM-HDV2-1T1/E1
• NM-HDV2-2T1/E1
• NM-HDV 1

66
Prerequisites for Conferencing and Transcoding for Voice Gateway Routers
• NM-HDV-FARM 1
• PVDM-256K 1
• PVDM2 on Cisco 2800 series or Cisco 3800 series
1. Does not support hardware MTP services.
Cisco Unified CallManager and Cisco IOS Release

• Minimum software requirements for type of network or voice module:
Module Cisco Unified CallManager version Cisco IOS Release

NM-HDV2, Cisco CallManager 3.3(4) or later for Cisco IOS Release 12.3(8)T or later
NM-HD-1V/2V/2VE conferencing and transcoding,
Cisco Unified CallManager 4.0(1) or
later for MTP
PVDM2 (Cisco 2800 series) Cisco CallManager 3.3(5) or later for Cisco IOS Release 12.3(8)T4 or later
conferencing and transcoding,
Cisco Unified CallManager 4.0(2a)
or later for MTP
PVDM2 (Cisco 3800 series) Cisco CallManager 3.3(5) or later for Cisco IOS Release 12.3(11)T or later
conferencing and transcoding,
Cisco Unified CallManager 4.0(2a)
or later for MTP
NM-HDV Cisco CallManager 3.2(2c) or later Cisco IOS Release 12.2(13)T or later
• Conference bridge, transcoder, and MTP services must be configured in Cisco Unified CallManager.
See the following chapters in the Cisco Unified CallManager Administration Guide:
Release 4.0(1):
– “Conference Bridge Configuration”
– “Media Termination Point Configuration”
– “Transcoder Configuration”
Release 3.3(4):
– “Conference Bridge Configuration”
Codecs
End-user devices must be equipped with one of the following codecs:
Codec Packetization Periods for Transcoding (ms)

G.711 a-law, G.711 u-law 10, 20, or 30
G.729, G.729A, G.729B, G.729AB 10, 20, 30, 40, 50, or 60
1
GSM EFR, GSM FR 20
1. Supported for NM-HDV2 and NM-HD-1V/2V/2VE only

67
Restrictions for Conferencing and Transcoding for Voice Gateway Routers
Restrictions for Conferencing and Transcoding for Voice

Gateway Routers
• DSP farm services communicate with Cisco Unified CallManager using Skinny Client Control
Protocol (SCCP); other protocols are not supported.
• DSP farm services are not supported for Cisco Survivable Remote Site Telephony (SRST) or
Cisco Unified CallManager Express.
• DSP farm services cannot be enabled for a slot on the Cisco 1700 series so the dsp services dspfarm
command is not supported and cannot be configured for a voice card on the Cisco 1700 series.
• Conferencing is not supported on a Cisco 3640 using the NM-HD-1V, NM-HD-2V, or NM-HD-2VE.
• Simultaneous use of DSP farm services on the NM-HDV and NM-HDV2 is not supported.
• Hardware MTPs are not supported on the NM-HDV or NM-HDV-FARM.
• Hardware MTPs support only G.711 a-law and G.711 u-law. If you configure a profile as a hardware
MTP, and you want to change the codec to other than G.711, you must first remove the hardware
MTP by using the no maximum sessions hardware command.
• Software MTPs are supported on the NM-HDV only if the dsp services dspfarm command is not
enabled on the voice card.
• Only one codec is supported for each MTP profile. To support multiple codecs, you must define a
separate MTP profile for each codec.
• If an MTP call is received but MTP is not configured, transcoding is used if resources are available.
• Dynamic conference and transcoding resource allocation is not supported.
• Fax is not supported for transcoding.
Information About Conferencing and Transcoding for Voice

Gateway Routers
To configure Cisco conferencing and transcoding, you should understand the following concepts:
• DSP Farms, page 69
• DSP Farm Profiles, page 69
• Conferencing, page 69
• Transcoding, page 70
• MTP, page 71
• Conferencing and Transcoding Features on the NM-HDV2 and NM-HD-1V/2V/2VE, page 71
• Conferencing and Transcoding Features on the NM-HDV, page 72
• Conferencing and Transcoding Features on the Cisco 1751 and Cisco 1760, page 72
• Allocation of DSP Resources, page 73

68
Information About Conferencing and Transcoding for Voice Gateway Routers
DSP Farms
A DSP farm is the collection of DSP resources available for conferencing, transcoding, and MTP
services. DSP farms are configured on the voice gateway and managed by Cisco Unified CallManager
through Skinny Client Control Protocol (SCCP).
The DSP farm can support a combination of transcoding sessions, MTP sessions, and conferences
simultaneously. The DSP farm maintains the DSP resource details locally. Cisco Unified CallManager
requests conferencing or transcoding services from the gateway, which either grants or denies these
requests, depending on resource availability. The details of whether DSP resources are used, and which
DSP resources are used, are transparent to Cisco Unified CallManager.
The DSP farm uses the DSP resources in network modules on Cisco routers to provide
voice-conferencing, transcoding, and hardware MTP services.
Note Hardware MTP services are not supported on the NM-HDV.
Tip To determine how many DSP resources your router supports, see the “Allocation of DSP Resources”
section on page 73.
DSP Farm Profiles

DSP-farm profiles are created to allocate DSP-farm resources. Under the profile you select the service
type (conference, transcode, MTP), associate an application, and specify service-specific parameters
such as codecs and maximum number of sessions. A DSP-farm profile allows you to group DSP
resources based on the service type. Applications associated with the profile, such as SCCP, can use the
resources allocated under the profile. You can configure multiple profiles for the same service, each of
which can register with one Cisco Unified CallManager group. The profile ID and service type uniquely
identify a profile, allowing the profile to uniquely map to a Cisco Unified CallManager group that
contains a single pool of Cisco Unified CallManager servers.
Conferencing
Voice conferencing involves adding several parties to a phone conversation. In a traditional
circuit-switched voice network, all voice traffic passes through a central device such as a PBX.
Conference services are provided within this central device. In contrast, IP phones normally send voice
signals directly between phones, without the need to go through a central device. Conference services,
however, require a network-based conference bridge.
In an IP telephony network using Cisco Unified CallManager, the Conferencing and Transcoding for
Voice Gateway Routers feature provides the conference-bridging service. Cisco Unified CallManager
uses a DSP farm to mix voice streams from multiple participants into a single conference-call stream.
The mixed stream is played out to all conference attendees, minus the voice of the receiving attendee.
The following conferencing features are supported:
• A conference can be either of the following types:
– Ad hoc—The person controlling the conference presses the telephone conference button and
adds callers one by one.

69
– Meet me—Participants call in to a central number and are joined in a single conference.
• Participants whose end devices use different codec types are joined in a single conference; no
additional transcoding resource is needed.
This feature provides voice conferencing at the remote site, without the need for access to the central
site (see Figure 5).
Figure 5 Conferencing Service
Headquarters
PSTN Branch
WAN
IP
IP
IP IP
82999
Transcoding
Transcoding compresses and decompresses voice streams to match endpoint-device capabilities.
Transcoding is required when an incoming voice stream is digitized and compressed (by means of a
codec) to save bandwidth, but the local device does not support that type of compression. Ideally, all IP
telephony devices would support the same codecs, but this is not the case. Rather, different devices
support different codecs.
Transcoding is processed by DSPs on the DSP farm; sessions are initiated and managed by Cisco Unified
CallManager. Cisco Unified CallManager also refers to transcoders as hardware MTPs.
This feature provides transcoding at the remote site, without the need for access to the central site
(see Figure 6).

70
Figure 6 Transcoding Service
Headquarters
Branch
WAN
IP
IP
IP IVR
88001
MTP
A Media Termination Point (MTP) bridges the media streams between two connections allowing
Cisco Unified CallManager to relay calls that are routed through SIP or H.323 endpoints.
The following MTP resources are supported for Cisco Unified CallManager 4.0 and later releases:
• Software MTP—Software-only implementation that does not use a DSP resource for endpoints
using the same codec and the same packetization time.
• Hardware MTP—Hardware-only implementation that uses a DSP resource for endpoints using the
same G.711 codec but a different packetization time. The repacketization requires a DSP resource
so it cannot be done by software only. Cisco Unified CallManager also uses the term software MTP
when referring to a hardware MTP.
For MTP and transcoding, the DSP farm supports only two IP streams connected to each other at a time.
If more than two streams need connecting, the streams must be connected using conferencing.
Conferencing and Transcoding Features on the NM-HDV2 and

NM-HD-1V/2V/2VE
Conferencing
• Cisco Unified CallManager meet-me and ad-hoc conferences with up to eight participants each
• Up to 50 eight-party conferences on a single NM-HDV2, up to 24 eight-party conferences on a
single NM-HD-2VE, and up to 8 eight-party conferences on a single NM-HD-1V/2V
• Participants using G.711 and G.729 codecs joined in a single conference; no additional transcoding
resources are needed to include the disparate codec types
• Easy deployment of conference resources in routers across the network, reducing WAN use and
improving voice-network performance

71
Transcoding
• Transcoding between G.711 and G.729, G.729a, G.729b, G.729ab, GSM FR, and GSM EFR codecs
• Up to 128 transcoding sessions on a single NM-HDV2
MTP
• Software-only implementation that does not use a DSP resource for endpoints with the same codec
and the same packetization time.
• Hardware-only implementation using a DSP resource for endpoints with the same G.711 codec but
a different packetization time.
Conferencing and Transcoding Features on the NM-HDV

Conferencing
• Cisco Unified CallManager meet-me and ad-hoc conferences with up to six participants each
• Up to 15 six-party conferences on a single NM-HDV
Transcoding
• Transcoding between G.711 and G.729, G.729a, G.729b, and G.729ab codecs
• Up to 60 transcoding sessions on a single NM-HDV
Conferencing and Transcoding Features on the Cisco 1751 and Cisco 1760
Conferencing
• Cisco Unified CallManager meet-me and ad-hoc conferences with up to six participants each
• Up to 5 six-party conferences
• One conference on a single DSP
Transcoding
• Transcoding between G.711 and G.729, G.729a, G.729b, and G.729ab codecs
• Up to 16 transcoding sessions on the Cisco 1751
• Up to 20 transcoding sessions on the Cisco 1760
• Two transcoding sessions on a single DSP

72
Allocation of DSP Resources

You must allocate DSP resources on two levels:
• Within the voice network module, between the DSP farm and your voice trunk group that handles
standard voice termination
• Within the DSP farm, between transcoding and voice-conferencing services
Allocation of DSP Resources Within the Voice Network Module

You allocate DSP resources either to voice termination of the voice trunk group or to the DSP farm.
Occasionally these allocations can conflict.
If you previously allocated DSP resources to voice termination and you now try to configure a DSP farm,
you might find that insufficient DSP resources are available. Conversely, if you previously allocated DSP
resources to a DSP farm and you now try to configure a trunk group, you might find that insufficient DSP
resources are available.
If your requested configuration is rejected, you have two options:
• Insert more DSPs on the voice network module (NM-HDV or NM-HDV2)
• Allocate a different voice network module for either the DSP farm or the trunk group
Allocation of DSP Resources Within the DSP Farm

You should know the following about your system:
• Number of DSPs required to handle your anticipated number of conference calls and transcoding
sessions
• Number of DSPs that your system can support
DSP resources can reside in packet-voice DSP modules (PVDMs) installed in voice network modules,
for example the NM-HDV2, or directly in the network module, for example the NM-HD-2V. Cisco 2800
series and 3800 series voice gateway routers have onboard DSP resources located on PVDM2s installed
directly on the motherboard. Your router supports one or more voice network modules.
Table 3 lists the total DSPs that are supported on a fully-loaded voice network module.
Table 3 Total DSPs Supported Per Voice Network Module
Maximum DSPs per Maximum PVDM2s/PVDMs

Network Module PVDM2/PVDM per Network Module Maximum DSPs
NM-HDV2 4 4 16
NM-HD-1V/2V — — 1
NM-HD-2VE — — 3
NM-HDV 3 5 15

73
Table 4 lists the total number of network modules that are supported per router.
Table 4 Maximum Voice Network Modules Supported Per Router
NM-HD-1V, NM-HD-2V,
Router NM-HDV2 NM-HD-2VE NM-HDV
Cisco 2600 series — — 1
Cisco 2600 XM 1 1 1
Cisco 2691 1 1 1
Cisco 2801 — — —
Cisco 3620 — — 11
Cisco 3640 — — 31
Cisco 3660 — 6 6
Cisco 3725 2 2 2
2 2
Cisco 3745 4 4 4
Cisco VG200 — — 1
1. Although the chassis has a slot for an additional module, it cannot operate with more than the specified number.
2. Provided processor resources are available.
Conferencing and Transcoding Session Capacities

Each DSP is individually configurable to support either conferencing or transcoding and standard voice
termination. The total number of conferencing, transcoding, and voice termination sessions is limited by
the capacity of the entire system, which includes the DSPs, hardware platform, physical voice interface,
and Cisco Unified CallManager.
Table 5 and Table 6 list the maximum number of conference calls and transcoding sessions that DSPs
can handle, in theory. Actual capacity may be less based on the total system design.
Table 5 DSP Theoretical Session Capacities
NM-HD-1V/2V NM-HD-2VE NM-HDV2 2801/2811 2821/2851 3825, 3845

Application (1 DSP) (3 DSPs) (16 DSPs) (2 PVDM2-64) (3 PVDM2-64) (4 PVDM2-64)
Conferencing
G.711 8 sessions 24 sessions 50 sessions 50 sessions 50 sessions 50 sessions
(64 conferees) (192 conferees) (400 conferees) (400 conferees) (400 conferees) (400 conferees)
G.729 2 sessions 6 sessions 32 sessions 16 sessions 24 sessions 32 sessions
(16 conferees) (48 conferees) (256 conferees) (128 conferees) (192 conferees) (256 conferees)
GSM FR — 2 sessions 14 sessions 7 sessions 10 sessions 14 sessions
(16 conferees) (112 conferees) (56 conferees) (80 conferees) (112 conferees)
GSM EFR — 1 session 10 sessions 5 sessions 8 sessions 10 sessions
(8 conferees) (80 conferees) (40 conferees) (64 conferees) (80 conferees)

74
Table 5 DSP Theoretical Session Capacities (continued)
NM-HD-1V/2V NM-HD-2VE NM-HDV2 2801/2811 2821/2851 3825, 3845

Application (1 DSP) (3 DSPs) (16 DSPs) (2 PVDM2-64) (3 PVDM2-64) (4 PVDM2-64)
Transcoding
G.711 a-law/u-law 8 sessions 24 sessions 128 sessions 64 sessions 96 sessions 128 sessions
<->
G.729a/G.729ab/
GSM FR
<-> G.729/G.729b/
GSM EFR
Voice Termination
G.726, G.729a, 8 sessions 24 sessions 128 sessions 64 sessions 96 sessions 128 sessions
G.729ab, GSM FR
G.729, G.729b, 6 sessions 18 sessions 96 sessions 48 sessions 72 sessions 96 sessions
G.723.1, G.728,
GSM EFR
Table 6 Theoretical System Capacities for One DSP
Application G.711 a-law/u-law G729 a/ab G.729, G.729b GSM FR GSM EFR
Conferencing 8 sessions 2 sessions 2 sessions — —
(8 x 8 = 64 (8 x 2 = 16 (8 x 2 = 16
conferees) conferees) conferees)
Conferencing on 4 sessions 1 session 1 session — —
PVDM2-8 (4 x 8 = 32 (1 x 8 = 8 (1 x 8 = 8
conferees) conferees) conferees)
Hardware MTP 16 sessions — — — —
Transcoding 8 sessions 8 sessions 6 sessions 8 sessions 6 sessions
NM-HDV System Capacities

Table 7 lists the number of transcoding sessions and conference calls supported on the NM-HDV.
Table 7 NM-HDV Theoretical System Capacities
Device Capacity
A single DSP 4 transcoding sessions
1 conference call with up to 6 participants
A single PVDM (3 DSPs) 12 transcoding sessions
3 conference calls, each with up to 6 participants, for a
total of up to 18 participants

75
Table 7 NM-HDV Theoretical System Capacities (continued)
Device Capacity
A fully loaded NM-HDV 60 transcoding sessions
(5 PVDMs holding 15 DSPs) 15 concurrent conference calls, each with up to
6 participants, for a total of up to 90 participants
Use the following tables to determine the number of PVDMs required to support your DSP needs and
whether your router is capable of holding enough NM-HDVs to accommodate these PVDMs:
• See Table 8 if you use either of the following:
– 20-, 30-, 40-, 50-, or 60-ms packetization
– 10-ms packetization with voice-activity detection (VAD) enabled
• See Table 9 if you use 10-ms packetization with VAD disabled
Table 8 PVDM Requirements Using 20-, 30-, 40-, 50-, or 60-ms Packetization or 10-ms
Packetization with VAD Enabled 1
Transcoding Conference Calls

Sessions 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
0 — 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5
1–4 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 —
5–8 1 1 2 2 2 3 3 3 4 4 4 5 5 5 — —
9–12 1 2 2 2 3 3 3 4 4 4 5 5 5 — — —
13–16 2 2 2 3 3 3 4 4 4 5 5 5 — — — —
17–20 2 2 3 3 3 4 4 4 5 5 5 — — — — —
21–24 2 3 3 3 4 4 4 5 5 5 — — — — — —
25–28 3 3 3 4 4 4 5 5 5 — — — — — — —
29–32 3 3 4 4 4 5 5 5 — — — — — — — —
33–36 3 4 4 4 5 5 5 — — — — — — — — —
37–40 4 4 4 5 5 5 — — — — — — — — — —
41–44 4 4 5 5 5 — — — — — — — — — — —
45–48 4 5 5 5 — — — — — — — — — — — —
49–52 5 5 5 — — — — — — — — — — — — —
53–56 5 5 — — — — — — — — — — — — — —
57–60 5 — — — — — — — — — — — — — — —
1. Numbers given represent the number of PVDMs required within a single NM-HDV or NM-HDV-FARM to support the
desired configuration. Where numbers are not given, the configuration is not possible using a single NM-HDV.

76
How to Configure Conferencing and Transcoding for Voice Gateway Routers
Table 9 PVDM Requirements Using 10-ms Packetization and with VAD Disabled 1
Transcoding Conference Calls

Sessions 0 1 2 3 4 5 6 7 8 9 10
0 — 1 1 1 2 2 2 3 3 3 4
1–4 1 1 1 2 2 2 3 3 3 — —
5–8 1 1 2 2 2 3 3 3 — — —
9–12 1 2 2 2 3 3 3 — — — —
13–16 2 2 2 3 3 — — — — — —
17–20 2 2 3 3 — — — — — — —
21–24 2 3 3 — — — — — — — —
25–28 3 — — — — — — — — — —
29–30 3 — — — — — — — — — —
1. Numbers given represent the number of PVDMs required within a single NM-HDV to
support the desired configuration. Where numbers are not given, the configuration is not
possible using a single NM-HDV.
How to Configure Conferencing and Transcoding for Voice

Gateway Routers
This section contains the procedures for configuring conferencing and transcoding support on Cisco IOS
voice gateways. The procedures that you perform depend on the type of voice network module you are
using to allocate DSP resources:
• Determining DSP Resource Requirements, page 78 (required)
• Enabling SCCP on the Cisco Unified CallManager Interface, page 79 (required)
• Configuring Enhanced Conferencing and Transcoding, page 80 (required)
• Configuring Conferencing and Transcoding (NM-HDV), page 91 (required)
• Configuring Conferencing and Transcoding (PVDM-256K), page 94 (required)
• Configuring Out-of-Band to In-Band DTMF Relay, page 95 (optional)

77
Determining DSP Resource Requirements

DSPs reside either directly on a voice network module, such as the NM-HD-2VE, on PVDM2s that are
installed in a voice network module, such as the NM-HDV2, or on PVDM2s that are installed directly
onto the motherboard, such as on the Cisco 2800 and 3800 series voice gateway routers. You must
determine the number of PVDM2s or network modules that are required to support your conferencing
and transcoding services and install the modules on your router.
SUMMARY STEPS
1. Determine performance requirements.

2. Determine the number of DSPs that are required.
3. Determine the number of network modules that are supportable.
4. Verify your solution.
5. Install hardware.
DETAILED STEPS

Step 1 Determine the number of transcoding sessions and Establishes your performance requirements.
conference calls that your router must support.
Step 2 Determine the number of DSPs that are required to Establishes your hardware requirements.
support the transcoding sessions and conference calls
(see Table 5 on page 74 and Table 6 on page 75). If
voice termination is also required, determine the
additional DSPs required.
Example:
8 G.711 conferences and 32 transcoding sessions
require 1 PVDM2-64 (4 DSPs) on the NM-HDV2.
Step 3 Determine the maximum number of network modules Establishes your router capabilities.
that your router can support (see Table 4 on page 74).
Example:
A Cisco 3745 router can support up to 4 NM-HDV2s
(provided processor resources are available).
Step 4 Ensure that your requirements fall within router Verifies your proposed solution.
capabilities, taking into account whether your router
supports multiple network modules. If necessary,
reassess performance requirements.
Step 5 Install PVDM2s and network modules, as needed (see Prepares your system for DSP-farm configuration.
the “Connecting Voice Network Modules” chapter in
the Cisco Network Modules Hardware Installation
Guide, and the Cisco Network Modules and Interface
Cards Regulatory Compliance and Safety
Information).

78
Enabling SCCP on the Cisco Unified CallManager Interface

Perform this task to enable SCCP on the local interface that the voice gateway uses to communicate with
SUMMARY STEPS
1. enable
3. sccp ccm {ip-address | dns} identifier identifier-number [port port-number]
[version version-number]
or
sccp ccm {ip-address | dns} priority priority [port port-number] [version version-number]
4. sccp local interface-type interface-number
5. sccp ip precedence value
6. sccp
7. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 NM-HDV2, NM-HD-1V, NM-HD-2V, NM-HD-2VE, or PVDM2 Adds a Cisco Unified CallManager server to the list of
sccp ccm {ip-address | dns} identifier available servers to which the Cisco voice gateway can
identifier-number [port port-number] [version register.
version-number]
• Repeat this step for each Cisco Unified CallManager
NM-HDV, Cisco 1751, or Cisco 1760 server that the gateway registers with.
sccp ccm {ip-address | dns} priority priority
[port port-number] [version version-number]
Example:
Router(config)# sccp ccm 10.0.0.0 identifier 1
version 4.0
Example:
Router(config)# sccp ccm 10.0.0.0 priority 1
version

79

Step 4 sccp local interface-type interface-number Selects the local interface that SCCP applications use to
register with Cisco Unified CallManager.
Example:
Router(config)# sccp local Ethernet 1
Step 5 sccp ip precedence value (Optional) Sets the IP precedence value for SCCP.
• This command enables you to increase the priority of
Example: voice packets over connections controlled by SCCP.
Router(config)# sccp ip precedence 3
• value—Range is 1(highest) to 7 (lowest). Default is 5.
Step 6 sccp Enables SCCP and brings it up administratively.
Example:
Router(config)# sccp
Example:
Configuring Enhanced Conferencing and Transcoding

Perform the following procedures to configure enhanced conferencing and transcoding on the
NM-HDV2, NM-HD-1V, NM-HD-2V, NM-HD-2VE, or PVDM2:
• Configuring a DSP Farm Profile, page 80 (required)
• Associating a DSP Farm Profile to a Cisco Unified CallManager Group, page 83 (required)
• Modifying Default Settings for SCCP Connection to Cisco Unified CallManager, page 85 (optional)
• Verifying DSP Farm Configuration, page 87 (optional)
• Troubleshooting DSP-Farm Services, page 91 (optional)
Configuring a DSP Farm Profile

Perform this procedure to define a DSP farm on the NM-HDV2, NM-HD-1V, NM-HD-2V,
NM-HD-2VE, or PVDM2. You must configure each conferencing, transcoding, and MTP profile
separately.
Note Because a software-only MTP does not require DSP resources, you can configure a software-only MTP
without a voice network module, or on the NM-HDV if you do not enable the dsp services dspfarm
command for the voice card.
Prerequisites
Requires Cisco IOS Release 12.3(8)T or a later release.

80
SUMMARY STEPS
1. enable
3. voice-card slot
4. dsp services dspfarm
5. exit
6. dspfarm profile profile-identifier {conference | mtp | transcode}
7. description text
8. codec codec-type
9. maximum sessions number
or
maximum sessions {hardware | software} number
10. associate application sccp
11. no shutdown
12. exit
13. gateway
14. timer receive-rtp seconds
15. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 voice-card slot Enters voice-card configuration mode for the network
module on which you want to enable DSP-farm services.
Example:
Router(config)# voice-card 1
Step 4 dsp services dspfarm Enables DSP-farm services for the voice card.
Example:
Router(config-voicecard)# dsp services dspfarm

81

Step 5 exit Exits voice-card configuration mode.
Example:
Router(config-voicecard)# exit
Step 6 dspfarm profile profile-identifier Enters DSP farm profile configuration mode to define a
{conference | mtp | transcode} profile for DSP farm services.
Note The profile-identifier and service type uniquely
Example: identifies a profile. If the service type and
Router(config)# dspfarm profile 20 conference profile-identifier pair is not unique, you are
prompted to choose a different profile-identifier.
Step 7 description text (Optional) Includes a specific description about the
Cisco DSP farm profile.
Example:
Router(config-dspfarm-profile)# description
art_dept
Step 8 codec codec-type Specifies the codecs supported by a DSP farm profile.
• Repeat this step for each codec supported by the profile.
Example: Note Hardware MTPs support only G.711 a-law and
Router(config-dspfarm-profile)# codec gsmefr
G.711 u-law. If you configure a profile as a
hardware MTP, and you want to change the codec to
other than G.711, you must first remove the
hardware MTP by using the no maximum sessions
hardware command.
Note Only one codec is supported for each MTP profile.

To support multiple codecs, you must define a
separate MTP profile for each codec.
Step 9 maximum sessions number Specifies the maximum number of sessions that are
or supported by the profile.
maximum sessions {hardware | software} number • number—Range is determined by the available
registered DSP resources. Default is 0.
Example: Note The hardware and software keywords apply only
Router(config-dspfarm-profile)# maximum to MTP profiles.
sessions 4
Step 10 associate application sccp Associates the SCCP protocol to the DSP farm profile.
Example:
Router(config-dspfarm-profile)# associate
application sccp
Step 11 no shutdown Enables the profile, allocates DSP farm resources, and
associates the application.
Example:
Router(config-dspfarm-profile)# no shutdown

82

Step 12 exit Exits DSP farm profile configuration mode.
Example:
Router(config-dspfarm-profile)# exit
Step 13 gateway Enters gateway configuration mode.
Example:
Router(config)# gateway
Step 14 timer receive-rtp seconds Sets the Real-Time Transport Protocol (RTP) timeout
interval to clear hanging connections.
Example: • seconds—Range is 180 to 1800. Default is 1200.
Router(config-gateway)# timer receive-rtp 600
Step 15 exit Exits to global configuration mode.
Example:
Router(config-gateway)# exit
Associating a DSP Farm Profile to a Cisco Unified CallManager Group

Perform this procedure to define a Cisco Unified CallManager group and to associate a DSP farm profile
with the Cisco Unified CallManager group.
Prerequisites
This procedure requires Cisco IOS Release 12.3(8)T or later.
SUMMARY STEPS
1. enable
3. sccp ccm group group-number
4. associate ccm identifier-number priority priority-number
5. associate profile profile-identifier register device-name
6. bind interface interface-type interface-number
7. description string
8. end

83
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 sccp ccm group group-number Creates a Cisco Unified CallManager group and enters
SCCP Cisco Unified CallManager configuration mode.
Example:
Router(config)# sccp ccm group 118
Step 4 associate ccm identifier-number priority Adds a Cisco Unified CallManager server to the
priority-number Cisco Unified CallManager group and establishes its
priority within the group.
Example: • Repeat this step for each Cisco Unified CallManager
Router(config-sccp-ccm)# associate ccm 125 server that you want to add to the group.
priority 2
Step 5 associate profile profile-identifier register Associates a DSP farm profile to the Cisco Unified
device-name CallManager group.
• device-name—Must match the device name configured
Example: in Cisco Unified CallManager; otherwise profile is not
Router(config-sccp-ccm)# associate profile registered to Cisco Unified CallManager.
register abgz12345
• Repeat this step for each DSP farm profile that you
want to register with this Cisco Unified CallManager
group.
Step 6 bind interface interface-type interface-number Binds an interface to the Cisco Unified CallManager group.
Example:
Router(config-sccp-ccm)# bind interface
fastethernet 2:1
Step 7 description text (Optional) Includes a specific description of the
Cisco Unified CallManager group.
Example:
Router(config-sccp-ccm)# description boston
office
Example:
Router(config)# end

84
Modifying Default Settings for SCCP Connection to Cisco Unified CallManager

Perform this task to tune the performance of the SCCP connection between the DSP farm and
Note The optimum settings for these commands depend on your platform and individual network
characteristics. Modify the defaults to meet your performance requirements.
SUMMARY STEPS
1. enable
3. sccp ccm group group-number
4. connect interval seconds
5. connect retries number
6. keepalive retries number
7. keepalive timeout seconds
8. registration retries retry-attempts
9. registration timeout seconds
10. switchover method {graceful | immediate}
11. switchback method {graceful | guard [timeout-value] | immediate | uptime uptime-value}
12. switchback interval seconds
13. end
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 sccp ccm group group-number Enters SCCP Cisco Unified CallManager configuration
mode.
Example: • group-number—Range is 1 to 65535.
Router(config)# sccp ccm group 118

85

Step 4 connect interval seconds (Optional) Specifies the amount of time that a DSP farm
profile waits before attempting to connect to another
Cisco Unified CallManager when the current
Example:
Router(config-sccp-ccm)# connect interval 1200
Cisco Unified CallManager fails to connect.
• seconds—Range is 1 to 3600. Default is 60.
Step 5 connect retries number (Optional) Specifies the number of times that a DSP farm
attempts to connect to a Cisco Unified CallManager when
the current Cisco Unified CallManager connections fails.
Example:
Router(config-sccp-ccm)# connect retries 5 • number—Range is 1 to 32. Default is 3.
Step 6 keepalive retries number (Optional) Sets the number of keepalive retries from SCCP
to the Cisco Unified CallManager.
Example: • number—Range is 1 to 32. Default is 3.
Router(config-sccp-ccm)# keepalive retries 7
Step 7 keepalive timeout seconds (Optional) Sets the number of seconds between keepalive
messages from SCCP to the Cisco Unified CallManager.
Router(config-sccp-ccm)# keepalive timeout 50
Step 8 registration retries retry-attempts (Optional) Sets the number of registration retries that
SCCP tries to register with the Cisco Unified CallManager.
Example: • retry-attempts—Range is 1 to 32. Default is 3.
Router(config-sccp-ccm)# registration retries 15
Step 9 registration timeout seconds (Optional) Sets the number of seconds between registration
messages sent from SCCP to the Cisco Unified CallManager.
Router(config-sccp-ccm)# registration timeout 8
Step 10 switchover method {graceful | immediate} (Optional) Sets the switchover method that the SCCP client
uses when the communication link to the active
Cisco Unified CallManager fails.
Example:
Router(config-sccp-ccm)# switchover method • Default is graceful.
graceful
Step 11 switchback method {graceful | guard (Optional) Sets the switchback method to use when the
[timeout- value] | immediate | uptime primary or higher priority Cisco Unified CallManager
uptime- value}
becomes available again.
• Default is guard, with a timeout value of
Example: 7200 seconds.
Router(config-sccp-ccm)# switchback method
graceful

86

Step 12 switchback interval seconds (Optional) Sets the number of seconds that the DSP farm
waits before polling the primary Cisco Unified
CallManager when the current Cisco Unified CallManager
Example:
Router(conf-sccp-ccm)# switchback interval 120
fails to connect.
• seconds—Range is 1 to 3600. Default is 60.
Example:
Router(config-sccp-ccm)# end
Verifying DSP Farm Configuration

To verify conferencing, transcoding, and MTP services, perform the following steps.
SUMMARY STEPS
2. show sccp ccm group [group-number]
3. show dspfarm profile [profile-number]
4. show dspfarm all
5. show sccp
6. show sccp connections
7. show media resource status
DETAILED STEPS
Step 1 Use the show running-config command to display the configuration of the MTP profile, for example:
...
sccp local FastEthernet0/0
sccp ccm 10.40.10.10 identifier 10 version 4.0
sccp
!
sccp ccm group 999
associate ccm 10 priority 1
associate profile 12 register MTP123456789
associate profile 2 register XCODE123456
!
dspfarm profile 12 mtp
codec g711ulaw
maximum sessions hardware 4
maximum sessions software 40
associate application SCCP
!
Step 2 show sccp ccm group [group-number]
Use this command to verify the configuration of the Cisco Unified CallManager group, for example:
Router# show sccp ccm group 999

87
CCM Group Identifier: 999

Description: None
Associated CCM Id: 10, Priority in this CCM Group: 1
Associated Profile: 2, Registration Name: XCODE1234567
Associated Profile: 12, Registration Name: MTP123456789
Registration Retries: 3, Registration Timeout: 10 sec
Keepalive Retries: 3, Keepalive Timeout: 30 sec
CCM Connect Retries: 3, CCM Connect Interval: 10 sec
Switchover Method: GRACEFUL, Switchback Method: GRACEFUL_GUARD
Switchback Interval: 10 sec, Switchback Timeout: 7200 sec
Signaling DSCP value: default, Audio DSCP value: default
Step 3 show dspfarm profile [profile-number]

Use this command to verify the configured DSP farm profiles, for example:
Router# show dspfarm profile 12
Dspfarm Profile Configuration
Profile ID = 12, Service = MTP, Resource ID = 2

Profile Admin State : UP
Profile Operation State : ACTIVE
Application : SCCP Status : ASSOCIATED
Resource Provider : FLEX_DSPRM Status : UP
Number of Resource Configured : 14
Number of Resource Available : 14
Hardware Configured Resources 4
Hardware Available Resources 4
Software Resources 10
Codec Configuration
Codec : g711ulaw, sa
Profile ID = 6, Service = TRANSCODING, Resource ID = 1

Codec Configuration
Codec : g711ulaw, Maximum Packetization Period : 30
Codec : g711alaw, Maximum Packetization Period : 30
Codec : g729ar8, Maximum Packetization Period : 60
Codec : g729abr8, Maximum Packetization Period : 60
Codec : gsmfr, Maximum Packetization Period : 20
Codec : g729br8, Maximum Packetization Period : 60
Codec : gsmefr, Maximum Packetization Period : 20
Note This command is not supported on the NM-HDV or Cisco 1700 series.
Step 4 show dspfarm all

Use this command to verify the status of the DSP farm, for example:
Router# show dspfarm all
DSPFARM Configuration Information:

88
Admin State: UP, Oper Status: ACTIVE - Cause code: NONE

Transcoding Sessions: 0(Avail: 0), Conferencing Sessions: 2 (Avail: 2)
Trans sessions for mixed-mode conf: 0 (Avail: 0), RTP Timeout: 600
Connection check interval 600 Codec G729 VAD: ENABLED
Total number of active session(s) 0, and connection(s) 0
SLOT DSP CHNL STATUS USE TYPE SESS-ID CONN-ID PKTS-RXED PKTS-TXED
0 0 1 UP FREE conf - - - -
0 0 2 UP FREE conf - - - -
0 0 3 UP FREE conf - - - -
0 0 4 UP FREE conf - - - -
0 0 5 UP FREE conf - - - -
0 0 6 UP FREE conf - - - -
Step 5 show sccp

Use the show sccp command to verify that the DSP farm is registered, for example:
Router# show sccp
SCCP Admin State: UP

Gateway IP Address: 10.10.100.29, Port Number: 0
IP Precedence: 5
User Masked Codec list:
Call Manager: 10.10.100.51, Port Number: 2000
Priority: N/A, Version: 4.0, Identifier: 2
Priority: N/A, Version: 4.0, Identifier: 1
Transcoding Oper State: ACTIVE - Cause Code: NONE

Active Call Manager: 10.10.100.51, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 10
Reported Max Streams: 6, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g729abr8, Maximum Packetization Period: 60
Supported Codec: gsmfr, Maximum Packetization Period: 20
Supported Codec: g729br8, Maximum Packetization Period: 60
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 20
Software MTP Oper State: ACTIVE - Cause Code: NONE

Step 6 show sccp connections

Use this command to verify the active SCCP connections, for example:
Router# show sccp connections
sess_id conn_id stype mode codec ripaddr rport sport
16777268 2164263392 mtp recvonly g711u 0.0.0.0 0 17540
Step 7 show media resource status

Use this command to verify the current media resource status, for example:

89
Router# show media resource status
Resource Providers:
Resource Provider ID :: FLEX_DSPRM Status :: REGISTERED

Service Profiles
MTP ::
TRANSCODING :: 6 11
CONFERENCING :: 10
Applications :
Application ID : SCCP, Status : REGISTERED
Troubleshooting Tips for Conferencing and Transcoding on Voice Gateway Routers

This section describes techniques for troubleshooting DSP-farm services.
Basic Troubleshooting Procedures

1. Verify the Cisco Unified CallManager version is 4.0 or later.
2. Verify that Cisco Unified CallManager is properly configured to provision conferencing,
transcoding, and MTP resources.
3. Organize your Cisco Unified CallManager group IDs, device IDs, and DSP farm profile names. Use
the
show dsp command to verify that the association between SCCP Cisco Unified CallManager and
the DSP farm profiles match your organizational plan.
4. Verify that the VoIP dial peer application exists on the terminating gateway.
5. Collect relevant information from debug and show commands, and configuration files before
contacting Cisco Technical Support for assistance.
6. You can clear any of the following by disabling the DSP farm or SCCP:
– Active calls
– DSPs
– Active connection to a Cisco Unified CallManager
MTP Troubleshooting Tips

• MTP profiles can use only G.711 a-law or G.711 u-law. If you define a profile for a hardware MTP,
and you want to change the codec to other than G.711, you must first remove the hardware MTP by
using the no maximum sessions hardware command.
• Verify that only one codec is assigned for each MTP profile. To support multiple codecs, you must
define a separate MTP profile for each codec.

90
Troubleshooting DSP-Farm Services

You can troubleshoot performance by performing any of the following steps.
SUMMARY STEPS
1. debug sccp {all | errors | events | packets | parser}

2. debug dspfarm {all | errors | events | packets}
3. debug media resource provisioning {all | errors | events}
DETAILED STEPS

Step 1 debug sccp {all | errors | events | packets | (Optional) Sets debugging levels for SCCP and its
parser} applications.
Example:
Router# debug sccp all
Step 2 debug dspfarm {all | errors | events | packets} (Optional) Sets debugging levels for DSP-farm service.
Example:
Router# debug dspfarm all
Step 3 debug media resource provisioning {all | errors (Optional) Sets debugging levels for media resource
| events} provisioning.
Example:
Router# debug media resource provisioning all
Configuring Conferencing and Transcoding (NM-HDV)

Perform the following procedures to configure enhanced conferencing and transcoding on the NM-HDV.
• Configuring the DSP Farm on the NM-HDV, page 91
• Tuning DSP-Farm Performance on the NM-HDV, page 93
Configuring the DSP Farm on the NM-HDV

Perform this task to configure a DSP farm on an NM-HDV.
Note If you configured a DSP farm in Cisco IOS Release 12.1(5)YH and have now upgraded to Cisco IOS
Release 12.2(13)T or later, you must reconfigure the DSP farm, including enabling DSP-farm services
on the NM-HDV and specifying maximum session numbers in each category as appropriate. Your
previous configuration no longer works.

91
SUMMARY STEPS
1. enable
3. voice-card slot
4. dsp services dspfarm
5. exit
6. dspfarm confbridge maximum sessions number
7. dspfarm transcoder maximum sessions number
8. dspfarm
9. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 voice-card slot Enters voice-card configuration mode for the network
module on which you want to enable DSP-farm services.
Example:
Router(config)# voice-card 1
Step 4 dsp services dspfarm Enables DSP-farm services on the voice card.
Example:
Router(config-voicecard)# dsp services dspfarm
Step 5 exit Returns to global configuration mode.
Example:
Router(config-voicecard)# exit
Step 6 dspfarm confbridge maximum sessions number Specifies the maximum number of conferencing sessions to
be supported by the DSP farm. A DSP can support
1 conference session with up to 6 participants.
Example:
Router(config)# dspfarm confbridge maximum Note When you assign this value, take into account the
sessions 3 number of DSPs allocated for transcoding services.

92

Step 7 dspfarm transcoder maximum sessions number Specifies the maximum number of transcoding sessions to
be supported by the DSP farm. A DSP can support up to
4 transcoding sessions.
Example:
Router(config)# dspfarm transcoder maximum Note When you assign this value, take into account the
sessions 12 number of DSPs allocated for conferencing
services.
Step 8 dspfarm Enables the DSP farm.
Example:
Router(config)# dspfarm
Example:
Tuning DSP-Farm Performance on the NM-HDV

Use the following optional commands to tune performance.
SUMMARY STEPS
1. enable
3. sccp switchback timeout guard seconds
4. dspfarm rtp timeout seconds
5. dspfarm connection interval seconds
6. exit
DETAILED STEPS

Example:
Router> enable
Example:

93

Step 3 sccp switchback timeout guard seconds (Optional) Sets the guard timer.
Example:
Router(config)# sccp switchback timeout guard
180
Step 4 dspfarm rtp timeout seconds (Optional) Configures the Real-Time Transport Protocol
(RTP) timeout interval for when the error condition “RTP
port unreachable” occurs.
Example:
Router(config)# dspfarm rtp timeout 60
Step 5 dspfarm connection interval seconds (Optional) Specifies how long to monitor RTP inactivity
before deleting an RTP stream.
Example:
Router(config)# dspfarm connection interval 60
Example:
What to Do Next
• To verify the configuration of conferencing and transcoding services on the NM-HDV, see the
“Verifying DSP Farm Configuration” section on page 87.
• For information on troubleshooting, see the “Troubleshooting DSP-Farm Services” section on
page 91.
Configuring Conferencing and Transcoding (PVDM-256K)

Perform this task to configure a DSP farm for conferencing and transcoding services using the
PVDM-256K on the Cisco 1751 or Cisco 1760.
Prerequisites for Conferencing and Transcoding on the Cisco 1751 or Cisco 1760
Determine that there are enough DSPs available for conferencing and transcoding services by using the
show voice dsp command.
SUMMARY STEPS
1. enable
3. dspfarm confbridge maximum sessions number
4. dspfarm transcoder maximum sessions number
5. dspfarm
6. exit

94
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 dspfarm confbridge maximum sessions number Specifies the maximum number of conferencing sessions to
be supported by the DSP farm. A DSP can support
1 conference session with up to 6 participants.
Example:
Router(config)# dspfarm confbridge maximum Note When you assign this value, take into account the
sessions 3 number of DSPs allocated for transcoding services.
Step 4 dspfarm transcoder maximum sessions number Specifies the maximum number of transcoding sessions to
be supported by the DSP farm. A DSP can support up to
4 transcoding sessions.
Example:
Router(config)# dspfarm transcoder maximum Note When you assign this value, take into account the
sessions 12 number of DSPs allocated for conferencing
services.
Step 5 dspfarm Enables the DSP farm.
Example:
Router(config)# dspfarm
Example:
What to Do Next
• To verify the configuration of conferencing and transcoding services on the NM-HDV, see the
“Verifying DSP Farm Configuration” section on page 87.
• For information on troubleshooting, see the “Troubleshooting DSP-Farm Services” section on
page 91.
Configuring Out-of-Band to In-Band DTMF Relay

There are no specific configuration tasks necessary to support the Out-of-Band to In-Band DTMF Relay
for Cisco IOS Voice Gateways feature except those described in the following Prerequisites section.

95
Prerequisites
Hardware
• NM-HDV2, NM-HD-2VE, or onboard PVDM2 (Cisco 2800 series or Cisco 3800 series).
• WS-SVC-CMM-6T1 or WS-SVC-CMM-6E1 port adapter for Cisco Catalyst 6500 series and
Cisco 7600 series Communication Media Module (CMM).
Software
• Enable SCCP on the local interface that the MTP resource uses to communicate with Cisco Unified
CallManager. For instructions, see the “Enabling SCCP on the Cisco Unified CallManager
Interface” section on page 79.
• Configure a DSP farm profile for MTP resources. For instructions, see the “Configuring a DSP Farm
Profile” section on page 80.
• Associate the MTP profile with the Cisco Unified CallManager group. For instructions, see the
“Associating a DSP Farm Profile to a Cisco Unified CallManager Group” section on page 83.
• Configure DTMF relay in the SIP dial peers using the dtmf-relay rtp-nte command.
• Configure DTMF relay in Cisco Unified CallManager 4.0 or later. For information, see the
Cisco Unified CallManager 4.0 documentation.
• Consider your system requirements when configuring DSP farms and SCCP because the defaults for
some commands might not result in expected behavior. In particular, the correct settings for the
following commands are platform-specific and depend on your individual network characteristics:
– connect interval
– connect retries
– keepalive retries
– keepalive timeout
– sccp registration retries
– sccp registration timeout
– switchback interval
Restrictions
• Multifrequency is supported by MTPs but Cisco Unified CallManager does not support it.
• Software MTP supports G.711 codecs only.
Out-of-Band to In-Band DTMF Relay for Cisco IOS Voice Gateways

The Out-of-Band to In-Band DTMF Relay for Cisco IOS Voice Gateways feature provides the event
processing capability in RFC 2833 that enables DTMF relay communication between SIP devices and
nonSIP endpoints using Cisco Unified CallManager. RFC 2833 defines a method of transporting tones
and other telephony events over Real-Time Transport Protocol (RTP) to ensure DTMF digits are
accurately transmitted in a packet environment. A single packet representing a DTMF tone as an event
code is passed within an RTP audio stream instead of sending the DTMF tone in-band, where it could
be corrupted because of packet loss. When the packet reaches the receiver, it re-creates a tone of the
correct frequency and duration.

96
DTMF detection and generation capabilities are added to the hardware and software MTP. The MTP
generates out-of-band SCCP events to Cisco Unified CallManager when it detects a DTMF tone. The
MTP creates event packets for DTMF digits and inserts the packets into the outgoing RTP stream after
receiving an SCCP request from Cisco Unified CallManager.
Figure 7 illustrates the media setup and DTMF tone flow between a SIP network and nonSIP network
over a DSP farm MTP.
Figure 7 DTMF Tone Flow Between a SIP and NonSIP Network
PSTN
T1/E1/PRI/CAS
SIP media
V gateway V
In-band DTMF Out-of-band DTMF
SIP NonSIP
network network
MTP
resources
IP IP IP IP
SIP IP SCCP phones
phones
103192
This feature supports DTMF relay using the following MTP and transcoder resources for Cisco Unified
CallManager 4.0:
• Software MTP—Software-only implementation that does not use a DSP resource for endpoints
using the same codec and the same packetization time.
• Hardware MTP—Hardware-only implementation that uses a DSP resource for endpoints using the
same G.711 codec but a different packetization time. Cisco Unified CallManager refers to it also as
a software MTP.
• Transcoder—Hardware-only implementation using a DSP resource for endpoints using different
codecs. Cisco Unified CallManager also refers to it as a hardware MTP.
For MTP and transcoding, the DSP farm supports only two IP streams connected to each other at a time.
If more than two streams need connecting, the streams must be connected using conferencing.
Note For more information on MTPs and transcoders, see the Cisco Unified CallManager System Guide
Release 4.0(1).

97
Configuration Examples for Conferencing and Transcoding

• DSP-Farm Services on the NM-HDV2/PVDM2: Example, page 98
• DSP-Farm Services on the NM-HDV: Example, page 100
• Tuning DSP-Farm Services on the NM-HDV: Example, page 102
• DSP-Farm Services on the Cisco 1760: Example, page 102
• Dut-Band to In-Band DTMF Relay (Cisco 2801): Example, page 104
• Out-Band to In-Band DTMF Relay (Cisco 3725): Example, page 106
DSP-Farm Services on the NM-HDV2/PVDM2: Example

The following example shows a configuration of conferencing and transcoding services on an
NM-HDV2 or PVDM2. DSP farm profile 6, which supports transcoding, and profile 10, which supports
conferencing are both assigned to Cisco Unified CallManager group 988.
Note This configuration requires Cisco IOS Release 12.3(8)T or later.

!
version 12.3
!
hostname sjl23
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
ip subnet-zero
!
!
!
ip host boating 223.255.254.254
!
voice-card 1
no dspfarm
dsp services dspfarm
!
!
voice service voip
h323
!
!
controller T1 4/1
framing sf
crc-threshold 0
linecode ami
!
controller T1 4/2

98
framing sf
crc-threshold 0
linecode ami
!
!
!
ip address 10.4.20.7 255.255.255.0
no ip mroute-cache
speed auto
half-duplex
no cdp enable
!
no ip address
no ip mroute-cache
shutdown
duplex auto
speed auto
no cdp enable
!
ip default-gateway 10.4.0.1
ip classless
ip route 223.255.254.254 255.255.255.255 10.4.0.1
no ip http server
!
!
no cdp run
!
!
control-plane
!
!
voice-port 1/0/0
!
voice-port 1/0/1
!
!
sccp ip precedence 3
sccp
!
sccp ccm group 988
associate profile 10 register CFB123456789966
keepalive retries 5
switchover method immediate
switchback method immediate
switchback interval 15
!
dspfarm profile 6 transcode
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec gsmfr
maximum sessions 4

99

!
dspfarm profile 10 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
maximum sessions 1
!
!
!
!
codec g711ulaw
!
destination-pattern 5550...
codec g711ulaw
!
forward-digits 0
!
!
!
gateway
timer receive-rtp 1200
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password test
login
!
!
end
DSP-Farm Services on the NM-HDV: Example

The following sample configuration shows voice conferencing and transcoding are both configured on
the same NM-HDV.
!
version 12.2

100

!
hostname router
!
voice-card 1
!
ip subnet-zero
!
mta receive maximum-recipients 0
!
controller T1 1/0
framing sf
linecode ami
no yellow generation
no yellow detection
!
controller T1 1/1
framing sf
linecode ami
no yellow generation
no yellow detection
!
ip address 10.10.10.11 255.255.255.0
load-interval 30
duplex auto
speed auto
!
ip address 10.3.150.139 255.0.0.0
load-interval 30
duplex auto
speed auto
!
ip classless
ip http server
!
call rsvp-sync
!
!
sccp
sccp ccm 10.10.10.1 priority 1
!
dspfarm transcoder maximum sessions 1
dspfarm confbridge maximum sessions 1
dspfarm
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 1/1/0
!
voice-port 1/1/1
!
!

101
!
port 1/0/0
!
! Following dial peer is for calls to H.323 end-point 313.... for transcoding.
! Session target is IP address of Cisco CallManager.
!
!
! Following dial peer is for calls to IP Phones for conferencing.
! Session target is IP address of Cisco CallManager.
!
codec g711alaw
!
line con 0
line aux 0
line vty 0 4
login
!
end
Tuning DSP-Farm Services on the NM-HDV: Example

...
sccp local FastEthernet 0/0
sccp
sccp ccm 10.10.10.1 priority 1 version 3.1+
sccp switchback timeout guard 180
!
dspfarm rtp timeout 60
dspfarm connection interval 60
dspfarm
DSP-Farm Services on the Cisco 1760: Example

!
version 12.3
!
hostname c1760
!
boot-start-marker
boot-end-marker
!
no logging console
!

102
tdm clock E1 1/0 both export line

tdm clock bri-auto
no mmi pvc
voice-card 0
!
voice-card 1
!
no aaa new-model
ip subnet-zero
ip cef
!
!
no ip domain lookup
ip multicast-routing
isdn switch-type basic-net3
!
!
!
!
controller E1 1/0
!
!
ip address 10.1.1.34 255.255.0.0
ip igmp join-group 172.16.1.10
speed auto
no keepalive
!
interface BRI0/0
no ip address
!
interface BRI0/1
no ip address
shutdown
!
ip classless
no ip http server
ip rtcp report interval 2000
!
!
control-plane
!
!
!
voice-port 0/0
!
voice-port 0/1
!
!
sccp
sccp switchback timeout guard 180
!

103
dspfarm transcoder maximum sessions 4

dspfarm rtp timeout 60
dspfarm connection interval 60
dspfarm
!
!
incoming called-number 261760....
direct-inward-dial
port 0/0
prefix 241760
!
playout-delay minimum low
codec g711ulaw
no vad
!
gateway
timer receive-rtcp 5
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
login
!
end
Dut-Band to In-Band DTMF Relay (Cisco 2801): Example

In the following configuration, the voice gateway acts as both a H.323 gateway and DSP farm.
Building configuration...

!
version 12.3
!
hostname 2801_router
!
boot-start-marker
boot-end-marker
!
no logging console
!
no mmi pvc

104

no aaa new-model
ip subnet-zero
ip cef
!
!
!
isdn switch-type primary-net5
voice-card 0
!
!
!
controller T1 2/0
shutdown
framing esf
linecode b8zs
!
controller T1 2/1
framing esf
linecode b8zs
!
!
!
ip address 192.168.12.21 255.255.255.0
duplex auto
speed auto
!
no ip address
shutdown
duplex auto
speed auto
!
interface BRI4/0
no ip address
!
interface BRI4/1
no ip address
!
ip classless
ip http server
!
!
!
control-plane
!
!
!
voice-port 3/0
!
voice-port 3/1
!
voice-port 4/0
!
voice-port 4/1
!
!

105
sccp
!
sccp ccm group 1
bind interface FastEthernet0/0
associate profile 2 register amalthea-mtp
associate profile 1 register amalthea-xcode
registration retries 20
registration timeout 30
keepalive retries 10
connect retries 30
connect interval 30
!
description xcode func
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec gsmfr
codec g729r8
maximum sessions 2
!
codec g711ulaw
!
!
port 3/0
!
destination-pattern 52..
dtmf-relay h245-alphanumeric
!
gateway
!
!
line con 0
line aux 0
line vty 0 4
login
!
end
Out-Band to In-Band DTMF Relay (Cisco 3725): Example

The following running configuration example shows the MTP device configuration:

!
version 12.3

106

!
hostname router1
!
voice-card 1
no dspfarm
!
voice-card 2
dspfarm
!
no aaa new-model
ip subnet-zero
!
ip host sample 10.10.10.5
mpls ldp logging neighbor-changes
no scripting tcl init
no scripting tcl encdir
!
no voice hpi capture buffer
no voice hpi capture destination
!
ip address 10.4.118.13 255.255.255.255
duplex auto
speed auto
!
no ip address
shutdown
duplex auto
speed auto
!
ip classless
!
ip http server
!
sccp
!
sccp ccm group 999
associate profile 2 register XCODE123456
!
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec gsmfr
maximum sessions 2
!
codec g711ulaw

107

!
SIP Gateway: Example

The following running configuration example shows the SIP gateway configuration for the Out-Band to
In-Band DTMF Relay feature:

!
version 12.3
!
hostname cisco_sip_gw
!
!
voice-card 2
dspfarm
!
no aaa new-model
ip subnet-zero
!
!
ip domain name cisco.com
ip host sample 10.10.10.5
ip host myhost 10.4.175.2
!
!
!
!
ccm-manager mgcp
ccm-manager config
!
!
controller T1 2/0
framing esf
linecode b8zs
!
controller T1 2/1
framing sf
linecode ami
!
!
!
ip address 10.4.175.14 255.255.0.0

108
duplex auto
speed auto
!
no ip address
shutdown
duplex auto
speed auto
!
interface BRI1/0
no ip address
!
ip classless
!
ip http server
!
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 1/1/0
!
voice-port 2/0:1
!
!
!
session protocol sipv2
dtmf-relay rtp-nte
codec g711ulaw
!
application mgcpapp
port 2/0:1
!
application mgcpapp
port 2/0:1
!
port 1/0/0
!
port 1/0/0
!
!
line con 0
line aux 0
line vty 0 4
login
!
!
end

109
Where to Go Next
Where to Go Next
• To enable MGCP on a Cisco IOS gateway, see Configuring MGCP Gateway Support for
Cisco Unified CallManager, page 23.
• To download region-specific tones and the associated frequencies, amplitudes, and cadences, see
release, Cisco Unified CallManager and Cisco IOS interoperability features.
• “Conference Bridges” chapter in the Cisco Unified CallManager System Guide, Release
4.0(1)—Overview of conference devices in Cisco Unified CallManager 4.0.
• “Conference Bridge Configuration” chapter in the Cisco Unified CallManager Administration
Guide, Release 4.0(1)—Describes how to configure conference bridges in Cisco Unified
CallManager 4.0.
• “Transcoders” chapter in the Cisco Unified CallManager System Guide—Overview of transcoder
devices in Cisco Unified CallManager 4.0.
• “Transcoder Configuration” chapter in the Cisco Unified CallManager Administration
Guide—Describes how to configure transcoders in Cisco Unified CallManager 4.0.
• IP Communications High-Density Digital Voice/Fax Network Module feature document—Describes
how to configure support for the NM-HDV2 in Cisco IOS gateways.
• “Connecting Voice Network Modules” chapter in the Cisco Network Modules Hardware Installation
Guide—Describes how to install the voice network modules.

110
Configuring MGCP PRI Backhaul and T1 CAS
Support for Cisco Unified CallManager
This chapter describes the procedures for enabling MGCP PRI backhaul support on the Cisco IOS
gateway and describes related features.
Feature History for QSIG Supplementary Features for Voice Gateway Routers
Feature History for MGCP Gateway Support for Cisco Unified CallManager Network Specific Facilities
12.2(15)ZJ This feature was introduced.
Feature History for MGCP PRI Backhaul and T1 CAS Support for Cisco CallManager
12.2(2)XN This feature was introduced for Cisco CallManager Version 3.0.
12.2(11)T Support was added for Cisco CallManager Version 3.2.

111
Configuring MGCP PRI Backhaul and T1 CAS Support for Cisco Unified CallManager
Contents
Contents
• Restrictions for MGCP PRI Backhaul and T1 CAS Support, page 112
• Information About MGCP PRI Backhaul and T1 CAS Support, page 112
• How to Configure MGCP PRI Backhaul Support for Cisco Unified CallManager, page 113
• Configuration Examples for MGCP PRI Backhaul and T1 CAS, page 124
Prerequisites for MGCP PRI Backhaul and T1 CAS Support

• Cisco IOS Release 12.2(11)T
• QSIG signaling is required to support supplementary services over the T1 and E1 time-division
multiplexing (TDM) trunks that support the PRI backhaul mechanism.
Restrictions for MGCP PRI Backhaul and T1 CAS Support

• Voice interfaces on the NM-HDA and the AIM-VOICE-30 are not supported.
• Integrated access, in which the channels on a T1 or E1 interface are divided between a group used
for voice and another group used for WAN access, is not supported when voice is controlled by
Cisco Unified CallManager through MGCP.
• T1 and E1 protocols, such as QSIG, E1 R2, T1 FGD, and PRI NFAS, are not supported with MGCP
only with H.323.
• E1 CAS is not supported.
• Do not add the application mgcpapp command to dial peers that support PRI backhaul.
Information About MGCP PRI Backhaul and T1 CAS Support

To configure MGCP PRI backhaul, you should understand the following concepts:
• MGCP PRI Backhaul Overview, page 112
• ISDN NSF in Route Patterns, page 113
MGCP PRI Backhaul Overview

MGCP PRI backhaul is a method for transporting complete IP telephony signaling information from an
ISDN PRI interface in an MGCP gateway to Cisco Unified CallManager using a highly reliable TCP
connection. The gateway uses a single TCP connection to backhaul all ISDN D channels to
Cisco Unified CallManager. The “SAP/Channel ID” parameter in the header of each message identifies
individual D channels. In addition to carrying the backhaul traffic, the TCP keepalive mechanism also
determines MGCP voice gateway connectivity to an available call agent.

112
How to Configure MGCP PRI Backhaul Support for Cisco Unified CallManager
MGCP PRI backhaul terminates all ISDN PRI Layer 2 (Q.921) signaling functions on the MGCP
gateway while, at the same time, packaging all the ISDN PRI Layer 3 (Q.931) signaling information into
packets for transmission to Cisco Unified CallManager through an IP tunnel over a TCP connection. This
ensures the integrity of the Q.931 signaling information that passes through the network for managing
IP telephony devices. A rich set of user-side and network-side ISDN PRI calling functions is supported
by MGCP PRI backhaul.
The MGCP gateway also establishes a TCP link to the backup (secondary) Cisco Unified CallManager
server. In the event of a Cisco Unified CallManager switchover, the secondary Cisco Unified
CallManager server performs the MGCP PRI backhaul functions. During the switchover, all active ISDN
PRI calls are preserved, and the affected MGCP gateway is registered with the new Cisco Unified
CallManager server through a Restart-in-Progress (RSIP) message. In this way, continued gateway
operation is ensured.
T1 CAS is supported in nonbackhaul fashion. Cisco Unified CallManager supports the following CAS
signaling types: E&M, wink-start, and E&M delay-dial. E1 CAS is not supported.
ISDN NSF in Route Patterns

The MGCP Gateway Support for Cisco Unified CallManager Network Specific Facilities (NSF) feature
supports the use of the ISDN NSF information element in the route pattern. This feature is compatible
with Cisco CallManager Version 3.3(2) and later.
The route pattern design in Cisco Unified CallManager enables facilities or services to be invoked on a
call-by-call basis. The NSF information element, which is used in ISDN PRI setup messages for
outgoing calls, includes the carrier identification code (CIC) and service parameters. The NSF
configuration is done in Cisco Unified CallManager as part of the route pattern for MGCP-controlled
PRI ports. The NSF information element is inserted in the Q.931 stream so that the attached PSTN switch
can interpret the information elements and select the service and route the call to a network.
With NSF configured, NSF can be used on a call-by-call basis. Without NSF configuration, you must
configure associated gateways as standalone H.323 gateways for which NSF services are configured
locally within the router. No configuration is required on the MGCP gateway to use the NSF feature.
How to Configure MGCP PRI Backhaul Support for Cisco Unified

CallManager
This section contains the following procedures for configuring MGCP PRI backhaul and related features
on Cisco IOS MGCP gateways.
• Configuring MGCP PRI Backhaul on the Cisco Voice Gateway, page 114 (required)
• Verifying MGCP PRI Backhaul Configuration, page 115 (optional)
• Configuring MGCP Gateway Support for Cisco Unified CallManager Network Specific Facilities,
page 118 (optional)
• Verifying Configuration of MGCP Gateway Support for Cisco Unified CallManager Network
Specific Facilities, page 119 (optional)
• Configuring QSIG Supplementary Features for Cisco IOS Voice Gateways, page 122 (optional)

113
Configuring MGCP PRI Backhaul on the Cisco Voice Gateway

This task shows you how to configure MGCP PRI backhaul on a Cisco IOS gateway.
SUMMARY STEPS
1. enable
3. controller {t1 | e1} slot/port
4. framing {esf | sf | crc4 | no crc4 | mp-crc4} [australia]
5. clock source {internal | line}
6. linecode {ami | b8zs | hdb3}
7. pri-group timeslots timeslot-range service mgcp
8. exit
9. interface serial slot/port:timeslot
10. isdn switch-type {primary-4ess | primary-5ess | primary-dms100 | primary-ni | primary-net5 |
primary-ntt | primary-qsig | primary-ts014}
11. isdn bind-L3 ccm-manager
12. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 controller {t1 | e1} slot/port Enters controller configuration mode.
Example:
Router(config)# controller t1 3/0
Step 4 framing {esf | sf | crc4 | no-crc4 | mp-crc4} Specifies the framing type on a E1 or T1 PRI line.
[australia]
• Default is sf (super frame) for T1 lines; CRC4 for E1
lines.
Example:
Router(config-controller)# framing esf

114

Step 5 clock source {internal | line} Configures the clock source used by the E1 or T1
controller.
Example: • Default is line.
Router(config-controller)# clock source internal
Step 6 linecode {ami | b8zs | hdb3} Specifies the line encoding method for the link.
• Default is ami (alternate mark inversion) for T1 lines;
Example: hdb3 (high-density bipolar 3) for E1 lines.
Router(config-controller)# linecode b8zs
Step 7 pri-group timeslots timeslot-range service mgcp Specifies MGCP as the control protocol used for
backhaul.
Example: Note The controller time slots cannot be shared between
Router(config-controller)# pri-group timeslots backhaul and other Layer 3 protocols.
1-24 service mgcp
Step 8 exit Exits controller configuration mode and returns to global
configuration mode.
Example:
Step 9 interface serial slot/port:timeslot Enters serial interface configuration mode.
• The syntax of this command is platform-dependent;
Example: type ? to determine.
Router(config)# interface serial 3/0:0
Step 10 isdn switch-type {primary-4ess | primary-5ess | Specifies the ISDN switch type.
primary-dms100 | primary-ni | primary-net5 |
primary-ntt | primary-qsig | primary-ts014} Note This command can be entered in either global
configuration mode or interface configuration
mode.
Example:
Router(config-if)# isdn switch-type primary-5ess
Step 11 isdn bind-L3 ccm-manager Enables ISDN to backhaul Q.931.
Example:
Router(config-if)# isdn bind-L3 ccm-manager
Step 12 exit Exits interface configuration mode and returns to global
configuration mode.
Example:
Router(config-if)# exit
Verifying MGCP PRI Backhaul Configuration

SUMMARY STEPS
1. show isdn status

2. show ccm-manager
3. show ccm-manager backhaul

115
DETAILED STEPS
Step 1 show isdn status

Use the show isdn status command to verify connectivity.
In the following sample output, the Layer 2 protocol is Q.921, and the Layer 3 protocol is
CCM-MANAGER. This output verifies that the Layer 2 and Layer 3 protocols are configured to
backhaul ISDN. If you are connected to a live line, you should see Layer 1 status as active and Layer 2
as MULTIPLE_FRAME_ESTABLISHED.
Router# show isdn status
*00:03:34.423 UTC Sat Jan 1 2000

Global ISDN Switchtype = primary-net5
ISDN Serial1:23 interface
!
******* Network side configuration *******
!
dsl 0, interface ISDN Switchtype = primary-net5
!
**** Master side configuration ****
!
L2 Protocol = Q.921 L3 Protocol(s) = CCM-MANAGER
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
NLCB:callid=0x0, callref=0x0, state=31, ces=0 event=0x0
NLCB:callid=0x0, callref=0x0, state=0, ces=1 event=0x0
0 Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
Number of active calls = 0
Number of available B-channels = 23
Total Allocated ISDN CCBs = 0

Use the show ccm-manager command to view the registration status with Cisco Unified CallManager,
for example:
MGCP Domain Name: AV-2620-4

============================================================
First Backup Backup Ready 10.16.240.128
Second Backup None
Current active Call Manager: 10.16.240.124

Backhaul/Redundant link port: 2428
Last failover time: None
Switchback mode: Graceful
MGCP Fallback mode: Not Selected
PRI Backhaul Link info:

116
Link Protocol: TCP

Remote Port Number: 2428
Remote IP Address: 10.16.240.124
Current Link State: OPEN
Statistics:
Packets recvd: 32
Recv failures: 0
Packets xmitted: 32
Xmit failures: 0
PRI Ports being backhauled:
Slot 1, port 0
Configuration Auto-Download Information

=======================================
Current version-id: {1645327B-F59A-4417-8E01-7312C61216AE}
Last config-downloaded:00:00:49
Current state: Waiting for commands
Configuration Download statistics:
Download Attempted : 6
Download Successful : 6
Download Failed : 0
Configuration Attempted : 1
Configuration Successful : 1
Configuration Failed(Parsing): 0
Configuration Failed(config) : 0
Last config download command: New Registration
Configuration Error History:
FAX mode: cisco
Step 3 show ccm-manager backhaul

Use the show ccm-manager backhaul command to verify the PRI backhaul link information, for
example:
Router# show ccm-manager backhaul
PRI Backhaul Link info:

Link Protocol: TCP
Statistics:
Packets recvd: 0
Recv failures: 0
Packets xmitted: 21
Xmit failures: 0
PRI Ports being backhauled:
Slot 1, port 1
Reference, Release 12.3T.

117
Configuring MGCP Gateway Support for Cisco Unified CallManager Network

Specific Facilities
There are no specific Cisco IOS configuration tasks necessary to support the NSF feature other than
enabling MGCP PRI backhaul as described in the “Configuring MGCP PRI Backhaul on the Cisco Voice
Gateway” section on page 114.
Prerequisites for MGCP Gateway Support for Cisco Unified CallManager Network Specific
Facilities
• NM-HDV or NM-HDV2
• Supported interface cards:
– AIM-ATM-VOICE-30
– AIM-VOICE-30
• Supported switch types:
– PRI 4ESS
– PRI 5E8
– PRI 5E9
– DMS 100
– DMS 250
– PRI NI-2
• MGCP PRI backhaul configuration. For information, see:
– “Configuring MGCP PRI Backhaul and T1 CAS Support for Cisco Unified CallManager” on
page 111
– How to Configure MGCP with Digital PRI and Cisco Unified CallManager
• Cisco CallManager Version 3.3(2) or later with the following configured:
– Network Service Protocol—Choose the PRI protocol that matches the protocol of the
terminating gateway from the Network Service Protocol drop-down field.
– Network Service—Choose the appropriate network service. The values vary depending on the
network service protocol that you choose from the Network Service Protocol drop-down field.
– Service Parameter Name—Displays the service parameter name that is associated with the
chosen network service. If no service parameter exists for the network service, the field displays
<Not Exist>.
– Service Parameter Value—Enter the appropriate service parameter value. Valid entries include
the digits 0 to 9. If a service parameter does not exist for the network service, Cisco Unified
CallManager disables this field.
– Route patterns—For more information, see the Cisco Unified CallManager Administration
Guide, Release 4.0(1).

118
• Cisco Unified CallManager supports NSF only if the appropriate carrier identification code (CIC)
is entered in the CIC field. CICs, which can be 3 or 4 digits or no digits, enable you to reach the
services of interexchange carriers. For a complete list of CICs, go to http://www.nanpa.com. The
following are examples of commonly used CICs:
– 0222—WorldCom and MCI
– 0288—ATT
– 0333—Sprint
Verifying Configuration of MGCP Gateway Support for Cisco Unified

CallManager Network Specific Facilities
SUMMARY STEPS
1. show ccm-manager
2. show mgcp endpoints
3. debug ccm-manager backhaul
4. debug isdn q931
DETAILED STEPS

Use the show ccm-manager command to verify the registration status of Cisco Unified CallManager,
for example:
MGCP Domain Name: Router

============================================================
First Backup None

Second Backup None
PRI Backhaul Link info
Link Protocol: TCP
Statistics:
Packets recvd: 32
Recv failures: 0

119
Packets xmitted: 32
Xmit failures: 0
PRI Ports being backhauled: Slot 1, port 0
!
Configuration Auto-Download Information
=======================================
No configurations downloaded
Current state: Automatic Configuration Download feature is disabled
FAX mode: cisco
Step 2 show mgcp endpoints

Use the show mgcp endpoints command to verify the status of the ports on the T1 interface, for
example:
Router# show mgcp endpoints
Interface T1 1/0
!
ENDPOINT-NAME V-PORT SIG-TYPE ADMIN
S1/ds1-0/1@AV-2620-4 1/0:23 none up
S1/ds1-0/2@AV-2620-4 1/0:23 none up
S1/ds1-0/3@AV-2620-4 1/0:23 none up
S1/ds1-0/4@AV-2620-4 1/0:23 none up
S1/ds1-0/5@AV-2620-4 1/0:23 none up
S1/ds1-0/6@AV-2620-4 1/0:23 none up
S1/ds1-0/7@AV-2620-4 1/0:23 none up
S1/ds1-0/8@AV-2620-4 1/0:23 none up
S1/ds1-0/9@AV-2620-4 1/0:23 none up
S1/ds1-0/10@AV-2620- 1/0:23 none up
S1/ds1-0/11@AV-2620- 1/0:23 none up
S1/ds1-0/12@AV-2620- 1/0:23 none up
S1/ds1-0/13@AV-2620- 1/0:23 none up
S1/ds1-0/14@AV-2620- 1/0:23 none up
S1/ds1-0/15@AV-2620- 1/0:23 none up
S1/ds1-0/16@AV-2620- 1/0:23 none up
S1/ds1-0/17@AV-2620- 1/0:23 none up
S1/ds1-0/18@AV-2620- 1/0:23 none up
S1/ds1-0/19@AV-2620- 1/0:23 none up
S1/ds1-0/20@AV-2620- 1/0:23 none up
S1/ds1-0/21@AV-2620- 1/0:23 none up
S1/ds1-0/22@AV-2620- 1/0:23 none up
S1/ds1-0/23@AV-2620- 1/0:23 none up
Step 3 debug ccm-manager backhaul

Use the debug ccm-manager backhaul command to verify that the NSF messages are backhauled
correctly between the gateway and Cisco Unified CallManager, for example:
Router# debug ccm-manager backhaul events
!
Call Manager backhaul events debugging is ON.
!
3:05:20:
1w0d:
cmbh_rcv_callback: <-- Receiving backhaul msg for Se1/1:23 :
| bk_msg_type = DATA_REQ
| bk_chan_id (slot:port) = 1:1
| Q.931 length = 52
| Q.931 message type: SETUP
| Q.931 message = 080200040504038090A21803A983971E028083200604A1323838E7

120
The bold portion of the above number is the NSF related information in the setup message of the
backhaul packet.
28086E616D65343430316C0600813434303170058039393939
1w0d:
cmbrl_send_pak: >-- Sending backhauled msg for Se1/1:23 :
| bk_msg_type = DATA_IND
| Q.931 length = 12
| Q.931 message type: STATUS
| Q.931 message = 080280047D080280E4140101
1w0d:
cmbrl_send_pak: --> Sending backhauled msg for Se1/1:23 :
| Q.931 length = 10
| Q.931 message type: CALL PROCEEDING
| Q.931 message = 08028004021803A98397
1w0d:
| Q.931 length = 9
| Q.931 message type: PROGRESS
| Q.931 message = 08028004031E028188
1w0d:
| Q.931 length = 9
| Q.931 message type: CONNECT
| Q.931 message = 08028004071E028182
1w0d:
| Q.931 length = 5
| Q.931 message type: CONNECT ACK
| Q.931 message = 080200040F
1w0d:
| Q.931 length = 9
| Q.931 message type: DISCONNECT
| Q.931 message = 080280044508028290
1w0d:
| Q.931 length = 5
| Q.931 message type: RELEASE
| Q.931 message = 080200044D
1w0d:
| Q.931 length = 5
| Q.931 message type: RELEASE COMPLETE
| Q.931 message = 080280045A
Step 4 debug isdn q931

121
Use the debug isdn q931 command to display the ISDN Layer 3 processing, for example:
Router# debug isdn q931
!
debug isdn q931 is ON.
1w0d: ISDN Se1/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0003
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Progress Ind i = 0x8083 - Origination address is non-ISDN
Net Specific Fac i = 0x04A1323838E7
Display i = 'name4401'
Calling Party Number i = 0x0081, '4401'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '9999'
Plan:Unknown, Type:Unknown
1w0d: ISDN Se1/1:23 Q931: RX <- STATUS pd = 8 callref = 0x8003
Cause i = 0x80E4 - Invalid information element contents
Call State i = 0x01
1w0d: ISDN Se1/1:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x8003
Channel ID i = 0xA98397
Exclusive, Channel 23
1w0d: ISDN Se1/1:23 Q931: RX <- PROGRESS pd = 8 callref = 0x8003
Progress Ind i = 0x8188 - In-band info or appropriate now available
1w0d: ISDN Se1/1:23 Q931: RX <- CONNECT pd = 8 callref = 0x8003
Progress Ind i = 0x8182 - Destination address is non-ISDN
1w0d: ISDN Se1/1:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x0003
1w0d: ISDN Se1/1:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x8003
Cause i = 0x8290 - Normal call clearing
1w0d: ISDN Se1/1:23 Q931: TX -> RELEASE pd = 8 callref = 0x0003
1w0d: ISDN Se1/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8003
Reference, Release 12.3T and the Cisco IOS Debug Command Reference, Release 12.3.
Configuring QSIG Supplementary Features for Cisco IOS Voice Gateways

There are no specific configuration tasks necessary to support QSIG features on the voice gateway
except those described in the following Prerequisites section.
Prerequisites
• MGCP must be configured on the voice gateway. For information, see “Configuring MGCP Gateway
• ISDN PRI Backhaul must be configured on the MGCP gateway. For information, see the
“Configuring MGCP PRI Backhaul on the Cisco Voice Gateway” section on page 114.

122
• QSIG signaling is required to support supplementary services over the T1 and E1 time-division
multiplexing (TDM) trunks that support the PRI backhaul mechanism.
WS-SVC-CMM-6T1 or WS-SVC-CMM-6E1 port adapter.
QSIG Supplementary Features for Cisco IOS Voice Gateways

The QSIG protocol, a variation of ISDN PRI signaling that is used by PBXs, supports basic calls and
supplementary services over TDM trunks. Cisco Unified CallManager can interoperate with PBXs using
QSIG. The voice gateway supports QSIG over PRI backhaul interfaces. Call control is transparent to the
voice gateway as all layer 3 messages are passed through PRI backhaul.
These additional QSIG features and services are supported for Cisco Unified CallManager 4.0 and later:
• Call diversion (forwarding)
• Call transfer
• Identification services
• Message waiting indication services
Figure 8 QSIG and Supplementary Services Overview
IP communications
Legacy telephony
systems
systems
QSIG and
supplementary
services
IP LAN
IP V
Cisco voice
gateway
IP
103193
IP
For more information about QSIG support in Cisco Unified CallManager, see the “Understanding IP
Telephony Protocols” chapter in the Cisco Unified CallManager System Guide.

123
Configuration Examples for MGCP PRI Backhaul and T1 CAS
Configuration Examples for MGCP PRI Backhaul and T1 CAS

This section provides the following configuration example:
• MGCP PRI Backhaul and T1 CAS: Example, page 124
Note To view relevant configuration examples, go to the Cisco Systems Technologies website at
http://cisco.com/en/US/tech/index.html. From the website, select Voice > IP Telephony/VoIP, then
click Technical Documentation > Configuration Examples.
MGCP PRI Backhaul and T1 CAS: Example

In the following example, T1 CAS and PRI backhaul is configured for an MGCP gateway:
mgcp
mgcp modem passthrough voip codec g711alaw
mgcp modem passthrough voip redundancy
mgcp package-capability dtmf-package
mgcp package-capability mf-package
mgcp default-package line-package
mgcp timer net-cont-test 3000
call rsvp-sync
!
ccm-manager mgcp
!
controller T1 3/0
framing esf
linecode b8zs
pri-group 0 timeslots 1-24 service mgcp
!
no ip address
isdn switch-type primary-ts014
isdn T306 60000
isdn bind-L3 ccm-manager
no cdp enable
!
!
application mgcpapp
port 1/0/0
!
application mgcpapp
port 1/0/1
!

124
Where to Go Next

application mgcpapp
port 3/0:0
!
Where to Go Next
• How to Configure MGCP with Digital PRI and Cisco Unified CallManager—Technical support
configuration document that includes sample configurations and troubleshooting tips.

125

126
Configuring MGCP-Controlled Backhaul of
BRI Signaling in Conjunction with Cisco Unified
CallManager
The MGCP-Controlled Backhaul of Basic Rate Interface (BRI) Signaling in Conjunction with
Cisco Unified CallManager feature provides MGCP service to remote-office gateways that connect by
means of ISDN BRI trunks to a centralized Cisco Unified CallManager.
Feature benefits include the following:
• Centralized call-management architecture, enabling a high degree of network control
• Short voice cut-through times
• Graceful evolution to new technology and to AVVID
Only the ETSI BRI basic-net3 switch type is supported.
Feature History for MGCP-Controlled Backhaul of BRI Signaling in Conjunction with Cisco Unified CallManager
12.2(15)ZJ This feature was introduced for Cisco CallManager 3.3(2).
12.3(11)T Support was added for Cisco Unified CallManager 4.1.
12.4(2)T This feature was implemented on the Cisco 2600XM, Cisco 2691,
Cisco 2800 series, Cisco 3700 series, and Cisco 3800 series.

127
Configuring MGCP-Controlled Backhaul of BRI Signaling in Conjunction with Cisco Unified CallManager
Contents
Contents
• Prerequisites for MGCP-Controlled Backhaul of BRI Signaling, page 128
• Restrictions for MGCP-Controlled Backhaul of BRI Signaling, page 129
• Information About MGCP-Controlled Backhaul of BRI Signaling, page 129
• How to Configure MGCP-Controlled Backhaul of BRI Signaling, page 131
• Configuration Examples for MGCP-Controlled Backhaul of BRI Signaling, page 135
Prerequisites for MGCP-Controlled Backhaul of BRI Signaling

• Cisco Unified CallManager 4.1(1) or a later release
Cisco Voice Gateway

• 20-MB flash memory
• 64-MB DRAM
• One of the supported combinations of BRI voice interface card (VIC) and network module:
– VIC-2BRI-NT/TE or VIC-2BRI-S/T in NM-1V or NM-2V with Cisco IOS Release 12.3(11)T
or a later release
– VIC2-2BRI-NT/TE in NM-HD-1V, NM-HD-2V, NM-HD-2VE, or NM-HDV2 with Cisco IOS
Release 12.4(2)T or a later release
– EM-4BRI-NT/TE in EVM-HD-8FXS/DID with Cisco IOS Release 12.4(2)T or a later release
• MGCP enabled globally in a VoIP network

128
Restrictions for MGCP-Controlled Backhaul of BRI Signaling
• MGCP control of dial peers and voice ports

• MGCP single-point configuration enabled
Note For MGCP configuration instructions, see “Configuring MGCP Gateway Support for
Cisco Unified CallManager” on page 23.
Restrictions for MGCP-Controlled Backhaul of BRI Signaling

• BRI backhaul uses the enhanced interface numbering support available in Cisco IOS
Release 12.3(11)T and later. Previous releases supported only the slot/subslot/port format with the
subslot forced to 0 on the Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series. Cisco IOS
Release 12.3(11)T and later releases support both the slot/port and slot/subslot/port interface
numbering formats for BRI backhaul.
• Only the ETSI BRI Basic-NET3 switch type is supported.
• BRI calls are cleared during MGCP gateway fallback and rehome because ISDN BRI L2 must be
reinitiated and brought up again by the new L3 task.
• Do not add the application mgcpapp command to voice dial peers that support BRI backhaul.
Information About MGCP-Controlled Backhaul of BRI Signaling

To configure MGCP-controlled backhaul of BRI signaling, you should understand the following
concept:
• MGCP-Controlled Backhaul of BRI Signaling, page 129
MGCP-Controlled Backhaul of BRI Signaling

The MGCP-Controlled Backhaul of BRI Signaling feature supports a centralized Cisco Unified
CallManager architecture with BRI trunks connected to remote branch offices. Transporting signaling
information from a branch-office MGCP gateway to a centralized media-gateway controller for
processing is called backhaul. D-channel signal information is backhauled to Cisco Unified
CallManager through a TCP session. All Q.931 messages are passed through the TCP connection
between the Cisco MGCP gateway and Cisco Unified CallManager. The MGCP gateway neither parses
nor has any knowledge of the contents of those messages.
This feature enables you to connect remote ISDN PBXs and key systems to a Cisco ISDN BRI network
termination (network side) or PSTN Class 4/5 switch through a Cisco ISDN BRI terminal equipment (as
user side) interface. External call-control entities, such as one or more Cisco Unified CallManager
servers, provide voice service between local and remote branch offices.
Figure 9 depicts a typical network-side scenario. NT denotes network termination; TE denotes terminal
equipment.

129
Information About MGCP-Controlled Backhaul of BRI Signaling
Figure 9 Typical ISDN BRI Network-Side Scenario
Euro ISDN demarcation

S/T
US ISDN demarcation
ISDN BRI
U
ISDN phone PBX TE NT

NT1 ISDN
TE
NT
IP network/
WAN
82726
Media gateway
Figure 10 shows a typical user-side scenario.
Figure 10 ISDN BRI User-Side Scenario
WAN M
V
HQ Cisco Unified CallManager
BRI
PSTN
82768
The following is the sequence of events during normal backhaul:
1. A call comes in from the PSTN and passes over the BRI trunk to the MGCP gateway.
2. The MGCP gateway passes signaling information from the call across the WAN to the Cisco Unified
CallManager at headquarters.
3. Cisco Unified CallManager instructs the MGCP gateway on how to set up and manage the call.
4. The call is established.

130
How to Configure MGCP-Controlled Backhaul of BRI Signaling

• Configuring the BRI Interface as an MGCP-BRI Backhaul Endpoint, page 131 (required)
• Verifying MGCP-BRI Backhaul Configuration, page 132 (optional)
• Troubleshooting Tips for MGCP-Controlled Backhaul of BRI Signaling, page 134 (optional)
Configuring the BRI Interface as an MGCP-BRI Backhaul Endpoint

SUMMARY STEPS
1. enable
3. interface bri slot/port
4. shutdown
5. isdn switch-type basic-net3
6. isdn bind-L3 ccm-manager service mgcp
7. no shutdown
8. no mgcp
9. mgcp
10. exit
DETAILED STEPS

Example:
Router> enable
Step 2 configure terminal Enters global configuration mode on the BRI slot and port.
Example:
Step 3 interface bri slot/port Configures the BRI interface as the MGCP-BRI backhaul
endpoint.
Example: • Slot and port syntax is platform-dependent; type ? to
Router(config)# interface bri 1/0 determine.
Note This command is supported only for a user-side
ETSI NET3 switch-type.

131

Step 4 shutdown (Optional) Clears the interface of any active calls. If there
are no active calls, you can skip this step.
Example:
Router(config-if)# shutdown
Step 5 isdn switch-type basic-net3 Sets the central-office switch type on the ISDN interface to
basic-net3.
Example:
Router(config-if)# isdn switch-type basic-net3
Step 6 isdn bind-L3 ccm-manager service mgcp Sets ISDN L3 binding on the BRI interface.
Example:
Router(config-if)# isdn bind-L3 ccm-manager
service mgcp
Step 7 no shutdown Restarts the interface if it was previously disabled.
Example:
Router(config-if)# no shutdown
Step 8 no mgcp Disables all MGCP applications and protocols.
Example:
Router(config-if)# no mgcp
Step 9 mgcp Restarts MGCP and reregisters the gateway to
Example:
Router(config-if)# mgcp
Step 10 exit Exits interface-configuration mode.
Example:
Router(config-if)# end
Verifying MGCP-BRI Backhaul Configuration

SUMMARY STEPS
1. show isdn status

2. show ccm-manager
3. show ccm-manager backhaul
4. show mgcp endpoint
DETAILED STEPS
Step 1 show isdn status

132
Use the show isdn status command to verify that Layer 2 is established and that Layer 3 is configured
as Cisco Unified CallManager. This output displays only if TEI negotiation is performed at startup.
Router# show isdn status
ISDN BRI1/1 interface

dsl 1, interface ISDN Switchtype = basic-net3
L2 Protocol = Q.921 L3 Protocol(s) = CCM-MANAGER
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Note Use this command only if TEI negotiation is done at startup. Otherwise, TEI negotiation is done
when the first call is placed, so output shows Layer 2 with no TEI negotiated and Layer 3 as
down.

Use the show ccm-manager command to verify your Cisco Unified CallManager configuration on the
gateway.
MGCP Domain Name:3845-1.cisco.com

============================================================
First Backup None
Second Backup None

Last keepalive sent: 20:58:35 UTC Sep 3 2004 (elapsed time:00:00:11)
Last MGCP traffic time: 20:58:35 UTC Sep 3 2004 (elapsed time:00:00:11)
Last switchback time: None
Last MGCP Fallback start time: None
Last MGCP Fallback end time: None
MGCP Download Tones: Disabled

FAX mode:cisco
Step 3 show ccm-manager backhaul

Use the show ccm-manager backhaul command to display information about the BRI backhaul link.
Router# show ccm-manager backhaul
Backhaul Link info:

Link Protocol: TCP
Remote Port Number:2428
Current Link State:OPEN
Statistics:
Packets recvd: 4
Recv failures: 0
Packets xmitted:2

133
Xmit failures: 0
BRI Ports being backhauled:
Slot 0, VIC 0, port 0
Slot 1, VIC 0, port 0
Step 4 show mgcp endpoint

Use the show mgcp endpoint command to display a list of your MGCP endpoints.
Router# show mgcp endpoint
BRI/S1/SU0/P1/1@3745-1
BRI/S1/SU0/P1/2@3745-1
Troubleshooting Tips for MGCP-Controlled Backhaul of BRI Signaling

Table 10 lists commands that are available for troubleshooting your configuration.
Table 10 Troubleshooting Commands
Command Purpose
command-type a-law Enables you to address poor voice quality. If your
system uses a-law pulse-code modulation (PCM),
use this command in interface-BRI configuration
mode to reconfigure the BRI voice port in the
gateway for a-law PCM. The system default is
mu-law PCM.
debug ccm-manager backhaul packets Displays debugging information about
Cisco Unified CallManager backhaul message
packets.
debug isdn q931 Displays debugging information about ISDN L3
Q.931 message packets.
debug mgcp packets Displays debugging information about MGCP
message packets.
Configuring SRTP Mode on Cisco IOS MGCP Gateways

SRTP mode provides secure VoIP calls by addressing security requirements for privacy, integrity, and
confidentiality of voice conversations. IPsec, a standards-based set of security protocols and algorithms,
ensures that signaling information that is sent between the gateway and Cisco Unified CallManager are
encrypted. Media encryption using standards-based Secure Real-Time Transport Protocol (SRTP)
ensures that media streams between supported devices are secure.
Perform this task to configure SRTP mode on the gateway.
Prerequisites for SRTP Mode

You should first establish an IPsec connection between Cisco Unified CallManager and the MGCP
gateway before using the MGCP SRTP package. Otherwise, media keys are sent in clear text and your
voice call is not considered secure.

134
Configuration Examples for MGCP-Controlled Backhaul of BRI Signaling
SUMMARY STEPS
1. enable
3. mgcp package-capability srtp-package
4. mgcp validate call-agent source-ipaddr
5. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 mgcp package-capability srtp-package Enables the MGCP gateway capability to process SRTP
packages.
Example:
Router(config)# mgcp package-capability
srtp-package
Step 4 mgcp validate call-agent source-ipaddr (Optional) Enables the MGCP application validation that
packets received are sent by a configured call agent.
Example:
Router(config)# mgcp validate call-agent
source-ipaddr
Example:
Configuration Examples for MGCP-Controlled Backhaul of BRI

Signaling
This section provides the following configuration example:
• MGCP BRI Backhaul on Cisco 3745: Example, page 136
• MGCP BRI Backhaul on Cisco 3640: Example, page 139

135
MGCP BRI Backhaul on Cisco 3745: Example


!
version 12.3
!
hostname Router
!
boot-start-marker
boot-end-marker
!
!
no network-clock-participate slot 1
no network-clock-participate aim 0
no aaa new-model
ip subnet-zero
ip cef
!
!
!
ip dhcp pool phone1
host 10.3.102.102 255.255.0.0
client-identifier 0100.1121.116b.dd
option 150 ip 10.3.102.99
default-router 10.3.102.2
!
!
ip ids po max-events 100
voice-card 1
no dspfarm
!
voice-card 2
no dspfarm
!
voice-card 3
no dspfarm
!
!
!
ccm-manager mgcp
!
!
!

136
ip address 10.3.102.2 255.255.0.0
duplex auto
speed auto
!
no ip address
shutdown
duplex auto
speed auto
!
interface BRI1/0
no ip address
isdn bind-l3 ccm-manager service mgcp
isdn skipsend-idverify
!
interface BRI1/1
no ip address
isdn protocol-emulate network
isdn layer1-emulate network
!
interface BRI2/0
no ip address
!
interface BRI2/1
no ip address
!
interface BRI3/0
no ip address
!
interface BRI3/1
no ip address
!
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.3.0.1
!
ip http server
no ip http secure-server
!

137
!
access-list 10 deny 10.3.102.99 log
access-list 10 permit any
!
!
!
control-plane
!
!
call application alternate DEFAULT
!
!
voice-port 1/1/0
!
voice-port 1/1/1
!
voice-port 2/0/0
!
voice-port 2/0/1
!
voice-port 3/0/0
!
voice-port 3/0/1
!
voice-port 3/1/0
!
voice-port 3/1/1
!
voice-port 3/1/2
!
voice-port 3/1/3
!
!
mgcp
mgcp package-capability srtp-package
!
!
!
!
application mgcpapp
direct-inward-dial
port 3/0/0
forward-digits all
!
application mgcpapp
destination-pattern 9...
incoming called-number .
!
port 3/1/0
!
destination-pattern 6T
direct-inward-dial
port 3/0/1
!

138
port 3/1/3
!
destination-pattern 2T
direct-inward-dial
port 2/0/1
!
application mgcpapp
direct-inward-dial
port 2/0/0
forward-digits all
!
!
!
call-manager-fallback
max-conferences 8
ip source-address 10.3.102.2 port 2000
max-ephones 2
max-dn 4
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
login
!
end
MGCP BRI Backhaul on Cisco 3640: Example

version 12.2
no service dhcp
!
hostname 3640
!
!
voice-card 3
!
ip subnet-zero
!
!
!
isdn switch-type primary-qsig
!
!
voice call carrier capacity active
!
voice service voip
h323
call start slow
!
!
!
!
mta receive maximum-recipients 0
ccm-manager mgcp

139
!
controller T1 3/0
framing esf
linecode b8zs
!
controller T1 3/1
framing esf
linecode b8zs
!
!
!
ip address 10.15.43.101 255.255.0.0
duplex auto
speed auto
no cdp enable
!
interface Serial0/0
no ip address
encapsulation frame-relay
shutdown
clockrate 125000
frame-relay lmi-type ansi
!
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/1
no ip address
shutdown
clockrate 125000
!
interface BRI1/0
no ip address
!
interface BRI1/1
no ip address
isdn switch-type basic-qsig
!
no ip address
isdn switch-type primary-qsig
no cdp enable
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.15.10.11
ip http server
!
ip pim bidir-enable
!
!
!
call rsvp-sync

140
Where to Go Next
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 2/0/0
!
voice-port 2/0/1
!
voice-port 2/1/0
!
voice-port 2/1/1
!
voice-port 3/0:23
!
mgcp
mgcp sdp simple
!
!
!
!
!
!
!
application mgcpapp
port 2/0/0
!
application mgcpapp
port 2/0/1
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
login
!
!
end
Where to Go Next

141
• “Configuring ISDN BRI” in the Cisco IOS Dial Technologies Configuration Guide,
Release 12.4—Describes how to configure ISDN BRI on the voice gateway.
• “ISDN Switch Types, Codes, and Values” appendix in the Debug Command Reference,
Release 12.4—Describes supported switch types.
• Cisco Unified CallManager documentation—Describes how to install and configure Cisco Unified
CallManager.

142
Configuring Tone Download to MGCP Gateways
feature enables the Cisco IOS gateway to download region-specific tones and the associated frequencies,
amplitudes, and cadences in its XML configuration files.
Cisco IOS gateways support static tone tables that are predefined for each country in Cisco IOS tone
tables. Voice ports use the static tone tables associated with the Cisco Unified CallManager network
locale unless the custom tone download feature is enabled
Feature History for Customizable Tone Download to Cisco IOS MGCP Gateways from Cisco Unified CallManager
12.2(15)ZJ This feature was introduced.
Feature History for Globalized Cadence and Tone for Cisco IOS Gateways
12.2(11)T This feature was introduced.
Cisco Unified CallManager and Cisco IOS Interoperability Guide

143
Contents
Contents
• Information About Tone Download to MGCP Gateways, page 144
• How to Configure Tone Download to MGCP Gateways, page 146
• Configuration Examples for Tone Download to MGCP Gateways, page 158
Information About Tone Download to MGCP Gateways

To configure tone download, you should be familiar with the following concepts:
• Tone Download Process for MGCP Gateways, page 144
• Static Tones, page 144
• Custom Tones, page 146
Tone Download Process for MGCP Gateways

When configuring MGCP gateways in a Cisco IP-telephony network, you can use a centralized TFTP
server in your network to automatically download an XML file with the gateway-specific configuration.
The XML configuration file includes the network locale for each voice port on the gateway. The network
locale configured in Cisco Unified CallManager defines the tones and cadences that are used by a device
in a specific geographic area. A network locale is associated with each voice port in the MGCP gateway.
When the XML file is downloaded to the gateway, it is parsed, converted to Cisco IOS commands, and
the active configuration is updated. If the gateway is restarted or reset, it triggers a download of the XML
file from the TFTP server. If the specified TFTP server is not available, the gateway keeps trying to
download the updated XML file and does not alter the current configuration.
For information on downloading XML configuration files to your MGCP gateway, see the “Enabling
Single-Point Configuration for MGCP Gateways” section on page 44.
Static Tones
The Globalized Cadence and Tone for Cisco IOS Gateways feature enables Cisco IOS gateways to
support Cisco Unified CallManager localization using static tone tables that are predefined for each
country in Cisco IOS tone tables. The static tone table that is used for a voice port is determined by the
network locale that is specified for the voice port in Cisco Unified CallManager. When an MGCP
gateway registers to Cisco Unified CallManager, or if the gateway restarts or resets, the network locale
for each voice port is downloaded in the gateway’s XML configuration file.
The static tones and cadences associated with the Cisco Unified CallManager network locale are used
by a voice port unless a custom tone table is downloaded. No configuration is required on the MGCP
gateway to use the static tones.

144
Information About Tone Download to MGCP Gateways
Table 11 shows the list of valid two-letter country codes and the corresponding countries.
Table 11 Country Codes
Code Country Code Country

AR Argentina KE Kenya
AT Austria KR Korea Republic
AU Australia LB Lebanon
BE Belgium LU Luxemborg
BR Brazil MX Mexico
CA Canada MY Malaysia
CH Switzerland NG Nigeria
CN China NL Netherlands
CO Colombia NO Norway
CY Cyprus NP Nepal
CZ Czech Republic NZ New Zealand
DE Germany PA Panama
DK Denmark PE Peru
EG Egypt PH Philippines
ES Spain PK Pakistan
FI Finland PL Poland
FR France PT Portugal
GB United Kingdom RU Russian Federation
GH Ghana SA Saudi Arabia
GR Greece SE Sweden
HK Hong Kong SG Singapore
HU Hungary SI Slovenia
ID Indonesia SK Slovakia
IE Ireland TH Thailand
IL Israel TR Turkey
IN India TW Taiwan
IS Iceland US United States
IT Italy VE Venezuela
JO Jordan ZA South Africa
JP Japan ZW Zimbabwe

145
How to Configure Tone Download to MGCP Gateways
Custom Tones
feature enables an MGCP gateway to download locale-specific tones and their associated frequency,
amplitude, and cadence information from the XML-based configuration file.
The XML tone file includes all supported tones for one country with the frequency, amplitude, and
cadence information. The XML tone file is parsed and saved into a custom tone table on the MGCP
gateway. Each gateway supports up to two custom tone tables. The default values for North America are
overwritten with the new values specified in the XML file. Dual tones and sequential tones, and up to
4 frequencies for standard or custom tones are supported.
When Cisco Unified CallManager requests a specific tone, the gateway references the custom tone table
associated with the network locale of the voice port. After the custom tone specification is downloaded
to the gateway, it can be used even if the gateway loses connectivity to Cisco Unified CallManager and
reverts to H.323 control in fallback mode.
If custom tone download is not configured, the voice port uses the static tone table associated with the
network locale of the voice port. If custom tone download is configured but fails, the voice port continues
to use the static tone table for the network locale.
Figure 11 shows the download of the XML file from the TFTP server to the MGCP gateway.
Figure 11 Download of XML File from TFTP Server
Cisco Unified CallManager cluster
XML file
TFTP server
IP cloud
MGCP gateway
After tone download
Static tone
Custom tone
82980

• Verifying Globalized Cadence and Tone Configuration, page 147 (optional)
• Configuring Customizable Tone Download to Cisco IOS MGCP Gateways, page 151 (required)
• Verifying Customizable Tone Download, page 152 (optional)

146
Verifying Globalized Cadence and Tone Configuration

Perform this task to verify which network locale is configured in Cisco Unified CallManager.
Note There are no configuration tasks necessary to enable globalized cadence and tone except those described
in Prerequisites.
Prerequisites
• Cisco CallManager 3.2 or higher
• Cisco Unified CallManager 4.0 or higher
• Cisco IOS gateway must be configured for MGCP and must have single-point configuration enabled.
See “Configuring MGCP Gateway Support for Cisco Unified CallManager” on page 23 for
information.
Note The IP hostname should match the gateway name that is specified in the Cisco Unified
CallManager configuration.
• Ad-hoc conferencing and transcoding port adapter (WS-SVC-CMM-ACT) must be installed and
configured on the Cisco Catalyst 6500 Series and Cisco 7600 Series Router Communication Media
Module (CMM).
SUMMARY STEPS
1. show voice port slot/port
DETAILED STEPS
Step 1 show voice port slot/port

Use the show voice port command to verify the globalized cadence and tone configuration as shown in
the following examples.
Cisco IAD2420 series

Router# show voice port 0/5
E&M 0:5 Slot is 0, Port is 5

Type of VoicePort is E&M
Operation State is DOWN

147

Coder Type is g729ar8
Voice Activity Detection is enabled
Nominal Playout Delay is 60 milliseconds
Maximum Playout Delay is 200 milliseconds
Rx A bit no conditioning set
Rx B bit no conditioning set
Rx C bit no conditioning set
Rx D bit no conditioning set
Tx A bit no conditioning set
Tx B bit no conditioning set
Tx C bit no conditioning set
Tx D bit no conditioning set
Rx Seize ABCD bits = 1111 Default pattern
Rx Idle ABCD bits = 0000 Default pattern
Tx Seize ABCD bits = 1111 Default pattern
Tx Idle ABCD bits = 0000 Default pattern
Ignored Rx ABCD bits = BCD
Region Tone is set for CN
Analog Info Follows:

Currently processing none
Maintenance Mode Set to None (not in mtc mode)
Number of signaling protocol errors are 0
Impedance is set to 600r Ohm
Voice card specific Info Follows:

Operation Type is 2-wire
E&M Type is 1
Signal Type is immediate
Dial Type is dtmf
In Seizure is inactive
Out Seizure is active
Digit Duration Timing is set to 100 ms
InterDigit Duration Timing is set to 100 ms
Pulse Rate Timing is set to 10 pulses/second
InterDigit Pulse Duration Timing is set to 750 ms
Clear Wait Duration Timing is set to 400 ms
Wink Wait Duration Timing is set to 200 ms
Wait Wink Duration Timing is set to 550 ms
Wink Duration Timing is set to 200 ms
Delay Start Timing is set to 150 ms
Delay Duration Timing is set to 2000 ms
Dial Pulse Min. Delay is set to 140 ms
Percent Break of Pulse is 60 percent
Auto Cut-through is disabled

148
Dialout Delay is 300 ms
Cisco 2600 series

Router# show voice port
TE Basic Rate Interface 1/0/0 Slot is 1, Sub-unit is 0, Port is 0
Type of VoicePort is ISDN-BRI
The Last Interface Down Failure Cause is Administrative Shutdown
Busyout on interface monitor
Ethernet0/0
Wait Release Time Out is 30 s
TE Basic Rate Interface 1/0/1 Slot is 1, Sub-unit is 0, Port is 1
Type of VoicePort is ISDN-BRI
Wait Release Time Out is 30 s

149
Cisco 3660
Foreign Exchange Station 2/0/0 Slot is 2, Sub-unit is 0, Port is 0
Type of VoicePort is FXS
Cisco VG200
DS0 Group 1/0:15 - 1/0:15

Type of VoicePort is XCC

150

Companding Type is A-law
Rx A bit no conditioning set
Rx B bit no conditioning set
Rx C bit no conditioning set
Rx D bit no conditioning set
Tx A bit no conditioning set
Tx B bit no conditioning set
Tx C bit no conditioning set
Tx D bit no conditioning set
Continuity Test Tone CO1 is set to 2010
Continuity Test Tone CO2 is set to 1780
Configuring Customizable Tone Download to Cisco IOS MGCP Gateways

Perform this task to download custom tones to the Cisco IOS gateway.
Prerequisites
• Cisco CallManager 3.3(2) or higher.
• Cisco Unified CallManager 4.0 or higher
• DSP 3.6.16 or later for analog interfaces; DSP 4.0 or later for digital interfaces.
• For languages other than English and countries other than the United States, locale files that provide
regional tones and cadences must be installed in Cisco Unified CallManager. The locale installer
adds the files to the correct directories and updates the Cisco Unified CallManager database.
See the Using the Cisco IP Telephony Locale Installer document for information.
• The following cards are supported:
– AIM-ATM-VOICE
– AIM-VOICE
– NM-HDA
– NM-HDV
– VIC-2FXO
– VIC-2FXS
Restrictions
Up to two custom tone tables are supported on a gateway; that is, no more than two custom tone tables
can be downloaded to one gateway even if there are more that two countries or regions configured for
the gateway.

151
SUMMARY STEPS
1. enable
3. ccm-manager config {server ip-address | name}
4. ccm-manager config
5. ccm-manager download-tones
6. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 ccm-manager config {server ip-address | name} Specifies the TFTP server that contains the XML
configuration file to download.
Example: Note Up to three servers can be configured.
Router(config)# ccm-manager config server
10.10.10.0
Step 4 ccm-manager config Enables single-point download and configuration.
Example:
Router(config)# ccm-manager config
Step 5 ccm-manager download-tones Enables the custom tone download to the gateway.
Example:
Router(config)# ccm-manager download-tones
Step 6 exit Exits the session.
Example:
Verifying Customizable Tone Download

Perform this task to verify that the customizable tone download and voice ports are configured correctly.
SUMMARY STEPS
1. show voice port port/slot

152
2. show ccm-manager download-tones

3. debug ccm-manager config-download all
4. debug ccm-manager config-download tone
DETAILED STEPS
Step 1 show voice port port/slot

Use the show voice port command to verify that the custom tones are assigned. The following sample
shows that voice port 1/0/1 has C1 assigned, which corresponds to France:
!
recEive and transMit Slot is 1, Sub-unit is 0, Port is 1
Type of VoicePort is E&M
.
.
.
Rx Seize ABCD bits = 1111 Default pattern
Rx Idle ABCD bits = 0000 Default pattern
Tx Seize ABCD bits = 1111 Default pattern
Tx Idle ABCD bits = 0000 Default pattern
Ignored Rx ABCD bits = BCD
Region Tone is set for C1
!
! Custom Tone 1 is assigned to this voice port.
Note Voice ports are automatically configured during the initial download of the XML file from the
TFTP server.
Step 2 show ccm-manager download-tones

Use the show ccm-manager download-tones command to verify that the custom tones have been
downloaded. The following sample output shows that Custom Tone 1 is assigned to France and that
Custom Tone 2 is assigned to Spain:
Router# show ccm-manager download-tones

153
MGCP Download Tones: Enabled

Custom Tone 1: France
Custom Tone 2: Spain
The following sample output shows the downloaded tone information including the number of
frequencies and cadences:
Router# show ccm-manager download-tones C1
!
Custom Tone 1 : United Kingdom
Pulse dial: normal, Percent make: 35%, DTMF low Amp. = 65438, high Amp. = 65463 Pcm: u-Law
FXS FXO E&M FXS FXO E&M
Dual Tone DR NF FOF FOS AOF AOF AOF AOS AOS AOS ONTF OFTF ONTS OFTS ONTT OFTT ONT4 OFT4
(optional) FOF2 FOS2 FOF3 FOS3 FOF4 FOS4 FOT FO4 AOT AO4 RCT1 RCT2 RCT3 RCT4
BUSY 0 1 400 0 -200 -200 -240 0 0 0 375 375 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
RING_BACK 0 2 400 450 -190 -190 -190 -190 -190 -190 400 200 400 2000 0 0 0 0 0 0 0 0 0 0
CONGESTION 0 1 400 0 -200 -200 -200 0 0 0 400 350 225 525 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
NUMBER_UNOBTAINABLE 0 1 400 0 -150 -150 -150 0 0 0 400 350 225 525 0 0 0 0 0 0 0 0 0 0 0 0
DIAL_TONE 0 2 350 440 -150 -150 -150 -150 -150 -150 65535 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
DIAL_TONE2 0 2 350 440 -150 -150 -150 -150 -150 -150 65535 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0
OUT_OF_SERVICE 0 1 950 0 -150 -150 -185 0 0 0 330 330 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ADDR_ACK 0 1 600 0 -240 -240 -240 0 0 0 125 125 125 65535 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
DISCONNECT 0 1 600 0 -150 -150 -150 0 0 0 330 330 330 65535 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
OFF_HOOK_NOTICE 0 2 1400 2040 -240 -240 -240 -240 -240 -240 100 100 0 0 0 0 0 0 0 0 0 0 0
OFF_HOOK_ALERT 0 2 1400 2040 -150 -150 -185 -150 -150 -185 100 100 0 0 0 0 0 0 0 0 0 0 0 0
WAITING 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
CONFIRM 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
CNFWRN_J 0 1 950 0 -170 -170 -190 0 0 0 100 100 100 65535 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
CNFWRN_D 0 1 600 0 -170 -170 -190 0 0 0 100 100 100 65535 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
STUTT_DIALTONE 0 2 350 440 -150 -150 -150 -150 -150 -150 100 100 100 100 100 100 65535 0 0
Sequence Tone DR NF F1C1 F2C1 AOF AOS C1ONT C1OFT C2ONT C2OFT C3ONT C3OFT C4ONT C4OFT F1C2
F2C2 F1C3 F2C3 F1C4 F2C4
INTERCEPT 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
TONE_ON_HOLD 0 1 500 500 0 0 100 150 100 150 100 150 0 10000 500 0 500 0 0 0
NO_CIRCUIT 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
!
Legend:
DR : direction NF : number of frequency
FO<F,S,T,4> : frequency of<1st,2nd,3rd,4th> AO<F,S,T,4> : amplitude of<1st,2nd,3rd,4th>
FOF<1-4> : frequency of 1st, cadence<1-4> FOS<1-4> : frequency of 2nd, cadence<1-4>
ONT<F,S,T,4> : on time<1st,2nd,3rd,4th> OFT<F,S,T,4> : off time<1st,2nd,3rd,4th>
RCT<1-4> : repeat count for cadence<l-4> F(1-4>C<1-4> : frequency<1-4> of cadence<1-4>
C<1-4>ONT : cadence<1-4> on time C<1-4>OFT : cadence<1-4> off time
Step 3 debug ccm-manager config-download all

The following sample output shows the download of the country-specific gateway tone files:
Router# debug ccm-manager config-download all
!
00:53:17: cmapp_xml_tftp_download_file line 170:
File (tftp://10.10.10.55/met2.cnf.xml) read 7490 bytes
:
00:53:17: cmapp_xml_get_info_from_name: name = AALN/S1/SU0/0@met2
00:53:17: cmapp_process_tag_networkLocale
00:53:17: cmapp_process_tag_networkLocale: NetworkLocale = Hong Kong
:
00:53:17: cmapp_xml_get_info_from_name: name = AALN/S1/SU0/1@met2
00:53:17: cmapp_process_tag_networkLocale
00:53:17: cmapp_process_tag_networkLocale: NetworkLocale = United Kingdom
Step 4 debug ccm-manager config-download tone

154
Use the debug ccm-manager config-download tone command to troubleshoot the download procedure.
The following sample output shows the locale name as United Kingdom and lists all of the dual-tone
parameters for that region:
Router# debug ccm-manager config-download tone
00:09:07:
cmapp_prefix_process_tag_tones:
00:09:07: cmapp_process_tag_trkLocaleName: region = United Kingdom
00:09:07: cmapp_process_tag_pulse_ratio: pulse ratio = 40
00:09:07: cmapp_process_tag_dtmf_llevel: low frequency level = 65438
00:09:07: cmapp_process_tag_dtmf_hlevel: high frequency level = 65463
00:09:07: cmapp_process_tag_special_oper: operation = uLaw
00:09:07: cmapp_prefix_process_tag_lpig:
00:09:07: cmapp_process_tag_fxs: ignore LPIG for fxs
00:09:07: cmapp_process_tag_fxo: ignore LPIG for fxo
00:09:07: cmapp_process_tag_digital: ignore LPIG for digital
00:09:07: cmapp_prefix_process_tag_lpog:
00:09:07: cmapp_process_tag_fxs: ignore LPOG for fxsBoth ports are in service
00:09:07: cmapp_process_tag_fxo: ignore LPOG for fxo
00:09:07: cmapp_process_tag_digital: ignore LPOG for digital
00:09:07: cmapp_prefix_process_tag_tonetable_info:
00:09:07:
cmapp_prefix_process_tag_dualtone: TID=[0:CPTONE_BUSY]
00:09:07: cmapp_process_tag_nf: number of frequencies = 1
00:09:07: cmapp_process_tag_dr: direction = 0
00:09:07: cmapp_process_tag_fof: frequency 1 = 400
00:09:07: cmapp_process_tag_fos: frequency 2 = 0
00:09:07: cmapp_process_tag_fot: frequency 3 = 0
00:09:07: cmapp_process_tag_fo4: frequency 4 = 0
00:09:07: cmapp_prefix_process_tag_aof_level:
00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -200
00:09:07: cmapp_process_tag_fxo: amplitude of 1st = -200
00:09:07: cmapp_process_tag_digital: amplitude of 1st = -240
00:09:07: cmapp_prefix_process_tag_aos_level:
00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 0
00:09:07: cmapp_process_tag_digital: amplitude of 2nd = 0
00:09:07: cmapp_prefix_process_tag_aot_level:
00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 0
00:09:07: cmapp_process_tag_digital: amplitude of 3rd = 0
00:09:07: cmapp_prefix_process_tag_ao4_level:
00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 4th = 0
00:09:07: cmapp_process_tag_digital: amplitude of 4th = 0
00:09:07: cmapp_process_tag_ontf: frequency 1 on time = 375
00:09:07: cmapp_process_tag_oftf: frequency 1 off time = 375
00:09:07: cmapp_process_tag_onts: frequency 2 on time = 0
00:09:07: cmapp_process_tag_ofts: frequency 2 off time = 0
00:09:07: cmapp_process_tag_ontt: frequency 3 on time = 0
00:09:07: cmapp_process_tag_oftt: frequency 3 off time = 0
00:09:07: cmapp_process_tag_ont4: frequency 4 on time = 0
00:09:07: cmapp_process_tag_oft4: frequency 4 off time = 0
00:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 0
00:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 0
00:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 0

155
00:09:07:
cmapp_prefix_process_tag_dualtone: TID=[1:CPTONE_RING_BACK]
00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = -190
00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = -190
00:09:07: cmapp_process_tag_digital: amplitude of 2nd = -190
00:09:07:
cmapp_prefix_process_tag_dualtone: TID=[2:CPTONE_CONGESTION]
00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 0
00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 0
00:09:07: cmapp_process_tag_digital: amplitude of 2nd = 0

156

The following sample output shows the network locales in the XML file:
Router# debug ccm-manager config-download tone
!
00:54:08: cmapp_xml_tftp_download_file line 170
File (tftp://10.10.10.55/Hong_Kong/gateway-tones.xml) read 20993 bytes
00:54:08: cmapp_prefix_process_tag_tones
00:54:08: cmapp_process_tag_trkLocaleName: region = Hong Kong
!
00:54:08: cmapp_xml_tftp_download_file line 170
File (tftp://10.10.10.55/United_Kingdom/gateway-tones.xml) read 20993 bytes
00:54:08: cmapp_prefix_process_tag_tones
00:54:08: cmapp_process_tag_trkLocaleName: region = United_Kingdom
Note For a description of the significant fields displayed in these output examples, see the Cisco IOS Voice
Command Reference and Cisco IOS Debug Command Reference, Release 12.3T.
Troubleshooting Tips for Customizable Tone Download

If the custom tone file is not downloaded at least once, the North America tones are used. When a
download fails, the static tones associated with the network locale of the voice port are used. For
example, if a voice port is defined with a static tone for Hong Kong, and the download fails, the static
tone for Hong Kong is used.
The administrator, after correcting the problem (a glitch in the network, a TFTP server that is down, or
missing XML tone files), must reset the gateway from Cisco Unified CallManager. Resetting the
gateway triggers a download of the XML configuration file.
If tone download is successful, the downloaded tone file overwrites the default custom tone table, and
the voice port refers to the downloaded custom tones.

157
Configuration Examples for Tone Download to MGCP Gateways
Configuration Examples for Tone Download to MGCP Gateways

This section contains the following examples:
• Customizable Tone Download Voice-Port Configuration: Example, page 158
• Customizable Tone Download Using Single-Point Configuration: Example, page 158
Customizable Tone Download Voice-Port Configuration: Example

The following sample output shows that voice port 1/0/0 has been configured to use C1:
Router# show voice port 1/0/0
!
Foreign Exchange Station 1/0/0 Slot is 1, Sub-unit is 0, Port is 0
Type of VoicePort is FXS
Region Tone is set for C1
Customizable Tone Download Using Single-Point Configuration: Example

The following example shows single-point configuration enabled for an MGCP gateway:
!
version 12.3
no parser cache
!
hostname Router
!
!
voice-card 1
!
ip subnet-zero
!
ip domain-name anything.com
!
mgcp
call rsvp-sync
!
! The following output shows that the TFTP server has an IP address of 10.10.10.50 and
that the download has been enabled.
!

158
Where to Go Next

ccm-manager config
ccm-manager download-tones
!
Where to Go Next
• “Enabling Single-Point Configuration for MGCP Gateways” section on page 44 in Configuring
MGCP Gateway Support for Cisco Unified CallManager—Describes how to configure MGCP
gateways by downloading XML configuration files.
• Using the Cisco IP Telephony Locale Installer—Describes how to install the Cisco IP Telephony
Locale Installer for Cisco Unified CallManager.

159

160
Configuring MCID for Cisco IOS Voice Gateways
The MCID for Cisco IOS Voice Gateways feature supports the Malicious Call Identification (MCID)
supplementary service that enables Cisco Unified CallManager to identify the source of malicious calls.
Feature History for MCID for Cisco IOS Voice Gateways

12.3(14)T Support was added for the new Cisco IOS command structure for voice
applications in the HTTP Client API for TCL IVR feature.

161
Contents
Contents
• “Prerequisites for MCID for Cisco IOS Voice Gateways” on page 162
• “Restrictions for MCID for Cisco IOS Voice Gateways” on page 162
• “Information About MCID for Cisco IOS Voice Gateways” on page 163
• “How to Configure MCID for Cisco IOS Voice Gateways” on page 164
• “Configuration Examples for MCID for Cisco IOS Voice Gateways” on page 169
• “Where to Go Next” on page 173
• “Additional References” on page 173
Prerequisites for MCID for Cisco IOS Voice Gateways

• MCID must be configured in Cisco Unified CallManager 4.0 or later. For information, see the
“Malicious Call Identification” chapter in the Cisco Unified CallManager Features and Services
Guide, Release 4.0(1).
• Your platform must support MCID and TCL IVR 2.0.
• You must either use the script app_mcid.2.0.0.40.tcl or a later version, or write your own TCL
IVR 2.0 script that implements MCID. To download the script, go to the Software Download site at
http://www.cisco.com/cgi-bin/tablebuild.pl/tclware. To write your own script, see the TCL IVR API
Version 2.0 Programming Guide.
• If you require an MCID service log in RADIUS, you can write a script that supports the RADIUS
service and uses the aaa accounting update command to generate an accounting record.
WS-SVC-CMM-6T1, WS-SVC-CMM-6E1, or WS-SVC-CMM-24 FXS port adapter in H.323
environment.
Restrictions for MCID for Cisco IOS Voice Gateways

• Supported only for NET5 switches that have MCID functionality enabled. Other switch types are
not supported.
• Supported only for incoming calls from the ISDN network.
• MCID requests from the central office are ignored by Cisco Unified CallManager and are not
supported by the Cisco voice gateway.
• Service provider on the time-division multiplexing (TDM) side of the PSTN must have MCID
functionality enabled.
• ISDN interface on the voice gateway must have the ISDN switch type set to primary-net5 with the
isdn switch-type command and operate in user-side mode (default).
• Voice gateways with PRI interfaces should provide the following capabilities:
– Receive MCID requests relating to the call from upper layers and relay them to the connected
network using the PRI protocol specified for the MCID service.

162
Information About MCID for Cisco IOS Voice Gateways
– Receive MCID related response signals and information from the connected network using the
PRI protocol specified for the MCID service. Cisco Unified CallManager ignores the signals
and information.
• Not supported on the Access Gateway Module (AGM).
Information About MCID for Cisco IOS Voice Gateways

To configure a voice gateway for MCID, you should understand the following concept:
• MCID, page 163
MCID
Malicious Call Identification (MCID) is a supplementary service that enables Cisco Unified
CallManager to identify the source of malicious calls. A user who receives a malicious call from another
network, typically the PSTN, can select a softkey on the IP phone which immediately notifies the system
administrator, flags the call detail record (CDR) for the Cisco Unified CallManager cluster, and notifies
the PSTN of the malicious nature of the call, allowing the offnet system to take action, such as notifying
legal authorities.
Figure 12 shows an example of the MCID call flow. After receiving an MCID request from an endpoint
device (victim), Cisco Unified CallManager sends an H.225 Facility message with the MCID
information element (IE) to the voice gateway. The gateway sends a Q.931 Facility message with the
MCID IE to the ISDN network (central office).
Figure 12 MCID Functionality
Central office (CO)
PSTN
Caller
Q931 facility message

(MCID response) (MCID request)
IP LAN
V
H.225 Facility
103191
Victim message
MCID IE

163
How to Configure MCID for Cisco IOS Voice Gateways
A called party invokes MCID by pressing the appropriate softkey on the IP phone. A configurable timer
is available when awaiting a response after sending a Facility message to the PSTN. If a response is not
received within the specified time, the TCL IVR script is notified. Depending on how the script is
written, it could try to reinvoke MCID or perform some other action, for example, playing a message to
the user that the MCID attempt did not work.

Perform these tasks to support MCID on your MGCP gateway:
• Enabling the ISDN Interface to Send MCID Requests, page 164 (required)
• Configuring MCID on the Voice Gateway (Cisco IOS Release 12.3(14)T), page 165 (required)
• Configuring MCID on the Voice Gateway (Cisco IOS Release 12.3(11)T), page 167 (required)
Enabling the ISDN Interface to Send MCID Requests

Perform this task to enable an ISDN interface to send MCID requests and to set the timer.
SUMMARY STEPS
1. enable
3. interface serial slot/port:timeslot
4. isdn switch-type {primary-net5 | primary-ni2}
5. isdn incoming-voice {data | modem | voice}
6. isdn supp-service mcid
7. isdn t-activate msec
8. exit
DETAILED STEPS

Example:
Router> enable
Example:

164

Step 3 interface serial slot/port:timeslot Enters interface configuration mode and specifies a serial
interface created on a channelized E1 or channelized T1
controller.
Example:
Router(config)# interface serial 2/1:23
Step 4 isdn switch type {primary-net5 | primary-ni} Specifies the user-side switch type.
Note Only NET5 switches are supported.
Example:
Router(config-if)# isdn switch-type
primary-net5
Step 5 isdn incoming-voice {data | modem | voice} Specifies whether incoming voice calls are handled as data,
voice, or modems.
Example:
Router(config-if)# isdn incoming-voice voice
Step 6 isdn supp-service mcid Configures the ISDN interface to send the MCID invocation
and response on the specified serial interface.
Example:
Router(config-if)# isdn supp-service mcid
Step 7 isdn t-activate msec (Optional) Specifies how long to wait for a response from
the PSTN after sending the MCID request.
Example: When the timer expires, the TCL IVR script receives an
Router(config-if)# isdn t-activate 4000 expiration event and depending on your script, it could
trigger an announcement or initiate another attempt.
Note The timer starts when there is a disconnect message,
and both calls legs are reclaimed after the timer
expires.
Example:
Router(config-if)# end
Configuring MCID on the Voice Gateway (Cisco IOS Release 12.3(14)T)

Use this procedure to define the MCID application on a voice gateway that is running Cisco IOS
Release 12.3(14)T or later. To verify your release, use the show version command.
SUMMARY STEPS
1. enable
3. application
4. service mcid location
5. param mcid-release-timer seconds
6. param retry-count number

165
7. exit
9. service mcid
10. incoming called-number string
12. port
13. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 application Enters application configuration mode.
Example:
Router(config)# application
Step 4 service mcid flash:app_mcid.2.0.0.40.tcl Specifies the name and location of the MCID script.
Example:
Router(config-app)# service mcid
flash:app_mcid.2.0.0.40.tcl
Step 5 param mcid-release-timer seconds (Optional) Number of seconds the script waits before
releasing both call legs after it receives a disconnect
message. Default is 60 seconds.
Example:
Router(config-app-param)# param
mcid-release-timer 30
Step 6 param retry-count number (Optional) Maximum number of times the called party can
trigger MCID if all previous attempts failed. Default is 0,
which means the user can invoke MCID as many times as
Example:
Router(config-app-param)# param retry-count 3
needed.
Example:
Router(config-app-param)# exit

166

Step 8 dial-peer voice tag pots Configures incoming dial peer and enters dial-peer
configuration mode.
Example:
Step 9 service mcid Configures the incoming dial peer to use the MCID
application.
Example:
Router(config-dial-peer)# service mcid
Step 10 incoming called-number string Configures the incoming called number for the MCID
application.
Example:
Router(config-dial-peer)# incoming
called-number 222....
Step 11 direct-inward-dial Configures direct-inward-dial (DID) for the MCID
application.
Example:
Step 12 port slot/port:timeslot Configures the port for the MCID application.
Note The syntax of the port command is
Example: platform-specific. For information on the specific
Router(config-dial-peer)# port 3/0:23 syntax for your platform, see the Cisco IOS Voice
Command Reference.
Example:
Configuring MCID on the Voice Gateway (Cisco IOS Release 12.3(11)T)

Use this procedure to define the MCID application on a voice gateway that is running Cisco IOS
Release 12.3(11)T. To verify your release, use the show version command.
SUMMARY STEPS
1. enable
3. call application voice mcid location
4. call application voice mcid mcid-release-timer seconds
6. application mcid
7. incoming called-number string
9. port

167
10. exit
DETAILED STEPS

Example:
Router> enable
Example:
Step 3 call application voice mcid location Specifies the name and location of the MCID script.
Example:
Router(config)# call application voice mcid
flash:app_mcid.2.0.0.40.tcl
Step 4 call application voice mcid mcid-release-timer (Optional) Number of seconds the script waits to release
seconds both call legs after it receives a disconnect message. Default
is 60 seconds.
Example:
Router(config)# call application voice mcid
mcid-release-timer 30
Step 5 dial-peer voice tag pots Configures incoming dial peer and enters dial-peer
configuration mode.
Example:
Step 6 application mcid Configures the incoming dial peer to use the MCID
application.
Example:
Router(config-dial-peer)# application mcid
Step 7 incoming called-number string Configures the incoming called number for the MCID
application.
Example:
Router(config-dial-peer)# incoming
called-number 222....
Step 8 direct-inward-dial Configures direct-inward-dial (DID) for the MCID
application.
Example:

168
Configuration Examples for MCID for Cisco IOS Voice Gateways

Step 9 port slot/port:timeslot Configures the port for the MCID application.
Note The syntax of the port command is
Example: platform-specific. For information on the specific
Router(config-dial-peer)# port 3/0:23 syntax for your platform, see the Cisco IOS Voice
Command Reference.
Example:

• Configuring MCID in Cisco IOS Release 12.3(14)T (Cisco 2801): Example, page 169
• Configuring MCID in Cisco IOS Release 12.3(11)T (Cisco 3745): Example, page 1719
Configuring MCID in Cisco IOS Release 12.3(14)T (Cisco 2801): Example

!
version 12.3
no service timestamps debug uptime
no service timestamps log uptime
!
hostname router_2801
!
boot-start-marker
boot-end-marker
!
no logging console
!
no aaa new-model
!
resource manager
!
no mmi pvc
ip subnet-zero
ip cef
!
!
no ip dhcp use vrf connected
!
!
no ip domain lookup

169
!
voice-card 0
!
!
!
application
service mcid flash:app_mcid.2.0.0.40.tcl
param mcid-release-timer 10
param retry-count 3
!
!
controller T1 0/2/0
framing esf
linecode b8zs
pri-group timeslots 1-24
!
controller T1 0/2/1
framing esf
linecode b8zs
!
!
ip address 9.1.0.102 255.255.0.0
duplex auto
speed auto
no keepalive
!
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/2/0:23
no ip address
isdn supp-service mcid
isdn T-Activate 5000
no cdp enable
!
ip classless
!
ip http server
!
disable-eadi
!
!
control-plane
!
!
voice-port 0/2/0:23
!
!
!
service mcid
direct-inward-dial
port 0/2/0:23
prefix 111111

170
!
playout-delay minimum low
codec g711ulaw
no vad
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
login
!
end
Configuring MCID in Cisco IOS Release 12.3(11)T (Cisco 3745): Example

!
version 12.3
!
hostname router_3745
!
!
voice-card 3
dspfarm
!
no aaa new-model
ip subnet-zero
!
!
isdn switch-type primary-4ess
!
!
!
!
controller T1 3/0
framing esf
linecode b8zs
pri-group timeslots 1-24
!
controller T1 3/1
framing sf
linecode ami
!
!
ip address 10.4.175.116 255.255.0.0
duplex auto

171
speed auto
!
shutdown
duplex auto
speed auto
!
isdn supp-service mcid
no cdp enable
!
ip classless
!
ip http server
!
!
control-plane
!
!
call application voice mcid flash:app_mcid.2.0.0.40.tcl
call application voice mcid mcid-release-timer 10
!
voice-port 3/0:23
!
!
!
!
application mcid
incoming called-number 2000
direct-inward-dial
port 3/0:23
forward-digits all
!
!
!
line con 0
line aux 0
line vty 0 4
login
!
end

172
Where to Go Next
Where to Go Next
• “Malicious Call Identification” chapter in the Cisco Unified CallManager Features and Services
Guide—Describes how to configure MCID in Cisco Unified CallManager 4.0.

173

174
Configuring RSVP Agent
The RSVP Agent feature implements a Resource Reservation Protocol (RSVP) agent on Cisco IOS voice
gateways that support Cisco Unified CallManager 5.0.1. The RSVP agent enables Cisco Unified
CallManager to provide resource reservation for voice and video media to ensure QoS and call admission
control (CAC). Cisco Unified CallManager controls the RSVP agent through Skinny Client Control
Protocol (SCCP). This signaling is independent of the signaling protocol used for the call so SCCP, SIP,
H.323, and MGCP calls can all use the RSVP agent.
Benefits of this feature include the following:
• Improves flexibility and scalability of bandwidth management in a meshed network by
decentralizing call admission control
• Provides method of managing unpredictable bandwidth requirements of video media
• Enables RSVP across WAN for Cisco IP phones and other devices that do not support RSVP
Feature History for RSVP Agent

12.4(6)T This feature was introduced.
Contents
• Prerequisites for RSVP Agent, page 176
• Restrictions for RSVP Agent, page 176
• Information About RSVP Agent, page 176
• How to Enable the RSVP Agent on the Voice Gateway, page 178
• Configuration Examples for RSVP Agent, page 184

175
Prerequisites for RSVP Agent
Prerequisites for RSVP Agent

Cisco IOS Voice Gateway
• Cisco IOS Release 12.4(4)T or a later release.
• Transcoder and MTP services must be configured on the voice gateway. See “Configuring Enhanced
Conferencing and Transcoding for Voice Gateway Routers” on page 65.
• SCCP must be enabled on the local interface that the voice gateway uses to register with
Cisco Unified CallManager. See the “Enabling SCCP on the Cisco Unified CallManager Interface”
section on page 79.
• The ip rsvp bandwidth command must be enabled on all interfaces.
• The ip rsvp policy preempt command must be enabled.
• The sccp ccm command must use the keyword version 5.0.1.

• Cisco Unified CallManager 5.0.1 or a later release.
• Transcoder and MTP services must be configured in Cisco Unified CallManager. See the following
chapters in the Cisco Unified CallManager Administration Guide:
– “Media Termination Point Configuration”
• RSVP policy level must be configured in Cisco Unified CallManager. See the “Service Parameters
Configuration” chapter in the Cisco Unified CallManager Administration Guide.
Restrictions for RSVP Agent

• RSVP agent is not supported by conference devices.
• RSVP agent is not supported by a hardware MTP or transcoder device using the NM-HDV.
• RSVP agent is supported by a software MTP using the NM-HDV only if the dsp services dspfarm
command is not enabled for the voice card.
• Lip-sync for video calls is not supported.
Information About RSVP Agent

To configure the RSVP agent on a Cisco IOS voice gateway, you should understand the following
concept:
• RSVP Agent, page 177

176
Information About RSVP Agent
RSVP Agent
Resource Reservation Protocol (RSVP) is the IP service that allows applications to request end-to-end
QoS guarantees from the network. Cisco VoIP applications use RSVP for call admission control, limiting
the accepted voice load on the IP network to guarantee the QoS levels of calls. In networks that include
both voice and video media, bandwidth requirements can vary considerably over any given time.
Cisco Unified CallManager ensures resource reservation for voice and video media by using RSVP.
The RSVP agent is a transcoding or MTP device on the Cisco IOS gateway that registers with
Cisco Unified CallManager as RSVP-capable. The RSVP agent is controlled by Cisco Unified
CallManager which communicates with the RSVP agent using SCCP.
Cisco Unified CallManager consults its policy configuration to determine if RSVP is required for a voice
or video call. If the configured QoS level for a call is optional or mandatory, and the RSVP agent is
enabled on the voice gateway, Cisco Unified CallManager inserts a pair of RSVP agents into the media
path to provide RSVP support. The RSVP agent on the Cisco IOS gateway creates the RSVP reservation
for the two endpoints and bridges the media connection so that resources are reserved for the media path,
providing QoS for the call.
Figure 13 shows where the RSVP agent fits in a Cisco Unified CallManager meshed network.
Figure 13 RSVP Agent in Cisco Unified CallManager Meshed Network
IP IP Cisco Unified CallManager

M
RSVP agent
V
V RSVP agent RSVP agent V

127438
IP IP IP
IP phones PC video
To support video calls, MTP and transcoding resources can process multiple streams in a single session,
including audio, video and data, one-way or two-way, using a pass-through mode. In pass-through mode,
a SCCP device processes streams using a pure software MTP, regardless of the type of stream, so it can
be used for any stream type. Video and data streams are processed using pass-through mode. Audio
streams can be processed with or without pass-through mode.

177
How to Enable the RSVP Agent on the Voice Gateway

• Enabling RSVP in a DSP Farm Profile, page 178 (required)
• Verifying RSVP Agent Configuration, page 180 (optional)
• Troubleshooting the RSVP Agent, page 181 (optional)
Note This document does not contain details about configuring Cisco Unified CallManager. See the
documentation and online help for Cisco Unified CallManager for configuration instructions.
Enabling RSVP in a DSP Farm Profile

Perform this procedure to enable the RSVP agent on an MTP or transcoder device.
SUMMARY STEPS
1. enable
3. dspfarm profile profile-identifier {mtp | transcode}
4. codec pass-through
5. maximum sessions number
or
maximum sessions {hardware | software} number
6. associate application sccp
7. rsvp
8. no shutdown
9. end
DETAILED STEPS

Example:
Router> enable
Example:

178

Step 3 dspfarm profile profile-identifier {mtp | Enters DSP farm profile configuration mode to define a
transcode} profile for DSP farm services.
Note The profile-identifier and service type uniquely
Example: identifies a profile. If the service type and
Router(config)# dspfarm profile 20 transcode profile-identifier pair is not unique, you are
prompted to choose a different profile-identifier.
Step 4 codec pass-through Enables codec pass-through mode for the DSP farm profile.
• Codec pass-through must be enabled for the RSVP
Example: agent to support Cisco Unified CallManager.
Router(config-dspfarm-profile)# codec
pass-through
• Transcoder profiles support multiple codecs. MTP
profiles support only one codec in addition to
pass-through mode. You must define a separate MTP
profile for each additional codec.
Step 5 maximum sessions number Specifies the maximum number of sessions that are
or supported by the profile.
maximum sessions {hardware | software} number • number—Range is determined by the available
registered DSP resources. Default is 0.
Example: Note The hardware and software keywords apply only
Router(config-dspfarm-profile)# maximum to MTP profiles.
sessions 4
Step 6 associate application sccp Associates the SCCP protocol to the DSP farm profile.
Example:
Router(config-dspfarm-profile)# associate
application sccp
Step 7 rsvp Enables RSVP support in the DSP farm profile.
Example:
Router(config-dspfarm-profile)# rsvp
Step 8 no shutdown Enables the profile, allocates DSP farm resources, and
associates the application.
Example:
Router(config-dspfarm-profile)# no shutdown
Example:
Router(config-dspfarm-profile)# end
What to Do Next
Assign the DSP-farm profile to the appropriate Cisco Unified CallManager group. See the “Associating
a DSP Farm Profile to a Cisco Unified CallManager Group” section on page 83.

179
Verifying RSVP Agent Configuration

Perform this procedure to verify the RSVP Agent configuration on the voice gateway.
SUMMARY STEPS
2. show dspfarm profile profile-number
3. show sccp ccm group group-number
DETAILED STEPS

Use the show running-config command to verify that the RSVP agent is enabled on the SCCP device
and that the device is assigned to a Cisco Unified CallManager group:
!
sccp ccm group 1
associate profile 10 register mtp_A1
associate profile 120 register xcoder_A2
!
codec g711ulaw
codec gsmfr
codec g711alaw
codec g729r8
codec g729ar8
codec g729br8
codec g729abr8
codec pass-through
rsvp
maximum sessions 5
!
Step 2 show dspfarm profile profile-number
Use the show dspfarm profile command to verify the configuration and status of the resource:
Profile ID = 20, Service = TRANSCODING, Resource ID = 1

Profile Description :
Codec Configuration
Codec : gsmfr, Maximum Packetization Period : 20
Codec : g729abr8, Maximum Packetization Period : 60

180
Codec : g711alaw, Maximum Packetization Period : 30

Codec : g711ulaw, Maximum Packetization Period : 30
Codec : g729r8, Maximum Packetization Period : 60
Codec : g729ar8, Maximum Packetization Period : 60
Codec : g729br8, Maximum Packetization Period : 60
Codec : pass-through, Maximum Packetization Period : 0
RSVP : ENABLED
Step 3 show sccp ccm group group-number

Use the show sccp ccm group command to verify the DSP farm profiles that are assigned to the
Cisco Unified CallManager group and the registration names of the SCCP devices.
Router# show sccp ccm group 1
CCM Group Identifier: 1

Description: None
Binded Interface: NONE, IP Address: NONE
Associated Profile: 10, Registration Name: mtp_A1
Associated Profile: 20, Registration Name: xcoder_A1
Associated Profile: 110, Registration Name: mtp_A2
Associated Profile: 120, Registration Name: xcoder_A2
Registration Retries: 3, Registration Timeout: 10 sec
Keepalive Retries: 3, Keepalive Timeout: 30 sec
CCM Connect Retries: 3, CCM Connect Interval: 10 sec
Switchover Method: GRACEFUL, Switchback Method: GRACEFUL_GUARD
Switchback Interval: 10 sec, Switchback Timeout: 7200 sec
Signaling DSCP value: default, Audio DSCP value: default
Troubleshooting the RSVP Agent

You can troubleshoot the performance of the RSVP agent by performing any of the following steps.
SUMMARY STEPS
1. show sccp
2. show sccp connections
3. show sccp connections details
4. show sccp connections rsvp
5. show ip rsvp installed
6. show sccp statistics
7. debug sccp all
8. debug call rsvp-sync [events | func-trace]
9. debug voip ccapi inout

181
DETAILED STEPS
Step 1 show sccp

Before the start of a call, use the show sccp command to verify that the MTP or transcoder device is
successfully registered with Cisco Unified CallManager:
Router# show sccp
SCCP Admin State: UP

Gateway IP Address: 192.168.20.1, Port Number: 0
IP Precedence: 5
User Masked Codec list: None
Priority: N/A, Version: 5.0.1, Identifier: 3
…..
Software MTP Oper State: ACTIVE - Cause Code: NONE

Supported Codec: pass-thru, Maximum Packetization Period: N/A
RSVP : ENABLED
Step 2 show sccp connections

During the call, use the show sccp connections command to display information about the active SCCP
connections established for the call, the DSP farm service type (MTP or transcoding), codec (for
example, pass-through or g711ulaw), and remote end information:
Router# show sccp connections
sess_id conn_id stype mode codec ripaddr rport sport
17537646 19438263 mtp sendrecv pass_th 192.168.20.5 35548 16576

17537646 19438260 mtp sendrecv pass_th 192.168.22.1 16832 19164
Step 3 show sccp connections details

Use the show sccp connections details command to display details about active SCCP connections,
including the internal call leg ID:
Router# show sccp connections details
bridge-info(bid, cid) - Normal bridge information(Bridge id, Calleg id)

mmbridge-info(bid, cid) - Mixed mode bridge information(Bridge id, Calleg id)
sess_id conn_id call-id codec pkt-period type bridge-info(bid, cid)

mmbridge-info(bid, cid)
17537646 - 326 N/A N/A swmtpmsp All RTPSPI Callegs N/A
17537646 19438263 324 pass_th 20 rtpspi (221,326) N/A
17537646 - 326 N/A N/A swmtpmsp All RTPSPI Callegs N/A

182
17537646 19438260 325 pass_th 20 rtpspi (222,326) N/A
Total number of active session(s) 1, connection(s) 2, and callegs 4
Step 4 show sccp connections rsvp

Use the show sccp connections rsvp command to display information about the active RSVP
reservations for the call:
Router# show sccp connections rsvp
sess_id conn_id rsvp_id dir local ip :port remote ip :port
17537646 19438260 -244 SEND 192.168.20.1 :19164 192.168.22.1 :16832

17537646 19438260 -245 RECV 192.168.20.1 :19164 192.168.22.1 :16832
Total active sessions 1, connections 2, rsvp sessions 2
Step 5 show ip rsvp installed

Use the show ip rsvp installed command to see that the RSVP reservation is successfully made and to
display the reserved bandwidth for the call:
Router# show ip rsvp installed
RSVP: Loopback0 has no installed reservations

RSVP: FastEthernet0/0 has no installed reservations
RSVP: Serial0/0
BPS To From Protoc DPort Sport Weight Conversation
80K 192.168.22.1 192.168.20.1 UDP 16832 19164 25 265
RSVP: FastEthernet0/1 has no installed reservations
RSVP: Serial0/1 has no installed reservations
Step 6 show sccp statistics

Use the show sccp statistics command to display the SCCP messages exchanged between the RSVP
agent and Cisco Unified CallManager:
Router# show sccp statistics
SCCP Application Service(s) Statistics:
Profile Identifier: 10, Service Type: Software MTP

TCP packets rx 9, tx 6
Unsupported pkts rx 0, Unrecognized pkts rx 0
Register tx 0, successful 0, rejected 0, failed 0
KeepAlive tx 1, successful 1, failed 0
OpenReceiveChannel rx 2, successful 2, failed 0
CloseReceiveChannel rx 0, successful 0, failed 0
StartMediaTransmission rx 2, successful 2, failed 0
StopMediaTransmission rx 0, successful 0, failed 0
PortReq rx 1
PortRes tx 1, successful 1, failed 0
PortClose rx 0
QosListen rx 1
QosPath rx 1
QosTeardown rx 0, send 0, recv 0, sendrecv 0
QosResvNotify tx 2, send 2, recv 0, sendrecv 0
QosErrorNotify tx 0, send 0, recv 0, sendrecv 0
err0 0, err1 0, err2 0, err3 0, err4 0, err5 0,
err6 0, err7 0, err8 0, err9 0, err10 0, err11 0,
QosModify rx 1, send 0, recv 1, sendrecv 0
UpdateDscp rx 0

183
Configuration Examples for RSVP Agent
Reset rx 0, successful 0, failed 0

MediaStreamingFailure rx 0
Switchover 0, Switchback 0
Step 7 debug sccp all

Use the debug sccp all command to display the sequence of the SCCP messages. The message sequence
may be different if the RSVP policy defined in Cisco Unified CallManager is not set to mandatory.
Router# show sccp statistics
Router# show log | incl (rcvd | txed)
Feb 4 20:28:41.791: sccp_parse_control_msg: rcvd KeepAliveAckMessage msg

Feb 4 20:28:55.647: sccp_parse_control_msg: rcvd PortReq msg:
Feb 4 20:28:55.647: sccp_send_port_res: PortRes msg txed in hex(including header) - len
36
Feb 4 20:28:55.651: sccp_parse_control_msg: rcvd QosPath msg:
Feb 4 20:28:55.651: sccp_parse_control_msg: rcvd QosListen msg:
Feb 4 20:28:55.675: sccp_send_qos_resv_notify: QosResvNotify txed in hex(including
header) - len 36
Feb 4 20:28:57.706: OpenReceviceChannel msg rcvd in hex -
Feb 4 20:28:57.710: sccp_open_receive_chnl_ack: OpenRecvChnlAck msg txed in hex(including
header) - len 32
Feb 4 20:28:57.714: OpenReceviceChannel msg rcvd in hex -
Feb 4 20:28:57.718: StartMediaTrans msg rcvd in hex -
Feb 4 20:28:57.726: sccp_open_receive_chnl_ack: OpenRecvChnlAck msg txed in hex(including
header) - len 32
Feb 4 20:28:57.866: StartMediaTrans msg rcvd in hex -
Feb 4 20:28:57.870: sccp_parse_control_msg: rcvd QosModify msg:
Feb 4 20:28:57.878: sccp_send_qos_resv_notify: QosResvNotify txed in hex(including
header) - len 36
Step 8 debug call rsvp-sync {events | func-trace}

Use the debug call rsvp-sync event and debug call rsvp-sync func-trace with the debug sccp all
command to show how SCCP messages and RSVP events trigger each other.
Step 9 debug voip ccapi inout
Use the debug voip ccapi inout command to trace the execution path through the call control application
programming interface (API).

This section contains the following configuration example:
• RSVP Agent, page 177
RSVP Agent: Example

version 12.4
!
hostname Router

184
!
boot-start-marker
boot-end-marker
!
no logging console
enable password lab
!
no aaa new-model
ip subnet-zero
ip cef
!
!
no ip domain lookup
voice-card 2
dspfarm
!
!
!
interface Loopback0
ip address 192.168.26.1 255.255.255.255
max-reserved-bandwidth 100
ip rsvp bandwidth
!
ip address 192.168.20.1 255.255.255.0
duplex auto
speed auto
fair-queue 64 256 1000
ip rsvp bandwidth
!
interface Serial0/0
ip address 192.168.25.2 255.255.255.252
ip rsvp bandwidth
!
ip address 192.168.24.1 255.255.255.0
shutdown
duplex auto
speed auto
ip rsvp bandwidth
!
interface Serial0/1
ip address 192.168.25.69 255.255.255.252
shutdown
ip rsvp bandwidth
!
router ospf 10
log-adjacency-changes
network 192.168.0.0 0.0.255.255 area 0
!
ip classless

185
ip http server
ip rsvp policy preempt
!
!
!
control-plane
!
!
!
voice-port 2/0/0
!
voice-port 2/0/1
!
!
sccp
!
sccp ccm group 1
!
codec g711ulaw
codec gsmfr
codec pass-through
codec g711alaw
codec g729r8
codec g729ar8
codec g729br8
codec g729abr8
rsvp
maximum sessions 5
!
codec g729abr8
codec gsmfr
codec g711alaw
codec g711ulaw
codec g729r8
codec g729ar8
codec g729br8
codec pass-through
rsvp
maximum sessions 5
!
dspfarm profile 30 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
!

186
codec g711ulaw
codec pass-through
rsvp
!
codec pass-through
codec g711ulaw
rsvp
!
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
exec-timeout 0 0
no login
!
ntp clock-period 17175018
ntp server 192.168.20.12
end
• Cisco Unified CallManager Administration Guide, Release 5.0(1)
• Cisco Unified CallManager System Guide, Release 5.0(1)
• Cisco Unified CallManager Features and Services Guide, Release 5.0(1)

187

188
INDEX
clock source command 115

A
codec (DSP profile) command 82, 179
application mcid command 168 command-type a-law command 134
application mgcpapp command 40 conferencing and transcoding, description 18
associate application sccp command 82, 179 Conferencing and Transcoding for Voice Gateway Routers
associate ccm command 84 feature 65
associate profile command 84 conferencing overview 69

configuration of
conferencing and transcoding
B troubleshooting service 91
dial peers and voice ports 39
bind interface command 84
MGCP fallback and switchover 30
MGCP gateway 27
C MGCP PRI backhaul for Cisco CallManager 112
music-on-hold 47
call application alternate command 34
single-point download 44
call application voice mcid command 168
connect interval command 86
call application voice mcid mcid-release-timer
command 168 connect retries command 86
ccm-manager config command 46, 152 controller command 114

ccm-manager config server command 46 Customizable Tone Download to Cisco IOS MGCP
Gateways from Cisco CallManager feature 143
ccm-manager download-tones command 152
ccm-manager fallback-mgcp command 34
ccm-manager mgcp command 28 D
ccm-manager music-on-hold bind command 48
debug ccm-manager backhaul command 120
ccm-manager music-on-hold command 48
debug ccm-manager backhaul packets command 134
ccm-manager redundant-host command 34
debug ccm-manager config-download all command 154
ccm-manager switchback command 34
debug ccm-manager config-download tone command 154
ccm-manager switchover-to-backup command 34
debug dspfarm command 91
Cisco AVVID, description 14
debug isdn q931 command 121, 134
Cisco IOS interoperability with Cisco CallManager
debug media resource provisioning command 91
information about 25
debug mgcp packets command 134
prerequisites 24
debug sccp command 91
restrictions 25
description (Cisco CallManager group) command 84

189
Index
description (DSP profile) command 82 isdn bind-L3 ccm-manager service mgcp command 132
dial-peer voice command 40, 168 isdn incoming-voice command 165
direct-inward-dial command 40, 167, 168 isdn supp-service mcid command 165
dspfarm command 93, 95 isdn switch-type basic-net3 command 132
dspfarm confbridge maximum sessions command 92, 95 isdn switch type command 165
dspfarm connection interval command 94 isdn switch-type command 115
dspfarm profile command 82, 179 isdn t-activate command 165
dspfarm rtp timeout command 94
DSP farms
K
allocation of resources 73
description 69 keepalive retries command 86
dspfarm transcoder maximum sessions command 93, 95 keepalive timeout command 86
dsp services dspfarm command 81, 92
L
E
linecode command 115
Enhanced Conferencing and Transcoding for Voice
Gateway Routers feature 65
M
F maximum sessions command 82, 179

mgcp call-agent command 28
framing command 114
mgcp command 28
MGCP-Controlled Backhaul of BRI Signaling in
Conjunction with Cisco CallManager feature 127
G
mgcp dtmf-relay voip codec command 28
gateway command 83 MGCP gateway fallback, description 15, 31
MGCP gateways, description 14
MGCP Gateway Support for Cisco CallManager
H feature 23
MGCP Gateway Support for Cisco CallManager Network
hostname command 28
Specific Facilities feature 111
MGCP Generic Configuration Support for Cisco
CallManager feature 23
I
MGCP PRI backhaul, description 16, 112
incoming called-number command 167, 168 MGCP PRI Backhaul and T1 CAS Support for Cisco
CallManager feature 111
interface bri command 131
mgcp validate domain-name command 28
interface ethernet command 27
MLPP 49
interface serial command 115, 165
MLPP for Cisco IOS Voice Gateways feature 49
ip address command 27
Multicast Music-on-Hold feature 23
isdn bind-L3 ccm-manager command 115

190
Index
music-on-hold, description 16 show ccm-manager music-on-hold command 49

music-on-hold configuration example 58 show dial-peer voice command 42
show dspfarm all command 88
show dspfarm profile command 88
O
show interfaces ethernet command 29
Out-of-Band to In-Band DTMF Relay for Cisco IOS Voice show isdn status command 116, 132
Gateways feature 95 show media resource status command 89
show mgcp command 29
show mgcp endpoint command 134
P
show mgcp endpoints command 120
port command 40, 167, 169 show sccp ccm group command 87
pri-group timeslots command 115 show sccp command 89
show sccp connections command 89
show voice port command 42, 147, 153
Q
single-point configuration download, description 16
QSIG 122 supplementary services, description 16
QSIG Supplementary Features for Cisco IOS Voice switchback, description 17, 31
Gateways feature 122
switchback interval command 87
switchback method command 86
R switchover method command 86
registration retries command 86

registration timeout command 86 T
RSVP Agent feature 175
timer receive-rtp command 83
rsvp command 179
tones and cadences, description 17
transcoding overview 70
sccp ccm command 79 V

sccp ccm group command 84, 85
voice-card command 81, 92
sccp command 80
sccp ip precedence command 80
sccp local command 80
sccp switchback timeout guard command 94
show ccm-manager backhaul command 117, 133
show ccm-manager command 38, 116, 119, 133
show ccm-manager config-download command 46
show ccm-manager download-tones command 153
show ccm-manager fallback-mgcp command 39

191

Cisco CallManager and Cisco IOS Interoperability Guide

Uploaded by

Copyright:

Available Formats

Cisco CallManager and Cisco IOS Interoperability Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cisco CallManager and Cisco IOS Interoperability Guide

Uploaded by

Copyright:

Available Formats

What are MGCP gateways?

What are MGCP gateways?

What is MGCP PRI backhaul?

What is MGCP PRI backhaul?

Cisco Unified CallManager and Cisco IOS

Interoperability Configuration Guide

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

Cisco Unified CallManager and Cisco IOS Interoperability Features Roadmap 9

Platforms and Cisco IOS Software Images 9

Cisco Unified CallManager and Cisco IOS Interoperability Feature List 9

Overview of Cisco Unified CallManager and Cisco IOS Interoperability 13

Information About Cisco Unified CallManager and Cisco IOS Interoperability 13

Configuring MGCP Gateway Support for Cisco Unified CallManager 23

Information about MGCP Gateway Support for Cisco Unified CallManager 25

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

MGCP Gateways and Cisco Unified CallManager 25

How to Configure MGCP Gateway Support for Cisco Unified CallManager 26

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

Configuring Enhanced Conferencing and Transcoding for Voice Gateway Routers 65

Prerequisites for Conferencing and Transcoding for Voice Gateway Routers 66

Restrictions for Conferencing and Transcoding for Voice Gateway Routers 68

Information About Conferencing and Transcoding for Voice Gateway Routers 68

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

Configuration Examples for Conferencing and Transcoding 98

Additional References 110

Prerequisites for MGCP PRI Backhaul and T1 CAS Support 112

Restrictions for MGCP PRI Backhaul and T1 CAS Support 112

Information About MGCP PRI Backhaul and T1 CAS Support 112

Additional References 125

Configuring MGCP-Controlled Backhaul of BRI Signaling in Conjunction with Cisco Unified

Prerequisites for MGCP-Controlled Backhaul of BRI Signaling 128

Restrictions for MGCP-Controlled Backhaul of BRI Signaling 129

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

Information About MGCP-Controlled Backhaul of BRI Signaling 129

Additional References 142

Configuring Tone Download to MGCP Gateways 143

Information About Tone Download to MGCP Gateways 144

Where to Go Next 159

Additional References 159

Configuring MCID for Cisco IOS Voice Gateways 161

Prerequisites for MCID for Cisco IOS Voice Gateways 162

Restrictions for MCID for Cisco IOS Voice Gateways 162

Information About MCID for Cisco IOS Voice Gateways 163

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

How to Configure MCID for Cisco IOS Voice Gateways 164

Where to Go Next 173

Additional References 173

Configuring RSVP Agent 175

Prerequisites for RSVP Agent 176

Restrictions for RSVP Agent 176

Information About RSVP Agent 176

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

Platforms and Cisco IOS Software Images

Cisco Unified CallManager and Cisco IOS Interoperability

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

Table 1 Cisco Unified CallManager and Cisco IOS Interoperability Features

Release Features Introduced in That Release1 Feature Description Feature Documentation

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide

Release Features Introduced in That Release1 Feature Description Feature Documentation

Cisco Unified CallManager and Cisco IOS Interoperability Configuration Guide