Cisco Cisco TelePresence MCU 4510 Release Notes
Cisco ClearPath Support
The MCU now supports ClearPath to improve media resilience within lossy networks.This feature is always enabled
on the MCU MSE 8510 and MCU 5300 Series and does not require any configuration. The MCU implementation of
ClearPath includes FEC (Forward Error Correction) and two other techniques which are only used inside the video
streams, namely LTRF (Long Term Reference Frames) and incoming GDR (Gradual Decoder Refreshes).
on the MCU MSE 8510 and MCU 5300 Series and does not require any configuration. The MCU implementation of
ClearPath includes FEC (Forward Error Correction) and two other techniques which are only used inside the video
streams, namely LTRF (Long Term Reference Frames) and incoming GDR (Gradual Decoder Refreshes).
ClearPath will be negotiated with any endpoints that support ClearPath. The MCU's web interface and API will report
statistics and capabilities on the media resilience techniques used in those calls.
statistics and capabilities on the media resilience techniques used in those calls.
The following endpoints currently support ClearPath in their most recent software releases:
■
Cisco Jabber Video for TelePresence
■
Cisco Jabber
■
Cisco TelePresence System T Series
■
Cisco TelePresence System Quick Set Series (C20, SX20)
■
Cisco TelePresence MX Series (MX200, MX300)
■
Cisco TelePresence System EX Series (EX60, EX90)
■
Cisco TelePresence Profile Series (Profile 42", 52", 52" Dual, 65", and 65" Dual)
■
Csco TelePresence Integrator C Series (Codecs C40, C60, and C90)
FEC (Forward Error Correction)
The MCU applies FEC to enable media packet recovery on outgoing video and audio streams. It can also process
incoming streams containing FEC packets and will try to recover media packets lost from these streams.
incoming streams containing FEC packets and will try to recover media packets lost from these streams.
The technique involves interleaving the original stream with additional, corrective packets, so that if media packets
are lost they can potentially be recovered by the recipient without resorting to retransmission of the originals.
are lost they can potentially be recovered by the recipient without resorting to retransmission of the originals.
Applying FEC consumes additional bandwidth, so a call negotiated at a certain maximum bandwidth will use less
bandwidth for the media streams because it needs overhead for the FEC packets. The bandwidth overhead can range
from 0% - which means that FEC packets are not used - to 100% when every media packet is protected by a FEC
packet. A 50% overhead means that one corrective packet is inserted to protect every two media packets.
bandwidth for the media streams because it needs overhead for the FEC packets. The bandwidth overhead can range
from 0% - which means that FEC packets are not used - to 100% when every media packet is protected by a FEC
packet. A 50% overhead means that one corrective packet is inserted to protect every two media packets.
The MCU only starts using FEC when it observes packet loss and then dynamically adjusts the overhead based on the
monitored packet loss.
monitored packet loss.
Separate Content Channel Support for Encrypted SIP Participants
This release introduces support for sending content in a separate channel from main video for encrypted SIP
participants. Note that this functionality is already supported for H.323 participants and unencrypted SIP participants.
participants. Note that this functionality is already supported for H.323 participants and unencrypted SIP participants.
Support is limited to transcoded content and transcoded content channel in hybrid mode only; passthrough content is
not supported to encrypted SIP participants.
not supported to encrypted SIP participants.
This new feature is supported on all MCU platforms except MCU 4200 Series and MCU MSE 8420.
SIP Configuration Improvements
This release allows you to configure a box-wide default SIP domain for proxy/trunk calls. Previously this was only
possible for registrar calls. For example, a typical use case would be an MCU trunked to a Cisco Unified
Communications Manager (Unified CM), where you want to dial Unified CM registered endpoint numbers from the
MCU and need a domain appended to the number before the call is placed over the Unified CM trunk.
possible for registrar calls. For example, a typical use case would be an MCU trunked to a Cisco Unified
Communications Manager (Unified CM), where you want to dial Unified CM registered endpoint numbers from the
MCU and need a domain appended to the number before the call is placed over the Unified CM trunk.
This feature has introduced some new settings on the SIP settings page. The following new settings can now be
configured on a boxwide basis via the SIP settings page:
configured on a boxwide basis via the SIP settings page:
3
Cisco TelePresence MCU Series Software Maintenance Release Notes