Overview
Transcoding is a process that converts a media stream encoded with one algorithm to another using Digital Signal Processors (DSPs). For example, a media stream encoded using OPUS may be decoded and re-encoded (transcoded) using G.711.
Note |
In high availability configurations, checkpointing for transcoded calls requires both the standby system and its DSPs to be ready when a call begins. Calls that are set up before the standby resources are ready will not be maintained on failover. |
Note |
SCCP-based transcoding is not supported with IOS XE releases. |
Note |
Video transcoding is not supported. This document only refers to transcoding for CUBE B2BUA calls. Refer to System Configuration Guide for Cisco Unified Communications Manager for UCM MTP details. |
LTI based Transcoding
-
Internal API is used to access Digital Signal Processor (DSP) resources for transcoding.
-
Transcoding resources (DSPFARM) and CUBE must be on the same platform.
-
Only DSPFARM profile configuration is required. Skinny Client Control Protocol (SCCP) configuration is not required.
-
No TCP socket is opened and no registration is used.
-
DSPFARM profile is associated to application type CUBE. Device(config)# dspfarm profile 1 transcode Device(config-dspfarm-profile)# associate application CUBE
-
DSPs are not used for encryption with IOS XE. As all media is encrypted or decrypted as it leaves or enters the platform, transcoding may be used for any combination of RTP-RTP, RTP-SRTP, or SRTP-SRTP calls.
Note |
Transcoding cannot be used for SRTP-Passthrough calls or when pass-thru content SDP is enabled. |
Note |
The following support LTI-based transcoding:
|