Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
■
Multi-domain and multi-customer support is limited as follows:
—
Prior to X8.5, each Cisco VCS deployment supported only one IM&P domain (even though IM and Presence
Service 10.0 or later supports Multiple Presence Domains).
Service 10.0 or later supports Multiple Presence Domains).
—
As of X8.5, you can create multiple deployments on the Cisco VCS Control, but this feature is still limited to one
domain per deployment.
domain per deployment.
—
As of X8.5.1, a deployment can have Multiple Presence Domains. This feature is in preview, and we currently
recommend that you do not exceed 50 domains.
recommend that you do not exceed 50 domains.
■
Mobile and remote access functionality is not within the FIPS boundary.
■
NTLM authentication via the HTTP proxy.
■
Maintenance mode; if the Cisco VCS Control or the Cisco VCS Expressway is placed into maintenance mode,
any existing calls passing through that Cisco VCS will be dropped.
any existing calls passing through that Cisco VCS will be dropped.
■
The Cisco VCS Expressway must not have TURN services enabled.
■
Deployments on Large VM servers are limited to 2500 proxied registrations to Unified CM (the same limit as
Cisco VCS appliances or equivalent VM).
Cisco VCS appliances or equivalent VM).
Interoperability
The interoperability test results for this product are posted to
, where you can also find
interoperability test results for other Cisco TelePresence products.
Upgrading to X8.7
Prerequisites and Software Dependencies
Existing TMS Agent (Legacy Mode) Provisioning Deployments
Cisco 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
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
Cisco 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 Cisco VCS and a
Microsoft Lync Server. See
OCS Relay you must migrate to using the Microsoft Lync B2BUA to route SIP calls between the Cisco VCS and a
Microsoft Lync Server. See
VCS and Microsoft Lync Deployment Guide for information about this deployment.
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:
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
7
Cisco TelePresence Video Communication Server Release Note