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

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-63
Field 13Assigns whether a DS1 facility (translated in field 12) will be used as the primary or
secondary synchronization source to the switch. Field encodes and their descriptions
are:
0 Assigns that the facility is not used as a synchronization source
1 Assigns that the facility is the primary synchronization source
2 Assigns that the facility is the secondary synchronization source
NOTE: The primary must be administered before the secondary. The secondary
must be removed before the primary.
Traditional modules may be configured with the ANN11 and/or ANN35 circuit packs.
Only the slot translated 1 (primary) and/or the slot translated 2 (secondary) must be
configured with synchronization cables. These cables connect the backplane of the
translated DS1 to the backplane of the TN463. The cables are identified as group 334
for intercabinet and group 361 for intracabinet applications. When traditional modules
are translated, field 20 will display the number (code 99) which shows that the switch
could not read information from the DS1 circuit pack.
Universal modules may be configured with the TN767 circuit pack. The intercabinet
cable (group 503) is required to connect to the TN463 SC, which will always be
located in the TMS cabinet. For universal modules, whenever this field is translated,
field 20 displays a number which corresponds to:
a.Whether the circuit pack is used as a synchronization source
b.If it is a synchronization source, then which type
c.Which cable connector (cable 0 or cable 1) contains the circuit pack
synchronization leads½
½
½
½
½
CAUTIONA loop-timing problem can be created if synchronization sources are not
administered correctly. The loop-timing problem exists as the result of
an error where both switch endpoints (for the same T1-span) are
administered as the primary. This causes the clock frequency to vary
widely and can bring down the switch. Loop-timing problems can be
avoided by following a correctly engineered network synchronization
diagram.½
½
½
½
½
½
½
NOTE: Depending on the application type (encode) translated, there may be
additional administration, slot, and port grouping restrictions.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-64ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 14Field encodes and their descriptions are:
0 Assigns that the DS1/DMI-BOS channels can be used for both trunks and lines
(mixed); the latter is frequently called off-premises stations (OPS).
1 Assigns that the interface is used to provide DMI-BOS trunks. The DMI-BOS
trunk groups are defined using procedure 100, word 1 (encode 108 and/or 109).
DMI-BOS applications use the switchs DS1 to provide a high-speed multiplexed
data interface for connecting to compatible computers. The computers may be
located on the same customer premises as the switch or many miles away. The
DS1/T1-carrier facilities are used between the switch and remote computers.
The DMI-BOS application provides 23 data channels plus 1 signaling channel.
Each data channel can be considered a 64K-bps clear-channel. However,
permissible data rates depend on the trunk group translations selected in procedure
100, word 2.
24th-channel signaling is the only required service/facility option. All others
(framing format and line coding format) are DMI application independent.
However, the distant computer and all intermediate T1 transmission equipment
must be compatible; refer to the caution regarding B8ZS line format and data
communication protocols.
The ACCUNET switched digital service can be provided by setting up a trunk
group with encode 109. However, a DS1 must be optioned for RBS (procedure
260 field 8). The only other administration requirement is that the trunk groups
translation (field 3 of procedure 100, word 2) be enabled for 56K-bps encode one.
The trunk group used to provide ACCUNET switched digital service may contain
as few as 1 or as many as 24 members. Therefore, the same DS1 may also be½
½
½
½
½
½
used to provide CO, FX, WATS, DID, and Remote Access trunks.
2 Assigns that the DS1 provides 24 lines. These are generally called off-premises
stations (OPS).
When a DS1 facility is used exclusively for lines, it must be administered for RBS.
Also, the facility cannot be used as a synchronization reference.
When a DS1 is administered for lines (OPS), it provides 24 channels that terminate
in a remote D4-channel bank, CDM, or their equivalent.½
½
Analog equipment location assignments are administered by procedure 000, word 1,
with field 8 translated to a 2. The DSl/OPS channels are translated to equipment
locations (individual extensions) with procedure 000, word 1, with field 8 translated
to a 9, rather than with procedure 116 that was used for trunks.
5 Assigns that the DS1 is used to provide DMI-MOS or ISDN-PRI trunk facilities.
NOTE: When encode 5 is administered, procedure 262 is automatically
translated with standard default options. These default options should be
rechecked later for consistency with the distant end (refer to procedure 262,
word 1).½
½
½
½
½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-65
Field 15Some facilities require that the contents of the D-channel be inverted to guarantee that
the minimum ones density be maintained (that is, ZCS line coding is used). This field
shows whether the D-channel is inverted or not. Field encodes and their descriptions
are:
- (Dash) not applicable or ZCS line coding is translated in field 9. The dash is
appropriate for all applications of the ANN11 circuit pack. RBS does not use the
24th-channel to transmit signaling information. 24th-channel signaling via the BOS
interface uses A and B bits for signaling and the channel structure is such that the
ones-density is never violated.
0 Assigns that the signaling information, contents of the D-channel, is inverted.
Either 0 or 1 must be administered for ISDN-PRI. Recall that B8ZS is
recommended for ISDN-PRI applications. However, not all transmission facilities
will permit B8ZS on an end-to-end basis. Administration must be coordinated with
the network facilities/distant end to ensure compatibility.
NOTE: This field must be a dash (–) when ZCS line coding is selected with½
½
½
½
½
½
ISDN and for automatic inversion of the D-channel.
1 Assigns that the signaling information, contents of the D-channel, is not inverted.
Option 1 (no inversion) is strongly recommended for use when B8ZS is
administered in field 9.
NOTE: When connected to a 4ESS, you must inform the 4ESS on the order
form whether bits are or are not inverted.
Field 16Field encodes and their descriptions are:½
½
½
½
½
½
- (Dash) DS1/DMI-BOS applications should be administered with a dash (-).
0 Indicates that DMI-MOS/ISDN-PRI applications use metallic cable facilities.
1 Indicates that DMI-MOS/ISDN-PRI applications use nonmetallic cable facilites.
NOTE: Terminating fiber cable directly on the DS1/MFAT carrier or
universal module port carrier is not currently supported. Therefore, this option
is not applicable.
Field 17½
This field is added to bring System 85 R2V4 into compliance with EIA specification
PIN-1429. This EIA specification relates to bit-oriented-signaling (BOS); message-
oriented-signaling (MOS) is defined by a CCITT specification.
Field encodes and their descriptions are:½
½
*½
½
½
½
-
0
1
(Dash) not applicable
NOTE: The dash is appropriate for all applications of the ANN35 and TN767
circuit packs (both DMI-MOS and ISDN-PRI).
Appropriate for all applications of DS1/DMI-BOS except when connecting to a
switch that uses the Canadian style of signaling.
Used when connecting to a DS1/DMI-BOS that uses the Canadian style signaling
as specified in PN-1429.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-66ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 18Loop length refers to the total cable distance between the switch and the NCTE, CDM,
BCM32000, DSX-1 cross-connect, and T1 office repeater. Traditional modules may
contain the ANN11 and/or ANN35 circuit packs. Both circuit packs contain DIP
switches for setting the compensation value [refer to table 3-1, System 85 Traditional
Module Equalizer Settings (Metallic Cable) ]. Therefore, software administration is not
applicable and the (–) should be administered for traditional modules.
Universal modules may contain the TN767 circuit pack. Line compensation value be
administered in software. Table 7-7, TN767 Compensation Values, identifies the
appropriate administration encode for distance intervals of 133 feet up to a maximum
distance of 655 feet.
TABLE 7-7. TN767 Compensation Values½
½
Distance to Midpoint
or Endpoint (FT)Compensation
22 AWG ABAM & 24 AWG PDS
26 AWG PDSValue
0 to 133
0 to 90
0
133 to 26690 to 180
1
266 to 399
180 to 270
2
399 to 532270 to 360
3
532 to 665
360 to 4504
NOTE: Compensation values assume 22-gauge ABAM or 24-gauge PDS cables. Two switches
(colocated) can be up to 1310 feet apart with maximum compensation on both systems. If 26-gauge PDS
cables are used, distances are reduced as assigned.
Field 19The T1 office repeaters or T1 line repeaters can be used when the on-premises distance
limitation is exceeded. A T1 office repeater is required at each end of the connection
to provide an interconnection range of up to 3000 feet. Each repeater only provides
regeneration for the receive direction. The T1 line repeaters can be used to
accommodate distances up to 6000 feet between switches. The T1 line repeaters can
be used in tandem to accommodate greater distances.
Field encodes and their descriptions are:½
—
0
1(Dash) required option for all traditional modules. It is also required for all ISDN-
PRI links provided with universal modules.
Preferred for DS1 service provided with universal modules (shows that a DS1
provides standard DMI-BOS).
Assigns that the DS1 provides the AT&T proprietary method of signaling on the
24th channel. This option is required when connection to System 75 that uses
TN722 circuit packs.
NOTE: When connecting to a TN722B or ANN11 circuit pack, the
recommended option is (0).½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-67
Field 20This display-only field serves to show which cables contain which synchronization
cables.
Procedure 262 Word 1: Additional DMI-MOS/ISDN-PRI Facility Options
Procedure 262 is used to administer the ANN35 and TN767 circuit packs. Figure 7-29, Procedure 262
Word 1: Additional DMI-MOS/ISDN-PRI Facility Options (Generic 2), depicts this procedure.½
ENHANCED MODE — PROCEDURE: 262, WORD: 1
ISDN BOARD PARAMETERS
EQUIPMENT LOCATION
13. PRI Interface Identifier:
1.
2.
3.
4.
5.Module:
Cabinet:
Carrier:
Slot:
Circuit:
PRI PARAMETERS
6.
7.
8.Interface Type:
Facility Test Code:
Terminal Endpoint Identifier:
PRI AND BRI LAYER 2 PARAMETERS
9.
10.
11.
12.Timer T203:
Timer T200:
Counter N200:
Counter K:
Connected to CC0 ON-LINE
enter command:
Figure 7-29. Procedure 262 Word 1: Additional DMI-MOS/ISDN-PRI Facility 0ptions (Generic 2)½
Fields 1-4
Assigns the circuit pack to an equipment location. These include the module number,
cabinet number, port carrier number, and slot number.½
NOTE: Entries for these four fields are the default values from translating a 5 in
field 14 of procedure 260. These entries should always be correct.½
Field 5BRI Only
For ISDN-PRI and DMI-MOS applications, the dash (-) is appropriate.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-68ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 6Assigns this interface as the user (0) or the network (1) side. When connected to a
4ESS, the customer premises switch is always the user side. When not connected to a
4ESS (that is, when connected to another switch), one switch is the user side and the
other the network side.½
½
½
For MOS facilities (such as DMI-MOS and ISDN-PRI), each link must be segmented
into user and network sides. At a Generic 2, each MOS-based facility connected to the
public network is administered as the user side, while other connections (such as that
to a 4ESS) are administered as the network side. For private network DMI-MOS and
ISDN-PRI connections, additional care must be exercised in defining user and network
sides. Specifically at each facility, only one end must be administered as the user side
(0) while the alternate must be defined as the network side (1). If the private network
node is a tandem switch, then that node may function as both user side and network
side depending on the particular facility.½
½
½
NOTE: Whenever a Generic 2 connects to a host computer via MOS, the
computer should always be assigned as the network side.½
Field 7This field is used for administering one of four facility test codes. For most
installations it is desirable to enable or establish permission, thus allowing selected
maintenance software to test the DMI-MOS/ISDN-PRI transmission facility on a
demand basis.
Procedure 648 contains several tests that may be done on a demand basis (by executing
procedure 648) whenever facility test codes 1, 2, or 3 are administered.
The DMI-MOS/ISDN-PRI communication protocol consists of three layers or levels.
Level 1 is the physical layer. Level 2 is the data link layer. Level 3 is the network
layer [also called the link access procedure on the D channel (LAPD)].½
Field encodes and their descriptions are:
0 Disables or prohibits maintenance testing from being done on the specified
(module, cabinet, carrier, and slot) transmission facility.
1 Assigns that a level-2 test may be executed via procedure 648.
Encode 1 should be translated for all DMI-MOS to host computer links.½
2 Assigns that only the level-3 network layer may be tested.½
3 Permits both level-2 and level-3 tests to be done.
Encode 3 should be used for all ISDN-PRI connections that terminate on a 4ESS if
the Generic 2 is equipped with an SN261C analog/digital facility test circuit pack.
If an SN261C is not present, use encode 1 instead.½
½
Fields 8-12 are assigned the default values when the ANN35/TN767 circuit pack is assigned in
procedure 260.½
Field 8This field accepts encodes from 0 to 126. However, all point-to-point (nonswitched)
links, such as a System 85 R2V4 or Generic 2 DMI-MOS link to a host computer, must
be administered with encode 0 (the default value).½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-69
Field 9The field accepts encodes from 0 through 255, which correspond to 1 second intervals
for a maximum elapsed time of 4 minutes and 15 seconds. The default value for this
T203 timer is 30 (30 seconds). This timer functions to monitor the facility data link
and specifies the maximum time allowed without frames being exchanged on a data
link layer connection.
Field 10The field accepts encodes from 0 through 255, which correspond to 0.1 seconds per
increment for a maximum range of 25.5 seconds. The default value for this T200
timer is 10 (1 second). This timer functions to monitor multiple frame operation on
the data link layer.
Field 11This field defines a value for the N200 counter. The value determines the maximum
number of frame retransmissions. Permitted are 1 to 10, with 3 being the default
value.
Field 12
This field defines a value for the K counter. The value determines the maximum
number of outstanding or unacknowledged information I frames. Permitted values are
1 to 10, with 7 being the default value.
NOTE: Administration values for these procedure 262 timers and counters must
be coordinated with the other terminating end.
Field 13NFAS-PRI Only
Use to specify NFAS arrangements (populate the ISDN interface ID within the channel
ID IE). This information must match exactly on each end of the facility and the
encode must come from the premise switch (as described in Technical Publication
41459). Field encodes and their descriptions are:½
½
l     Dash (–), the only value for non-NFAS arrangements
l     Any number within the range of (0 through 31) for NFAS arrangements.
Procedure 262 Word 2: ISDN-PRI D-Channel Backup
This procedure is currently only applicable for certain ISDN-PRI connections. Specifically, those
B-channel groups that use NFAS. Each of these groups is identified by a unique number known as the
D-Channel group number. For NFAS, fields 2 through 5 define the D-channel for a signaling group.
Figure 7-30, Procedure 262 Word 2: ISDN-PRI D-Channel Backup (Generic 2), depicts this procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-70ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
ENHANCED MODE — PROCEDURE: 262, WORD: 2
ISDN NFAS/D-CHANNEL BACKUP
1. D-Channel Group Number:
PRIMARY D-CHANNEL EQUIPMENT LOCATION
2.
3.
4.
5.Module:
Cabinet:
Carrier:
Slot:
BACKUP D-CHANNEL EQUIPMENT LOCATION
6.
7.
8.
9.Module:
Cabinet:
Carrier:
Slot:
DISPLAY ONLY
10. Number of Trunks Assigned to This D-Channel Group:
Connected to CC0 ON-LINE
enter command:½
Field 1Figure 7-30. Procedure 262 Word 2: ISDN-PRI D-Channel Backup (Generic 2)
Identifies a particular D-channel group number. The range of encodes is 1 through½
255.
NOTE: ISDN trunks are assigned to a specific equipment location in procedure
116. Procedure 116 is also used to assign ISDN-PRI circuits to the D-Channel
group numbers.
Fields 2-5
Assigns a particular circuit pack as providing the primary D-channel for the identified
D-channel group number. Table 7-9, Codeset Differences, depicts the permitted
equipment ranges.½
NOTE: The ISDN-PRI facility (slot) that is translated as the primary must have
also been translated for (23B + 1D) signaling, procedure 260, field 7, must use
encode 0.½
½
Fields 6-9
Assigns a particular circuit pack as providing the backup D-Channel (which is
optional) for the identified D-Channel Group Number. Table 7-9, Codeset Differences,
depicts the permitted equipment ranges.½
½
A prime objective for the design of each D-channel group is to have members from
two or more modules. By accommodating this objective, it is highly recommended
that the Backup D-Channel equipment location be a different module from that
selected as the Primary D-Channel. The ISDN-PRI facility (slot) that is translated as
the backup must be translated for (23B + 1D) signaling, procedure 260, field 7, must
have encode (0).½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-71
Procedure 262 Word 3: ISDN-PRI Codeset Map Assignments
Depending on the terminating switch it may be necessary to administer a Codeset Map Assignment and
convert from one codeset or codepoint to a different codeset or codepoint. This administration
assignment is required for ISDN-PRI links originating on a Generic 2 and terminating on a System 85
R2V4. Figure 7-31, Procedure 262 Word 3: ISDN-PRI Codeset Map Assignments (Generic 2), depicts½
this procedure.
ENHANCED MODE — PROCEDURE: 262, WORD: 3
ISDN LINK PARAMETERS
EQUIPMENT LOCATION
1.
2.
3.
4.
5.Module:
Cabinet:
Carrier:
Slot:
Circuit:
6.
7.Codeset Map Number:
Hyperactivity Management:
Connected to CC0 ON-LINE
enter command:
Figure 7-31. Procedure 262 Word 3: ISDN-PRI Codeset Map Assignments (Generic 2)½
Fields 1-4Assigns a particular equipment location/circuit pack to be given a codeset map number.½
Table 7-9, Codeset Differences, depicts the permitted equipment ranges.
Field 5
Assigns whether the circuit pack is BRI or PRI. dash (–) is appropriate for ISDN-PRI.
Field 6
Assigns a codeset map number. The permitted range is (0 through 15). Number
selection is arbitrary, however; a suggestion is start with 0 and select higher numbers
as needed.
When Codeset map numbers are translated they are assigned on a D-Channel Group
number basis. All ISDN-PRI circuits within a D-Channel Group must be administered
with the same Codeset Map Number.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-72ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 7Assigns whether hyperactivity management will be enabled for the ISDN-PRI link.
Hyperactivity is defined as erratic behavior by the D-signaling channel. Typically, a
hyperactive link will generate an excessive amount of meaningless traffic. Excessive
D-channel traffic may overload the module processor and degrade system performance.½
Field encodes and their descriptions are:
- (Dash) not applicable. This would be administered for all ISDN-BRI links.
0 Disables hyperactivity management for the particular ISDN-PRI link (this is the
recommended option for SNC links).
1 Enables hyperactivity management (recommended for all ISDN-PRI links except
SNC links). This software (hyperactivity management) functions to monitor link
performance, detect when certain error thresholds have been exceeded, busyout the
link on exceeding the threshold, and record the failure reason as FAULT CODE
337 in the maintenance log.
Procedure 280 Word 1: ISDN-PRI Receive/Transmit Codeset Mapping
This procedure is used to translate Codeset Mapping parameters. Because switches sometimes differ in
the codesets in which certain ISDN IEs are sent and also in the values of the opcodes of those IE,
Generic 2 has the capability to map the codesets and opcodes to accommodate these different
implementations across systems. For example, System 85 R2V4 implements the TCM IE in codeset 7
whereas Generic 2 implements it in codeset 6 by default. If Generic 2 must pass TCMs to or from a
System R2V4, it must map the TCM IE from codeset 6 to codeset 7. When connected to a 4ESS, this
mapping is necessary only if an R2V4 is present in an all-ISDN SDN network. Also note that the
opcode value of the TCM IE and display does not need to be mapped to a different value.½
½
½
½
½
½
½
½
Codeset mapping is implemented here as follows:½
In field 1, assign an index in the range 0 to 15½
In field 2, select Incoming½
In field 3, select a codeset to be mapped in the incoming direction½
In field 4, select an opcode (IE) belonging to the selected codeset½
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
In field 5, select the codeset on the Generic 2 to which the incoming codeset from field 3 is to be
mapped½
½
In field 6, select the opcode on the Generic 2 to which the incoming opcode from field 4 is to be
mapped½
½
Steps 2 through 6 can be repeated up to 256 times for the incoming case.½
When Outgoing is selected in field 2, repeat steps 3 through 7. For every incoming mapping there
should be an identical outgoing mapping.½
½
All of the above steps can be repeated up to 16 times (the number of map numbers available).½
For each ANN35 or TN767 containing a primary D-channel to which you want codeset mapping,
assign the map numbers in procedure 262, word 3.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4