Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Configuring the MCU
Cisco TelePresence MCU 4.3 Product administration guide
Page 164 of 242
nHD
video
ports
video
ports
Up to w360p at 30fps. MCU MSE 8510 only.
Dedicated
streaming
and
content
ports
streaming
and
content
ports
The number of dedicated streaming and content ports available. Where streaming and content
ports are provided, when streaming and content ports are used up, video ports will not be allocated
to streaming viewers or providers of content. Where there are no streaming and content ports,
conferences with streaming viewers and conferences with content will use available video ports.
ports are provided, when streaming and content ports are used up, video ports will not be allocated
to streaming viewers or providers of content. Where there are no streaming and content ports,
conferences with streaming viewers and conferences with content will use available video ports.
Additional
audio
ports
audio
ports
The number of audio-only ports available. Each audio port can be used by one voice-only
participant in a video conference. When audio-only ports are unavailable, voice-only participants
will use available video ports.
participant in a video conference. When audio-only ports are unavailable, voice-only participants
will use available video ports.
On HD-capable MCUs, the additional audio ports value is 0 when the Media port mode is either
SD or nHD.
SD or nHD.
Configuring encryption settings
You can configure the MCU to encrypt connections to and from H.323 and SIP endpoints.
The encryption technology that the MCU uses for encryption to and from H.323 endpoints is Advanced
Encryption Standard (AES).
Encryption Standard (AES).
The encryption technology that the MCU uses for encryption to and from SIP endpoints is Secure Real-time
Transport Protocol (SRTP).
Transport Protocol (SRTP).
To use encryption, you must have the Encryption feature key present on the MCU. For information about
installing feature keys, refer to
installing feature keys, refer to
. To access encryption settings, go to
Settings > Encryption
.
Encryption is used when both devices in a call agree to use encryption; by default if one of the devices
cannot use encryption (for example if a SIP endpoint does not support SRTP), the MCU will allow the call to
be unencrypted, unless the conference configuration dictates that encryption is Required. Where encryption
is required, calls that cannot used encryption will not be allowed.
cannot use encryption (for example if a SIP endpoint does not support SRTP), the MCU will allow the call to
be unencrypted, unless the conference configuration dictates that encryption is Required. Where encryption
is required, calls that cannot used encryption will not be allowed.
When encryption is in use to and from H.323 endpoints, the MCU will encrypt audio, video, and content
media. It does not encrypt control or authentication information.
media. It does not encrypt control or authentication information.
When encryption is in use to and from SIP endpoints, the MCU will encrypt audio and video media using
SRTP. Control or authentication information can also be encrypted using TLS. For more information refer to
SRTP. Control or authentication information can also be encrypted using TLS. For more information refer to
, below.
You can:
n
configure the MCU to advertise its ability to encrypt connections, such that it will use encryption if an
H.323 endpoint can use AES encryption.
H.323 endpoint can use AES encryption.
n
configure the MCU to advertise its ability to encrypt connections, such that it will use encryption if a SIP
endpoint can use SRTP encryption.
endpoint can use SRTP encryption.
n
configure the MCU so that the default encryption option for new conferences is either Optional or Required.
Be aware that anyone creating a new conference will be able to set the encryption setting for the
conference to either Optional or Required.
Be aware that anyone creating a new conference will be able to set the encryption setting for the
conference to either Optional or Required.
n
force new ad hoc conferences to use encryption (by correctly configuring the ad hoc conference template,
see
see
).