User's Manual

Managing video on your network
Administering Avaya Video Conferencing Solutions 6.1 29
DRAFT
Site 1, designated Location A and Network Region 1, uses mostly SIP and some H.323 video
endpoints within conference rooms and on desksets within the executive suites. They also use
some SIP and H.323 video desksets throughout the building and audio endpoints as well.
Location A is allocated 100 Mbps for the SIP endpoints, and Network Region 1 is allocated 50
Mbps for the H.323 endpoints.
Site 2, designated Location B and Network Region 2, uses mostly H.323 video and some SIP
endpoints within offices. Location B is allocated 25 Mbps for the SIP endpoints, and Network
Region 2 is allocated 50 Mbps for the H.323 endpoints.
In both Network Regions, the 50 Mbps bandwidth is divided into 3 pools: audio, normal video,
and priority video. One example would be to allocate 20% for audio calls, 50% for normal video
calls, and 30% for priority video calls. For information on classifying users see User
classification on page 20.
When calling between locations and network regions, the bandwidth used is counted against
the terminating endpoint. For example, if you are calling from an H.323 endpoint in Location A to
a SIP endpoint in Location B, the bandwidth used is counted against the bandwidth pool
managed by Session Manager. If you are calling from a SIP endpoint in Location A to an H.323
endpoint in Location B, the bandwidth used is counted against the bandwidth pool managed by
Communication Manager.
Bandwidth pools
Bandwidth for H.323 is managed through Communication Manager using Network Regions,
and bandwidth for SIP is managed through Session Manager using Locations. Network
Regions and Locations must have a 1-to-1 mapping. This mapping presents some limitations:
● Communication Manager supports no more than 250 Network Regions, but Session
Manager supports thousands of Locations.
● Session Manager maps IP addresses to Locations; Communication Manager maps IP
addresses to Network Regions. These mappings must be synchronized manually.
● As part of Communication Manager administration, the SIP trunk to Communication
Manager must be placed within a dummy Network Region for which no bandwidth limits
are set.
Because Locations and Network Regions cover the same physical links, the bandwidth limits of
the links must be divided between Session Manager bandwidth and Communication Manager
bandwidth and within an enterprise possibly among many Communication Managers. The
appropriate division depends on expected call traffic breakdown.
When setting up bandwidth pools, you set them up the same as you do for H.323-only and
SIP-only endpoints.
The following tables provide examples of how you could specify the bandwidth settings for your
network.