Cisco Cisco Expressway
Introduction
This deployment guide provides guidelines on how to configure the Cisco Expressway (Expressway) version X8.7 and
Cisco Unified Communications Manager (Unified CM) versions 8.6.x and 9.x to interwork via a SIP trunk.
Cisco Unified Communications Manager (Unified CM) versions 8.6.x and 9.x to interwork via a SIP trunk.
Deployment Scenario
A company already has Unified CM running their telephone/video system. They want to integrate this via a SIP trunk to
an Expressway-C to provide further services such as integration with Jabber Guest servers or another Expressway
managing integration to Microsoft Lync.
an Expressway-C to provide further services such as integration with Jabber Guest servers or another Expressway
managing integration to Microsoft Lync.
For the purposes of this example, the existing Unified CM system uses telephone (digit-only) numbers to specify who to
call:
call:
■
Endpoints connected to the Unified CM are identified by 3xxx extension numbers.
■
Endpoints and systems that are contacted via the Expressway-C are identified by 4xxx extension numbers.
Note that more complicated dial plans can also be supported, including alphanumeric dialing; they would require
additional transforms/routing configuration.
additional transforms/routing configuration.
Unified CM and the Expressway-C are connected together using a SIP trunk across an IP network; the Expressway-C
domain is exp.domain. Calls sent to Unified CM will have the domain portion set to the Expressway domain; calls from
Unified CM to Expressway will arrive with the domain portion set as <FQDN of Expressway>:5060 for TCP and <FQDN
of Expressway>:5061 for TLS.
domain is exp.domain. Calls sent to Unified CM will have the domain portion set to the Expressway domain; calls from
Unified CM to Expressway will arrive with the domain portion set as <FQDN of Expressway>:5060 for TCP and <FQDN
of Expressway>:5061 for TLS.
This guide specifies how to configure both the Unified CM and the Expressway-C so that SIP calls can be routed
between each system. It does not describe how to configure the onward routing, such as additional neighbor zones from
the Expressway to other systems (such as another Expressway, Jabber Guest servers or a Cisco VCS).
between each system. It does not describe how to configure the onward routing, such as additional neighbor zones from
the Expressway to other systems (such as another Expressway, Jabber Guest servers or a Cisco VCS).
Initially the configuration use non-secure TCP connections, as this allows for easier troubleshooting. It then describes
how to secure the video network over TLS.
how to secure the video network over TLS.
3
Cisco Expressway SIP Trunk to Unified CM Deployment Guide