TANDBERG Gatekeeper - Manual (Page 30)

TANDBERG Gatekeeper User Guide
Page 30 of 105
7. Bandwidth Control
7.1. About Bandwidth Control
The TANDBERG Gatekeeper allows you to control endpoints' use of bandwidth on your network.
Figure 9 shows a typical network deployment: a broadband LAN, where high bandwidth calls are
acceptable; a pipe to the internet with restricted bandwidth; and two satellite offices, each with their own
restricted pipes.
In order to utilize the available bandwidth efficiently, the TANDBERG Gatekeeper allows you to model
your network, and bandwidth controls on individual components of the network. Bandwidth controls may
be set on a call-by-call basis and on a total concurrent usage basis.
Figure 9: Typical network deployment
7.2. Subzones
All endpoints registered with your Gatekeeper are part of its local zone. As shown in Figure 9, the local
zone can contain two or more different networks with different bandwidth limitations. In order to model
this, the local zone is made up of one or more subzones. When an endpoint registers with the
Gatekeeper it is assigned to a subzone, based on its IP address.
By default all endpoints registering with the Gatekeeper are assigned to the default subzone. This is
suitable if you have uniform bandwidth available between all your endpoints. When you have differing
bandwidth provision, as in Figure 9, you should create a new subzone for each pool of endpoints. Each
subzone you create can include up to 5 subnets (based on a specified range of IP addresses).
Subzones are added and configured using the web interface via
Gatekeeper Configuration >. SubZones ,
and the either selecting Add New SubZone , or highlighting an existing subzone and selecting Edit . This
will take you to the screen shown in Figure 10. You can also add and configure subzones using the
following commands:
xConfiguration SubZones SubZone [1..100] Name
xConfiguration SubZones SubZone [1..100] Subnet [1..5] IP Prefixlength
xConfiguration SubZones SubZone [1..100] Subnet [1..5] IP Address