The collection of all endpoints, gateways, MCUs and Content Servers registered with the VCS
make up its Local Zone.
The Local Zone is made up of subzones. These include an automatically created Default Subzone
and up to 100 manually configurable subzones. Each manually configured subzone specifies a
range of IP addresses. When an endpoint registers with the VCS it is allocated to the appropriate
subzone based on its IP address. If the endpoint’s IP address does not match any of the
subzones, it is assigned to the Default Subzone.
Subzones are used for the purposes of bandwidth management. Once 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.

The VCS also has a special type of subzone known as the Traversal Subzone. This is a conceptual
subzone; no endpoints can be registered to it, but all traversal calls (i.e. calls for which the VCS is
taking the media in addition to the signaling) must pass through it. The Traversal Subzone exists
in order to allow you to control the amount of bandwidth used by traversal calls, as these can be
particularly resource-intensive.
The Local Zone may be independent of network topology, and may be comprised of multiple
network segments.

•
•

•

Local Zone and Subzones

Configuring the Local Zone and its Subzones

The Local Zone and its subzones exist for the purposes of bandwidth management. For full details
of how to create and configure subzones, and apply bandwidth limitations to these and the Default
Subzone and Traversal Subzone, see the section on

Bandwidth Control

TANDBERG

VIDEO COMMUNICATION SERVER

ADMINISTRATOR GUIDE

Advertising

Popular Brands

Popular manuals