Release Notes

Limitations
Cisco TelePresence MCU 5300 Series 4.3(2.30) Software release notes Page 4 of 15
Identifier
Description
release.
CSCtz69665
In previous releases, the 'purge selected' button to delete selected conferences on the MCU did not
work for certain localisation packages (e.g. Russian). This is resolved in this release.
CSCua09848
In previous 4.3 releases, the MCU API did not trigger an update through participant.enumerate when
the active speaker in the conference changed. This is resolved in this release.
Limitations
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.
Interoperability with CTS endpoints
Using CTS Series endpoints with the MCU 5300 Series is not currently recommended.
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.
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.
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.
Version 4.3(2.17) of the MCU software was used for this interoperability testing.
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.
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.
Call path 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
Endpoint <--H.323--> VCS <--SIP--> MCU.
SIP to H.323 interworking
Endpoint <--SIP--> VCS <--H.323--> MCU.