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

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-133
Network Synchronization Options — DS1 and ISDN-PRI Applications
The 
SYNCHRONIZATION PLAN screen is used to specify which of the two DS1/T1-spans (previously
administered with slip detection y) is the primary reference source and which is the secondary reference
source. Figures 7-70, Synchronization Plan Screen, Stratum 3, and 7-71, Synchronization Plan Screen,½
½
Stratum 4, depict this procedure.½
SYNCHRONIZATION PLANPage 1 of 1
SYNCHRONIZATION SOURCE (DS1 circuit pack location)
Stratum: 3
Port Network: 1½
½
Figure 7-70. Synchronization Plan Screen, Stratum 3½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-134ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
SYNCHRONIZATION PLANPage 1 of 2
SYNCHRONIZATION SOURCE (DS1 circuit pack location)
Stratum: 4
Primary:Secondary:
DS1 CIRCUIT PACKS
Location
Name
slipLocationNameslip½
½
½
½
½
Figure 7-71. Synchronization Plan Screen, Stratum 4½
½
Stratum½The stratum level used for synchronization. Options are:
3 Stratum 3 clock. If this option is used, the remainder of the screen disappears and
the Port Network field appears.½
½
NOTE: A TN780 circuit pack must be used when selecting the stratum 3
clock option.½
½
4 Stratum 4 clock (default)½
Port½When a stratum 3 clock is selected in the Stratum field, this field is used to specify
Network½
which port network (1, 2, or 3) containing a stratum 3 clock will be used as the
synchronization source. This field does not appear when a stratum 4 clock is selected
in the Stratum field.½
½
½
½
Primary
The 3-character location of the circuit pack that is the primary synchronization
reference.
NOTE: The primary will be the DS1 circuit pack administered with slip detection
y. The location, name, and slip (that is, slip detection) fields list the DS1 circuit
packs that have been administered on the 
DS1 CIRCUIT PACK screen. The primary and
secondary source must be selected from this list.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-135
SecondaryThe 3-character location of the circuit pack that is the secondary synchronization
reference. There is no requirement that a secondary source be provided. However, it
is a good practice.
The Command Line Feature set provides four executable commands for controlling and
monitoring synchronization. They are:
l     Disable
l     Enable
l     Status
l     Set
Trunk Group/Trunk Group Members — DS1 Trunk Applications
For DS1/DMI applications the TN722 circuit pack emulates three categories of trunk types, while the
TN767 circuit pack emulates three additional trunk types; refer to table 6-1, Supported Digital Facilities.
DS1/DMI trunking applications are defined by using page 1 and page 2 of the 
TRUNK GROUP screen; this
is the same as for analog trunk groups. Trunk members are added to the 
GROUP MEMBER ASSIGNMENTS
screen (pages 3 through 9). This series of screens administers many of the same parameters as
procedures 100 and 101 do for Generic 2. Figure 7-72, Trunk Group Screen, Page 1 (Tie), depicts this½
½
½
procedure.½
TRUNK GROUPPage 1 of 9
Group Number:
Group Type:
tieSMDR Reports? y
Group Name:OUTSIDE CALLCOR: 1
TAC: _
Direction: two-way
Outgoing Display? n
Dial Access? yBusy Threshold: 99Night Service:
Queue Length: 0
Incoming Destination:
Comm Type: avdAuth Code? n
BCC: 0
TRUNK PARAMETERS
Trunk Type (in/out):
Incoming Rotary Timeout (sec): 5Outgoing Dial Type: toneIncoming Dial Type: toneDisconnect Timing (msec): 500Digit Treatment:Digits:Connected to Toll? nSTT Loss: normal
DTT to DCO Loss: normal
Incoming Dial Tone? y
Bit Rate: 1200
Synchronization: async
Duplex: full
Answer Supervision Timeout? 10
Figure 7-72. Trunk Group Screen, Page 1 (Tie)
Most fields require no unusual entries for DS1 service applications. Only those fields that may require
special attention are mentioned.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-136ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
Comm TypeThe default is voice with avd and data being the alternate selections.
NOTE: Trunk groups that are administered avd require that the DS1 Interface
also be administered for common-channel signaling (24th). Furthermore, if avd
is translated; then the baud rate, synchronization, and duplex fields are displayed.
These three fields enable the trunk group to function with a modem pool. A
Data Originate code is required to start a modem pool call.½
BCCThis field is only displayed when ISDN-PRI is enabled on the SYSTEM PARAMETERS
CUSTOMER-OPTIONS 
screen and when the Communications Type field is administered avd
or data.
Trunk TypeEstablishes the physical type of incoming and outgoing trunks. For tie trunk
(in/out)applications, field encodes and their descriptions are:
l     Auto
l     Immed-start
l     Wink-start
l     Delay-dial
With System 75, the digital loss plan is administered by entering a code with the
Group Name field. With Generic 1, the digital loss plan is administered with the
following three fields.½
½
Connect toThe default is n. Enter y if the trunk group terminates on a Digital Toll Office.
Toll
STT LossThis field is only displayed condition that the Connected to Toll field is translated n.
Allowable entries are the default normal or option low. Refer to chapter 4, The Digital
Loss Plan, for a description of the digital loss plan and for application information.
DTT to
Allowable entries are the default normal or option low. Refer to chapter 4, The Digital
DCO LOSSLoss Plan, for a description of the digital loss plan and for application information.
Figures 7-73, Trunk Group Screen, Page 2 (Tie), an 7-74, Trunk Group Screen, Page 3 (Tie), depict this
procedure.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-137½
TRUNK GROUPPage 2 of 9
ACA Assignment? n
Long Holding Time (hours): 1
Short Holding Time (secs.): 10Short Holding Threshold: 15
MIS Measured? n
Internal Alert? n
Used for DCS? nPBX ID: 1Data Restriction? n
Maintenance Tests? y
Suppress # Outpulsing? n
Figure 7-73. Trunk Group Screen, Page 2 (Tie)½
GROUP MEMBER ASSIGNMENTSPage 3 of 9
Port
NameNightModeTypeAns Delay
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:11:12:
13:
14:15:
Figure 7-74. Trunk Group Screen, Page 3 (Tie)
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-138ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
PortThis field associates each trunk group member to a particular network (1 or 2), carrier
(A-E), slot (01-20), and circuit (01-24). To keep things simple, try to match trunk
group member and DS1 channel assignments (for example, trunk group member 1 on
channel 1
NameTypically, this entry is a 7-digit telephone number. However, another candidate would
be the 10-digit trunk circuit identification number, which is available from the circuit
provider.
NightThis is a new capability with Generic 1 and System 75, R1V3. It permits an individual
trunk member to override the night service option that is administered on page 1
of the 
TRUNK GROUP screen. Allowable entries are an extension, the attendant, or to
leave blank if the Trunk Type field does not begin with auto/...½
ModeFor DS1 tie trunk applications, the default and only permitted entry is e&m.
TypeFor DS1/DMI applications, the default is T1 stan (T1 standard). Normally, this
field is not administered. The default value is appropriate.
Ans Delay
Allowable entries (in milliseconds) range from 20 to 5100 in intervals of 20. This
should only be translated if delay-dial were optioned.
Processor Interface Data Module — ISDN-PRI Applications
Each ISDN-PRI circuit pack maintains the 24th channel as the D-signaling channel. For the switch
processor to communicate with the D-signaling channel an administration link must be established
between the processor and the D-channel. The procedure for establishing this link involves
administering the following three screens:½
l     PROCESSOR INTERFACE DATA MODULE
l     PROCESSOR CHANNEL ASSIGNMENTS
l     INTERFACE LINKS
Figure 7-75, Data Module Screen, depicts this procedure.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-139½
Data
DATA MODULEPage 1 of 1
Data Extension:
Type: procr-infc
Physical Channel:
Name:Cos: 1
COR: 1
Maintenance Extension:
ABBREVIATED DIALING
List 1:
HOT LINE DESTINATION
Abbreviated Dialing Dial Code (from above list) :
_
ASSIGNED MEMBERS (Stations with a data extension button for this data module)
ExtNameExt
Name
1:3:
2:4:
Figure 7-75. Data Module Screen
A unique extension number that identifies the data module. Actually, this is a phantom½
Extension
data module and frequently this extension number is identified as a phantom number.
The extension number can be any reserved number within the Dial Plan Record. (See
also the Physical Channel field description below.)
Type
Enter procr-infc for ISDN-PRI applications.
PhysicalA two digit number which corresponds to the physical channel of the processor
Channelinterface circuit packs (TN765s). If there is one TN765, these numbers range form 01
to 04; if there are two TN765s, these numbers range form 01 to 08.
Name
Completing this field is optional. If you choose to complete this field, enter a unique
link application, such as ISDN-PRI(1) or ISDN-PRI(2).
The ISDN-PRI application does not place any additional restraints or special considerations on the
remaining fields.
Processor Channel Assignments — ISDN-PRI Applications
This screen associates a processor channel to an interface link number. (Processor Interface Data
Module), which was previously defined. Additionally, 1 of the 64 interface channels is identified and
linked, via administration, to identified processor channel. Figure 7-76, Processor Channel Assignment
Screen, depicts this procedure.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-140ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1½
PROCESSOR CHANNEL ASSIGNMENTPage 1 of 4
ProcInterfaceRemote
ChanAppl.Link ChanPriorityProc ChanMachine-ID
1:2:
3:
4:5:6:7:
8:
9:10:11:12:13:14:15:16:
Figure 7-76. Processor Channel Assignment Screen
Proc Chan
This is a display only field. You can select any of the following processor channels
(5-7, 9, 11-58, 60-64); conditional that the identified channel is not already used.
ApplThis field should be administered isdn for ISDN-PRI applications.
Interface
Permitted encodes are 1 through 8. The number selected should match the number
Link
previously administered on the 
PROCESSOR INTERFACE DATA MODULE screen.
Interface
Not used in Generic 1.
Chan½
PriorityServicing the D-Channel is a high priority issue. Therefore, h (for high) should be
administered for all ISDN-PRI applications.½
For ISDN-PRI applications the other fields should remain blank.
Interface Links — ISDN-PRI Applications
This screen identifies the interface link and enables the link. Figure 7-77, Interface Links Screen,
depicts this procedure.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-141½
INTERFACE LINKSPage 1 of 1
LinkEnableEst
ConnPIExtProtDestination
DigitsBrdDTE/
DCEIdentification
1:y2:n3:n4:n5:n
6:n7:n
8:n
yISDN
––
–
–
–
–
–*
Figure 7-77. Interface Links Screen
Link
This is a display only field. The interface link identified and enabled should be the
same number as previously translated in the Physical Channel field of the 
DATA MODULE
screen.
Enable
Est Conn
PI ExtEnter y to enable the link.
Enter y for all ISDN-PRI applications.
This is a display only field. It should display the phantom Data Extension that was
previously administered with the 
DATA MODULE screen.
Prot
Destination
Digits
Destination
Brd
Enter ISDN for all ISDN-PRI applications.
Field disappears when PROT=ISDN
Enter the ISDN-PRI 4-character circuit pack address. The first digit (1 or 2) identifies
the port, the second character (A-E) identifies the carrier, the third and fourth digits
(01-20 or 01-18) identify the circuit pack slot number.
DTE/DCE
IdentificationField disappears when PROT=ISDN
Optional, but typically should include the identifying name of the destination switch.
Trunking Considerations — ISDN-PRI Applications
It is necessary to determine those types of ISDN-PRI network services desired before attempting to build
the ISDN-PRI trunk groups. Some of the more significant considerations should include the following:
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-142ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
NOTE: An ISDN-PRI trunk group is created by translating the Group Type field as isdn-pri.
1.
2.
3.
4.
5.
6.Will the switch provide ISDN-PRI private network access or ISDN-PRI public network
access?
If private network access, you can translate the Service Type field as tie. Depending on the
particular application other service types may also be applicable (such as tandem), in particular
if you want traveling class marks (TCMs).
If public network access, then the identity of the interexchange carrier (IXC) or local exchange
carrier (LEC) must be known. Furthermore, the particular carriers ISDN network
Services/Features (that are to be used) must be known and defined in software translations.½
NOTE: The NETWORK-FACILITIES screen lists (by name and facility coding definition) each
of the currently available AT&T ISDN network Services/Features. These are frequently
called the Predefined Services/Features. If public network access is to an LEC or to an
IXC other than AT&T (or if it is not defined), then that carriers ISDN Services/Features
should be defined in the lower half of the screen.
If public network access, then translate the Service Type field as required (such as cbc).
If the Service Type field is translated cbc, then (as an option):
a.
b.
From 1-to-3 USAGE ALLOCATION PLANS may be defined.
A time-of-day day-of-week ASSIGNMENT SCHEDULE (consisting of up to six
transition times per day) may be defined for each usage allocation plan. Alternately, a
usage allocation plan may be defined as fixed meaning that the selected allocation plan is
always in effect.
For all Service Types, each incoming type of Service/Feature (such as MEGACOM 800 and
SDN) may receive service-specific incoming call handling treatment. Included is the
administration ability to request SID-ANI on a per call basis, to do digit deletion/digit
insertion on a per call basis, or to effect night-service routing based on attributes of the
incoming call.
NOTE: The determination of whether the switch will request SID/ANI (on a CBC basis)
depends on the station called and certain administration data for that station.
Advantages of CBC Trunking
In a non-CBC Service Selection environment, specific DS1 channels must be preassigned and
provisioned for each desired service. To determine the proper number of trunks per service application
requires extensive traffic engineering studies. With such a study, trunk groups can be designed to
accommodate a customer’s peak traffic for given service applications. Furthermore, the time when one
service application encounters peak traffic may not coincide with when another service application
encounters peak traffic. As an alternative, if multiple network services are accommodated with a single
trunk group, and that trunk group is provided with allocation and scheduling controls, then significant
trunking efficiencies are realized by distributing the traffic over the total number of available trunks.
CBC Usage Allocation Plans control the trunk groups so that dedicating a trunk group to an ISDN
application is not needed. However, the administration ability to establish dedicated (or static) trunk
groups still exists. By implementing usage allocation plans, the customer can optimize the CBC trunk
group without involving any of the IXC/LEC network services personnel. The flexibility to control the
CBC trunk is built into Generic 1; changes are transparent to the network provider.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4