Configuring Conferencing and Transcoding for Voice Gateway Routers
Last Updated: December 6, 2012
This chapter describes the steps for enabling conferencing and transcoding support on Cisco IOS voice gateways in a Cisco Unified Communications Manager 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 G.722-64 and iLBC Codec Support on Cisco Unified Communications Manager Express
Release
Modification
12.4(15)XZ
This feature was introduced.
15.0(1)M
This feature was integrated into Cisco IOS Release 15.0(1)M.
Feature History for G.722-64 and iLBC Codec Support on Cisco UBEs, DSP Farms, and Voice Gateways
Release
Modification
12.4(15)XY
This feature was introduced.
15.0(1)M
This feature was integrated into Cisco IOS Release 15.0(1)M.
Feature History for Universal Voice Transcoding Support for Cisco Unified Border Elements
Release
Modification
12.4(11)XY
This feature was introduced.
15.0(1)M
This feature was integrated into Cisco IOS Release 15.0(1)M.
Feature History for Out-of-Band to In-Band DTMF Relay for Voice Gateway Routers
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.
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
Release
Modification
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
Release
Modification
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.
Finding Support Information for 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.
For more information about this and related Cisco IOS voice features, see the following:
"Overview of Cisco Unified Communications Manager and Cisco IOS Interoperability" on page 13
.
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see
Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
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:
Cisco Unified Communications Manager and Cisco IOS Release
Minimum software
requirements for type of network or voice module:
Module
Cisco Unified Communications Manager version
Cisco IOS Release
NM-HDV2,NM-HD-1V/2V/2VE
Cisco Unified Communications Manager 3.3(4) (formerly known
as Cisco CallManager 3.3(4)) or later for conferencing and transcoding, Cisco
Unified Communications Manager 4.0(1) (formerly known as Cisco CallManager
4.0(1)) or later for MTP
Cisco IOS Release 12.3(8)T or later
PVDM2(Cisco 2800 series)
Cisco Unified Communications Manager 3.3(5) (formerly known
as Cisco CallManager 3.3(5)) or later for conferencing and transcoding, Cisco
Unified Communications Manager 4.0(2a) (formerly known as Cisco CallManager
4.0(2a)) or later for MTP
Cisco IOS Release 12.3(8)T4 or later
PVDM2(Cisco 3800 series)
Cisco Unified Communications Manager 3.3(5) (formerly known
as Cisco CallManager 3.3(5)) or later for conferencing and transcoding, Cisco
Unified Communications Manager 4.0(2a) (formerly known as Cisco CallManager
4.0(2a)) or later for MTP
Cisco IOS Release 12.3(11)T or later
NM-HDV
Cisco Unified Communications Manager 3.2(2c) (formerly
known as 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 Communications
Manager. See the following chapters in the Cisco Unified Communications Manager
Administration Guide :
Restrictions for Conferencing and Transcoding for Voice Gateway Routers
DSP farm services communicate with Cisco Unified Communications Manager 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 Communications Manager Express.
DSP farm services cannot be enabled for a slot on the Cisco 1700 series so the dspservicesdspfarm 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 nomaximumsessionshardware command.
Software MTPs are supported on the NM-HDV only if the dspservicesdspfarmcommand 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:
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 Communications Manager 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 Communications Manager 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 Communications Manager.
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.
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 Communications Manager group. The profile ID and service type uniquely identify a profile, allowing the profile to uniquely map to a Cisco Unified Communications Manager group that contains a single pool of Cisco Unified Communications Manager 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 Communications Manager, the Conferencing and Transcoding for Voice Gateway Routers feature provides the conference-bridging service. Cisco Unified Communications Manager 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.
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 the figure below).
Figure 1
Conferencing Service
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 Communications Manager which 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 the figure below).
Figure 2
Transcoding Service
Media Termination Point
A Media Termination Point (MTP) bridges the media streams between two connections allowing Cisco Unified Communications Manager to relay calls that are routed through SIP or H.323 endpoints.
The following MTP resources are supported for Cisco Unified Communications Manager 4.0 (formerly known as Cisco 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 Communications Manager also uses the term software MTP when referring to a hardware MTP.
Transcoder as MTP--Implementation that uses a DSP resource for endpoints using the same G.711 codec (on both legs) or a mixture of different supported codecs. This functionality is used by Cisco Unified Communications Manager to view the transcoders as usable MTP resources (if they are available in the pool) and enables Cisco Unified Communications Manager to use MTP resources more effectively when a call is deemed to use a transcoder and an MTP resource at the same time.
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 Communications Manager 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
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 Communications Manager meet-me and ad-hoc conferences with up to six participants each
Up to 15 six-party conferences on a single NM-HDV
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
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 Communications Manager meet-me and ad-hoc conferences with up to six participants each
Up to 5 six-party conferences
One conference on a single DSP
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
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
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.
The table below lists the total DSPs that are supported on a fully-loaded voice network module.
Table 1
Total DSPs Supported Per Voice Network Module
Network Module
Maximum DSPs per PVDM2/PVDM
Maximum PVDM2s/PVDMs per Network Module
Maximum DSPs
NM-HDV2
4
4
16
NM-HD-1V/2V
--
--
1
NM-HD-2VE
--
--
3
NM-HDV
3
5
15
The table below lists the total number of network modules that are supported per router.
Table 2
Maximum Voice Network Modules Supported Per Router
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 Communications Manager.
The tables below 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 3
DSP Theoretical Session Capacities
Application
NM-HD-1V/2V (1 DSP)
NM-HD-2VE (3 DSPs)
NM-HDV2 (16 DSPs)
2801/2811 (2 PVDM2-64)
2821/2851 (3 PVDM2-64)
3825, 3845 (4 PVDM2-64)
Conferencing
G.711
8 sessions (64 conferees)
24 sessions (192 conferees)
50 sessions (400 conferees)
50 sessions (400 conferees)
50 sessions (400 conferees)
50 sessions (400 conferees)
G.722-64
2 sessions (16 conferees)
6 sessions (48 conferees)
32 sessions (256 conferees)
16 sessions (128 conferees)
24 sessions (192 conferees)
32 sessions (256 conferees)
G.729
2 sessions (16 conferees)
6 sessions (48 conferees)
32 sessions (256 conferees)
16 sessions (128 conferees)
24 sessions (192 conferees)
32 sessions (256 conferees)
GSM FR
--
2 sessions (16 conferees)
14 sessions (112 conferees)
7 sessions (56 conferees)
10 sessions (80 conferees)
14 sessions (112 conferees)
GSM EFR
--
1 session (8 conferees)
10 sessions (80 conferees)
5 sessions (40 conferees)
8 sessions (64 conferees)
10 sessions (80 conferees)
iLBC
1 session (8 conferees)
3 sessions (24 conferees)
16 sessions (128 conferees)
8 sessions (64 conferees)
12 sessions (96 conferees)
16 sessions (128 conferees)
Transcoding
G.711 a-law/u-law <-> any (with high complexity codec in
dspfarmprofile)
6 sessions
18 sessions
96 sessions
48 sessions
72 sessions
96 sessions
G.711 a-law/u-law <-> any (without high complexity codec in
dspfarmprofile)
8 sessions
24 sessions
128 sessions
64 sessions
96 sessions
128 sessions
G.711 a-law/u-law <-> G.729a/G.729ab/ GSM FR
8 sessions
24 sessions
128 sessions
64 sessions
96 sessions
128 sessions
G.711 a-law/u-law <-> G.729/G.729b/ GSM EFR
6 sessions
18 sessions
96 sessions
48 sessions
72 sessions
96 sessions
G.722-64<-> any
4 sessions
12 sessions
64 sessions
32 sessions
48 sessopms
64 sessions
G.722-64 <-> G.711
8 sessions
24 sessions
128 sessions
64 sessions
96 sessions
128 sessions
iLBC <-> any
3 sessions
9 sessions
48 sessions
24 sessions
36 sessions
48 sessions
iLBC <-> G.711
6 sessions
18 sessions
96 sessions
48 sessions
72 sessions
96 sessions
Universal Transcoding (with high complexity codec in
dspfarmprofile)
3 sessions
9 sessions
48 sessions
24 sessions
36 sessions
48 sessions
Universal Transcoding (without high complexity codec in
dspfarmprofile)
4 sessions
12 sessions
64 sessions
32 sessions
48 sessions
64 sessions
Voice Termination
G.711 a-law/u-law
16 sessions
48 sessions
256 sessions
128 sessions
192 sessions
256 sessions
G.726, G.729a, G.729ab, GSM FR
8 sessions
24 sessions
128 sessions
64 sessions
96 sessions
128 sessions
G.729, G.729b, G.723.1, G.728, GSM EFR
6 sessions
18 sessions
96 sessions
48 sessions
72 sessions
96 sessions
Table 4
Theoretical System Capacities for One DSP
Application
G.711 a-law/u-law
G.722-64
G729 a/ab
G.729, G.729b
GSM FR
GSM EFR
iLBC
Conferencing
8 sessions (8 x 8 = 64 conferees)
2 sessions (8 x 2 = 16 conferees)
2 sessions (8 x 2 = 16 conferees)
2 sessions (8 x 2 = 16 conferees)
--
--
1 session (1 x 8 = 8 conferees)
Conferencing on PVDM2-8
4 sessions (4 x 8 = 32 conferees)
1 session (1 x 8 = 8 conferees)
1 session (1 x 8 = 8 conferees)
1 session (1 x 8 = 8 conferees)
--
--
1 session (1 x 8 = 8 conferees)
Hardware MTP
16 sessions
--
--
--
--
--
--
Transcoding
8 sessions
8 sessions
8 sessions
6 sessions
8 sessions
6 sessions
8 sessions
NM-HDV System Capacities
The table below lists the number of transcoding sessions and conference calls supported on the NM-HDV.
Table 5
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
A fully loaded NM-HDV (5 PVDMs holding 15 DSPs)
60 transcoding sessions
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 the table below 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 the table beneath the table below if you use 10-ms packetization with VAD disabled
Note
Numbers in the following table 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.
Table 6
PVDM Requirements Using 20-, 30-, 40-, 50-, or 60-ms Packetization or 10-ms Packetization with VAD Enabled
Transcoding Sessions
Conference Calls
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
--
--
--
--
--
--
--
--
--
--
--
--
--
--
--
Note
Numbers given in the following table 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.
Table 7
PVDM Requirements Using 10-ms Packetization and with VAD Disabled
Transcoding Sessions
Conference Calls
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
--
--
--
--
--
--
--
--
--
--
How to Configure Conferencing and Transcoding for Voice Gateway Routers
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 the number of transcoding sessions and conference calls that your router must support.
2. Determine the number of DSPs that are required to support the transcoding sessions and conference calls. If voice termination is also required, determine the additional DSPs required.
3. Determine the maximum number of network modules that your router can support.
4. Ensure that your requirements fall within router capabilities, taking into account whether your router supports multiple network modules. If necessary, reassess performance requirements.
5. Install PVDM2s and network modules, as needed.
DETAILED STEPS
Command or Action
Purpose
Step 1
Determine the number of transcoding sessions and conference calls that your router must support.
Establishes your performance requirements.
Step 2
Determine the number of DSPs that are required to support the transcoding sessions and conference calls. If voice termination is also required, determine the additional DSPs required.
For 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 capabilities, taking into account whether your router supports multiple network modules. If necessary, reassess performance requirements.
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
dspservicesdspfarmcommand for the voice card.
Before You Begin
Requires Cisco IOS Release 12.3(8)T or a later release. Universal
transcoding requires Cisco IOS Release 12.4(11)XY or a later release.
Enters DSP farm profile configuration mode to define a profile
for DSP farm services.
Note
The
profile-identifier and service type uniquely identifies a
profile. If the service type and
profile-identifier pair is not unique, you are prompted to
choose a different
profile-identifier .
(Optional) Includes a specific description about the Cisco DSP
farm profile.
Step 8
codeccodec-type
Example:
Router(config-dspfarm-profile)# codec ilbc
Specifies the codecs supported by a DSP farm profile.
Repeat this step for
each codec supported by the profile.
Note
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
nomaximumsessionshardware 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
maximumsessions {hardware |
software}
number
Example:
Router(config-dspfarm-profile)# maximum sessions 4
Specifies the maximum number of sessions that are supported by
the profile.
number --Range is determined by the available registered
DSP resources. Default is 0.
Note
The
hardware and
software keywords apply only to MTP
profiles.
Associates the SCCP protocol to the DSP farm profile.
Step 11
noshutdown
Example:
Router(config-dspfarm-profile)# no shutdown
Enables the profile, allocates DSP farm resources, and associates
the application.
Step 12
exit
Example:
Router(config-dspfarm-profile)# exit
Exits DSP farm profile configuration mode.
Step 13
gateway
Example:
Router(config)# gateway
Enters gateway configuration mode.
Step 14
timerreceive-rtpseconds
Example:
Router(config-gateway)# timer receive-rtp 600
Sets the Real-Time Transport Protocol (RTP) timeout interval to
clear hanging connections.
seconds --Range is 180 to 1800. Default is 1200.
Step 15
exit
Example:
Router(config-gateway)# exit
Exits to global configuration mode.
Associating a DSP Farm Profile to a Cisco Unified Communications Manager Group
Perform this procedure to define a Cisco Unified Communications Manager group and to associate a DSP farm profile with the Cisco Unified Communications Manager group.
Before You Begin
This procedure requires Cisco IOS Release 12.3(8)T or later release.
Associates a DSP farm profile to the Cisco Unified Communications Manager group.
device-nam
e--Must match the device name configured in Cisco Unified Communications Manager; otherwise profile is not registered to Cisco Unified Communications Manager.
Repeat this step for each DSP farm profile that you want to register with this Cisco Unified Communications Manager group.
Binds an interface to the Cisco Unified Communications Manager group.
Step 7
descriptiontext
Example:
Router(config-sccp-ccm)# description boston office
(Optional) Includes a specific description of the Cisco Unified Communications Manager group.
Step 8
end
Example:
Router(config)# end
Exits to privileged EXEC mode.
Modifying Default Settings for SCCP Connection to Cisco Unified Communications Manager
Perform this task to tune the performance of the SCCP connection between the DSP farm and Cisco Unified Communications Manager.
Note
The optimum settings for these commands depend on your platform and individual network characteristics. Modify the defaults to meet your performance requirements.
(Optional) Specifies the amount of time that a DSP farm profile waits before attempting to connect to another Cisco Unified Communications Manager when the current Cisco Unified Communications Manager fails to connect.
seconds
--Range is 1 to 3600. Default is 60.
Step 5
connectretriesnumber
Example:
Router(config-sccp-ccm)# connect retries 5
(Optional) Specifies the number of times that a DSP farm attempts to connect to a Cisco Unified Communications Manager when the current Cisco Unified Communications Manager connections fails.
number
--Range is 1 to 32. Default is 3.
Step 6
keepaliveretriesnumber
Example:
Router(config-sccp-ccm)# keepalive retries 7
(Optional) Sets the number of keepalive retries from SCCP to the Cisco Unified Communications Manager.
number
--Range is 1 to 32. Default is 3.
Step 7
keepalivetimeoutseconds
Example:
Router(config-sccp-ccm)# keepalive timeout 50
(Optional) Sets the number of seconds between keepalive messages from SCCP to the Cisco Unified Communications Manager.
seconds
--Range is 1 to 180. Default is 30.
Step 8
registrationretriesretry-attempts
Example:
Router(config-sccp-ccm)# registration retries 15
(Optional) Sets the number of registration retries that SCCP tries to register with the Cisco Unified Communications Manager.
retry-attempts
--Range is 1 to 32. Default is 3.
Step 9
registrationtimeoutseconds
Example:
Router(config-sccp-ccm)# registration timeout 8
(Optional) Sets the number of seconds between registration messages sent from SCCP to the Cisco Unified Communications Manager.
(Optional) Sets the switchback method to use when the primary or higher priority Cisco Unified Communications Manager becomes available again.
Default is guard, with a timeout value of 7200 seconds.
Step 12
switchbackintervalseconds
Example:
Router(conf-sccp-ccm)# switchback interval 120
(Optional) Sets the number of seconds that the DSP farm waits before polling the primary Cisco Unified Communications Manager when the current Cisco Unified Communications Manager fails to connect.
seconds
--Range is 1 to 3600. Default is 60.
Step 13
end
Example:
Router(config-sccp-ccm)# end
Exits to privileged EXEC mode.
Verifying DSP Farm Configuration
To verify conferencing, transcoding, and MTP services, perform the following steps.
SUMMARY STEPS
1.
Use the showrunning-config command to display the configuration of the MTP profile, for example:
2.showsccpccmgroup [group-number]
3.showdspfarmprofile [profilenumber]
4.showdspfarmall
5.showsccp
6.showsccpconnections
7.showmediaresourcestatus
DETAILED STEPS
Step 1
Use the showrunning-config command to display the configuration of the MTP profile, for example:
Example:
Router# show running-config
...
sccp local FastEthernet0/0
sccp ccm 10.40.10.10 identifier 10 version 4.0
sccp
!
sccp ccm group 48
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
showsccpccmgroup [group-number]
Use this command to verify the configuration of the Cisco Unified Communications Manager group, for example:
Use this command to verify the configured DSP farm profiles, for example:
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
Router# show dspfarm profile 6
Dspfarm Profile Configuration
Profile ID = 6, Service = TRANSCODING, Resource ID = 1
Profile Admin State : UP
Profile Operation State : ACTIVE
Application : SCCP Status : ASSOCIATED
Resource Provider : FLEX_DSPRM Status : UP
Number of Resource Configured : 4
Number of Resource Available : 4
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
showdspfarmall
Use this command to verify the status of the DSP farm, for example:
Example:
Router# show dspfarm all
DSPFARM Configuration Information:
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
showsccp
Use the showsccp command to verify that the DSP farm is registered, for example:
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
Call Manager: 10.10.100.50, Port Number: 2000
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
Active Call Manager: 10.10.100.51, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 20
Reported Max Streams: 176, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 20
Step 6
showsccpconnections
Use this command to verify the active SCCP connections, for example:
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
Total number of active session(s) 1, and connection(s) 1
Step 7
showmediaresourcestatus
Use this command to verify the current media resource status, for example:
Example:
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
Tips for Troubleshooting Conferencing and Transcoding on Voice Gateway Routers
This section describes techniques for troubleshooting DSP-farm services.
Basic Troubleshooting Procedures
Verify the Cisco Unified Communications Manager 4.0 (formerly known as Cisco CallManager 4.0) or later.
Verify that Cisco Unified Communications Manager is properly configured to provision conferencing, transcoding, and MTP resources.
Organize your Cisco Unified Communications Manager group IDs, device IDs, and DSP farm profile names. Use theshowdsp command to verify that the association between SCCP Cisco Unified Communications Manager and the DSP farm profiles match your organizational plan.
Verify that the VoIP dial peer application exists on the terminating gateway.
Collect relevant information from debug and show commands, and configuration files before contacting Cisco Technical Support for assistance.
You can clear any of the following by disabling the DSP farm or SCCP:
Active calls
DSPs
Active connection to a Cisco Unified Communications Manager
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 nomaximumsessionshardware 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.
Troubleshooting DSP-Farm Services
You can troubleshoot performance by performing any of the following steps.
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.
SUMMARY STEPS
1.enable
2.configureterminal
3.voice-cardslot
4.dspservicesdspfarm
5.exit
6.dspfarmconfbridgemaximumsessionsnumber
7.dspfarmtranscodermaximumsessionsnumber
8.dspfarm
9.exit
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.
Enter your password when prompted.
Step 2
configureterminal
Example:
Router# configure terminal
Enters global configuration mode.
Step 3
voice-cardslot
Example:
Router(config)# voice-card 1
Enters voice-card configuration mode for the network module on which you want to enable DSP-farm services.
Step 4
dspservicesdspfarm
Example:
Router(config-voicecard)# dsp services dspfarm
Enables DSP-farm services on the voice card.
Step 5
exit
Example:
Router(config-voicecard)# exit
Returns to global configuration mode.
Step 6
dspfarmconfbridgemaximumsessionsnumber
Example:
Router(config)# dspfarm confbridge maximum sessions 3
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.
Note
When you assign this value, take into account the number of DSPs allocated for transcoding services.
Step 7
dspfarmtranscodermaximumsessionsnumber
Example:
Router(config)# dspfarm transcoder maximum sessions 12
Specifies the maximum number of transcoding sessions to be supported by the DSP farm. A DSP can support up to 4 transcoding sessions.
Note
When you assign this value, take into account the number of DSPs allocated for conferencing services.
Step 8
dspfarm
Example:
Router(config)# dspfarm
Enables the DSP farm.
Step 9
exit
Example:
Router(config)# exit
Exits global configuration mode.
Tuning DSP-Farm Performance on the NM-HDV
Use the following optional commands to tune performance.
SUMMARY STEPS
1.enable
2.configureterminal
3.sccpswitchbacktimeoutguardseconds
4.dspfarmrtptimeoutseconds
5.dspfarmconnectionintervalseconds
6.exit
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.
Enter your password when prompted.
Step 2
configureterminal
Example:
Router# configure terminal
Enters global configuration mode.
Step 3
sccpswitchbacktimeoutguardseconds
Example:
Router(config)# sccp switchback timeout guard 180
(Optional) Sets the guard timer.
Step 4
dspfarmrtptimeoutseconds
Example:
Router(config)# dspfarm rtp timeout 60
(Optional) Configures the Real-Time Transport Protocol (RTP) timeout interval for when the error condition "RTP port unreachable" occurs.
Step 5
dspfarmconnectionintervalseconds
Example:
Router(config)# dspfarm connection interval 60
(Optional) Specifies how long to monitor RTP inactivity before deleting an RTP stream.
Step 6
exit
Example:
Router(config)# exit
Exits global configuration mode.
What to Do Next
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.
Before You Begin
Determine that there are enough DSPs available for conferencing and transcoding services by using the showvoicedsp command.
SUMMARY STEPS
1.enable
2.configureterminal
3.dspfarmconfbridgemaximumsessionsnumber
4.dspfarmtranscodermaximumsessionsnumber
5.dspfarm
6.exit
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.
Enter your password when prompted.
Step 2
configureterminal
Example:
Router# configure terminal
Enters global configuration mode.
Step 3
dspfarmconfbridgemaximumsessionsnumber
Example:
Router(config)# dspfarm confbridge maximum sessions 3
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.
Note
When you assign this value, take into account the number of DSPs allocated for transcoding services.
Step 4
dspfarmtranscodermaximumsessionsnumber
Example:
Router(config)# dspfarm transcoder maximum sessions 12
Specifies the maximum number of transcoding sessions to be supported by the DSP farm. A DSP can support up to 4 transcoding sessions.
Note
When you assign this value, take into account the number of DSPs allocated for conferencing services.
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.
Configure DTMF relay in the SIP dial peers using the dtmf-relayrtp-nte command.
Configure DTMF relay in Cisco Unified Communications Manager 4.0 (formerly known as Cisco 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:
connectinterval
connectretries
keepaliveretries
keepalivetimeout
sccpregistrationretries
sccpregistrationtimeout
switchbackinterval
Restrictions
Multifrequency is supported by MTPs but Cisco Unified Communications Manager 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 Communications Manager. 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.
DTMF detection and generation capabilities are added to the hardware and software MTP. The MTP generates out-of-band SCCP events to Cisco Unified Communications Manager 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 Communications Manager.
The figure below illustrates the media setup and DTMF tone flow between a SIP network and nonSIP network over a DSP farm MTP.
Figure 3
DTMF Tone Flow Between a SIP and NonSIP Network
This feature supports DTMF relay using the following MTP and transcoder resources for Cisco Unified Communications Manager 4.0 (formerly known as Cisco 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 Communications Manager refers to it also as a software MTP.
Transcoder--Hardware-only implementation using a DSP resource for endpoints using different codecs. Cisco Unified Communications Manager 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.
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 Communications Manager group 988.
Note
This configuration requires Cisco IOS Release 12.3(8)T or later.
Current configuration : 2661 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname sjl23
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
ip subnet-zero
!
!
!
ip host boating 223.255.254.254
no ftp-server write-enable
!
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
framing sf
crc-threshold 0
linecode ami
!
!
!
interface FastEthernet0/0
ip address 10.4.20.7 255.255.255.0
no ip mroute-cache
speed auto
half-duplex
no cdp enable
!
interface FastEthernet0/1
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 0.0.0.0 0.0.0.0 FastEthernet0/0
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 local FastEthernet0/0sccp ccm 10.4.20.24 identifier 1 version 4.0sccp ccm 10.4.20.25 identifier 2 version 4.0sccp ccm 10.4.20.26 identifier 3 version 4.0sccp ip precedence 3sccpsccp ccm group 48 associate ccm 1 priority 1 associate ccm 2 priority 2 associate ccm 3 priority 3 associate profile 10 register CFB123456789966 associate profile 6 register MTP123456789988 keepalive retries 5 switchover method immediate switchback method immediate switchback interval 15dspfarm profile 6 transcode codec g711ulaw codec g711alaw codec g729ar8 codec g729abr8 codec gsmfr maximum sessions 4 associate application SCCPdspfarm profile 10 conference codec g711ulaw codec g711alaw codec g729ar8 codec g729abr8 codec g729r8 codec g729br8 maximum sessions 1 associate application SCCP
!
dial-peer cor custom
!
!
dial-peer voice 200 voip
destination-pattern 111....
session target ipv4:10.4.205.24
!
dial-peer voice 2600 voip
destination-pattern 666....
session target ipv4:10.4.205.24
codec g711ulaw
!
dial-peer voice 100 voip
destination-pattern 5550...
session target ipv4:10.4.205.24
codec g711ulaw
!
dial-peer voice 10 pots
destination-pattern 7770000
forward-digits 0
!
dial-peer voice 11 pots
destination-pattern 7771111
!
dial-peer voice 999 voip
session target ipv4:10.4.205.8
!
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.
Current configuration : 1163 bytes
!
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname router
!
voice-card 1 dsp services dspfarm
!
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
!
interface FastEthernet0/0
ip address 10.10.10.11 255.255.255.0
load-interval 30
duplex auto
speed auto
!
interface FastEthernet0/1
ip address 10.3.150.139 255.0.0.0
load-interval 30
duplex auto
speed auto
!
ip classless
ip route 192.255.254.254 255.255.255.255 FastEthernet0/1
ip http server
!
call rsvp-sync
!
mgcp profile default
!
sccp local FastEthernet0/0 sccp sccp ccm 10.10.10.1 priority 1 sccp ccm 10.10.10.2 priority 2 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
!
mgcp profile default
!
dial-peer cor custom
!
dial-peer voice 10 pots
destination-pattern 3140001
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 Unified Communications Manager.
!
dial-peer voice 100 voip destination-pattern 313.... session target ipv4:10.10.10.1
!
! Following dial peer is for calls to IP Phones for conferencing.
! Session target is IP address of Cisco Unified Communications Manager.
!
dial-peer voice 200 voip destination-pattern 700.... session target ipv4:10.10.10.1 codec g711alaw
!
line con 0
line aux 0
line vty 0 4
login
!
end
The following running configuration example shows the SIP gateway configuration for the Out-Band to In-Band DTMF Relay feature:
Building configuration...
Current configuration : 2051 bytes
!
version 12.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname cisco_sip_gw
!
logging buffered 6000000 debugging
!
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
mpls ldp logging neighbor-changes
no ftp-server write-enable
no scripting tcl init
no scripting tcl encdir
!
!
no voice hpi capture buffer
no voice hpi capture destination
!
!
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.4.175.2
ccm-manager config
!
!
controller T1 2/0
framing esf
linecode b8zs
ds0-group 1 timeslots 1-24 type e&m-wink-start
!
controller T1 2/1
framing sf
linecode ami
!
!
!
interface FastEthernet0/0
ip address 10.4.175.14 255.255.0.0
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface BRI1/0
no ip address
!
ip default-gateway 10.4.0.1
ip classless
ip route 0.0.0.0 255.255.0.0 FastEthernet0/0
ip route 223.255.254.254 255.255.255.255 FastEthernet0/0
!
ip http server
!
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 1/1/0
!
voice-port 2/0:1
!
mgcp profile default
!
!
dial-peer voice 1 voip
destination-pattern 2000
session protocol sipv2
session target ipv4:10.4.175.2
dtmf-relay rtp-nte
codec g711ulaw
!
dial-peer voice 3 pots
application mgcpapp
port 2/0:1
!
dial-peer voice 999201 pots
application mgcpapp
port 2/0:1
!
dial-peer voice 2 pots
destination-pattern 2005
port 1/0/0
!
dial-peer voice 5 pots
destination-pattern 2001
port 1/0/0
!
!
line con 0
line aux 0
line vty 0 4
login
!
!
end
Universal Transcoding with an Inbox on a Universal Gateway Example
The following example shows a universal transcoding configuration with an inbox on a Cisco Unified Border Element on a universal gateway. Universal gateways include the Cisco AS5350XM and Cisco AS5400XM platforms:
iLBC_UUT1#sh run
Building configuration...
Current configuration : 3244 bytes
!
!
voice-card 5
dsp services dspfarm
!
voice-card 6
!
voice-card 7
dsp services dspfarm
!
!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
modem passthrough none codec g729r8 pre-ietf
!
!
interface GigabitEthernet0/0
ip address 10.10.10.2 255.255.0.0
duplex auto
speed auto
negotiation auto
!
interface GigabitEthernet0/1
ip address 10.20.20.2 255.255.0.0
duplex auto
speed auto
negotiation auto
!
!
sccp local GigabitEthernet0/0
sccp ccm 10.10.10.2 identifier 1
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 10 register MTPNEWONE
!
dspfarm profile 10 transcode universal
codec g711ulaw
codec g711alaw
codec ilbc
codec g723r63
codec g723r53
codec gsmamr-nb
codec g729ar8
codec g729abr8
maximum sessions 10
associate application SCCP
!
!
dial-peer voice 10 voip
destination-pattern 9991...
session protocol sipv2
session target ipv4:20.20.20.1
!
dial-peer voice 20 voip
session target ipv4:10.10.10.1
incoming called-number 9991...
codec ilbc
!
!
telephony-service -------------------------> Only Required for InBox
sdspfarm units 1
sdspfarm transcode sessions 128
sdspfarm tag 1 MTPNEWONE
ip source-address 10.10.10.2 port 2000
max-conferences 8 gain -6
transfer-system full-consult
!
G.711 to Any Transcoding with an Inbox on a Universal Gateway Example
The following example shows the configuration for transcoding for G.711 to any codec with an inbox on a Cisco Unified Border Element on a universal gateway. Universal gateways include the Cisco AS5350XM and Cisco AS5400XM platforms:
iLBC_UUT1#sh run
Building configuration...
Current configuration : 3244 bytes
!
!
voice-card 5
dsp services dspfarm
!
voice-card 6
!
voice-card 7
dsp services dspfarm
!
!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
modem passthrough none codec g729r8 pre-ietf
!
!
interface GigabitEthernet0/0
ip address 10.10.10.2 255.255.0.0
duplex auto
speed auto
negotiation auto
!
interface GigabitEthernet0/1
ip address 10.20.20.2 255.255.0.0
duplex auto
speed auto
negotiation auto
!
!
sccp local GigabitEthernet0/0
sccp ccm 10.10.10.2 identifier 1
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 20 register traditional
!
!
dspfarm profile 20 transcode
codec g711ulaw
codec g711alaw
codec ilbc
codec g723r63
codec g723r53
codec gsmamr-nb
codec g729ar8
codec g729abr8
maximum sessions 20
associate application SCCP
!
!
dial-peer voice 10 voip
destination-pattern 9991...
session protocol sipv2
session target ipv4:10.20.20.1
codec g711ulaw
!
dial-peer voice 20 voip
session target ipv4:10.10.10.1
incoming called-number 9991...
codec ilbc
!
!
telephony-service -------------------------> Only Required for InBox
sdspfarm units 1
sdspfarm transcode sessions 128
sdspfarm tag 1 traditional
ip source-address 10.10.10.2 port 2000
max-conferences 8 gain -6
transfer-system full-consult
!
Universal and G.711 to Any Transcoding with an Inbox on a Universal Gateway Example
The following example shows the configuration for transcoding for both universal and G.711 to any codec with an inbox on a Cisco Unified Border Element on a universal gateway. Universal gateways include the Cisco AS5350XM and Cisco AS5400XM platforms:
iLBC_UUT1#sh run
Building configuration...
!
voice-card 5
dsp services dspfarm
!
voice-card 6
!
voice-card 7
dsp services dspfarm
!
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
modem passthrough none codec g729r8 pre-ietf
!
!
interface GigabitEthernet0/0
ip address 10.10.10.2 255.255.0.0
duplex auto
speed auto
negotiation auto
!
interface GigabitEthernet0/1
ip address 10.20.20.2 255.255.0.0
duplex auto
speed auto
negotiation auto
!
!
sccp local GigabitEthernet0/0
sccp ccm 10.10.10.2 identifier 1
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 20 register traditional
associate profile 10 register MTPNEWONE
!
dspfarm profile 10 transcode universal
codec g711ulaw
codec g711alaw
codec ilbc
codec g723r63
codec g723r53
codec gsmamr-nb
codec g729ar8
codec g729abr8
maximum sessions 10
associate application SCCP
!
dspfarm profile 20 transcode
codec g711ulaw
codec g711alaw
codec ilbc
codec g723r63
codec g723r53
codec gsmamr-nb
codec g729ar8
codec g729abr8
maximum sessions 20
associate application SCCP
!
dial-peer voice 10 voip
destination-pattern 9991...
session protocol sipv2
session target ipv4:10.20.20.1
codec g711ulaw
!
dial-peer voice 20 voip
session target ipv4:10.10.10.1
incoming called-number 9991...
codec ilbc
!
!
telephony-service -------------------------> Only Required for InBox
sdspfarm units 2
sdspfarm transcode sessions 128
sdspfarm tag 1 traditional
sdspfarm tag 2 MTPNEWONE
ip source-address 10.10.10.2 port 2000
max-conferences 8 gain -6
transfer-system full-consult
!
Universal and G.711 to Any Transcoding with an Inbox on an ISR Example
The following example shows the configuration for transcoding for both universal and G.711 to any codec with an inbox on a Cisco Unified Border Element on an integrated services router. Integrated services routers include the Cisco 2800 and Cisco 3800 platforms:
crosby-3845#
!
voice-card 0
no dspfarm
dsp services dspfarm !
!
voice service voip
allow-connections h323 to h323
!
interface GigabitEthernet0/0
ip address 10.3.65.102 255.255.0.0
duplex auto
speed auto
media-type rj45
!
!
sccp local GigabitEthernet0/0
sccp ccm 10.3.65.102 identifier 1
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 20 register MTP000ABCD
associate profile 10 register OLDONE
keepalive retries 5
switchback method immediate
!
dspfarm profile 10 transcode ------------> for g711 to any
codec g711ulaw
codec g711alaw
codec ilbc
codec g723r63
codec g723r53
codec gsmamr-nb
codec g729ar8
codec g729abr8
maximum sessions 10
associate application SCCP
!
dspfarm profile 20 transcode universal --------------> for Any to Any
codec g711ulaw
codec g711alaw
codec ilbc
codec g723r63
codec g723r53
codec gsmamr-nb
codec g729ar8
codec g729abr8
maximum sessions 2
associate application SCCP
!
!
dial-peer voice 10 voip
destination-pattern 2...
session target ipv4:1.3.65.12
codec ilbc
!
dial-peer voice 11 voip
destination-pattern 1...
session target ipv4:10.3.65.11
codec g711ulaw
!
!
telephony-service -----------> Minimum config for telephony is required for InBox
ip source-address 10.3.65.102 port 2000
sdspfarm units 2
sdspfarm transcode sessions 30
sdspfarm tag 1 MTP000ABCD
sdspfarm tag 2 OLDONE
max-ephones 20
max-dn 20
max-conferences 12 gain -6
transfer-system full-consult
create cnf-files version-stamp 7960 Sep 27 2006 20:39:40
Where to Go Next
To enable MGCP on a Cisco IOS gateway, see
Configuring MGCP Gateway Support for Cisco Unified Communications Manager, page 23
.
To enable MGCP PRI backhaul support, see
"Configuring MGCP PRI Backhaul and T1 CAS Support for Cisco Unified Communications Manager" on page 113
.
To enable MGCP BRI backhaul support, see
"Configuring MGCP-Controlled Backhaul of BRI Signaling in Conjunction with Cisco Unified Communications Manager" on page 129
.
To download region-specific tones and the associated frequencies, amplitudes, and cadences, see
"Configuring Tone Download to MGCP Gateways" on page 145
.
Additional References
"Overview of Cisco Unified Communications Manager and Cisco IOS Interoperability" on page 13 --Describes basics of underlying technology and lists related documents.
"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.
"Connecting Voice Network Modules" chapter in the
Cisco Network Modules Hardware Installation Guide --Describes how to install the voice network modules.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.