Cisco Cisco TelePresence MCU 4510 Release Notes
Resolved issues
Cisco TelePresence MCU 4.4(3.49) Maintenance Release Notes
Page 8 of 27
Resolved since 4.3(2.32)
Identifier
Description
CSCud59266
In previous releases, in rare circumstances the MCU could experience an unexpected restart if
invalid bitstream was sent to the DSP and the exit message would show an sse validate failure
error. This is resolved in this release.
invalid bitstream was sent to the DSP and the exit message would show an sse validate failure
error. This is resolved in this release.
CSCtz69347
In previous releases, MCU 4200 Series models could experience an unexpected restart when
the maximum MTU size was set to 400 bytes or lower. This is resolved in this release.
the maximum MTU size was set to 400 bytes or lower. This is resolved in this release.
CSCua55120
In previous releases, the MCU could experience an unexpected restart when a participant's
muted video was used as content source. This is resolved in this release.
muted video was used as content source. This is resolved in this release.
CSCuc58773
In previous releases, when a space character was used for the displayNameOverrideValue string
over the API, the MCU could not correctly overlay this character on the participant's video. This is
resolved in this release.
over the API, the MCU could not correctly overlay this character on the participant's video. This is
resolved in this release.
CSCuc57928
In previous releases, the MCU 4200 Series models could experience an unexpected restart with
an H.264 decoder marker check failure message when invalid bitstream was sent to the DSP.
This is resolved in this release.
an H.264 decoder marker check failure message when invalid bitstream was sent to the DSP.
This is resolved in this release.
CSCuc46770
In previous releases, when content mode was set to passthrough, content transmission could fail
from a C-series endpoint when an MXP endpoint was present in the same conference and the
call bandwidth was less than 1Mbps. This is resolved in this release.
from a C-series endpoint when an MXP endpoint was present in the same conference and the
call bandwidth was less than 1Mbps. This is resolved in this release.
CSCub83253
In previous releases, when dialing a SIP participant by IP address, if the SIP registrar box was
ticked, the MCU would incorrectly append its SIP domain name to the IP address. This is
resolved in this release.
ticked, the MCU would incorrectly append its SIP domain name to the IP address. This is
resolved in this release.
CSCub18876
In previous releases, MCU 4501 or 4505 models could take over a minute to establish H.245
connection to participants when there are several incomplete H.225 TCP connections open to
powered-off endpoints. In this release, the behavior is improved for those models but it is still
advised to ensure endpoints are turned on if they are preconfigured on the MCU as they will be
automatically dialed out; alternatively use a gatekeeper.
connection to participants when there are several incomplete H.225 TCP connections open to
powered-off endpoints. In this release, the behavior is improved for those models but it is still
advised to ensure endpoints are turned on if they are preconfigured on the MCU as they will be
automatically dialed out; alternatively use a gatekeeper.
CSCuc40088
In previous releases, the MCU could experience an unexpected restart due to a picture buffer
overrun that could be triggered by a corrupt bit-stream. This is resolved in this release.
overrun that could be triggered by a corrupt bit-stream. This is resolved in this release.
CSCtx81724
In previous releases, the RTCP PLI (picture loss indication) messages sent by the MCU were not
part of a compound RTCP packet. This is resolved in this release.
part of a compound RTCP packet. This is resolved in this release.
CSCud59262
In previous releases, there was incorrect behavior of the conference's disconnect remaining
guests feature and the participants' auto-disconnect feature. The MCU would ignore chairs that
were configured to auto-disconnect when deciding if only guests remained in the conference. In
this release, under the same circumstances, the MCU does not disconnect the remaining guests
unless all the chairs have disconnected—irrespective of whether any chairs are configured to
auto-disconnect.
guests feature and the participants' auto-disconnect feature. The MCU would ignore chairs that
were configured to auto-disconnect when deciding if only guests remained in the conference. In
this release, under the same circumstances, the MCU does not disconnect the remaining guests
unless all the chairs have disconnected—irrespective of whether any chairs are configured to
auto-disconnect.
CSCud48267
In previous releases, the MCU would attempt a registrar call for an endpoint that was configured
to use a SIP registrar, even if SIP registrar usage was disabled for the whole MCU. This has been
resolved in this release.
to use a SIP registrar, even if SIP registrar usage was disabled for the whole MCU. This has been
resolved in this release.
CSCtz42558
In previous releases, custom codec selections were not correctly applied to pre-configured SIP
participants when they dialed in to the MCU. This is resolved in this release.
participants when they dialed in to the MCU. This is resolved in this release.
CSCuc40073
In previous releases, the MCU event log sometimes reported failure to send serial messages to
the Supervisor even when the box is idle. This is resolved in this release.
the Supervisor even when the box is idle. This is resolved in this release.
CSCty83668
In previous releases, when a SIP participant was put on hold, it would appear either as a black
pane or a frozen image to other participants. This is resolved in this release; when a participant is
put on hold, that participant's video pane is not displayed.
pane or a frozen image to other participants. This is resolved in this release; when a participant is
put on hold, that participant's video pane is not displayed.