Chapter 4-Additional Conferencing Information
Polycom, Inc. 4-27
2Optional. Add a participant to the list of participants to be Auto Scanned:
—Click on the participant’s name in the All Participants list and then click the Add
button to move the participant to the Scanning Order pane.
3Optional. Delete a participant from the list of participants to be Auto Scanned:
—Click on a participant’s name in the Scanning Order list and then click the Delete
button to move the participant back to the All Participants pane.
4Optional. Add all participants to the list of participants to be Auto Scanned by clicking
the Add All button.
5Optional. Delete all participant from the list of participants to be Auto Scanned by
clicking the Delete All button.
6Optional. Move the participant up in the Scanning Order by clicking the Up button.
7Optional. Move the participant down in the Scanning Order by clicking the Down
button.
8Click the Apply button to confirm and keep the Conference Properties dialog box open, or
click the OK the button to confirm and return to the Collaboration Server Web Client Main
Screen.
Media Encryption
Encryption is available at the conference and participant levels, based on AES 128
(Advanced Encryption Standard) and is fully H.233/H.234 compliant and the Encryption
Key exchange DH 1024-bit (Diffie-Hellman) standards.

Media Encryption Guidelines

• Encryption is not available in all countries and it is enabled in the MCU license. Contact
Polycom Support to enable it.
• Endpoints must support both AES 128 encryption and DH 1024 key exchange
standards which are compliant with H.235 (H.323) to encrypt and to join an encrypted
conference.
• The encryption mode of the endpoints is not automatically recognized, therefore the
encryption mode must be set for the conference or the participants (when defined).
• Conference level encryption must be set in the Profile, and cannot be changed once the
conference is running.
• If an endpoint connected to an encrypted conference stops encrypting its media, it is
disconnected from the conference.
• In Cascaded conferences, the link between the cascaded conferences must be encrypted
in order to encrypt the conferences.
• The recording link can be encrypted when recording from an encrypted conference to
the RSS that is set to encryption. For more information, see "Recording Link Encryption”
on page13-7.
• Encryption of SIP Media is supported using SRTP (Secured Real-time Transport Protocol)
and the AES key exchange method.
• Encryption of SIP Media requires the encryption of SIP signaling - TLS Transport Layer
must be used.
• Encryption of SIP Media is supported in conferences as follows: