If a Cisco router running CME also has PVDM modules installed the router may be configured to support hardware conferencing for features such as MeetMe conferences or cBarge.
1. The voice-card command references a dspfarm so more than one PVDM may be allocated for DSP availability.
dsp services dspfarm
2. Skinny is the protocol used to communicate with the MTP internal to the router. We define the source sccp packets to come from loopback 0. The ccm IP is the telephony-service IP so sccp knows the CME IP to register to. The name CME-CONF is used to name this MTP. When sccp registers with the CME IP it will reference the name CME-CONF. We will define this in telephony-service as well.
sccp local loopback 0
sccp ccm 192.168.1.254 identifier 1 priority 1 version 7.0
sccp ccm group 1
bind interface loopback 0
associate ccm 1 priority 1
associate profile 1 register CME-CONF
3. After the sccp configuration has been completed the dspfarm profile 1 (as referenced by sccp ccm group 1) must be created for conferencing. By default the dspfarm is shutdown.
dspfarm profile 1 conference
maximum sessions 2
associate application SCCP
4. The heart of CME’s configuration lies within telephony-service. Here we tell CME to use hardware conferencing and that the dspfarm registered by Skinny will be CME-CONF. The sdspfarm units tell CME the maximum number of sccp dspfarms that can be registered with CME.
sdspfarm units 5
sdspfarm tag 1 CME-CONF