RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

Appendix D-Ad Hoc Conferencing and External Database 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.
IP Endpoint
IP Endpoint
IP Endpoint
9251000
925DefaultEQ
9251000
MCU Prefix in
Gatekeeper - 925
Network
MCU
Figure D-3 Conference Access - Conference 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.
• When the participant enters the conference password or his/her personal password, it
is sent to the external database application for validation.
• 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.
• If the Conference IVR Service is configured to prompt for the chairperson identifier and
password, the participant is requested to enter the chairperson identifier.
Polycom, Inc. D-5
1001
1001
1300
Name: DefaultEQ
Numeric ID: 1000
On Going
Conference
with this ID?
Correc t
Pa sswo rd ?
New Conference
ID: 1300