Which Cisco Unified Communications Manager service parameter should be enabled disconnect a multiparty call when the call initiator hangs up?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmsys/CUCM_BK_SE5FCFB6_00_cucm-system-guide-100/The correct answer to the question is A. Drop Ad Hoc Conference.
In Cisco Unified Communications Manager (CUCM), a multiparty call is a conference call where more than two parties are involved. By default, when the initiator of a multiparty call hangs up, the other parties continue to be connected until they also hang up or the call is terminated by other means.
To enable the automatic termination of a multiparty call when the initiator hangs up, the "Drop Ad Hoc Conference" service parameter should be enabled. This parameter is located in the "Clusterwide Parameters (System - Service)" section of the CUCM Administration web interface.
Enabling the "Drop Ad Hoc Conference" parameter causes the conference to be terminated when the initiator hangs up, regardless of whether other parties are still on the call. This helps to prevent long-lasting conference calls that tie up resources and can cause confusion when participants are left on the call without the initiator.
Option B, "H.225 Block Setup Destination," is a service parameter used to prevent the establishment of H.225 connections to certain IP addresses or IP address ranges.
Option C, "Block OffNet to OffNet Transfer," is a service parameter used to prevent the transfer of calls between two off-net (external) destinations.
Option D, "Enterprise Feature Access Code for Conference," is a service parameter used to define an access code that is required to initiate an ad hoc conference call. This access code is used to prevent unauthorized conference calls from being established.