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

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-143
Network Facilities — ISDN-PRI Applications
This screen is, from the user perspective, display only. However, the Customer Support Service
Organization (CSSO) may administer (add) new services or features as required. In terms of
comparison, this screen is somewhat equivalent to procedure 279, word 1. Figure 7-78, Network-½
Facilities Screen, depicts this procedure.½
NETWORK-FACILITIES
Predefine Services/Features
Facility
Facility
Name
Type
Coding
Name
TypeCoding
outwats-bnd
100001megacom-800100010operator000101megacom100011sub-operator000110
Inwats100100
sdn100001wats-max-bnd100101
accunet100110lds100111
i800101000multiquest110000
Additional Services/Features
Facility
Facility
Name
TypeCodingName
TypeCoding
—
—
—
—½
½
_
_
_
_
NameFigure 7-78. Network-Facilities Screen
Up to 15 alphanumeric characters that uniquely identify (by name) the Service or
Feature.½
NOTE: The name ACCUNET is used to access both domestic and international
service.½
½
Facility
The ISDN-PRI specification requires that each network capability be identified as
Type
either a feature (0), or service (1).
Facility
The ISDN-PRI specification further requires that each service or feature be identified as
Codinga:
l
l
l
lParameterized Service
Parameterized Feature
Binary Service
Binary Feature*
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-144ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
Trunk Group — ISDN-PRI Trunk Applications
ISDN-PRI trunk groups are defined by using the first page of the 
TRUNK GROUP screen. Since ISDN-PRI
uses Message Oriented Signaling, the format of this screen is somewhat different from the assigned
basic DS1 service.
Page 2 administers certain features that are unique to ISDN-PRI trunk groups. Screen pages 3 and 4 are
only displayed if the Service Type field on page 1 is administered CBC. Screen pages 5 through 11 are½
used as required to assign group members.
Figure 7-79, Trunk Group Screen, Page 1 (ISDN-PRI), depicts this procedure.½
½
TRUNK GROUPPage 1 of 11
Group Number:
Group Type:—isdn-priSMDR Reports? y
Group Name:OUTSIDE CALLCOR: 1TAC:Direction: two-wayOutgoing Display? n
Dial Access: yBusy Threshold: 99Night Service:
Queue Length: 0
Service Type: cbcAuth Code? n
Usage Allot? yFar End Test No:
TRUNK PARAMETERS
Send Display/TCM in codeset 6/7: 6
Max Message Size to Send: 260
Connected to Toll? nSTT Loss: normalDTT to DCO Loss: normal
Bit Rate: 1200Synchronization: asyncDuplex: full
Figure 7-79. Trunk Group Screen, Page 1 (ISDN-PRI)
Only the new ISDN-PRI service application fields or those fields that require special or additional
considerations are mentioned here.
Group TypeFor ISDN-PRI service applications this field should be translated isdn-pri.
NOTE: The 
SYSTEM-PARAMETERS CUSTOMER-OPTION screen must have ISDN-PRI
service enabled before this trunk group type can be translated.
Dial AccessNormally, this field is defined as y. However, for some public network connections
(such as service type CBC, MEGACOM, etc.), this field is defined as n.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-145
Night
Service
Service Type
Usage Allot
Far End
Test No½
½
Send
Display/TCM
in Codeset
6/7
If administered, then the extension number translated will receive all incoming calls
(for the particular trunk group) when the switch is placed in night service mode.
NOTE: Page 2 of the 
TRUNK GROUP screen permits an override entry for each
particular type of ISDN network service. Also, trunk member night service is
allowed.
Assigns the service application for the ISDN-PRI trunk group. Since CBC permits
reduced costs (depending on tariff and application), an improved grade-of-service, and
customer premis control of networking, the option cbc should be considered for public
network applications. Other options include any of the predefined or additional
Services/Features listed in the Name field of the 
NETWORK-FACILITIES screen. Also, the
options access, tie, and tandem are permitted.
Field encodes and their descriptions are:
y Enable usage allocation for those services provided by the trunk group. Used to
maximize customer control of the allocation of CBC trunk group members to
services (such as preventing a service from monopolizing the member of a group).
NOTE: This option permits up to three usage allocation plans to be defined
for the identified trunk group. The term usage allocation is the ability to set
both a minimum and maximum number of trunk members that an ISDN
Service/Feature may use at a given time. Each usage allocation plan can set
limits for up to 10 services/features.
n Disable usage allocation for the trunk group (default). This option places
restrictions on either the Services/Features that can be carried on the trunk group or
the number of calls that any one Service/Feature can have at any given time.
This is the ISDN-PRI test line associated with the far-end’s test equipment and is
reserved exclusively for maintenance testing. The test number should be assigned for
both private and public networks. There is one test number per trunk group. As a part
of the installation and ISDN-PRI service provisioning process, the test number must be
coordinated with the terminating switch.
NOTE: This field is equivalent to translating procedure 108, word 1, for
Generic 2.
This field maps the display information (codepoint 8) and the TCM information
(codepoint 40) to codeset 6 or codeset 7, depending on whether a 6 or a 7 is translated.
The distant switch will determine which should be translated. Specifically, if the
distant switch is a 4ESS with 4e11 or 4e12 software, or a System 85 R2V4, then this
field should be translated with a 7. If the distant switch is a 4ESS with 4e13,
Generic 1, or Generic 2, then the field should be translated with a six.
NOTE: For tandem node configurations, Generic 1 rebuilds the message in
conformance to the outgoing trunk group. If any codeset/codepoint conversions
are required, then the two endpoints must coordinate the conversions. Generic 1
can receive in either codeset (this is a send option).½
½
½
½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-146ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
MaxThis field determines the maximum number of bytes that may be transmitted before an
Message Sizeacknowledge reply is required. Permitted entries are 128, 244, 256, and 260 (default).
to SendThis field must be administered to be the maximum size messages that the far end is
able to receive and process. If the distant switch is another Generic 1, then any entry
will work. Currently, System 85 R2V4, Generic 2, all releases of 4ESS, and 5ESS only
support 128.½
The fields on page 2 of the TRUNK GROUP screen comprise an incoming call handling table. The table
consists of up to 12 rows of seven columns per row. The first three columns constitute a key that
together select which row or unique treatment should apply for an incoming call on the group. The
remaining four columns specify the treatment to be provided for a call that matches the key.
The first column or field in the key is the Service/Feature field. If an incoming call is for a service
listed in a row in the incoming call handling table, then that row may specify the treatment for the call,
depending on the other two columns of the key. The Called Len field is used to continue the row
determination. If the number of digits received with the incoming call match the number of digits in the
Called Len field for calls to the matched service, then this row may apply. If no other row also contains
a matching service and called length, then this row does apply. If another row does exist with the same
service and number length, then the Called Number field will be used to continue the row determination.
If the leading digits received with the incoming call match the digits specified in the Called Number
field, then this row applies to the call. Therefore, with this table, a unique treatment can be given to any
incoming call, even if these calls are to the same service or have the same length of digits. The
remaining four fields specify the unique treatment for the call once the row has been determined.
Together, the Del and Insert fields can be used to manipulate the incoming number that will be used to
route the call. The Per Call SID/ANI field can be used to request SID/ANI only for specific calls
incoming on the group. The Night Serv field is used to have calls of different types routed to different
night destinations when night service is in effect.
The biggest application of this table is when a Generic 1 is connected to the public network with several
different services, such as MEGACOM® 800 service and ACCUNET® Switched Digital Services, but it
also has applications when used in a private network.½
NOTE: Administering this table is optional.
Figure 7-80, Trunk Features Screen, Page 2 (ISDN-PRI), depicts this procedure.½
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-147½
TRUNK FEATURESPage 2 of 11
ACA Assignment? nLong Holding Time (hours): 1
Short Holding Time (secs.): 10Short Holding Threshold: 15
MIS Measured? nInternal Alert? n
Used For DCS? nPBX ID: 1Data Restriction? n
Maintenance Tests? ySend SID? n
Send Name? n
Service/CalledCalledDelInsertPer CallNightFeatureLenNumberSID/ANIServ
Figure 7-80. Trunk Group Screen, Page 2 (ISDN-PRI)
Only the new ISDN-PRI service application fields or those fields that require special or additional
considerations are mentioned here.
Send SID½
This field determines whether the Station Identification (SID) number is sent to the
network for both incoming and/or outgoing ISDN calls. For outgoing calls, the user’s
calling party number is sent. For incoming calls, the number associated with the
answering party is sent. Field encodes and their descriptions are:
y Send the SID.
NOTE: If SID is enabled, then the 
SID PREFIX TABLE screen must be completed.
n Do not send the SID (default).
NOTE: Both SID and ANI significantly enhance the AT&T ISDN network
capabilities. The customer can subscribe to the SID/ANI service and have a
representation of the calling party number forwarded from the AT&T network
to the terminating switch. Therefore, consider provisioning and enabling the
SID/ANI option as part of the installation/administration process.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-148ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
Send NameThis field determines whether the calling (originating) party’s administered name is
sent to the network for outgoing calls and whether the connected (answering) party’s
name is sent to the network for incoming calls. Field encodes and their descriptions
are:
y Enable this capability. You can enable this field; however, there may be cases
where it is desirable to disable this option (for example, security, privacy, and
personal preference).
n Disable this capability (default).
NOTE: Administering the Send Name field is equivalent to administrating
procedure 012, words 1 and 2, with the exception that Generic 1 cannot be
administered to transmit the trunk group name.½
Typically, those trunk groups that are administered for cbc service type will receive a variety of
incoming call types. These incoming calls may originate from a variety of sources (for example, public
network, private network, or host computer).
The incoming call handling software processes incoming calls based on:
l     The number of digits received
l     The type of digits
l     Whether the call has an identifying NSF (for example, MEGACOM 800, SDN, or ACCUNET)
Service/Feature Permitted entries include any of the predefine or additional Services/Feature listed on
the 
NETWORK FACILITIES screen and supported by this trunk group. Also, the special
identifier, other, may be translated (as a catch-all entry) for all Services/Features not
explicitly specified.
The Service/Feature field is the first item searched. Following a match in the
Service/Feature field, then the associated entry for the Called Len field is searched, and
if a match is found then the Called Number field is searched. Failure to match the
associated Called Len or Called Number will cause the search to continue to the next
Service/Feature entry. (For a list of predefined Service/Features that can be received,
see the Service Type field description.)
Called Len
Specifies the expected number of digits to be contained in the called-party number IE.
Field encodes and their descriptions are:
l     A number within the range (0 to 16) — the number of digits received must match
the number that is administered in this field.
If the IXC is AT&T and if the ISDN network service is MEGACOM 800, SDN, or
a switched digital service, then a 4ESS may deliver from 0 to 7 digits. Therefore,
if the service is correctly provisioned, then the proper number (and required
number) of digits will be delivered to the switch.½
l     No entry, leave the field blank. This will suffice for the case where the number of
digits received is not significant.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-149
CalledGenerally, this field only specifies some of the leading digits that are contained in the
Numbercalled-party number IE. The digits received must match, on a digit-per-digit basis,
what is administered in this field. Field encodes and their descriptions are:
l     A series of numbers, which may consist of from 1 to 16 digits, corresponding to
the required leading digits.
NOTE: If this field is administered then the associated Called Len field must
also be administered.
l     No entry, leave the field blank. This will suffice for the case where the digits
received are not significant.
DelThe digit Del and digit Insert fields (together) provide the ability to do digit
manipulation/digit replacement on incoming calls. It is the manipulated number that is
used to route the call.
The Del field specifies the number of leading digits to be deleted from the Called Party
Number IE. Once the specified number of digits have been deleted, the digits specified
in the Insert field are prepended to the front of the Called Party Number. Field
encodes and their descriptions are:
l     A series of numbers, which may consists of from 1 to 16 digits, corresponding to
the leading digits that are to be deleted. This administration option may be used to
solve many of the problems relating to cross dial plan mapping.
Application Example #1
If the called-party number IE contains a 4 digit number (that uniquely identifies an
extension or hunt group) but does not align with the required address because the
switch has a 5 digit dial plan. Then, the appropriate leading digit may be inserted
so that the call will route correctly.
Application Example #2
If the called-party number IE contains the digits [8123] or [8567] but it is desired
to route these calls to hunt groups with extensions [44123] and [44567]
respectively. Then, the screen would have an entry for each number, and the Del
fields would contain a one and the Insert fields would contain the digits 44.
NOTE: The number of digits deleted cannot be greater than the number
specified in the Called Len field.
l     No entry, leave the field blank. When no digits are to be deleted.
l     The word all. This option may be used to route particular types of calls to a
specific extension number. This specific extension number would be administered
in the Insert field.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-150ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
InsertThe digits inserted before the Called Party Number IE. This specifies the digits
prepended to the front of the remaining digits after any (optional) digit deletion has
been performed. The resultant number formed from digit deletion/insertion is used to
route the call, providing that night service is not in effect. Field encodes and their
descriptions are:
l     A series of numbers, which may consists of from 1 to 16 digits.
l    No entry, leave the field blank. This will suffice for the case where no digits are to
be inserted.
Per Call
Specifies if and how to request SID or ANI for this particular type of Service/Feature.
SID/ANIField encodes and their descriptions are:
l
l
l
l
l
lNo entry, leave the field blank (default). Specifies that the switch will not request
either SID or ANI for any of these types of calls after call delivery. Use no
entry when the network is provisioned to always send SID/ANI with call setup.
ANI-only
ANI-pref — but will accept SID
SID-only
SID-pref — but will accept ANI
None — same as blank
Night Serv
Permits the administration of a particular night service extension for each row in the
table. This entry will override the night service administered for the whole trunk
group (on page 1 of the 
TRUNK GROUP screen). Field encodes and their descriptions are:
l    An extension number
l    The attendant
l    No entry, leave the field blank (default). This will not override night service for
the whole trunk group.
The 
TRUNK FEATURES screen (Page 2 of 11) may have more than one entry for the same Service/Feature.
Frequently, multiple entries (per Service/Feature) are used to provide multiple call routes for that
Service/Feature. The route selected will be dependent on the received digits and specific administration
details of the digit manipulation fields. If an incoming call matches more than one entry, then the most
restrictive entry is selected. (This is why it is not CBC specific.)
The following case examples show this point and should clarify how the incoming call handling
software functions in this scenario.
Case 1
l     Service/Feature field is specified (for example, mega800).
l     Called Len field is specified with a requirement of N digits (for example, N = 5).
l     Called Number field is specified with M leading digits, where M is a number of digits less than N
(for example, the three digits 855).
ADDENDUM 1 (December 1990) to 55S-025-101, Issue 4 
						

							ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 17-151
