Ad Hoc Conferencing With Authentication; Entry Queue Level - Conference Initiation Validation With An External Database Application - Polycom RMX 1500 Administrator's Manual

Ad Hoc Conferencing with Authentication

The MCU can work with an external database application to validate the participant's right
to start a new conference. The external database contains a list of participants, with their
assigned parameters. The conference ID entered by the participant is compared against the
database. If the system finds a match, the participant is granted the permission to start a new
conference.
To work with an external database application to validate the participant's right to start a
new conference, the Entry Queue IVR Service must be configured to use the external
database application for authentication. In the external database application, you must
define all participants (users) with rights to start a new conference using Ad Hoc
conferencing. For each user defined in the database, you enter the conference ID,
Conference Password (optional) and Chairperson Password (when applicable), billing code,
Conference general information (corresponding to the User Defined 1 field in the Profile
properties) and user's PIN code. The same user definitions can be used for conference access
authentication, that is, to determine who can join the conference as a participant and who as
a chairperson.
Entry Queue Level - Conference Initiation Validation with an External Database
Application
Starting a new conference with external database application validation entails the
following steps:
IP Endpoint
IP Endpoint
IP Endpoint
Figure D-2 Conference Initiation Validation with External Database Application
1
2
3
Polycom, Inc.
MCU Prefix in
Gatekeeper - 925
925DefaultEQ
Network
The participant dials in to an Ad Hoc-enabled Entry Queue.
The participant is requested to enter the Conference ID.
The participant enters the conference ID via his/her endpoint remote control using
DTMF codes. If there is an ongoing conference with this Conference ID, the participant
is moved to that conference where another authentication process can occur, depending
on the IVR Service configuration.
Appendix D-Ad Hoc Conferencing and External Database Authentication
MCU
On Going
Conference
with this ID?
Name: DefaultEQ
Numeric ID: 1000
New Conference
ID: 1300
D-3