You can apply bandwidth limits to the Default Subzone, Traversal Subzone and all manually
configured subzones. The types of limitations you can apply vary depending on the type of
subzone, as follows:

Limitation

Description

Can be applied to

Total

Limits the total concurrent bandwidth being
used by all endpoints in the subzone at any
one time.

Default Subzone
Traversal Subzone
Manually configured subzones

•
•
•

Per call intra Limits the bandwidth of any individual call

between two endpoints within the subzone.

Default Subzone
Manually configured subzones

•
•

Per call inter Limits the bandwidth of any individual call

between an endpoint in the subzone, and an
endpoint in another subzone or zone.

Default Subzone
Traversal Subzone
Manually configured subzones

•
•
•

For all these settings, a

bandwidth mode

of:

None

will mean that no bandwidth is allocated and therefore no calls can be made.

Limited

will mean that limits are applied. You must also enter a value in the corresponding

bandwidth (kbps)

field.

Unlimited

will mean that no restrictions will be applied to the amount of bandwidth being used.

•
•

•

Use subzone bandwidth limits if you want to configure the bandwidth available between one
specific subzone and all other subzones or zones.
Use

Pipes

if you want to configure the bandwidth available between one specific subzone

and another specific subzone or zone.
If your bandwidth configuration is such that multiple types of bandwidth restrictions are placed on
a call (for example, if there are both subzone bandwidth limits and pipe limits), the lowest limit will
always apply to that call.

How Different Bandwidth Limitations are Managed

In situations where there are differing bandwidth limitations applied to the same link, the lower
limit will always be the one used when routing the call and taking bandwidth limitations into
account.
For example, Subzone A may have a per call inter bandwidth of 128. This means that any
calls between Subzone A and any other subzone or zone will be limited to 128kbps. However,
Subzone A also has a link configured between it and Subzone B. This link uses a pipe with a
limit of 512kbps. In this situation, the lower limit of 128kbps will apply to calls between the two,
regardless of the larger capacity of the pipe.
In the reverse situation, where Subzone A has a per call inter bandwidth limit of 512kbps and a
link to Subzone B with a pipe of 128, any calls between the two subzones will still be limited to
128kbps.

Applying Bandwidth Limitations to Subzones

A non-traversal call between two endpoints within the same subzone would consume the
amount of bandwidth of that call. A traversal call between two endpoints within the same
subzone must, like any other traversal call, pass through the Traversal Subzone. This

means that such calls will consume from the originating subzone’s total concurrent allocation
twice the bandwidth of the call – once for the call from the subzone to the Traversal Subzone, and
again for the call from the Traversal Subzone back to the originating subzone.

Calls passing through the Traversal Subzone consume an amount of bandwidth within the
subzone equal to that of the call.

TANDBERG

VIDEO COMMUNICATION SERVER

ADMINISTRATOR GUIDE

Bandwidth Control

Advertising

Popular Brands

Popular manuals