Polycom RMX 1500 Administrator's Manual page 700

Polycom RMX 1500/2000/4000 Administrator's Guide
4
5
6
7
To enable this workflow, the following components must be defined in the system:
•
•
•
•
•
•
D-4
If there is no ongoing conference with that Conference ID, the MCU verifies the
Conference ID with the database application that compares it against its database. If the
database application finds a match, the external database application sends a response
back to the MCU, granting the participant the right to start a new ongoing conference.
If this Conference ID is not registered in the database, the conference cannot be started
and this participant is disconnected from the Entry Queue.
The external database contains a list of participants (users), with their assigned
parameters. Once a participant is identified in the database (according to the conference
ID), his/her parameters (as defined in the database) can be sent to the MCU in the same
response granting the participant the right to start a new ongoing conference. These
parameters are:
— Conference Name
— Conference Billing code
— Conference Password
— Chairperson Password
— Conference Information, such as the contact person name. These fields correspond
to Info 1, 2 and 3 fields in the Conference Properties - Information dialog box.
— Maximum number of participants allowed for the conference
— Conference Owner
These parameters can also be defined in the conference Profile. In such a case,
parameters sent from the database overwrite the parameters defined in the Profile. If
these parameters are not sent from the external database to the MCU, they will be taken
from the Profile.
A new conference is started based on the Profile assigned to the Entry Queue.
The participant is moved to the conference.
If no password request is configured in the Conference IVR Service assigned to the
conference, the participant that initiated the conference is directly connected to the
conference, as its chairperson.
If the Conference IVR Service assigned to the conference is configured to prompt for the
conference password and chairperson password, without external database
authentication, the participant has to enter these passwords in order to join the
conference.
A Conference IVR Service with the appropriate prompts. If conference access is also
validated with the external database application it must be configured to access the
external database for authentication.
An Entry Queue IVR Service configured with the appropriate audio prompts
requesting the Conference ID and configured to access the external database for
authentication.
Create a Profile with the appropriate conference parameters and the appropriate
Conference IVR Service assigned to it.
An Ad Hoc-enabled Entry Queue with the appropriate Entry Queue IVR Service and
Conference Profile assigned to it.
An external database application with a database containing Conference IDs associated
with participants and their relevant properties.
Define the flags required to access the external database in System Configuration.
Polycom, Inc.