Conference Access With External Database Authentication; Conference Access Validation - All Participants (Always - Polycom RMX 1500 Administrator's Manual

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:
•
•
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
Figure D-3 Conference Access - Conference Password validation with External Database Application
Joining the conference entails the following steps:
•
•
Polycom, Inc.
For more information, see Figure , "MCU Configuration to Communicate with an External
Database Application" on page D-9.
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.
MCU Prefix in
Gatekeeper - 925
925DefaultEQ
Network
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.
Appendix D-Ad Hoc Conferencing and External Database Authentication
MCU
On Going
Conference
with this ID?
Name: DefaultEQ
Numeric ID: 1000
Correc t
P assword?
New Conference
ID: 1300
D-5