Cisco Cisco TelePresence MCU 4510 Release Notes
Open issues
Cisco TelePresence MCU 4.3(2.30) Software Release Notes
Page 8 of 17
Identifier
Description
This has been resolved in this release.
CSCtu04630 In Version 4.2, the MCU was using an ephemeral port range for both TCP and UDP of 10000 to
65535 instead of the documented range of 49152 to 65535. This has been resolved in this release.
CSCtu19596 When a conference created via an API call (for example, by Cisco TelePresence Management Suite
(TMS)) uses a duplicate numeric ID to that of an existing ad-hoc conference on the MCU, the MCU
correctly stops the conference from being created and generates the following error : "Failed to
create conference" - duplicate numeric id". However, in previous releases, this error state continued
even after the ad-hoc conference was deleted from the MCU. This has been resolved in this release.
correctly stops the conference from being created and generates the following error : "Failed to
create conference" - duplicate numeric id". However, in previous releases, this error state continued
even after the ad-hoc conference was deleted from the MCU. This has been resolved in this release.
CSCtw49855 In previous releases, when downloading a configuration file from the master MCU in a cluster which
is heavily loaded with participants, in rare circumstances the slave MCUs could restart because of
loss of contact with the master MCU. This has been resolved in this release.
loss of contact with the master MCU. This has been resolved in this release.
CSCtw49892 In previous releases, when attempting to join a conference using a ConferenceMe invitation link, the
request would fail with the message: “Error: conference no longer exists” if the conference name
included some special characters. This has been resolved in this release.
included some special characters. This has been resolved in this release.
CSCtw52422 In previous releases, under certain conditions, the Polycom Viewstation endpoint was not able to
register to the MCU’s built-in gatekeeper, and a warning message would appear in the event log.
This has been resolved in this release.
This has been resolved in this release.
CSCtw61034 In previous releases, when resuming a call to the MCU that was placed on hold by any C-series
endpoint, other participants did not hear any audio from that endpoint. This occurred in some
versions of the MCU Version 4.2 software release and when the RTP sequence numbers increased
by more than 32000 on resume. This has been resolved in this release.
versions of the MCU Version 4.2 software release and when the RTP sequence numbers increased
by more than 32000 on resume. This has been resolved in this release.
CSCtw72308 In previous releases, the participant join notification text was sometimes not seen by video
participants when an audio-only participant joined the conference. This has been resolved in this
release.
release.
CSCtw95448 In previous releases, the MCU could reboot when a participant set as the focused participant for
active streaming viewers disconnected. This has been resolved in this release.
CSCtx00682 In previous releases, when using QuickTime player to stream the content window, QuickTime would
fail over HTTP if "redirect http to https" was enabled. This was because the MCU would incorrectly
redirect the streaming request from HTTP to HTTPS and QuickTime player does not support this.
This has been resolved in this release.
redirect the streaming request from HTTP to HTTPS and QuickTime player does not support this.
This has been resolved in this release.
CSCtx29749 In previous releases of the MCU, when sending G.728 to an MXP based endpoint, a high-pitched
noise was heard after approximately 30 minutes. This has been resolved in this release.
CSCtx34673 In previous releases, under rare circumstances, the MCU 4500 could fail due to a memory address
being read incorrectly. This issue has been resolved in this release.
Open issues
The following issues apply to this version of the Cisco TelePresence MCU software:
Identifier
Description
CSCty77949 When an attempt has been made to overwrite a valid auto attendant banner image with an invalid
image, the MCU may not subsequently be able to delete the valid banner image when a user deletes
the associated auto attendant. This can lead to a situation where all the auto attendant banner space
is used, but the images can not be deleted
the associated auto attendant. This can lead to a situation where all the auto attendant banner space
is used, but the images can not be deleted
– preventing further banner image uploads.