Ad-Hoc Conferencing And Active Directory; Integration - Polycom ReadiConvene Deployment Manual

Ad-hoc Conferencing and
Active Directory

Integration

An ad hoc conference is a conference that is started instantly, without a
reservation or conference definition. The new conference parameters are
taken from a Profile that is stored on the MCU and is linked to the Entry
Queue. In contrast to Meeting Rooms that are defined individually and
saved on the MCU, in ad-hoc conferencing only the Profile is predefined
and it is used to start many conferences, saving configuration time and
MCU resources. Once an ad-hoc conference is started it becomes an On
Going Conference and it is monitored and controlled as any standard On
Going Conference.
The Active Directory is used as an external database for validation. The
validation can be done at the Entry Queue level or at the conference
level, or both. The database can contain additional information
associated with the ID entered by the user. This information can be sent
back to the MCU together with the permission to create the conference
and it replaces the conference data taken from the Profile.
At the Entry Queue level, the user is prompted for the conference ID.
The ID entered by the user is checked against the list of ongoing
conferences. If such a conference does not exist on the MCU, a query is
sent to the Active Directory server to verify whether this ID can be used
to create a new conference. If the ID is confirmed, a new conference is
started on the MCU. If additional data is defined for this ID, the
information is returned from the Active Directory to the MCU and it
replaces the existing conference data taken from the Profile.
4
4-1