19.08.2013 Views

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix D-Ad Hoc Conferencing and External Database Authentication<br />

D-6<br />

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

authentication.<br />

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

prompts requesting the Conference ID and configured to access the<br />

external database for authentication.<br />

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

appropriate Conference IVR Service assigned to it.<br />

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

IVR Service and Conference Profile assigned to it.<br />

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

Conference IDs associated with participants and their relevant<br />

properties.<br />

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

Configuration. For more information, see "$paratext>” on page D-13.<br />

Conference Access with External Database<br />

Authentication<br />

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

participant’s right to join an existing conference. The external database<br />

contains a list of participants, with their assigned parameters. The<br />

conference password or chairperson password entered by the participant<br />

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

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

To work with an external database application to validate the<br />

participant’s right to join the conference, the Conference IVR Service must<br />

be configured to use the external database application for authentication.<br />

Conference access authentication can be performed as:<br />

• Part of the Ad Hoc conferencing flow where the participants must be<br />

authorized before they can enter the conference created in the Ad<br />

Hoc flow<br />

• Independent of Ad Hoc conferencing where conference access is<br />

validated for all conferences running on the MCU regardless of the<br />

method in which the conference was started.<br />

Conference access authentication can be implemented for all participants<br />

joining the conference or for chairpersons only.

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

Saved successfully!

Ooh no, something went wrong!