Filter
Top Products
TANDBERG Gatekeeper User Guide
Page 32 of 105
Figure 11: Configuring a pipe
Pipes may be shared between one or more links. This is used to model the situation where a site
communicates with several other sites over the same broadband connection to the Internet. Each link
may have up to two pipes associated with it. This is useful for modeling two sites, each with their own
broadband connection to the Internet backbone. Calls between zones or subzones consume bandwidth
from each zone and any pipes on the link between them.
When a Gatekeeper is neighbored with another Gatekeeper or Border Controller, the neighbor is placed
in its own zone. This allows you to control the bandwidth used by calls to and from endpoints controlled
by the other Gatekeeper. Sometimes you may place and receive calls to Gatekeepers you are not
neighbored with (see URI Dialing, section 9). These Gatekeepers, and any unregistered endpoints
reached by dialing their IP address, are placed in the Default Zone.
7.3. Insufficient Bandwidth
7.3.1. Insufficient bandwidth
If bandwidth control is in use, there may be situations when there is insufficient bandwidth available to
place a call at the requested rate. By default (and assuming that there is some bandwidth still available)
the Gatekeeper will still attempt to connect the call, but at a reduced bandwidth - known as
downspeeding .
You can prevent the downspeeding of calls by navigating to Gatekeeper Configuration > Gatekeeper and
in the Downspeeding section, clearing the relevant boxes (see Figure 12). You can also control whether
or not calls are downspeeded through the following commands:
xConfiguration Gatekeeper Downspeed PerCall Mode: <On/Off>
xConfiguration Gatekeeper Downspeed Total Mode: <On/Off>
If downspeeding has been disallowed and there is insufficient bandwidth to place the call at the
originally requested rate, the call will not be placed.