CME supports DSPs for transcoding. It does not support DSP-based conference bridges at this time. The configuration is similar to registering DSPs to a CallManager. The IP address used in the sccp ccm command is the IP address of the CME service. This should match the ip source-address specified under telephony-service.
After you have completed Step 6 for C549 DSPs or Step 8 for C5510 DSPs, the following steps register the transcoders to CME:
Enter telephony-service configuration mode.
Set the maximum number of DSP farms that can be registered to CME.
GW_2811(config-telephony)#sdspfarm units number
A CME can support up to five transcoder sessions. These can be locally defined transcoders on the CME gateway or DSPs that are defined on other gateways.
Specify the maximum number of transcoding sessions supported across all registered transcoders.
GW_2811(config-telephony)#sdspfarm transcode sessions number
This is the total number of sessions provided by all registered transcoders. Valid entries are 1 through 128.
Specify the name of the DSP farm.
GW_2811(config-telephony)#sdspfarm tag number device-name
The device name follows the same rules as CallManager registrations. For C549 DSPs, the device-name is "MTP" plus the MAC address of the SCCP local interface. For C5510 DSPs, the device-name is specified when you associate the transcoder profile to the ccm group.
Case Study Add DSP Resources to the Miami Gateway
Part I: Voice Gateways and Gatekeepers
Gateways and Gatekeepers
Part II: Gateways
Media Gateway Control Protocol
Session Initiation Protocol
Connecting to the PSTN
Connecting to PBXs
Connecting to an IP WAN
Influencing Path Selection
Configuring Class of Restrictions
SRST and MGCP Gateway Fallback
Using Tcl Scripts and VoiceXML
Part III: Gatekeepers
Part IV: IP-to-IP Gateways
Cisco Multiservice IP-to-IP Gateway
Appendix A. Answers to Chapter-Ending Review Questions