Cisco Cisco Expressway Maintenance Manual
■
Failed: the protocol is enabled for that zone but its connection has failed
■
Checking: the protocol is enabled for that zone and the system is currently trying to establish a connection
To neighbor with another system (such as another Expressway or gatekeeper), create a connection over a firewall to
a traversal server or traversal client, or discover endpoints via an ENUM or DNS lookup, you must configure a zone on
the local Expressway. The available zone types are:
a traversal server or traversal client, or discover endpoints via an ENUM or DNS lookup, you must configure a zone on
the local Expressway. The available zone types are:
■
: connects the local Expressway to a neighbor system
■
: connects the local Expressway to a traversal server
■
: connects the local Expressway-E to a traversal client
■
: enables ENUM dialing via the local Expressway
■
: enables the local Expressway to locate endpoints and other systems by using DNS lookups
The zone type indicates the nature of the connection and determines which configuration options are available. For
traversal server zones, traversal client zones and neighbor zones this includes providing information about the
neighbor system such as its IP address and ports.
traversal server zones, traversal client zones and neighbor zones this includes providing information about the
neighbor system such as its IP address and ports.
. The Default Zone represents any incoming calls from
endpoints or other devices that are not recognized as belonging to any of the existing configured zones.
Note that connections between the Expressway and neighbor systems must be configured to use the same SIP
transport type, that is they must both be configured to use TLS or both be configured to use TCP. Any connection
failures due to transport type mismatches are recorded in the Event Log.
transport type, that is they must both be configured to use TLS or both be configured to use TCP. Any connection
failures due to transport type mismatches are recorded in the Event Log.
(Configuration > Dial plan > Search rules) otherwise search requests will not be sent to that zone.
Configuring Neighbor Zones
A neighbor zone could be a collection of endpoints registered to another system (such as a Cisco VCS), or it could be
a SIP device (for example Cisco Unified Communications Manager). The other system or SIP device is referred to as a
neighbor. Neighbors can be part of your own enterprise network, part of a separate network, or even standalone
systems.
a SIP device (for example Cisco Unified Communications Manager). The other system or SIP device is referred to as a
neighbor. Neighbors can be part of your own enterprise network, part of a separate network, or even standalone
systems.
You create a neighbor relationship with the other system by adding it as a neighbor zone on your local Expressway.
After you have added it, you can:
After you have added it, you can:
■
query the neighbor about its endpoints
■
apply transforms to any requests before they are sent to the neighbor
■
control the bandwidth used for calls between your local Expressway and the neighbor zone
Note that:
■
neighbor zone relationship definitions are one-way; adding a system as a neighbor to your Expressway does
not automatically make your Expressway a neighbor of that system
not automatically make your Expressway a neighbor of that system
■
inbound calls from any configured neighbor are identified as coming from that neighbor
■
systems that are configured as cluster peers (formerly known as Alternates) must not be configured as
neighbors to each other
neighbors to each other
The configurable options for a neighbor zone are:
Field
Description
Usage tips
Configuration section:
Name
The name acts as a unique identifier, allowing you
to distinguish between zones of the same type.
to distinguish between zones of the same type.
103
Cisco Expressway Administrator Guide