Technical information

Tools that Restrict Unauthorized Outgoing Calls
Issue 7 June 2001
4-15
COR-to-COR Restrictions/Calling Permissions
If it is not practical to dial-access-restrict outgoing or two-way trunk groups, then
COR-to-COR restrictions should be used to prevent direct access to those trunk
groups. These restrictions can give no calling permissions to CORs assigned to
trunk groups or data stations.
The following options are available:
 Voice Terminal—Public Restriction: restricts callers at specified voice
terminals from receiving public network calls. A denied call is routed to an
intercept tone, a recorded announcement, or the attendant.
Calls can redirect to a public-restricted voice terminal. The COR of the
originally called extension number is the only one checked.
 Voice Terminal—Termination Restriction: restricts voice terminal users on
specified extension numbers from receiving any calls. However, voice
terminal users CAN originate calls. Direct Inward Dialing or Advanced
Private Line Termination calls are routed to a recorded announcement or
the attendant.
NOTE:
When a call is to a VDN extension, the COR of the caller and the
VDN are compared to determine if the associated Call Vector can be
accessed. After the vector is accessed, the COR of the VDN is used
for further call permission checking. See also ‘‘Restriction Override
(3-way COR Check)’’ on page 4-15.
Restriction Override (3-way COR Check)
The Restriction Override feature, which is available only with DEFINITY
G3i-Global and G3V2 and later, determines whether or not there is a 3-way COR
check made on Conference and Transfer Calls.
For DEFINITY G3 systems prior to DEFINITY ECS Release 5, as well as for G1
and System 75 systems, the default value of the “Restriction Override” field on the
COR form is “all.” Starting with DEFINITY ECS Release 5, the default value of the
field is “none” for all CORs. This helps ensure that the feature is assigned only
when appropriate.
If Restriction Override=all, only the controlling party’s COR is checked against the
CORs of all other parties on the conference and/or transfer call for
station-controlled transfers and conferences, not attendant-controlled
conferences and attendant-extended calls. If Restriction Override=none, the new
party’s COR is always checked against the CORs of all other parties on attendant
extended calls and attendant-controlled conferences, as well as on all
station-controlled conferences and transfers.