Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Interoperability
Cisco TelePresence Video Communication Server Software Release Notes (X8.2.2)
Page 18 of 31
Unsupported features and limitations when using mobile and remote
access
access
n
Secure XMPP traffic between VCS Control and IM&P servers (XMPP traffic is secure between VCS
Control and VCS Expressway, and between VCS Expressway and remote endpoint)
Control and VCS Expressway, and between VCS Expressway and remote endpoint)
n
Endpoint management capability (SNMP, SSH/HTTP access)
n
Multi-domain and multi-customer support; each VCS deployment supports only one IM&P domain (even
though IM & Presence 10.0 or later supports multiple IM&P domains)
though IM & Presence 10.0 or later supports multiple IM&P domains)
n
Mobile and remote access functionality is not within the FIPS boundary
n
The VCS Control used for Mobile and Remote Access cannot also be used as a Lync 2013 gateway (if
required, this must be configured on a stand-alone VCS Control
required, this must be configured on a stand-alone VCS Control
n
NTLM authentication via the HTTP proxy
n
Maintenance mode; if a VCS Control or VCS Expressway is placed into maintenance mode, any existing
calls passing through that VCS will be dropped
calls passing through that VCS will be dropped
n
The VCS Expressway must not have TURN services enabled
n
Deployments on Large VM servers are limited to 2500 proxied registrations to Unified CM (the same limit
as VCS appliances or equivalent VM)
as VCS appliances or equivalent VM)
Supported clients when using mobile and remote access
n
Cisco Jabber for Windows 9.7 or later
n
Cisco Jabber for iPhone and iPad 9.6.1 or later
n
Cisco Jabber for Android 9.6 or later
n
Cisco Jabber for Mac 9.6 or later
n
Cisco TelePresence endpoints/codecs running TC7.0.1 or later firmware
Interoperability
, where you
can also find interoperability test results for other Cisco TelePresence products.
Updating to X8.2.2
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
you use OCS Relay you must migrate to using the Microsoft Lync B2BUA to route SIP calls between the