Table of Contents
Advertisement
Grey Headline (continued)
Subzones
Types of Limitations
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
Total
Limits the total concurrent bandwidth being
used by all endpoints in the subzone at
any one time. In the case of the Traversal
Subzone, this is the maximum bandwidth
available for all concurrent traversal calls.
Calls
Limits the bandwidth of any individual call
entirely
between two endpoints within the subzone.
within...
Calls into
Limits the bandwidth of any individual call
our out of...
between an endpoint in the subzone, and an
endpoint in another subzone or zone.
Calls
The maximum bandwidth available to any
handled
individual traversal call.
by...
For all these settings, a
bandwidth mode
•
NoBandwidth
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.
Overview and
Introduction
Getting Started
Status
D14049.04
JULY 2008
Applying Bandwidth Limitations to Subzones
Can be applied to
•
Default Subzone
•
Traversal Subzone
•
Manually configured subzones
•
Default Subzone
•
Manually configured subzones
•
Default Subzone
•
Manually configured subzones
•
Traversal Subzone
of:
System
VCS
Configuration
Configuration
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.
A
non-traversal call
that subzone the amount of bandwidth of that call. A
within the same subzone must, like all traversal call, pass through the Traversal Subzone.
This means that such calls will consume an amount of bandwidth from the originating subzone's
total concurrent allocation that is equal to 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.
In addition, since this call passes through the Traversal Subzone, it will consume an amount of
bandwidth from the Traversal Subzone equal to that of the call.
Zones and
Call
Bandwidth
Neighbors
Processing
Control
139
TANDBERG
VIDEO COMMUNICATIONS SERVER
between two endpoints within the same subzone would consume from
traversal call
Firewall
Applications
Traversal
ADMINISTRATOR GUIDE
between two endpoints
Maintenance
Appendices
Advertisement
Table of Contents
