Cisco Cisco TelePresence MCU 4510 Release Notes
Resolved issues
Cisco TelePresence MCU 4.3(2.30) Software Release Notes
Page 6 of 17
Identifier
Description
this release.
CSCty61469 In previous releases, the MCU will only send a CIF resolutions to a Polycom RMX MCU even when
the Polycom MCU is capable of receiving higher resolutions. This is resolved in this release.
CSCty67022 In previous releases, the MCU could get into a state when no streaming media can be played from
the streaming page. This is resolved in this release.
CSCty83602 In previous releases, when using the MCU in HD mode, any configuration changes on the Settings
page would render 'Video Receive Bit Rate Optimisation' and 'Flow Control On Video Errors' options
unchecked and greyed out. This is resolved in this this release.
unchecked and greyed out. This is resolved in this this release.
CSCty91132 In previous 4.3 releases, the display name field of a SIP participant was not always prioritised over
the username of the participant. This is resolved in this release.
CSCtz35468 In previous releases, long term use of the Microsoft Internet Explorer web browser could result in the
MCU gradually running out of memory, which could cause an unexpected restart.
CSCtz25884 In previous releases, the MCU could experience an unexpected restart if a participant creating a
conference through the auto attendant was moved prematurely to the same conference via the web
interface before completing the task of configuring the pin for that conference. This is resolved in this
release.
interface before completing the task of configuring the pin for that conference. This is resolved in this
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.
Resolved since 4.3(1.68)
Identifier
Description
CSCtz09450 In the previous 4.3 release it was possible to configure a cluster of four Cisco TelePresence MCU
MSE 8510 blades in the Cisco TelePresence MSE 8000 chassis when we only officially support three
blades. This is resolved in this release.
blades. This is resolved in this release.
CSCtz03995 Previous versions of MCU software, running on platforms other than the MCU 5300, do not support
cascading with the MCU 5300. This has been resolved in 4.3(2.18) on MCU platforms in general (this
release), and in 4.3(2.17) on the MCU 5300 (first full release).
release), and in 4.3(2.17) on the MCU 5300 (first full release).
CSCty98522 In previous releases, when the display name override field was used for preconfigured participants,
the MCU would only display that name on the video display but not on the web interface. This is
resolved in this release.
Note that if a non-printing character, e.g. a space, is used for the display name override, the web
interface reverts to the participant's name instead of the non-printing override, but the video display
still shows the override.
resolved in this release.
Note that if a non-printing character, e.g. a space, is used for the display name override, the web
interface reverts to the participant's name instead of the non-printing override, but the video display
still shows the override.
CSCtx48168 In previous releases, the MCU participant.enumerate API response would sometimes omit the
'callDirection' parameter. This has been resolved in this release.
CSCtx62208 In previous releases, if a conference template name ended with a space, it was not possible to edit
any fields for that template. This has been resolved in this release.
CSCty06858 In previous releases, the MCU 4500 experienced an unexpected restart when the MCU tried to
access a decoder that is not present or invalid. This has been resolved in this release.
CSCty07111 In previous releases, an MCU running in HD mode only sent CIF resolution to Polycom RSS2000
(v.4), even though Polycom can support resolutions up to 1080p at 30 frames per second. This has
been resolved in this release.
been resolved in this release.
CSCty10645
In previous 4.3 releases, the top menu bar was not rendered correctly on the Conferences ->