Cisco Cisco Expressway
4. If Unified CM servers (
System > Server
) are configured by Host Name (rather than IP address), then
ensure that those host names are resolvable by the Expressway-C. Note that server names configured as
fully qualified host names (FDQNs) are not supported.
fully qualified host names (FDQNs) are not supported.
5. 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).
6. Ensure that the Cisco AXL Web Service is active on the Unified CM publishers you will be using to
discover the Unified CM servers that are to be used for remote access. To check this, select the
Cisco
Unified Serviceability
application and go to
Tools > Service Activation
.
7. We recommend that remote and mobile devices are configured (either directly or by Device Mobility) to
use publicly accessible NTP servers.
a. Configure a public NTP server
System > Phone NTP Reference
.
b. Add the Phone NTP Reference to a Date/Time Group (
System > Date/Time Group
).
c. Assign the Date/Time Group to the Device Pool of the endpoint (
System > Device Pool
).
IM and Presence
Ensure that the Cisco AXL Web Service is active on the IM&P publishers you will be using to discover the
IM&P servers that are to be used for remote access. To check this, select the
IM&P servers that are to be used for remote access. To check this, select the
Cisco Unified Serviceability
application and go to
Tools > Service Activation
.
Expressway
The following steps summarize the configuration required on the Expressway-E and the Expressway-C. Full
details are described in section
details are described in section
Unified Communications: Mobile and Remote Access via Cisco Expressway Deployment Guide (X8.1.1)
Page 12 of 36
Configuration overview