Avaya Communication Manager Administrator's Manual page 1405

The "No Hold Conference" feature automatically conferences another party in when that party
answers the call, without the user having to press a "conference" completion button. Similarly, the
"Meet-Me Conference" feature automatically conferences another party onto a conference call
when the user dials a specific number. Hence the CAC-BL feature will check that the bandwidth
limits are correct for the completed conference in these cases.
•
E911
If for some reason, the system is configured so that E911 calls go between network regions, then
the CAC-BL feature will treat E911 calls no differently than any other call. If an E911 call needs
to be routed over a WAN link and the WAN bandwidth limits have been reached, the E911 call
will be re-routed using the various features available in Communication Manager, just as any
other call would. This is the same strategy that is used for E911 calls over IP when there are no
VoIP resources available.
It is not recommended that E911 calls be administered to route between network regions. This is
true for safety reasons – the person having the emergency would be in one location and the
emergency would be reported possibly to a different region of the world.
•
Firmware Download to Port Boards
Since the firmware download feature of Communication Manager for port boards uses a bearer
channel from the CLAN board to the other port board, this download bandwidth traffic must be
taken into account. The firmware download uses a 10 ms G.711-like packet, which is allocated
110 Kbits per second of bandwidth.
This is the only type of non-voice bearer traffic that the CAC-BL feature takes into account.
The CAC-BL feature does not apply to the self-download feature of boards like C-LAN and VAL,
which do not use a bearer channel.
•
Hold
In order to reserve the bandwidth necessary at any point a user would want to take a call off hold,
no adjustment is made for a call placed on hold. Hence, a user will never be blocked from taking a
call off hold. Note that this does tie up bandwidth that is not actually being used while the call is
on hold.
•
Media Processor Resources
The Prowler board and the Gateways must have VoIP resources available for IP calls to be
initiated. The CAC-BL feature has not changed that requirement.
•
Multi-Level Precedence and Preemption (MLPP)
With Release 2.0, MLPP will become a generally available feature. At this point in time, the
MLPP feature is built on the design of unlimited bandwidth; hence, it is highly recommended that
no bandwidth limits be administered in systems that are using the MLPP feature. If there are
bandwidth limits administered, the MLPP feature will not be able to override those limits in
Release 2.0.
•
Multiple Terminations
Multiple terminations include features such as Bridging, Pickup Groups, Terminating Extension
Groups, Whisper Page, etc. These features allow terminations of multiple parties to a call. When
the call is ringing, it is unknown which of the multiple end parties will answer the call. Therefore,
bandwidth for all of the possible call terminations must be taken into account. If any particular
termination exceeds the CAC limits, that termination is blocked. Once one party answers the call,
the reserved bandwidth can be released, if Communication Manager already dropped the other
terminations.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Call admission control - bandwidth limitation
1405