Cisco Cisco TelePresence MCU 4510 Release Notes
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
■
Outbound call configuration — this setting replaces the SIP registrar usage field. The drop-down menu now
has three options:
has three options:
—
Use registrar enables SIP registration and routes outbound SIP calls via the registrar.
—
Use trunk disables SIP registration and tears down existing registrations. Routes outbound calls to the trunk
destination, e.g. Cisco VCS or Unified CM.
destination, e.g. Cisco VCS or Unified CM.
—
Call direct disables SIP registration and tears down existing registrations. Outbound SIP calls go directly
(not via registrar or trunk).
(not via registrar or trunk).
■
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.
■
Outbound domain – this setting replaces the SIP registrar domain field. This field is the domain of the SIP
registrar or trunk destination.
registrar or trunk destination.
When upgrading to 4.5 from an earlier software version, the following fields will map accordingly after upgrade:
■
if SIP registrar usage was set to enabled, the Outbound call configuration is set to Use registrar.
■
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.
the SIP registrar field is used to populate the Outbound domain and the the SIP proxy address is used to
populate the Outbound address.
■
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.
■
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.
■
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.
to populate the Outbound address.
■
if SIP registrar usage was set to disabled and a blank SIP proxy address, the Outbound call configuration
is set to Call direct.
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.
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.
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.
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.
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.
(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.
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.
Without this, you can view the Call Home web settings but the functionality will not be available.
4
Cisco TelePresence MCU Series Software Maintenance Release Notes