more topics
|
Remote Access Feature
Description
Class of Restrictions (COR)
Barrier codes should be used for all lines/trunks including those that will
be accessed by Remote Access users (Hybrid/PBX mode only). ARS calls and non-local
dial plan calls on private network trunks ignore the barrier code requirement
setting, but use the other COR settings assigned to all tie and/or all non-tie
trunks. The barrier code requirement setting must require barrier codes, however,
to protect against toll fraud for those calls from the PSTN that do not ignore
the requirement.
A maximum of 16 barrier codes is allowed, each with a different class of restrictions.
The class of restrictions allows or denies the use of system features to individuals
or groups of users. Classes of restrictions are assigned whether or not barrier
codes are used for Remote Access. If barrier codes are used, the class of restriction
is assigned to each barrier code. If barrier codes are not used, the class of
restriction settings are assigned to all non-tie trunks or to all tie trunks,
or both. They apply to trunks that are not specifically assigned as Remote Access
facilities, as explained in the table, Remote Access Routing.
The restriction classes are as follows:
- Calling Restrictions. Determine whether Remote Access users can
make local and/or toll calls. The factory setting is outward-restricted, meaning
the user can make only inside calls. The restricted user cannot make toll
calls or any outside calls. The setting can be changed either to unrestricted,
meaning the user can make inside local, toll, or outside calls, or to toll-restricted,
meaning the user can make only inside and local outside calls. When barrier
codes are not used, restrictions are assigned to all trunks and cannot be
assigned to individual tie trunk or non-tie trunks. When barrier codes are
used, restrictions are assigned to individual barrier codes. For routing calls
on tandem trunks across networked systems (Hybrid/PBX mode), the outward restriction
must be turned off. For additional details, see Tandem
Switching. Outward restrictions can still be applied to barrier codes
that are used when callers employ PRI dial plan routed, DID, or non-local
dial plan Remote Access.
- Automatic Route Selection and Uniform Dial Plan (UDP) Facility Restriction
Level (FRL). If the system uses the ARS feature or UDP routing over tandem
trunks (Hybrid/PBX mode), you can restrict the use of outgoing lines/trunks
by Remote Access users by assigning a user restriction level from 0 to 6.
The factory setting, 0, is the most restrictive, and 6 is the least restrictive.
The value assigned corresponds inversely to the FRL assigned to the ARS or
UDP route. That is, an FRL of 0 is the least restrictive, and 6 is the most
restrictive. To restrict remote users from using selected lines/trunks, you
should assign a value that is lower than the FRL assigned to the route.
When barrier codes are not used, the FRL is assigned to all Remote Access
lines/trunks and cannot be assigned to individual lines/trunks. When barrier
codes are used, FRLs are assigned to individual barrier codes, and this setting
is ignored. For networked systems (Hybrid/PBX mode), barrier codes should
be required; they are then required for non-network calls into these systems
via the public switched telephone network or via the Remote Access code in
the non-local dial plan. Network call routes (UDP or ARS) use the default
COR FRL and do not use barrier codes. For additional details, see Tandem
Switching.
- Allowed List Assignment. Does not apply to Allowed List Assignment.
Do not assign Allowed Lists as default COR settings.
- Disallowed List Assignment. Assigns Disallowed Lists; use when Remote
Access users are not restricted from making local and/or toll calls. When
a Disallowed List is assigned, remote users cannot dial the specific numbers
included on the list. Disallowed Lists are set up for all system users (see
Allowed / Disallowed Lists).
When barrier codes are not used, Disallowed Lists can be assigned to all Remote
Access lines/trunks and cannot be assigned to individual lines/trunks. When
barrier codes are used, Disallowed Lists are assigned to individual barrier
codes. For networked systems (Hybrid/PBX mode), a Disallowed List should be
assigned; it is applied both to non-network calls into these systems via the
public switched telephone network and to network-routed calls. For additional
details, see Tandem Switching.
- Automatic Callback (Autoqueuing). The factory setting prevents a
remote caller who reaches a busy pool (Hybrid/PBX only) or extension from
using the Automatic Callback feature to request a pool or extension. The factory
setting can be changed to allow remote users to use Automatic Callback to
request busy pools or extensions. Automatic Callback assignment applies to
all Remote Access users and cannot be assigned to lines/trunks or barrier
codes on an individual basis. For networked systems (Hybrid/PBX mode), the
Automatic Callback setting does not apply to network calls that are routed
across a system using ARS or UDP routing. Callback features only work for
lines and trunks on a local system. If a Remote Access caller calls into a
system and attempts to make a non-local extension call or an ARS call that
is routed to another networked system, the Callback setting only permits or
does not permit Callback when local tandem trunks are unavailable; calls queue
for Route 1 only. For additional details, see Tandem
Switching.
