Cisco Cisco TelePresence MCU 4510 Release Notes
Limitations
Cisco TelePresence MCU 4.5(1.45) Software Release Notes
Page 9 of 16
Identifier
Description
CSCuc58400
When the MCU shuts down due to high ambient temperature, the diagnostic log correctly reports
this event as a thermal override shutdown. However, the MCU status page incorrectly logs this
restart as a 'user requested shutdown'.
this event as a thermal override shutdown. However, the MCU status page incorrectly logs this
restart as a 'user requested shutdown'.
CSCuo92882
In encrypted calls between a Cisco TelePresence MCU 5300 Series and Cisco Jabber Video for
iPad, no video is shown on the Jabber Video screen. Video in the other direction (i.e. Cisco
Jabber Video for iPad to MCU) and audio in both directions all work as expected. As a
workaround, turn off encryption, either on the MCU or on Jabber Video for iPad.
iPad, no video is shown on the Jabber Video screen. Video in the other direction (i.e. Cisco
Jabber Video for iPad to MCU) and audio in both directions all work as expected. As a
workaround, turn off encryption, either on the MCU or on Jabber Video for iPad.
CSCts46406
If the MCU Ethernet interfaces are configured to have the same IP address and then you attempt
to disable a service on one of the interfaces the service is still allowed, even though the web
interface shows it set to disabled.
to disable a service on one of the interfaces the service is still allowed, even though the web
interface shows it set to disabled.
CSCuo95136
The MCU 8510 may experience an unexpected restart when a participant disconnects from a
conference when it is being previewed by another participant in an auto attendant. As a
workaround, participants can join conferences directly by registering conferences to an H.323
Gatekeeper or SIP Registrar with a Numeric ID. Alternatively, use an API management device to
always dial out from MCU conferences to participants.
conference when it is being previewed by another participant in an auto attendant. As a
workaround, participants can join conferences directly by registering conferences to an H.323
Gatekeeper or SIP Registrar with a Numeric ID. Alternatively, use an API management device to
always dial out from MCU conferences to participants.
CSCuo88631
On the MCU, with port reservation mode enabled, in some situations you cannot edit a
conference to have more ports, even if they are available. As a workaround you can delete and
re-add the conference for which you want to increase the port count.
conference to have more ports, even if they are available. As a workaround you can delete and
re-add the conference for which you want to increase the port count.
CSCum50859 An MCU 5300 Series may experience an unexpected restart with a number of SIP participants
connected and result in a 'broadcast decoder' message.
CSCun15854
An MCU 5300 Series may become unresponsive when connected to a 100Mbps Switch (Cisco
2960 running IOS 12.2(50)SE5) due to a duplex mismatch.
2960 running IOS 12.2(50)SE5) due to a duplex mismatch.
As a workaround you can configure correct duplex settings on both the MCU port and the switch
port to avoid a duplex mismatch.
port to avoid a duplex mismatch.
Limitations
Downgrade without restore causes username inconsistency after
upgrade
upgrade
When you downgrade from MCU 4.5 to MCU 4.3 or earlier, change a username, then upgrade to 4.5 again,
that username's original 4.5 value is retained and is not changed. The reason for this is that the 4.4 software
introduced a new field in configuration.xml to hold a longer username than was previously possible, but the
previous field was also retained (the previous field was retained to ensure you could log in to restore your
configuration). After you downgrade, the new field remains in the configuration file until you overwrite it with
your 4.3 (or earlier) configuration file. If you fail to restore your 4.3 (or earlier) configuration, the upgrade
process does not subsequently recreate the configuration file (which already has the new field) and so the
usernames can become inconsistent.
that username's original 4.5 value is retained and is not changed. The reason for this is that the 4.4 software
introduced a new field in configuration.xml to hold a longer username than was previously possible, but the
previous field was also retained (the previous field was retained to ensure you could log in to restore your
configuration). After you downgrade, the new field remains in the configuration file until you overwrite it with
your 4.3 (or earlier) configuration file. If you fail to restore your 4.3 (or earlier) configuration, the upgrade
process does not subsequently recreate the configuration file (which already has the new field) and so the
usernames can become inconsistent.
To work around this limitation, follow the recommended backup and restore procedures when downgrading or
upgrading. When you downgrade, you must also restore your configuration to ensure that the configuration
file matches the software version.
upgrading. When you downgrade, you must also restore your configuration to ensure that the configuration
file matches the software version.
Google Chrome on Microsoft Windows 7 fails to provide client certificate
Certificate-based authentication and login will fail if the user attempts to access the MCU web interface
using Google Chrome on Microsoft Windows 7. This issue only occurs when the client certificate is
using Google Chrome on Microsoft Windows 7. This issue only occurs when the client certificate is