Cisco Cisco TelePresence MCU 4510 Release Notes
Updating to 4.4
Cisco TelePresence MCU 4.4(3.49) Maintenance Release Notes
Page 18 of 27
Cisco Unified
Communications
Manager
Communications
Manager
9.0.1
n
Calls from Cisco Unified IP Phone 9971 via the CUCM to VCS
path result in no audio/video from the endpoint. (CSCub97604).
path result in no audio/video from the endpoint. (CSCub97604).
n
60fps capable endpoints may not be able to negotiate 60fps
with the MCU when the call is made via the CUCM to VCS path.
with the MCU when the call is made via the CUCM to VCS path.
n
CUCM may not correctly respond to mid-call renegotiation from
the MXP on a call to the MCU via the CUCM to MCU path
(CSCtx16122).
the MXP on a call to the MCU via the CUCM to MCU path
(CSCtx16122).
Cisco TelePresence
Content Server
Content Server
S5.3
Tested H.323 and SIP.
n
On some MCU models, audio may be distorted or fail to decode
if G722.1 codec is negotiated with this endpoint (CSCty01044).
This affects MCU MSE Series, MCU 4200 Series, and MCU
4500 Series.
if G722.1 codec is negotiated with this endpoint (CSCty01044).
This affects MCU MSE Series, MCU 4200 Series, and MCU
4500 Series.
n
H.323 audio only calls to a TCS will not be recorded
(CSCud41359).
(CSCud41359).
TANDBERG
Gatekeeper
Gatekeeper
N5.2
Tested H.323.
GNU Gatekeeper
(GnuGk)
(GnuGk)
2.3.1
Tested H.323.
Polycom MGC-50
9.0.3.1
Tested H.323.
n
H.264 video between the MGC and the MCU is not supported if
the call bandwidth is 384 kbps or less. To avoid this, either use a
higher bandwidth or disable H.264 when dialing the MGC using
custom codec selection (CSCts46389).
the call bandwidth is 384 kbps or less. To avoid this, either use a
higher bandwidth or disable H.264 when dialing the MGC using
custom codec selection (CSCts46389).
Polycom
PathNavigator
PathNavigator
7.00.03
Tested H.323.
Updating to 4.4
Software dependencies
To ensure full functionality, the Cisco TelePresence Supervisor MSE 8050 (Supervisor) blade must be
running software version 2.2 or later before you install this release on the MCU MSE Series blades. If the
Supervisor is running Version 2.1(1.18), you can use it to configure an IPv4 address for Port A on the MCU
MSE Series blade but we advise you not to use it for other configuration options as results may be
unpredictable. If the Supervisor is running software earlier than version 2.1(1.18), we advise you not to use it
for any MCU configuration purposes.
running software version 2.2 or later before you install this release on the MCU MSE Series blades. If the
Supervisor is running Version 2.1(1.18), you can use it to configure an IPv4 address for Port A on the MCU
MSE Series blade but we advise you not to use it for other configuration options as results may be
unpredictable. If the Supervisor is running software earlier than version 2.1(1.18), we advise you not to use it
for any MCU configuration purposes.
Prerequisites
The software upgrade process requires a hardware restart. Make sure that the MCU is not in use, or warn any
active users who may be affected by the loss of service.
active users who may be affected by the loss of service.
Have the following items available:
n
The new software image file.
n
The current software image file (in case you need to reverse the upgrade).
n
The backup configuration.xml file.