Home
>
ATT
>
Communications System
>
ATT DEFINITY Communications System Generic 3 Instructions Manual
ATT DEFINITY Communications System Generic 3 Instructions Manual
Here you can view all the pages of manual ATT DEFINITY Communications System Generic 3 Instructions Manual. The ATT manuals for Communications System are available online for free. You can easily download all the documents as PDF.
Page 681
Class of Restriction (COR) Issue 3 March 1996 3-537 Partitioned Group Number (PGN) When AAR and ARS services are to be partitioned among different groups of users within a single system, all users in a specific group must share the same PGN. A PGN is assigned to each COR. The PGN is not a restriction, but a means used to indicate the choice of route tables to b e used on a particular call. If the Time of Day Routing feature is assigned, this field is replaced with a “ Time of Day Plan Numb er”...
Page 682
Feature Descriptions 3-538Issue 3 March 1996 For intraflowed calls from one hunt group to another to be given p riority queuing treatment, ACD software must b e activate d. DAC The “Direct Agent Calling” field on the COR form indicates whether the user can originate and receive Direct Ag ent calls through an adjunct. If either the originating or the d estination party of a Direct Ag ent call does not have the proper COR, the call is denied. Direct Agent Calling allows an adjunct to transfer a...
Page 683
Class of Restriction (COR) Issue 3 March 1996 3-539 field administered as y, facilities with that COR cannot be used to dial a number that matches one of the digit strings in the Restricted Call List. Unrestricted Call List Ten Unrestricted Call Lists are assigned to the system by the System Manager. Each Unrestricted Call List is made up of specific digit strings which can be dialed from facilities associated with the call list. The “ Unrestricte d Call List” fields on the “COR” form are used...
Page 684
Feature Descriptions 3-540Issue 3 March 1996 outgoing routes from a sp ecific system and the desired levels of calling privileges. This is part of AAR/ARS customization. The FRL of the call originator is contained in the COR assigned. The “ FRL” field in a COR assigned to an outgoing trunk group is never checked and should be ignored. Assuming AAR and/or ARS has been customized for a system, the System Manager must establish unique CORs for each of the up to eight levels of ARS calling...
Page 685
Class of Restriction (COR) Issue 3 March 1996 3-541 Certain facilities, such as voice terminals, can originate and receive calls. Call origination and termination restrictions are specified via a single COR. Misc ellaneous Restrictions can prevent calling any COR, including one’s own COR. When a COR is administered, the allowance or denial of access from that COR to each of the CORs applies only to the COR b eing administered. For example, if COR 6 is administered with access denied to COR 3,...
Page 686
Feature Descriptions 3-542Issue 3 March 1996 — Those that can place local central office and in-house calls only. — Those that can place local central office, FX, and in-house calls only. To implement the a bove requirements, a COR must be assigned to each facility or group of facilities. For simplicity, each can have a unique COR. The CORs are arb itrarily assigned as follows: nCOR 30 — Local central office trunks nCOR 31 — WATS trunks nCOR 32 — FX trunks nCOR 33 — Data modules nCOR 34 —...
Page 687
Class of Restriction (COR) Issue 3 March 1996 3-543 nCOR 34 (attendant group) — The attendant group cannot call COR 33 (data modules). Specify an n beside COR 33 in the “CALLING PERMISSION” field. Specify 34 in the “COR Number” field. nCOR 35 (unrestricted voice terminals) — Since no restrictions were specified, only the COR number needs to be entered. nCOR 36 (no FX or WATS calls) — This COR cannot call COR 32 (FX) or COR 31 (WATS). Sp e cify an n beside CORs 32 and 31 in the “ CALLING...
Page 688
Feature Descriptions 3-544Issue 3 March 1996 — Those that are toll restricted — Those that cannot call outside to a public network (outward restricted) — Those that can receive calls only from an attendant — Those that can call anywhere, any time — Those that cannot place FX or WATS calls — Those that cannot place WATS calls To implement the a bove requirements, a COR must be assigned to each facility or group of facilities. For simplicity, each can have a unique COR. The CORs are arb itrarily...
Page 689
Class of Restriction (COR) Issue 3 March 1996 3-545 nCOR 45 (TEG) — This COR can receive internal voice terminal-originated calls only. Since no tie trunks are specified for this examp le, the Inward Restriction feature can provide the desired restriction. Specify ‘‘inward’’ as the Called Party Restriction. If dial repeating tie trunks are provided, Misc ellaneous Restrictions could be used to deny trunk access to the group. Also, specify 45 as the COR number. nCOR 46 (Loudspeaker Paging A...
Page 690
Feature Descriptions 3-546Issue 3 March 1996 Assignments for these requirements could be made as follows: nCOR 20 — Manual Terminating Line Restriction nCOR 21 — Inward Restriction nCOR 22 — Toll Restriction nCOR 23 — Outward Restriction NOTE: A new Manual Terminating Line Restriction for voice terminals was not established. COR 20, above, can be assigned. nCOR 24 — Unrestricted nCOR 25 — COR for WATS nCOR 26 — COR for FX nCOR 27 — Provides Miscellaneous Restrictions for WATS and FX. Enter an n...