Cisco Cisco Expressway Release Notes
Limitations
Unified Communications Cisco Expressway Series Software Release Notes (X8.5.3)
Page 10 of 23
n
If you prefer single-server certificate distribution, modify the Common Name of the Tomcat certificate on
each node so that the value differs from its fully qualified domain name (FQDN).
This ensures that the FQDN of the server is correctly added as a Subject Alternate Name to that
certificate.
each node so that the value differs from its fully qualified domain name (FQDN).
This ensures that the FQDN of the server is correctly added as a Subject Alternate Name to that
certificate.
Limitations
Unsupported features (general)
n
DTLS is not supported through the Expressway-C/Expressway-E. SRTP is used to secure calls instead;
attempts to make DTLS calls will fail.
attempts to make DTLS calls will fail.
n
SIP UPDATE method. Features that rely on the SIP UPDATE method (
) will not work as
expected because the Expressway does not support this method.
n
Audio calls may be licensed as video calls in some circumstances. Calls that are strictly audio-ONLY
consume fewer licenses than video calls. However, when audio calls include non-audio channels, such as
the iX channel that enables ActiveControl, they are treated as video calls for licensing purposes.
consume fewer licenses than video calls. However, when audio calls include non-audio channels, such as
the iX channel that enables ActiveControl, they are treated as video calls for licensing purposes.
Unsupported endpoint features when using mobile and remote access
Note: This list contains known limitations and is not exhaustive. The MRA deployment does not necessarily
support pass through of line-side features provided by Cisco Unified Communications Manager. Absence of
such items from this list does not imply that they are supported.
support pass through of line-side features provided by Cisco Unified Communications Manager. Absence of
such items from this list does not imply that they are supported.
n
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
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.