Cisco Cisco Expressway
Unsupported Jabber features when using mobile and remote access
n
Directory access mechanisms other than UDS
n
Certificate provisioning to remote endpoints e.g. CAPF
n
File transfer (except when operating in hybrid Webex mode)
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 features and limitations when using mobile and remote
access
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; each Expressway deployment supports only one IM&P domain
(even though IM & Presence 10.0 or later supports multiple IM&P domains). As of X8.5, you can create
additional deployments on the Expressway-C, but this feature is still limited to one domain per deployment.
(even though IM & Presence 10.0 or later supports multiple IM&P domains). As of X8.5, you can create
additional deployments on the Expressway-C, but this feature is still limited to one domain per deployment.
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).
Protocol summary
The table below lists the protocols and associated services used in the Unified Communications solution.
Protocol
Security
Service
SIP
TLS
Session establishment – Register, Invite etc.
HTTPS
TLS
Logon, provisioning/configuration, directory, visual voicemail
RTP
SRTP
Media - audio, video, content sharing
XMPP
TLS
Instant Messaging, Presence
Unified Communications Mobile and Remote Access via Cisco Expressway Deployment Guide (X8.5)
Page 41 of 50
Additional information