Cisco Cisco TelePresence MCU 4510 Release Notes
Limitations
Cisco TelePresence MCU 4.5(1.45) Software Release Notes
Page 12 of 16
CTS does not see content on joining or after hold/resume
If calling a CTS into (or out from) a conference that already has content, it does not display it. Similarly it does
not see content it was previously seeing after hold/resume. Restarting the content works. (Issue identifier
CSCum68244)
not see content it was previously seeing after hold/resume. Restarting the content works. (Issue identifier
CSCum68244)
Busy message not sent when port limit is reached
The MCU returns a TRYING message once the port limit is reached instead of a 486 busy message. This is
only an issue when MCU is directly trunked from Cisco Unified Communications Manager. We recommend
deploying the MCU(s) behind Cisco TelePresence Conductor to avoid this.
only an issue when MCU is directly trunked from Cisco Unified Communications Manager. We recommend
deploying the MCU(s) behind Cisco TelePresence Conductor to avoid this.
The MCU does not support sender-side flow control
The MCU does not support sender-side media flow control. This can create problems when calls are made
over low bandwidth pipes to endpoints that do not support receive-side flow control. In such calls, flow
control is not possible for the media from the MCU to the endpoint. To assist in this situation low bandwidth
can be set on the endpoint.
over low bandwidth pipes to endpoints that do not support receive-side flow control. In such calls, flow
control is not possible for the media from the MCU to the endpoint. To assist in this situation low bandwidth
can be set on the endpoint.
Unable to add a VNC user on Windows 7 for MCU
It is not possible to add a VNC user to an MCU conference if the VNC user is running Windows 7 on their
desktop. This is an issue on the Microsoft side - the connection will attempt to call out but fail. In the MCU
logs the following error message will appear: Connect failed with errno 60. The workaround is for
the VNC user to upgrade to Windows 7 SP1 and apply the necessary updates. (Issue identifier
CSCun87357)
desktop. This is an issue on the Microsoft side - the connection will attempt to call out but fail. In the MCU
logs the following error message will appear: Connect failed with errno 60. The workaround is for
the VNC user to upgrade to Windows 7 SP1 and apply the necessary updates. (Issue identifier
CSCun87357)
Slot 10 of the Cisco TelePresence MSE 8000 chassis does not support
clustering
clustering
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.
(Issue identifier CSCtr53874)
release. However, slot 10 in the same chassis as a cluster can be used for a standalone blade of any type.
(Issue identifier CSCtr53874)
MCU times out outbound SIP call after 64 seconds
If an outbound SIP call from an MCU takes longer than 64 seconds to connect, the MCU may time-out the
call before call set-up is complete. (Issue identifier CSCum70556) . To work around this:
call before call set-up is complete. (Issue identifier CSCum70556) . To work around this:
n
Reduce the call setup time by reconfiguring other nodes in the call path, or
n
Use H.323, which has a longer timeout. (The Cisco TelePresence VCS can interwork between H.323 and
SIP.)
SIP.)
Windows Media Player streaming only works over HTTP
Windows Media Player (WMP) streaming will work if the protocol is set to HTTP or Auto-negotiate, but there
may be a delay in connection for auto-negotiate. MMS streaming will fail, and has also been removed from
WMP 11 and onwards.
may be a delay in connection for auto-negotiate. MMS streaming will fail, and has also been removed from
WMP 11 and onwards.