NOTE: The screen that follows these case examples depicts a line entry (Service/Feature, Called
Len, Called Number,...) for each case. The first (top) entry is for case 1, the second entry from the
top is for case 2,...the last entry shown is for case 7.
Case 2
l     Service/Feature field is specified (for example, mega800).
l     Called Len field is specified with a requirement of N digits (for example, N = 5).
l     Called Number field is specified with M leading digits, where M is a number of digits less than N
(for example, the single digit 8).
Application for Case 1 being selected — most restrictive
Assume the switch receives a MEGACOM 800 call that has a called-party number IE with 85542.
Based on the Service/Feature and Called Len fields alone, this call will match both case 1 and case 2.
However, on analyzing the called-party number, the incoming call handling software will select Case 1
since it is the more restrictive match. Each incoming call is searched against every screen entry to
identify the appropriate match.
Application for Case 2 being selected
Assume the switch receives a MEGACOM 800 call that has a called-party number IE with the digits
84000. Based on the Service/Feature and Called Len fields alone, this call will match both Case 1 and
case 2. However, on analyzing the called-party number, it is determined that the leading digits (84000)
do not match the digits for Case 1 but do match for Case 2.
Case 3
l     Service/Feature field is specified (for example, mega800).
l     Called Len field is specified (for example, 4).
l     Called Number field is not specified (that is, left blank).
Application for Case 3 being selected
A MEGACOM 800 call is received that has a called-party number IE with the digits 8654. Based on
the Service/Feature field alone, this call matches Cases 1-3. However, on analyzing the Called Party
Number IE, there are only 4 leading digits (8654). Cases 1 and 2 are eliminated since they require a
Called Len of 5 digits (Case 3 requires 4 digits). Furthermore, the Case 3 Called Number field is blank,
which matches any number regardless of digit format. The incoming call handling software selects Case
3 since it matches and is more restrictive than Cases 4-7.
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4 
						

							7-152ADMINISTRATION OPTIONS AND REQUIREMENTS — SYSTEM 75 R1V5 & GENERIC 1
