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

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-83
ENHANCED MODE — PROCEDURE: 014, WORD: 2
BEARER CAPABILITY CLASS OF SERVICE — DATA OPTIONS
1. Bearer Capability COS:
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 Speed:
11.
12.
13.
14.Synchronous:
Duplex:
Clock:
Default Data Rate:
Connected to CC0 ON-LINE
enter command:
Field 1
Field 2-10
Field 11
Field 12
Field 13
Field 14Figure 7-38. Procedure 014 Word 2: BCCOS Data Options
Translates BCCOS modem pool support. Field encodes and their descriptions are:
l     Dash (–) is used when the BCCOS does not support modem pools
l     Numbers between (0 and 255)
These fields select the data rates (64000, 56000, 19200, 9600, 4800, 2400, 1200, 300,
or low speed) supported by this modem pool. Field encodes and their descriptions are:
0 Not supported
1 Supported
Defines if synchronization is 
(1) or is not (0) supported.
Defines if half 
(1) or full (0) duplex operation is supported.
Defines if an external 
(1) or an internal (0) clock source is used.
Whenever a modem pool supports more than one data rate it is generally desirable to
assign one data rate as a default or first choice. Field encodes and their descriptions
are numbers (1 through 9; which correspond to Low, 300,...64000-bps respectively).
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-84ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Procedure 010 Word 4: Line Side (B-Channel) ISDN Routing Options
Figure 7-39, Procedure 010 Word 4: Line Side (B-Channel) ISDN Routing Options, depicts this½
procedure.½
ENHANCED MODE — PROCEDURE: 010, WORD: 4
EXTENSION CLASS OF SERVICE — RESTRICTIONS
1.
2.
3.Class of Service:
Maximum Precedence Level:
ISDN Routing:
Connected to CC0 ON-LINE
enter command:½
Field 1
Field 2Figure 7-39. Procedure 010 Word 4: Terminal COS Restrictions (Generic 2)
When ISDN is administered, each COS assignment must have an associated BC and
ISDN routing assignment. That is to say that whenever ISDN is enabled, all COS
assignments must also be translated for procedure 010, word 4. COS assignments
must be within the 2-digit range of 1 through 63.
This fields encodes are only useful for AUTOVON applications. Dash (-) is
appropriate for ISDN applications.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-85
Field 3* This field shows the ISDN-PRI routing option. Field encodes and their descriptions
are:
0 Any type of trunking facility is OK. The 0 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 (for example, SID/display).½
1 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).
NOTE: Mode 0 data, depending on its origin, may require a restricted
channel. Recall that an unrestricted channel is only provided by those ISDN-
PRI facilities that use the B8ZS line-coding format.
2 Any trunking facility will work but 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 (such as with the Integrated Telemarketing Gateway or ITG). Figure 7-40, Procedure 100
Word 1: Trunk Group Type Signaling and Dial Access (ID) Code, depicts this procedure.½
½
½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-86ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
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.
9.Trunk Type:
Dial Access Restriction:
Personal CO Line Appearance:
Public Network Access/Egress:
DISPLAY ONLY
10. Signaling Type:
Connected to CC0 ON-LINE
enter command:
Figure 7-40. Procedure 100 Word 1: Trunk Group Type Signaling and Dial Access (ID) Code½
½
Field 1
Field 2
Field 3
Field 4
Field 5
(Generic 2)
Assigns a trunk group number. Permitted entries include any not already used number
within the range of 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 include digits 0
through 9.
Assigns the third digit of the trunk access code. Permitted entries include digits 0
through 9.½
Assigns the fourth digit of the trunk access code. Permitted entries include digits 0
through 9.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-87
Field 6Defines the trunk type of a specific trunk group. The ISDN-PRI facilities may be used
to support several different trunk types. These may include both conventional trunk
types as well as the ISDN-dynamic trunk type. An important point to remember is that
the particular service application and the incoming digits are the primary determining
factors that control which trunk type is selected. Most service applications may be
supported (over ISDN facilities) by either a conventional trunk type or ISDN-dynamic.
Table 7-10, Trunks Supporting Signaling Type 20, shows some permitted field entries
that support signaling type 20.
NOTE: Trunk types not included in the categories listed in table 7-10 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.½
½
½
TABLE 7-10. Trunks Supporting Signaling Type 20½
Trunk
DescriptionTrunkType
2-way CCSA/APLT
CO
Data
DID
DMI
FX
ISDN
M/S TIE
Special
TIE
WATS12—15
16, *17 (Note), 18—20
100—107
*30, *31
*108, *109
21—25
120
70—78
2, 5, 6, 50—58, 62, 65—67, 90—93
32—40, *41, *42, *43, 44, 45, *46, *47
26, *27, 28
NOTE: Trunk types preceded with an asterisk (*) may be selected by trunk type 120 on an as needed
CBC Service Selection basis.
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.
For 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 (CBC) basis. For example,
one incoming call over the group may expect station number digits (for example, a MEGACOM call),
while the next call over the group may expect a network number (for example, an SDN call).
This trunk type allows flexibility in processing calls as opposed to a fixed static trunk type. 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
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-88ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
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.
Field 7
Assigns the dial access code restriction. Field encodes and their descriptions are:
0 Allows access to the trunk group via a dial access code.
1 Restricts and only allows access to the trunk group for trunk testing and for
providing unattended console service.
Field 8
Field 9½
Field 10Assigns the trunk group as a Multifunction Terminal CO line appearance. This is not
applicable to ISDN so assign encode 0 here.
Assigns the type of network access for the trunk group. Encodes are:
0 Allows access to the public network
1 Allows access to private network facilities
Displays and verify that the type of trunk signaling is correct. ISDN uses message-
oriented signaling. Therefore, encode 20 should be displayed.
Procedure 100 Word 2: Trunk Group Data Translations
This word is used to administer data characteristics for each trunk group (including BCCOS). Figure 7-
41, Procedure 100 Word 2: Trunk Group Data Translations, depicts this procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-89
ENHANCED MODE — PROCEDURE: 100, WORD: 2
TRUNK GROUPS — MODEM POOLING AND BCCOS
1.
2.Trunk Group:
Bearer Capability Class of Service:
MODEM POOLING
3.
4.
5.
6.Originate Mode:
Answer Mode:
Modem Type:
First Choice:
7. Test Type:
Connected to CC0 ON-LINE
enter command:
Figure 7-41. Procedure 100 Word 2: Trunk Group Data Translations (Generic 2)
Field 1
Specifies a particular trunk group. The field encode will be the same as previously
translated in procedure 100, word 1.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-90ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 2Assigns a BCCOS to the trunk group. This field is used for non-ISDN to ISDN
tandem connections. The permitted range of encodes is (0 through 255). Field
encodes and their descriptions are:½
0 Voice
1 Mode 2 Data
2 Voice
3 Unknown Digital
4 Unknown Analog
5 Voice Grade Data
6 Mode 0 data
7 Mode 1 data
8 Mode 3 data
9 X.25 Packet Switched on B-channel½
NOTE: All calls use the BCCOS assigned to preferences in routing patterns as
administered in procedures 309 word 1 and 321 word 5. If not assigned to
preferences, the preference will default to the BCCOS of the associated trunk
group.½
½
½
½
Procedure 100 Word 3: ISDN Trunk Group Signaling Options
The trunk type and signaling type attributes are translated as individual parameters. Figure 7-42,
Procedure 100 Word 3: ISDN Trunk Group Signaling Options, depicts this procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							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:
Connected to CC0 ON-LINE
enter command:½
Specifies a trunk group. Permitted entries include any not already used number within
the range of 18 to 999.
ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-91
Figure 7-42. Procedure 100 Word 3: ISDN Trunk Group Signaling Options (Generic 2)
Field 2
Specifies the signaling type for the trunk group. For ISDN, use signaling type 20.
Field 3
For all ISDN trunking applications except DCS, glare is resolved by the ISDN
protocol. Therefore, this field is ignored for ISDN applications.
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 has priority over the user
when both calls are preferred or exclusive. This capability is administered in field 5 of
procedure 262, word 1. Field 1½
½
½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-92ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 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 uses 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:
0 Multiple retry is not desired, that is retry not active
NOTE: The ISDN-PRI protocol contains an automatic retry capability.
Whenever trunk type 120 is selected, the zero (0) encode is required.
1 Recommended for ISDN applications where the 40-series of trunk types is used.
This encode enables a double try single retry and thus provides slightly improved
call completion, particularly for large trunk groups that span across more than one
transmission facility.½
½
Field 5
Not applicable for ISDN applications (encode must be 0 for not active).
Field 6Not applicable for ISDN applications (encode must be 0 for not active).
Field 7
Not applicable for ISDN applications (encode must be 0 for no failure threshold).
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.½
Field 8
Permits user control of whether optional ISDN IEs are transmitted and whether access
to other ISDN network features is desired.½
The optional ISDN IEs include the following:
l     Calling number display
l     *Connected party number
l     *User-to-user information
l     *Called party name
l     *Calling party name
l     *Data mode 3 parameters
l     *Traveling class marks
NOTE: Items preceded with an asterisk (*) are only transmitted on an end-
to-end basis whenever all public network links are provided with CCITT
interoffice communication.
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 Do not transmit the optional ISDN IEs.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4