Each authorization code is assigned a Class of Restriction (COR) that contains an associated FRL. Within a system, the FRL that is assigned to the point at which the call originates determines the access privileges that are associated with the call. When a user dials an AAR or an ARS call, the system connects or disconnects the call, based on the FRL of the originating station. You use COR to restrict internal or non-AAR or an ARS calls.

You can assign authorization codes to individual users to specify the level of calling privileges. Such codes work regardless of the originating facility. Once an authorization code is required and dialed on an AAR or an ARS call, the FRL assigned to the authorization code replaces the originating FRL. This new FRL controls and defines the privileges of the user.

An AAR call or an ARS call that a system user originates, or routes over an incoming tie trunk can require a dialed authorization code to continue routing.

When you administer authorization codes, ensure that the user does not have to dial the authorization code more than once. For example, if a user makes an AAR call or an ARS call, and the FRL of the user 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 that is 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 system routes the call through another system, the user might be required to dial an authorization code again. This type of situation can be avoided through careful administration.

An authorization code might be required on some, but not all, trunk groups. In such cases, the system prompts for an authorization code when the originating FRL is not high enough to access the next available trunk group in the routing pattern.