Cisco Cisco TelePresence MCU 4510 Release Notes
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 browsers include:
IE6; Firefox 1.5 (Mac and PC); Safari 2.0.3 and earlier, and Camino. IE7 and Safari 2.0.4 do not appear to be affected
by this. Using the QuickTime 6.5 plus later option for the Player format on the MCU will allow streaming to QuickTime
using any browser that supports a QuickTime plug-in.
MCU can cause certain browsers to crash or remain in the 'negotiating' state indefinitely. Affected browsers include:
IE6; Firefox 1.5 (Mac and PC); Safari 2.0.3 and earlier, and Camino. IE7 and Safari 2.0.4 do not appear to be affected
by this. Using the QuickTime 6.5 plus later option for the Player format on the MCU will allow streaming to QuickTime
using any browser that supports a QuickTime plug-in.
Clustering Limitations
Cisco TelePresence MCU Conference Director will only work with the master blade in a cluster.
If you are using Cisco Telepresence Management Server Version 12.6 or earlier to schedule conferences on clustered
blades, only add the master blade to TMS. Do not add slave blades to TMS and remove from TMS any blade that you
subsequently configure as a slave blade: you will need to reconfigure any scheduled conferences that were
previously configured on slave blades as new conferences running on the master blade.
blades, only add the master blade to TMS. Do not add slave blades to TMS and remove from TMS any blade that you
subsequently configure as a slave blade: you will need to reconfigure any scheduled conferences that were
previously configured on slave blades as new conferences running on the master blade.
Uploading and Downloading Large Files while Heavily Loaded
We recommend that you do not upload or download large files from the MCU while it is hosting active calls. Files such
as CDRs, audit logs and code images should be transferred when there are few or no calls on the MCU.
as CDRs, audit logs and code images should be transferred when there are few or no calls on the MCU.
Automatic Link-Local IPv6 Assignment on Disabled Interface
When you enable IPv6 on any of the device's Ethernet ports (Network > Port A or Network > Port B), the device
automatically assigns a link-local IPv6 address to each Ethernet port, even if the port is disabled. An IP address that is
assigned to a disabled Ethernet port may not be apparent on the web interface.
automatically assigns a link-local IPv6 address to each Ethernet port, even if the port is disabled. An IP address that is
assigned to a disabled Ethernet port may not be apparent on the web interface.
Link-Local Addresses
Link-local IPv6 addresses are generated using the MAC address of each physical interface, and are thus unique per
physical interface. No restrictions are imposed on link-local IPv6 addresses and all services enabled on their
corresponding global IPv6 addresses are available on the link-local address. They support basic configuration and
administration services (such as the web interface) but may not support full functionality such as making and
receiving calls. Full functionality is only guaranteed for the main global IPv6 address on each interface.
physical interface. No restrictions are imposed on link-local IPv6 addresses and all services enabled on their
corresponding global IPv6 addresses are available on the link-local address. They support basic configuration and
administration services (such as the web interface) but may not support full functionality such as making and
receiving calls. Full functionality is only guaranteed for the main global IPv6 address on each interface.
We recommend using a PC with a single network interface connected to the local subnet when trying to access the
MCU web UI using its link-local IPv6 address. Otherwise, login may fail since web browsers do not support URL
redirection for an address with a scope ID.
MCU web UI using its link-local IPv6 address. Otherwise, login may fail since web browsers do not support URL
redirection for an address with a scope ID.
MCU to MCU SIP Cascading is not Supported
When doing SIP to SIP cascading, the MCU's BFCP negotiation fails and the content appears in the main video
instead of separate channel.
instead of separate channel.
ClearPath not Supported on the Content Channel
MCU does not support ClearPath for the content channel.
Unicode H.323 IDs are Not Rendered Correctly on Conference Pages
Unicode H.323 IDs are not rendered correctly on conference pages. Additionally calls to or from endpoints that use
UCS2 unicode H.323 IDs will not work.
UCS2 unicode H.323 IDs will not work.
8
Cisco TelePresence MCU Series Software Maintenance Release Notes