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

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-73½
½
½
Table 7-8, Codeset Mapping Requirements, summarizes the current codeset mapping requirements for
Generic 2:½
½
Table 7-8. Codeset Mapping Requirements½
½
IECodeset MapOpcode Map
When Required½
TCM
DisplayMap from codeset 6 to codeset
7 outgoing.
Map from codeset 7 to codeset
6 incoming.
Map from codeset 6 to codeset
7 outgoing.
Map from codeset 7 to codeset
6 incoming.
Map from opcode 8 to opcode
8 in both directions.½
½If a System 85 R2V4 is present
in an end-to-end ISDN network
with Generic 2, this codeset
mapping is required.
If a System 85 R2V4 is present
in an end-to-end ISDN network
with a Generic 2, this codeset
mapping is required.½
½
½
½
Map from opcode 40 to opcode
40 in both directions. NOTE: Different interfaces can have different map numbers assigned. For example, one
interface can map the TCM to codeset 7 while another interface can map the TCM to codeset
0.½
½½
½
½
½
Figure 7-32, Procedure 280 Word 1: ISDN-PRI Receive/Transmit Codeset Mapping (Generic 2), depictsthis procedure.
ENHANCED MODE PROCEDURE: 280, WORD: 1
ISDN CODESET MAPPING
1.
2.Codeset Map Number:
Incoming/Outgoing:
MAPPED FROM CODESET/INFORMATION ELEMENT
3.
4.Codeset:
Information Element Opcode:
MAPPED TO CODESET/INFORMATION ELEMENT
5.
6.Codeset:
Information Element Opcode:
DISPLAY ONLY
7. Available Map Number Mappings:
Connected to CC0 ON-LINE
enter command:
Figure 7-32. Procedure 280 Word 1: ISDN-PRI Receive/Transmit Codeset Mapping (Generic 2)½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-74ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 1*Assigns a codeset map number (such as defined in procedure 262, word 3). Field
encodes and their descriptions are:
l     Dash (–), which disables codeset mapping.
l     Any number between 0 and 15 that is previously defined with procedure 262, word
3.
Field 2* Specifies whether codeset mapping is for incoming messages or outgoing messages.
Field encodes and their descriptions are:
0
1Assigns mapping for incoming messages.
Assigns mapping for outgoing messages.
From a Generic 2 perspective, incoming means mapped from Codeset 6 to Codeset
7. While outgoing means Codeset 6 is mapped to Codeset 7. Two-way trunk
groups will normally have a Codeset Map translated for both incoming and
outgoing.
Field 3
Specifies a mapped from codeset number. Permitted encodes are 0 to 7. These
numbers correspond to the respective codesets on a number-per-number basis.
NOTE: Currently, codeset 1 through codeset 5 are reserved for future use. Thus,
only encodes 6 and 7 are applicable for the codeset fields.
If field 2 is translated (0) for incoming then encode (7) is appropriate for field 3.
If field 2 is translated 
(1) for outgoing then encode (6) is appropriate for field 3.
Field 4Identifies the IE code to be mapped from. Field encodes and their descriptions are:
- (Dash) is available but not recommended. If a dash were translated, all IEs would
be mapped from one codeset to the other codeset on a one-to-one basis. Because
some codeset 7 IEs are different from their numerical equivalent in codeset 6, it is
generally NOT desirable to map on a one-to-one basis.
Table 7-9, Codeset Differences, identifies current IE differences between codeset 6
and codeset 7.
TABLE 7-9. Codeset Differences
IE Name
Codeset 6
CodeSet 7
Traveling Class Mark88
Logical Link Identification264
Display
40
40
Packet Layer Parameters
622
Link Layer Parameters641
number Any number within the range of (0 through 127).*
*
*
*
*
*
*
*
*½
½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-75
Field 5Specifies a mapped-to codeset number. Permitted encodes are numbers within the
range (0 through 7) These numbers correspond to the respective codesets on a
number-per-number basis.
If field 2 is translated one for incoming, then encode seven is appropriate for field 5.
Field 6
Identifies the IE code to be mapped to. Permitted encodes are the same as field 4.
Field 7
Each code set map number may contain up to a maximum of 255 incoming and 255
outgoing mappings. This display-only field shows the number of mappings that remain
(the number of unassigned mappings).
Procedure 354 Word 3: NPA-NXX Digits Assignment
This word and procedure are used to administer the ISDN numbering plan. Depending on the switch
configuration, there may be more than one ISDN numbering plan. Contents of these fields make up a
part of the station identification number (SID). The SID is transmitted in the calling number IE (part of
the setup message) or connect party number (part of the connect message).
NOTE: This word need not be translated unless the application requires that SID or the connected½
½
½
number be transmitted to the network. If the SID is to be passed through the ISDN network, then it
must also be administered here and in procedure 000, word 4.
Figure 7-33, Procedure 354 Word 3: NPA-NXX Digits Assignment (Generic 2), depicts this procedure.½
½
*
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-76ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
ENHANCED MODE — PROCEDURE: 354, WORD: 3
NPA-NXX ASSIGNMENTS
1.
2.
3.
4.
NPA-NXX Deesignator:
NPA:
NXX:
Thousands Digit:
Connected to CC0 ON-LINE
enter command:
Figure 7-33. Procedure 354 Word 3: NPA-NXX Digits Assignment (Generic 2)½
Field 1
This field should be translated for both private and public network connections. The
NPA-NXX designator is a 2-digit field and within the range of 1 through 99.
Field 2
This 3-digit field should contain the Numbering Plan Area (NPA), which is also called
the area code. The NPA is the area code in which the switch resides. Assignment is
therefore dependent on the particular location and application.½
Field 3This 3-digit field should specify the NXX, which is also called the office code of the
local exchange company. Permitted values must be those numbers within the range of
200 through 999 and must be the office code of the local exchange.½
½
Field 4This 1-digit field specifies the thousands digit. When not used, it should contain (–).
When used, digits 0 through 9 may be assigned. Use this field only with three-digit
dial plans. Do not use it with four- or five-digit dial plans.
Procedure 000 Word 3: Line-Side BCCOS Designator
This procedure assigns a BCCOS in field 5 to the extension shown in field 1. One implication of this½
COS is the pattern or preference selected for this extension on outgoing calls (see the Procedure 309
Word 5 and Procedure 321 Word 5 sections later in this chapter).½
½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-77
The 10 BCs are defined in field 16 of procedure 014, word 1. This definition codes the BC information
element (IE) in the setup message when the extension (that is, the extension in field 1 of procedure 000,
word 3) accesses an ISDN-PRI trunk for an outgoing call. Figure 7-34, Procedure 000 Word 3: Line-½
½
½
½
Side BCCOS Designator, depicts this procedure.
ENHANCED MODE — PROCEDURE: 000, WORD: 3
SINGLE TERMINAL - MISCELLANEOUS FEATURES
1.
2.
3.
4.
5.
6.Extension:
Hot Line:Dedicated Switch Connection Messages:
Audible Message Waiting - Automatic:
Bearer Capability Class of Service:
Universal Code Calling ID:
Connected to CC0 ON-LINE
enter command:
Figure 7-34. Procedure 000 Word 3: Line-Side BCCOS Designator½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-78ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Procedure 000 Word 4: NPA-NXX Index Designator
Depending on how the switch is used, procedure 000, word 4, may or may not be translated.
Specifically, word 4, field 4, is used for partitioning, ISDN, or both, and must be translated when:
a.     The switch transmits SID or connected number to the network
b.     The switch provides unique extension number partitions
Field 4 of procedure 000, word 4, need not be translated when: the switch does not transmit SID or
connected number to the network (public or private).
If the switch contains more than one office code, multiple NPA/NNX designators may be needed.
Figure 7-35, Procedure 000 Word 4: NPA-NXX Index Designator, depicts this procedure.½
½
ENHANCED MODE — PROCEDURE: 000, WORD: 4
EXTENSION NPA-NXX/PARTITION ASSIGNMENT
1.
2.
3.
4.First Extension:
Last Extension:
Extension Partition:
NPA-NXX Designator:
DISPLAY ONLY
5. Invalid Extension:
Connected to CC0 ON-LINE
enter command:
Field 1
Field 2Figure 7-35. Procedure 000 Word 4: NPA-NXX Index Designator
Assigns a single extension number or the first extension number for a block of
numbers. The single number or block of numbers will be unique in terms that they
relate to a single extension partition identification.
Assigns the last extension number for a block of numbers.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-79
Field 3Assigns the extension partition identification for the tenant services feature. This
number associates the single or block of extension numbers to a particular ISDN
facility (NPA-NXX Designator).
Field 4Associates an NPA-NXX Designator with the previously defined extension.
Procedure 210 Word 2: LDN, NPA, and NNX Attendant Partition Assignments
This procedure is used to configure the attendant consoles into groups known as attendant partitions.
Also, LDN and NPA-NXX assignments are completed, thus relating these assignments to a particular
attendant console or attendant partition. Figure 7-36, Procedure 210 Word 2: LDN, NPA, and NNX
Attendant Partition Assignments, depicts this procedure.½
½
½
ENHANCED MODE — PROCEDURE: 210, WORD: 2
CONSOLE ASSIGNMENT - ATTENDANT PARTITIONS
1.
2.
3.
4.
5.Console Number:
Attendant Partition:
Control:
LDN:
NPA-NXX Designator:
Connected to CC0 ON-LINE
enter command:
Figure 7-36. Procedure 210 Word 2: LDN, NPA, and NNX Attendant Partition Assignments
Field 1
Translates a console number. Permitted encodes are any 2-digit number within the
range of 1 through 40.
Field 2NOTE: This console must be previously assigned in procedure 210, word 1.
Assigns the attendant partition number. Permitted encodes are any unused number
within the range of 0-40.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-80ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Field 3Assigns the one console in the attendant partition that will be the controlling console.
All other members of this group must have control denied. Field encodes and their
descriptions are:
0 For all but the controlling console
1 Only for the controlling console
Field 4
Field 5Assigns or associate the LDN with a particular console or console partition. The
number is dependent on the switch or private network numbering plan.
Assigns or associate the NPA-NNX designator with the console or console partition.
The encode must be the same as that defined in procedure 354, word 3.
Procedure 014 Word 1: BCCOS Routing Options
This procedure is required to administer the attributes of each BCCOS assignment. Generic 2 permits up
to a maximum of 256 different numeric assignments. The switch software is supplied with numbers (0
through 8) already defined. Each number (0 through 8) has different default parameters. Therefore,
each number is unique and may be applied to a different type of routing configuration. It is currently
believed that these numbers may be applied to meet the needs of most routing configurations.½
If it is determined that the existing BCCOS numbers do not meet the needs of a particular routing
configuration, then new numbers may be defined. New numbers should begin with 255 and continue in
descending order. Refer to chapter 1, Introduction, for more information about BCCOS.½
The differences between System 85 R2V4 and Generic 2 are:
1.
2.With System 85 R2V4, BC and ISDN routing are administered in procedure 010, word 4; but,
with Generic 2 these are moved to procedure 014, word 1.½
With System 85 R2V4, the switch assumes that all user data/information will be presented for
transmission in a form called Restricted. Restricted means that the data/information is encoded so
that the all-zeroes octet will not occur. The DCP data modules encode user data into the form
Restricted.½
With Generic 2, the switch administration software (procedure 014 word 1, field 3) assigns½
whether user data/information is presented to the switch as Restricted or Unrestricted.
Unrestricted means that the data may contain the all-zeroes octet.
3.
With System 85 R2V4, the AVD bit shows when a modem pool is required. With Generic 2, the
BCCOS with AAR and ARS shows whether a modem pool is required.
Figure 7-37, Procedure 014 Word 1: BCCOS Routing Options, depicts this procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 27-81
ENHANCED MODE — PROCEDURE: 014, WORD: 1
BEARER CAPABILITY CLASS OF SERVICE — CALL OPTIONS
1.
2.
3.Bearer Capability COS:
Transport Mode:
Information Type:DEFAULT CAPABILITIES
14.
15.
16.Transport Mode:
Information Type:
Bearer Capability:
CALL TYPES AND ACTION TAKEN
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.Voice:
Voice Grade Data:
Mode 0:
Mode 1:
Mode 2:
Mode 3:
Unknown Digital:
Unknown Analog:
Mode 3/2:
X.25:
Connected to CC0 ON-LINE
enter command:
Field 1
Field 2
Field 3Figure 7-37. Procedure 014 Word 1: BCCOS Routing Options
Translates new (additional) BCCOS numbers. Field encodes and their descriptions are:
l     Dash (-) is used when the BCCOS does not support new numbers
l     Numbers between (0 and 255)
Assigns the transport mode. Field encodes and their descriptions are:
0 Circuit switch the call
1 Packet switch the call
2 Both circuit and packet
Specifies whether the endpoint is unrestricted (1) or restricted (0) with respect to
incoming calls.
It is the AAR/ARS software that routes calls. This software will block calls from an
unrestricted type to a restricted type. As a contrast, the software will route calls from
a restricted type to an unrestricted type. Furthermore, the software will route calls
from restricted to restricted, depending on other attributes of the two BCCOS encodes.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-82ADMINISTRATION OPTIONS AND REQUIREMENTS — GENERIC 2
Fields 4-13The translation parameters administered for fields 4 through 13 determine what actions
the switch will take for the BCCOS specified in field 1. Regarding Generic 2, it is
important to remember that the administration (of the BCCOS) determines when a
modem pool member is added and not the particular trunk type. By administering the
BCCOS on an AAR/ARS preference basis allows a single trunk group to support both
circuit switched and modem pooled calls. Field encodes and their descriptions are:½
0 Circuit switch the call
1 Insert a mode 2 modem pool
2 Block the call
Fields 14 through 16 are the default capabilities assumed by the switch for an originating facility (on
this switch) that does not have a BCCOS IE (non-ISDN). The switch assumes these default capabilities
are acceptable to the originating facility when it tries to connect the originating facility to the
terminating facility. These default capabilities are not the predefined BCCOSs that default through
administration.
Field 14
Assigns a packet switched (1) or a circuit switched (0) call transport mode
Field 15
Assigns a clear (1) or a restricted (0) channel type. This relates to calls outgoing from
an endpoint, except for DMI modes 0 or 3.
Field 16
The default BC class (BCC). Used for an outgoing call BC IE (except for BRI
modes). (See chapter 1, Introduction, for more information about BC and BCC.)
Field encodes and their descriptions are:½
½
0 Voice
1 Mode 1
2 Mode 2
3 Mode 3
4 Mode 0
5 Voice grade data
6 Unknown digital
7 Unknown analog
8 Mode 3/2
9 X.25
Procedure 014 Word 2: BCCOS Data Options
This procedure is used to define the data capabilities for the modem pools. The data rates selected are
dependent on local requirements and the particular type of analog modem used. Figure 7-38, Procedure
014 Word 2: BCCOS Data Options, depicts this procedure.½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4