Cisco Cisco Expressway
The Expressway neighbor zones to Unified CM use the names of the Unified CM nodes that were returned by Unified
CM when the Unified CM publishers were added (or refreshed) to the Expressway. The Expressway uses those
returned names to connect to the Unified CM node. If that name is just the host name then:
CM when the Unified CM publishers were added (or refreshed) to the Expressway. The Expressway uses those
returned names to connect to the Unified CM node. If that name is just the host name then:
■
it needs to be routable using that name
■
this is the name that the Expressway expects to see in the Unified CM's server certificate
If you are using secure profiles, ensure that the root CA of the authority that signed the Expressway-C certificate is
installed as a CallManager-trust certificate (Security > Certificate Management in the Cisco Unified OS
Administration application).
installed as a CallManager-trust certificate (Security > Certificate Management in the Cisco Unified OS
Administration application).
Media Encryption
Media encryption is enforced on the call legs between the Expressway-C and the Expressway-E, and between the
Expressway-E and endpoints located outside the enterprise.
Expressway-E and endpoints located outside the enterprise.
The encryption is physically applied to the media as it passes through the B2BUA on the Expressway-C.
Limitations
■
The IPV4 protocol only is supported for mobile and remote access users
■
In Expressway-E systems that use dual network interfaces, XCP connections (for IM&P XMPP traffic) always
use the non-external (i.e. internal) interface. This means that XCP connections may fail in deployments where
the Expressway-E internal interface is on a separate network segment and is used for system management
purposes only, and where the traversal zone on the Expressway-C connects to the Expressway-E's external
interface.
use the non-external (i.e. internal) interface. This means that XCP connections may fail in deployments where
the Expressway-E internal interface is on a separate network segment and is used for system management
purposes only, and where the traversal zone on the Expressway-C connects to the Expressway-E's external
interface.
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 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
■
Deskphone control (QBE/CTI)
■
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 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.
38
Mobile and Remote Access Through Cisco Expressway Deployment Guide
Additional Information