02-24-2017 02:48 AM - edited 03-19-2019 12:09 PM
Hi Guys,
I am new here on the Support Forum.
I have a few small questions regarding Ad-Hoc Conferencing on a BE6000S system.
When you make a conference call and have lets say 5 people in the group and you as the initiator disconnects or ends the call. What happens to the remaining users and who handles those calls?
Why I am asking is the following when I test this on our system which I setup myself, When I leave the call from my IP Phone extension the other 2 external cell calls are still connected.
Is our system handling those calls? ie are we still paying for those calls?
If YES to the above how do I go about setting it up that the conference collapses when the initiator leaves.
Thanks in advance.
Solved! Go to Solution.
02-24-2017 05:08 AM
The default behavior is for the ad-hoc conference to continue until two participants remain, at which point the call drops back to a direct call. That distinction is important if you want to prevent this.
There are two CUCM Service Parameters under the Cisco CallManager service:
For your example where there are five people in an ad-hoc conference and the initiator leaves, changing Drop Ad Hoc Conference to a setting other than Never will cause the conference to end and hang up on the remaining participants. Be careful that this applies to all conferences system-wide, even simple three-way calls.
You may also need to set the Block OffNet To OffNet Transfer to True and ensure that all Gateways or Trunks that face the PSTN are classified as an OffNet destination. The may be necessary (i.e. you should test this) on a three-way call where the initiator drops. At that point the call effectively becomes a transfer and not a conference. I'm just not certain whether Drop Ad Hoc Conference would cover this scenario or not. Use caution though as this would prevent anyone from transferring a offnet call back out to the PSTN (e.g. someone calls the receptionist and she wants to transfer to an employee's cell phone).
02-24-2017 05:08 AM
The default behavior is for the ad-hoc conference to continue until two participants remain, at which point the call drops back to a direct call. That distinction is important if you want to prevent this.
There are two CUCM Service Parameters under the Cisco CallManager service:
For your example where there are five people in an ad-hoc conference and the initiator leaves, changing Drop Ad Hoc Conference to a setting other than Never will cause the conference to end and hang up on the remaining participants. Be careful that this applies to all conferences system-wide, even simple three-way calls.
You may also need to set the Block OffNet To OffNet Transfer to True and ensure that all Gateways or Trunks that face the PSTN are classified as an OffNet destination. The may be necessary (i.e. you should test this) on a three-way call where the initiator drops. At that point the call effectively becomes a transfer and not a conference. I'm just not certain whether Drop Ad Hoc Conference would cover this scenario or not. Use caution though as this would prevent anyone from transferring a offnet call back out to the PSTN (e.g. someone calls the receptionist and she wants to transfer to an employee's cell phone).
03-01-2017 01:54 AM
Hi Johnathan,
That was a perfect explanation it helped me a lot in understanding the Incoming and Outgoing of Call traffic flow of our system.
Thank you for taking the time in answering my question!
Kind Regards,
Chris
11-22-2018 05:37 PM
How can I do the same with the conference now, I noticed that when the controller leave the conference the rest of the parties remains in it.
11-22-2018 08:32 PM
You can't, conference now is basically a front end for a meet me conference and those parameters are not applicable.
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