Cisco Cisco Expressway Release Notes
Limitations
Unsupported Features (General)
■
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.
■
SIP UPDATE method. Features that rely on the SIP UPDATE method (
) will not work as expected
because the Expressway does not support this method.
■
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.
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.
this list does not imply that they are supported.
■
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 Expressway
does not support this method. For example, CUCM and endpoints use UPDATE to implement blind transfer,
which does not work correctly via MRA.
which does 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 Expressway 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 Expressway 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.
Unsupported Expressway Features and Limitations When Using Mobile and Remote
Access
Access
■
The Expressway cannot be used for Jabber Guest when it is used for MRA.
■
The Expressway-C used for Mobile and Remote Access cannot also be used for Microsoft Interoperability.
Microsoft Interoperability requires a dedicated Expressway-C.
Microsoft Interoperability requires a dedicated Expressway-C.
■
MRA is not supported in IPv6 only mode.
■
Endpoint management capability (SNMP, SSH/HTTP access).
13
Cisco Expressway Series Release Notes
Limitations