Cisco Cisco TelePresence MCU 4510 Release Notes
Resolved issues
Cisco TelePresence MCU 4.4(3.54) Maintenance Release Notes
Page 7 of 27
Identifier
Description
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.
CSCud53710 In previous releases, if the called party identification had been updated during the call, and the
call subsequently failed, the MCU would use the updated information when attempting to
reconnect the call instead of using the original information. This led to a reconnection failure. This
issue is now resolved.
reconnect the call instead of using the original information. This led to a reconnection failure. This
issue is now resolved.
CSCue55707 In previous releases, the MCU chose to send H.263 over H.264 to new Polycom
RealPresenceGroup series endpoints even though the endpoints advertise H.264 support. This
issue is now resolved.
issue is now resolved.
CSCue36290 In previous releases, the MCU on-line help pages (help_content_support.html and help_
conference_add.html) had a misleading description for Hybrid content mode. This issue is now
resolved.
resolved.
CSCuf02861
In previous releases, the MCU host processor could become overloaded when holding
conferences with a large number of participants with additional web and API usage. This could
result in slow web and API responsiveness and in extreme conditions, the MCU could experience
an unexpected restart. In this release, a number of performance related enhancements have been
made to prevent the host processor from overloading.
conferences with a large number of participants with additional web and API usage. This could
result in slow web and API responsiveness and in extreme conditions, the MCU could experience
an unexpected restart. In this release, a number of performance related enhancements have been
made to prevent the host processor from overloading.
CSCtx29996
In previous releases, when making SIP calls to Panasonic endpoints, the MCU sent incorrectly
formed SIP UPDATE messages which resulted in the call being disconnected. This issue is now
resolved.
formed SIP UPDATE messages which resulted in the call being disconnected. This issue is now
resolved.
CSCuc22159
In previous releases, a customer MCU 4500 experienced an unexpected restart due to a memory
corruption resulting from a buffer overflow. This issue is now resolved.
corruption resulting from a buffer overflow. This issue is now resolved.