1. Create Conferencing DSP farm profile
dspfarm profile 1 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
maximum sessions 2
associate application SCCP
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
maximum sessions 2
associate application SCCP
2. DSP farm profile SCCP configuration
sccp local GigabitEthernet0/0
sccp ccm 192.168.20.254 identifier 1 priority 1 version 7.0
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register CFB
sccp ccm 192.168.20.254 identifier 1 priority 1 version 7.0
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register CFB
3. sdspfarm configuration on CME under telephony-service
telephony-service
sdspfarm units 2
sdspfarm tag 1 CFB
no privacy
conference hardware
sdspfarm units 2
sdspfarm tag 1 CFB
no privacy
conference hardware
4. Create ephone template with cBarge softkey in remote-in-use state
ephone-template 1
softkeys remote-in-use CBarge Newcall
softkeys remote-in-use CBarge Newcall
5. Sample ephone configuration
ephone 1
privacy off
privacy-button
device-security-mode none
mac-address 0021.5555.5555
ephone-template 1
type 7965
button 1:1 2:3
!
!
!
ephone 2
privacy off
privacy-button
device-security-mode none
mac-address 0026.2222.2222
ephone-template 1
type 7975
button 1:2 2:3
privacy off
privacy-button
device-security-mode none
mac-address 0021.5555.5555
ephone-template 1
type 7965
button 1:1 2:3
!
!
!
ephone 2
privacy off
privacy-button
device-security-mode none
mac-address 0026.2222.2222
ephone-template 1
type 7975
button 1:2 2:3
6. Create shared line ephone-dn and ad-hoc conference ephone-dn
ephone-dn 3 octo-line
number 5003
!
!
ephone-dn 4 octo-line
number A123
conference ad-hoc
number 5003
!
!
ephone-dn 4 octo-line
number A123
conference ad-hoc
After I've created the ephone-dn 4 for ad-hoc conferencing, cBarge is setup successfully without the error any more!
3 comments:
Thanks for posting this!
I had the same problem and I was able to resolve it following your blog!
This actually really helped me. Can you explain why does the ad-hoc octo-line need to be be configured to get it work since its not associated with anything? The Cbarge couldn't work without it but I understand why not?
You can take a look at this:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeadm/cmebarge.html
Ad-hoc conference resource needs to be setup prior using cBarge. And that ad-hoc conference DN is a system DN, will not be used directly by end users but by the system itself, therefore you need that in place before cBarge will work.
Post a Comment