Cisco Cisco TelePresence MCU 4510 Release Notes
Open issues
Cisco TelePresence MCU 4.4 (3.42) Release Notes
Page 8 of 24
Identifier
Description
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
CSCud53710 If the called party identification information has been updated during the call, and the call
subsequently fails, the MCU uses the updated information when attempting to reconnect the call
instead of using the original information. This can lead to reconnection failure in scenarios where
the identification information is transformed in the call path.
instead of using the original information. This can lead to reconnection failure in scenarios where
the identification information is transformed in the call path.
CSCud48262 On the MCU 4220, 4520, and MSE 8420 models, the internal message queue can become
saturated if a large number of participants simultaneously disconnect from the MCU. This can
happen when a single conference with 70 or more participants is ended, or if all those participants
are simultaneously disconnected. Repetition of these circumstances can lead to a reduction in the
maximum number of participants that the MCU can support. You can recover the full capacity of
the MCU by restarting it.
happen when a single conference with 70 or more participants is ended, or if all those participants
are simultaneously disconnected. Repetition of these circumstances can lead to a reduction in the
maximum number of participants that the MCU can support. You can recover the full capacity of
the MCU by restarting it.
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.
CSCuc41501
MCU 4500 Series and MCU 4200 Series models are unable to register with their internal
gatekeepers using their global IPv6 addresses. The workaround for this issue is to use an IPv6
loopback address [::1] rather than the global IPv6 address.
gatekeepers using their global IPv6 addresses. The workaround for this issue is to use an IPv6
loopback address [::1] rather than the global IPv6 address.