06-24-2011 08:45 AM - edited 03-21-2019 04:16 AM
I get a "Cannot Complete Conference" when attempting to make a conference call. Fast busy on the meet me numbers also. Anyone seen this before? Could it be a bug or am i missing something?
Solved! Go to Solution.
06-24-2011 11:20 AM
In CCA under the conferencing link I would disable then enable multiparty conferencing. That should clear up your issue even if it was botched up via CLI. Let me know what happens.
06-24-2011 11:20 AM
In CCA under the conferencing link I would disable then enable multiparty conferencing. That should clear up your issue even if it was botched up via CLI. Let me know what happens.
06-28-2011 03:58 PM
Hi Eric,
Can you please do the following for me
on the command line execute the following command: ROUTER# sh dsp farm all
Provide the output on here.
Have you done a hard reboot of the phone system? Give that a try, in some cases the DSP resources have been locked out for unknown reasons, a complete power down (Count to ten) and then a power up seems to free up the resources and they get re-allocated again.
You may also want to look at reducing the size of the conference capabilities as well, just incase there is an issue with the resources.
Cheers,
David.
06-28-2011 04:40 PM
I had similar issues when I first started with Cisco UC500 systems. The issue had nothing to do with the actual configration, it was my lack of experiance. Here are my notes for creating a conference. (MeetMe, Ad-Hoc)
MeetMe
MeetMe conference is initiated by an internal user. Typically used when you are planning a conference, you can proactively setup a conference room.
You will receive a fast busy if you simply dial the MeetMe extension, for example lets assume we have assigned extension 700 to our MeetMe conference room.
If I pick up my phone and dial 700, the phone recives a fast busy, followed by the status message "Cannot Complete Conference"
When you want to create a MeetMe conference, use the softkey MeetMe.
Try the Following:
Conference Initiator: Press New Call | MeetMe | Dial the MeetMe extension (700)
Conference Attendees: New Call | Dial the MeetMe extension (700)
Once the conference room has been created, you DO NOT need to use the MeetMe softkey.
Ad-Hoc Conference
The ad-hoc conference is created during an active call for example you are on an active call and decide to conference in a third caller.
You do not dial an extension, the ad-hoc conference is completed with Confrn soft key.
For example:
Internal user 1 is on the phone with an external user, internal user 1 then decides to conference in a 2nd internal or external user.
1. During an active call press the Confrn soft key (This puts external caller on hold)
2. Dial the user you wish to conference in (Internal or External number) wait to the personal answers the call
3. Press the Confm soft key once again to complete the 3-way conference.
06-28-2011 06:07 PM
This is usually because the dspfarm profile for Conference isn't registered. If you run "Show dspfarm profile" command, you will see if the profile is in the "UP" state and is "ASSOCIATED". If you see something different, then there is some underlying issue causing the resource not to register.
Regards,
Adam Compton
07-05-2011 03:32 PM
I ended up disabling then enablling multiparty conferencing. The first time i tried this it did not work, the second time worked.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide