Drop Ad Hoc Conference, prevents toll fraud (where an internal conference controller disconnects from the conference while
outside callers remain connected). The service parameter settings specify conditions under which an ad hoc conference gets
Never—The conference does not get dropped. (We recommend that you use the default option to avoid unintentional termination of
When No OnNet Parties Remain in the Conference—The system drops the active conference when the last on-network party in the conference hangs up or drops out of the conference.
Unified Communications Manager releases all resources that are assigned to the conference.
Drop Ad Hoc Conference feature in an ILS deployment will not drop the parties when it set at When No OnNet Parties Remain in the Conference because the route patterns learned are classified as On Net.
When Conference Controller Leaves—The active conference terminates when the primary controller (conference creator) hangs up. Unified Communications Manager releases all resources that are assigned to the conference.
We recommend that you set this service parameter to Never. Any other setting can result in unintentional termination of a conference.
The Drop Ad Hoc Conference service parameter works differently for conference calls that are initiated from a Cisco Unified IP Phone 7940 or 7960 that is running SIP, or a third-party phone that is running SIP
Ad Hoc Conference
parameter specifies the maximum number of participants that are allowed in a
single Ad Hoc conference.
Ad Hoc Conference Enabled
parameter determines whether advanced Ad Hoc conference features are
enabled. This includes the ability of non-controller participants to add and
remove other participants and the ability of all participants to link ad hoc
Non-linear Ad Hoc Conference Linking Enabled
parameter determines whether more than two Ad Hoc conferences can be linked
directly to an Ad Hoc conference in a non-linear fashion ( three or more
conferences linked to any one conference).
Choose Encrypted Audio Conference Instead Of Video Conference
This parameter determines whether Unified Communications Manager chooses an encrypted audio conference bridge or an unencrypted video conference bridge for an Ad-Hoc conference call when
the conference controller's Device Security Mode is set to either Authenticated or Encrypted and at least two conference participants
are video-capable. Because encrypted video conference bridges are not supported in this release, Unified Communications Manager must choose between an encrypted audio conference bridge and an unencrypted video conference bridge. The default value is
Minimum Video Capable Participants To Allocate Video Conference
This parameter specifies the number of video-capable conference participants that must be present in an Ad Hoc conference
to allocate a video conference bridge. If the number of video-capable participants is less than the number specified in this
parameter, Unified Communications Manager allocates an audio conference bridge. If the number of video-capable participants is equal to, or greater than, the number
specified in this parameter, Unified Communications Manager allocates a video conference bridge, when available, from the configured media resource group list (MRGL). Specifying a value
of zero means that video conference bridges will always be allocated, even when none of the participants on the conference
are video-capable. When a conference has been established using an audio bridge and then additional video-capable participants
join the conference, the conference will remain on the audio bridge and will not convert to video. The default value is 2.
Allocate Video Conference Bridge For Audio Only Conferences When The Video Conference Bridge Has Higher Priority
This parameter determines whether Unified Communications Manager chooses a video conference bridge, when available, for an Ad Hoc audio-only conference call when the video conference bridge
has a higher priority than an audio conference bridge in the media resource group list (MRGL). If an audio conference bridge
has higher priority than any video conference bridge in the MRGL, Unified Communications Manager ignores this parameter. This parameter proves useful in situations where the local conference bridge is a video bridge (and
configured in the MRGL with the highest priority) and audio conference bridges are only available in remote locations; in
that situation, enabling this parameter means thatUnified Communications Manager would attempt to use the local video conference bridge first, even for audio-only conference calls. The default value is
Click-to-Conference for Third-Party Applications
This parameter determines whether the Click-to-Conference functionality over the SIP trunk is enabled on Unified Communications Manager. The Click-to-Conference feature allows third-party applications to setup a conference using the SIP out of dialog REFER
method and subscribe to the SIP trunk for Conference Event Package through SIP SUBSCRIBE/NOTIFY.
Enabling this parameter could negatively affect CTI applications that are not
coded to support this feature.
Cluster Conferencing Prefix Identifier
This parameter defines a number, up to 8 digits (e.g. 0001), that is prefixed to a conference identifier generated for Adhoc
and Meet-Me conferences that will be hosted on a SIP conference bridge such as Cisco Telepresence MCU or Cisco Telepresence
Conductor. This field should be populated by the administrator when there are multiple clusters in a network that will be
sharing the SIP conference bridges that Unified Communications Manager manages. Every cluster should be configured with a unique prefix to ensure that the conference identifier for Adhoc and Meet-Me
conferences is unique. If conference resources are not being shared across clusters, then this field may not be populated.