Cisco Cisco TelePresence MCU 4510 Release Notes
Resolved issues
Cisco TelePresence MCU 4.3(2.18) Software Release Notes
Page 6 of 16
Identifier
Description
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 ->
Template page of the MCU web user-interface when a localization package was uploaded on the
MCU. This has been resolved in this release.
Template page of the MCU web user-interface when a localization package was uploaded on the
MCU. This has been resolved in this release.
CSCty13904 In previous 4.3 releases, when a localization package was uploaded on the MCU web interface, some
of the fields were not displayed correctly. This has been resolved in this release.
CSCty22375 In previous releases, when a participant.remove API command was sent immediately after a
participant.disconnect API command, the MCU would not successfully remove the participant from
the participant list. This has been resolved in this release.
the participant list. This has been resolved in this release.
Resolved since 4.2(1.50)
Identifier
Description
CSCtt19422 In previous releases, when a SIP session was refreshed, the session version parameter in the MCU's
SDP was not updated correctly. This caused an interoperability issue with IMS phone switch where
the calls from MCU would disconnect. This is resolved in this release.
the calls from MCU would disconnect. This is resolved in this release.
CSCtx76766 In previous releases, MCU could under certain circumstances experience slow performance when
uploading large CDR logs (>100,000 messages) to TMS. This is resolved in this release.
CSCty98518 In previous releases, when a 2 Mbps SIP call was placed from an MCU in HD mode, the MCU
participants page would incorrectly report the receive bandwidth as 4 Mbps instead of 2 Mbps. This is
resolved in this release.
resolved in this release.
CSCtq91175 In previous releases, participants added to a conference via the API would not inherit the default
layout control value of the conference. This has been resolved in this release.
CSCtq99800 In previous releases, the MCU did not attempt to register to the alternate gatekeeper if the primary
gatekeeper had sent a URQ. This has been resolved in this release.
CSCtr15071 In previous releases, if a Cisco Unified Border Element (CUBE) was in the call path between the
MCU and an endpoint, H.239 content negotiation was not possible. This has been resolved in this
release.
release.
CSCtr51282 In previous releases, under some circumstances a Polycom MGC would send content to the MCU
that is outside the advertised capabilities of the MCU and therefore the MCU was unable to correctly
decode it. Support for these content capabilities has been added in this release.
decode it. Support for these content capabilities has been added in this release.
CSCtr80218 In previous releases, an MCU with gatekeeper setting as required, did not send an ARQ to its H.323
gatekeeper for an incoming call from a Microsoft Netmeeting client. This has been resolved in this