Polycom 1500/1800/2000/4000 Manual De Usuario
Implementing Media Encryption for Secured Conferencing
Polycom®, Inc.
158
Connection to the Entry Queue
An undefined participant connecting to an Entry Queue inherits the encryption characteristics of the Entry
Queue as defined in the Entry Queue’s profile.
Queue as defined in the Entry Queue’s profile.
Participants can be moved from the Entry Queue and the destination conference if both conferencing
entities have the same Profile settings, i.e. from SVC Only Entry Queue to SVC Only conference and from
mixed CP and SVC Entry Queue to a mixed CP and SVC conference, etc.
entities have the same Profile settings, i.e. from SVC Only Entry Queue to SVC Only conference and from
mixed CP and SVC Entry Queue to a mixed CP and SVC conference, etc.
The following table summarizes the connection possibilities for a participant that is to be moved from an
Entry Queue to a destination conference for each of the conference Profile and Entry Queue encryption
options.
Entry Queue to a destination conference for each of the conference Profile and Entry Queue encryption
options.
Moving from the Entry Queue to Conferences or Between Conferences
Participants can be moved from the Entry Queue and the destination conference if both conferencing
entities have the same Profile settings, i.e. from SVC Only Entry Queue to SVC Only conference and from
mixed CP and SVC Entry Queue to a mixed CP and SVC conference, etc.
entities have the same Profile settings, i.e. from SVC Only Entry Queue to SVC Only conference and from
mixed CP and SVC Entry Queue to a mixed CP and SVC conference, etc.
When moving participants from the Entry Queue to the destination conference, or when the Collaboration
Server user moves AVC participants from one conference to another (SVC participants cannot be moved
between conferences), the connection rules are similar and they are summarized in the table below:
Server user moves AVC participants from one conference to another (SVC participants cannot be moved
between conferences), the connection rules are similar and they are summarized in the table below:
Connection of Undefined Participants to the Entry Queue Based on Encryption Settings
Entry Queue Encryption
Setting
Setting
Undefined Participant Connection to the Entry Queue
*Flag = No
*Flag = YES
No Encryption
Connected, non-encrypted
(Encryption is not declared by the
Collaboration Server, therefore endpoint
does not use encryption)
(Encryption is not declared by the
Collaboration Server, therefore endpoint
does not use encryption)
Connected, non-encrypted
(Encryption is not declared by the
Collaboration Server, therefore endpoint
does not use encryption)
(Encryption is not declared by the
Collaboration Server, therefore endpoint
does not use encryption)
Encrypt All
Connected only if encrypted.
Non-encrypted endpoints are
disconnected
Non-encrypted endpoints are
disconnected
Connected only if encrypted.
Non-encrypted endpoints are
disconnected
Non-encrypted endpoints are
disconnected
Encrypt When Possible
Connected encrypted - Endpoints with
encryption capabilities.
Connected non-encrypted - endpoints
without encryption capabilities
encryption capabilities.
Connected non-encrypted - endpoints
without encryption capabilities
Connected only if encrypted.
Non-encrypted endpoints are
disconnected.
Non-encrypted endpoints are
disconnected.
* Flag = FORCE_ENCRYPTION_FOR_UNDEFINED_PARTICIPANT_IN_WHEN_AVAILABLE_MODE
Moving participants from entry queue to conference / between conferences depending on encryption settings
Destination
Conference
Encryption Setting
Conference
Encryption Setting
Current Participant Encryption Status
Encrypted
Non-Encrypted
*Flag = NO
*Flag = YES
*Flag = NO
*Flag = YES
No Encryption
Move succeeds, connected encrypted
Move succeeds, connected
non-encrypted
non-encrypted