Cisco Cisco TelePresence MCU 4510 Release Notes
Resolved and open issues in 4.5(1.55)
Cisco TelePresence MCU 4.5(1.55) Software Maintenance Release Notes
Page 7 of 17
Resolved since 4.4(3.67)
Identifier
Description
CSCun99662
In some circumstances an MCU 4500 Series could experience an unexpected restart while a
VNC participant was connected. This issue is now resolved.
VNC participant was connected. This issue is now resolved.
CSCun29147
Preconfigured participants that dialled back into an MCU conference after being disconnected
may not have seen the configured custom pane placement layout. This issue is now resolved.
may not have seen the configured custom pane placement layout. This issue is now resolved.
CSCug62534
In a call between an MCU 4500 and a TX9000, if the TX9000 switched the camera used to supply
video, then the video stream from the MCU showing that participant would become blurry for one
or two seconds. This issue is now resolved.
video, then the video stream from the MCU showing that participant would become blurry for one
or two seconds. This issue is now resolved.
CSCuc41501
MCU 4500 Series and MCU 4200 Series models were unable to register with their internal
gatekeepers using their global IPv6 addresses. This issue is now resolved.
gatekeepers using their global IPv6 addresses. This issue is now resolved.
CSCue35267
In certain scenarios, the MCU participant disconnect CDR log may have left the disconnection
cause field empty instead of reporting the event as 'unknown'. The possible conditions that may
have triggered this were: the participant had been disconnected through in-call menu; the
participant had been disconnected by the participant.disconnect API call; the unit had shut down;
port allocation had been exceeded when the participant was already in the conference and then
disconnected; ConferenceMe participant disconnected as ConferenceMe had been disabled
mid-call etc. This issue is now resolved.
cause field empty instead of reporting the event as 'unknown'. The possible conditions that may
have triggered this were: the participant had been disconnected through in-call menu; the
participant had been disconnected by the participant.disconnect API call; the unit had shut down;
port allocation had been exceeded when the participant was already in the conference and then
disconnected; ConferenceMe participant disconnected as ConferenceMe had been disabled
mid-call etc. This issue is now resolved.
CSCuo63492
During a call with an MCU, a Polycom Group endpoint could report that it was receiving content
video despite the MCU not sending any. This issue is now resolved.
video despite the MCU not sending any. This issue is now resolved.
CSCuo24405
In some rare conditions the MCU 5300 Series could experience an unexpected restart when the
H.264 encoder stalled under load. This issue is now resolved.
H.264 encoder stalled under load. This issue is now resolved.
CSCuo16063
If an MCU 5300 Series was receiving content from a Cisco Telepresence System C Series
endpoint, and this endpoint was receiving a lot of keyframe requests for the content video, then
after a certain amount of time the MCU would no longer be able to decode the content stream.
This issue is now resolved.
endpoint, and this endpoint was receiving a lot of keyframe requests for the content video, then
after a certain amount of time the MCU would no longer be able to decode the content stream.
This issue is now resolved.
CSCuo00020
The Java applet used for viewing content when streaming a conference was not
cryptographically signed. Java versions from 7 update 51 onwards disable unsigned applets by
default, and users need to change their security settings in order to use them. This issue is now
resolved.
cryptographically signed. Java versions from 7 update 51 onwards disable unsigned applets by
default, and users need to change their security settings in order to use them. This issue is now
resolved.
CSCun84221
When a permanent conference was ended 100 days or more after it started, or a conference of
100 days or more was created via the API, the duration displayed on the web interface was
incorrect. (The hours field was appended to the days field. For example, a conference lasting
100 days, 1 hour, 3 minutes was displayed as 1001 days, 1 hour, 3 minutes.) This issue is now
resolved.
100 days or more was created via the API, the duration displayed on the web interface was
incorrect. (The hours field was appended to the days field. For example, a conference lasting
100 days, 1 hour, 3 minutes was displayed as 1001 days, 1 hour, 3 minutes.) This issue is now
resolved.
CSCuo08027
In a call with a Microsoft Lync client, video from the Lync client could appear horizontally
squashed if there was significant motion in the video. This issue is now resolved.
squashed if there was significant motion in the video. This issue is now resolved.
CSCum78087 When using the content streaming Java applet, Mac OS X streaming participants were unable to
send text messages. This issue is now resolved.
CSCul55354
An MCU 4510 could experience an unexpected restart after trying to incorrectly allocate some
memory to store a video frame. This issue is now resolved.
memory to store a video frame. This issue is now resolved.
CSCul30254
In an H.323 call, when a conference's content mode was set to hybrid, around 40 RTP packets
would be missing from the start of the passthrough content stream sent by the MCU. This issue is
now resolved.
would be missing from the start of the passthrough content stream sent by the MCU. This issue is
now resolved.