more topics
|
Calling Restrictions Feature |
|
Description |
Facility Restriction Level (Hybrid/PBX Only)
The ARS FRL is used to restrict the extension to certain routes. When ARS is used, an FRL is assigned to control or restrict access to specific routes in an ARS table. There are seven FRLs assigned to routes, ranging from 0 to 6, where 0 is the least restricted and 6 is the most restricted.
FRLs from 0 to 6 are also assigned to extensions and are used to determine whether callers have permission to use the routes. To use a route, an extension must have an FRL equal to or greater than the route's FRL. The restrictions of the FRL assigned to an extension, therefore, are the opposite of the restrictions of an FRL assigned to a route. In other words, an extension with an FRL of 0 has the fewest ARS privileges (routes with levels 1 through 6 cannot be used), and an extension with an FRL of 6 has the most privileges (any route may be used). See Automatic Route Selection for additional ARS information.
Restrictions for VMI PortsAny port programmed as a VMI port is factory-set with an FRL of 0.
The FRL of the VMI port must be equal to or greater than the FRL of the UDP route. See the Network Reference for details.
If the System Manager wants to allow access to the voice messaging system Outcalling feature, the FRL applies to Outcalling calls.
SECURITY ALERT! Any changes to the FRL and other restrictions of VMI ports must be considered carefully in order to minimize the potential for toll fraud.
If the System Manager changes a VMI port to a non-VMI port, the FRL is not reassigned on the port. If the default FRL should be changed, the System Manager must change it through system programming.
Remote AccessOutward/toll and FRL calling restrictions can also be applied to remote access users. These calling restrictions can be applied to each individual barrier code (up to 16) or, if barrier codes are not used, to all remote access tie/DID trunks and all remote access non-tie/non-DID trunks. See Remote Access for additional information. Refer to the Network Reference for additional information for private networks (Hybrid/PBX mode only).
Night ServiceOther calling restrictions can be applied when Night Service is activated. Night Service can be set up to require that a password be dialed before a non-emergency number can be dialed. When the correct password is entered, the system then checks for calling restrictions assigned to each extension before allowing calls to outside numbers.
A Night Service Exclusion List can be created to exempt specific extensions from the password requirement. Normal calling restrictions (if any) assigned to the extension, however, are still in effect. A Night Service Emergency Allowed List can also be created, which can contain up to 10 numbers that can be dialed without entering the Night Service password. See Night Service for additional information. If Night Service is programmed with outward restriction, the restriction does not apply to non-local dial plan calls. Exclusion lists apply only to the local system's extensions and do not apply to UDP calls.
| Topics | |||||||||
 |
Description | ||||||||
|
|||||||||
| |
At a Glance | ||||||||
| |
Considerations and Constraints | ||||||||
| |
System Programming | ||||||||
| Mode Differences | |||||||||
| |
Feature Interactions | ||||||||
