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

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-93
Field 9Specifies the network service that is requested for trunk verification by station (TVS).
The following table shows permitted field entries that support signaling type 20.½
½
Trunks Supporting Signaling Type 20½
½
Trunk
DescriptionTrunkType½
CO
Data
DID
DMI (Note 2)
FX
ISDN
M/S TIE
Special
TIE
WATS16, *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.
2.
3.Trunk types preceded with an asterisk (*) may be selected by trunk type 120 on an as needed
Call-By-Call (CBC) Service Selection basis.
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.
Beginning with the 1.0 software load of Generic 2 and the 1.2 software load of System 85 R2V4
digits may be inferred where 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. This field displays the trunk type that was administered
in procedure 100, word 1.
Procedure 101 Word 1: ISDN Trunk Group, CDR, and Digital Loss Plan
Procedure 101, word 1, is used (primarily) to turn on CDR, as well as translate the digital loss plan.
Figure 7-43, Procedure 101 Word 1: ISDN Trunk Group, CDR, and Digital Loss Plan, depicts this
procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-94ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
ENHANCED MODE — PROCEDURE: 101, WORD: 1
TRUNK GROUP CHARACTERISTICS
1.
2.
3.
4.
5.
6.
7.
8.
9.Trunk Group:
Balance:
Battery Reversal:
Incoming Prefix Digit:
DCS:
Touch-Tone In:
Touch-Tone Out:
CDR Active:
AIOD Billing Number:
TIMED RECALL
10.
11.
Time:Level:
12.
13.
14.
15.
16.CDR Variable Timer:
Pad Group:
Tie Toll:
APLT Features Allowed:
Disconnect Supervision:
Connected to CC0 ON-LINE
enter command:
Figure 7-43. Procedure 101 Word 1: ISDN Trunk Group, CDR, and Digital Loss Plan (Generic 2)½
Field 1
Field 2
Field 3
Field 4
Field 5
Fields 6-7Displays the trunk group number, such as previously translated in procedure 100.
Assigns whether the trunk group has (1) or does not have (0) balanced transmission
facilities. Encode 1 is required for ISDN-PRI.
Assigns whether the trunk group has (1) or does not have (0) the battery reversal
option. Encode 0 is required for ISDN-PRI.
Assigns the number of prefix digits. Field encodes and their descriptions are:
l     Dash (–) is always applicable for ISDN-PRI applications except for DID trunks
(trunk types 30 and 31).
l     Any single digit number (0 through 9). Which number is determined by the trunk
group and its application.
Assigns whether the trunk group is (1) or is not (0) used for DCS applications.
This field is ignored for ISDN applications and either encode (0 or 1) may be
translated.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-95
Field 8Assigns or not assign the trunk group to CDR record keeping. Field encodes and their
descriptions are:
0 Trunk group usage not applicable for CDR recording
1 Trunk group usage will be recorded by CDR
2 Trunk group usage will be recorded, account code is required
Fields 9-11Not used for ISDN applications.
Field 12This field is only applicable when CDR is being used, and then only to change the
default CDR timer value. Field encodes represent intervals in 1-second increments.
The range is 1 through 99 with dash (–) being the default timer value of 6 seconds.
Field 13Administers the optional transmission loss assignments. The encode translated depends
on the network configuration and service application. Field encodes and their
corresponding loss plan are listed as follows:½
½
½
½
0
1
2
3
4
5
6
7
8
The Digital FIXED Loss Plan
ISL Tie Trunk
EIA Tie Trunk
NOTE: This is the recommended option for Speedial Access Connections to a
4ESS.
ISL Digital Central Office
EIA Digital Central Office
Digital Toll Office
Analog Toll Office
AUTOPLEX NETWORK Interface V
AUTOPLEX NETWORK Interface Y
Refer to chapter 4, The Digital Loss Plan, for a description of the digital loss plan and
to table 4-2, Digital Loss Plan (Port-to-Port Losses), in this same chapter for a list of
port-to-port loss values.
Fields 14-16
These fields are ignored by ISDN software. Either encode (0 or 1) is satisfactory.
Procedure 103 Word 1: Network Trunk Group Translations
This procedure is used to translate the trunk group network parameters. Figure 7-44, Procedure 103
Word 1: Network Trunk Group Translations, depicts this procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-96ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
ENHANCED MODE — PROCEDURE: 103, WORD: 1
NETWORK TRUNK GROUP TRANSLATION
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.Trunk Group:
Facility Restriction Level:
Network Trunk:
Main/Tandem:
Incoming Tie to AAR/ARS or APLT:
Authorization Code Required:
Bridge-On Allowed:
Trunk Reservation Limit:
AAR/ARS Prefix:
Data Protection (Permanent):
Remote Access Echo Suppressor:
AAR Conditional Routing:
Second TCM:
Digit Collection:
Connected to CC0 ON-LINE
enter command:
Figure 7-44. Procedure 103 Word 1: Network Trunk Group Translations (Generic 2)½
Field 1
Displays the trunk group number, such as previously administered in procedure 100
and 101.
Fields 2-13
The ISDN-PRI does not place any new or additional considerations on translating these
fields. The encodes that are translated are generally dependent on each trunk group, its
application, and the associated trunk groups.
Field 14
Specifies how the dialed digits are outpulsed. Field encodes and their descriptions are:
0 Digit outpulsing may overlap digit reception.
1 All digits must be received before outpulsing may start. All ISDN applications,
regardless of the trunk type, require that a (1) be translated in this field. Digit
outpulsing does not begin until all digits are received. Then digits are outpulsed as
ASCII characters — per the ISDN recommendations.½
Procedure 116 Word 1: DS1/DMI/ISDN-PRI Trunk Assignments
For more information, see chapter 6, Port Types/Installation Compatibilities. Each analog trunk circuit
pack provides four circuits that are administered by using procedure 150. Conversely, each DS1
provides 24 circuits (channels) that are administered by using procedure 116.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-97
For traditional modules, each DS1/MFAT carrier will support a maximum of two DS1s, each occupying
one slot and located in slots 5 and 18. When a DSl/DMI/ISDN interface (trunk applications) is located
in slot 5, it uses the six slots 0, 1, 2, 5, 6, and 7. When the interface is located in slot 18, it uses the six
slots 13, 14, 15, 18, 19, and 20. Figure 7-45, Procedure 116 Word 1: DSI/DMI/ISDN-PRI Trunk½
½
½
Assignments, depicts this procedure.
ENHANCED MODE — PROCEDURE: 116, WORD: 1
DS1 AND ISDN TRUNK ASSIGNMENTS
EQUIPMENT LOCATION
1.
2.
3.
4.
5.Module:
Cabinet:
Carrier:
Slot:
Circuit:
6.
7.
8.
9.
10.
11.Trunk Group:
Night Terminal:
Disable Signaling:
AIOD Equipment Number:
Interface Endpoint:
D-Channel Group Number:
Connected to CC0 ON-LINE
enter command:
Figure 7-45. Procedure 116 Word 1: DS1/DMI/ISDN-PRI Trunk Assignments (Generic 2)½
The DS1 channels are assigned to slot and circuit locations according to the order in which the module
processor scans the equipment carrier as shown in table 7-11, DS1/ISDN-PRI Administration — Channel
Versus Trunk Assignments.
When the traditional module DS1/MFAT carrier is configured with two DS1s, physical slots 3, 8, 16,
and 21 are available for other applications. If only one DS1 is configured, then six additional slots are
available for other applications.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-98ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
TABLE 7-11. DS1/ISDN-PRI Administration — Channel Versus Trunk Assignments½
DS1 ChannelSlot/CircuitDS1 Channel
Slot/Circuit
15/0 or 18/013
0/0 or 13/0
26/0 or 19/0
14
1/0 or 14/0
3
7/0 or 20/0152/0 or 15/0
4
5/1 or 18/1160/1 or 13/1
5
6/1 or 19/1
171/1 or 14/1
67/1 or 20/1
18
2/1 or 15/1
75/2 or 18/2
190/2 or 13/2
86/2 or 19/2201/2 or 14/2
97/2 or 20/2212/2 or 15/2
105/3 or 18/3220/3 or 13/3
116/3 or 19/3
231/3 or 14/3
127/3 or 20/3242/3 or 15/3
When the traditional module DS1-MFAT carrier is configured with two DS1s, physical slots 3, 8, 16,
and 21 are available for other applications. If only one DS1 is configured, then six additional slots are
available for other applications.
To minimize confusion and eliminate the need for maintaining elaborate trunk to channel cross-reference
tables, trunk group member assignments should match the DS1 channel assignments; for example, trunk
group member 1 on channel 1. For example, using procedure 116, word 1, refer to table 7-10,
DS1/ISDN-PRI Administration — Channel Versus Trunk Assignments, to determine which slot and
circuit to translate for channel 1. Repeat this procedure by sequentially selecting DS1 channels (2, 3,
and so on) and translating the appropriate slot and circuits as required.
Fields 1-5
These fields are used to translate the equipment location, including slot and circuit
(channel) location, and to associate the equipment location (channel) with the particular
trunk group translated in field 6.
Field 6
Translates the trunk group. Permitted encodes must be numbers with the range of 18
through 999.
Field 7
Translates a particular number that functions as the night service number. The digits
depend on the particular application and its numbering plan.
Field 8
Disables a channel’s signaling. This disable function is required for establishing a
dedicated switched connection. Field encodes and their descriptions are:
0 Signaling is enabled (default value).
1 Signaling is disabled. This option is only translated for the channels that is used as
a dedicated switched connection.
Field 9
Not applicable for ISDN-PRI.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-99
Field 10Assigns the function of the terminating endpoint. For PRI nodal services, this endpoint
is the network. Field encodes and their descriptions are:½
0 Another customer premises switch
1 A private network connection to a host computer
2 Public network connections
Field 11Translates the D-channel group number. These numbers should be coordinated with
field 1 of procedure 262, word 2. Field encodes and their descriptions are:
l     Dash (–), for non-NFAS arrangements.
l     Numbers within the range 1 through 255 for all NFAS arrangements.½
Procedure 012 Word 1: Name Database
The name database is used by those features (such as DCS, ISDN-PRI) which provide display type
information to voice terminals. Some examples of common display information are: calling party name,
vector directory number, and trunk group name. For ISDN-PRI applications, the name database
information is used to populate the display IE. Figure 7-46, Procedure 012 Word 1: Name Database,½
½
½
½
depicts this procedure.
ENHANCED MODE — PROCEDURE: 012, WORD: 1
NAME DATABASE — NAME TO BE DISPLAYED
1.
2.
3.
4.
5.
6.Extension, VDN, or Trunk Group:
Type:
Display Start:
Outgoing Trunk Display:
Copy Mode:
Extension, VDN, or Trunk Group to Copy or Share:
DISPLAY ONLY
7.
8.
9.Characters In Name:
Shared Primary Extensions or Trunk Groups:
Associated Extension Name Assigned:
Connected to CC0 ON-LINE
enter command:
Figure 7-46. Procedure 012 Word 1: Name Database (Generic 2)
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4½ 
						

							7-100ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 1Assigns either an extension number, vector directory number, or trunk group. Field
