Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Limitations
Cisco TelePresence Video Communication Server Software Release Notes (X8.5.1)
Page 8 of 23
n
Directory access mechanisms other than UDS
n
Certificate provisioning to remote endpoints e.g. CAPF
n
Features that rely on the SIP UPDATE method (
) will not work as expected because the VCS
does not support this method. For example, CUCM and endpoints use UPDATE to implement blind
transfer, which does not work correctly via MRA.
transfer, which does not work correctly via MRA.
n
Peer-to-peer file transfer when using IM and Presence Service and Jabber is unsupported via MRA
l
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
later) clients is supported via MRA
l
File transfer with WebEx Messenger Service and Cisco Jabber is supported via MRA
n
Deskphone control (QBE/CTI)
n
Additional mobility features including DVO-R, GSM handoff and session persistency
n
Hunt group/hunt pilot/hunt list
n
Self-care portal
n
Support for Jabber SDK
n
Shared lines are supported in a limited way. Multiple endpoints can share a line but in-call features (like
hold/resume) only work on the first endpoint that answers. Endpoints sharing the line may not correctly
recognise the state of the call.
hold/resume) only work on the first endpoint that answers. Endpoints sharing the line may not correctly
recognise the state of the call.
Unsupported VCS features and limitations when using mobile and
remote access
remote access
n
The VCS cannot be used for Jabber Guest when it is used for MRA.
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 is limited as follows:
l
Prior to X8.5, each 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).
l
As of X8.5, you can create multiple deployments on the VCS Control, but this feature is still limited to
one domain per deployment.
one domain per deployment.
l
As of X8.5.1, a deployment can have Multiple Presence Domains. This feature is in preview with X8.5.1,
and we currently recommend that you do not exceed 10 domains.
and we currently recommend that you do not exceed 10 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).