MERLIN LEGEND Communications System Release 6.1
Feature Reference
555-661-110
Issue 1
August 1998
Features
Page 586Remote Access
Class of Restrictions (COR) 40
Barrier codes should be used for all lines/trunks including those that will be
accessed by remote access users in Release 6.0 and later systems (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 Table 40, page 584
.
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 Release 6.0
and later systems (Hybrid/PBX mode), the outward restriction must be
turned off. For additional details, see “Tandem Switching” on page 671
.
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 (Release 6.0 and later systems, 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
(Release 6.0 and later systems). 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
To Next Page
Loading...
Need help?
General
