Cisco Cisco TelePresence MCU 4510 Release Notes
Resolved issues
Cisco TelePresence MCU 4.4(3.57) Maintenance Release Notes
Page 7 of 28
Identifier
Description
CSCui47687 In previous releases an MCU would only ever send CIF to a Polycom RSS4000. This issue is now
resolved.
CSCuj04596 In previous releases it was not possible to set a subnet mask of the form xxx.0.0.0 using the MCU's
web interface. The error message Please fix errors and re-submit error: Invalid IP
address
address
was produced. This issue is now resolved.
CSCui72250 In previous releases if a localization package was uploaded to an MCU when the Use localization
package setting was already checked, the localization package may not have taken immediate
effect. This issue is now resolved.
effect. This issue is now resolved.
Resolved since 4.4(3.49)
Identifier
Description
CSCug89505 In previous releases it was possible for an MCU to experience an unexpected restart if it received
an API message including a displayNameOverrideValue that was longer than the maximum of
31 characters. This issue is now resolved.
31 characters. This issue is now resolved.
CSCub28587 In some circumstances, an encrypted conference participant could be incorrectly reported as an
unencrypted participant. This issue is now resolved.
CSCug56190 In previous releases, a customer MCU 4500 experienced an unexpected restart because it ran
out of memory while trying to run many processes. This issue is further improved in this release.
CSCua00144 In previous releases a warning message was generated when the MCU received an unexpected
SIP message. In this release, the message will now only appear at Trace level.
CSCuh78036 In previous 4.4 releases, under some circumstances it was possible for guests in an Automatic
Lecture Mode type 2 conference to receive black video. This issue is now resolved.
Resolved since 4.4(3.42)
Identifier
Description
CSCue49344 In previous releases, some attribute fields could incorrectly appear before bandwidth information
in the SDP of a SIP message. This issue is now resolved.
CSCuc09395
In the 4.3 release, a customer MCU 4500 experienced an unexpected restart because it ran out of
memory while trying to run many processes. This issue is improved in this release.
memory while trying to run many processes. This issue is improved in this release.
CSCue03922 In previous releases, when the MCU received invalid RTCP messages, it would print error
messages at a very high rate in the event/serial log which added extra load to the host processor.
In this release, the error messages are rate limited so that the MCU host processor is not
overwhelmed with printing hundreds of error messages.
In this release, the error messages are rate limited so that the MCU host processor is not
overwhelmed with printing hundreds of error messages.
CSCue08737 In previous releases, a customer MCU 4500 experienced an unexpected restart when encoding
an H.263 bit-stream due to a misconfiguration of the encoder. This issue is now resolved.
CSCud48262 In previous releases, on the MCU 4220, 4520, and MSE 8420 models, the internal message
queue could become saturated if a large number of participants simultaneously disconnected
from the MCU. Repetition of these circumstances could lead to a reduction in the maximum
number of participants that the MCU could support. This issue is now resolved.
from the MCU. Repetition of these circumstances could lead to a reduction in the maximum
number of participants that the MCU could support. This issue is now resolved.