Avaya Communication Manager Administrator's Manual page 1370

Feature Reference
Authorization codes
A Cancellation of Authorization Code Request (CACR) digit may be administered. The CACR digit
cancels the 10-second interval between dialing. When the CACR digit is dialed, the call immediately
routes according to system administration. (Incoming trunk calls receive intercept treatment or go to the
attendant.) Other calls receive intercept treatment unless the user's FRL is high enough to route the call.
A CACR digit from an off-premises extension over DID/Tie trunks use DID/Tie trunk intercept
treatment. Internal calls receive intercept tone.
CAUTION:
Do not program passwords or authorization codes onto auto dial buttons. Display
telephones display the programmed buttons, providing internal abusers access to the auto
dial buttons to originate unauthorized calls. If passwords or authorization codes must be
programmed onto auto dial buttons, use the ~s (suppress) character to prevent displaying
the codes.
For more information, see BCS Products Security Handbook.
AAR and ARS Calls
Each authorization code is assigned a COR that contains an associated FRL. Within a system, access
privileges are determined by the FRL assigned to the facility where the call is originated. When an
AAR/ARS call is dialed, the system allows or denies the call based on the FRL of the originating station.
COR is used to restrict internal or non-AAR/ARS calls.
Authorization codes are given to individual users and provide a method of specifying the level of calling
privileges for that user regardless of the originating facility. Once an authorization code is required and
dialed on an AAR/ARS call, the FRL assigned to the authorization code replaces the originating FRL and
controls and defines the user's privileges.
An AAR or ARS call originated by a system user or routed over an incoming tie trunk may require a
dialed authorization code to continue routing.
Extreme care should be taken when administering authorization codes, so that a user does not have to dial
the authorization code more than once. For example, if a user makes an AAR or ARS call and the user's
FRL is not high enough to access any of the trunks in the routing pattern, the system prompts the user for
an authorization code. If the FRL assigned to the authorization code is high enough to access the next
trunk group in the routing pattern, the user is not prompted to dial the code again. If the call is routed
through another switch, the user may be required to dial an authorization code again. This type of
situation can be avoided through careful administration.
When an authorization code is required on some, but not all, trunk groups, the system prompts for an
authorization code when the originating FRL is not adequate to access the next available trunk group in
the routing pattern.
1370 Administrator's Guide for Avaya Communication Manager
November 2003