Zone Configuration; Configuring Neighbor Zones - Cisco TelePresence Administrator's Manual

Zone configuration

The Zones page (VCS configuration > Zones >
VCS, and lets you create, edit and delete zones (.
It also displays the zone's H.323 or SIP connection status:
Off: the protocol is disabled at either the zone or system level
n
Active: the protocol is enabled for that zone and it has at least one active connection; if multiple
n
connections are configured and some of those connections have failed, the display indicates how many of
the connections are Active
On: applies to DNS and ENUM zones only and indicates that the protocol is enabled for that zone
n
Failed: the protocol is enabled for that zone but its connection has failed
n
Checking: the protocol is enabled for that zone and the system is currently trying to establish a connection
n
To neighbor with another system (such as another VCS 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 VCS. The available zone types are:
Neighbor: connects the local VCS to a neighbor system
n
Traversal client: connects the local VCS to a traversal server
n
Traversal server: connects the local VCS Expressway to a traversal client
n
ENUM: enables ENUM dialing via the local VCS
n
DNS: enables the local VCS to locate endpoints and other systems by using DNS lookups
n
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.
The VCS also has a pre-configured
endpoints or other devices that are unregistered or not recognized as belonging to the Local Zone or any of
the existing configured zones.
Note that connections between the VCS 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. In software
versions prior to X5.1 a connection could be established if one system was configured to use TLS and the
other used TCP. Any connection failures due to transport type mismatches are recorded in the Event Log.
After creating a zone you would normally make it a target of at least one of your zone policy
(VCS configuration > Dial plan > Search

Configuring neighbor zones

A neighbor zone could be a collection of endpoints registered to another system (such as a VCS,
Gatekeeper, or Border Controller), or it could be a SIP device (for example Microsoft Office Communications
Server (OCS) 2007 / Lync 2010). 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 VCS.
After you have added it, you can:
Cisco VCS Administrator Guide (X7.2)
Zones) lists all the zones that have been configured on the
Default Zone. The Default Zone represents any incoming calls from
rules) otherwise search requests will not be sent to that zone.
Zones and neighbors
search rules
Page 132 of 498