Study guide
7.4 IOS XE Media Resources & DSP Management
Cisco 350-801 CLCOR CCNP/CCIE Collaboration Core v2.0
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Collaboration Architecture, Deployment Models, Sizing & Upgrades
1.1 Collaboration Architecture & Deployment Models 1.2 Capacity Planning, Sizing & Bandwidth Considerations 1.3 High Availability, Redundancy & Disaster Recovery 1.4 Cisco Unified CM Cluster Upgrade Process
2 Chapter 2: Edge Architecture, Security & Network Services
2.1 Collaboration Edge Architecture: CUBE & Expressway 2.2 Security Protocols & PKI: SSO, OAuth, TLS & SRTP 2.3 Network Infrastructure Services: DNS, NTP, DHCP & LDAP
3 Chapter 3: Protocols, Codecs & Endpoint Provisioning
3.1 SIP Signaling Architecture & Call Flows 3.2 Session Description Protocol (SDP) & Early Offer vs. Delayed Offer 3.3 Audio/Video Codecs & DTMF Relay 3.4 Endpoint Deployment, Onboarding & Troubleshooting
4 Chapter 4: CUCM Dial Plan Fundamentals & Digit Analysis
4.1 Partitions and Calling Search Spaces (CSS) 4.2 Route Patterns, Route Groups & Route Lists 4.3 Translation Patterns, Transformation Patterns & Digit Manipulation 4.4 Globalized Call Routing & Local Route Group (LRG)
5 Chapter 5: Advanced Call Control, Call Routing & User Management
5.1 Call Admission Control (CAC), Locations & AAR 5.2 Toll Fraud Prevention & Call Privileges 5.3 CUCM User Management, LDAP Integration & RBAC 5.4 Administrative XML (AXL) API & Dial-Plan Troubleshooting Tools
6 Chapter 6: Cisco Unity Connection & Voicemail Integration
6.1 Cisco Unity Connection Architecture & SIP Integration 6.2 Mailbox Provisioning, User Templates & Class of Service 6.3 Message Waiting Indication (MWI) & Troubleshooting 6.4 Call Handlers & Directory Handlers
7 Chapter 7: IOS XE Voice Gateways, CUBE & Media Resources
7.1 Cisco IOS XE Voice Gateways & Dial Peers 7.2 Voice Translation Rules and Translation Profiles 7.3 Cisco Unified Border Element (CUBE) Configuration & Redundancy 7.4 IOS XE Media Resources & DSP Management
8 Chapter 8: Webex Architecture, Control Hub, Meetings & Messaging
8.1 Webex Suite Overview & Control Hub Architecture 8.2 Cloud Identity Management, SCIM & Directory Connector 8.3 Webex Developer Platform & APIs 8.4 Configuring Webex Cloud Meetings 8.5 Configuring Webex Cloud Messaging
9 Chapter 9: Webex Calling Routing, Permissions & PSTN Connectivity
9.1 Webex Calling Architecture, Locations & Number Management 9.2 Webex Calling Routing, Trunks & Dial Plans 9.3 Webex Calling Call Routing Process & Translation Patterns 9.4 Webex Calling Toll Fraud Prevention, Call Permissions & Operating Modes 9.5 PSTN Connectivity: Cloud-Connected PSTN (CC-PSTN) & Cisco Calling Plans 9.6 Webex Calling Local Gateway (LGW) Architecture & Configuration
10 Chapter 10: Webex Hybrid Services & Cloud Connected UC
10.1 Cloud-Connected UC (CCUC) Architecture & Telemetry 10.2 Webex Hybrid Calendar & Hybrid Directory Services 10.3 Webex Video Mesh & Hybrid Data Security
11 Chapter 11: Media Quality, QoS Engineering & Troubleshooting
11.1 Real-Time Media Characteristics & Impairments 11.2 QoS Classification, Marking & Trust Boundaries 11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE 11.4 Troubleshooting Media Quality & Call Failures
7.4 IOS XE Media Resources & DSP Management
Key Takeaways Explain This Topic AI
Hardware Digital Signal Processors (PVDM3 and PVDM4) provide dedicated silicon on Cisco voice gateways for high-density audio transcoding, conference mixing, and media termination points.
DSP farm profiles define specialized media resource services (transcode, conference, mtp) that register to Cisco Unified Communications Manager using the Skinny Client Control Protocol (SCCP).
Universal transcoding allows any-to-any codec translation between disparate algorithms and sampling rates (such as wideband G.722 16 kHz to narrowband G.711/G.729 8 kHz), unlike standard transcoding which is limited to G.711 and G.729.
Hardware Media Termination Points (MTPs) resolve packetization interval mismatches (e.g., 20 ms to 30 ms), bridge dynamic payload types, and convert in-band DTMF to RFC 2833.
In CUCM, Media Resource Groups (MRGs) aggregate hardware and software media resources, and Media Resource Group Lists (MRGLs) assign prioritized resource pools to Device Pools and individual endpoints.
Last updated: October 2026
7.4 IOS XE Media Resources & DSP Management
In enterprise unified communications networks, diverse endpoints and trunks negotiate contrasting audio codecs, packetization intervals, signaling protocols, and encryption standards. When two communicating endpoints cannot establish a direct, compatible media stream—such as an external mobile caller negotiating G.729 over a WAN trunk speaking to an internal contact center agent negotiating G.711 or wideband G.722—a media resource must intercept, decode, translate, and re-encode the Real-time Transport Protocol (RTP) bitstreams in real time.
While Cisco Unified Communications Manager (CUCM) can supply basic software-based media resources, enterprise deployments rely on Hardware Digital Signal Processor (DSP) modules hosted within Cisco IOS XE voice gateways for scalable, high-fidelity media processing. +-----------------------------------------------------------------------------------------+
- | HARDWARE DSP FARM ARCHITECTURE IN IOS XE |
- | |
- | +-----------------------------------------------------------------------------------+ |
- | | CISCO IOS XE ROUTER | |
- | | | |
- | | +----------------------+ +---------------------+ +--------------------+ | |
- | | | PVDM4 HARDWARE DSP | | PVDM4 HARDWARE DSP | | PVDM4 HARDWARE DSP | | |
- | | | (Transcoding) | | (Conferencing) | | (MTP) | | |
- | | +----------+-----------+ +----------+----------+ +---------+----------+ | |
- | | | | | | |
- | | v v v | |
- | | [ Profile 1: XCODE ] [ Profile 2: CONF ] [ Profile 3: MTP ] | |
- | | \ | / | |
- | | +---------------------------+------------------------+ | |
- | | | | |
- | | v | |
- | | [ SCCP Client Subsystem ] | |
- | +------------------------------------------+----------------------------------------+ |
- | | |
- | SCCP | TCP Port 2000 |
- | v |
- | +-----------------------------------------------------------------------------------+ |
- | | CISCO UNIFIED COMMUNICATIONS MANAGER (CUCM) | |
- | | - Discovers Hardware Resources via SCCP Registration | |
- | | - Groups Resources into Media Resource Groups (MRGs) | |
- | | - Assigns Prioritized MRGLs to Device Pools & Endpoints | |
- | +-----------------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------------+
- 1. Cisco Hardware DSP Architecture: PVDM3 vs. PVDM4
Cisco Packet Voice Digital Signal Processor Modules (PVDMs) are specialized hardware acceleration daughter cards mounted directly onto the motherboard or Network Interface Modules (NIMs) of Cisco voice routers.
Architectural Evolution
PVDM3 (ISR G2 / 2900 & 3900 Series) : Multi-core DSPs connected across the internal TDM backplane of the router. Supports high-density voice processing, standard transcoding, and audio conferencing, but requires motherboard TDM bus routing for packet-to-packet DSP tasks.
PVDM4 (ISR 4000 & Catalyst 8000 Series) : Directly interfaced with the router's centralized packet forwarding engine (QuantumFlow Processor - QFP). PVDM4 modules plug directly into NIM carrier slots or motherboard DSP slots, eliminating legacy TDM backplane bottlenecks.
Hardware DSPs vs. Software Media Resources
- Capability CUCM Software Media Resource IOS XE Hardware DSP (PVDM4)
- Processing Location Virtual machine CPU (ESXi Host) Dedicated DSP hardware silicon on router
- Transcoding Support None (Cannot transcode audio) Universal any-to-any transcoding
- Sampling Rate Conversion None 8 kHz (narrowband) to 16 kHz (wideband)
Conference Mixing Limited codec support (mainly G.711); CPU intensive Multi-codec (G.711, G.729, G.722 wideband)
- Codec Complexity Fixed Dynamic DSP credit allocation
- Jitter & Latency Variable (subject to VM hypervisor load) Deterministic sub-millisecond hardware processing
- 2. DSP Farm Configuration & Services
A DSP Farm is the Cisco IOS XE software architecture that allocates physical DSP channels into logical pools of media processing services. Configuring a DSP farm requires three core configuration steps:
- Step 1: Enable DSP Services on the Voice Card voice-card 0/1
- dsp services dspfarm
- Step 2: Configure DSP Farm Profiles
Each DSP farm profile defines a specific media function: transcoding , conferencing , or Media Termination Point (MTP) . ! --- Profile 1: Hardware Transcoder ---
- dspfarm profile 1 transcode universal
- description == Hardware Universal Transcoder for WAN Trunks ==
- codec g711ulaw
- codec g711alaw
- codec g729ar8
- codec g729abr8
- codec g722-64
- maximum sessions 24
- associate application SCCP
- no shutdown
!
- ! --- Profile 2: Hardware Conference Bridge ---
- dspfarm profile 2 conference
- description == Hardware Audio Conference Bridge ==
- codec g711ulaw
- codec g711alaw
- codec g729ar8
- codec g722-64
- maximum sessions 12
- associate application SCCP
- no shutdown
!
- ! --- Profile 3: Hardware MTP ---
- dspfarm profile 3 mtp
- description == Hardware MTP for DTMF & Packetization Interworking ==
- codec g711ulaw
- maximum sessions hardware 30
- associate application SCCP
- no shutdown
- 3. Transcoding: Universal vs. Standard Transcoding
Transcoding is the real-time conversion of an encoded digital audio stream from one compression algorithm to another.
Standard Transcoding
Converts between G.711 mu-law / a-law (64 kbps uncompressed narrowband audio sampled at 8 kHz) and G.729a / G.729b (8 kbps compressed audio sampled at 8 kHz).
Requires that both streams operate at the same audio sampling frequency (8 kHz narrowband).
Universal Transcoding
Supported natively on PVDM3 and PVDM4 hardware.
Enables any-to-any codec translation across disparate codec families, bit rates, and sampling frequencies.
Translates wideband audio (e.g., G.722 , sampled at 16 kHz / 64 kbps) to narrowband audio (e.g., G.711 or G.729, sampled at 8 kHz) by performing real-time downsampling and upsampling .
Configured with dspfarm profile <tag> transcode universal ; a plain transcode profile supports only standard (G.711 to G.729 family) transcoding.
Supports additional codecs such as iLBC and G.722; check the platform's DSP codec matrix for the exact list.
DSP Credit Allocation & Channel Density
PVDM4 modules utilize a credit-based resource sharing architecture. High-complexity codecs and wideband sampling require significantly more DSP processing credits than simple narrowband codecs:
Transcoding between G.711 and G.729 requires standard complexity credits .
Transcoding between G.722 wideband and G.729 requires high complexity credits , effectively reducing the total number of simultaneous sessions supported by the physical PVDM chip.
4. Hardware Audio Conferencing
A hardware conference bridge sums multiple incoming audio streams into a combined composite audio mix, reproducing a unified conversation for all participants:
Dynamic Mixing & Active Speaker Selection : Hardware DSPs analyze energy levels across all incoming RTP streams, mixing the audio of the loudest active speakers (typically the top 3 active speakers) while suppressing background noise from passive listeners.
Multi-Codec Participation : Hardware conference bridges allow endpoints using different codecs (e.g., an internal G.722 executive phone, an internal G.711 user, and an external G.729 mobile caller) to join the same conference room without requiring separate external transcoders.
5. Hardware Media Termination Point (MTP)
An MTP is a software or hardware resource that extends or bridges two RTP media streams without altering the underlying audio payload algorithm.
Primary Operational Roles of MTPs
Packetization Interval Bridging : When an originating endpoint packetizes audio at 20 ms sample sizes (standard for Cisco IP phones) and a legacy PBX requires 30 ms packetization , an MTP buffers and restructures the RTP payload frames without transcoding the audio.
DTMF Method Interworking : Bridges disparate DTMF signaling mechanisms, such as translating RFC 2833 (RTP Named Telephony Events) to In-Band Audio tones or H.245 alphanumeric signaling.
SIP Early Offer (EO) Support : Legacy third-party PBXs or SIP trunks may require an incoming SIP INVITE to contain an initial SDP media offer (Early Offer). If a calling device only supports Delayed Offer (sending SDP in the ACK), CUCM inserts an MTP into the call path to generate the initial SDP offer on behalf of the calling station.
6. SCCP Control & Registration to CUCM
While call signaling between CUCM and voice gateways uses SIP, DSP farm profiles register to CUCM using the Skinny Client Control Protocol (SCCP) over TCP port 2000 : ! --- Configure SCCP Local Source & CUCM Cluster Bindings ---
- sccp local GigabitEthernet0/0/0
- sccp ccm 10.1.10.11 identifier 1 priority 1 version 7.0+
- sccp ccm 10.1.10.12 identifier 2 priority 2 version 7.0+
!
- sccp ccm group 1
- associate ccm 1 priority 1
- associate ccm 2 priority 2
- associate profile 1 register XCODE_ROUTER1
- associate profile 2 register CONF_ROUTER1
- associate profile 3 register MTP_ROUTER1
!
- sccp
- CUCM Device Registration
When the sccp global command is enabled, the router opens an SCCP signaling session to the primary CUCM subscriber ( 10.1.10.11 ). In CUCM Administration under Media Resources , administrators configure corresponding entries for:
- Transcoder (Device Name: XCODE_ROUTER1 )
- Conference Bridge (Device Name: CONF_ROUTER1 )
- Media Termination Point (Device Name: MTP_ROUTER1 )
Once configured, the devices show a registration status of Registered with the router's IP address.
7. CUCM Media Resource Management: MRGs and MRGLs
CUCM allocates media resources to endpoints and trunks using a hierarchical two-tier framework: +-----------------------------------------------------------------------------------+
- | CUCM MEDIA RESOURCE ALLOCATION |
- | |
- | [ INDIVIDUAL MEDIA RESOURCES ] |
- | - Hardware Transcoder (XCODE_ROUTER1) |
- | - Hardware Conference Bridge (CONF_ROUTER1) |
- | - Software Conference Bridge (CFB_CUCM-SUB1) |
- | - Hardware MTP (MTP_ROUTER1) |
- | | |
- | v |
- | [ MEDIA RESOURCE GROUPS (MRGs) ] |
- | +-----------------------------------+ +-----------------------------------+ |
- | | MRG_BRANCH_HARDWARE | | MRG_CENTRAL_SOFTWARE | |
- | | - XCODE_ROUTER1 | | - CFB_CUCM-SUB1 | |
- | | - CONF_ROUTER1 | | - MOH_CUCM-SUB1 | |
- | | - MTP_ROUTER1 | | | |
- | +-----------------+-----------------+ +-----------------+-----------------+ |
- | | | |
- | +--------------------+--------------------+ |
- | | |
- | v |
- | [ MEDIA RESOURCE GROUP LIST (MRGL) ] |
- | +-----------------------------------------------------------------------------+ |
- | | MRGL_BRANCH_OFFICE: | |
- | | 1. MRG_BRANCH_HARDWARE (Priority 1 - Local Hardware Low Latency) | |
- | | 2. MRG_CENTRAL_SOFTWARE (Priority 2 - Central Failover Backup) | |
- | +--------------------------------------+--------------------------------------+ |
- | | |
- | v Assigned to: |
- | [ DEVICE POOL / ENDPOINT ] (Branch Phones, Local SIP Trunks, Branch Gateways) |
- +-----------------------------------------------------------------------------------+
- Media Resource Group (MRG)
An MRG is an unordered logical grouping of media resources.
An MRG can contain any combination of transcoders, conference bridges, MTPs, and Music on Hold (MOH) servers.
Media Resource Group List (MRGL)
An MRGL defines an ordered, prioritized list of MRGs .
When an endpoint or trunk requires a media resource (e.g., an MTP for an Early Offer SIP call), CUCM evaluates the endpoint's MRGL from top to bottom:
CUCM checks the first MRG in the list for an available resource of the required type.
If all resources in the first MRG are exhausted, out of service, or lack the requested capability, CUCM evaluates the second MRG.
If no resource is found across any MRG in the assigned MRGL, CUCM falls back to the system Default Media Resource Group (which contains all unassigned resources in the cluster). If still unavailable, the media operation fails.
MRGL Assignment Precedence
MRGLs can be applied at two administrative levels in CUCM:
Device Level (Direct Configuration) : Assigned directly on an IP Phone, SIP Trunk, or Voice Gateway configuration page.
Device Pool Level : Assigned to a Device Pool inherited by all devices within that pool.
Precedence Rule : An MRGL assigned directly at the Device Level takes absolute precedence over an MRGL configured at the Device Pool level.