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.

Chapter 3-Additional Conferencing Information<br />

— Encrypt All - Encryption is enabled for the conference and all conference<br />

participants must be encrypted.<br />

— No Encryption - Encryption is disabled for the conference.<br />

— Encrypt when possible - enables the negotiation between the MCU and the<br />

endpoints and let the MCU connect the participants according to their capabilities,<br />

where encryption is the preferred setting. For connection guidelines see "Mixing<br />

Encrypted and Non-encrypted Endpoints in one Conference” on page 3-34.<br />

For more information about recording encrypted conferences, see "Recording Link<br />

Encryption” on page 13-6.<br />

Enabling Encryption at the Participant Level<br />

You can select the encryption mode for each of the defined participants. Encryption options<br />

are affected by the settings of the flag in the system configuration. Undefined participants<br />

are connected with the Participant Encryption option set to Auto, inheriting the conference/<br />

Entry Queue encryption setting.<br />

To enable encryption at the participant level:<br />

>> In the Participant Properties – Advanced dialog box, in the Encryption list, select one of the<br />

following options: Auto, On, or Off.<br />

— Auto - The participant inherits the conference/Entry Queue encryption setting.<br />

The participant connects as encrypted only if the conference is defined as<br />

encrypted.<br />

— Yes - The participant joins the conference/Entry Queue as encrypted.<br />

— No - The participant joins the conference/Entry Queue as non-encrypted.<br />

<strong>Polycom</strong>, Inc. 3-39

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

Saved successfully!

Ooh no, something went wrong!