Cisco Cisco TelePresence Video Communication Server Expressway
Unsupported Endpoint Features when Using Mobile and Remote Access
■
Calls to/from additional lines on IP phones and endpoints that support multiple lines; only the primary line is
supported via Mobile and Remote Access.
supported via Mobile and Remote Access.
■
Directory access mechanisms other than UDS.
■
Certificate provisioning to remote endpoints e.g. CAPF.
■
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.
not work correctly via MRA.
■
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 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 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.
VCS Limitations and Unsupported Features when Using Mobile and Remote Access
■
The VCS cannot be used for Jabber Guest when it is used for MRA.
■
The VCS Control used for Mobile and Remote Access cannot also be used for Microsoft Interoperability.
Microsoft Interoperability requires a dedicated VCS Control.
Microsoft Interoperability requires a dedicated 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 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 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.
currently recommend that you do not exceed 50 domains.
■
NTLM authentication via the HTTP proxy.
■
Maintenance mode; if the VCS Control or the 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.
■
The 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
VCS appliances or equivalent VM).
VCS appliances or equivalent VM).
Protocol Summary
The table below lists the protocols and associated services used in the Unified Communications solution.
46
Mobile and Remote Access Through Cisco Video Communication Server Deployment Guide
Additional Information