Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Bandwidth control
Field
Description
Usage tips
Downspeed
total mode
total mode
Determines what happens if the total bandwidth
restrictions on a subzone or pipe mean that there
is insufficient bandwidth available to place a call
at the requested rate.
restrictions on a subzone or pipe mean that there
is insufficient bandwidth available to place a call
at the requested rate.
On: the call will be downspeeded.
Off: the call will not be placed.
About downspeeding
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 Cisco VCS will still attempt to connect the call, but at a reduced bandwidth – this is
known as downspeeding.
place a call at the requested rate. By default (and assuming that there is some bandwidth still
available) the Cisco VCS will still attempt to connect the call, but at a reduced bandwidth – this is
known as downspeeding.
Downspeeding can be configured so that it is applied in either or both of the following scenarios:
n
when the requested bandwidth for the call exceeds the lowest per-call limit for the subzone or pipes
n
when placing the call at the requested bandwidth would mean that the total bandwidth limits for that
subzone or pipes would be exceeded
subzone or pipes would be exceeded
You can turn off downspeeding, in which case if there is insufficient bandwidth to place the call at the
originally requested rate, the call will not be placed at all. This could be used if, when your network is
nearing capacity, you would rather a call failed to connect at all than be connected at a lower than
requested speed. In this situation endpoint users will get one of the following messages, depending on
the system that initiated the search:
originally requested rate, the call will not be placed at all. This could be used if, when your network is
nearing capacity, you would rather a call failed to connect at all than be connected at a lower than
requested speed. In this situation endpoint users will get one of the following messages, depending on
the system that initiated the search:
n
"Exceeds Call Capacity"
n
"Gatekeeper Resources Unavailable"
About subzones
The Local Zone is made up of subzones. Subzones are used to control the bandwidth used by various
parts of your network, and to control registrations.
parts of your network, and to control registrations.
When an endpoint registers with the Cisco VCS it is allocated to an appropriate subzone, determined
by
by
based on endpoint IP address ranges or alias pattern matches.
You can create and configure subzones through the
page (
VCS configuration > Local
Zone > Subzones
).
Three special subzones — the Default Subzone, the Traversal Subzone and the Cluster Subzone
(only applies if the Cisco VCS is in a cluster) — are automatically created and cannot be deleted.
(only applies if the Cisco VCS is in a cluster) — are automatically created and cannot be deleted.
Default links between subzones
The Cisco VCS is shipped with the Default Subzone and Traversal Subzone (and Default Zone)
already created, and with links between the three. You can delete or amend these
already created, and with links between the three. You can delete or amend these
if you
need to model restrictions of your network.
About the Traversal Subzone
The Traversal Subzone is a conceptual subzone. No endpoints can be registered to the Traversal
Subzone; its sole purpose is to control the bandwidth used by
Subzone; its sole purpose is to control the bandwidth used by
.
Cisco VCS Administrator Guide (X6)
Page 158 of 295