Tandberg Data N3 - Manual (Page 21)

15
xConfiguration Links Link [1..100] Pipe2 Name
Each subzone may be configured with its own bandwidth limits. Calls placed between two
endpoints in the same subzone consume resource from the subzone
’
s allocation. Subzone
bandwidths are configured on the Gatekeeper Configuration > SubZones page (see Figure 6
for a screenshot of the configuration) or using the following command line commands:
xConfiguration SubZones SubZone [1..100] Bandwidth TotalMode
xConfiguration SubZones SubZone [1..100] Bandwidth Total Limit
xConfiguration SubZones SubZone [1..100] Bandwidth PerCall Mode
xConfiguration SubZones SubZone [1..100] Bandwidth PerCall Limit
When calls are placed between endpoints in different subzones, it is possible to control the
bandwidth used on the link between them. To do this, create a pipe and configure it with the
required bandwidth characteristics. This pipe is then assigned to a link. Calls traversing the
link will now take the pipe
’
s bandwidth allocation into consideration. Pipes are created and
configured on the Gatekeeper Configuration > Pipes page (see Figure 7 for a screenshot of
the Pipe Configuration) or using the following command line commands:
xConfiguration Pipes Pipe [1..100] Name
xConfiguration Pipes Pipe [1..100] Bandwidth Total Mode
xConfiguration Pipes Pipe [1..100] Bandwidth Total Limit
xConfiguration Pipes Pipe [1..100] Bandwidth PerCall Mode
xConfiguration Pipes Pipe [1..100] Bandwidth PerCall Limit
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 a 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 section 3.9, URI Dialing).
These Gatekeepers, and any unregistered endpoints reached by dialing their IP address, are
placed in the Default Zone.
If bandwidth control is in use, there are two possible behaviors when a call cannot be placed
at the bandwidth requested. By default the call will be connected at a reduced bandwidth
(down-speeding), assuming that there is some bandwidth still available. Optionally the call
may be rejected if it cannot be placed at the requested bandwidth. This option is controlled
through the web interface of the Gatekeeper by navigating to Gatekeeper Configuration >
Gatekeeper (for a screenshot of these settings, see Figure 8) or through the following
command line instructions:
xConfiguration Gatekeeper Downspeed PerCall Mode: <On/Off>
xConfiguration Gatekeeper Downspeed Total Mode: <On/Off>