Polycom RealPresence 1800 Administration Manual page 364

Conference Access with External Database
Authentication
The MCU can work with an external database application to validate the participant's right to join an existing
conference. The external database contains a list of participants, with their assigned parameters. The
conference password or chairperson password entered by the participant is compared against the database.
If the system finds a match, the participant is granted the permission to access the conference.
To work with an external database application to validate the participant's right to join the conference, the
Conference IVR Service must be configured to use the external database application for authentication.
Conference access authentication can be performed as:
● Part of the Ad Hoc conferencing flow where the participants must be authorized before they can enter
the conference created in the Ad Hoc flow
● Independent of Ad Hoc conferencing where conference access is validated for all conferences
running on the MCU regardless of the method in which the conference was started.
Conference access authentication can be implemented for all participants joining the conference or for
chairpersons only.
Conference Access Validation - All Participants
(Always)
Once the conference is created either via an Ad Hoc Entry Queue, or a standard ongoing conference, the
right to join the conference is authenticated with the external database application for all participants
connecting to the conference.
Polycom, Inc.
Appendix - Ad Hoc Conferencing and External Database Authentication
343