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

Create successful ePaper yourself

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

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

4 The MCU checks whether a conference with the same Conference ID is running on the<br />

MCU. If there is such a conference, the participant is moved to that conference. If there<br />

is no ongoing conference with that Conference ID, the system creates a new conference,<br />

based on the Profile assigned to the Entry Queue, and connects this participant as the<br />

conference chairperson.<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 />

Name: DefaultEQ<br />

Numeric ID: 1000<br />

Figure D-1 Ad Hoc Conference Initiation without Authentication<br />

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

• An Entry Queue IVR Service with the appropriate audio file requesting the Conference<br />

ID<br />

• An Ad Hoc-enabled Entry Queue with an assigned Profile<br />

Ad Hoc Conferencing with Authentication<br />

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

to start a new conference. The external database contains a list of participants, with their<br />

assigned parameters. The conference ID entered by the participant is compared against the<br />

database. If the system finds a match, the participant is granted the permission to start a new<br />

conference.<br />

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

new conference, the Entry Queue IVR Service must be configured to use the external<br />

database application for authentication. In the external database application, you must<br />

define all participants (users) with rights to start a new conference using Ad Hoc<br />

conferencing. For each user defined in the database, you enter the conference ID,<br />

Conference Password (optional) and Chairperson Password (when applicable), billing code,<br />

Conference general information (corresponding to the User Defined 1 field in the Profile<br />

properties) and user’s PIN code. The same user definitions can be used for conference access<br />

authentication, that is, to determine who can join the conference as a participant and who as<br />

a chairperson.<br />

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

MCU<br />

1001<br />

1001<br />

1300<br />

On Going<br />

Conference<br />

with this ID?<br />

Maple_Room<br />

Conference ID: 1001<br />

New Conference<br />

ID: 1300

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

Saved successfully!

Ooh no, something went wrong!