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

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

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

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

D-8<br />

If there is no match (i.e. the conference or personal password are not<br />

defined in the database), the request to access the conference is<br />

rejected and the participant is disconnected from the MCU.<br />

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

chairperson identifier and password, the participant is requested to<br />

enter the chairperson identifier.<br />

— If no identifier is entered, the participant connects as a standard,<br />

undefined participant.<br />

• If the chairperson identifier is entered, the participant is requested to<br />

enter the chairperson password. In this flow, the chairperson<br />

password is not validated with the external database application,<br />

only with the MCU.<br />

— If the correct chairperson password is entered, the participant is<br />

connected to the conference as its chairperson.<br />

— If the wrong password is entered, he/she is disconnected from<br />

the conference.<br />

To enable conference access validation for all participants the following<br />

conferencing components are required:<br />

• The external database must hold the conference password or the<br />

participant personal password/PIN code or the participant’s Alias.<br />

• The Conference IVR Service assigned to the conference (defined in<br />

the Profile) must be configured to authenticate the participant’s right<br />

to access the conference with the external database application for all<br />

requests. In addition it must be configured to prompt for the<br />

Conference Password.

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

Saved successfully!

Ooh no, something went wrong!