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

• The operator can move participants between ongoing Continuous Presence<br />

conferences.<br />

Operator Conference <strong>Guide</strong>lines<br />

• An Operator conference can only run in Continuous Presence mode.<br />

• Operator conference is defined in the Conference Profile. When enabled in Conference<br />

Profile, High Definition Video Switching option is disabled.<br />

• An Operator conference can only be created by a User with Operator or Administrator<br />

Authorization level.<br />

• Operator conference name is derived from the User Login Name and it cannot be<br />

modified.<br />

• Only one Operator conference per User Login Name can be created.<br />

• When created, the Operator conference must include one and only one participant - the<br />

Operator participant.<br />

• Only a defined dial-out participant can be added to an Operator conference as an<br />

Operator participant<br />

• Once running, the <strong>RMX</strong> user can add new participants or move participants from other<br />

conferences to this conference. The maximum number of participants in an Operator<br />

conference is the same as in standard conferences.<br />

• Special icons are used to indicate an Operator conference in the Ongoing Conferences list<br />

and the operator participant in the Participants list.<br />

• An Operator conference cannot be defined as a Reservation.<br />

• An Operator conference can be saved to a Conference Template. An ongoing Operator<br />

conference can be started from a Conference Template.<br />

• The Operator participant cannot be deleted from the Operator conference or from any<br />

other conference to which she/he was moved to, but it can be disconnected from the<br />

conference.<br />

• When deleting or terminating the Operator conference, the operator participant is<br />

automatically disconnected from the MCU, even if participating in a conference other<br />

than the Operator conference.<br />

• Participants in Telepresence conferences cannot be moved from their conference, but an<br />

operator can join their conference and help them if assistance is required.<br />

• Moving participants from/to an Operator conference follows the same guidelines as<br />

moving participants between conferences. For move guidelines, see "Move <strong>Guide</strong>lines”<br />

on page 9-18.<br />

• When a participant is moved from the Entry Queue to the Operator conference, the option<br />

to move back to the source (Home) conference is disabled as the Entry Queue is not<br />

considered as a source conference.<br />

• The conference chairperson cannot be moved to the Operator conference following the<br />

individual help request if the Auto Terminate When Chairperson Exits option is enabled,<br />

to prevent the conference from automatically ending prematurely. In such a case, the<br />

assistance request is treated by the system as a conference assistance request, and the<br />

operator can join the conference.<br />

9-2 <strong>Polycom</strong>, Inc.

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

Saved successfully!

Ooh no, something went wrong!