Cisco Cisco TelePresence MCU 4510 Release Notes
Limitations
Cisco TelePresence MCU 4.5(1.45) Software Release Notes
Page 11 of 16
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.
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.
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.
Files such as CDRs, audit logs and code images should be transferred when there are few or no calls on the
MCU.
Raw IPv6 addresses in Firefox 4.0 and later
It is not possible to access an MCU HTTPS web interface in Mozilla Firefox Version 4.0 using a raw IPv6
address. It is possible with IPv4 addresses and in earlier versions of Firefox, or if a hostname is used instead
of the raw IPv6 address. This issue is being tracked by Mozilla as bug 633001.
address. It is possible with IPv4 addresses and in earlier versions of Firefox, or if a hostname is used instead
of the raw IPv6 address. This issue is being tracked by Mozilla as bug 633001.
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.
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.
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.
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.
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 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.
video 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.
that use UCS2 unicode H.323 IDs will not work.