Cisco Cisco Expressway
This means that you cannot use Expressway-E to give Mobile and Remote Access to endpoints that must traverse a
nested perimeter network to call internal endpoints.
nested perimeter network to call internal endpoints.
Expressway-C in DMZ with Static NAT
We do not support Expressway-C in a DMZ that uses static NAT. This is because the Expressway-C does not perform
the SDP rewriting that is required to traverse static NAT-enabled firewalls. You should use the Expressway-E for this
purpose.
the SDP rewriting that is required to traverse static NAT-enabled firewalls. You should use the Expressway-E for this
purpose.
You could potentially place the Expressway-C in a DMZ that does not use static NAT, but we strongly discourage this
deployment because it requires a lot of management on the inmost firewall. We always recommend placing the
Expressway-C in the internal network.
deployment because it requires a lot of management on the inmost firewall. We always recommend placing the
Expressway-C in the internal network.
Configuration Overview
This section summarizes the steps involved in configuring your Unified Communications system for mobile and remote
access. It assumes that you already have set up:
access. It assumes that you already have set up:
■
the Expressway-E in the DMZ)
■
Unified CM and IM and Presence Service have been configured as specified in Configuration and
Administration of IM and Presence Service on Cisco Unified Communications Manager (for your version), at
Administration of IM and Presence Service on Cisco Unified Communications Manager (for your version), at
Prerequisites
■
Expressway X8.1.1 or later (this document assumes X8.8.3)
■
Unified CM 9.1(2)SU4
‡
or later
13
Mobile and Remote Access Through Cisco Expressway Deployment Guide
Configuration Overview