To configure a DSP conference bridge in IOS you will need to iron out a few sections of config in a particular order and then link it all together with the “associate” commands.

First, configure SCCP on the box and reference the UCM system(s) in your environment

!define a source
!reference your UCM system(s) and prioritize them when using redundancy
interfacesccp local GigabitEthernet0/0
sccp ccm 192.168.1.10 identifier 1 priority 1 version 7.0

Next, build out your dspfarm profile for this conference.  This is where you allocate resources and specify codecs that are supported

!name it and indicate its a conference.
!enumerate codecs
!indicate the maximum number of conferences that can be used at a time
!associate this profile with the SCCP process running on the router
dspfarm profile 1 conference
 codec g729br8
 codec g729r8
 codec g729abr8
 codec g729ar8
 codec g711alaw
 codec g711ulaw
 maximum sessions 1
 associate application SCCP

Next, we link the profile to the SCCP process and give it specific registration information.  Think of this config as the “device” that registers with CUCM.

!Give this "device" a unique group number
!Bind it to an interface on the router
!Associate to the CUCM defined above
!Associate the conference profile
!Specify the name by which this SCCP device will register with CUCM
sccp ccm group 1
 bind interface GigabitEthernet0/0
 associate ccm 1 priority 1
 associate profile 1 register TEST01

All in all the configuration sitting on the router will look like this:

sccp local GigabitEthernet0/0
sccp ccm 192.168.1.10 identifier 1 priority 1 version 7.0
sccp
!
sccp ccm group 1
description TEST01
bind interface GigabitEthernet0/0
associate ccm 1 priority 1
associate profile 1 register TEST01
!
!
!
dspfarm profile 1 conference
codec g729br8
codec g729r8
codec g729abr8
codec g729ar8
codec g711alaw
codec g711ulaw
maximum sessions 1
associate application SCCP