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

included in SRTP packets sent by the <strong>RMX</strong>. This System Flag should not be set to<br />

NO when HDX endpoints, Microsoft Office Communicator and Lync Clients. For<br />

more information, see "System Configuration Flags” on page 21-1.<br />

Mixing Encrypted and Non-encrypted Endpoints in one Conference<br />

Mixing encrypted and non-encrypted endpoints in one conference is possible, based on the<br />

Encryption option “Encrypt When Possible” in the Conference Profile - Advance dialog box.<br />

The behavior is different for H.323/SIP and ISDN participants.<br />

In versions prior to version <strong>7.6.1</strong>, this behavior is based on the setting of the system flag<br />

ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF.<br />

The option “Encrypt When Possible” enables the negotiation between the MCU and the<br />

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

encryption is the preferred setting. Defined participants that cannot connect encrypted are<br />

connected non-encrypted, with the exception of dial-out SIP participants.<br />

• When the conference encryption is set to "Encrypt when possible", dial out SIP participants<br />

whose encryption is set to AUTO can only connect with encryption, otherwise they are<br />

disconnected from the conference.<br />

• In CISCO SIP environments, dial in endpoints that are registered to CUCM can only connect as<br />

non-encrypted when the conference encryption is set to "Encrypt when possible" as the CUCM<br />

server sends the Invite command without SDP.<br />

The same system behavior can be applied to undefined participants, depending on the<br />

setting of the System Flag<br />

FORCE_ENCRYPTION_FOR_UNDEFINED_PARTICIPANT_IN_WHEN_AVAILABLE_MODE:<br />

• When set to NO and the conference encryption in the Profile is set to “Encrypt When<br />

Possible”, both Encrypted and Non-encrypted undefined participants can connect to the<br />

same conferences, where encryption is the preferred setting.<br />

• When set to YES (default), Undefined participants must connect encrypted, otherwise<br />

they are disconnected.<br />

For defined participants, connection to the conference is decided according to the encryption<br />

settings in the conference Profile, the Defined Participant’s encryption settings.<br />

For undefined participants, connection to the conference is decided according to the<br />

encryption settings in the conference Profile, the System Flag setting and the connecting<br />

endpoint’s Media Encryption capabilities.<br />

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

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

Saved successfully!

Ooh no, something went wrong!