Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
65
D14049.08
November 2010
November 2010
Grey Headline (continued)
CISCO TELEPRESENCE
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Zones
A zone is a collection of endpoints, either all
registered to a single system (for example a
Cisco VCS, gatekeeper, or Border Controller), or
located in a certain way such as via an ENUM
or DNS lookup.
Zones are used to:
registered to a single system (for example a
Cisco VCS, gatekeeper, or Border Controller), or
located in a certain way such as via an ENUM
or DNS lookup.
Zones are used to:
•
control through links whether calls can be
made between your local subzones and
these other zones
made between your local subzones and
these other zones
•
manage the bandwidth of calls between your
local subzones and endpoints in other zones
local subzones and endpoints in other zones
•
search for aliases that are not registered
locally
locally
You can configure up to 1000 zones of five
different types. The VCS also has a non-
configurable Default Zone.
See the
different types. The VCS also has a non-
configurable Default Zone.
See the
sections for
section for information on including zones
as targets for search rules.
About zones
To traverse a firewall, the VCS must be
connected with a traversal server (for example
a VCS Expressway or a TANDBERG Border
Controller).
In this situation your local VCS is a traversal
client, so you create a connection with the
traversal server by creating a traversal client
zone on your local VCS. You then configure the
client zone with details of the corresponding
zone on the traversal server. (The traversal
server must also be configured with details of
the VCS client zone.)
After you have neighbored with the traversal
server you can:
connected with a traversal server (for example
a VCS Expressway or a TANDBERG Border
Controller).
In this situation your local VCS is a traversal
client, so you create a connection with the
traversal server by creating a traversal client
zone on your local VCS. You then configure the
client zone with details of the corresponding
zone on the traversal server. (The traversal
server must also be configured with details of
the VCS client zone.)
After you have neighbored with the traversal
server you can:
•
use the neighbor as a traversal server
•
query the traversal server about its
endpoints
endpoints
•
apply transforms to any queries before they
are sent to the traversal server
are sent to the traversal server
•
control the bandwidth used for calls
between your local VCS and the traversal
server
between your local VCS and the traversal
server
See the
section for information on the specific
configuration options available.
configuration options available.
A VCS Expressway is able to act as a traversal
server, providing firewall traversal on behalf of
traversal clients (for example, VCS Controls or
gatekeepers).
In order to act as a traversal server, the
VCS Expressway must have a special type
of two-way relationship with each traversal
client. To create this connection, you create
a traversal server zone on your local VCS
Expressway and configure it with the details of
the corresponding zone on the traversal client.
(The client must also be configured with details
of the VCS Expressway.)
After you have neighbored with the traversal
client you can:
server, providing firewall traversal on behalf of
traversal clients (for example, VCS Controls or
gatekeepers).
In order to act as a traversal server, the
VCS Expressway must have a special type
of two-way relationship with each traversal
client. To create this connection, you create
a traversal server zone on your local VCS
Expressway and configure it with the details of
the corresponding zone on the traversal client.
(The client must also be configured with details
of the VCS Expressway.)
After you have neighbored with the traversal
client you can:
•
provide firewall traversal services to the
traversal client
traversal client
•
query the traversal client about its
endpoints
endpoints
•
apply transforms to any queries before they
are sent to the traversal client
are sent to the traversal client
•
control the bandwidth used for calls
between your local VCS and the traversal
client
between your local VCS and the traversal
client
See the
section for information on the specific
configuration options available.
configuration options available.
Traversal client-server zone relationships must be two-way. For firewall traversal to work, the
traversal server and the traversal client must each be configured with the other’s details.
(See the
traversal server and the traversal client must each be configured with the other’s details.
(See the
section for more information.)
The client and server will then be able to communicate over the firewall and query each
other.
other.
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).
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:
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).
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:
•
query the neighbor about its endpoints
•
apply transforms to any requests before
they are sent to the neighbor
they are sent to the neighbor
•
control the bandwidth used for calls
between your local VCS and the neighbor
zone
between your local VCS and the neighbor
zone
See the
section
for information on the specific configuration
options available.
options available.
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.
are one-way. Adding a system as a
neighbor to your VCS does not
automatically make your VCS a
neighbor of that system.
Inbound calls from any configured
neighbor are identified as coming from
that neighbor.
neighbor are identified as coming from
that neighbor.
Traversal client zone
Traversal server zone
Neighbor zone