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

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-153
Cases 5-8 are similar to Cases 1 through 4 respectively. The only difference is that the Service/Feature
field is changed to other. The remaining fields repeat the same conditions on a case-by-case basis.
Therefore, cases 5-8 may serve to receive other incoming Services/Features (for example, SDN or any of
the Switched Digital Services).
Example Screen Entries for Cases 1-8
l     Called Number field is not specified (that is, left blank).
NOTE: Case 8 is the least restrictive (nonrestrictive) and will match all calls not handled by
any other case.
Applications for Cases 5-8
Figure 7-81, Trunk Group Screen, Page 2 (ISDN-PRI) for Cases 1-8, depicts this example.½
½
TRUNK FEATURESPage 2 of 11
ACA Assignment? n
Long Holding Time (hours): 1
Short Holding Time (secs.): 10
Short Holding Threshold: 15
MIS Measured? nInternal Alert? n
Used For DCS? n
PBX ID: 1Data Restriction? n
Maintenance Tests? y
Send SID? n
Send Name? n
Service/CalledCalledDel
InsertPer CallNightFeatureLenNumberSID/ANIServmega8005855mega80058
mega8004mega800
otherNMotherNM
otherNblankotherblablank
Figure 7-81. Trunk Group Screen, Page 2 (ISDN-PRI) for Cases 1-8
Trunk Group Usage Allocation — ISDN-PW Applications
If the trunk group Service Type field is administered cbc, then up to 10 Service/Feature specific digit
treatments can be administered for each usage allocation plan, refer to the 
CBC TRUNK GROUP USAGE
ALLOCATION 
screen (Page 3 of 11).
NOTE: Although each usage allocation plan may contain up to 10 entries, a given Service/Feature
may only be listed once per plan:
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-154ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
Many other scenarios may be developed for applying a plan. Various reasons may be used. Figure 7-
82, Trunk Group Screen, Page 3 (ISDN-PRI), depicts this procedure.½
½
CBC TRUNK GROUP USAGE ALLOCATIONPage 3 of 11
Usage Allocation Plan 1Usage Allocation Plan 2
UsageAllocation Plan 3
Service/Feature Min# Max#Service/Feature Min# Max# Service/Feature Min# Max#
Chan ChanChan ChanChan Chan
Figure 7-82. Trunk Group Screen, Page 3 (ISDN-PRI)
Before administering the Usage Allocation Plans it is first necessary to define a
strategy for each plan. For example; plan 1 could specify those actions to be taken
during a normal business day, plan 2 could specify those actions to be taken during
non working hours of the business day (during lunch and when phones are not
attended), while plan 3 could specify those actions to be taken during the weekend.
An alternate example could just use plans 1 and 2 on a scheduled basis, but have plan
3 defined and available for fixed allocation. Obviously, many other strategies could be
defined.
Usage
Allocation
Plan
Service/Feature
Permitted entries include any of the predefined or additional Service/Features listed on
the 
NETWORK FACILITIES screen that this trunk group supports. Also, the special identifier
other may be translated (as a catch-all entry) for all Services/Features not explicitly
specified.
Min# Chan
This field reserves a specified number of trunk group members that are to always be
available to the associated Service/Feature. Permitted numbers are any number within
the range of 0 to 99.
NOTE: For each allocation plan, the sum of the Min# Chan columns must be
less than the total number of members for the trunk group. To maximize the
utility of CBC Service Selection, the sum of the Min# Chan column must be much
less than the total number of members for the trunk group. The difference
between this sum and the total numbers of members determines the overflow pool.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-155
Max# ChanThis field established the maximum number of trunk members that can be used by the
associated Service/Feature application at any one time (for example, MEGACOM 800).
An Example Application for Usage Allocation Plans
A given ISDN-PRI trunk group has the Service Type field translated cbc and has 23 trunk members.
And if:
1.
1.
2.At any given time, no more than 15 members (that is, Max# Chan = 15) will be used for the
particular Service/Feature.
2.At least 5 members (that is, Min# Chan = 5) will always be reserved for this service application.
Then, these Min Chan and Max Chan administration assignments insure the following:
At least 8 trunk members will be available for other types of calls. Other types of calls may be a
combination of both incoming and outgoing.
Regardless of the maximum bound assigned to other services, there will always be at least 5
members that can carry calls for the associated Service/Feature (for example, MEGACOM 800).
NOTE: This type of allocation plan has the characteristic of insuring that no single service
will dominate the trunk group, while still allowing for periodic fluctuations in demand. If a
particular Service/Feature attempts a call that would result in exceeding the specified
threshold, then that call is rejected.
Usage Allocation Plan Assignment Schedule — ISDN-PRI Applications
The 
CBC USAGE ALLOCATION PLAN ASSIGNMENT SCHEDULE screen permits the customer to administer a usage
allocation plan and to vary the plan by both time of day and day of week. Figure 7-83, Trunk Group
Screen, Page 4 (ISDN-PRI), depicts this procedure.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-156ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1½
CBC TRUNK GROUP USAGE ALLOCATION PLAN ASSIGNMENT SCHEDULEPage 4 of 11
Usage Method:
Fixed? yAllocation Plan Number: 1
Scheduled? n
Usage Allocation Plan Activation Schedule:
ActPlan ActPlan ActPlan ActPlan ActPlan ActPlanTime #Time #Time #
Time #Time #Time #
SunMonTueWedThuFri
Sat
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ ____ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ ____ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ ____ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ ____ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ ____ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
___ : ___ _
Fixed
Allocation
Plan
Number
ScheduledFigure 7-83. Trunk Group Screen, Page 4 (ISDN-PRI)
This method allows the customer to specify a single usage allocation plan to be used
for all time. Field encodes and their descriptions are:
y Enable this method. The plan that is administered in the Allocation Plan Number
field will be enabled.
n Disable this method. Consequently, the scheduled method must be enabled for this
CBC application.
Specifies the plan number (1, 2, or 3) that is to be enabled when fixed usage is
selected.
This method allows the customer to specify that scheduled usage allocation is desired.
Field encodes and their descriptions are:
y Enable this method.
NOTE: The time of day (account time or plan number) day of week entries
must have been administered before this field is enabled. The customer can
override or suspend the specified usage allocation schedule by changing or
enabling the fixed method.
n Disable this option.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							Plan #
ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-157
Act TimeSpecifies the time that the associated usage allocation plan will become effective.
Time must be specified in 24-hr format. Permitted entries are 00:00 through 23:59.
NOTE: Each day of the week must have at least one entry, but may have as
many as six transition times. A transition time is defined as the time when
another plan becomes effective. A new or different plan will not effect existing
calls, but will effect new call attempts.
Specifies the plan number effective from the activation time to the activation time of
the next Act Time. Field encodes and their descriptions are:
1 Plan number 1
2 Plan number 2
3 Plan number 3
Trunk Group Member Assignments — ISDN-PRI Trunk Applications
Adding members to an ISDN-PRI trunk group is similar to adding members to a DS1 trunk group. The
prime difference is that with ISDN-PRI the 
TRUNK GROUP screen does not have the right three fields
(Mode, Type, and Ans Delay). Figure 7-84, Trunk Group Screen, Page 5 (ISDN-PRI), depicts this½
procedure.½
GROUP MEMBER ASSIGNMENTSPage 5 of 11
PortNameNightSig Grp½
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.1B1501
1B1523
1B1601
1B1623
1B1701
1B1709
1B1716
1B1724
1B1801
1B1823
1B1901
1B19231
1
1
1
1
_
_
_
2
2
3
3
_
_
_
_½
½
½
½
½
½
½
½
½
½
½
½
½
½
½
½
Figure 7-84. Trunk Group Screen, Page 5 (ISDN-PRI)
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-158ADMINISTRATION 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 assignments with B-channel assignments (for example, trunk group
member 1 on channel 1).
Typically, this entry is a 7-digit telephone number. However, another candidate would
be the 10-digit trunk circuit identification number (available from the circuit provider).
This is a new capability with Generic 1. 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.
Sig Grp
This field associates a signaling group to a trunk group member. If a DS1 is assigned
to only one signaling group, then this number appears in the Sig Grp column. This
value cannot be changed (that is, a trunk cannot be moved from one signaling group to
another) from this screen. To change a signaling group assignment, use the 
SIGNALING
GROUP 
screen.
If a DS1 is assigned to more than one signaling group, no number appears in the Sig
Grp column. You must manually assign one of these preassigned signaling groups
(from 1-8) to this field.½
Name
Night½
½
½
½
½
½
½
½
½
SID Prefix Table — ISDN-PRI Applications
If the Trunk Group field Send SID is enabled (page 2 of the 
TRUNK FEATURES screen), then the screen SID
PREFIX TABLE must be administered. Figure 7-85, SID Prefix Table Screen, depicts this procedure.½
½
SID PREFIX TABLE
Page 1 of 5
ExtExtSIDExtExtSIDExtExtSID
LenCodePrefixLenCodePrefixLenCodePrefix
Figure 7-85. SID Prefix Table Screen
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-159
Permitted entries are single digit numbers less than or equal to the number
administered in the Page Length field of the 
DIAL PLAN RECORD screen. For example, if
the Page Length field is translated five (meaning a five digit numbering plan), then this
field may contain the number 1, 2, 3, 4, or 5. If the Page Length field is translated
four (meaning a four digit numbering plan), then this field may contain the number 1,
2, 3, or 4.
NOTE: For most applications it is expected that this field will be translated with
the same number as the Page Length field.
Ext Code
Specifies a single explicit extension number, or a range of extension numbers.
Permitted entries are any valid extension number, or range of extension numbers that
are defined on the 
DIAL PLAN RECORD screen.
For example, assume that the Ext Len is five and that the Ext Code is administered
with the digits 65. Then, the range of extension numbers is 65000 through 65999.
SID PrefixThe number that is prefixed to the extension number to form a 10-digit Station
Identification. The SID prefix can be a 5, 6, 7, 8, 9, or 10-digit number, or blank. A
typical 6-digit SID prefix would be the switch 3-digit NPA and the 3-digit NNX (that
is, NPANNX). If the number of digits in the SID prefix plus the extension length
exceed ten, then excess leading digits from the extension number are deleted when
forming the 10-digit SID number. If the SID prefix is a 10-digit number, then the
extension number is not used.
An Example Application that uses SID
Assume that the switch has a 5-digit dial plan. For illustration purposes, assume that a company has its
billing department (extensions 31000 through 31999) and sales department (extensions 41000 through
41999) located on the same switch. Furthermore, assume that the billing department does not want their
individual extension numbers displayed on the far-end but rather wants the company’s LDN (for
example, 201-235-3000) displayed. On the other hand, the sales department does want their individual
calling party’s number displayed rather than the companys LDN. Figure 7-86, SID Prefix Table Screen,
Sample Application, depicts the appropriate translations to achieve these objectives.½
NOTE: If the SID Prefix field is blank, then neither the calling party name or calling party
extension number is displayed.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-160ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1½
SID PREFIX TABLEPage 1 of 5
ExtLen55
ExtCode31
41
SIDPrefix
2012353000
20123Ext
Len
ExtCodeSIDPrefixExt
LenExt
CodeSIDPrefix
Figure 7-86. SID Prefix Table Screen, Sample Application
Routing Patterns — ISDN-PRI Applications
NOTE: The 
ROUTING PATTERN screen only relates to outgoing calls; page 2 of the TRUNK GROUP screen
only relates to incoming calls.
A routing pattern is a set of trunk groups that carry calls to a particular switch. Each routing pattern is
identified by a unique number known as the pattern number. A maximum of 254 different patterns may
be administered. Each pattern may contain up to six different trunk groups (six alternate trunk routes).
Once a routing pattern is accessed the call processing software will, depending on trunk group
compatibility (both FRL and BCC) and trunk member availability, select the trunk groups in decreasing
order of preference (that is, 1, 2,...6).
NOTE: Both ISDN-PRI private networks and ISDN-PRI public networks require that one or more
ROUTE-PATTERN screens be administered. For private networks, the RNX tables must be translated.
Each RNX table serves as a pointer to one or more pattern numbers. For public networks, the
appropriate HNPA, FNPA, and/or RHNPA tables must be translated. These tables serve as a pointer
to one or more different pattern numbers.
Figure 7-87, Routing Patterns Screen, depicts this procedure.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-161½
ROUTING PATTERNSPage 1 of 1
Pattern Number:
—
Pattern Assignments (Enter Up To 6)
Grp.FRL NPAPrefixToll     No. DelInsertedIXCNo.MarkListDigitsDigits1._2._3._4._5._6._
BCC ValueService/Feature
01234
1._____Band:2._____Band:3._____Band:4.Band:_____5._____Band:6._____Band:
Figure 7-87. Routing Patterns Screen
PatternPermitted entries are numbers within the range 1 through 254. The appropriate number
FRL
NPA Numbermust come from the RNX/HNPA/FNPA/RHNPA tables.
Grp No.Permitted entries are numbers within the range 1 through 99. The appropriate number
must come from the previously administered 
TRUNK GROUP screen.
NOTE: There is no restriction on using the same trunk group number in more
than one routing pattern.
Permitted entries are numbers within the range 0 through 7 (where 0 is least restrictive
and 7 is most restrictive).
NOTE: ISDN-PRI does not alter the usage of FRLs. However, to access an
ISDN-PRI trunk group, the calling extension must be compatible, both in terms of
FRL and BCC.
Permitted entries are the NPA (area code) for the terminating switch.
NOTE: This field is not used for AAR or tie trunk applications, although it may
still be translated.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-162ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
Prefix Mark
This field is only used for public network (ARS) applications.
The Prefix Mark relates to the ARS Prefix 1 Required? field on the 
DIAL PLAN RECORD
screen. If the ARS Prefix 1 Required? field is translated y, then (for certain type of
calls) it may be necessary to transmit the one along with the dialed digits. The Prefix
Mark field permits four different entries (numbers) for administering this capability.
Field encodes and their descriptions are:
0 Specifies that the prefix digit one is not inserted.
NOTE: This entry is appropriate when there are no Interchangeable CO
Codes within the NPA. If the destination number is seven digits or less (for
example, NNX-XXXX or a service code N11) then the digits are sent as
dialed. Furthermore, for these type calls, if the prefix digit one is dialed it is
not deleted. For 10-digit (NPA-NNX-XXXX) calls, if the prefix one is dialed
it is deleted.
1 Specifies that the prefix digit one is sent if and only if the call is a 10-digit calls.
For this entry, there may be Interchangeable CO Codes within the NPA.
2 Specifies that the prefix digit one is sent for all 7- and 10-digit toll calls. The
associated toll list assigns which office codes are toll calls. For this entry, there
may not be Interchangeable CO Codes within the NPA. With this entry, if the
customer were to dial a one before a nontoll 7-digit call, the call would route as a
toll call.
3 Specifies that the prefix digit one is sent for all toll calls, regardless of the number
of digits. For this entry, there may be Interchangeable CO Codes within the NPA.
Toll List
This field is only used for public network (ARS) applications.
This field relates a specific ARS toll table to Prefix Marks two and three. Permitted
entries are numbers 1 through 32.
No. Del
Determines the number of digits deleted from the beginning of the digit string that is
Digits
being prepared for sending. Permitted entries are numbers within the range of 0
through 11.
NOTE: The insertion or deletion of the NPA is done with the Prefix Mark and
the NPA is not included in the number of digits deleted or inserted.
Inserted
Specifies the digits to be inserted at the beginning of the digit string that is being
Digits
prepared for sending.
IXC½For ISDN-PRI private networks, enter a blank. For ISDN-PRI public networks the
interexchange carriers three digit identification should be translated. If this field is left
blank for public network connections, then the presubscribed common carrier is
assumed.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4