
prevents such calls from consuming too large a percentage of the available
bandwidth of a location (Total Bandwidth).
3. If the Total Bandwidth is left “BLANK” then Session Manager does not perform
CAC for calls in the Location.
4. Allows audio and multimedia bandwidth sharing at a location by selecting the option
Audio Calls Can Take Video Bandwidth.
• If selected, then Session Manager considers only the Total Bandwidth when
deciding whether a new audio call can proceed.
• If not selected, then Session Manager considers the Total Bandwidth minus
the Multimedia Bandwidth when deciding whether a new audio call can
proceed.
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.
Refer to the topic on “Recommended modifications for the earlier versions of Session Manager”
for understanding the location based configuration changes required in the earlier versions of
Session Manager.
Managing Session Manager routing
250 Administering Avaya Aura
®
Session Manager November 2010
Comentarios a estos manuales