Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
■
Peer-to-peer file transfer when using IM and Presence Service and Jabber is unsupported via MRA
—
Managed File Transfer (MFT) with IM and Presence Service 10.5.2 (and later) and Jabber 10.6 (and later)
clients is supported via MRA
clients is supported via MRA
—
File transfer with WebEx Messenger Service and Cisco Jabber is supported via MRA
■
Jabber SDK, Jabber for Mac, and Jabber for Windows are not capable of deskphone control when they are
connected over MRA, because the CTI-QBE protocol is not traversed by the Cisco VCS pair. When these
Jabber applications, or other CTI applications, can connect to CUCM CTIManager (on-premises or VPN) then
they can deskphone control endpoints and clients that are connected over MRA.
connected over MRA, because the CTI-QBE protocol is not traversed by the Cisco VCS pair. When these
Jabber applications, or other CTI applications, can connect to CUCM CTIManager (on-premises or VPN) then
they can deskphone control endpoints and clients that are connected over MRA.
■
Additional mobility features including GSM handoff and session persistency.
■
Hunt group/hunt pilot/hunt list.
■
Self-care portal.
■
Support for Jabber SDK.
■
Shared lines are not supported on endpoints connected over MRA.
Some shared line features may work but are not supported.
Unsupported Cisco VCS Features and Limitations When Using Mobile and Remote
Access
Access
■
The Cisco VCS cannot be used for Jabber Guest when it is used for MRA.
■
The Cisco VCS Control used for Mobile and Remote Access cannot also be used for Microsoft Interoperability.
Microsoft Interoperability requires a dedicated Cisco VCS Control.
Microsoft Interoperability requires a dedicated Cisco VCS Control.
■
MRA is not supported in IPv6 only mode.
■
Endpoint management capability (SNMP, SSH/HTTP access).
■
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.
one 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.
currently recommend that you do not exceed 50 domains.
■
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
, where you can
also find interoperability test results for other Cisco TelePresence products.
Notable Interoperability Concerns
X8.7.n (and earlier versions) of Cisco VCS are not interoperable with Cisco Unified Communications Manager IM and
Presence Service 11.5(1).
Presence Service 11.5(1).
This is caused by a deliberate change in that version of IM and Presence Service, and there is a corresponding
change in Cisco VCS X8.8.
change in Cisco VCS X8.8.
15
Cisco TelePresence Video Communication Server Release Notes
Interoperability