Case 4
l     Service/Feature field is specified (for example, mega800).
l     Called Len field is not specified (that is, left blank).
l     Called Number field is not specified (that is, left blank).
Application for Case 4 being selected
Assume the switch receives a MEGACOM 800 call that has a called-party number IE with the digits
75442. Based on the Service/Feature field alone, this call will match Case 1, 2, 3, and 4. However, on
analyzing the Called Party Number IE, it is determined that there are the following 5 leading digits
(75442). Case 3 does not match because it requires 4 digits. Case 1 and 2 both require 5 digits, but
specify an 8 as the leading digit and therefore do not match. For Case 4, the Called Len and Called
Number fields are blank, which matches any number regardless of the number of digits or digit format.
Case 5
l     Service/Feature field is specified as other.
l     Called Len field is specified with a requirement of N digits (for example, N = 5).
l     Called Number field is specified with M leading digits, where M is a number of digits less than N
(for example, the three digits 855).
Case 6
l     Service/Feature field is specified as other.
l     Called Len field is specified with a requirement of N digits (for example, N = 5).
l     Called Number field is specified with M leading digits, where M is a number of digits less than N
(for example, the single digit 8).
Case 7
l     Service/Feature field is specified (for example, other)
l     Called Len field is specified (for example, N)
l     Called Number field is not specified (that is, left blank)
Case 8
l     Service/Feature field is specified (for example, other)
l     Called Len field is not specified (that is, left blank).
ADDENDUM 1 (December 1990) to 555-025-101, Issue 4