Configuring DSP Resources

Step 1.

Set the interface used for Skinny Client Control Protocol (SCCP).

Gateway(config)#sccp local interface

The IP address of the configured interface is used to register with CallManager. For C549 DSPs, the MAC address of the physical interface is used for the device name. Transcoders will use the device name MTPxxxxxxxxxxxx, and Conference bridges will use the device name CFBxxxxxxxxxxxx, where xxxxxxxxxxxx is the MAC address.

Step 2.

Configure the CallManager address.

Gateway(config)#sccp ccm ipaddr [priority priority-level]

The default priority level is 1. You can configure up to three redundant CallManagers by using the priority option.

Step 3.

Enable SCCP.

Gateway(config)#sccp

You must set the sccp local interface before you enter the sccp command. When you enter the sccp command, the gateway initiates the registration process with CallManager.

Step 4.

Configure the voice card to support transcoding and conferencing.

Gateway(config-voicecard)#dsp services dspfarm  

Step 5.

Set the number of transcoder and conference sessions.

Gateway(config)#dspfarm transcoder maximum sessions number Gateway(config)#dspfarm confbridge maximum sessions number  

Step 6.

Enable DSP farming.

Gateway(config)#dspfarm  

Step 7.

Configure the transcoder and conference bridge resources in CallManager.

[View full width]

Step 1.

Set the interface used for SCCP.

GW_2811(config)#sccp local interface

For Enhanced Transcoding and Conferencing, this command only determines which IP address CallManager will use to communicate with the gateway. The device name(s) are defined in a later step.

Step 2.

Configure the CallManager addresses.

GW_2811(config)#sccp ccm ipaddr identifier identifier [version ccm version]

Each CallManager that the gateway will register with must be configured with a unique identifier. In a later step, one or more CallManager groups will be created. You will associate the CallManager identifiers that you create here with a CallManager group and assign them a priority for registration.

Specifying the CallManager version is optional but should be set to avoid registration issues.

Step 3.

Initialize SCCP.

GW_2811(config)#sccp  

Step 4.

Configure the voice card to support transcoding and conferencing.

GW_2811(config)#voice-card 0 GW_2811(config-voicecard)#dsp services dspfarm  

Step 5.

Create a DSP farm profile for transcoding.

GW_2811(config)#dspfarm profile profile transcoder GW_2811(config-dsp-profile)#associate application sccp GW_2811(config-dsp-profile)#maximum sessions number GW_2811(config-dsp-profile)#no shutdown

With Enhanced Transcoding and Conferencing, you create one or more profiles for each service type. You can associate each profile with a CallManager group. The profiles are always associated with the application sccp.

Step 6.

Create a DSP farm profile for conferencing.

GW_2811(config)#dspfarm profile profile conference GW_2811(config-dsp-profile)#associate application sccp GW_2811(config-dsp-profile)#maximum sessions sessions GW_2811(config-dsp-profile)#no shutdown  

Step 7.

Create a DSP farm profile for MTP.

GW_2811(config)#dspfarm profile profile mtp GW_2811(config-dsp-profile)#associate application sccp GW_2811(config-dsp-profile)#maximum sessions {hardware|software} sessions GW_2811(config-dsp-profile)#no shutdown

You can configure software MTPs without enabling DSP services on the voice-card, even if no voice card is installed in the router.

Step 8.

Associate profiles with CallManager groups.

GW_2811(config)#sccp ccm group number GW_2811(config-sccp-ccm)#associate ccm identifier priority priority GW_2811(config-sccp-ccm)#associate profile profile register device-name GW_2811(config-sccp-ccm)#bind interface interface

You can associate multiple profiles with a CallManager group. Each profile is assigned a unique device-name between 6 and 16 characters long, which is used to register with CallManager. The device-name must be unique to the ccm group.

Step 9.

Define the resources in CallManager.

[View full width]