User's Manual

Design and deployment
38 Administering Avaya Video Conferencing Solutions 6.1
DRAFT
5. Specifies per-call bandwidth limits (as specified in Per-Call Bandwidth Parameters section),
restricting the size of individual multimedia calls. Session Manager alters the SDP provided
by call parties by enforcing the bandwidth limits as follows:
● Determines how much bandwidth to be reserved for each call and counts the
determined value against the provisioned limit.
● If the multimedia bandwidth is beyond what is provisioned (Maximum Multimedia
Bandwidth (Intra-Location) or Maximum Multimedia Bandwidth (Inter-Location)),
Session Manager can reduce the multimedia bandwidth as low as the administered
multimedia minimum (Minimum Multimedia Bandwidth) limit. In such cases, users
experience a reduction in media (usually video) quality. Otherwise, calls are either
alternate-routed or denied when limit enforcement cannot be achieved by quality
reduction. Audio call quality is not modified by Session Manager.
● If Session Manager cannot allow the multimedia minimum (Minimum Multimedia
Bandwidth), then multimedia streams are removed from the call by setting their ports
to zero, which results in denying the multimedia portion of the call
SDP functionality can be enabled by clearing the Global Settings option Ignore SDP for Call
Admission Control in the Session Manager Administration page. This setting changes the CAC
mode from “Ignore SDP” (as in Session Manager 6.0) to “Use SDP” (as in Session Manager
6.1). This setting takes effect at cluster level in the core and hence all the Session Manager
instances are affected accordingly.
See Administering Avaya Aura
®
Session Manager for understanding the location based
configuration changes required in the earlier versions of Session Manager.
Provisioning Session Manager and Communication Manager CAC
together
For simultaneous use of Session Manager and Communication Manager CAC, following
configurations should be done:
1. Create 1-to-1 mapping of Session Manager Locations to Communication Manager Network
Regions, because Communication Manager uses Network Regions for CAC. This is limited
by the fact that Communication Manager supports no more than 250 Network Regions,
while Session Manager supports thousands of Locations.
2. As Session Manager maps IP addresses to Locations, Communication Manager maps IP
addresses to Network Regions. These mappings must be synchronized manually.
3. As part of Communication Manager administration, the SIP trunk to Communication
Manager must be placed within a dummy Network Region for which no CAC limits are set.
This enables the following changes: