Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Bandwidth control
Cisco VCS Administrator Guide (X7.1)
Page 206 of 479
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.
of your network, and to control registrations.
When an endpoint registers with the VCS it is allocated to an appropriate subzone, determined 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 VCS is in a cluster) — are automatically created and cannot be deleted.
applies if the VCS is in a cluster) — are automatically created and cannot be deleted.
Default links between subzones
The VCS is shipped with the Default Subzone and Traversal Subzone (and Default Zone) already created,
and with links between them. If the VCS is added to a cluster then default links to the Cluster Subzone are
also established automatically. You can delete or amend these
and with links between them. If the VCS is added to a cluster then default links to the Cluster Subzone are
also established automatically. 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
its sole purpose is to control the bandwidth used by
.
The
Traversal Subzone
page (
VCS configuration > Local Zone > Traversal Subzone
) allows you to
place bandwidth restrictions on calls being handled by the Traversal Subzone and to configure the range of
ports used for the media in traversal calls.
ports used for the media in traversal calls.
Configuring bandwidth limitations
All traversal calls are deemed to pass through the Traversal Subzone, so by applying bandwidth limitations to
the Traversal Subzone you can control how much processing of media the VCS will perform at any one time.
These limitations can be applied on a total concurrent usage basis, and on a per-call basis.
the Traversal Subzone you can control how much processing of media the VCS will perform at any one time.
These limitations can be applied on a total concurrent usage basis, and on a per-call basis.
See
for more details.
Configuring the Traversal Subzone ports
You can configure the range of ports used for the media in traversal calls. A single traversal call can consist
of up to 5 types of media (audio, video, far end camera control, dual streams and BFCP) and each type of
media may require a pair of ports – for example, audio and video each require one port for RTP, and one for
RTCP. Separate pairs of ports are required for the inbound and outbound portions of a call. A single traversal
call can therefore take up to 20 ports.
of up to 5 types of media (audio, video, far end camera control, dual streams and BFCP) and each type of
media may require a pair of ports – for example, audio and video each require one port for RTP, and one for
RTCP. Separate pairs of ports are required for the inbound and outbound portions of a call. A single traversal
call can therefore take up to 20 ports.
The default range for the ports used for media is 50000 - 52399 UDP, but these can be changed to any values
between 1024 and 65533. Ports are allocated from this range in pairs, with the first port number of each pair
being an even number. Therefore the range must start with an even number and end with an odd number.
between 1024 and 65533. Ports are allocated from this range in pairs, with the first port number of each pair
being an even number. Therefore the range must start with an even number and end with an odd number.