Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Interoperability
Cisco TelePresence Video Communication Server Software Release Notes (X8.5.3)
Page 12 of 26
n
Phone security profile: If the phone security profile for any of these endpoints has TFTP Encrypted
Config checked, you will not be able to use the endpoint via Mobile and Remote Access. This is because
the MRA solution does not support devices interacting with CAPF (Certificate Authority Proxy Function).
Config checked, you will not be able to use the endpoint via Mobile and Remote Access. This is because
the MRA solution does not support devices interacting with CAPF (Certificate Authority Proxy Function).
n
Trust list: You cannot modify the root CA trust list on these endpoints. Make sure that the VCS
Expressway's server certificate is signed by one of the CAs that the endpoints trust, and that the CA is
trusted by the VCS Control and the VCS Expressway.
Expressway's server certificate is signed by one of the CAs that the endpoints trust, and that the CA is
trusted by the VCS Control and the VCS Expressway.
n
Bandwidth restrictions: The Maximum Session Bit Rate for Video Calls on the default region on
Cisco Unified Communications Manager is 384 kbps by default. The Default call bandwidth on VCS
Control is also 384 kbps by default. These settings may be too low to deliver the expected video quality for
the DX Series.
Cisco Unified Communications Manager is 384 kbps by default. The Default call bandwidth on VCS
Control is also 384 kbps by default. These settings may be too low to deliver the expected video quality for
the DX Series.
Interoperability
, where you
can also find interoperability test results for other Cisco TelePresence products.
Updating to X8.5.3
Prerequisites and software dependencies
Existing TMS Agent (legacy mode) provisioning deployments
VCS X8.1 and later no longer supports TMS Agent (legacy mode) provisioning. Before you upgrade to X8
or later, if you are using TMS Agent (legacy mode) for provisioning you must first migrate to Cisco
TelePresence Management Suite Provisioning Extension which requires TMS 13.2.x. See Cisco TMS
Provisioning Extension Deployment Guide for instructions about how to migrate.
or later, if you are using TMS Agent (legacy mode) for provisioning you must first migrate to Cisco
TelePresence Management Suite Provisioning Extension which requires TMS 13.2.x. See Cisco TMS
Provisioning Extension Deployment Guide for instructions about how to migrate.
Existing OCS Relay deployments
VCS X8.1 and later no longer supports OCS Relay integration with Microsoft Lync 2010 / OCS 2007 R2. If
you use OCS Relay you must migrate to using the Microsoft Lync B2BUA to route SIP calls between the
VCS and a Microsoft Lync Server. See VCS and Microsoft Lync Deployment Guide for information about
how to configure your video network.
you use OCS Relay you must migrate to using the Microsoft Lync B2BUA to route SIP calls between the
VCS and a Microsoft Lync Server. See VCS and Microsoft Lync Deployment Guide for information about
how to configure your video network.
Existing non-AES build installations
As of version X8.1, the software uses AES encryption. Prior to this, a version that used weaker encryption
was available. If you are upgrading to X8.1 or later (or another version that uses AES) from a version that
used the weaker encryption, you must perform a factory reset. Proceed as follows to ensure you can
upgrade in future:
was available. If you are upgrading to X8.1 or later (or another version that uses AES) from a version that
used the weaker encryption, you must perform a factory reset. Proceed as follows to ensure you can
upgrade in future:
1. Record all your software configuration details
2. Upgrade the software with the AES-encryption version
All configuration will be lost
3. Perform a factory reset
4. Manually reconfigure the software