D 14049.01
07.2007 110
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Bandwidth Control
Introduction Getting
Started
System
Overview
System
Configuration
H.323 & SIP
Configuration
Registration
Control
Zones and
Neighbors
Call
Processing
Firewall
Traversal
Bandwidth
Control Maintenance Appe ndices
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Bandwidth
Control
About Subzones
All endpoints registered wit h the VCS are part of its Local Zo ne.
The Local Zone is made up of two or mo re subzones. The
first two subzones are automa tically created for you. These
are the Default Subzone and the Traver sal Subzone. You can
create and configure furt her subzones manually on the basi s
of endpoints’ IP addresses: when a n endpoint registers with
the VCS its IP address is checked a nd it is assigned to the
appropriate subzone.
The main purpose of subzones is to ena ble you to control the
bandwidth used by various par ts of your network.
Bandwidth Consumption of Traversal Calls
Traversal calls between two endp oints within a single subzone
on the VCS must, like any other travers al call, pass through
the VCS’s Traversal Subzone. This means that suc h calls
will consume an amount of bandwid th from the originating
subzone’s total concurrent allocati on that is equal to twice the
bandwidth of the call – once for t he call from the subzone to
the Traversal Subzone, and again for the c all from the Traversal
Subzone back to the originatin g subzone.
Calls passing through the Traversa l Subzone will consume an
amount of bandwidth within th e subzone equal to that of the
call.
Traversal Calls
A traversal call is any call passing thr ough the VCS that includes
both the signaling (informati on about the call) and media (voice
and video). The only other type of c all is a non-traversal cal l,
where the signaling passes thr ough the VCS but the media goes
directly between the endp oints.
Traversal calls include:
calls that are traversing a fire wall
SIP to H.323 interworking calls
IPv4 to IPv6 interwork ing calls.
Traversal calls use more resource th at non-traversal calls, a nd
the numbers of each type of c all are licensed separately. The
VCS has one license for the maximu m number of concurrent
traversal calls it can take, and ano ther for the maximum
number of concurrent non -traversal calls.
•
•
•
About the Default Subzone
When an endpoint registers wit h the VCS, its IP address is
checked and it is assigned to the ap propriate subzone. If no
subzones have been created, or the e ndpoint’s IP address does
not match any of the specified su bzones, it will be assigned to
the Default Subzone.
The use of a Default Subzone on its ow n (i.e. without any
other manually configured su bzones) is suitable only if you
have uniform bandwidth availa ble between all your endpoin ts.
However, it is possible for a Local Zone to co ntain two or more
different networks with d ifferent bandwidth limi tations. In this
situation, you should configur e separate subzones for each
different part of the net work.
Specifying the IP Address Range of a Subzone
A subzone is defined by specif ying a range of IP addresses.
The VCS allocates endpoints to a su bzone based on their
IP address. You specify which I P addresses are associated
with the subzone by configurin g up to 5 subnets for that
subzone.
Default Settings
The VCS is shipped with the Defa ult Subzone, Traversal
Subzone and Default Zone alread y created, and with links
between the three. You may delete or ame nd these default
links if you need to model restric tions of your network.
If any of these links have been deleted, t hey may be
automatically restored via:
xCommand DefaultLinksAdd
To restore this link via the web interfa ce, you must recreate it
manually. See Creating Links for inst ructions on how to do this.
•
About the Traversal Subzone
The Traversal Subzone is a conceptual s ubzone. No endpoints
can be registered to the Traversal Su bzone; its sole purpose is
to allow for the control of bandwid th used by traversal calls.
All traversal calls are deemed to p ass through the Traversal
Subzone, so by applying bandwid th limitations to the Traversal
Subzone you can control how much p rocessing of media the
VCS will perform at any one time. T hese limitations can be
applied on a total concurrent us age basis, and/or on a per-call
basis.
Subzones
A call is “traversal” or “non-t raversal” from the point of
view of the VCS through which it is b eing routed at the
time. A call between two endpoi nts may pass through a
series of VCSs. Some of these syste ms may just take the
signaling, in which case the call w ill be a non-traversal cal l for
that VCS. Other systems in the rou te may need to take the
media as well, and so the call will count as a t raversal call on
that particular VCS.
If an endpoint’s IP address matches m ore than one
subnet, it will be allocated to the su bnet with the
narrowest range.
Bandwidth ControlBandwidth Control