encodes and their descriptions are:
l    000 through 99999, for extension and directory numbers. Whether the number is
three, four, or five digits depends on the numbering plan.
l    18 through 999, for trunk group numbers.
Field 2Specifies whether the encode for field 1 is a trunk group or extension/vector directory
number. Field encodes and their descriptions are:
0 Trunk groups
1 Extension numbers and vector directory numbers
Field 3This field is only applicable for the identified extension’s display module. It controls
the number of blank spaces that are inserted before the first displayed character of the
name, dialed number, or trunk group name. Permitted encodes are numbers from 1 to
30.
Field 4The main function of this field is to provide some administration control over what is
displayed on the voice terminals digital display. Field encodes and their descriptions
are:
- (Dash) all incoming only trunk groups
0 The user (extension) does not want the outgoing trunk group name displayed but
does desire the dialed number to remain on the display
1 The user desires to display the name of the outgoing trunk group (for example,
ISDN/SDN, MEGACOM, CBC)
NOTE: For a tandem interworking call the name of the incoming trunk group
is transmitted in the display IE of the ISDN-PRI outgoing trunk group.
Field 5
Assigns the method used to define the name. Field encodes and their descriptions are:
0 Add a new name or change an existing name; requires that the name change be
made with word 2
1 Copy the name from the extension or trunk group displayed in field 6
Field 6This field is used with field 5 to copy an existing name to the extension or trunk group
identified in field 1. Field encodes and their descriptions are:
l    000 through 99999, for extension and directory numbers. Whether the number is
three, four, or five digits depends on the numbering plan.
l    18 through 999, for trunk group numbers.
Procedure 012 Word 2: Name Database
This word is used to translate a name (up to a maximum of 30 characters). Figure 7-47, Procedure 012
Word 2: Name Database, depicts this procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-101
ENHANCED MODE — PROCEDURE: 012, WORD: 2
NAME DATABASE — ENTRY
1. Segment:
CHARACTER ENCODES
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.Character 1:
Charaacter 2:
Character 3:
Character 4:
Character 5:
Character 6:
Character 7:
Character 8:
Character 9:
Character 10:
Connected to CC0 ON-LINE
enter command:½
Field 1
Fields 2-11Figure 7-47. Procedure 012 Word 2: Name Database (Generic 2)
Identifies one-of-three 10 character fields. Field encodes and their descriptions are:
1
2
3Characters 1 through 10
Characters 11 through 20
Characters 21 through 30
There exists 94 different encodes (00-12, 14, 15, 17-96) which correspond to
numbers 0 through 9, lower case letters, upper case letters, and special characters.
The Manager II help screen or the document DEFINITY Communications System
Generic 2 Administration Procedures (555-104-506) may be used for determining
the desired encodes.½
Each field should be translated with the encode that corresponds to the desired
character.
Procedure 012 Word 3: Name Database
Since the name database has the potential to use a large amount of memory it is generally desirable to
run the compact operation whenever all names have been added. Figure 7-48, Procedure 012 Word 3:
Name Database, depicts this procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-102ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
ENHANCED MODE — PROCEDURE: 012, WORD:3
NAME DATABASE COMPACTION
1. Compact:
DISPLAY ONLY
2.
3.
4.Names That Can Yet Be Assigned:
Words Available:
Words to Be Gained by Compacting:
Connected to CC0 ON-LINE
enter command:
Figure 7-48. Procedure 012 Word 3: Name Database (Generic 2)½
Field 1Assigns whether the name database is (1) or is not (0) to be compacted.
Fields 2-4Are display only and serve to show status of the database.
Procedure 279 Word 1: Network Facilities Coding
Each interexchange carrier (which provides public network ISDN service) must have a unique identifier
number. Furthermore, each carrier may provide multiple ISDN services and ISDN features that must be
individually identified via a Network Specific Facility (NSF) coding value. A NSF is an ISDN IE (sent
in the setup message) that is used to identify the network or feature associated with the call. When
connected to a 4ESS, a Generic 2 must send the appropriate NSF for MEGACOM, SDN, and
ACCUNET switched digital service calls. (MEGACOM 800 service calls do not require an NSF since it
is an incoming-only service and the Generic 2 cannot tandem it to another switch as a MEGACOM 800
call.)
NOTE: All NSFs must be defined in field 1 of this procedure prior to use in field 5 of procedure
309, word 5, and field 4 of procedure 321, word 5 should all have the same value.
Figure 7-49, Procedure 279 Word 1: Network Facilities Coding, depicts this procedure.½
½
½
½
½
½
½
½
½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4