Appendix D - Ad Hoc Conferencing and External Database Authentication
Polycom®, Inc. 689
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:
●The external database must hold the conference password or the participant personal password/PIN
code or the participant’s Alias.
●The Conference IVR Service assigned to the conference (defined in the Profile) must be configured
to authenticate the participant’s right to access the conference with the external database application
for all requests. In addition it must be configured to prompt for the Conference Password.
Conference Access Validation - Chairperson Only (Upon Request)
An alternative validation method at the conference level is checking only the chairperson password with the
external database application. All other participants can be checked only with the MCU (if the Conference
IVR Service is configured to prompt for the conference password) or not checked at all (if the Conference
IVR Service is configured to prompt only for the chairperson password).
Conference Access - Chairperson Password validation with external database application
Joining the conference entails the following steps:
●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.
●If the Conference IVR Service is configured to prompt for the Conference password, the participant
is requested to enter the conference password. In this flow, the conference password is not validated
with the external database application, only with the MCU.
If the wrong password is entered, he/she is disconnected from the conference.
●If the correct conference password is entered, the participant is prompted to enter the chairperson
identifier key.
If no identifier is entered, the participant is connected to the conference as a standard participant.
●If the chairperson identifier is entered, the participant is prompted to enter the chairperson password.
●When the participant enters the chairperson password or his/her personal password, it is sent to the
external database application for validation.
1001
1001
1300
On Going
Conference
with this ID?
Network
Numeric ID: 1000
Name: DefaultEQ
9251000
9251000
MCU
IP Endpoint
IP Endpoint
MCU
Gatekeeper - 925
Prefix in
925DefaultEQ
IP Endpoint
New Conference
ID: 1300
Chairperson
Password?
Enters the
conference as
Chairperson
Enters the
conference as
standard
participant