Cisco Cisco TelePresence MCU 4510 Release Notes
Interoperability
Cisco TelePresence MCU 4.3(2.18) Software Release Notes
Page 9 of 16
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.
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
It is recommended that you do not upload or download large files from the MCU while it is heavily loaded. 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.
Binary Floor Control Protocol on encrypted calls
The transmission of SIP content from the MCU using Binary Floor Control Protocol (BFCP) is not supported on
encrypted calls. To allow content to be transmitted over SIP calls in a separate channel from main video, you should
disable encryption on the MCU or on the target endpoint.
encrypted calls. To allow content to be transmitted over SIP calls in a separate channel from main video, you should
disable encryption on the MCU or on the target endpoint.
Raw IPv6 addresses in Firefox 4.0
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 is being tracked by Mozilla as bug 633001.
is possible with IPv4 addresses and in earlier versions of Firefox, or if a hostname is used instead of the raw IPv6
address. This is being tracked by Mozilla as bug 633001.
Interoperability
We endeavor to make the MCU interoperable with all relevant standards-based equipment. While it is not possible to
test all scenarios, the testing that the data below is based on covers all the most common functions of the listed
endpoints and infrastructure.
test all scenarios, the testing that the data below is based on covers all the most common functions of the listed
endpoints and infrastructure.
About the interoperability section
The interoperability section describes the equipment and software revisions that were tested for interoperability with
this release. The absence of a device or revision from this section does not imply a lack of interoperability.
this release. The absence of a device or revision from this section does not imply a lack of interoperability.
Interoperability testing often requires interworking from one signaling/call control protocol to another. The following
table lists phrases that are used to briefly describe the call paths that were tested for each interoperability scenario.
The explicit call paths in the table place the endpoint first and the MCU last as a general convention.
table lists phrases that are used to briefly describe the call paths that were tested for each interoperability scenario.
The explicit call paths in the table place the endpoint first and the MCU last as a general convention.
Call path
phrase
phrase
Explicit call path description
SIP
Endpoint <--SIP--> MCU. A registrar is used but not shown here.
H.323
Endpoint <--H.323--> MCU. A gatekeeper is used but not shown here.
H.323 to SIP
interworking
interworking
Endpoint <--H.323--> VCS <--SIP--> MCU.
SIP to H.323
interworking
interworking
Endpoint <--SIP--> VCS <--H.323--> MCU.
CUCM to VCS
H.323
H.323
Endpoint <--SIP--> CUCM <--SIP--> VCS <--H.323--> MCU.
CUCM to VCS
SIP
SIP
Endpoint <--SIP--> CUCM <--SIP--> VCS <--SIP--> MCU.
Note: Unless otherwise stated, CUCM version 8.6(1a) and VCS version X7.0 were used in the interoperability tests.