Cisco Cisco TelePresence MCU 4510 Release Notes
Limitations
Cisco TelePresence MCU 4.4(3.57) Maintenance Release Notes
Page 11 of 28
Limitations
Downgrade without restore causes username inconsistency after
upgrade
upgrade
When you downgrade from MCU 4.4 to MCU 4.3 or earlier, change a username, then upgrade to 4.4 again,
that username's original 4.4 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.4 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
generated by the Microsoft Certification Authority. To work around the issue, use a different browser,
operating system, or certification authority.
using Google Chrome on Microsoft Windows 7. This issue only occurs when the client certificate is
generated by the Microsoft Certification Authority. To work around the issue, use a different browser,
operating system, or certification authority.
Transferring a persistent call can result in both endpoints joining the
conference
conference
When you transfer a persistent call from the active endpoint to another endpoint, the MCU redials the original
endpoint, maintaining the persistence on that call, and also joins the target endpoint to the conference without
call persistence. The transfer use case is not officially supported in this version.
endpoint, maintaining the persistence on that call, and also joins the target endpoint to the conference without
call persistence. The transfer use case is not officially supported in this version.
Firefox 14
Firefox 14 is not supported for use with the MCU. We strongly recommend that you refrain from using Firefox
14 to access the MCU web interface. This version of the browser causes an issue that was not present in
previous browser versions and which has been fixed in the following version (Firefox 15).
14 to access the MCU web interface. This version of the browser causes an issue that was not present in
previous browser versions and which has been fixed in the following version (Firefox 15).
Dynamic IP address assignment
This limitation applies to MCU 4200 Series and MCU 4500 Series only. When you configure dynamic
IP address assignment for IPv4 or IPv6 on one of the unit's Ethernet ports, the other IP interface on that port
temporarily loses network connectivity.
IP address assignment for IPv4 or IPv6 on one of the unit's Ethernet ports, the other IP interface on that port
temporarily loses network connectivity.
Issues when removing the CompactFlash™ during operation
Removing the CompactFlash card while the MCU is in operation has been known to cause a restart.