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

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 857-23
Field 3This field is used to populate the BC code IE or an ISDN-PRI facility. All endpoints
(such as analog lines and DCP voice terminals) must show their information transfer
requirements in terms of a BC code. The BC code is the mechanism by which
specialized routing is provided for various categories of calls.½
NOTE: Once the BC code is assigned, it is fixed and does not change with
different calls.
Field encodes and their descriptions are:
0
1
2
3
4Voice and Voice-grade data
Mode 1 data (56K-bps)
Mode 2 data (subrate up to 19.2K-bps)
Mode 3 data (also called packet mode)
Mode 0 data (64K-bps digital data).
Field 4This field is used to populate part of the TCM IE and shows an ISDN-PRI Routing
option. Field encodes and their descriptions are:
0
1
2For when any type of trunking facility is OK. This option should be used when
there are no specific requirements for ISDN-PRI trunks. Generally, this will
include all voice and voice-grade data applications (BC code = 0) except those
where user-to-user information transfer is desired.
When ISDN-PRI trunking facilities are required. Generally, these applications
include those COS groups established for Mode 1 data (BC code = 1), Mode 3 data
(BC code = 3), and Mode 0 data (BC code = 4).
Mode 0 data, depending on its origin, may require a unrestricted channel. Recall
that an unrestricted channel is only provided by those ISDN-PRI facilities that use
the B8ZS line-coding format.½
When any trunking facility will work but when ISDN-PRI trunk facilities are
preferred. This may include voice and voice-grade data (BC code = 0) and Mode 2
data (BC code = 2).
Procedure 100 Word 1: Trunk Group Type, Signaling, and Dial Access (ID) Code
Translating word 1 is the first step in establishing trunk groups. Those trunk groups established for
ISDN applications may be of the same design as those for non-ISDN applications, except for the type of
signaling used. Or, they may (optionally) be designed to take maximum advantage of the ISDN
capabilities. Figure 7-10, Procedure 100 Word 1: Trunk Group Translations (System 85 R2V4), shows
procedure 100, word 1.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-24ADMINISTRATION OPTIONS AND REQUIREMENT’S — SYSTEM 85
ENHANCED MODE — PROCEDURE: 100, WORD: 1
TRUNK GROUP TRANSLATION
1.
Trunk Group:
DIAL ACCESS CODE/TRUNK ID CODE
2.
3.
4.
5.Digit 1:
Digit 2:
Digit 3:
Digit 4:
6.
7.
8.Trunk Type:
Dial Access Restriction:
Personal CO Line Appearance:
DISPLAY ONLY
9.
Signaling Type:
Connected to CC0 ON-LINE
enter command:½
Field 1
Field 2
Field 3
Field 4
Field 5
Field 6Figure 7-10. Procedure 100 Word 1: Trunk Group Translations (System 85 R2V4)
Assigns a trunk group number. Permitted entries are any unused number from 18
through 999.
Assigns the first digit of the trunk access code. Permitted entries are 0 through 9 for
digits 0 through 9 and with 11 and 12 for the symbols * and #, respectively.
Assigns the second digit of the trunk access code. Permitted entries are 0 through 9.
Assigns the third digit of the trunk access code. Permitted entries are 0 through 9.
Assigns the fourth digit of the trunk access code. Permitted entries are 0 through 9.
Defines the trunk type of a specific trunk group. The ISDN-PRI facility may be used
to support several different trunk types. These may include both conventional and the
ISDN-dynamic trunk types. An important point to remember is that the service
application (such as MEGACOM, MEGACOM 800, or SDN) and incoming digits are
the primary determining factors controlling which trunk type is selected.
To date, trunk type 41, 42, or 43 have been the trunk types used most frequently to
support all ISDN applications, including CBC.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 857-25
Incoming ISDN dynamic trunk type 120 calls (to a System 85) may or may not specify
an NSF. Generally, incoming calls from the public network will specify an NSF while
calls from the private network will not specify an NSF. For example, if the NSF is
delivered and it shows an SDN call, then the System 85 defaults to trunk type 46. For
all other incoming NSF values, the switch will default to trunk type 30. For those
incoming calls which do not deliver an NSF the switch will either use those interface
endpoint trunks that are translated in procedure 116 or use a default that is dependent
on the type call. For example, trunk type 41 is the default for switch-to-switch
connections, trunk type 30 is the default for public network-to-switch connections, and
trunk type 108 is the default for host-to-switch calls.
Table 7-2, Trunks Supporting Signaling Type 20, shows permitted field entries that½
½
support signaling type 20.
TABLE 7-2. Trunks Supporting Signaling Type 20
Trunk
DescriptionTrunk
Type
CO
Data
DID
DMI (Note 2)
FX
ISDN
M/S TIE
Special
TIE
WATS
16, *17 (Note 1), 18, 19, 20
100—107
*30, *31
*108, *109
21—25
120 (Note 3)
70—78
2, 5, 6, 50—58, 62, 65—67, 90—93
32—40, *41, *42, *43, 44, 45, *46, *47
26, *27, 28
NOTES:
1.
Trunk types preceded with an asterisk (*) may be selected by trunk type 120 on an as needed
Call-By-Call (CBC) Service Selection basis.
2.Trunk types not included in these categories may not be translated for ISDN-PRI service. Most
conventional trunk types specify, as a part of their name, an in/out signaling sequence. Actually,
these signaling sequences are disabled and type 20 signaling is used exclusively over ISDN
facilities.
3.
Beginning with the 1.0 software load of Generic 2 and the 1.2 software load of System 85 R2V4
digits may be inferred when using the ISDN-dynamic trunk type. The default of 30 infers DID
(if necessary). A default of 46 infers AAR/ARS. (See Appendix C, “Administrative Procedure
Summary,” for a complete explanation of this field.)
For ISDN trunk groups as well as other types of trunk groups, the entered type defines
feature operation for the trunk group. For example, if a trunk group is assigned the
type of 19, incoming calls over this trunk group are routed to the attendant console.
On DID trunk type groups, the switch expects station number digits on all incoming
trunks; on tie trunk type groups the switch can handle either station number digits or
network numbers.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-26ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 85
Field 7
Field 8
Field 9For an ISDN trunk group, a dynamic trunk type (120) can be assigned to the group.
This trunk type allows the group to process calls with a different trunk type on a call
by call basis. For example, one incoming call over the group may expect station
number digits (as does a MEGACOM call), while the next call over the group may
expect a network number (as does an SDN call).*
Both an AAR/ARS prefix digit (procedure 103) and a DID additional digit (procedure
101) can be administered for ISDN dynamic trunk groups. (This cannot be done for
any other type of trunk group.) The dynamic trunk type may be used for CBC service
although any of the conventional trunk types could also be used if incoming digits
have been provisioned consistently. For example, trunk type 41 could be used as a
CBC trunk group to support MEGACOM, MEGACOM 800, and SDN if the incoming
digits (for both MEGACOM 800 and SDN) reflect extension numbers or seven digit
RNX-XXXX numbers. Customers can choose between 0 and 7 incoming digits to a
switch.
Assigns the dial access code restriction. Field encodes and their descriptions are:
0
1Allows access to the trunk group via a dial access code.
Restricts and only allows access to the trunk group for trunk testing and for
providing unattended console service.
Assigns the trunk group as a MFT CO line appearance. For the ISDN application,
encode (0) is applied.
Displays default signaling and verify that the type of trunk signaling is correct. The
ISDN feature uses message-oriented signaling. Therefore, encode 20 should be used.
If the trunk signaling is not as desired — then it may be changed with field 2 of word
3.
Procedure 100 Word 2: Trunk Group Data Translations
This word is used to administer data characteristics for each trunk group. The ISDN feature does not
place any new or additional requirements or restriction on the use of this procedure. Selecting the
appropriate translations requires the same basic considerations as previously. Therefore, a description
for this procedure’s fields is not provided. Figure 7-11, Procedure 100 Word 2: Trunk Group Data
Characteristics (System 85 R2V4), depicts procedure 100, word 2.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 857-27½
½
ENHANCED MODE — PROCEDURE: 100, WORD: 2
TRUNK GROUPS — DATA AND MODEM POOLING
1. Trunk Group:
MODEM POOLING
DATA RATE
2.
3.4.5.6.
7.
8.
9.10.64000 bps:
56000 bps:
19200 bps:
9600 bps:
4800 bps:2400 bps:
1200 bps:
300 bps:
Low:13.
14.
15.
16.
17.Originate Mode:
Answer Mode:
Modem Type:
Clock:
First Choice:
18.
19.Test Type:
Host Access Clock:
11.
12.Synchronous:Duplex:½
Connected to CC0 ON-LINE½*
enter command:½
Figure 7-11. Procedure 100 Word 2: Trunk Group Data Characteristics (System 85 R2V4)½
Procedure 100 Word 3: ISDN Trunk Group Signaling Options
With System 85 R2V4, the two attributes (trunk type and signaling type) are separated and translated as
individual parameters. Figure 7-12, Procedure 100 Word 3: Trunk Group/Trunk Type — Signaling
Type Translations (System 85 R2V4), depicts the procedure for translating the signaling type and
associating that attribute to a particular trunk group or trunk type.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-28ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 85½
ENHANCED MODE — PROCEDURE: 100, WORD: 3
TRUNK GROUPS — SIGNALING AND OTHER PARAMETERS
1.
2.
3.
4.
5.
6.
7.
8.
9.Trunk Group:
Signaling Type:
Glare:
Retry:
Outgoing Maintenance Busy Out Seizure:
Incoming Permanent Seizure:
Failure Threshold:
Optional ISDN Information Inhibited:
Network Service Value:
DISPLAY ONLY
10. Trunk Type:
Connnected to CC0 ON-LINE½*
enter command:
Figure 7-12.Procedure 100 Word 3: Trunk Group/Trunk Type — Signaling Type Translations
(System 85 R2V4)
Specifies a trunk group. Permitted entries include any not already used number within
the range of 18 to 999.
Administers or changes the signaling type for the trunk group.
For all ISDN trunking applications except DCS, glare is resolved by the ISDN
protocol. Glare is discussed in more detail in chapter 2, Network Connections and
Configurations. Specifically, ISDN negotiates the losing call to a different channel if
the original channel is preferred. Exclusive calls (such as DCS) are not negotiated and
the user hears the reorder tone. In either case, the network interface has priority over
the user interface when both calls are preferred or exclusive. This capability is
administered in procedure 262, word 1, and field 5. Therefore, this field 3 entry may
be any of the available encodes (0, 1, or 2) since this field is ignored for ISDN
applications.½
½Field 1
Field 2
Field 3½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 857-29
0
1
Field 5
Field 6
Field 7Field 4Retry permits multiple attempts to seize a busy trunk from the specified trunk group.
This field is primarily applicable for those trunk groups routed over analog facilities
and use one of the following trunk types: 41, 42, 43, 46, or 47. Depending on the
particular configuration, RETRY may or may not be applicable for ISDN applications.
Field encodes and their descriptions are:
When multiple retry is not desired RETRY NOT ACTIVE. The ISDN-PRI
protocol contains retry capability. When signaling type 20 is selected, 0 encode is
required.
Recommended for ISDN applications where the 40-series of trunk types is used.
Encode 1 enables a double retry and thus provides slightly improved call
completion, particulary for large trunk groups that span across more than one
transmission facility.
Not applicable for ISDN applications. Therefore, the required option must be 0 for not
active.
Not applicable for ISDN applications. Therefore, the required option must be 0 for not
active.
Not applicable for ISDN applications. Therefore, the required option must be 0 for no
failure threshold. See field 17 of procedure 107, word 5, for related information.
NOTE: This field is only applicable for analog trunk facilities. It permits the
user to establish a trunk failure threshold that, when exceeded, will generate an
alarm. The threshold limit will affect service availability and, on an indirect basis,
the customer’s maintenance costs.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-30ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 85
Field 8Selects whether the optional ISDN information is transmitted and access to other ISDN
network features is desired.
The optional ISDN IEs include the following:
l
l
l
l
l
l
lCalling number display
*Connected party number
*User-to-user information
*Called party name
*Calling party name
*Data mode 3 parameters
*Traveling class marks
NOTE: Those items identified with an asterisk (*) can only be passed through
the ISDN public network, on an end-to-end basis, whenever all interoffice
signaling links use CCITT signaling system number 7 (SS7).
Field encodes and their descriptions are:
-(Dash) only applicable whenever ISDN is not available
0
Recommended for all ISDN configurations, both public and private network
arrangements.
1
When the optional ISDN IEs are not to be transmitted.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 857-31
Field 9A CBC function used in conjunction with trunk verification by station (TVS) which
specifies the requested network service. The following table shows permitted field
entries that support signaling type 20.½
½
½
½
½
Trunks Supporting Signaling Type 20
Trunk
DescriptionTrunk
Type½
½
CO
Data
DID
DMI (Note 2)
FX
ISDN
M/S TIE
Special
TIE
WATS
16, *17 (Note 1), 18, 19, 20
100—107
*30, *31
*108, *109
21—25
120 (Note 3)
70—78
2, 5, 6, 50—58, 62, 65—67, 90—93
32—40, *41, *42, *43, 44, 45, *46, *47
26, *27, 28½
½
½
½
½
½
½
½
½
½
NOTES:½
1.Trunk types preceded with an asterisk (*) may be selected by trunk type 120 on an as needed
Call-By-Call (CBC) Service Selection basis.
2.
Trunk types not included in these categories may not be translated for ISDN-PRI service. Most
conventional trunk types specify, as a part of their name, an in/out signaling sequence for default
signaling types. Actually, these signaling sequences are disabled and type 20 signaling is used
exclusively over ISDN facilities.
3Beginning with the 1.0 software load of Generic 2 and the 1.2 software load of System 85 R2V4
digits may be inferred when using the ISDN-dynamic trunk type. The default of 30 infers DID
(if necessary). A default of 46 infers AAR/ARS. (See Appendix C, “Administrative Procedure
Summary,” for a complete explanation of this field.)
Field 10½Used as a display-only field. The field displays the trunk type that was administered in
procedure 100, word 1.½
Procedure 101 Word 1: ISDN Trunk Group, CDR, Digital Loss Plan, and AVD Assignments½
Procedure 101, word 1, is used primarily to start CDR, as well as translate the digital loss plan and
AVD options. Figure 7-13, Procedure 101 Word 1: Additional Trunk Group Translations (System 85
R2V4), depicts this procedure.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-32ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 85½
ENHANCED MODE — PROCEDURE: 101, WORD: 1½
TRUNK GROUP CHARACTERISTICS
1.
2.
3.
4.
5.
6.
7.
8.
9.Trunk Group:
APLT Features Allowed:
Disconnect Supervision:
Balance:15.
16.
17.
Battery Reversal:
Incoming Prefix Digit:AVD:
DCS:
Touch-Tone In:
Touch-Tone Out:
CDR Active:
AIOD Billing Number:
TIMED RECALL
10.
11.Time:
Level:
12.
13.
14.CDR Variable Timer:
Pad Group:
Tie Toll:
Connected to CC0 ON-LINE½*
enter command:
Figure 7-13. Procedure 101 Word 1: Additional Trunk Group Translations (System 85 R2V4)½
Field 1
Field 2
Field 3
Field 4
Field 5½Displays the trunk group number, such as previously translated in procedure 100.
Selects whether the trunk group uses balanced transmission facilities. Field encodes
and their descriptions are:
0
Not provided — the required option for ISDN-PRI.
1Provided — not applicable for ISDN-PRI.
Translates the battery reversal option. Field encodes and their descriptions are:
0
Not provided — the required option for ISDN-PRI
1Provided — not applicable for ISDN-PRI
Depending on how each type of DID service is provisioned it may or may not be
necessary for the switch to infer (generate) a digit to complete the call. Field encodes
and their descriptions are:
lDash (–) is applicable for all ISDN-PRI applications except DID (trunk types 30,
31, and 120).
lAny single digit number (0 through 9). Which number is determined by the trunk
group and its application.
NOTE: When using System 85 R2V4 1.1 software, digits cannot be inferred
for ISDN-dynamic trunk types.
Assigns whether the trunk group is (1) or is not (0) used for DCS applications.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4