ATT Definity Addendum 1 For Ds1, Dmi, Isdn Pri Instructions Manual

							TIE TRUNK SETTINGSE-5
TABLE E-1 (continued). System 85 R2V4 Administration Settings
PROCEDURE
WORDFIELDREMARKS
00044Assign the NPA and NXX index for the terminal extension
number. This information is used to populate the calling party
number field in a connect party number ISDN-PRI message.
The analogous Generic 1 administration is in the 
SID PREFIX
TABLE 
screen.
01043For each terminal class of service (COS) on a System 85,
assign either mode 0, 1, 2, or 3 data, or voice/voice-grade data.
The assignments here are responsible for populating the bearer
capability (BC) IE in the ISDN-PRI messages. This is used
for interworking between ISDN and non-ISDN trunks and
endpoints and also for routing calls based on BC. For
example, if you want only mode 1 terminal extensions to use a
certain trunk group, mode 1 is assigned to the COS for that
terminal and the preference is also assigned mode 1 in
procedure 321 word 1 and/or 309 word 5. If you want a
terminal to have more than one BC, it must have more than
one extension.
An analogous Generic 1 administration does not exist because
the Generic 1 automatically determines the BC of its endpoints
without administration. The BCC value appears as read only,
however, on the 
STATION and DATA MODULE screens.
4Use this field to assign which terminals can/cannot use ISDN
facilities. For example, you may want to assure the caller (a
company executive, for instance) that a call is going over
ISDN facilities. You have the option here to have calls from a
particular extension routed only over ISDN facilities, only over
non-ISDN facilities, or over either, depending on the
availability of ISDN facilities when the call is made.
An analogous Generic 1 administration does not exist although
an all-ISDN route can be set up using AAR/ARS partitioning.
10016Assign trunk type 41 if TCMs are passed.
The analogous Generic 1 administration is in the Service
Type field of the TRUNK GROUP screen.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							E-6TIE TRUNK SETTINGS
TABLE E-1 (continued). System 85 R2V4 Administration Settings
PROCEDURE
100
WORD
3
FIELD
2
3
4
7
8
REMARKS
Use ISDN signaling type, which is type 20.
The analogous Generic 1 administration is in the Group
Type field of the TRUNK GROUP screen.
Glare control is automatically handled with ISDN trunks and
does not have to be administered.
Assign a 1 here if you have assigned trunk types 41, 42, 43,
46, or 47.
This field is used to set the number of errors allowed over two
5-minute intervals before automatic busyout. You can set any
number from 1 to 99. If you are assigning this number for use
in a test, set it to 1.
Assign a 1 in this field if you do not want optional IEs sent,
or to a 0 if you do want these sent. Either all will be sent or
none will be sent, depending on the setting. These optional
IEs are:
l
l
l
l
l
l
l
l
lConnected number
User-user
Calling party number
Display
Logical link identification
Traveling class mark
Link layer parameters
Packet layer parameters
Look-Ahead Interflow
The calling party number option will populate the ISDN-PRI
setup message with the information necessary to deliver SID to
the called party. User-to-user information is not yet available.
When available, it will allow discretionary information to be
passed from the calling party to the called party in various
ISDN-PRI messages.
The analogous Generic 1 administration for the
calling/connected party number is the Send SID field of the
TRUNK GROUP screen. The analogous Display IE administration
is in the Send Name field of the 
TRUNK GROUP screen.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							TIE TRUNK SETTINGSE-7
TABLE E-1 (continued). System 85 R2V4 Administration Settings
PROCEDURE
WORDFIELDREMARKS
101117Assign AVD to all trunk groups that will be used for digital
data calls to and from Generic 1. Do not assign AVD if the
trunk group is to be used for voice-grade data using the
modem pool feature. You cannot mix digital data and modem
pooled data on the same trunk groups in R2V4. In Generic 2,
this is be possible because of BCCOS. You can put voice-
grade data on the digital data trunk groups if the modems are
not automatically inserted by the modem pool feature. For
example, if you have a modem on your terminal you can use
the same trunk groups as used for the digital data.
10313This field and field 4 should be set to 1 if TCMs are to be
sent and received. The trunk type should be type 41.
The analogous Generic 1 administration is in the Service
Type and Service/Feature fields of the TRUNK GROUP
screen.
4This field and field 3 should be set to 1 if TCMs are to be
sent. The trunk type should be type 41.
The analogous Generic 1 administration is in the Service
Type and Service/Feature fields in the TRUNK GROUP
screen. If TCMs are to be sent here, use TANDEM trunks;
otherwise, use ACCESS trunks.
9Enter the AAR or ARS prefix digit here. On incoming calls,
this setting routes calls to AAR or ARS.
The analogous Generic 1 administration is in the Incoming
Call Handling Table fields on page 2 of the 
TRUNK
GROUP 
screen (see table E-8).
14Assign a 1 here for all ISDN trunks. This is to collect all
digits before seizing trunks.
The analogous Generic 1 administration is in the preferences in
the 
ROUTING PATTERN screen. Digits are all collected starting
with the first ISDN-PRI preference in a pattern and for all
subsequent preferences, whether they are ISDN-PRI trunk
groups or not. Thus, you can achieve the same effect as this
procedure does in the Generic 1 by assigning an ISDN-PRI
preference as the first preference in a pattern.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							E-8TIE TRUNK SETTINGS
TABLE E-1 (continued). System 85 R2V4 Administration Settings
PROCEDURE
WORDFIELDREMARKS
103115This field applies to calls incoming on this trunk group. If
non-ISDN trunks are to interwork with ISDN trunks, then the
non-ISDN trunks may have their BCs assigned here. An
example would be a non-ISDN data call coming into a
System 85 that is tandemed to an outgoing ISDN trunk bound
for a Generic 1. Here, the incoming trunk should have its BC
set so that the far-end knows what mode of data it is.
The analogous Generic 1 administration is in the BCC field for
trunk groups set as comm type AVD or data in the 
TRUNK
GROUP screen.
116110When connected to a Generic 1, the interface endpoint is PBX.
Thus, assign a 0 here.
The analogous Generic 1 administration is in the connect
field of the 
DS-1 CIRCUIT PACK screen.
2102Assign the Listed Directory Number (LDN) and NPA-NXX
designator for the attendant console in this procedure.
309This procedure (for ARS) and procedure 321 (for AAR)
implement the private networking capabilities between
System 85 R2V4 and Generic 1. Fields relating to either
ISDN-PRI or to the dial plan are discussed below.
18For calls going out trunk groups bound for a Generic 1 via
private tie trunks, a 1 should not be sent. Thus, put a 0 in
this field.
The analogous Generic 1 administration is the prefix digit in
the ROUTING PATTERN screen.
10This field is part of the subnet trunking feature. If you want
to dial a Generic 1 with public network numbers (NPA-NXX-
XXXX) but route the call over private tie trunks, you must
delete all the digits except for the station numbers. This field
works with procedure 309, words 3 and 4. Also, procedure
103, word 4, must be set to 1 to allow subnet trunking.
The analogous Generic 1 administration is in the No.
Deleted Digits and Inserted Digits fields in the
ROUTING PATTERN screen.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							TIE TRUNK SETTINGSE-9
TABLE E-1 (continued). System 85 R2V4 Administration Settings
PROCEDUREWORDFIELDREMARKS
309111For all ISDN-PRI trunk groups, this field should be 0.
12This field does not apply to the configuration and application
discussed in this appendix because a System 85 R2V4 is
connected to another communications system via private lines.
If it is connected to a 4 ESS, 288 would be entered here,
which is the AT&T network. Thus, you can leave this field
blank for tie trunk groups connecting to a Generic 1.
54This field applies only to ISDN Dynamic trunk type 120. For
the configuration and application described in this appendix,
dedicated trunk groups should be used. A - should be
assigned in this field.
5This field applies to connections to central office or toll
switches, not to connections to other private communications
systems. A - should be assigned here.
6-10Use these fields to assign BCs to be supported by preferences.
For example, if you want a trunk group to be used for mode 0
and mode 1 calls only, assign mode 0 and mode 1 to all
appropriate preferences containing that trunk group. If the BC
of the originating terminal does not match that of the
preference, that preference will be skipped over.
The analogous Generic 1 administration is in the BCC fields in
the ROUTING PATTERN screen.
3211Administer the same as procedure 309, word 1.
5Administer this procedure the same as you would proc 309,
word 5. The only difference is you are using AAR patterns
instead of ARS patterns.
107ATMS terminating test line digits for and station features.
106This procedure is display only. It shows far-end maintenance
busyout, near end ISDN busyout, and far-end ISDN busyout.
Generic 1 Administration Settings
This section describes the ISDN-PRI-specific administration settings for a Generic 1 connected to a
System 85 R2V4 in the configuration shown in Figure 1. Each required administration screen is shown
with an example of the appropriate settings. After each screen is a table explaining each of the settings
related to ISDN-PRI. Fields not discussed in the table do not relate directly to the configuration shown
in figure 1. Typical settings for these fields are shown in the examples, though they are not required for
this interface.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							E-10TIE TRUNK SETTINGS
For those fields of a screen not discussed in the tables following these screens, you can assume that the
settings shown are reasonable. They are the settings used by a customer having a System 85 R2V4
connected to a Generic 1 with ISDN-PRI tie trunks. The only significant difference between the
configuration discussed in this appendix and the configuration administered in the sample screens is that
the customer has DCS implemented over the ISDN-PRI trunks.
Administration Summary
Before administering a Generic 1, you should have the dial plan completed.
Following is a summary of the administration screens specific to this configuration, listed in a suggested
order they should be administered. Not all screens are order-dependent, but if you follow this suggested
order you should not encounter any order-related administration problems.
Refer to DEFINITY® 75/85 Communications System, Generic 1 and System 75
Administration/Measurements, Issue 4, February 1989, 555-200-500 for the administration commands
applicable to each of these screens.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
System Parameters - Customer Options
Feature-Related System Parameters
Maintenance-Related System Parameters
Dial Plan Record
DS-1 Circuit Pack
Synchronization Plan
Processor Interface Data Module
Interface Links. (Fill in all but the enable fields.)
Processor Channel Assignment
Interface Links. (Enable the interface links.)
Signaling group (R1V5 only)
Trunk Group
Various routing screens (RNX, HNPA, FNPA, RHNPA)
Routing Pattern
SID Prefix Table
Hunt Group
Terminating Extension Group
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							TIE TRUNK SETTINGSE-11
System Parameters — Customer Options Screen Settings
The administration for this screen is done remotely by the Customer Service Support Organization
(CSSO) of the Network Operations Group (NOG). It enables the optional features of a Generic 1.
Following is an example of typical settings for this screen when a Generic 1 is connected to a System 85
R2V4 via ISDN-PRI tie trunks:
OPTIONAL FEATURES
Abbreviated Dialing Enhanced List? nHospitality? y
ACD? y
Hospitality Parameter Reduction? n
ARS? yISDN-PRI? y
ARS Partitioning? yOCM? n
Authorization Codes? yPrivate Networking? y
CAS Branch? yService Observing? y
CAS Main? n
Ten to Seven Digit Conversion? y
DCS? yTime of Day Routing? n
Emergency Access to Attendant? nUniform Dialing Plan? y
Forced Entry of Account Codes? n
(NOTE: You must logoff & login to effect the permission changes.)
Figure E-1. OPTIONAL FEATURES Screen
Table E-2, System Parameters - Customer Options Screen Administration — Generic 1, describes the
administration settings for the fields of this screen relevant to the configuration shown in figure 1:
TABLE E-2. System Parameters - Customer Options Screen Administration — Generic 1
FIELD
SETTING
REMARKS
ARSARS is required if you are using Ten-Digit-to-Seven-Digit
Conversion. If you are using subnet trunking or uniform dial
plan with the ISDN-PRI trunk to a System 85, you need either
AAR (PNA) or ARS.
ARS Partitioning
YThis field is factory-set to y if ARS is ordered.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							E-12TIE TRUNK SETTINGS
TABLE E-2 (continued). System Parameters — Customer Options Screen Administration — Generic 1
FIELDSETTINGREMARKS
ISDN-PRIYA y here turns on ISDN-PRI. ISDN-PRI software is ordered
by specifying attribute use 6 when ordering the TN767
DS-1 circuit pack.
Private Network
YPNA is analogous to AAR on System 85. Either this or ARS
Access (PNA)software is required for ISDN-PRI. If the Ten-Digit-to-
Seven-Digit Conversion feature is used, you must have PNA
and ARS. If you use the Subnet Trunking feature, you need
either PNA or ARS. If you use the UDP feature, you do not
need PNA. UDP software is a separate PEC having no
prerequisite.
Ten-Digit-to-YThis option is not strictly required. It allows you to dial the
Seven-Digit-public network number of an endpoint on a System 85 but
Conversionroute the call over the private ISDN-PRI tie trunk by
converting the public network number to a private network
number. To administer this option, ARS and UDP or PNA
must be enabled. All entries on the 
TEN-DIGIT TO SEVEN-DIGIT
CONVERSION 
screen must be assigned. Instructions for doing
this can be found in DEFINITY® 75/85 Communications
System, Generic 1 and System 75 Implementation, Issue 1,
February 1989, 555-204-654. See pages 4-23 and 6-176.
Uniform Dialing
YThis option is not strictly required. It is useful in setting up a
Planuniform four or five digit dial plan between a System 85
R2V4 and a Generic 1. This feature works by converting an
extension number to an RNX plus an extension number. To
administer UDP, see DEFINITY® 75/85 Communications
System, Generic 1 and System 75 Implementation, Issue 1,
February 1989, 555-204-654. See pages 3-243, 4-20, 4-28,
5-68, 6-73, 6-163, and 6-164.
Feature-Related System Parameters Screen Settings
Following is an example of typical settings for this screen when a Generic 1 is connected to a System 85
R2V4 via ISDN-PRI tie trunks:
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							TIE TRUNK SETTINGSE-13
FEATURE-RELATED SYSTEM PARAMETERS
Trunk-to-Trunk Transfer? y
Coverage - Don’t Answer Interval for Subsequent Redirection (rings): 2
Coverage — Caller Response Interval (seconds): 4
Keep Held SBA at Coverage Point? y
Automatic Callback — No Answer Timeout Interval (rings): 4
Call Park Timeout Interval (minutes): 10
Off-Premises Tone Detect Timeout Interval (seconds) : 25
AAR/ARS Dial Tone Required? y
Music On Hold Port:
Music (or Silence) on Transferred Trunk Calls? no
DID/Tie/ISDN Intercept Treatment: 67987
Messaging Service Adjunct (MSA) Connected? n
Automatic Circuit Assurance (ACA) Enabled? y
ACA Referral Calls: remote
ACA Remote PBX Identification: 3
Figure E-2. FEATURE-RELATED SYSTEM PARAMETERS Screen
The only ISDN-PRI-related field in this screen is the DID/Tie/ISDN Intercept Treatment
field. You should enter the extension of the recorded announcement you want to use for intercept
treatment for invalid ISDN-PRI calls. This field defaults to 0 to go to the attendant.
Maintenance-Related System Parameters Screen Settings
This screen is primarily for use by maintenance personnel. Following is an example of typical settings
when a Generic 1 is connected to a System 85 via ISDN-PRI tie trunks:
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							E-14TIE TRUNK SETTINGS
MAINTENANCE-RELATED SYSTEM PARAMETERS
MAINTENANCE THRESHOLDS (Before Notification)
Minimum Threshold for TTRs: 12Minimum Threshold for CPTRs: 6
TERMINATING TRUNK TRANSMISSION TEST ( Extension )
Test Type 100: 67380Test Type 102: 67382Test Type 105: 67385
ISDN TEST CALL
Extension: 67920
LOSS PLAN ( Leave Blank if no Extra Loss is Required )
Minimum Number of Parties in a Conference Before Adding Extra Loss:
Figure E-3. MAINTENANCE-RELATED SYSTEM PARAMETERS Screeen
The only ISDN-PRI-specific field in this screen is the ISDN Test Call Extension field. You
should enter the extension that this System 85 R2V4 should call when it does an ISDN test. This screen
is described in detail in DEFINITY® 75/85 Communications System, Generic 1 Installation and Test,
Issue 1, February 1989, 555-204-104, chapter 6 (Activate System).
Dial Plan Record Screen Settings
This screen does not directly relate to the use of ISDN-PRI trunks. It must be completed, however, to
implement the dial plan between the two communications systems. If UDP is used, the 
DIAL PLAN RECORD
screen has two parts. The first part is page 1. The second part consists of pages 2-6. The second part
is the UDP screen administration. For details on how to administer these screens, see DEFINITY®
75/85 Communications System, Generic 1 and System 75 Implementation, Issue 1, February 1989, 555-
204-654, pages 5-68 - 5-74 (Dial Plan). Also refer to DEFINITY® 75/85 Communications System,
Generic 1 and System 75 Feature Description, Issue 5, February 1989, 555-200-201, pages 3-257 - 3-259
(Dial Plan and 3-457 - 3-461 (Single Digit Dialing and Mixed Station Numbering).
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4