Cisco Cisco Expressway Release Notes
Limitations
Unified Communications Cisco Expressway Series Software Release Notes (X8.5.1)
Page 8 of 19
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
Expressway does not support this method. For example, CUCM and endpoints use UPDATE to implement
blind transfer, which does not work correctly via MRA.
blind 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 Expressway features and limitations when using mobile
and remote access
and remote access
n
The Expressway cannot be used for Jabber Guest when it is used for MRA.
n
Secure XMPP traffic between Expressway-C and IM&P servers (XMPP traffic is secure between
Expressway-C and Expressway-E, and between Expressway-E and remote endpoint).
Expressway-C and Expressway-E, and between Expressway-E 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 Expressway deployment supported only one IM&P domain (even though IM and
Presence Service 10.0 or later supports Multiple Presence Domains).
Presence Service 10.0 or later supports Multiple Presence Domains).
l
As of X8.5, you can create multiple deployments on the Expressway-C, 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
The Expressway-C 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 Expressway-C.
required, this must be configured on a stand-alone Expressway-C.
n
NTLM authentication via the HTTP proxy.
n
Maintenance mode; if an Expressway-C or Expressway-E is placed into maintenance mode, any existing
calls passing through that Expressway will be dropped.
calls passing through that Expressway will be dropped.
n
The Expressway-E 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 Small / Medium VM servers).
as Small / Medium VM servers).
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