19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

— Conference Information, such as the contact person name. These fields correspond<br />

to Info 1, 2 and 3 fields in the Conference Properties - Information dialog box.<br />

— Maximum number of participants allowed for the conference<br />

— Conference Owner<br />

These parameters can also be defined in the conference Profile. In such a case,<br />

parameters sent from the database overwrite the parameters defined in the Profile. If<br />

these parameters are not sent from the external database to the MCU, they will be taken<br />

from the Profile.<br />

6 A new conference is started based on the Profile assigned to the Entry Queue.<br />

7 The participant is moved to the conference.<br />

If no password request is configured in the Conference IVR Service assigned to the<br />

conference, the participant that initiated the conference is directly connected to the<br />

conference, as its chairperson.<br />

If the Conference IVR Service assigned to the conference is configured to prompt for the<br />

conference password and chairperson password, without external database<br />

authentication, the participant has to enter these passwords in order to join the<br />

conference.<br />

To enable this workflow, the following components must be defined in the system:<br />

• A Conference IVR Service with the appropriate prompts. If conference access is also<br />

validated with the external database application it must be configured to access the<br />

external database for authentication.<br />

• An Entry Queue IVR Service configured with the appropriate audio prompts<br />

requesting the Conference ID and configured to access the external database for<br />

authentication.<br />

• Create a Profile with the appropriate conference parameters and the appropriate<br />

Conference IVR Service assigned to it.<br />

• An Ad Hoc-enabled Entry Queue with the appropriate Entry Queue IVR Service and<br />

Conference Profile assigned to it.<br />

• An external database application with a database containing Conference IDs associated<br />

with participants and their relevant properties.<br />

• Define the flags required to access the external database in System Configuration.<br />

For more information, see Figure , “MCU Configuration to Communicate with an External<br />

Database Application” on page D-9.<br />

Conference Access with External Database Authentication<br />

The MCU can work with an external database application to validate the participant’s right<br />

to join an existing conference. The external database contains a list of participants, with their<br />

assigned parameters. The conference password or chairperson password entered by the<br />

participant is compared against the database. If the system finds a match, the participant is<br />

granted the permission to access the conference.<br />

To work with an external database application to validate the participant’s right to join the<br />

conference, the Conference IVR Service must be configured to use the external database<br />

application for authentication.<br />

D-4 <strong>Polycom</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!