Cisco Cisco TelePresence MCU 4510 Release Notes
Open issues
Cisco TelePresence MCU 4.4(3.49) Maintenance Release Notes
Page 9 of 27
Identifier
Description
CSCty77949
In previous releases, when attempts were made to overwrite a valid auto attendant banner
image with an invalid image, the MCU might not subsequently have been able to delete the
valid banner image when a user deleted the associated auto attendant. This led to a situation
where all the auto attendant banner storage space was used, but the images could not be
deleted – preventing further banner image uploads. This is resolved in this release.
image with an invalid image, the MCU might not subsequently have been able to delete the
valid banner image when a user deleted the associated auto attendant. This led to a situation
where all the auto attendant banner storage space was used, but the images could not be
deleted – preventing further banner image uploads. This is resolved in this release.
CSCty98516
In previous releases, the display field in the FROM header of an MCU sip log did not correctly
display Unicode characters. This is resolved in this release.
display Unicode characters. This is resolved in this release.
CSCua09538
In previous releases, the MCU 4500 series could experience a DSP watchdog trip restart due to
exposure to corrupt H.264 bit stream. This is resolved in this release.
exposure to corrupt H.264 bit stream. This is resolved in this release.
CSCub18878
In previous releases, there were a number of areas within the H.264 decoder code where invalid
(non-H.264) data could potentially cause an error and as a consequence the DSP could crash
or timeout. The H.264 decoder resiliency has been vastly improved in this release.
(non-H.264) data could potentially cause an error and as a consequence the DSP could crash
or timeout. The H.264 decoder resiliency has been vastly improved in this release.
CSCub15957
In previous releases, the MCU would not refresh its registration to a SIP registrar if the contact
header field of the 200 OK message from the registrar exceeded 256 characters.
header field of the 200 OK message from the registrar exceeded 256 characters.
This issue has been resolved in this release.
CSCub15970
In some circumstances, the MCU stopped responding to HTTP(S) requests on both the web
interface and API calls. This recent problem has been attributed to Firefox browser version 14.0.1
(the first release code of Firefox 14; release date: 17th July 2012) and is improved in this release.
This version of Firefox is still not recommended; Firefox 15 or later should be used instead. See
also the limitations section of these release notes.
interface and API calls. This recent problem has been attributed to Firefox browser version 14.0.1
(the first release code of Firefox 14; release date: 17th July 2012) and is improved in this release.
This version of Firefox is still not recommended; Firefox 15 or later should be used instead. See
also the limitations section of these release notes.
CSCty91132
In previous releases, when multiple names were received in the SIP header field, the MCU often
did not prioritize the 'display field' among other names. This is resolved in this release.
did not prioritize the 'display field' among other names. This is resolved in this release.
Open issues
The following issues apply to this version of the Cisco TelePresence MCU Series software.
Identifier
Description
CSCuc58400
When the MCU shuts down due to high ambient temperature, the diagnostic log correctly reports
this event as a thermal override shutdown. However, the MCU status page incorrectly logs this
restart as a 'user requested shutdown'.
this event as a thermal override shutdown. However, the MCU status page incorrectly logs this
restart as a 'user requested shutdown'.
CSCue35267 In certain scenarios, the MCU participant disconnect CDR log may leave the disconnection cause
field empty instead of reporting the event as 'unknown'. The possible conditions that may trigger
this are: the participant has been disconnected through in-call menu; the participant has been
disconnected by the participant.disconnect API call; the unit has shut down; port allocation has
exceeded when the participant was already in the conference and then disconnected;
ConferenceMe participant disconnected as ConferenceMe has been disabled mid-call etc.
this are: the participant has been disconnected through in-call menu; the participant has been
disconnected by the participant.disconnect API call; the unit has shut down; port allocation has
exceeded when the participant was already in the conference and then disconnected;
ConferenceMe participant disconnected as ConferenceMe has been disabled mid-call etc.
CSCtr53874
Slot 10 of the Cisco TelePresence MSE 8000 chassis does not support clustering in this MCU
software release. However, slot 10 in the same chassis as a cluster can be used for a standalone
blade of any type.
software release. However, slot 10 in the same chassis as a cluster can be used for a standalone
blade of any type.
CSCts46406
If the MCU Ethernet interfaces are configured to have the same IP address and then you attempt
to disable a service on one of the interfaces the service is still allowed, even though the web
interface shows it set to disabled.
to disable a service on one of the interfaces the service is still allowed, even though the web
interface shows it set to disabled.
CSCuc41494
RealPlayer multicast for IPv6 is not currently supported.