Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
■
Off: the protocol is disabled at either the zone or system level
■
Active: the protocol is enabled for that zone and it has at least one active connection; if multiple connections
are configured and some of those connections have failed, the display indicates how many of the connections
are Active
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
■
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 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:
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:
■
: connects the local VCS to a neighbor system
■
: connects the local VCS to a traversal server
■
: connects the local VCS Expressway to a traversal client
■
: enables ENUM dialing via the local VCS
■
: enables the local VCS 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 unregistered or not recognized as belonging to the Local Zone or any of the existing configured
zones.
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.
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.
(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 another 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 VCS. After you
have added it, you can:
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 VCS and the neighbor zone
Note that:
■
neighbor zone relationship definitions are one-way; adding a system as a neighbor to your VCS does not
automatically make your VCS a neighbor of that system
automatically make your VCS 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:
144
Cisco TelePresence Video Communication Server Administrator Guide