Cisco Cisco TelePresence MCU 4510 Release Notes
New features in 4.5
Cisco TelePresence MCU 4.5(1.55) Software Maintenance Release Notes
Page 4 of 17
When upgrading to 4.5 from an earlier software version, the following fields will map accordingly after
upgrade:
upgrade:
n
if SIP registrar usage was set to enabled, the Outbound call configuration is set to Use registrar.
n
if SIP registrar usage was set to enabled and both the SIP registrar domain and SIP proxy address
filled in, the SIP registrar field is used to populate the Outbound domain and the the SIP proxy address
is used to populate the Outbound address.
filled in, the SIP registrar field is used to populate the Outbound domain and the the SIP proxy address
is used to populate the Outbound address.
n
if SIP registrar usage was set to enabled with only the SIP registrar domain filled in, the SIP registrar
domain is used to populate both the Outbound domain and outbound address.
domain is used to populate both the Outbound domain and outbound address.
n
if SIP registrar usage was set to disabled and the SIP proxy address filled in, the Outbound call
configuration is set to Use trunk.
configuration is set to Use trunk.
n
if SIP registrar usage was set to disabled and the SIP proxy address filled in, the SIP proxy address is
used to populate the Outbound address.
used to populate the Outbound address.
n
if SIP registrar usage was set to disabled and a blank SIP proxy address, the Outbound call
configuration is set to Call direct.
configuration is set to Call direct.
Note: When downgrading, any changes made post upgrade will be retained.
Disconnection of inactive calls
The MCU can now respond to inactive calls by disconnecting them. If media is expected from an endpoint
but is not received for 30 to 45 seconds, then the MCU will disconnect the call.
but is not received for 30 to 45 seconds, then the MCU will disconnect the call.
When media has unexpectedly stopped in this way, the MCU will not show a frozen frame from that stream;
it will show no video until it disconnects the call.
it will show no video until it disconnects the call.
This feature applies to any calls using H.323 or SIP call protocols. If auto-reconnect is enabled for the call,
the MCU retries the call after disconnecting it.
the MCU retries the call after disconnecting it.
The MCU will not disconnect a call if the endpoint has signaled that it is on hold or if the media channels are
muted.
muted.
TMMBR support
The MCU now supports flow control for SIP calls using RFC 5104 Temporary Maximum Media Stream Bit
Rate Request (TMMBR). Flow control using TMMBR is supported for both incoming and outgoing main video
and content channel.
Rate Request (TMMBR). Flow control using TMMBR is supported for both incoming and outgoing main video
and content channel.
Cisco Call Home support
This release enables the MCU to send diagnostic logs to the Cisco Call Home service. This feature can be
configured to enable logs to be submitted automatically (disabled by default) or logs can be submitted
manually.
configured to enable logs to be submitted automatically (disabled by default) or logs can be submitted
manually.
Note: The MCU currently only supports anonymous reporting.
Logs are only sent via encrypted HTTPS connections. This requires the MCU to have an encryption feature
key. Without this, you can view the Call Home web settings but the functionality will not be available.
key. Without this, you can view the Call Home web settings but the functionality will not be available.
Call Home messages are sent to
https://tools.cisco.com/its/service/oddce/services/DDCEService
https://tools.cisco.com/its/service/oddce/services/DDCEService
. At that point, you