Release Notes

Limitations
Cisco TelePresence MCU 4.4 (3.42) Release Notes Page 9 of 24
Limitations
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.
Transferring a persistent call can result in both endpoints joining the
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.
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).
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.
Issues when removing the CompactFlash™ during operation
Removing the CompactFlash card while the MCU is in operation has been known to cause a restart.
Windows Media Player
Streaming a conference with Windows Media Player in multiple windows or tabs on the same browser will
crash the browser. This is a known issue with Windows Media Player. If you need to stream more than one
conference simultaneously, use a different player such as QuickTime or Real Player.
In addition, Windows Media Player 11 can display streams incorrectly when used as an embedded player
with browsers other than Internet Explorer. This is a known incompatibility. In some cases, setting the video
size of the main streaming video window (the Video size field in the Streaming page) to Large will correct the
problem. To work around this issue, you can use QuickTime or RealPlayer instead of WMP, or use Internet
Explorer instead of your normal browser.
The MCU does not support 64-bit versions of Windows Media Player. To work around this limitation, use a
32-bit version of Windows Media Player.
Streaming to QuickTime 7 causes problems with some browsers
Streaming to an embedded QuickTime player using the QuickTime 7.0 plus later option for the Player format
on the MCU can cause certain browsers to crash or remain in the 'negotiating' state indefinitely. Affected