Cisco Cisco TelePresence MCU 4510 Release Notes
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
New features in 4.5
Cisco TelePresence MCU 4.5(1.55) Software Maintenance Release Notes
Page 3 of 17
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.
process 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.
packets 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.
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.
The MCU only starts using FEC when it observes packet loss and then dynamically adjusts the overhead
based on the monitored packet loss.
based on the 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.
content is 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.
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.
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
be configured on a boxwide basis via the
SIP settings
page:
n
Outbound call configuration — this setting replaces the SIP registrar usage field. The drop-down menu
now has three options:
now has three options:
l
Use registrar enables SIP registration and routes outbound SIP calls via the registrar.
l
Use trunk disables SIP registration and tears down existing registrations. Routes outbound calls to the
trunk destination, e.g. Cisco VCS or Unified CM.
trunk destination, e.g. Cisco VCS or Unified CM.
l
Call direct disables SIP registration and tears down existing registrations. Outbound SIP calls go
directly (not via registrar or trunk).
directly (not via registrar or trunk).
n
Outbound address – this setting replaces the SIP proxy address field. This field is the hostname or
IP address of the SIP registrar or trunk destination.
IP address of the SIP registrar or trunk destination.
n
Outbound domain – this setting replaces the SIP registrar domain field. This field is the domain of the
SIP registrar or trunk destination.
SIP registrar or trunk destination.