| more topics
|
Restrictions
If the FRL for an extension, for a remote access barrier code, or for the remote access default COR is equal to or greater than the FRL of any of the routes in the selected subpattern, those routes are eligible for selection. The Facility Restriction Levels Table below shows how FRLs are used to decide whether a route is allowed.
|
FRL |
Route FRL |
Allowed |
|
0 |
0 only |
Yes |
|
0 |
1 and up |
No |
|
1 |
0 and 1 |
Yes |
|
1 |
2 and up |
No |
|
2 |
0 - 2 |
Yes |
|
2 |
3 and up |
No |
|
3 |
0 - 3 |
Yes |
|
3 |
4 and up |
No |
|
4 |
0 - 4 |
Yes |
|
4 |
5 and up |
No |
|
5 |
0 - 5 |
Yes |
|
5 |
6 |
No |
|
6 |
Any |
Yes |
|
|
FRLs associated with extension numbers apply both to ARS calls and to local and non- local dial plan-routed calls over private networked trunks (Hybrid/PBX mode only), including those used to reach non-local dial plan extension numbers. See Tandem Switching and Uniform Dial Plan features for details. |
For a call, any route that does not match the call type (voice or data) is eliminated from eligibility. Each route may be specified as voice, data, or both.
If a voice call is queued for callback on a digital pool, it can get stuck in an infinite loop of queuing. The caller hears a continuous stutter tone and cannot get rid of it. To avoid this situation, be sure that you correctly program the voice and/or data capabilities of pools of PRI and BRI facilities in the ARS tables.
Any remaining eligible routes are scanned from the beginning of the list. The first eligible route that is not busy is selected. If all eligible routes are busy, the user hears a fast busy and can use Callback to queue the call for the first route only. Callers who are accessing ARS over private network trunks (Hybrid/PBX mode only) can queue for a private network trunk pool on their switch, but not for a route on the remote system associated with a PSTN trunk on that system.
|
|
Emergency numbers must be on an Allowed List to be called from a restricted extension. |
