Polycom RealPresence 1800 Administration Manual page 365

Conference Access - Conference Password validation with External Database Application
Joining a conference entails:
1 When the conference is started (either in the Ad Hoc flow or in the standard method), all participants
connecting to the conference are moved to the Conference IVR queue where they are prompted for
the conference password.
2 When the participant enters the conference or personal password, it is sent to the external database
application for validation.
3 If there is a match, the participant is granted the right to join the conference. In addition, the external
database application sends to the MCU the following parameters:
 Participant name (display name)
 Whether or not the participant is the conference chairperson
 Participant Information, such as the participant E-mail. These fields correspond to Info 1, 2, 3 and
4 fields in the Participant Properties - Information dialog box.
If there is no match (i.e. the conference or personal password are not defined in the database), the
request to access the conference is rejected and the participant is disconnected from the MCU.
4 If the Conference IVR Service is configured to prompt for the chairperson identifier and password,
the participant is requested to enter the chairperson identifier.
 If no identifier is entered, the participant connects as a standard, undefined participant.
 If the chairperson identifier is entered, the participant is requested to enter the chairperson
password.
In this flow, the chairperson password is not validated with the external database application, only
with the MCU.
 If the correct chairperson password is entered, the participant is connected to the conference
as its chairperson.
 If the wrong password is entered, he/she is disconnected from the conference.
To enable conference access validation for all participants the following conferencing components are
required:
Polycom, Inc.
Appendix - Ad Hoc Conferencing and External Database Authentication
344