TANDBERG D14049.04, Administrator'S Manual

Page: 63 / 296

63
D14049.07
March 2010
Grey Headline (continued)
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Introduction
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Clustering and
peers
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications Maintenance
Local Zone and subzones
The collection of all endpoints, gateways, MCUs and Content
Servers registered with the VCS make up its
Local Zone .
The Local Zone is divided into subzones . These include an
automatically created Default Subzone and up to 1000 manually
configurable subzones.
When an endpoint registers with the VCS it is allocated to an
appropriate subzone based on
subzone membership rules
.
These rules specify the range of IP addresses or alias pattern
matches for each subzone. If an endpoint’s IP address or alias
does not match any of the membership rules, it is assigned to
the Default Subzone.
The Local Zone may be independent of network topology, and
may comprise multiple network segments.
The VCS also has two special types of subzones:
•
the
Traversal Subzone
, which is always present (see the
About the Traversal Subzone section for more information)
•
the Cluster Subzone , which is always present but only used
when your VCS is part of a cluster (see the Cluster Subzone
section for more information)
Overview
Bandwidth management
The Local Zone’s subzones are used for bandwidth management.
After you have set up your subzones you can apply bandwidth
limits to:
•
individual calls between two endpoints within the subzone
•
individual calls between an endpoint within the subzone and
another endpoint outside of the subzone
•
the total of calls to or from endpoints within the subzone
For full details of how to create and configure subzones, and
apply bandwidth limitations to subzones including the Default
Subzone and Traversal Subzone, see the chapter on
Bandwidth
control .
Local Zone searches
One of the functions of the VCS is to route a call received from
a locally registered endpoint or external zone to its appropriate
destination. Calls are routed based on the address or alias of the
destination endpoint.
When searching for a destination endpoint, the VCS searches
its Local Zone and external zones. You can prioritize the order in
which these zones are searched, and filter the search requests
sent to each zone, based on the address or alias being searched
for. This allows you to reduce the potential number of search
requests sent to the Local Zone and out to external zones, and
speed up the search process.
For further information on how to configure search rules for the
Local Zone, see the
Configuring search and zone transform rules
section.
Configuring the Local Zone and its subzones