Instruction manual

Large business communications systems
5-16 Issue 9 May 2003
■ Toll Restriction: cannot make toll calls unless the numbers are specified on
an unrestricted call list. For G3, you can specify if the restriction applies to
all toll calls or only TAC toll calls over CO/FX trunks.
NOTE:
The switch identifies all public network calls with 0 or 1 as the first or
second digit as toll calls. For G3, toll calls and private network calls
are defined on the Toll Analysis screen. For G2.2, only the first digit, 0
or 1, identifies it as a toll call.
■ Code Restriction: for DEFINITY G1 and System 75, denies outgoing calls
to selected office and area codes administered in the code table.
■ Fully Restricted: for Communication Manager, MultiVantage™ Software,
DEFINITY ECS and DEFINITY G3, denies outgoing calls, including dial
access to trunks. Allows no incoming calls via public network trunks. See
also ‘‘Fully restrict service’’ on page 5-31
.
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 5-17.