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 />

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

participant.<br />

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

chairperson password. In this flow, the chairperson password is not validated with the<br />

external database application, only with the MCU.<br />

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

conference as its chairperson.<br />

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

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

components are required:<br />

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

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

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

configured to authenticate the participant’s right to access the conference with the<br />

external database application for all requests. In addition it must be configured to<br />

prompt for the Conference Password.<br />

Conference Access Validation - Chairperson Only (Upon Request)<br />

An alternative validation method at the conference level is checking only the chairperson<br />

password with the external database application. All other participants can be checked only<br />

with the MCU (if the Conference IVR Service is configured to prompt for the conference<br />

password) or not checked at all (if the Conference IVR Service is configured to prompt only<br />

for the chairperson password).<br />

IP Endpoint<br />

IP Endpoint<br />

IP Endpoint<br />

9251000<br />

925DefaultEQ<br />

9251000<br />

MCU Prefix in<br />

Gatekeeper - 925<br />

Network<br />

MCU<br />

Figure D-4 Conference Access - Chairperson Password validation with external database application<br />

Joining the conference entails the following steps:<br />

• When the conference is started (either in the Ad Hoc flow or in the standard method),<br />

all participants connecting to the conference are moved to the conference IVR queue<br />

where they are prompted for the conference password.<br />

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

participant is requested to enter the conference password. In this flow, the conference<br />

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

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

D-6 <strong>Polycom</strong>, Inc.<br />

1001<br />

1001<br />

1300<br />

Name: DefaultEQ<br />

Numeric ID: 1000<br />

On Going<br />

Conference<br />

with this ID?<br />

Chairperson<br />

Pa sswo rd ?<br />

Enters the<br />

conference as<br />

Chairperson<br />

Enters the<br />

conference as<br />

stand ard<br />

partic ipant<br />

New Conference<br />

ID: 1300

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

Saved successfully!

Ooh no, something went wrong!