Ss 7 DB
Ss 7 DB
Issue/date Purpose
Edition 01 P04, October 2007 Initial issue for Alcatel-Lucent 5070 SSG release 826-04.10.
This document is classified as ECCN 5E991 and is subject to US Export Administration Regulations, 15
CFR Parts 730 through 799 and the Canadian Export and Import Permits Act, and may be subject to
similar laws and regulations (collectively referred to as "Export Regulations"). As a condition to
allowing the use of this document, the recipient agrees not to export, re-export, use, distribute,
transfer, transmit, or otherwise release this document in contravention of applicable Export
Regulations.
If requested by Alcatel-Lucent, recipient shall sign written assurances and other export-related
documents as may be required for Alcatel-Lucent to comply with Export Regulations.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All
other trademarks are the property of their respective owners.
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Overview of sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SS7 network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SS7 network overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Communications paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Network hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Database overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Databases and forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Database dependencies and capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 1. Order of input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Network administration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Self-identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Logical networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5070 SSG identity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Local node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Node parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Signaling point restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Link sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Link set function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Link set procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Point code mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
MOPC with super link set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Special link set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Routing procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Destination point code route sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Introduction
Purpose
This document provides SS7 database provisioning procedures for the Alcatel-Lucent 5070
Signaling Server Global (5070 SSG). This document is for personnel who provision the SS7
database.
Scope
This document covers the MMI commands to provision the SS7 database.
The commands in this document are for use with the MMI Terminal option. This option is
available on the System Manager Desktop (the primary window of the 5070 SSG) and is
associated with the Launcher Tree tab. This option enables you to enter MMI commands with a
command line interface.
Overview of sections
This document contains the following sections:
The Introduction section introduces the document and provides an overview of the sections in
the document.
The SS7 network section describes the SS7 network in general terms and shows how the
components of the network operate together.
The Database overview section describes the database and shows the order for creating and
deleting database elements.
The Self-identity section describes how to define the 5070 SSG as a local node, define the local
node and LNP alias, change node parameters, define the logical networks, and enable SP
restart.
The Link sets section describes how to define link sets. This section also describes multiple
originating point code with super link set, special link sets, and point code mapping.
The Processors and links section describes how to add physical processors to the system to
support both LSLs and HSLs. In addition, this section describes how to define these links and
the related parameters.
The SS7-IP interworking section describes the steps to provision IP links, M2PA, and M3UA
functionality.
The Route set master section describes how to create a route set master and add link sets to
it.
The Routing section lists MTP routing types and describes how to define DPCs to be used for
routing.
The SCCP subsystem section describes the SCCP software, which performs signaling functions
for specialized routing and management services.
The GTT for SCCP section describes how to define a subsystem name and manage the SCCP
subsystem database.
The SCCP applications section describes how to set up mated applications for a duplicated
subsystem.
The Concerned signaling points section describes concerned signaling point groups and
concerned signaling points.
The Gateway screening section describes how to create and manage gateway screening
parameters.
Appendix. Database engineering forms contains the database engineering forms required to
configure the 5070 SSG database.
Appendix. SCCP and MTP timers describes how to configure MTP and SCCP timers for special
purposes and testing.
SS7 network
• Signal point
• Logical network
• Point codes
• MOPC with super link set
Signal point
A signaling network consists of nodes interconnected by signaling links. All nodes that
originate, route, or receive messages using the SS7 protocol are called SPs. An SS7 network
contains three types of SPs:
Logical network
A logical network is an internal distinction of networks having the same or different
characteristics. Each logical network contains the full range of signaling point codes, thus
allowing signaling point codes to overlap into any number of logical networks. Routing inside a
logical network is possible on the MTP or SCCP level.
Point codes
A unique signaling point code identifies each node in the network. Messages originate at an
origination node and are sent to a destination node. For message routing, the originating node
is identified by its point code, called the OPC. The destination node is identified by its point
code, called the DPC. The routing label for the message contains the OPC and the DPC.
The point code mapping feature supports network expansion and traffic redistribution to both
end office and tandem switches by introducing a new switch into the network without
requiring changes at the offices connected to the expanded office. Point code mapping
changes the DPC or OPC of call-processing messages and sends the changed messages to a
different switch.
The DPC of the messages received in the 5070 SSG from the distant end node to the old point
code is replaced with the new point code and sent to the new point code as per the point code
mapping table. The OPC of the messages received from the new point code to the distant end
node is replaced with the old point code and sent to the distant end node as per the point code
mapping table.
Synthetic routing
The synthetic routing feature enhances the point code mapping feature and provides a phased
approach for switch consolidation. The 5070 SSG can either replace the DPC or retain the
original DPC. If the DPC is replaced, then the point code mapping feature is in effect. If the
DPC is not replaced, then the synthetic routing feature is in effect. When synthetic routing is
in effect, the DPC message remains intact.
The DPC of the messages received in the 5070 SSG from the distant end node to the old point
code is not replaced with the new point code and sent to the new point code as per the point
code mapping table. The OPC of the messages received from the new point code to distant end
node is not replaced with the old point code and sent to the distant end node as per the point
code mapping table.
A normal link set assigned with an MOPC is called an MOPC link set. An MOPC link set maintains
a unique adjacent point code and so it is not a part of a super link set.
A super link set is a collection of 2 of 16 link sets with the same adjacent node that is treated
as a single link set.
A master link set is a link set in a super link set whose MOPC is unassigned.
A non-master link set is any link set in a super link set that is not the master link set.
A member link set is a link set that is either a master or a non-master link set.
A uniform parameter is any link set parameter that must be identical between two link sets.
The following are the uniform parameters:
• Preventive TFP
• SS7 accounting parameters
– Remuneration flag
– Remuneration origination operator ID flag
– Remuneration SI indicator
– Remuneration SI bit map
– Remuneration verification flag
– Remuneration verification origination operator ID flag
– Remuneration verification SI indicator
– Remuneration verification SI bit map
Communications paths
The following topics provide information about communication paths:
• Links
• Link sets
• Signaling link code
• Combined link sets
• Signaling link selection code
• Traffic distribution recommendations
• Route sets
• Ordered route sets
Links
A signaling link is a transmission facility that connects two nodes. In the 5070 SSG, link
interface processors perform these signaling link functions.
Links are associated with call routing and link processors in the link interface. The 5070 SSG
supports both odd-numbered and even-numbered links.
The 5070 SSG supports channelized E1/T1 simplex/duplex processors. Both CEDLK and CTDLK
processors support 32 channels across all four spans and support both 56 kb/s and 64 kb/s.
Link sets
The links that directly connect two nodes are grouped into one or more link sets. A link set can
contain as many as 16 signaling links.
An originating node should use combined link sets to equally distribute traffic between two
SSGs that are going to the same DPC.
In a 16-link link set, each SLS code contains exactly the same links so there is no difference
how each link is connected to the inbound processor. In a super link set that contains more
than 16 links, each SLS segment can use different links so there is a difference how inbound
processors are assigned to each link set or how originating nodes are connected to each
inbound processor.
Following are the recommendations for the link set to routing processor assignment. All
processor IDs of the routing processors are consecutive:
• The first link set of each originating node should be sequentially assigned to the routing
processor on a node group basis and the first assigned routing processor should use SLS
prefix zero.
The link sets after the first link set should be assigned in the same manner as assigned for
the first link set.
• If there is a limited number of routing processors, the second link set in each node group
should be assigned with the routing processor that uses the first segment in the next
segment cycle.
• If the node group has some traffic from the nodes in its own node group and some of the
traffic from the previous node group, then the first routing processor to be assigned should
start from the next routing processor that had not been assigned in the previous node
group.
• Each paired link sets should be assigned to the routing processors that has the same SLS
prefix.
• The links in the same link set should be assigned to the routing processors that has the
same SLS prefix.
• If a segment cycle is incomplete at the end of the array, then any segment that has the
equivalent SLS prefix can be used to make the segment cycle complete.
Route sets
One or more link sets that carry message traffic to a destination are called a route set. The
5070 SSG can send messages to a distant node over a direct link set that originates at the 5070
SSG and terminates at the distant node, or it can send messages by way of an intermediate
node. In a mated 5070 SSG pair, the mate 5070 SSG can forward messages to a node when the
direct link set cannot be used; therefore, the link set to the mate 5070 SSG is included in the
route set.
Network hierarchy
The following topics describe the network hierarchy:
Several 5070 SSG pairs can be interconnected at the same level to form a backbone 5070 SSG
network. These 5070 SSG pairs are called primary pairs. When a network handles a heavy
traffic load, a primary 5070 SSG pair can also be connected to a secondary 5070 SSG pair to
form a multilevel network. The secondary 5070 SSG pair is always homed to a particular
primary 5070 SSG pair. A primary 5070 SSG pair can support multiple secondary 5070 SSG pairs.
An SCP can also be replicated within a network; that is, the network can include two SCPs at
different locations with identical databases. Transactions can then be load-shared between
the two SCPs.
Alias addresses
A group of related nodes, such as a 5070 SSG or SCP pair, can be identified by a single point
code, called an alias. The alias address is used by nodes sending messages to the related nodes
over combined link sets. The nodes are assigned the alias point code in addition to their
individual point codes.
Link types
The links that interconnect network nodes are identified by the letters A-F, which indicate the
relationship of the nodes being connected. The following list defines the link types used in a
national signaling network.
Applications
• User functions
• Subsystems
• Global titles
• Global title translation
• Gateway screening
User functions
The primary function of the 5070 SSG is to route messages accurately to their destinations. In
certain cases, the destination of the message is not defined by point code alone. Certain
network services require additional processing to route the message (for example, 800 service
and calling card service).
Subsystems
The network provides its users with additional message processing in the form of application
software, called subsystems, residing in SSPs and SCPs. Each subsystem is assigned a number.
A node that requires data for a user function sends a message to the appropriate subsystem.
The message includes the point code of the node where the subsystem resides and the
subsystem number. The subsystem performs the function and returns the data to the node that
requested it.
Global titles
Messages can also indirectly identify network destinations. A message that indirectly identifies
its destination does not contain a point code and subsystem number in its message routing
label. Instead, it contains a global title. The global title has the following parameters:
• Point code
• Subsystem number
The SCCP software portion of the 5070 SSG performs GTT functions. The following list shows
the system responsible for, and the GTT process used, to complete an 800-service call.
Gateway screening
The gateway screening feature provides the 5070 SSG capabilities to screen incoming MTP and
SCCP message traffic received on link sets designated as gateway link sets. This feature
provides protection against unauthorized traffic or traffic sent in error to a network.
Database overview
Data tables organize this information into data elements and their parameters.
This document includes samples of generic database forms and explains the rules and
guidelines for completing each form. Appendix. Database engineering forms contains all
regular database provisioning forms. Copy and complete the forms to create or change
database elements.
Figure 1 shows the order of input for database elements. To delete database elements, start at
the appropriate point in the chart and work up. The following blocks are the starting points for
deletion:
• CCS cluster
• SCCP concerned signaling point
• SCCP mated applications
• Global translation
LOGNET parameters
CCS parameters
Point code
Link sets mapping/synthetic
routing
MPC
Processor
Link span
Processors and links
CCS link
The 5070 SSG stores the database as data tables. The 5070 SSG maintains two or more images
of each table in the SS7 database:
Data tables are downloaded to processor memory during IPL. Data tables are built and updated
by database editor commands. Each command operates on a set of tables to change, delete, or
display data elements. When a command executes, the system updates the affected data
tables. Data tables are identified by five- or six-character names assigned to the disk files
containing the tables.
Note: Back up the SS7 database after making any changes to the routing and GTT tables.
The system accesses the following data tables to perform database changes:
Self-identity
• Logical networks
• 5070 SSG identity
• Local node
• Alias
• Node parameters
• Signaling point restart
Logical networks
The logical network overcomes the limitation of the maximum number of networks imposed by
the network indicator field of the MTP protocol. The logical network concept allows for
multiple, logically separated networks to exist within the same network indicator. Routing
inside a logical network is possible on the MTP or SCCP level. Routing between different logical
networks requires use of SCCP GTT functionality. The logical network is uniquely determined
by the link set on which the message arrives. The 5070 SSG has self-identity in each logical
network that is configured.
Constraints
Data tables
The following data tables are changed when logical network parameters are assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN CCS LOGNET
2 Prompt: LN*NAME=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
3 Prompt: NI*INDICATOR=
Enter: (one of the following choices)
0 or 1 (international network indicator); go to Step 11.
2 or 3 (national network indicator); continue.
This entry defines the network indicator.
The default value is none.
4 Prompt: PROT*CLASS=
Enter: [A, ANSI, I, ITU, C, or CHINA]
This entry defines the protocol class.
If you enter A or ANSI, the system shows the logical network parameters; go to Step 13.
If you enter C or CHINA, go to Step 6; otherwise, continue.
5 Prompt: PC*FORMAT=
Enter: point code format
The point code valid range [1-255]-[0-255]-[0-255].
The default value is none.
The system shows the parameters associated with the local node.
6 Prompt: SPARE*BITS=
Enter: (one of the following choices)
0-3 (full range); go to Step 7.
0, 1, 2, 3 (single value); go to Step 9.
The system shows the logical network parameters.
This entry defines the spare bits.
7 Prompt: CONG*PROCDR=
Enter: [A or B]
A (congestion with priority)
B (congestion with level); go to Step 10.
This entry defines the congestion procedures.
The default value is congestion with level.
8 Prompt: RCT*SUPPORT=
Enter: [YES, NO, Y, or N]
This entry defines the RCT support.
9 Prompt: CONG*ASP=
Enter: [YES, NO, Y, or N]
The entry defines congestion applied to application servers.
The default value is YES.
10 Prompt: TFR*SUPPORT=
Enter: [YES, NO, Y, or N]
This entry defines the TFR support.
The system shows the logical network parameters.
11 Prompt: SND*TFPINV=
Enter: [YES, NO, Y, or N]
This entry defines the send TFP for invalid point codes.
The default value is NO.
12 Prompt: ROT*SLS=
Enter: [YES, NO, Y, or N]
This entry defines the rotate SLS for outgoing messages.
13 Prompt: DEST*LN=
Enter: destination logical network
This entry defines the destination logical network.
The default value is NO.
The system shows the logical network parameters.
Constraints
Data tables
The following data tables are changed when logical network parameters are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE CCS LOGNET
2 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
3 Prompt: NLN*NAME=
Enter: new logical network name
The default value is the old logical network name.
4 Prompt: NI*INDICATOR=
Enter: (one of the following name)
0 or 1 (international network indicator); go to Step 6.
2 or 3 (national network indicator); continue.
This entry defines the network indicator.
The default value is the old network indicator value.
5 Prompt: PROT*CLASS=
Enter: [A, ANSI, I, ITU, C, or CHINA]
This entry defines the protocol class.
If you enter A or ANSI, go to Step 13.
If you enter C or CHINA, go to Step 7; otherwise, continue.
The default is the old protocol class value.
6 Prompt: PC*FORMAT=
Enter: point code format
The point code valid range is [1-255]-[0-255]-[0-255].
The default value is none.
The system shows the parameters associated with the local node.
If you entered 0 or 1 in Step 4, go to Step 11; otherwise, continue.
The default value is old point code format.
7 Prompt: SPARE*BITS=
Enter: (one of the following choices)
0-3 (full-range); go to Step 8.
0,1, 2, 3 (single value); go to Step 10.
The system shows the logical network parameters.
This entry defines the spare bits.
8 Prompt: CONG*PROCDR=
Enter: [A or B]
A (congestion with priority)
B (congestion with level); go to Step 10.
This entry defines the congestion procedures.
The default is the old congestion procedures value.
9 Prompt: RCT*SUPPORT=
Enter: [YES, NO, Y, or N]
This entry defines the RCT support.
The default is the old RCT support value.
10 Prompt: TFR*SUPPORT=
Enter: [YES, NO, Y, or N]
This entry defines the TFR support.
11 Prompt: SND*TFPINV=
Enter: [YES, NO, Y, or N]
This entry defines the send TFP for invalid point codes
The default value if NO.
12 Prompt: ROT*SLS=
Enter: [YES, NO, Y, or N]
This entry defines the rotate SLS for outgoing messages.
The default value is NO.
13 Prompt: SCR*LS=
Enter: screening link set name or number
Note: To disable the logical network screening, enter 0. However, the screening link
set name or number must be already assigned so you can change it here.
14 Prompt: DEST*LN=
Enter: logical network
This entry defines the destination logical network.
The system shows the changed logical network parameters.
Constraint
• The logical network cannot be deleted if any node belonging to this logical network exists
in the MTP destination table (Y52).
• The logical network cannot be deleted if a subsystem already exists for the logical
network.
Data tables
The following data tables are changed when logical network parameters are deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE CCS LOGNET
2 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS LOGNET
2 Prompt: DLOG*NET=
Enter: logical network name, number, or ALL
The default value is none.
The following changes can be made to the local node after its self-identity is established:
Local node
A node is any SP that handles SS7 message traffic. The 5070 SSG is called the local node.
Distant nodes are linked to the local node.
This subsection describes procedures for configuring the local node. The route set master
procedures identify distant nodes and the route sets from the local node to the distant nodes.
The local node procedures define the characteristics and capabilities of the local node. The
local node has a node name and a point code. The local node may also have one or more alias
point codes.
Constraints
• The 5070 SSG must have a different node name in each network. In single ID mode, assign
only one node name. In multiple ID mode, assign the same node name to the multiple
point codes defining the 5070 SSG.
• This procedure defines the primary point code.
• The database is limited to 4096 point codes.
Data tables
The following MTP data tables are changed when a new network is added to the SS7 database:
• Network (Y33)
• MTP destination (Y52)
• Node name (Y55)
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: In this procedure, only the primary point codes may be defined.
1 Prompt: >
Enter: ASSIGN CCS NODE
2 Prompt: ANO*DE=
Enter: new node name
The node name can be 1-11 characters.
The node name must start with an alphabetic character with the remaining characters
A-Z or 0-9.
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters associated with the local node.
Constraints
The following constraints apply to changing the local node and the point code:
• Assigning a new name to the point code for the node changes the node name.
• Point codes are changed in different ways depending on the purpose:
– Change the point code to correct a database error: assign a different point code to
the node name.
– Change the point code to alter routing: delete the current node and add a new node
with the same name and a different point code.
• Change the point code only to correct the database, not to assign a new location to the
local node.
• If the primary point code is changed, the new primary point code is written to the
database entry marked as the self-identity.
Data tables
The following data tables are changed when node parameters are changed:
• Network (Y33)
• MTP link set (Y45)
• MTP destination (Y52)
• Node name (Y55)
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: See Display the local node in this section to show the parameters of the local
node name before making a change.
1 Prompt: >
Enter: CHANGE CCS NODE
2 Prompt: NODE=
Enter: (one of the following choices)
A node name; go to Step 5.
<RETURN>; continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: CPNODE=
Enter: A new node name
<RETURN> (current name)
6 Prompt: CPNT*COD=
Enter: new point code
Constraints
Data tables
The system retrieves local node parameters from these data tables:
• Network (Y33)
• Node name (Y55)
• Alias point code (W67)
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS NODE
2 Prompt: DNODE=
Enter: (one of the following choices)
A node name; go to Step 5.
ALL; go to Step 5.
<RETURN>; continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
4 Prompt: PNT*COD=
Enter: point code string
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the local node parameters.
Alias
An alias is a point code that identifies a group of related nodes. The alias allows other nodes to
address the related nodes as a unit. Messages are sent over combined link sets from the
originating node to the destination nodes. The alias is assigned to the related nodes as well as
to their individual point codes.
To add an alias for the 5070 SSG, assign an alias address to be used by distant nodes with
combined link sets to the two 5070 SSG systems. The procedure consists of assigning up to 32
point codes and alias node names to the 5070 SSG.
For the local node, an alias point code supports full broadcast for TFA or TCA messages about
the alias when the resources to support the processor are limited or not available.
The same alias point codes are assigned to the local 5070 SSG and the mate 5070 SSG. Distant
nodes use the alias to route messages to the 5070 SSG pair.
When the signaling network (level 3) software receives a message, it compares the destination
address with both the primary point code and alias point code assigned to the 5070 SSG. If the
addresses match, the message is handled by the 5070 SSG.
Note: The alias network numbers cannot differ from the primary (local) node.
• Assign an alias
• Change an alias
• Delete an alias
• Display an alias
Assign an alias
Use this procedure to assign multiple alias node names and alias point codes for the local node.
The system provisions the alias point codes in the alias point code table (W67).
Constraints
The following constraints apply to adding an alias for the local node:
• The alias node name must be different than the name assigned to the 5070 SSG when the
network configuration is defined.
• If the node name does not exist in the database, the MMI prompts for a new alias point
code.
• If the alias point code does not exist, this procedure adds the new alias node name and
point code to the database.
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN CCS ALIAS
2 Prompt: ALNO*DE=
Enter: alias node name
The alias node name can be 1-11 characters.
The alias node name must start with an alphabetic character with the remaining
characters A-Z or 0-9.
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the alias and local node parameters.
5 Prompt: DSS*AL=
Enter: [Y or N]
Y (designate as DSS alias)
N (do not designate as DSS alias - default)
The system shows the alias and local node parameters.
Change an alias
Use this procedure to change an alias node name and alias point code assigned to the local
node.
Constraints
• The alias node name must be different from the name assigned to the 5070 SSG when the
network configuration was established.
• The alias point code should not be changed while the system is handling live traffic.
• If the alias node name or the point code exists in the database as an alias self-identity, the
system prompts for a new alias node name.
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS ALIAS
2 Prompt: OALNO*DE=
Enter: (one of the following choices)
An alias node name; go to Step 5. The system shows currently assigned local
node information.
<RETURN>; continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the alias and local node parameters.
5 Prompt: CALNO*DE=
Enter: (one of the following choices)
A new alias node name
<RETURN> (current value)
6 Prompt: CPNT*COD=
Enter: point code
7 Prompt: CDSS*AL=
Enter: [Y or N]
Y (designate as DSS alias)
N (do not designate as DSS alias)
<RETURN> (current value)
Delete an alias
Use this procedure to delete the alias node names and alias point codes assigned to the local
node.
Constraints
Notify distant nodes using the alias address before the alias is deleted. Delete the alias from
the local 5070 SSG database.
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE CCS ALIAS
2 Prompt: OALNO*DE=
Enter: (one of the following choices)
An alias node name; go to Step 5. The system shows currently assigned local
node information.
<RETURN>; continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
Display an alias
Use this procedure to show alias node names and alias point codes assigned to the local node.
The system also shows the local primary node name and primary point code.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS ALIAS
2 Prompt: DLOG*NET=
Enter: logical network name, number, or ALL
Node parameters
The node parameters commands control the following data:
Constraints
If the local node is assigned before the node role, use the ASSIGN CCS NODE command to assign
the node role to the 5070 SSG.
Data tables
The system accesses the local node configuration data table (Y33) when the node role or the
number of dynamic status records is changed.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS PARAME
2 Prompt: SYSTEM*PAR=
Enter: [S or L]
S (system parameter - default)
L (logical network paramter)
If you enter L, go to Step 4; otherwise, continue.
3 Prompt: NODER*OLE=
Enter: (one of the following choices)
1 (STP or SSP with transfer)
2 (SSP without transfer)
3 (SCP without transfer)
4 (SCP with transfer)
<RETURN>, (current value)
Enter 1; the entry selects 5070 SSG with transfer capability. Go to Step 9.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: OFF*NDIS=
Enter: (one of the following choices)
E or ENABLE (enable the auto hourly off-normal status reporting feature)
D or DISABLE (disable the auto hourly off-normal status reporting feature)
<RETURN> (current value)
6 Prompt: HOP*COUNT=
Enter: (one of the following choices)
0-255 (hop counter for SCCP routing)
<RETURN> (current value)
7 Prompt: P*COMP=
Enter: (one of the following choices)
FULL or F (full response to all P_COMP requests)
TRUN or T (truncated response to all P_COMP requests)
CURR or C (full response to the P_COMP request for the current period only.
Truncated response to all previous P_COMP requests)
8 Prompt: NO_SERVICE_IMPACT_LINK_REMOVAL=
Enter: (one of the following choices)
E or ENABLE (enable service impact link removal feature)
D or DISABLE (disable service impact link removal feature)
<RETURN> (current value)
Go to Step 10.
9 Prompt: MTP_READY_WAIT_FOR_FLEXIBLE_ROUTING_DOWNLOAD=
Enter: (one of the following choices)
E or ENABLE (enable the processor to wait for flexible routing data to
complete download prior to setting the processor ready to route)
D or DISABLE (disable the processor to wait for flexible routing data
download)
<RETURN> (current value)
Constraints
Data tables
The system accesses the local node configuration data table (Y33) to show this information.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS PARAME
2 Prompt: LOG*NET=
Enter: logical network name or number
• Restart a node that has no available signaling links (resulting from a link failure, processor
outage, or management inhibition)
• Bring up a sufficient number of links for operation
• Update the routing tables for the node before signaling traffic resumes
Constraints
Data tables
The signaling point restart table (W62) is accessed when SPR parameters are changed.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS SPR
2 Prompt: LOG*NET=
Enter: logical network name or number
3 Prompt: SPR*FLG=
Enter: (one of the following choices)
E (enable the MRSP on the local node)
D (disable the MRSP on the local node)
<RETURN> (current value)
4 Prompt: IPR*FLG=
Enter: (one of the following choices)
E (enable DPC activated IPRs on the CCM restore after a duplex CCM failure)
D (disable DPC activated IPRs on the CCM restore after a duplex CCM failure)
<RETURN> (current value)
5 Prompt: BRDCST*FLG=
Enter: (one of the following choices)
E (enable full broadcast of TFA or TCA messages on the CCM restoral after the
duplex CCM failure)
D (disable full broadcast of TFA or TCA messages on the CCM restoral after
the duplex CCM failure)
<RETURN> (current value)
The system shows the enable and disable flags.
Data tables
The signaling point restart table (W62) is accessed when SPR parameters are changed.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS SPR
Verify that the SPR parameters are correct.
END PROCEDURE
Link sets
The following topics provide information about the link set related procedures:
The Processors and links section describes links and link parameters.
You can perform the following procedures to manage link sets and links:
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
2 Equip a call routing and link processor for each link to be assigned to the link set.
3 Remove the call routing and link processors that support the links in the link set from
service.
4 Restore the call routing and link processors that support the links in the link set to
service.
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
2 Remove the route set master from the ordered route. This task is required only if the
link set to be deleted is the last link set in the route.
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: You do not have to remove the call routing and link processor to delete a link
from a link set.
4 Remove the call routing and link processor card from the slot.
Link sets to a pair of mated nodes (such as another 5070 SSG pair) are usually grouped into
combined link sets. Combined link sets contain links that terminate at both the mated nodes.
The combined link sets can be used with the alias feature to send messages to either node.
Link sets are defined on the link set form. The link set form defines the link sets that terminate
at each adjacent node and contains information about link availability and network
management messages. A super link set may consist of 2 to 16 link sets.
Constraints
• Do not activate the link sets in a combined link set until both link sets are defined.
• All link sets originate at the 5070 SSG. Do not enter the local node name of the 5070 SSG
as the link set destination. A link set that terminates at the 5070 SSG cannot be defined.
• The adjacent node must be unique for each link set in a given logical network.
• Combined link sets must be assigned the same link set type.
• While a combined link set is assigned, the SLS value assigned to each link in the combined
link set should be unique.
• Only one C-type link set can be defined per logical network.
Data tables
When a new link set is added to the database, these data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN CCS LINKSE
2 Prompt: LSNAME=
Enter: link set name
Enter a link set name of 1-8 alphanumeric characters. The first character in the link set
name must be alphabetic.
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
4 Prompt: ADJN*ODE=
Enter: (one of the following choices)
The name or point code for the adjacent node; go to Step 5.
<RETURN>; continue.
Note: The prompt in Step 5 is displayed if the adjacent node name does not exist in the
node name table.
5 Prompt: ADDN*ODE=
Enter: [Y or N]
Y (add the node)
N (bypass adding the node)
6 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
Note: If the TFR*SUPPORT and SND*TFPINV parameters for the logical network are
assigned the value N or No, then the prompt in Step 7 is not displayed.
7 Prompt: SEND*PTFP=
Enter: [YES, NO, Y, or N]
Note: The system deactivates the second link set in a combined link set when the assign
command is confirmed.
8 Prompt: COMBINE=
Enter: the name or number of the link set
Press <RETURN> (current value)
9 Prompt: LSTYPE=
Enter: (a link set type)
A (access link)
B (bridge link)
C (cross link)
D (diagonal link)
E (extended link)
F (connects two SPs)
<RETURN> (current value)
10 Prompt: TFP*BROAD=
Enter: [Y or N]
Y (send TFP messages on the link set)
N (eliminate TFP messages)
<RETURN> (current value)
11 Prompt: LSPRIOR=
Enter: [1-16]
Enter the link set restoration priority. There is no default value.
12 Prompt: SPR*ENA=
Enter: [Y or N]
Y (enable the adjacent node restart support flag - default)
N (disable the adjacent node restart support flag)
<RETURN> (current value)
13 Prompt: REQ*ACT=
Enter: [YES, NO, Y, or N]
Y (activates the link set)
N (leave the link set in the deactivated state)
<RETURN> (current value)
The system shows the parameters.
Note: If you enter Y in Step 10, then the following caution message is displayed.
Constraints
• To combine two link sets, the 5- to 8-bit SLS conversion values must be the same.
• Do not activate the link sets in a combined link set until both link sets are defined.
Data tables
When parameters associated with an existing link set are changed, these data tables are
changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS LINKSE
2 Prompt: LINKS*ET=
Enter: link set name or number
Enter a link set name of 1-8 alphanumeric characters.
The system shows the links and other values associated with the link set.
3 Prompt: NLSN*AME=
Enter: new link set name
Enter a new link set name of 1-8 alphanumeric characters.
Press <RETURN> (current value).
4 Prompt: ADJN*ODE=
Enter: adjacent node name
<RETURN>; continue.
Note: The prompt in Step 5 is displayed if the adjacent node name does not exist in the
node name table.
5 Prompt: ADDN*ODE=
Enter: [Y or N]
Y (add the node)
N (bypass adding the node)
6 Prompt: CPNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
7 Prompt: SENT*PTFP=
Enter: [Y or N]
Y (send preventive TFP)
N (do not send preventive TFP)
Note: The system deactivates the second link set in a combined link set when the assign
command is confirmed.
8 Prompt: COMB*INED=
Enter: (one of the following choices)
(A combined link set name or number)
D (to delete the combination)
<RETURN> (current value)
9 Prompt: LSTYPE=
Enter: (a link set type from one of the following choices)
A (access link)
B (bridge link)
C (cross link)
D (diagonal link)
E (extended link)
F (connects two SPs)
<RETURN> (current value)
10 Prompt: MINLINK=
Enter: [1-16]
Enter the minimum number of active links. Press <RETURN> (current value).
11 Prompt: SLS*CONV=
Enter: [Y or N]
Y (apply 5- to 8-bit conversion on an outgoing link set)
N (bypass conversion)
<RETURN> (current value)
12 Prompt: TFP*BROAD=
Enter: [Y or N]
Y (send TFP messages on the link set)
N (bypass sending TFP messages)
<RETURN> (current value)
13 Prompt: LSPRIOR=
Enter: [1-16]
Enter the link set restoration priority. Press <RETURN> (current value).
14 Prompt: CSPR*ENA=
Enter: [Y or N]
Y (enable the signaling point restart flag - default)
N (disable the signaling point restart flag)
<RETURN> (current value)
This entry defines the signaling point restart supports for the adjacent end node.
15 Prompt: REQ*ACT=
Enter: [YES, NO, Y, or N]
Y (activate the requested link set)
N (leave the link set in the deactivated state)
<RETURN> (current value)
The system shows the parameters.
Note: If you enter Y in Step 7, then the following caution message is displayed.
Identify the link set to be deleted by link set name. To verify the identity of the link set before
deleting it, use the DISPLA CCS LINKSE command to show the link set.
Constraints
Deleting a link set disassociates the links from the link set. Links are still defined in the
database until they are deleted. The correct procedure for deleting a link set is the following:
Data tables
When an existing link set is deleted, these data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: Delete the point code associated with the link set before performing this
procedure. Use the Delete PCMAP procedure to delete the point code associated with
the link set.
1 Prompt: >
Enter: DELETE CCS LINKSE
2 Prompt: LINKS*ET=
Enter: link set name or number
Enter the link set name of 1-8 alphanumeric characters to be deleted.
The system shows the parameters.
Constraints
The SLS-to-link mapping assignments for a combined link set is displayed only if the link set is
provisioned as a combined link set.
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS LINKSE
2 Prompt: LSDISP=
Enter: (one of the following choices)
A link set name or number; go to Step 4.
ALL; continue.
3 Prompt: DIS*ORD=
Enter: [L or R]
L (show all link sets in ascending link set order - default)
R (show the link sets in restoration priority order)
<RETURN> (current value)
4 Prompt: FORM*AT=
Enter: [B or D]
B (show the brief format without link data)
D (show the detailed format with link data)
<RETURN> (current value)
The system shows the parameters.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ACTIVA CCS LINKSE
2 Prompt: LINK*SET=
Enter: link set name or number
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DEACTI CCS LINKSE
2 Prompt: LINK*SET=
Enter: link set name or number
Enter a link set name of 1-8 alphanumeric characters.
The following message appears when the link set is deactivated:
DISK ENTRY AND PROCESSOR(S) UPDATED
PCMAP is based on the contents of the SS7 point code mapping table (S80). This table contains
parameters that allow the call processing message point codes of one switch (both DPC and
OPC) to be mapped to a second switch's point code. The PCMAP feature supports movement of
trunk groups from one switch to another, while keeping the movement hidden from one of the
switches.
• Intercepts outgoing messages and maps them to the correct secondary destination
• Changes the DPC or OPC of call processing messages and forwards them to another switch
• Display PCMAP
• Assign PCMAP
• Change PCMAP
• Delete PCMAP
Display PCMAP
Use this procedure to show a single PCMAP entry, a range of entries, or all the entries from the
PCMAP entry table.
Constraints
Data tables
The PCMAP entries are in the SS7 point code mapping table (S80).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS PCMAP
2 Prompt: ENTNO*RNG=
Enter: (one of the following choices)
A single entry number
A range of entry numbers
ALL
The system shows the data for the entry number or numbers.
Assign PCMAP
Use this procedure to assign entries in the database for PCMAP.
Constraints
Data tables
The PCMAP entries are assigned to the point code mapping table (S80).
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN CCS PCMAP
2 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
3 Prompt: REP*DPC=
Enter: [Y or N]
If you enter Y in Step 3, the point code mapping function is performed; otherwise,
synthetic routing function is performed. The default value is No.
4 Prompt: OLDPNT*COD=
Enter: old point code
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: NEWPNT*COD=
Enter: new point code
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: DENPNT*COD=
Enter: destination point code
7 Prompt: LOW*CIC=
Enter: [0-16383]
Enter the low circuit identification code. The default is the current value.
Note: The HIGH*CIC value should be greater than the LOW*CIC value.
8 Prompt: HIGH*CIC=
Enter: [0-16383]
Enter the high circuit identification code. The default is the current value.
The system shows the entry number assigned.
Change PCMAP
Use this procedure to change a PCMAP entry.
Constraints
Data tables
The PCMAP entries to be changed are retrieved from the point code mapping table (S80).
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS PCMAP
2 Prompt: ENT*NO=
Enter: entry number
3 Prompt: NLOG*NET=
Enter: logical network name or number
The default value is none.
4 Prompt: CREP*DPC=
Enter: [Y or N]
If you enter Y in Step 4, the point code mapping function is performed; otherwise,
synthetic routing function is performed. The default retains current value.
5 Prompt: COLDPNT*COD=
Enter: change old point code
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: CNEWPNT*COD=
Enter: new point code
The point code valid range depends on the point code format that is configured for the
lognet.
7 Prompt: CDESPNT*COD=
Enter: destination point code
8 Prompt: CLOW*CIC=
Enter: [0-16383]
Enter the low circuit identification code. The default is the current value.
Note: The HIGH*CIC value should be greater than the LOW*CIC value.
9 Prompt: CHIGH*CIC=
Enter: [0-16383]
Enter the high circuit identification code. The default is the current value.
Delete PCMAP
Use this procedure to delete a PCMAP entry from the database.
Constraints
Data tables
The system deletes the PCMAP entry from the point code mapping table (S80).
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE CCS PCMAP
2 Prompt: ENT*NO=
Enter: single entry number
The system shows the entry number.
In a 5070 SSG, the multiple link sets to a single end node are called a super link set. A super
link set may consist of 2 to 16 link sets. Each link set in the super link set has the same
adjacent point code. The sets differ in their link ID numbers and their MOPC values.
A maximum of eight different multiple point codes are allowed on an MPC 5070 SSG.
MOPC retrieves data from the MTP link set table (Y45).
• Combines several 5070 SSG systems into one 5070 SSG with multiple addresses
• Combines the routing and global title functions into one 5070 SSG
These functions are transparent to the adjacent end nodes in the network.
• There is no CHANGE CCS MPCFEA MMI to enable the MOPC feature; it is always enabled.
• Use ASSIGN CCS MPCPAR to assign an MOPC.
• Use CHANGE CCS MPCPAR to delete the assigned normal MOPC to a link set.
• Use CHANGE CCS MPCPAR with H option in the OPC prompt to modify MOPC link set to
normal link set.
• Use DELETE CCS LINKSE or DELETE CCS MPCPAR MMI to delete the MOPC link set.
• Assign MPCPAR
• Change MPCPAR
• Display MPCPAR
• Delete MPCPAR
• Display super link set
• Audit MPC database
Assign MPCPAR
Use this procedure to assign an adjacent and/or originating point code for a specified link set,
thereby creating either an MOPC link set or a super link set.
Constraints
• A link set with the same adjacent point code should exist without any assigned MOPC.
• The link set should be an A type link set.
• There should be no duplication of the MOPC in the super link set. (For future use.)
• The MOPC that is same as another node in the network cannot be assigned.
Note: When a link set is created, the uniform parameters and the non-uniform parameters
should be automatically propagated from its master link set.
Data tables
The MOPC entries are in the MTP link set table (Y45).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN CCS MPCPAR
2 Prompt: LINKS*ET=
Enter: link set name or number
Enter a link set name of 1-8 alphanumeric characters.
If you enter an existing link set name or number, go to Step 4; otherwise, continue.
3 Prompt: ADJN*ODE=
Enter: adjacent node name
Enter adjacent node name of 1-11 characters.
4 Prompt: OPC*PROMPT=
Enter: originating point code
The system shows the values assigned to each field associated with the link set.
Change MPCPAR
Use this procedure to change the MOPC of a link set.
Constraints
• The MOPC should be an existing MOPC, or the MOPC to be created should not exceed the
maximum number of MOPC allowed.
• An MOPC cannot be defined as a destination point code.
• The adjacent point code to an unassigned value cannot be changed.
• A non-master link set cannot be changed to a normal link set if the adjacent point code of
the resultant normal link set is in a member super link set or in another normal link set.
(For future use.)
• If the link set is a non-master link set, the MOPC should not be in any other non-master
link set of the super link set.
• The MOPC that is same as another node in the network cannot be changed.
Data tables
The MOPC entries are in the MTP link set table (Y45).
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS MPCPAR
2 Prompt: LINKS*ET=
Enter: link set name or number
Enter a link set name of 1-8 alphanumeric characters.
The system shows the originating point code values associated with the link set.
3 Prompt: ADJN*ODE=
Enter: adjacent node name
Enter adjacent node name of 1-11 characters.
4 Prompt: COPC*PROMPT=
Enter: originating point code
The system shows the changed originating point code values associated with the link
set.
Display MPCPAR
Use this procedure to show the MOPCs associated with a link set in the MOPC data table.
Constraints
Data tables
The MOPC entries are in the MTP link set table (Y45).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS MPCPAR
2 Prompt: LS*CAT=
Enter: [S, M, or ALL]
S (Super link set); go to Step 3.
M (MOPC link set); go to Step 4.
ALL
3 Prompt: SUPERLS*NUM=
Enter: super link set number or ALL
The system displays the parameters for the category. Go to Step 5.
4 Prompt: LSDISP=
Enter: link set name, number or ALL
Enter a link set name of 1-8 alphanumeric characters.
The system displays the parameters for the category.
Delete MPCPAR
Use this procedure to delete a non-master link set or an MOPC link set.
Constraints
Data tables
The MOPC entries are in the MTP link set table (Y45).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE CCS MPCPAR
2 Prompt: LINKS*ET=
Enter: link set name or number
The system shows the parameters and the following message:
WARNING: ALL ASSIGNED LINKS MUST FIRST BE REMOVED FROM THE LINK
SET
Constraints
Data tables
The MOPC entries are in the MTP link set table (Y45).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS SUPERL
2 Prompt: SUPERLSNUM=
Enter: super link set number
ALL to display all super link sets
The default value is none.
3 Prompt: FORM*AT
Enter: [B or D]
B (display link set data without assigned links - default)
D (display lint set data with any assigned links)
Constraints
Data tables
The system displays the audit processing messages during audit execution and an execution
summary at the end of the audit. The audit is performed on the information from the link set
table (Y45).
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: AUDIT CCS MPC
The attributes are link set name, link set type, logical network, VOPC, and request link set
activation status.
Constraints
Data tables
The system receives the parameters showing the link data table (Y45).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN CCS SLKS
2 Prompt: LSNAME=
Enter: link set name
3 Prompt: LSTYPE=
Enter: link set type C
4 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
5 Prompt: VOPC*PROMPT=
Enter: originating point code
6 Prompt: REQ*ACT=
Enter: [YES, NO, Y, or N]
YES or Y (activate a link set request)
NO or N (do not activate a link set request)
Displays the status of the assigned link set.
Constraints
Data tables
The system receives the parameters showing the link data table (Y45).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE CCS SLKS
2 Prompt: LINKS*ET=
Enter: link set name or number
Displays the status of the current link set.
3 Prompt: NLSN*AME=
Enter: new link set name
4 Prompt: MINLINK=
Enter: minimum number of available links to consider route not restricted
5 Prompt: REQ*ACT=
Enter: [YES, NO, Y, or N]
YES or N (activate a link set request)
NO or N (do not activate link set request); go to Step 2.
Constraints
Data tables
The system receives the parameters showing the link data table (Y45)
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE CCS SLKS
2 Prompt: LINKS*ET=
Enter: link set name or number
Constraints
Data tables
The system receives the parameters showing the link data table (Y45).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY CCS SLKS
2 Prompt: LSDISP=
Enter: link set name or number
3 Prompt: FORM*AT=
Enter: [B or D]
B (shows the brief format without special link set data)
D (shows the detailed format with special link set data)
• Signaling links
• Processor provisioning
• Link span
• Links
• Low-speed E1 link parameters
• HSL parameters
• ATM over E1 high-speed links
For information on provisioning of IP links, M2PA, and M3UA, see the SS7-IP interworking
section.
Signaling links
Signaling links are the only elements in the SS7 database directly supported by a hardware
device. The system defines links in two places:
• In the SS7 configuration database - Links are equipped and assigned to a link set and a call
routing and link processor.
• In the hardware configuration database - Links are identified by the location of the call
routing and link processor that supports the link.
Add link
To add a new link, be sure that there is a call routing and link processor to support the link. If
necessary, install a processor card in the next available slot in the frame before starting these
procedures.
When the link is assigned to a link set, it can be tested. The link test verifies that the link
transmits and receives data without errors.
Processors
This topic describes processor provisioning and is aimed at provisioning these processors that
support a link.
• AE1LK
• CEDLK
• CELK
• CTDLK
• HELK
• IPLK (described in the SS7-IP interworking section)
• IPUA (described in the SS7-IP interworking section)
In addition, the system uses these additional processors for various operations:
• Admin
• CCM
• DSS
• TMM
• TNC-x
Processors can be added to handle the signaling load expected from the signaling links. After
the hardware is installed, a processor must be equipped in the database before it can execute
software functions.
The DSS processor hosts all flexible routing service handlers. The TMM processor controls
administration functions when the LNP application is installed.
Processor provisioning
This topic describes the procedures to provision processors, by equipping them, unequipping
them, removing them, and restoring them. This topic describes provisioning for the processors
directly related to links and for the admin processor.
• Equip processor
• Unequip processor
• Remove processor
• Restore processor
• Display processor configuration
• Display routing processor
• Display routing processor status
Equip processor
Use this procedure to equip the AE1LK, CEDLK, CELK, HELK, and CTDLK processors.
The AE1LK, CEDLK, CELK, HELK, and CTDLK processors provide these functions:
The CEDLK and CTDLK processor are duplicated for reliability and must be equipped before any
audits can be performed.
Constraints
The processor must reside in a slot designated by the prompts in the command sequence.
Data tables
The system accesses the hardware database tables to add an AE1LK, CEDLK, CELK, HELK, and
CTDLK processor to the system. However, the system does not access the SS7 network data
tables.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: CHANGE PROCES EQUIP
2 Prompt: SUBTYP*E=
Enter: [AE1LK, CEDLK, CELK, HELK, or CTDLK]
3 Prompt: SUNIT=
Enter: unit number of the processor being changed
0-127 (unit number for AE1LK and HELK)
0-119 (unit number for CELK)
0-99 (unit number for CEDLK)
0-63 (unit number for CTDLK and IPLK)
0-47 (unit number for IPUA)
If you enter AE1LK, CELK, HELK, IPLK, or IPUA in Step 2; go to Step 5.
If you enter CEDLK or CTDLK in Step 2; continue.
4 Prompt: PAIR=
Enter: [A or B]
5 Prompt: EQU*IP=
Enter: [UNEQD or EQD]
Enter EQD to equip the processor.
Note: The default value in the following prompts differs for each processors.
6 Prompt: BOARD*TYPE=
Enter: board type
Enter the board type that contains the device.
7 Prompt: FRNAME=
Enter: [ALF or LEF]
8 Prompt: FRNUM=
Enter: [0-0]
The default value is 0.
9 Prompt: VERT*ICAL=
Enter: [4, 10, 16, 22, 28, 34, 40, 46, 52, 58, or 64]
Enter the physical location of the device according to the number of vertical units from
the floor.
10 Prompt: HORIZ*ONTAL=
Enter: [1-21]
Enter the physical location of the device according to the slot number.
The system shows the configuration data entered for the processor.
Unequip processor
Use this procedure to unequip the processor.
Constraints
Data tables
The system accesses hardware database tables to unequip a processor. However, the system
does not access SS7 network data tables.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: CHANGE PROCES EQUIP
2 Prompt: SUBTYP*E=
Enter: (one of the following choices)
ADMIN; go to Step 4.
AE1LK; go to Step 3.
CCM; go to Step 4.
CEDLK; go to Step 3.
CELK; go to Step 3.
CTDLK; go to Step 3.
HELK; go to Step 3.
IPLK; go to Step 3.
IPUA; go to Step 3.
3 Prompt: SUNIT=
Enter: processor number
0-127 (unit number for AE1LK and HELK)
0-119 (unit number for CELK)
0-99 (unit number for CEDLK)
0-63 (unit number for CTDLK and IPLK)
0-47 (unit number for IPUA)
If you enter AE1LK, CELK, HELK, IPLK, or IPUA in Step 2, go to Step 5.
If you enter CEDLK or CTDLK in Step 2, continue.
4 Prompt: PAIR=
Enter: [A or B]
5 Prompt: EQU*IP=
Enter: [EQD or UNEQD]
Enter UNEQD to unequip the processor.
The system shows the configuration data entered for the processor.
Remove processor
Use this procedure to take a processor out of service so it can be reset and reloaded with
software. These options are available when a processor is removed from service:
• BOOT to reset the processor, load the operating system, and leave the processor in a
usable state
• NOBOOT to reset the processor
• RESTART to reset the processor and restart existing programs
Constraints
Data tables
The system accesses hardware database tables to remove a processor. However, the system
does not access SS7 network data tables.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
ALERT
ALERT! Do not remove the mate processor in a CCM, CTDLK, CEDLK, or TMM pair until the
COMM 88 IPR and the COMM 548 IPR (for 5070 SSG systems with flexible routing enabled) with
dataword 1=00FF% and dataword 2=0002% are received for the processor just restored. Failure
to wait for these IPRs may result in SS7 message loss. A CTDLK or TMM processor is not fully
restored until the system sends the SS7 “RECOVERY COMPLETED” IPR (COMM 88) and the
“FLEXIBLE ROUTING APPLICATION downloading status completed” IPR (COMM 548 with
dataword 1=00FF% and dataword 2=0002%) for 5070 SSG systems with flexible routing enabled.
The COMM 88 IPR indicates that the recovery process to rebuild and resynchronize the
database tables has started. The COMM 548 with dataword 1=00FF% and dataword 2=0002%
indicates that downloading of the flexible routing database tables has completed.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: REMOVE PROCES
2 Prompt: PROC=
Enter: [ADMIN, ALARM, AE1LK, CCM, CTDLK, CEDLK, CELK, HELK, DSS, FLXMGR,
IPLK, IPUA, LTD, MTNC, SM, TERMLK, TMM, TNC]
If you enter ADMIN, CCM, FLXMGR, MTNC, SM, TMM, or TNC, go to Step 4.
If you enter AE1LK, CEDLK, CELK, HELK, CTDLK, DSS, IPLK, IPUA, LTD, or TERMLK, go to
Step 3.
If you enter ALARM, go to Step 5.
3 Prompt: DEVNO=
Enter: processor unit number
ALL or 0-127 (unit number for AE1LK and HELK)
ALL or 0-119 (unit number for CELK)
ALL or 0-99 (unit number for CEDLK)
ALL or 0-15 (unit number for DSS)
ALL or 0-63 (unit number for IPLK and CTDLK)
ALL or 0-47 (unit number for IPUA)
ALL or 0-13 (unit number for LTD)
ALL or 0-3 (unit number for TERMLK)
If you enter AE1LK, CELK, HELK, DSS, IPLK, IPUA, or TERMLK in Step 2; go to Step 5.
If you enter CTDLK, LTD, or CEDLK in Step 2; continue.
4 Prompt: DEVID=
Enter: [A or B]
5 Prompt: REMOVE=
Enter: (one of the following choices)
BOOT or B (select the boot option)
NOBOOT or N (select the no boot option)
RESTAR or R (select the restart option)
Restore processor
Use this procedure to restore a specific processor to service. This command performs these
actions:
The restore procedure places a processor back in service. These options are available when a
processor is restored to service:
The processor LED remains red until all resident programs are loaded into the processor, and
then the light changes to green.
Constraints
Data tables
The system accesses hardware database tables to restore a processor. However, the system
does not access SS7 network data tables.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: RESTORE PROCES
2 Prompt: PROC=
Enter: [ADMIN, ALARM, AE1LK, CCM, CTDLK, CELK, CEDLK, HELK, DSS, FLXMGR,
IPLK, IPUA, LTD, MTNC, SM, TERMLK, TMM, TNC]
If you enter ADMIN, CCM, FLXMGR, MTNC, TMM, or TNC; go to Step 4.
If you enter AE1LK, CEDLK, HELK, CTDLK, CELK, DSS, IPLK, IPUA, LTD, or TERMLK; go to
Step 3.
If you enter ALARM, go to Step 5.
3 Prompt: DEVNO=
Enter: processor unit number
ALL or 0-127 (unit number for AE1LK and HELK)
ALL or 0-119 (unit number for CELK)
ALL or 0-99 (unit number for CEDLK)
ALL or 0-15 (unit number for DSS)
ALL or 0-63 (unit number for IPLK and CTDLK)
ALL or 0-47 (unit number for IPUA)
ALL or 0-13 (unit number for LTD)
ALL or 0-3 (unit number for TERMLK)
If you enter AE1LK, CELK, HELK, DSS, IPLK, or IPUA in Step 2, go to Step 5.
If you enter CTDLK, LTD, or CEDLK in Step 2, continue.
4 Prompt: DEVID=
Enter: [A or B]
5 Prompt: RESTOR=
Enter: (one of the following choices)
COLD or C (cold restart option)
WARM or W (warm restart option)
IPL or I (IPL option)
The system performs the restore process and issues the COMM 88 IPR.
Constraints
Data tables
The system reads hardware configuration and status tables to show the configuration of a
processor. However, the system does not read SS7 data tables.
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISPLA PROCES EQUIP
2 Prompt: SUBTYP*E=
Enter: (one of the following choices)
ADMIN; go to Step 4.
AE1LK; go to Step 3.
CCM; go to Step 4.
CEDLK; go to Step 3.
CELK; go to Step 3.
CTDLK; go to Step 3.
HELK; go to Step 3.
DSS; go to Step 3.
FLXMGR; go to Step 4.
IPLK; go to Step 3.
IPUA; go to Step 3.
3 Prompt: UNIT=
Enter: processor unit number
ALL or 0-127 (unit number for AE1LK and HELK)
ALL or 0-119 (unit number for CELK)
ALL or 0-99 (unit number for CEDLK)
ALL or 0-15 (unit number for DSS)
ALL or 0-63 (unit number for IPLK and CTDLK)
ALL or 0-47 (unit number for IPUA)
This entry defines the device unit number.
If you enter AE1LK, CELK, HELK, DSS, IPLK, or IPUA in Step 2, the system displays the
configuration data; go to Step 5.
If you enter CEDLK or CTDLK in Step 2, continue.
4 Prompt: PAIR=
Enter: [A or B]
The system displays the configuration data.
Constraints
Data tables
The system receives the parameters showing the link data table (Y34).
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISPLA CCS LINKRT
2 Prompt: PSU*BTYP=
Enter: (one of the following choices)
AE1LK (routing processor subtype); go to Step 3.
CEDLK (routing processor pair subtype); go to Step 4.
CTDLK (routing processor pair subtype); go to Step 5.
HELK (routing processor subtype); go to Step 6.
IPLK (routing processor subtype); go to Step 7.
CELK (routing processor pair subtype); go to Step 8.
ALL, the system displays the link table; go to Step 10.
<RETURN> (for link number prompt); go to Step 9.
3 Prompt: APRO*NUM=
Enter: [0-127]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
The system displays the link table; go to Step 10.
4 Prompt: PAIR*NUM=
Enter: [0-99]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
The system displays the link table; go to Step 10.
5 Prompt: CTDPRO*NUM=
Enter: [0-63]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
The system displays the link table; go to Step 10.
6 Prompt: HE*NUM=
Enter: [0-127]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
The system displays the link table; go to Step 10.
7 Prompt: IP*NUM=
Enter: [0-63]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
The system displays the link table; go to Step 10.
8 Prompt: CELK*PRNUM=
Enter: [0-119]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
The system displays the link table; go to Step 10.
9 Prompt: DL*INK=
Enter: [0-3071]
Enter a single number, list of numbers, range of numbers, or ALL for all link numbers.
The system displays the link table.
Constraints
Data tables
The following database tables are accessed when the status of a routing processor is displayed:
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: STATUS CCS LINKRT
2 Prompt: PSU*BTYP=
Enter: (one of the following choices)
AE1LK (routing processor subtype); go to Step 3.
CEDLK (routing processor pair subtype); go to Step 4.
CTDLK (routing processor pair subtype); go to Step 5.
HELK (routing processor subtype); go to Step 6.
IPLK (routing processor subtype); go to Step 7.
CELK (routing processor subtype); go to Step 8.
ALL; go to Step 10.
<RETURN>; go to Step 9.
3 Prompt: AE*NUM=
Enter: [0-127]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
Go to Step 10.
4 Prompt: CEDPRO*NUM=
Enter: [0-99]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
Go to Step 10.
5 Prompt: CTDRO*NUM=
Enter: [0-63]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
Go to Step 10.
6 Prompt: HEPRO*NUM=
Enter: [0-127]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
Go to Step 10.
7 Prompt: IPRO*NUM=
Enter: [0-63]
Enter a single number, list of numbers, range of numbers, or ALL for all processor
numbers.
Go to Step 10.
8 Prompt: CEPRO*NUM=
Enter: [0-119]
Enter a single number, list of numbers, range of numbers, or ALL for all link numbers.
Go to Step 10.
9 Prompt: DL*INK=
Enter: [0-3071]
Enter a single number, list of numbers, range of numbers, or ALL for all link numbers.
The system displays the link table.
10 Prompt: REF*RESH=
Enter: [YES, NO, Y, N, R, or NR]
If you enter N, NO, or NR, the system displays the status table, go to Step 12;
otherwise, continue.
11 Prompt: FREQ*UENC=
Enter: (one of the following choices)
5-255 (refresh frequency in seconds)
<RETURN> (5 seconds - the default value)
The system displays the status table.
The status table is refreshed for the frequency entered in Step 11.
Link span
Span performance monitoring detects error conditions on the span and reports IPRs and
alarms. Measurements are collected to facilitate network engineering and analysis of
equipment performance.
Constraints
Data tables
When parameters associated with an existing link span are changed, these data tables are
changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: CHANGE MAINT LKSPDF
2 Prompt: SUBTYPE=
Enter: AE1LK, CEDLK, CELK, or HELK; go to E1 link span.
CTDLK; go to T1 link span.
E1 link span
3 Prompt: CRC4*-Monitoring=
Enter: cyclic redundancy check error monitoring
Y (enable the error monitoring)
N (disable the error monitoring - default); go to Step 5.
4 Prompt: EBIT*-Monitoring=
Enter: EBIT error monitoring
Y (enable the error monitoring)
N (disable the error monitoring - default)
5 Prompt: CAS*-Monitoring=
Enter: channel associated signaling alarm monitoring on time slot 16
Y (enable the error monitoring - default)
N (disable the error monitoring)
If you entered AE1LK in Step 2; continue, otherwise go to Step 7.
6 Prompt: SLOT16-FOR-SS7SIGNALING=
Enter: time slot 16 for SS7 signaling
Y (enable the error monitoring)
N (disable the error monitoring - default)
7 Prompt: AIS*16-Monitoring=
Enter: AIS 16 error alarm monitoring
Y (enable the error monitoring)
N (disable the error monitoring - default)
8 Prompt: LINE*CODE=
Enter: line code for the link span
AMI (alternate mark inversion)
HDB3 (high density bipolar three - default)
If you entered CEDLK or CELK in Step 2, go to Step 10; otherwise, continue.
9 Prompt: TIMI*NG-SOURCE=
Enter: timing source for the link span
SYSTEM - default
LINE
10 Prompt: E1*IDLE-CODE=
Enter: [0-FF]
The idle channel codes for a link span. Default is 54.
The system shows the selection menu:
+------------------------MENU---------------------------+
| CHANGE VALUES FOR THE INDICATED ALARM TYPE |
|-------------------------------------------------------|
| 1 = AIS ERROR 2 = LOSS ERROR |
| 3 = FRAME LOSS ERROR 4 = LCA ERROR |
| 5 = AIS16 ERROR 6 = REMOTE ALARM ERROR |
| 7 = MULTIFRAME ERROR 8 = REMOTE MULTIFRAME ERROR |
| 9 = BI POLAR ERROR 10 = FRAME SLIP ERROR |
|11 = FAS ERROR 12 = CRC4 ERROR |
|13 = EBIT ERROR 14 = ES ERROR |
|15 = SES ERROR 16 = UAS ERROR |
+-------------------------------------------------------+
| 99 = EXIT AND UPDATE DISK IF ANY CHANGE MADE |
+-------------------------------------------------------+
11 Prompt: SELEC*TION=
Enter: (one of the choices mentioned in the menu)
1, 2, 4, or 5, go to Step 15.
3, 6, 7, or 8, go to Step 12.
9, 10, 11, 14, or 15, go to Step 23.
12, go to Step 34.
13, go to Step 35.
16, go to Step 36.
99, the system shows equipage, characteristics, and alarm thresholds for link
span. go to Step 37.
12 Prompt: CON*INUOUS-INTEGRATION-PERIOD=
Enter: the number of 100-millisecond scans allowed
13 Prompt: CONT*INUOUS-CLEAR-PERIOD=
Enter: the number of seconds to monitor for the clear threshold
14 Prompt: CONTI*NUOUS-CLEAR-THRESHOLD=
Enter: the maximum continuous response violations allowed during the clear period
15 Prompt: LIN*K-SPAN-REMOVAL=
Enter: [Y or N]
Enter Y if the 1-second alarm threshold is reached and the link span is to be removed.
If you entered 1 or 2 in Step 11, the system displays the selection menu; go to Step 11.
If you entered 6 or 8 in Step 11, go to Step 17.
Otherwise, continue.
16 Prompt: XM*IT-REMOTE-ALARM=
Enter: [Y or N]
Enter Y if a remote alarm is to be transmitted to the far-end switch when the OS
threshold is reached and when the link span is removed.
If you entered 4 or 5 in Step 11, the system displays the selection menu; go to Step 11.
If you entered 3, 7, 12, 13, or 16 in Step 11, go to Step 23.
Otherwise, continue.
17 Prompt: L*ONG-INTEGRATION-PERIOD=
Enter: the number of hours over which errors are accumulated
18 Prompt: LO*NG-MINOR-THRESHOLD=
Enter: the long period alarm minor threshold
19 Prompt: LON*G-MAJOR-THRESHOLD=
Enter: the long period alarm OS threshold
20 Prompt: LONG*OS-THRESHOLD=
Enter: the long period alarm OS threshold
21 Prompt: CL*EAR-LONG-PERIOD=
Enter: the number of hours to monitor for the clear threshold
22 Prompt: CLE*AR-LONG-THRESHOLD
Enter: the maximum long period violations allowed during the clear period
If you entered 3, 7, 9, 11, 12, or 13 in Step 11, enter the link span removal value and
the XMIT remote alarm value. The system displays the selection menu; go to Step 11.
If you entered 6 or 8 in Step 11, enter the link span removal value. The system displays
the selection menu; go to Step 11.
If you entered 14, 15, or 16 in Step 11, the system displays the selection menu; go to
Step 11.
Otherwise, continue.
23 Prompt: SH*ORT-INTEGRATION-PERIOD=
Enter: the number of seconds over which errors are accumulated
If you entered 10 in Step 11, go to Step 29; otherwise, continue.
24 Prompt: SHO*RT-MINOR-THRESHOLD=
Enter: the short period alarm minor threshold
25 Prompt: SHOR*T-MAJOR-THRESHOLD=
Enter: the short period alarm major threshold
26 Prompt: SHORT*OS-THRESHOLD=
Enter: the short period alarm OS threshold
27 Prompt: SHORT-*CLEAR-PERIOD=
Enter: the number of seconds to monitor for the clear threshold
28 Prompt: C*LEAR-SHORT-THRESHOLD=
Enter: the maximum short period violations allowed during the clear period
If you entered 3, 7, 9, 11, 12, or 13 in Step 11, enter the link span removal value and
the XMIT remote alarm value; go to Step 17.
If you entered 14, 15, or 16 in Step 11, go to Step 17.
Otherwise, continue.
29 Prompt: FRAME*-SLIP-SHORT-MINOR-THRESHOLD=
Enter: the period for frame slip error alarm minor threshold
30 Prompt: FRAM*E-SLIP-SHORT-MAJOR-THRESHOLD=
Enter: the period for frame slip error alarm major threshold
31 Prompt: FRA*ME-SLIP-SHORT-OS-THRESHOLD=
Enter: the period for frame slip error alarm OS threshold
32 Prompt: FR*AME-SLIP-SHORT-CLEAR-PERIOD=
Enter: the number of seconds to monitor for the clear threshold
33 Prompt: F*RAME-SLIP-SHORT-CLEAR-THRESHOLD=
Enter: the number of seconds to monitor for the clear error threshold
If you entered 10 in Step 11, enter the link span removal value and the XMIT remote
alarm value; go to Step 17; otherwise, continue.
34 Prompt: CRC*4-OS-ONE-SEC-THRESHOLD=
Enter: the number of CRC4 error counts per second
If you entered 12 in Step 11, go to Step 15; otherwise, continue.
35 Prompt: EB*IT-OS-ONE-SEC-THRESHOLD=
Enter: the number of EBIT error counts per second allowable
If you entered 13 in Step 11, go to Step 15; otherwise, continue.
36 Prompt: UAS*-OS-ONE-SEC-THRESHOLD=
Enter: the number of consecutive unavailable seconds allowable
If you have entered 16 in Step 11, go to Step 15; otherwise, continue.
37 Prompt: CONFIRM=
Enter: [Y, N, or M]
Y (execute the changes)
N (do not execute the changes)
M (multiple update)
<CTRL+A> (do not execute the changes and exit to the command prompt)
T1 link span
38 Prompt: LINE-*LENGTH=
Enter: (one of the following choices)
0 (0-99 ft)
1 (100-199 ft)
2 (200-299 ft)
3 (300-399 ft)
4 (400-499 ft)
5 (500-599 ft)
6 (600-655 ft)
<RETURN> (0 - the default value)
39 Prompt: T1*IDLE-CODE=
Enter: idle code
The system shows the following selection menu:
+------------------------MENU---------------------------+
| CHANGE VALUES FOR THE INDICATED ALARM TYPE |
|-------------------------------------------------------|
| 1 = RAI ERROR 2 = FRAME LOSS ERROR |
| 3 = BI-POLAR ERROR 4 = FRAME SLIP ERROR |
| 5 = CRC6 ERROR 6 = ES ERROR |
| 7 = SES ERROR 8 = UAS ERROR |
| 9 = DM ERROR 10 = CRC6 PER DM ERROR |
|11 = AIS ERROR 12 = LOS ERROR |
+-------------------------------------------------------+
| 99 = EXIT AND UPDATE DISK IF ANY CHANGE MADE |
+-------------------------------------------------------+
40 Prompt: SELEC*TION=
Enter: (one of the choices mentioned in the menu)
If you enter 1, 11, or 12, go to Step 61.
If you enter 2, go to Step 41.
If you enter 3, go to Step 43.
If you enter 4, go to Step 46.
If you enter 5, go to Step 48.
If you enter 6, go to Step 51.
If you enter 7, go to Step 53.
41 Prompt: FRM*-LOSS-HOURLY-THRESHOLD=
Enter: number of frame losses allowed per hour
42 Prompt: FRM-*LOSS-DAILY-THRESHOLD=
Enter: number of frame losses allowed per day
The system displays the selection menu; go to Step 40.
43 Prompt: BI*POLAR-1-SECOND-THRESHOLD=
Enter: number of bipolar violations allowed per second
44 Prompt: BIPO*LAR-HOURLY-THRESHOLD=
Enter: number of bipolar violations allowed per hour
45 Prompt: BIP*OLAR-DAILY-THRESHOLD=
Enter: number of bipolar violations allowed per day
Go to Step 61.
46 Prompt: FRM-S*LIP-HOURLY-THRESHOLD=
Enter: number of frame slip events allowed per hour
47 Prompt: FRM-SL*IP-DAILY-THRESHOLD=
Enter: number of frame slip events allowed per day
The system displays the selection menu; go to Step 40.
48 Prompt: CRC6*-1-SECOND-THRESHOLD=
Enter: number of CRC6 errors allowed per second
49 Prompt: CRC6-*HOURLY-THRESHOLD=
Enter: number of CRC6 errors allowed per hour
50 Prompt: CRC6-D*AILY-THRESHOLD=
Enter: number of CRC6 errors allowed per day
Go to Step 61.
51 Prompt: ES-H*OURLY-THRESHOLD=
Enter: number of errored seconds allowed per hour
52 Prompt: ES*-DAILY-THRESHOLD=
Enter: number of errored seconds allowed per day
The system displays the selection menu; go to Step 40.
53 Prompt: SES*-HOURLY-THRESHOLD=
Enter: number of severely errored seconds allowed per hour
54 Prompt: SE*-S-DAILY-THRESHOLD=
Enter: number of severely errored seconds allowed per day
The system displays the selection menu; go to Step 40.
55 Prompt: U*AS-1-SECOND-THRESHOLD=
Enter: number of consecutive unavailable seconds allowed per second
56 Prompt: UA*S-HOURLY-THRESHOLD=
Enter: number of unavailable seconds allowed per hour
57 Prompt: UAS-*DAILY-THRESHOLD=
Enter: number of consecutive unavailable seconds allowed per day
Go to Step 61.
58 Prompt: DM*-HOURLY-THRESHOLD=
Enter: number of degraded minutes allowed per hour
59 Prompt: DM-*DAILY-THRESHOLD=
Enter: number of degraded minutes allowed per day
The system displays the selection menu; go to Step 40.
60 Prompt: CRC6-E*RRORS-PER-DEGRADED-MINUTES=
Enter: number of CRC6 errors allowable within a minute before declaring a
degraded minute
The system displays the selection menu; go to Step 40.
61 Prompt: LINK-S*PAN-REMOVAL=
Enter: [Y or N]
If you enter 1, 11, or 12, the system displays the selection menu. Go to Step 40.
62 Prompt: XM*IT-REMOTE-ALARM=
Enter: [Y or N]
Enter Y if a remote alarm is to be transmitted to the far-end switch when the OS
threshold is reached and when the link is removed.
The system displays the selection menu; go to Step 40.
63 Prompt: CONF*IRM=
Enter: (one of the following choices)
Y (execute the changes)
N (do not execute the changes and re-prompt)
<CTRL+A> (do not execute the changes and exit to the command prompt)
END PROCEDURE
Constraints
Data tables
The system receives the parameters showing the default link span tables.
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISPLAY MAINT LKSPDF
2 Prompt: SUBTYPE=
Enter: [AE1LK, CEDLK, CELK, CTDLK, or HELK]
The system shows the equipage, characteristics, and error alarm thresholds for a
default link processor subtype.
Constraints
Link span characteristics cannot be changed when a link span is in the ACTM/OOSA state. Use
the Remove link span procedure to place the link span in an OOSM state.
Data tables
When parameters associated with an existing link span are changed, these data tables are
changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: CHANGE MAINT LKSPAN
Note: Link span characteristics cannot be changed when a link span is in the
ACTM/OOSA state. Use the Remove link span procedure to place the link span in an
OOSM state.
2 Prompt: CHAN*GE-OPTION(A,B,C)=
Enter: [A, B, or C]
A (link span equipage and characteristics only)
B (link span error alarm threshold data only)
C (change both)
3 Prompt: SUBTYPE=
Enter: [AE1LK, CELK, CEDLK, or HELK]; go to E1 link span.
CTDLK; go to T1 link span.
E1 link span
4 Prompt: UNIT*NUMBER=
Enter: (one of the following choices)
0-127 (unit number for AE1LK and HELK)
0-119 (unit number for CELK)
0-99 (unit number for CEDLK)
0-63 (unit number for CTDLK)
If you entered AE1LK or HELK in Step 3, go to Step 6; otherwise, continue.
5 Prompt: LI*NK-SPAN-NUMBER=
Enter: [ALL or 0-3]
6 Prompt: LINKS*PAN-NUMBER=
Enter: [0-3]
If the processor controlling the link span is unequipped, go to Step 7.
If the link span is ACTM/OOSA, go to the note before Step 2.
If you enter A or C in Step 2, and the link span is OOSM or unequipped, go to Step 8.
If you enter B in Step 2, and the link span is OOSM or unequipped, the system displays
the selection menu. Go to Step 18.
Note: Step 7 is used to confirm whether you want to continue to configure the link span
when the controlling processor is unequipped.
7 Prompt: CONF*IRM=
Enter: (one of the following choices)
Y (continue link span configuration)
N (do not continue link span configuration)
<CTRL+A> (do not continue link span configuration and exit to the command
prompt)
If you enter N, go to Step 2.
If you enter Y and A or C in Step 2, go to Step 8.
If you enter Y and B in Step 2, the system shows the following selection menu:
+------------------------MENU---------------------------+
| 0 = APPLY DEFAULT SPAN ERROR ALARM VALUE FOR CHANGE |
+-------------------------------------------------------+
| CHANGE VALUES FOR THE INDICATED ALARM TYPE |
|-------------------------------------------------------|
| 1 = AIS ERROR 2 = LOS ERROR |
| 3 = FRAME LOSS ERROR 4 = LCA ERROR |
| 5 = AIS16 ERROR 6 = REMOTE ALARM ERROR |
| 7 = MULTIFRAME ERROR 8 = REMOTE MULTIFRAME ERROR |
| 9 = BI POLAR ERROR 10 = FRAME SLIP ERROR |
|11 = FAS ERROR 12 = CRC4 ERROR |
|13 = EBIT ERROR 14 = ES ERROR |
|15 = SES ERROR 16 = UAS ERROR |
+-------------------------------------------------------+
| 99 = EXIT AND UPDATE DISK IF ANY CHANGE MADE |
+-------------------------------------------------------+
Go to Step 18.
8 Prompt: EQUIPPED*STATUS=
Enter: (one of the following choices)
EQD (equip the link span); continue
UNEQD(unequip the link span); the system displays the parameters, go to
Step 44.
9 Prompt: CONF*IRM=
Enter: (one of the following choices)
Y (use default data)
N (do not use default data)
<CTRL+A> (do not execute changes and exit to the command prompt)
If you enter N, continue.
If you enter Y and you entered A in Step 2, the system shows link span equipage and
characteristics. Go to Step 44.
If you enter Y and C in Step 2, the system shows link span equipage, characteristics,
and alarm thresholds. Go to Step 44.
10 Prompt: CRC4*-Monitoring=
Enter: cyclic redundancy check error monitoring
Y (enable the error monitoring)
N (disable the error monitoring - default); go to Step 12.
11 Prompt: EBIT*-Monitoring=
Enter: EBIT error monitoring
Y (enable the error monitoring)
N (disable the error monitoring - default)
12 Prompt: CAS*-Monitoring=
Enter: channel associated signaling alarm monitoring on time slot 16
Y (enable the error monitoring - default)
N (disable the error monitoring)
If you entered AE1LK in Step 2; continue, otherwise go to Step 14.
13 Prompt: SLOT16-FOR-SS7SIGNALING=
Enter: time slot 16 for SS7 signaling
14 Prompt: AIS*16-Monitoring=
Enter: AIS 16 error alarm monitoring
Y (enable the error monitoring)
N (disable the error monitoring-default)
15 Prompt: LINE*CODE=
Enter: line code for the link span
AMI (alternate mark inversion)
HDB3 (high density bipolar three - default)
If you entered CEDLK or CELK in Step 2, go to Step 17; otherwise, continue.
16 Prompt: TIMI*NG-SOURCE=
Enter: timing source for the link span
SYSTEM -default
LINE
17 Prompt: E1*IDLE-CODE=
Enter: [0-FF]
The idle channel codes for a link span. Default is 54. Go to Step 44.
18 Prompt: SELEC*TION=
Enter: (one of the choices mentioned in the menu)
0; the system displays the default span error value, go to Step 44.
1, 2, 4, or 5, go to Step 22.
3, 6, 7, or 8, go to Step 19.
9, 10, 11, 14, or 15, go to Step 30.
12, go to Step 41.
13, go to Step 42.
16, go to Step 43.
99, the system shows equipage, characteristics, and alarm thresholds for link
span. Go to Step 44.
19 Prompt: CON*TINUOUS-INTEGRATION-PERIOD=
Enter: the number of 100-millisecond scans allowed
20 Prompt: CONT*INUOUS-CLEAR-PERIOD=
Enter: the number of seconds to monitor for the clear threshold
21 Prompt: CONTI*NUOUS-CLEAR-THRESHOLD=
Enter: the maximum continuous response violations allowed
22 Prompt: LIN*K-SPAN-REMOVAL=
Enter: [Y or N]
Enter Y if the 1-second alarm threshold is reached and the link span is to be removed.
If you entered 1 or 2 in Step 18, the system displays the selection menu; go to Step 18.
If you entered 6 or 8 in Step 18, go to Step 24.
Otherwise, continue.
23 Prompt: XM*IT-REMOTE-ALARM=
Enter: [Y or N]
Enter Y if a remote alarm is to be transmitted to the far-end switch when the OS
threshold is reached and when the link is removed.
If you entered 4 or 5 in Step 18, the system displays the selection menu; go to Step 18.
If you entered 3, 7, 12, 13, or 16 in Step 18, go to Step 30.
Otherwise, continue.
24 Prompt: L*ONG-INTEGRATION-PERIOD=
Enter: the number of hours over which errors are accumulated
25 Prompt: LO*NG-MINOR-THRESHOLD=
Enter: the long period alarm minor threshold
26 Prompt: LON*G-MAJOR-THRESHOLD=
Enter: the long period alarm major threshold
27 Prompt: LONG*OS-THRESHOLD=
Enter: the long period alarm OS threshold
28 Prompt: CL*EAR-LONG-PERIOD=
Enter: the number of hours to monitor for the clear threshold
29 Prompt: CLE*AR-LONG-THRESHOLD=
Enter: the maximum long period violations allowed during the clear period
If you entered 3, 7, 9, 10, 11, 12, or 13 in Step 18, enter the link span removal value
and the XMIT remote alarm value. The system displays the selection menu; go to
Step 18.
If you entered 6 or 8 in Step 18, enter the link span removal value. The system displays
the selection menu; go to Step 18.
If you entered 14, 15, or 16 in Step 18, the system displays the selection menu; go to
Step 18.
Otherwise, continue.
30 Prompt: SH*ORT-INTEGRATION-PERIOD=
Enter: the number of seconds over which errors are accumulated
If you entered 10 in Step 18, go to Step 36; otherwise, continue.
31 Prompt: SHO*RT-MINOR-THRESHOLD=
Enter: the short period alarm minor threshold
32 Prompt: SHOR*T-MAJOR-THRESHOLD=
Enter: the short period alarm major threshold
33 Prompt: SHORT*OS-THRESHOLD=
Enter: the short period alarm OS threshold
34 Prompt: SHORT-*CLEAR-PERIOD=
Enter: the number of seconds to monitor for the clear threshold
35 Prompt: C*LEAR-SHORT-THRESHOLD=
Enter: the maximum short period violations allowed during the clear period
If you entered 3, 7, 9, 11, 12, or 13 in Step 18, enter the link span removal value and
the XMIT remote alarm value, then go to Step 24.
If you entered 14, 15, or 16 in Step 18, go to Step 24.
Otherwise, continue.
36 Prompt: FRAME*-SLIP-SHORT-MINOR-THRESHOLD=
Enter: the period for frame slip error alarm minor threshold
37 Prompt: FRAM*E-SLIP-SHORT-MAJOR-THRESHOLD=
Enter: the period for frame slip error alarm major threshold
38 Prompt: FRA*ME-SLIP-SHORT-OS-THRESHOLD=
Enter: the period for frame slip error alarm OS threshold
39 Prompt: FR*AME-SLIP-SHORT-CLEAR-PERIOD=
Enter: the number of seconds to monitor for the clear threshold
40 Prompt: F*RAME-SLIP-SHORT-CLEAR-THRESHOLD=
Enter: the number of seconds to monitor for the clear error threshold
If you entered 10 in Step 18, enter the link span removal value and the XMIT remote
alarm value; go to Step 24.
Otherwise, continue.
41 Prompt: CRC*4-OS-ONE-SEC-THRESHOLD=
Enter: the number of CRC4 error counts per second
If you entered 12 in Step 18, go to Step 22; otherwise, continue.
42 Prompt: EB*IT-OS-ONE-SEC-THRESHOLD=
Enter: the number of EBIT error counts per second allowable
If you entered 13 in Step 18, go to Step 22; otherwise, continue.
43 Prompt: UAS*-OS-ONE-SEC-THRESHOLD=
Enter: the number of consecutive unavailable seconds allowable
If you entered 16 in Step 18, go to Step 22; otherwise, continue.
44 Prompt: CONFIRM=
Enter: (one of the following choices)
Y (execute the changes)
N (do not execute the changes)
M (multiple update)
<CTRL+A> (do not execute the changes and exit to the command).
T1 link span
45 Prompt: UNIT*NUMBER=
Enter: device unit number, range of unit numbers, or ALL
46 Prompt: LI*NK-SPAN-NUMBER=
Enter: relative link span to be accessed
If the processor controlling the link span is unequipped, go to Step 47.
If the link span is ACTM/OOSA, go to the note before Step 2.
If you enter A or C in Step 2, and the link span is OOSM or unequipped, go to Step 48.
If you enter B in Step 2, and the link span is OOSM or unequipped, the system displays
the selection menu. Go to Step 53.
Note: Step 47 is used to confirm whether you want to continue to configure the link
span when the controlling processor is unequipped.
47 Prompt: CONF*IRM=
Enter: (one of the following choices)
Y (continue link span configuration)
N (do not continue link span configuration)
<CTRL+A> (do not continue link span configuration and exit to the command
prompt)
If you enter N, go to Step 2.
If you enter Y and A or C in Step 2, go to Step 48.
If you enter Y and B in Step 2, the system shows the following selection menu:
+------------------------MENU---------------------------+
| 0 = APPLY DEFAULT SPAN ERROR ALARM VALUE FOR CHANGE |
+------------------------MENU---------------------------+
| CHANGE VALUES FOR THE INDICATED ALARM TYPE |
|-------------------------------------------------------|
| 1 = RAI ERROR 2 = FRAME LOSS ERROR |
| 3 = BI-POLAR ERROR 4 = FRAME SLIP ERROR |
| 5 = CRC6 ERROR 6 = ES ERROR |
| 7 = SES ERROR 8 = UAS ERROR |
| 9 = DM ERROR 10 = CRC6 PER DM ERROR |
|11 = AIS ERROR 12 = LOS ERROR |
+-------------------------------------------------------+
| 99 = EXIT AND UPDATE DISK IF ANY CHANGE MADE |
+-------------------------------------------------------+
Go to Step 53.
48 Prompt: EQUIPPED*STATUS=
Enter: (one of the following choices)
EQD (equip the link span); continue.
UNEQD (unequip the link span); go to Step 77.
49 Prompt: CONF*IRM=
Enter: (one of the following choices)
Y (use default data)
N (do not use default data)
<CTRL+A> (do not execute changes and exit to the command prompt)
If you enter N, go to Step 50.
If you enter Y and A in Step 2, the system shows link span equipage and characteristics.
Go to Step 77.
If you enter Y and C in Step 2, the system shows link span equipage, characteristics and
alarm thresholds. Go to Step 77.
50 Prompt: LINE-*LENGTH=
Enter: (one of the following choices)
0 (0-99 ft)
1 (100-199 ft)
2 (200-299 ft)
3 (300-399 ft)
4 (400-499 ft)
5 (500-599 ft)
6 (600-655 ft)
<RETURN> (0 - the default value)
51 Prompt: TIMI*NG-SOURCE=
Enter: system or line timing source
52 Prompt: T1*IDLE-CODE=
Enter: idle code
The system shows the link span equipage and characteristics; go to Step 77.
53 Prompt: SELEC*TION=
Enter: (one of the choices)
If you enter 0, the system displays the default span error value; go to Step 77.
If you enter 1, 11, or 12, go to Step 74.
If you enter 2, go to Step 54.
If you enter 3, go to Step 56.
If you enter 4, go to Step 59.
If you enter 5, go to Step 61.
If you enter 6, go to Step 64.
If you enter 7, go to Step 66.
If you enter 8, go to Step 68.
If you enter 9, go to Step 71.
If you enter 10, go to Step 73.
If you enter 99, the system shows equipage, characteristics, and alarm thresholds for
link span. Go to Step 77.
54 Prompt: FRM*-LOSS-HOURLY-THRESHOLD=
Enter: number of frame loss allowed per hour
55 Prompt: FRM-*LOSS-DAILY-THRESHOLD=
Enter: number of frame loss allowed per day
The system displays the selection menu; go to Step 53.
56 Prompt: BI*POLAR-1-SECOND-THRESHOLD=
Enter: number of bipolar violation allowed per second
57 Prompt: BIPO*LAR-HOURLY-THRESHOLD=
Enter: number of bipolar violation allowed per hour
58 Prompt: BIP*OLAR-DAILY-THRESHOLD=
Enter: number of bipolar violation allowed per day
Go to Step 75.
59 Prompt: FRM-S*LIP-HOURLY-THRESHOLD=
Enter: number of frame slip events allowed per hour
60 Prompt: FRM-SL*IP-DAILY-THRESHOLD=
Enter: number of frame slip events allowed per day
The system displays the selection menu; go to Step 53.
61 Prompt: CRC6*-1-SECOND-THRESHOLD=
Enter: number of CRC6 errors allowed per second
62 Prompt: CRC6-*HOURLY-THRESHOLD=
Enter: number of CRC6 errors allowed per hour
63 Prompt: CRC6-D*AILY-THRESHOLD=
Enter: number of CRC6 errors allowed per day
Go to Step 75.
64 Prompt: ES-H*OURLY-THRESHOLD=
Enter: number of errored seconds allowed per hour
65 Prompt: ES*-DAILY-THRESHOLD=
Enter: number of errored seconds allowed per day
The system displays the selection menu; go to Step 53.
66 Prompt: SES*-HOURLY-THRESHOLD=
Enter: number of severely errored seconds allowed per hour
67 Prompt: SE*-S-DAILY-THRESHOLD=
Enter: number of severely errored seconds allowed per day
The system displays the selection menu; go to Step 53.
68 Prompt: U*AS-1-SECOND-THRESHOLD=
Enter: number of consecutive unavailable seconds allowed per second
69 Prompt: UA*S-HOURLY-THRESHOLD=
Enter: number of unavailable seconds allowed per hour
70 Prompt: UAS-*DAILY-THRESHOLD=
Enter: number of consecutive unavailable seconds allowed per day
Go to Step 75.
71 Prompt: DM*-HOURLY-THRESHOLD=
Enter: number of degraded minutes allowed per hour
72 Prompt: DM-*DAILY-THRESHOLD=
Enter: number of degraded minutes allowed per day
The system displays the selection menu; go to Step 53.
73 Prompt: CRC6-E*RRORS-PER-DEGRADED-MINUTES=
Enter: number of CRC6 errors allowed within a minute before declaring a degraded
minute
The system displays the selection menu; go to Step 53.
74 Prompt: LINK*-SPAN-REMOVAL=
Enter: [Y or N]
Enter Y if the link span is to be removed when an alarm condition is present.
The system displays the selection menu; go to Step 53.
75 Prompt: LINK-S*PAN-REMOVAL=
Enter: [Y or N]
Enter Y if 1-second alarm threshold is reached and the link span is to be removed.
76 Prompt: XM*IT-REMOTE-ALARM=
Enter: [Y or N]
Enter Y if a remote alarm is to be transmitted to the far-end switch when the OS
threshold is reached and when the link is removed.
The system displays the selection menu; go to Step 53.
77 Prompt: CONF*IRM=
Enter: (one of the following choices)
Y (execute the changes)
N (do not execute the changes)
M (multiple update)
<CTRL+A> (do not execute the changes and exit to the command prompt)
END PROCEDURE
Constraints
Data tables
The system receives the parameters showing the default link span tables.
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISPLAY MAINT LKSPAN
2 Prompt: DISP*LAY-OPTION(A,B)=
Enter: [A or B]
A (display link span equipage and characteristics)
B (display link span equipage, characteristics, and link span error alarm data)
3 Prompt: SUBTYPE=
Enter: [AE1LK, CEDLK, CELK, CTDLK, or HELK]
4 Prompt: UNIT*NUMBER=
Enter: device unit number
ALL or 0-127 (unit number for AE1LK and HELK)
ALL or 0-119 (unit number for CELK)
ALL or 0-99 (unit number for CEDLK)
ALL or 0-63 (unit number for CTDLK)
5 Prompt: LI*NK-SPAN-NUMBER=
Enter: relative link span to be accessed
The system shows the link span parameters.
Constraints
Data tables
The system accesses hardware database tables to remove a link span. However, the system
does not access SS7 network data tables.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: REMOVE LKSPAN
2 Prompt: SUB*TYPE=
Enter: [AE1LK, CEDLK, CELK, CTDLK, or HELK]
3 Prompt: UNIT=
Enter: (one of the following choices)
ALL or 0-127 (unit number for AE1LK and HELK); go to Step 6.
ALL or 0-119 (unit number for CELK)
ALL or 0-99 (unit number for CEDLK)
ALL or 0-63 (unit number for CTDLK)
4 Prompt: LI*NK-SPAN=
Enter: [ALL or 0-3]
The system performs the remove link span process.
Note: The prompt in Step 5 is displayed if the span has any active links.
5 Prompt: CONT*INUE=
Enter: [YES, Y, NO, or N]
If you enter N or NO, go to Step 7; otherwise, continue
Constraints
Data tables
The system accesses hardware database tables to restore a link span. However, the system
does not access SS7 network data tables.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: RESTORE LKSPAN
2 Prompt: SUB*TYPE=
Enter: [AE1LK, CEDLK, CELK, CTDLK, or HELK]
3 Prompt: UNIT=
Enter: (one of the following choices)
ALL or 0-127 (unit number for AE1LK and HELK); go to Step 5.
ALL or 0-119 (unit number for CELK)
ALL or 0-99 (unit number for CEDLK)
ALL or 0-63 (unit number for CTDLK)
4 Prompt: LI*NK-SPAN=
Enter: [ALL or 0-3]
The system performs the restore link span process.
Constraints
Data tables
The following database tables are accessed when the status of a link span is checked:
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: STATUS LKSPAN
2 Prompt: STAT*US-OPTION=
Enter: [A, B, or C]
A (span configuration status)
B (out-of-service spans only)
C (span error alarm information - default)
3 Prompt: SUB*TYPE=
Enter: [AE1LK, CEDLK, CELK, CTDLK, or HELK]
If you enter B in Step 2, go to Step 7; otherwise, continue.
4 Prompt: UNIT*-NUMBER=
Enter: (one of the following choices)
ALL or 0-127 (unit number for AE1LK and HELK)
ALL or 0-119 (unit number for CELK)
ALL or 0-99 (unit number for CEDLK)
ALL or 0-63 (unit number for CTDLK)
5 Prompt: SPAN=
Enter: the span number
Note: The prompt in Step 6 is displayed only for CTDLK processor subtype.
6 Prompt: STANDBY*-PROC-STAT=
Enter: link span error alarms data for standby processor
7 Prompt: MON*ITOR=
Enter: [Y, YES, N, or NO]
Y or YES (status report to be monitored periodically); continue.
N or NO (status report not to be monitored periodically - default); the system
displays the status of the link span; go to Step 9.
8 Prompt: FREQ*UENCY=
Enter: monitor frequency in seconds
The system displays the status of the link span.
Constraints
Data tables
The system accesses hardware database tables to enable a link span loopback.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: ENABLE LKSPAN LOOPBK
2 Prompt: SU*BTYPE=
Enter: CTDLK
3 Prompt: U*NIT=
Enter: [0-63]
4 Prompt: LI*NK-SPAN=
Enter: [ALL or 0-3]
5 Prompt: LOOPBK*TYPE=
Enter: setting link span to loopback state
The system shows the enabled link span parameters.
Data tables
The system accesses hardware database tables to disable a link span loopback.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISABLE LKSPAN LOOPBK
2 Prompt: SU*BTYPE=
Enter: CTDLK
3 Prompt: U*NIT=
Enter: [0-63]
4 Prompt: LI*NK-SPAN=
Enter: [ALL or 0-3]
The system shows the disabled link span parameters.
Links
Each link associated with an equipped call routing and link processor is assigned to a link set so
that the link can carry traffic.
SLS rotation
The SLS rotation is done prior to transmission on all the link sets except C links. The SLS
rotation is used for load-sharing methods that use the least-significant bit for selecting a link
set from a combined link set. The SLS rotation is also used to ensure that the information used
to load-share at any subsequent 5070 SSG is independent of the information used at the
previous 5070 SSG.
If the 5070 SSG uses a link set for routing and the SLS value is mapped to a link set SLS-to-link
assignment and the SLS rotation is OFF, then the 5070 SSG routes the traffic to that link as long
as the link is active. If the SLS rotation is ON, then the SLS value is rotated and the 5070 SSG
routes the traffic to the link to which the rotated SLS value was assigned. Only the four
least-significant bits of the 8-bit SLS code are rotated. Shifting the four least-significant bits of
the SLS code one position to the right and placing the first bit into the fourth bit position does
the rotation.
• Assign link
• Change link
• Display link
• Delete link
• Activate link
• Deactivate link
• Display span link
• Display CCS link status
• Display CCS link set status
• Display CCS destination status
Assign link
Use this procedure to create a signaling link and assign it to a link set. This procedure
provisions these parameters:
• SLC
• Routing processor pair
• Activation status
The system updates the link set parameters such as the number of links in the link set and the
number of active links required to stay unrestricted when the command is executed.
Constraints
• When a new link is added to an A, B, D, or E link set, the link set data must be updated to
increase the number of active links required to stay unrestricted. This parameter is
determined according to these restrictions:
– The number of active links must equal half the total number of links in a link set
containing an even number of links.
– The number of active links must equal half the total number of links plus one in a link
set containing an odd number of links.
• When a new link is added to a C link set, the number of active links required to stay
unrestricted is set to zero.
• The call routing and link processor supporting the new link should be equipped before
adding a link to a link set.
• The link set must be defined before adding links.
• Links in each link set should be distributed between two or more backplanes and across
ethernet switches. This configuration produces the most optimal distribution to handle
failure cases and prevents a backplane failure from failing more than half the links in a
link set.
• Links in multiple-link link sets should each be assigned to a different processor. If the
number of processors in the system is insufficient to support this rule, links must be
distributed such that no more than half the links in a link set are assigned to a single card.
Otherwise, a single card failure or SPLIT SYSTEM command may not leave a sufficient
number of links in service to support the traffic on that link set.
• For multiple-link link sets, half the links in each link set must be assigned to a split
processor and the other half to either a combine or activate processor. This configuration
splits the links in each link set evenly between the active and inactive sides during the
upgrade.
Data tables
When a new link set is added to the database, these data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: ASSIGN CCS LINK
2 Prompt: LS*NAMNUM=
Enter: the linkset name or number
The system shows the links in the link set.
3 Prompt: SLC=
Enter: [0-15]
4 Prompt: L*INK=
Enter: [0-3071]
If the issued link set is not a combined one, go to Step 6; otherwise, continue.
5 Prompt: CSLS=
Enter: [0-31]
6 Prompt: PSLS=
Enter: [0-15]
7 Prompt: RPSUB=
Enter: [AE1LK, CEDLK, CELK, CTDLK, HELK, or IPLK]
If you enter AE1LK, CELK, HELK, or IPLK, go to Step 9; otherwise, continue.
8 Prompt: PA*IR=
Enter: (one of the following choices)
0-99 (unit number for CEDLK)
0-63 (unit number for CTDLK)
Go to Step 10.
9 Prompt: RPNUM=
Enter: routing processor number
0-127 (unit number for AE1LK and HELK)
0-119 (unit number for CELK)
0-63 (unit number for IPLK)
If you enter AE1LK, HELK, or IPLK in Step 7, go to Step 12; otherwise, continue.
10 Prompt: SPAN*NUM=
Enter: [0-3]
11 Prompt: CHAN*NELNUM=
Enter: [1-31]
12 Prompt: ACT*IVATE=
Enter: [Y or N]
Y (request link to be activated)
N (request link to be deactivated)
The system shows the parameters of a assigned link.
Change link
Use this procedure to change the link parameters of an SLC, change routing processor-pair
parameters, request a change in activation status, and move a link from one link set to
another. Moving a link from one set to another using the CHANGE CCS LINK command preserves
previously set link parameters. Specify the link being changed by using the link set name or
number, or make the change using the SLC and link number.
Constraints
• When the number of links is changed in an A, B, D, or E link set, the link set data must be
updated to increase the number of active links required to stay unrestricted. This
parameter is determined according to these restrictions:
– The number of active links must equal half the total number of links in a link set
containing an even number of links.
– The number of active links must equal half the total number of links plus one in a link
set containing an odd number of links.
• When a new link is changed in a C link set, the number of active links required to stay
unrestricted is set to zero.
• The link set must be defined before changing links.
Data tables
The system changes the SS7 link data table (ATY34) when a link is changed in the database.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: CHANGE CCS LINK
2 Prompt: LS*NAMNUM=
Enter: (one of the following choices)
<RETURN>; go to Step 3.
A link set name or number; the system shows the links in the link set; go to
Step 4.
3 Prompt: L*INK=
Enter: [0-3071]
The system shows the links in the link set.
4 Prompt: SLC=
Enter: [0-15]
5 Prompt: CS*LC=
Enter: [0-15]
6 Prompt: SLSM*ENU=
Enter: (one of the following choices)
1 (assign a new SLS to a link); go to Step 12.
2 (change an SLS for a link to another SLS); go to Step 9.
3 (delete an SLS from a link); go to Step 12.
<RETURN>; go to Step 13.
Note: The prompts Step 7 and Step 8 are displayed only if you enter a combined link set
in the change option in Step 6.
7 Prompt: OLDCOMBSLS=
Enter: old signaling service code
8 Prompt: NEWCOMBSLS=
Enter: new signaling link service code
9 Prompt: OLDSLS=
Enter: [0-15]
Enter a single number, list of numbers, or range of numbers.
The system displays an old signaling link service code; go to Step 10.
<RETURN>; go to Step 13.
10 Prompt: NEWSLS=
Enter: new signaling link service code
Go to Step 13.
Note: Step 11 is displayed only if you enter a combined link set in the assign or delete
option in Step 6.
11 Prompt: COMBSLS=
Enter: [0-31]
12 Prompt: SLS=
Enter: [0-31]
13 Prompt: CRPSUB=
Enter: [AE1LK, CELK, HELK, CEDLK, CTDLK, or IPLK]
This entry defines the new routing processor subtype.
If you enter AE1LK, CELK, HELK, or IPLK, go to Step 15; otherwise, continue.
14 Prompt: CPA*IR=
Enter: (one of the following choices)
0-99 (unit number for CEDLK)
0-63 (unit number for CTDLK)
Go to Step 16.
15 Prompt: CRPNUM=
Enter: new routing processor number
0-127 (unit number for AE1LK and HELK)
0-119 (unit number for CELK)
0-63 (unit number for IPLK)
If you enter AE1LK, HELK, or IPLK in Step 13, go to Step 18.
Otherwise, continue.
16 Prompt: CSPAN*NUM=
Enter: span number
17 Prompt: CCHAN*NELNUM=
Enter: new channel number
18 Prompt: CAC*TIVATE=
Enter: [Y or N]
Y (activate the link)
N (do not activate the link)
The system shows the links in the link set, including changed information. An asterisk
(*) appears by the SLC for the changed link.
Display link
Use this procedure to show the parameters for a link.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISPLA CCS LINK
2 Prompt: LSD*ISP=
Enter: (one of the following choices)
The link set name or number; go to Step 3.
ALL; the system shows the link sets; go to Step 5.
<RETURN>; go to Step 4.
3 Prompt: DPS*LC=
Enter: SLC assigned to the link or ALL
The system shows the requested link sets and associated SLCs; go to Step 5.
4 Prompt: DL*INK=
Enter: [0-3071]
Enter the link set number.
The system shows the requested link sets and associated SLCs.
Delete link
Use this procedure to delete one link or all links from a link set. The system updates the
parameters of the link set to change the number of links in a link set and the number of links
required to remain unrestricted.
Constraints
• When a link is deleted from an A, B, D, or E link set, the number of active links required to
stay unrestricted must be updated for the link set according to these restrictions:
– Half of the total number of links in a link set containing an even number of links
– Half of the total number of links plus one in a link set containing an odd number of
links
• When a new link is deleted from a C link set, the number of active links required to stay
unrestricted is set to zero.
• The number of links in a link set field in the database for a given link set is updated with
the total number of links when a link is deleted from the link set.
• When a link selected for deletion is a M2PA IP link (assigned to IPLK processor), the
corresponding entry in IPCONN (ATY1A) is deleted.
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not use the DELETE CCS LINK command to move a link from one link set to another
because previously set link parameters will be lost and the link will assume default
parameters. Use the CHANGE CCS LINK command instead.
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DELETE CCS LINK
2 Prompt: LS*NAMNUM=
Enter: (one of the following choices)
The link set name or number; go to Step 4.
<RETURN>; continue.
3 Prompt: L*INK=
Enter: [0-3071]
The system shows the links in the link set; go to Step 5.
4 Prompt: DSL*C=
Enter: signaling link code
SLC assigned to the link
ALL
The system shows the parameters.
Activate link
Use this procedure to bring the link online by initiating the SS7 alignment procedure.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: ACTIVA CCS LINK
2 Prompt: LINK=
Enter: [0-3071]
Enter the link ID.
3 Prompt: DIST*RIB=
Enter: YES
This entry defines whether or not to distribute link parameters.
The following message appears when the link set is activated:
DISK ENTRY AND PROCESSOR(S) UPDATED
Deactivate link
Use this procedure to remove the link from active service.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DEACTI CCS LINK
2 Prompt: LINK=
Enter: [0-3071]
Enter the link ID.
The following message appears when the link set is deactivated:
DISK ENTRY AND PROCESSOR(S) UPDATED
Constraints
Data tables
The system retrieves the span link information from the following database tables:
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISPLAY CCS SPLINK
2 Prompt: PROCS*UB=
Enter: [AE1LK, CEDLK, CELK, HELK, or CTDLK]
If you enter AE1LK; go to Step 3.
If you enter CEDLK; go to Step 4.
If you enter CELK; go to Step 5.
If you enter CTDLK; go to Step 6.
If you enter HELK; go to Step 7.
3 Prompt: AE1LK*RPNUM=
Enter: [0-127]
Go to Step 8.
4 Prompt: CEDPROC*UM=
Enter: [0-99]
Go to Step 8.
5 Prompt: CELK*RPNUM=
Enter: [0-119]
Go to Step 8.
6 Prompt: CTPROC*NUM=
Enter: [0-63]
Go to Step 8.
7 Prompt: HEPROC*UM=
Enter: [0-127]
Go to Step 8.
8 Prompt: SPA*N=
Enter: [0-3]
The system shows the routing link identity and channel number.
Constraints
Data tables
BEGIN PROCEDURE
1 Prompt: >
Enter: STATUS CCS LINK
2 Prompt: L*INK=
Enter: [0-3071]
Enter a single number, list of number, or ALL for all link numbers.
3 Prompt: REF*RESH=
Enter: [YES, NO, Y, N, R, or NR]
If you enter N, NO, or NR, go to Step 5; otherwise, continue.
The default is NO.
4 Prompt: FREQ*UENC=
Enter: [5-255]
The default is 5 seconds.
Constraints
Data tables
The system retrieves data from the MTP link set number (Y45) table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: STATUS CCS LINKSE
2 Prompt: LINKS*ET=
Enter: link set name or number
Enter a single number, list of number, or ALL for all link numbers.
3 Prompt: REF*RESH=
Enter: [YES, NO, Y, N, R, or NR]
If you enter N, NO, or NR, go to Step 5; otherwise, continue.
The default is NO.
4 Prompt: FREQ*UENC=
Enter: [5-255]
The default is 5 seconds.
Constraints
Data tables
The system retrieves data from the MTP link set number (Y45) table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: STATUS CCS DEST
2 Prompt: NODE=
Enter: (one of the following choices)
A node name; go to Step 5.
<RETURN>; continue.
3 Prompt: LOG*NET=
Enter: (one of the following choices)
Logical network number or ALL; go to Step 5.
Logical network name; continue.
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for a
lognet.
The default value is none.
The system shows the parameters associated with the local node.
5 Prompt: DEST*TYPE=
Enter: [SM, DM, or ALL]
SM (static members)
DM (dynamic members)
ALL
The default value is ALL.
6 Prompt: ACT*IVE=
Enter: [Y, YES, N, or NO]
The default value is NO.
7 Prompt: FOR*MAT=
Enter: [B, S, or D]
B (Brief display)
S (Standard display - default)
D (Detailed display)
8 Prompt: REF*RESH=
Enter: [Y, YES, N, NO, R, or NR]
If you enter N, NO, or NR, go to Step 10; otherwise, continue.
The default value is NO.
9 Prompt: FREQ*UENC=
Enter: [5-255]
The default is 5 seconds.
However, special circumstances may require that some parameters be changed in operation.
The physical LSL parameters fall into five groups:
• Congestion level - defines congestion levels for messages being received and transmitted
• Timer - defines 5070 SSG MTP level 2 timer parameters
• Marginal threshold - defines hourly thresholds used to determine the marginal
performance of the LSL
• Common link - defines error-correction method, error-rate monitor, and octet threshold
Special system operation or a specific upgrade may require changes to one of these groups:
Received message congestion thresholds determine when a node sends link busy status
messages to an adjacent node and discards received messages. Transmitted message
congestion thresholds determine when a node invokes signaling traffic management procedure
to divert traffic from a congested link.
Note: For transmitted messages, separate congestion thresholds exist for each message
priority (L1, L2, and L3). There is an onset threshold, an abatement threshold, and a discard
threshold for each priority level.
Congestion level
attribute Identifies
RXONS Number of message buffers that contain received and untransmitted
messages - When the parameter exceeds the threshold, the node sends
retransmit messages.
RXABA Number of message buffers that contain received and untransmitted
messages - When the parameter falls below the threshold, the node resumes
normal operation.
RXDISC Number of message buffers containing received and untransmitted
messages - When the parameter exceeds the threshold, the node discards
further messages.
TXL1ONS, TXL2ONS, Number of message buffers containing received and untransmitted messages
TXL3ONS of a specific priority level (1, 2, or 3) - When the parameter exceeds the
threshold, the system is congested; the node instructs other nodes to send
lower priority messages away from the concerned destination.
TXL1ABA, TXL2ABA, Number of message buffers containing received and untransmitted messages
TXL3ABA of a specific priority level - When the parameter falls below the congestion
level, the node instructs other nodes to send all messages.
TXL1DISC, TXL2DISC, Number of message buffers containing untransmitted and unacknowledged
TXL3DISC messages - When the parameter exceeds the discard level, the node begins
deleting messages with lower priority than the priority level where congestion
is taking place.
TXONSET Number of message buffers to transmit congestion onset
TXABAT Number of message buffers to transmit congestion abatement
Note: The TXLONSET, TXLABAT, and TXLDISC prompts are issued only if the congestion parameter for
the logical network is set to “CONGESTION WITH PRIORITY”. The TXONSET and TXAABT prompts are
issued only if the congestion parameter for the logical network is set to “CONGESTION WITH LEVELS”.
Note: T97 and T98 are predefined for the SS7 protocol.
Timer parameters are defined for the initial alignment procedure and signaling link (level 2)
flow control. The default parameter for each timer depends on the speed of the link. Table A
lists the default timer rate for each signaling speed in seconds except for T9 in seconds:
Table A. E1 level 2 default timer parameters for signaling rates
Timer Default value (in seconds)
T1 45
T2S 15
T2L 90
T3 1.5
T4N 8.2
T4E 0.5
T5 0.12
T6 6
T7 1.0
T88 0.5
Constraints
These constraints are associated with changing physical low-speed E1 link parameters:
• The RX abatement level must be greater than 29 and less than the RX onset level plus 9.
• The RX onset level plus 9 must be less than the RX discard level.
• The RX discard level plus 9 must be less than 156.
• The TXL1 abatement level must be less than the TXL1 onset level plus 9.
• The TXL1 onset level must be greater than 49; the TXL1 onset level plus 9 must be less
than the TXL1 discard level.
• The discard level plus 9 for TXL1, TXL2, and TXL3 messages must be less than 140.
• The abatement level for TXL1, TXL2, and TXL3 messages must be greater than 9.
• The TXL2 onset level must be greater than TXL1 onset plus 9. The TXL2 onset level must
be greater than TXL2 abatement plus 9. TXL onset plus 9 must be less than the TXL2
discard level.
• The TXL3 onset level must be greater than the TXL3 abatement level plus 9. The TXL3
onset level must be greater than the TXL2 onset level plus 9.
• After physical parameters are changed for an active link, the link must be deactivated and
then reactivated with distribution to activate the new parameters.
• Parameters for T1–T7 must be multiples of 10.
Data tables
When physical link parameters are changed, these data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: The link has to be assigned to CEDLK and CELK. To assign a link, use the Assign
link procedure.
12 Prompt: >
Enter: CHANGE CCS CELKPA
13 Prompt: L*INK=
Enter: [0-3071]
14 Prompt: PARM*GP=
Enter: (one of the following choices)
1 (congestion level); perform this subsection: Change congestion level
parameters.
2 (timers); perform this subsection: Change timer parameters.
3 (traffic measurement marginal thresholds); perform this subsection:
Change marginal threshold parameters.
4 (common link); perform this subsection: Change common link parameters.
15 Prompt: RXONS=
Enter: maximum buffers to receive congestion onset
16 Prompt: RXABA=
Enter: maximum buffers to receive congestion abatement
17 Prompt: RXDISC=
Enter: maximum buffers to receive message discard
The system displays the prompts in Step 18 through Step 26 only if the congestion
parameter for the logical network is set to congestion with priorities; otherwise, go to
Step 27.
18 Prompt: TXL1ONS=
Enter: maximum L1 buffers to transmit congestion onset
19 Prompt: TXL1ABA=
Enter: maximum L1 buffers to transmit congestion abatement
20 Prompt: TXL1DISC=
Enter: maximum L1 buffers to transmit congestion discard
21 Prompt: TXL2ONS=
Enter: maximum L2 buffers to transmit congestion onset
22 Prompt: TXL2ABA=
Enter: maximum L2 buffers to transmit congestion abatement
23 Prompt: TXL2DISC=
Enter: maximum L2 buffers to transmit congestion discard
24 Prompt: TXL3ONS=
Enter: maximum L3 buffers to transmit congestion onset
25 Prompt: TXL3ABA=
Enter: maximum L3 buffers to transmit congestion abatement
26 Prompt: TXL3DISC=
Enter: maximum L3 buffers to transmit congestion discard
The system shows the congestion level parameters assigned to the low-speed E1 link; go
to Step 29.
27 Prompt: TXONSET=
Enter: maximum buffers to transmit congestion onset
28 Prompt: TXABAT=
Enter: maximum buffers to transmit congestion abatement
The system shows the congestion level parameters assigned to the low-speed E1 link.
Note: Defaults for each timer depend on the link speed (see Table A).
30 Prompt: TIMRDF=
Enter: [D or U]
D (select default timers T1-T7)
U (select user-defined timers T1-T7)
31 Prompt: T2TMER=
Enter: [L or H]
L (select low version of timer T2)
H (select high version of timer T2)
If you entered D in Step 30, go to Step 40; otherwise, continue.
32 Prompt: T1ALGN=
Enter: T1 timer parameter
33 Prompt: T2NALG=
Enter: T2 not aligned timer parameter
34 Prompt: T3ALGN=
Enter: T3 alignment timer parameter
35 Prompt: T4NORM=
Enter: T4 normal proving alignment state timer parameter
36 Prompt: T4EMERG=
Enter: T4 emergency proving alignment state timer parameter
37 Prompt: T5SIB=
Enter: T5 SIB timer parameter
38 Prompt: T6REM=
Enter: T6 high baud rate remote congestion timer parameter
39 Prompt: T7ACK=
Enter: T7 high baud rate acknowledgment delay timer parameter
40 Prompt: T88IDLE=
Enter: T8 low baud rate idle time
41 Prompt: T9FCT=
Enter: T9 false link congestion timer parameter
The system shows the timer parameters assigned to the low-speed E1 link.
43 Prompt: SUERR=
Enter: [1-65535]
This entry defines the hourly threshold for signal units received in error.
44 Prompt: NAKREC=
Enter: [1-65535]
This entry defines the hourly threshold for negative acknowledgments received.
45 Prompt: AUTOCHG=
Enter: [1-65535]
47 Prompt: ECM=
Enter: [B or P]
B (basic error correction)
P (preventive cyclic retransmission error correction); go to Step 48.
48 Prompt: N2OCT=
Enter: [2000-20000]
This entry defines the N2 SU octet forced retransmission threshold count.
Constraints
The link to be copied and the destination link must belong to the same logical network.
Data tables
When low-speed E1 link parameters are copied, these data tables are changed:
Procedure
BEGIN PROCEDURE
Note: The link has to be assigned to CEDLK and CELK. To assign a link, use the Assign
link procedure.
1 Prompt: >
Enter: COPY CCS CELKPA
2 Prompt: L*INK=
Enter: [0-3071]
3 Prompt: DSTLNK=
Enter: [0-3071]
Enter a single number, list of numbers, range of numbers, or combination of numbers.
The system shows the copied parameters of a single link to one or more links.
Constraints
Data tables
The system retrieves low-speed E1 link parameters from these data tables:
Procedure
BEGIN PROCEDURE
Note: The link has to be assigned to CEDLK and CELK. To assign a link, use the Assign
link procedure.
1 Prompt: >
Enter: DISPLA CCS CELKPA
2 Prompt: L*INK=
Enter: [0-3071]
3 Prompt: DPARAM*GP=
Enter: (one of the following choices)
0 (all groups)
1 (congestion level)
2 (timers)
3 (traffic measurement marginal threshold)
4 (common link)
The system shows the parameters of the SLPE link configuration table (Y49) and the
hourly marginal threshold table (W49) for a single link.
However, special circumstances may require that some parameters be changed in operation.
The physical LSL parameters fall into five groups:
• Congestion level - defines congestion levels for messages being received and transmitted
• Timer - defines 5070 SSG MTP level 2 timer parameters
• Marginal threshold - defines hourly thresholds used to determine the marginal
performance of the LSL
• Common link - defines error-correction method, error-rate monitor, and octet threshold
Special system operation or a specific upgrade may require changes to one of these groups:
Received message congestion thresholds determine when a node sends link busy status
messages to an adjacent node and discards received messages. Transmitted message
congestion thresholds determine when a node invokes signaling traffic management procedure
to divert traffic from a congested link.
Note: For transmitted messages, separate congestion thresholds exist for each message
priority (L1, L2, and L3). There is an onset threshold, an abatement threshold, and a discard
threshold for each priority level.
Congestion level
attribute Identifies
RXONS Number of message buffers that contain received and untransmitted
messages - When the parameter exceeds the threshold, the node sends
retransmit messages.
RXABA Number of message buffers that contain received and untransmitted
messages - When the parameter falls below the threshold, the node resumes
normal operation.
RXDISC Number of message buffers containing received and untransmitted
messages - When the parameter exceeds the threshold, the node discards
further messages.
TXL1ONS, TXL2ONS, Number of message buffers containing received and untransmitted messages
TXL3ONS of a specific priority level (1, 2, or 3) - When the parameter exceeds the
threshold, the system is congested; the node instructs other nodes to send
lower priority messages away from the concerned destination.
TXL1ABA, TXL2ABA, Number of message buffers containing received and untransmitted messages
TXL3ABA of a specific priority level - When the parameter falls below the congestion
level, the node instructs other nodes to send all messages.
TXL1DISC, TXL2DISC, Number of message buffers containing untransmitted and unacknowledged
TXL3DISC messages - When the parameter exceeds the discard level, the node begins
deleting messages with lower priority than the priority level where congestion
is taking place.
Level1 false Enables or disables the false congestion monitor flag.
congestion flag
The relationship between received message congestion levels is shown in the following list. RX
indicates received message.
The constraints associated with transmitted message congestion thresholds are shown in the
following list. TXL1 indicates transmitted message level 1 priority, TXL2 indicates transmitted
message level 2 priority, and TXL3 indicates transmitted message level 3 priority.
Note: The range of the timer values for T1 links differs based on the logical network assigned
to the ANSI or ITU protocol.
Note: T97 and T98 are predefined for the SS7 protocol.
Timer parameters are defined for the initial alignment procedure and signaling link (level 2)
flow control. The default parameter for each timer depends on the speed of the link. Table C
lists the default timer rate for each signaling speed in seconds except for T9 in seconds.
Table C. T1 level 2 default timer parameters for signaling rates
Timer 4800 b/s 9600 b/s 19.2 kb/s 56 kb/s 64 kb/s
T9* 30 30 30 30 30
Note: * In seconds.
Note: By default the CTDLK links takes all the timer values corresponding to 56 K baud rate.
Note: The T2 timer does not have a short or long version for CTDLK or CTLK links. So T2 timer selection is not
required
Signal unit error rate Error threshold for removing a link 20-1000
monitor from service
Constraints
These constraints are associated with changing physical low-speed T1 link parameters:
• The RX abatement level must be greater than 26 and less than the RX onset level plus 9.
• The RX onset level plus 9 must be less than the RX discard level.
• The RX discard level plus 9 must be less than 57.
• The TXL1 abatement level must be less than the TXL1 onset level plus 9.
• The TXL1 onset level must be greater than 62; the TXL1 onset level plus 9 must be less
than the TXL1 discard level.
• The discard level plus 9 for TXL1, TXL2, and TXL3 messages must be less than 140.
• The abatement level for TXL1, TXL2, and TXL3 messages must be greater than 9.
• The TXL2 onset level must be greater than TXL1 onset plus 9. The TXL2 onset level must
be greater than TXL2 abatement plus 9. TXL onset plus 9 must be less than the TXL2
discard level.
• The TXL3 onset level must be greater than the TXL3 abatement level plus 9. The TXL3
onset level must be greater than the TXL2 onset level plus 9.
• After physical parameters are changed for an active link, the link must be deactivated and
then reactivated with distribution to activate the new parameters.
• Parameters for T1-T7 must be multiples of 10.
Data tables
When physical link parameters are changed, these data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: The link has to be assigned to CTDLK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: CHANGE CCS T1LKPA
or
CHANGE CCS LINKPA
2 Prompt: L*INK=
Enter: [0-3071]
Enter the link ID.
3 Prompt: PARM*GP=
Enter: (one of the following choices)
1 (congestion level); perform the subsection Change congestion level
parameters.
2 (timers); perform the subsection Change timer parameters.
3 (traffic measurement marginal thresholds); perform the subsection Change
marginal threshold parameters.
4 (common link); perform the subsection Change common link parameters.
4 Prompt: RXONS=
Enter: maximum buffers to receive congestion onset
5 Prompt: RXABA=
Enter: maximum buffers to receive congestion abatement
6 Prompt: RXDISC=
Enter: maximum buffers to receive message discard
7 Prompt: TXL1ONS=
Enter: maximum L1 buffers to transmit congestion onset
8 Prompt: TXL1ABA=
Enter: maximum L1 buffers to transmit congestion abatement
9 Prompt: TXL1DISC=
Enter: maximum L1 buffers to transmit message discard
10 Prompt: LV1CON=
Enter: [YES, Y, NO, or N]
Y (enable the false congestion monitor flag)
N (disable the false congestion monitor flag)
11 Prompt: TXL2ONS=
Enter: maximum L2 buffers to transmit congestion onset
12 Prompt: TXL2ABA=
Enter: maximum L2 buffers to transmit congestion abatement
13 Prompt: TXL2DISC=
Enter: maximum L2 buffers to transmit message discard
14 Prompt: TXL3ONS=
Enter: maximum L3 buffers to transmit congestion onset
15 Prompt: TXL3ABA=
Enter: maximum L3 buffers to transmit congestion abatement
16 Prompt: TXL3DISC=
Enter: maximum L3 buffers to transmit message discard
The system shows the congestion level parameters assigned to the low-speed T1 link.
Note: The range of the timer values for T1 links differs based on the logical network
assigned to the ANSI or ITU protocol.
18 Prompt: TIMRDF=
Enter: [D or U]
D (select default timers T1-T7)
U (select user defined timers T1-T7)
19 Prompt: T2TMER=
Enter: [L or H]
L (select the low version of timer T2)
H (select the high version of timer T2)
If you enter D in Step 18, go to Step 28; otherwise, continue.
20 Prompt: T1ALGN=
Enter: T1 timer parameter
21 Prompt: T2NALG=
Enter: T2 not aligned timer parameter
22 Prompt: T3ALGN=
Enter: T3 alignment timer parameter
23 Prompt: T4NORM=
Enter: T4 normal proving alignment state timer parameter
24 Prompt: T4EMERG=
Enter: T4 emergency proving alignment state timer parameter
25 Prompt: T5SIB=
Enter: T5 SIB timer parameter
26 Prompt: T6REM=
Enter: T6 high baud rate remote congestion timer parameter
27 Prompt: T7ACK=
Enter: T7 high baud rate acknowledgment delay timer parameter
28 Prompt: T88IDLE=
Enter: T88 baud rate idle timer
29 Prompt: T9FCT=
Enter: T9 false link congestion timer parameter
The system shows the timer parameters assigned to the low-speed T1 link.
31 Prompt: SUERR=
Enter: [1-65535]
This entry defines the hourly threshold for signal units received in error.
32 Prompt: NAKREC=
Enter: [1-65535]
This entry defines the hourly threshold for negative acknowledgments received.
33 Prompt: AUTOCHG=
Enter: [1-65535]
This entry defines the hourly threshold for automatic changeovers.
35 Prompt: ECM=
Enter: [N or P]
N (normal error correction)
P (preventive cyclic retransmission error correction)
If you enter N in Step 35, then go to Step 37; otherwise, continue.
The system shows the existing common link parameters assigned to the low-speed link.
36 Prompt: N2OCT=
Enter: number of octets available for retransmission
37 Prompt: SUERMHI=
Enter: signal unit error rate monitor
38 Prompt: BAUDRT=
Enter: (one of the following choices)
1 (56 kb/s baud rate)
2 (64 kb/s baud rate)
The system shows the common link parameters assigned to the low-speed link.
Data tables
When low-speed T1 link parameters are copied, these data tables are changed:
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: The link has to be assigned to CTDLK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: COPY CCS T1LKPA
or
COPY CCS LINKPA
2 Prompt: LNKCPY=
Enter: [0-3071]
Enter the link ID.
3 Prompt: DSTLNK=
Enter: [0-3071]
Enter a single number, list of numbers, range of numbers, or a combination of numbers.
The system shows the copied parameters of a single link to one or more links.
Constraints
Data tables
The system retrieves low-speed T1 link parameters from these data tables:
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: The link has to be assigned to CTDLK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: DISPLA CCS T1LKPA
or
DISPLAY CCS LINKPA
2 Prompt: L*INK=
Enter: [0-3071]
Enter the link ID.
3 Prompt: DPARM*GP=
Enter: (one of the following choices)
0 (all groups)
1 (congestion level)
2 (timers)
3 (traffic measurement marginal threshold)
4 (common link)
The system shows the parameters of the SLPE link configuration table (Y49) and the
hourly marginal threshold table (W49) for a single link.
HSL parameters
Physical link parameters define the physical operation of the HSL. Generally, physical
parameters are established when the initial database is created; they are seldom changed.
When a new HSL is added, the physical parameters assigned to an HSL are usually copied for
the new HSL.
However, special circumstances may require that some parameters be changed in operation.
The physical HSL parameters fall into five groups:
• Common link - defines error-correction method, error-rate monitor, and octet threshold
• Congestion level - defines congestion levels for messages being received and transmitted
• Timer - defines 5070 SSG MTP level 2 timer parameters
• Marginal threshold - defines hourly thresholds used to determine the marginal
performance of the HSL
Special system operation or a specific upgrade may require changes to one of these groups:
Received message congestion thresholds determine when a node sends link busy status
messages to an adjacent node and discards received messages. Transmitted message
congestion thresholds determine when a node invokes signaling traffic management procedure
to divert traffic from a congested link.
Note: For transmitted messages, separate congestion thresholds exist for each message
priority (L1, L2, and L3). There is an onset threshold, an abatement threshold, and a discard
threshold for each priority level.
Congestion level
attribute Identifies
RXONS Number of message buffers that contain received and untransmitted
messages - When the parameter exceeds the threshold, the node sends
retransmit messages.
RXABA Number of message buffers that contain received and untransmitted
messages - When the parameter falls below the threshold, the node resumes
normal operation.
RXDISC Number of message buffers containing received and untransmitted
messages - When the parameter exceeds the threshold, the node discards
further messages.
TXL1ONS, TXL2ONS, Number of message buffers containing received and untransmitted messages
TXL3ONS of a specific priority level (1, 2, or 3) - When the parameter exceeds the
threshold, the system is congested; the node instructs other nodes to send
lower priority messages away from the concerned destination.
TXL1ABA, TXL2ABA, Number of message buffers containing received and untransmitted messages
TXL3ABA of a specific priority level - When the parameter falls below the congestion
level, the node instructs other nodes to send all messages.
TXL1DISC, TXL2DISC, Number of message buffers containing untransmitted and unacknowledged
TXL3DISC messages - When the parameter exceeds the discard level, the node begins
deleting messages with lower priority than the priority level where congestion
is taking place.
TXONSET Number of message buffers to transmit congestion onset.
TNABAT Number of message buffers to transmit congestion abatement.
Note: The congestion parameters must be set with the following criteria: RXL1AB
<RXL1ON<RXL1DS and TXL1AB <TXL1ON <TXL1DS <TXL2AB <TX2ON <TXL2DS <TXL3AB <TXL3ON
<TXL3DS, with all parameters differing by at least nine messages.
The default parameter for each timer depends on the speed of the link. Table H lists the
default timer rate.
Table H. HSL level 2 default timer parameters for signaling rates
Timer 2.048 Mb/s
Table H. HSL level 2 default timer parameters for signaling rates, contd
Timer 2.048 Mb/s
Note: T1, T2, T3,T6, T7, T4: normal proving in seconds. T5, T4: emergency proving in milliseconds.
Signal unit errors A limit on the number of signal units received with errors per hour
of operation
Automatic changeovers A limit on the number of times the link performs automatic
changeover to divert traffic from the link
Constraints
• The RX abatement level must be greater than 293 and less than the RX onset level plus 9.
• The RX onset level plus 9 must be less than the RX discard level.
• The RX discard level plus 9 must be less than 814.
• The TXL1 abatement level must be less than the TXL1 onset level plus 9.
• The TXL1 onset level must be greater than 49; the TXL1 onset level plus 9 must be less
than the TXL1 discard level.
• The discard level plus 9 for TXL1, TXL2, and TXL3 messages must be less than 140.
• The abatement level for TXL1, TXL2, and TXL3 messages must be greater than 9.
• The TXL2 onset level must be greater than TXL1 onset plus 9. The TXL2 onset level must
be greater than TXL2 abatement plus 9. TXL onset plus 9 must be less than the TXL2
discard level.
• The TXL3 onset level must be greater than the TXL3 abatement level plus 9. The TXL3
onset level must be greater than the TXL2 onset level plus 9.
• After physical parameters are changed for an active link, the link must be deactivated and
then reactivated with distribution to activate the new parameters.
• Parameters for T1–T7 must be multiples of 10.
Data tables
When physical link parameters are changed, these data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: The link has to be assigned to HELK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: CHANGE CCS HELKPA
2 Prompt: L*INK=
Enter: [0-3071]
The default value is none.
3 Prompt: PARAM*GP=
Enter: (one of the following choices)
1 (common link); perform the subsection: Change common link parameters.
2 (congestion link); perform the subsection: Change congestion level
parameters.
3 (timers); perform the subsection: Change timer parameters.
4 (traffic measurement marginal thresholds); perform the subsection: Change
marginal threshold parameters.
The default value is none.
4 Prompt: ECM=
Enter: [B or D]
B (basic error correction); go to Step 6.
P (preventive cyclic retransmission error correction); go to Step 5.
The default value is the current value or basic error correction method if the current
value is not valid.
5 Prompt: N2OCT=
Enter: number of octets available for retransmission
This entry defines the N2 SU octet forced retransmission threshold count.
The default value is the current value or 20000 if the current value is not valid.
7 Prompt: RXONS=
Enter: maximum buffers to receive congestion onset
8 Prompt: RXABA=
Enter: maximum buffers to receive congestion abatement
9 Prompt: RXDISC=
Enter: maximum buffers to receive message discard
Note: The system displays the prompts in Step 10 through Step 18 only if the congestion
parameter for the logical network is set to congestion with priorities; otherwise, go to
Step 19.
10 Prompt: TXL1ONS=
Enter: maximum l1 buffers to transmit congestion onset
11 Prompt: TXL1ABA=
Enter: maximum l1 buffers to transmit congestion abatement
12 Prompt: TXL1DISC=
Enter: maximum l1 buffers to transmit congestion discard
13 Prompt: TXL2ONS=
Enter: maximum l2 buffers to transmit congestion onset
14 Prompt: TXL2ABA=
Enter: maximum l2 buffers to transmit congestion abatement
15 Prompt: TXL2DISC=
Enter: maximum l2 buffers to transmit congestion discard
16 Prompt: TXL3ONS=
Enter: maximum l3 buffers to transmit congestion discard
17 Prompt: TXL3ABA=
Enter: maximum l3 buffers to transmit congestion abatement
18 Prompt: TXL3DISC=
Enter: maximum l3 buffers to transmit congestion discard
The system shows the congestion level parameters assigned to the HSL; go to Step 21.
Note: The system displays the prompts in Step 19 and Step 20 only if the congestion
parameter for the logical network is set to congestion with levels.
19 Prompt: TXONSET=
Enter: maximum buffers to transmit congestion onset
20 Prompt: TXABAT=
Enter: maximum buffers to transmit congestion abatement
The system shows the congestion level parameters assigned to the HSL.
22 Prompt: TIMRDF=
Enter: [D or U]
D (select default timers T1-T7); go to Step 32.
U (select user-defined timers T1-T7); continue.
The default value is the current value or D if the current value is not valid.
23 Prompt: T2TMER=
Enter: [L or H]
L (select low version of timer T2)
H (select high version of timer T2)
The default value is the current value or L if the current value is not valid.
24 Prompt: T1ALGN=
Enter: T1 timer parameter
The default is the current value or 300 milliseconds if the current value is not valid
25 Prompt: T2NALG=
Enter: T2 not aligned timer parameter
The default is the current value. if the current value is not valid, the default is assigned
depending on the T2TMER selection in Step 23.
If you entered L in Step 23, the default value is 15 milliseconds.
If you entered H in Step 23, the default value is 90 milliseconds.
26 Prompt: T3ALGN=
Enter: T3 aligned timer parameter
The default value is the current value or 105 milliseconds if the current value is not
valid.
27 Prompt: T4NORM=
Enter: T4 normal proving alignment state timer parameter
The default value is the current value or 30 milliseconds if the current value is not
valid.
28 Prompt: T4EMERG=
Enter: T4 emergency proving alignment state timer parameter
The default value is the current value or 500 milliseconds if the current value is not
valid.
29 Prompt: T5SIB=
Enter: T5 SIB timer parameter
The default value is the current value or 120 milliseconds if the current value is not
valid.
30 Prompt: T6ERM=
Enter: T6 high baud rate remote congestion timer parameter
The default value is the current value or 6 milliseconds if the current value is not valid.
31 Prompt: T7ACK=
Enter: T7 high baud rate acknowledgement delay timer parameter
The default value is the current value or 1000 if the current value is not valid.
The system shows the timer parameters assigned to the HSL.
33 Prompt: SUPER=
Enter: [1-65535]
This entry defines the hourly threshold for signal units received in error.
The default value is the current value or 6400 if the current value is not valid.
34 Prompt: NAKREC=
Enter: [1-65535]
This entry defines the hourly threshold for negative acknowledgement received.
The default value is the current value or 6400 if the current value is not valid.
35 Prompt: AUTOCHG=
Enter: [1-65535]
This entry defines the hourly threshold for automatic changeovers.
The default value is the current value or 4 if the current value is not valid.
Constraints
The link to be copied and the destination link must belong to the same logical network.
Data tables
When HSL parameters are copied, these data tables are changed:
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: The link has to be assigned to HELK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: COPY CCS HELKPA
2 Prompt: L*INK=
Enter: [0-3071]
The default value is none.
3 Prompt: DSTLNK=
Enter: [0-3071]
The system shows the copied parameters of a single link to one or more links.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: The link has to be assigned to HELK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: DISPLA CCS HELKPA
2 Prompt: L*INK=
Enter: [0-3071]
The default value is none.
3 DPARMGP=
Enter: (one of the following choices)
0 (All groups)
1 (Common link)
2 (Congestion level)
3 (Timers)
4 (Traffic measurement marginal threshold)
RXL1DS Number of message buffers containing received and untransmitted messages - When
the parameter exceeds the threshold, the node discards further messages.
TXL1ON, TXL2ON, Number of message buffers containing received and untransmitted messages of a
TXL3ON specific priority level (1, 2, or 3) - When the parameter exceeds the threshold, the
system is congested; the node instructs other nodes to send lower priority messages
away from the concerned destination.
TXL1AB, TXL2AB, Number of message buffers containing received and untransmitted messages of a
TXL3AB specific priority level - When the parameter falls below the congestion level, the
node instructs other nodes to send all messages.
Note: The congestion parameters must be set with the following criteria: RXL1AB < RXL1ON <
RXL1DS and TXL1AB < TXL1ON < TXL1DS < TXL2AB < TXL2ON < TXL2DS < TXL3AB < TXL3ON <
TXL3DS with all parameters differing by at least 25 messages.
COPTCC Time interval between transmission of BGN, END, RS and ER PDUs as long as
replies are received
COPTKA Maximum time interval to receive peer status or resumption of link traffic in
the keep-alive phase
CFNNIT2 Maximum time interval for alignment of a link in the align state
CFNNIT3 Time interval between the transmission of proving PDUs in the link proving
state
LMTNC Number of vail intervals to queue a PDU for transmission after receiving an
on-credit flow control message from the target
NUMINTL Number of monitoring intervals needed to span the time when messages are not
released from the buffers
CFC1CTR Number of proving PDUs to be sent after each T3 (CFNNIT3) interval in the
proving state
Data tables
When physical links are changed, these data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: The link has to be assigned to AE1LK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: CHANGE CCS E1LKPA
2 Prompt: HLINK=
Enter: [0-3071]
3 Prompt: PARMGPH=
Enter: (one of the following choices)
1 (ATM); perform the subsection Change ATM parameters.
2 (congestion level); perform the subsection Change congestion level
parameters.
3 (ATM timers); perform the subsection Change ATM timer parameters.
4 (traffic measurement marginal threshold); perform the subsection Change
traffic measurement marginal threshold parameters.
5 (SAAL); perform the subsection Change SAAL parameters.
4 Prompt: VPI=
Enter: [0-4095]
The default value is 0.
5 Prompt: VCI=
Enter: [0-65535]
The default value is 5.
6 Prompt: QSCLASS=
Enter: [0-3]
The default value is 3.
7 Prompt: LINBDO=
Enter: (one of the following choices)
0 (0 dB)
1 (7.5 dB)
2 (15 dB)
3 (22.5 dB)
Enter a line build out.
8 Prompt: CLKSCE=
Enter: (one of the following choices)
0 (line timing)
1 (LTD A)
2 (LTD B)
3 (NIC local oscillator)
Enter the timing type.
9 Prompt: TXPUTP=
Enter: (one of the following choices)
0 (0-133 ft)
1 (133-266 ft)
2 (266-399 ft)
3 (399-533 ft)
4 (533-655 ft)
Enter the TX pulse template.
10 Prompt: ATMSCR=
Enter: [YES or NO]
The default value is YES.
12 Prompt: RXL1ON=
Enter: maximum L1 buffers to receive congestion onset
13 Prompt: RXL1AB=
Enter: maximum L1 buffers to receive congestion abatement
14 Prompt: RXL1DS=
Enter: maximum L1 buffers to receive congestion discard
15 Prompt: TXL1ON=
Enter: maximum L1 buffers to transmit congestion onset
16 Prompt: TXL1AB=
Enter: maximum L1 buffers to transmit congestion abatement
17 Prompt: TXL1DS=
Enter: maximum L1 buffers to transmit congestion discard
18 Prompt: TXL2ON=
Enter: maximum L2 buffers to transmit congestion onset
19 Prompt: TXL2AB=
Enter: maximum L2 buffers to transmit congestion abatement
20 Prompt: TXL2DS=
Enter: maximum L2 buffers to transmit congestion discard
21 Prompt: TXL3ON=
Enter: maximum L3 buffers to transmit congestion onset
22 Prompt: TXL3AB=
Enter: maximum L3 buffers to transmit congestion abatement
23 Prompt: TXL3DS=
Enter: maximum L3 buffers to transmit congestion discard
25 Prompt: TMRDF=
Enter: [D or U]
D (default timers); go to Step 40.
U (user-defined timers); continue.
There is no default value.
26 Prompt: COPTCC=
Enter: [100-2000]
27 Prompt: COPTKA=
Enter: [25-500]
28 Prompt: COPTNR=
Enter: [500-2000]
29 Prompt: COPTP=
Enter: [25-500]
30 Prompt: COPTID=
Enter: [25-1000]
31 Prompt: COPTPV=
Enter: [0-1200]
32 Prompt: CFNNIT1=
Enter: [1-15]
33 Prompt: CFNNIT2=
Enter: [15-180]
34 Prompt: CFNNIT3=
Enter: [1000-25000]
35 Prompt: LMTRS=
Enter: [30-1440]
36 Prompt: LMTNC=
Enter: [1000-6000]
37 Prompt: LMTSUP=
Enter: [10-600]
38 Prompt: LMTLOS=
Enter: [500-10000]
39 Prompt: LMTTAU=
Enter: [25-250]
41 Prompt: EPSOEC=
Enter: [0-65535]
42 Prompt: SDPRETX=
Enter: [0-65535]
43 Prompt: HTAUTOC=
Enter: [0-65535]
44 Prompt: CPSOEC=
Enter: [0-65535]
46 Prompt: OPMAXCC=
Enter: [1-10]
47 Prompt: OPMAXPD=
Enter: [5-2120]
48 Prompt: OPMAXST=
Enter: [3-1021]
49 Prompt: CFNNIN1=
Enter: [50-50000]
50 Prompt: LMMXNRP=
Enter: [0-10]
51 Prompt: LMMEXSF=
Enter: [0-1000]
52 Prompt: LMQOSTH=
Enter: [100-1000]
53 Prompt: NUMINTL=
Enter: [1-25]
54 Prompt: NMITBLK=
Enter: [1-25]
55 Prompt: CFC1CTR=
Enter: [1-30]
Constraints
Data tables
When ATM over E1 high-speed link parameters are copied, these data tables are changed:
Procedure
BEGIN PROCEDURE
Note: The link has to be assigned to AE1LK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: COPY CCS E1LKPA
2 Prompt: HLINK=
Enter: [0-3071]
3 Prompt: DSTLNKH=
Enter: destination link ID
Enter a single number, list of numbers, range of numbers, or combination of numbers.
Constraints
Data tables
The system retrieves ATM over E1 high-speed link parameters from these data tables:
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: The link has to be assigned to AE1LK. To assign a link, use the Assign link
procedure.
1 Prompt: >
Enter: DISPLAY CCS E1LKPA
2 Prompt: HLINK=
Enter: [0-3071]
3 Prompt: DPARM*GPH=
Enter: (one of the following choices)
0 (all groups)
1 (ATM)
2 (congestion level)
3 (ATM timers)
4 (traffic measurement marginal threshold)
5 (SAAL)
6 (non provisional parameters)
SS7-IP interworking
This section describes the steps required to provision IP links and M3UA entities in the 5070
SSG.
The SS7 over IP using M2PA feature helps transport or receive SS7 traffic to or from an IP
network via an IPLK processor. The IPLK is a simplex, CP-1 processor that supports two IP ports
for connecting to the same or different IP networks.
The SS7 over IP using M3UA feature uses the IPUA processor. The IPUA is a simplex, CP-1 based
processor with two IP ports for connecting to the same or different IP networks. The IPUA
communicates with one or more ASPs according to the user-defined configuration. A separate
SCTP association is established with each ASP that the IPUA is configured to interface with,
and the M3UA layer on each IPUA uses the SCTP association to send the M3UA messages to the
appropriate ASP.
The SS7-IP interworking order of input figure illustrates the order of input for provisioning SS7
over IP links and M3UA entities in the 5070 SSG.
IPLK IPUA
Activate an application
server
Activate an application
server process
• Equip processor
• Display process equip
In addition, the following procedures (in the Processors and links section) can be performed for
processors configured as IPLK or IPUA:
• Unequip processor
• Remove processor
• Restore processor
• Display processor configuration
The following procedures (in the Processors and links section) can be performed for processors
configured as IPLK, but are not applicable to those configured as IPUA:
Equip processor
Use this procedure to equip the IPLK or IPUA processor.
Constraints
The processor must reside in a slot designated by the prompts in the command sequence.
Data tables
The system accesses hardware database tables to add an IPLK processor to the system.
However, the system does not access SS7 network data tables.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE PROCES EQUIP
2 Prompt: SUBTYP*E=
Enter: [IPLK or IPUA]
Enter the device subtype.
3 Prompt: SUNIT=
Enter: (one of the following choices)
IPLK (0-63)
IPUA (0-47)
4 Prompt: EQU*IP=
Enter: EQD
5 Prompt: BOARD*TYPE=
Enter: CP1
6 Prompt: FRNAME=
Enter: (one of the following choices)
ALF (administration link frame)
LEF (link expansion frame)
The default value is ALF.
7 Prompt: FRNUM=
Enter: (one of the following choices)
0 (for ALF)
0-2 (for LEF)
The default value is 0.
8 Prompt: VERT*ICAL=
Enter: [4, 10, 16, 22, 28, 34, 40, 46, 52, 58, or 64]
Enter the physical location of the device according to the number of vertical units from
the floor.
9 Prompt: HORIZ*ONTAL=
Enter: [1-21]
Enter the physical location of the device according to the slot number.
The system shows the configuration data entered for the processor.
Constraints
Data tables
The system reads hardware configuration and status tables to show the configuration of a
processor. However, the system does not read SS7 data tables.
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISPLA PROCES EQUIP
2 Prompt: SUBTYP*E=
Enter: [IPLK or IPUA]
3 Prompt: UNIT=
Enter: processor number
Use the ASSIGN HOSTS FILE MMI to configure the following IP routing information for each IP
interface:
• Source IP address
• Subnet MASK
• Four network routes (optional)
In addition, the IP address of the default route is configured for each processor.
Use this procedure to assign a local IP address, netmask, default router, and network routes to
each IPLK processor using the HOSTS FILE MMI commands. The hosts file resides on the admin
disk and associates host names with a corresponding local IP address, netmask, default router,
and network routes.
Constraints
• The IP address 127.0.0.1 is applicable for local loopback and it is preconfigured in the
hosts file.
• The hosts file MMI does not allow an IP address parameter in the range of 224.0.0.0 to
239.255.255.255 (reserved for multi-cast).
• The default router is optional, but if assigned, there can only be one for the processor.
The IP address of the default router is associated with one of the IP interfaces and
determines which IP interface to use when IP routing cannot determine where to send the
message. The default router prompt is not issued when the second IP interface is created.
Use the Change the host file procedure to change an existing default router.
Use the Display the host files procedure to display the parameters assigned to one more IP
interfaces.
Use the Delete hosts file procedure to delete all the parameters assigned to an IP interface.
Procedure
BEGIN PROCEDURE
! ALERT
ALERT! Use the COPY ADMIN FILE MMI command to make a copy of the existing hosts file
before modifying it. Be careful when updating the hosts file with the new IP configurations.
Contact your next level of support if you have any problems.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: Collect the local IP addresses, netmask, and remote IP addresses before starting
the procedure. A default route is not required if all IPLK traffic stays within a single
subnet.
2 Prompt: R*EPLACE=
Enter: N
3 Prompt: S*OURCE=
Enter: HOSTS
4 Prompt: D*ESTINATION=
Enter: a destination file name
5 Prompt: S*OURCE=
Enter: <RETURN>
6 Prompt: V*ERIFY=
Enter: Y
Note: After setting up the hosts file, you must remove and restore the affected
processors to pick up the new hosts file.
7 Prompt: >
Enter: ASSIGN HOSTS FILE
8 Prompt: LOCAL*REMOTE*ENTITY=
Enter: [LOCAL, L, REMOTE, or R]
If you enter R or REMOTE, go to Step 16; otherwise, continue.
9 Prompt: LOCAL*IP*ENTITY=
Enter: [PROCESSOR, P, CCMALIAS, or A]
If you enter CCMALIAS or A, go to Step 17; otherwise, continue.
10 Prompt: PROC*SUB=
Enter: [CCM, IPLK, IPUA, or PXP]
If you enter CCM, go to Step 15.
If you enter IPLK, go to Step 11.
If you enter IPUA, go to Step 12.
If you enter PXP, go to Step 13.
11 Prompt: PROC*NUM=
Enter: [0-63]
Go to Step 14.
12 Prompt: PROCNUMBER=
Enter: [0-47]
Go to Step 14.
13 Prompt: PROCESSOR*NUM=
Enter: [0-11]
Enter the processor number for PXP.
Go to Step 15.
14 Prompt: PORT*ID=
Enter: [1 or 2]
Go to Step 17.
15 Prompt: PAIR*ID=
Enter: [A or B]
A (displays the parameters of host file with pair ID A)
B (displays the parameters of host file with pair ID B)
Go to Step 17.
16 Prompt: REMOTE*IP*ENTITY=
Enter: [NTPSERVER or N]
17 Prompt: IP*ADDR=
Enter: IP address
Enter the IP address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
If you entered R in Step 8 or A in Step 9, go to Step 29; otherwise, continue.
18 Prompt: NET*ADDR=
Enter: netmask address
Enter the netmask address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
19 Prompt: DFT*ROUTER=
Enter: default router address
Enter the default router address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255 or
NONE.
If you entered CCM or PXP in Step 10, go to Step 29; otherwise, continue.
20 Prompt: NET*ROUTE1=
Enter: network route address
Enter the network route address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
If you enter NONE, go to Step 29; otherwise, continue.
21 Prompt: RT1*NTMSK=
Enter: network route netmask address
Enter the network route netmask address in the format of xxx.xxx.xxx.xxx, where xxx
is 0-255.
22 Prompt: NET*ROUTE2=
Enter: network route address
Enter the network route address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
23 Prompt: RT2*NTMSK=
Enter: network route netmask address
Enter the network route netmask address in the format of xxx.xxx.xxx.xxx, where xxx
is 0-255.
24 Prompt: NET*ROUTE3=
Enter: network route address
Enter the network route address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
If you enter NONE, go to Step 28; otherwise, continue.
25 Prompt: RT3*NTMSK=
Enter: network route netmask address
Enter the network route netmask address in the format of xxx.xxx.xxx.xxx, where xxx
is 0-255.
26 Prompt: NET*ROUTE4=
Enter: network route address
Enter the network route address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
If you enter NONE, go to Step 28; otherwise, continue.
27 Prompt: RT4*NTMSK=
Enter: network route netmask address
Enter the network route netmask address in the format of xxx.xxx.xxx.xxx, where xxx
is 0-255.
28 Prompt: GWY*ROUTER=
Enter: network gateway router address
Enter the network gateway router address in the format of xxx.xxx.xxx.xxx, where xxx
is 0-255.
32 Prompt: >
Enter: REMOVE PROCES xxxx y z N
where xxxx is CCM, IPLK, IPUA, or PXP
If the COMMAND COMPLETED - UNIT Y CONFIGURATION SUCCESSFUL message is
displayed (where Y is the processor number and Z is the pair ID), manual removal of the
processor was successful.
33 Prompt: >
Enter: REMOVE PROCES xxxx y z B
where xxxx is CCM, IPLK, IPUA, or PXP
If the COMMAND COMPLETED - UNIT Y CONFIGURATION SUCCESSFUL message is
displayed (where Y is the processor number and Z is the pair ID), manual removal of the
processor was successful.
Restore processor
34 Prompt: >
Enter: RESTOR PROCES xxxx y z I
where xxxx is CCM, IPLK, IPUA, or PXP
If the COMMAND COMPLETED - UNIT Y CONFIGURATION SUCCESSFUL message is
displayed (where Y is the processor number and Z is the pair ID), restore of the
processor was successful. The COMM 88 IPR is issued.
To continue configuring SS7-IP interworking using M2PA, go to SS7 over IP using M2PA,
or refer to SS7-IP interworking order of input to see which procedure(s) to do next.
To continue configuring SS7-IP interworking using M3UA, go to SS7 over IP using M3UA,
or refer to SS7-IP interworking order of input to see which procedure(s) to do next.
END PROCEDURE
Constraints
Procedure
BEGIN PROCEDURE
Note: Collect the local IP addresses, netmask, and remote IP addresses before starting
the procedure. A default route is not required if all IPLK traffic stays within a single
subnet.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: CHANGE HOSTS FILE
2 Prompt: LOCAL*REMOTE*ENTITY=
Enter: [LOCAL, L, REMOTE, or R]
If you enter REMOTE or R, go to Step 10; otherwise, continue.
3 Prompt: LOCAL*IP*ENTITY=
Enter: [PROCESSOR, P, CCMALIAS, or A]
If you enter CCMALIAS or A, the system shows the local IP address parameters; go to
Step 11.
Otherwise, continue.
4 Prompt: PROC*SUB=
Enter: [CCM, IPLK, IPUA, or PXP]
If you enter CCM, go to Step 9.
If you enter IPLK, go to Step 5.
If you enter IPUA, go to Step 6.
If you enter PXP, go to Step 7.
5 Prompt: PROC*NUM=
Enter: [0-63]
Go to Step 8.
6 Prompt PROCNUMBER=
Enter: [0-47]
Go to Step 8.
7 Prompt: PROCESSOR*NUM=
Enter: [0-11]
Enter the processor number for the PXP.
Go to Step 9.
8 Prompt: PORT*ID=
Enter: [1 or 2]
Go to Step 12.
9 Prompt: PAIR*ID=
Enter: [A or B]
A (displays the parameters of host file with pair ID A)
B (displays the parameters of host file with pair ID B)
Go to Step 11.
10 Prompt: REMOTE*IP*ENTITY=
Enter: [NTPSERVER or N]
The system shows the remote IP address parameters.
11 Prompt: NEW*IP*ADDR=
Enter: IP address
Enter the new IP address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
If you entered R in Step 2 or A in Step 3, the system shows the IP address parameters,
go to Step 23; otherwise, continue.
12 Prompt: NEW*NET*ADDR=
Enter: netmask address
Enter the new netmask address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
13 Prompt: NEW*DFT*ROUTER=
Enter: default router address
Enter the new default router address in the format of xxx.xxx.xxx.xxx, where xxx is
0-255.
If you entered CCM or PXP in Step 4, the system shows the local IP address parameters.
Go to Step 23; otherwise, continue.
14 Prompt: NEW*NET*ROUTE1=
Enter: new network route address
Enter the new network route address in the format of xxx.xxx.xxx.xxx, where xxx is
0-255.
15 Prompt: NEW*RT1NTMSK=
Enter: new network route netmask address
Enter the new network route netmask address in the format of xxx.xxx.xxx.xxx, where
xxx is 0-255.
16 Prompt: NEW*NET*ROUTE2=
Enter: new network route address
Enter the new network route address in the format of xxx.xxx.xxx.xxx, where xxx is
0-255.
17 Prompt: NEW*RT2NTMSK=
Enter: new network route netmask address
Enter the new network route netmask address in the format of xxx.xxx.xxx.xxx, where
xxx is 0-255.
18 Prompt: NEW*NET*ROUTE3=
Enter: new network route address
Enter the new network route address in the format of xxx.xxx.xxx.xxx, where xxx is
0-255.
19 Prompt: NEW*RT3NTMSK=
Enter: new network route netmask address
Enter the new network route netmask address in the format of xxx.xxx.xxx.xxx, where
xxx is 0-255.
20 Prompt: NEW*NET*ROUTE4=
Enter: new network route address
Enter the new network route address in the format of xxx.xxx.xxx.xxx, where xxx is
0-255.
21 Prompt: NEW*RT4NTMSK=
Enter: new network route netmask address
Enter the new network route netmask address in the format of xxx.xxx.xxx.xxx, where
xxx is 0-255.
22 Prompt: NEW*GWY*ROUTER=
Enter: new network gateway router address
Enter the new network gateway router address in the format of xxx.xxx.xxx.xxx, where
xxx is 0-255.
26 Prompt: >
Enter: REMOVE PROCES xxxx y z N
where xxx is CCM or PXP.
If the COMMAND COMPLETED - UNIT Y CONFIGURATION SUCCESSFUL message is
displayed (where Y is the processor number and Z is the pair ID), manual removal of the
processor was successful.
27 Prompt: >
Enter: REMOVE PROCES xxxx y z B
where xxx is CCM or PXP.
Restore processor
28 Prompt: >
Enter: RESTOR PROCES xxxx y z I
where xxx is CCM or PXP.
If the COMMAND COMPLETED - UNIT Y CONFIGURATION SUCCESSFUL message is
displayed (where Y is the processor number and Z is the pair ID), manual removal of the
processor was successful. The COMM 88 IPR is issued.
To continue configuring SS7-IP interworking using M2PA, go to SS7 over IP using M2PA,
or refer to SS7-IP interworking order of input to see which procedure(s) to do next.
To continue configuring SS7-IP interworking using M3UA, go to SS7 over IP using M3UA,
or refer to SS7-IP interworking order of input to see which procedure(s) to do next.
END PROCEDURE
Constraints
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: DISPLA HOSTS FILE
2 Prompt: LOCAL*REMOTE*ENTITY=
Enter: [LOCAL, L, REMOTE, R, or ALL]
If you enter ALL, the system shows the local IP address parameters. Go to Step 11.
If you enter LOCAL or L, go to Step 4.
Otherwise, go to Step 3.
3 Prompt: REMOTE*IP*ENTITY=
Enter: [NTPSERVER, N, or ALL]
The system displays the host files parameters; go to Step 11.
4 Prompt: LOCAL*IP*ENTITY=
Enter: [PROCESSOR, P, CCMALIAS, A, or ALL]
If you enter ALL, the system displays the host files of all the processors; go to Step 11.
If you enter PROCESSOR or P, go to Step 5.
If you enter CCMALIAS or A, the system displays the host file parameters; go to Step 11.
5 Prompt: PROC*SUB=
Enter: [CCM, IPLK, IPUA, PXP, or ALL]
If you enter CCM, go to Step 10.
If you enter IPLK, go to Step 6.
If you enter IPUA, go to Step 7.
If you enter PXP, go to Step 8.
If you enter ALL, the system displays the host files parameters of all the processor
subtypes; go to Step 11.
6 Prompt: PROC*NUM=
Enter: [0-63 or ALL]
Enter a single, a range, list of values, or ALL for all the values.
If you enter a processor number, go to Step 9.
If you enter ALL, the system displays the host files parameters; go to Step 11.
7 Prompt PROCNUMBER=
Enter: [0-47 or ALL]
Enter a single, a range, list of values, or ALL for all the values.
If you enter a processor number, go to Step 9.
If you enter ALL, the system displays the host file parameters; go to Step 11.
8 Prompt: PROCESSOR*NUM=
Enter: [0-11]
Enter a single, a range, list of values, or ALL for all the values.
If you enter a processor number; go to Step 10.
If you enter ALL, the system displays the host files parameters; go to Step 11.
9 Prompt: PORT*ID=
Enter: [1, 2, or BOTH]
The system displays the host file parameters, go to Step 11.
10 Prompt: PAIR*ID=
Enter: [A, B, or BOTH]
A (displays the parameters of host file with pair ID A)
B (displays the parameters of host file with pair ID B)
BOTH (displays the parameters of host file with pair ID A and B)
The system displays the host file parameters.
Constraints
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: Whenever changes are made to the hosts file, you must remove and restore the
affected processors to pick up the new hosts file.
1 Prompt: >
Enter: DELETE HOSTS FILE
2 Prompt: LOCAL*REMOTE*ENTITY=
Enter: [LOCAL, L, REMOTE, R, or ALL]
If you enter LOCAL or L, go to Step 3.
If you enter REMOTE or R, go to Step 10.
If you enter ALL, the system shows the local and remote IP address parameters. Go to
Step 12.
The following message is displayed if you enter ALL:
WARNING: ALL THE USER PROVISIONED IP ADDRESSES WILL BE DELETED.
3 Prompt: LOCAL*IP*ENTITY=
Enter: [PROCESSOR, P, CCMALIAS, A, or ALL]
If you enter ALL, the system shows the local IP address parameters. Go to Step 12;
otherwise, continue.
The following message is displayed if you enter ALL:
WARNING: ALL THE USER PROVISIONED IP ADDRESSES WILL BE DELETED.
4 Prompt: PROC*SUB=
Enter: [CCM, IPLK, IPUA, PXP, or ALL]
If you enter CCM, go to Step 9.
If you enter IPLK, go to Step 5.
If you enter IPUA, go to Step 6.
If you enter PXP, go to Step 7.
If you enter ALL, the system shows the IP address parameters of the IPLK and IPUA. Go
to Step 12.
5 Prompt: PROC*NUM=
Enter: [0-63]
Enter processor number for IPLK. Enter single, range, list of values, or ALL for all the
values.
Go to Step 8.
6 Prompt PROCNUMBER=
Enter: [0-47]
Enter processor number for IPUA. Enter single, a range, list of values, or ALL for all the
values.
Go to Step 8.
7 Prompt: PROCESSOR*NUM=
Enter: [0-11]
Enter a single, a range, list of values, or ALL for all the values.
Go to Step 9.
8 Prompt: PORT*ID=
Enter: [1, 2, or BOTH]
The system shows the IP address parameters for the IPLK and IPUA. Go to Step 11.
9 Prompt: PAIR*ID=
Enter: [A, B, or BOTH]
A (displays the parameters of host file with pair ID A)
B (displays the parameters of host file with pair ID B)
BOTH (displays the parameters of host file with pair ID A and B)
The system shows the IP address of the CCM and PXP.
Go to Step 11.
10 Prompt: REMOTE*IP*ENTITY=
Enter: [NTPSERVER, N, or ALL]
The system shows the IP address parameters assigned to NTP server.
14 Prompt: >
Enter: REMOVE PROCES xxxx y z N
where xxxx is CCM, IPLK, IPUA, or PXP
If the COMMAND COMPLETED - UNIT Y CONFIGURATION SUCCESSFUL message is
displayed (where Y is the processor number and Z is the pair ID), manual removal of the
processor was successful.
15 Prompt: >
Enter: REMOVE PROCES xxxx y z B
where xxxx is CCM, IPLK, IPUA, or PXP
If the COMMAND COMPLETED - UNIT Y CONFIGURATION SUCCESSFUL message is
displayed (where Y is the processor number and Z is the pair ID), manual removal of the
processor was successful.
Restore processor
16 Prompt: >
Enter: RESTOR PROCES xxxx y z I
where xxxx is CCM, IPLK, IPUA, or PXP
If the COMMAND COMPLETED - UNIT Y CONFIGURATION SUCCESSFUL message is
displayed (where Y is the processor number and Z is the pair ID), restore of the
processor was successful. The COMM 88 IPR is issued.
To continue configuring SS7-IP interworking using M2PA, go to SS7 over IP using M2PA,
or refer to SS7-IP interworking order of input to see which procedure(s) to do next.
To continue configuring SS7-IP interworking using M3UA, go to SS7 over IP using M3UA,
or refer to SS7-IP interworking order of input to see which procedure(s) to do next.
END PROCEDURE
Use the following procedure when you are setting up multiple links with the same or similar
parameters.
Constraints
Data tables
The following data table is changed when IP connection parameters are assigned:
• IP connections (ATY1A)
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: Use the Assign link set procedure if a new link is being configured.
1 Prompt: >
Enter: ASSIGN CCS LINK
2 Prompt: LS*NAMNUM=
Enter: link set name or number
The system shows the links in the link set.
3 Prompt: SLC=
Enter: [0-15]
4 Prompt: L*INK=
Enter: [0-3071]
If the issued link set is not a combined one, go to Step 6; otherwise, continue.
5 Prompt: CSLS=
Enter: signaling link selection
6 Prompt: PSLS=
Enter: signaling link selection
7 Prompt: RPSUB=
Enter: IPLK
Enter the new routing processor subtype.
8 Prompt: RPNUM=
Enter: [0-63]
Enter the new routing processor number.
9 Prompt: ACT*IVATE=
Enter: [YES, NO, Y, or N]
YES or Y (request activation; use this option if you are not going to change
any of the IP parameters later)
NO or N (do not request activation; use this option if you are going to change
any of the IP parameters later)
The system displays the parameters.
Assign IP connectivity
The following constraints apply while assigning the IPCONN:
• The destination IP address at each end should contain the IP address of the other
end.
• When links on each end are being configured, one side uses the well-known port
number for M2PA (3565) as the source port while the other uses a uniquely chosen
local port number as its source port.
• Likewise, the end with the well-known port number for M2PA as its source port
contains the other end’s uniquely chosen local port number as its destination port.
The end with the uniquely chosen local port number for its source port uses the
well-known port number for M2PA as its destination port.
Data tables
The following data table is changed when IP connection parameters are assigned:
• IP connections (ATY1A)
Note: When you configure IP links, the link parameters should remain as defaulted.
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: ASSIGN CCS IPCONN
2 Prompt: LINK=
Enter: [0-3071]
3 Prompt: ADESTIPA*DDRESS=
Enter: destination IP address
Enter the IP address in the format of xxx.xxx.xxx.xxx, where xxx is 0-255.
4 Prompt: ADESTP*ORT=
Enter: [1-65535]
5 Prompt: ASOURCEP*ORT=
Enter: [1-65535]
Constraints
Data tables
The following data tables are affected when IP system parameters are changed:
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: The link has to be assigned to IPLK. To assign a link, use the Assign links to a link
set procedure.
1 Prompt: >
Enter: CHANGE CCS IPLKPA
2 Prompt: L*INK=
Enter: [0-3071]
Enter the link ID.
3 Prompt: PARAGROUP=
Enter: (one of the following choices)
1 (M2PA); perform the subsection Change MTP2 user peer-peer adaptation.
2 (SCTP timing); perform the subsection Change SCTP timing parameters.
3 (SCTP sizing); perform the subsection Change SCTP sizing parameters.
4 (congestion); perform the subsection Change congestion level parameters.
5 (traffic measurement marginal threshold); perform the subsection Change
marginal threshold parameters.
4 Prompt: T1RE*ADY=
Enter: T1 timer ready parameter
5 Prompt: M2PA*T2=
Enter: T2 status alignment parameter
6 Prompt: T3ALGN=
Enter: T3 status proving parameter
7 Prompt: T4NO*RMAL=
Enter: T4 normal proving alignment state timer parameter
8 Prompt: T4EM*RG=
Enter: T4 emergency proving alignment state timer parameter
9 Prompt: M2PAT*6=
Enter: T6 peer to be congested timer parameter
10 Prompt: T7DEL*ACK=
Enter: T7 user data acknowledgment delay timer parameter
11 Prompt: SRTT=
Enter: maximum SRTT value allowed
The system shows the timer parameters.
13 Prompt: SCTP*T1=
Enter: T1 initialization parameter
14 Prompt: SCTPT*2=
Enter: T2 shutdown parameter
15 Prompt: B*DELAY=
Enter: delay allowed for bundling
16 Prompt: IDLE*TIMER=
Enter: delay allowed for RTT calculations timer parameter
17 Prompt: S*TIMER=
Enter: delay allowed for sending SACK timer parameter
18 Prompt: COO*KIE=
Enter: value suggesting an increase in the cookie life span
19 Prompt: MAXHB=
Enter: maximum number of heartbeat misses
The system shows the SCTP timing parameters.
21 Prompt: MIN*SZ=
Enter: minimum bundling message size
22 Prompt: I*SZ=
Enter: inbound message buffer size
23 Prompt: O*SZ=
Enter: outbound message buffer size
24 Prompt: SS*T=
Enter: SCTP slow start threshold value
25 Prompt: CWD=
Enter: congestion control window size
The system shows the SCTP sizing parameters.
Note: The system displays the prompts in Step 27 through Step 35 only if the congestion
parameter for the logical network is set to congestion with levels.
27 Prompt: TXL1AB*AT=
Enter: maximum L1 buffers to transmit congestion abatement
28 Prompt: TXL1ON*SET=
Enter: maximum L1 buffers to transmit congestion onset
29 Prompt: TXL1DI*SCARD
Enter: maximum L1 buffers to transmit congestion discard
30 Prompt: TXL2AB*AT=
Enter: maximum L2 buffers to transmit congestion abatement
31 Prompt: TXL2ON*SET=
Enter: maximum L2 buffers to transmit congestion onset
32 Prompt: TXL2DI*SCARD=
Enter: maximum L2 buffers to transmit congestion discard
33 Prompt: TXL3AB*AT=
Enter: maximum L3 buffers to transmit congestion abatement
34 Prompt: TXL3ON*SET=
Enter: maximum L3 buffers to transmit congestion onset
35 Prompt: TXL3DI*SCARD=
Enter: maximum L3 buffers to transmit congestion discard
Note: The system displays the prompts in Step 36 and Step 37 only if the congestion
parameter for the logical network is set to congestion with priority.
36 Prompt: RXABA*T=
Enter: maximum buffers to receive congestion abatement
37 Prompt: RXONSE*T=
Enter: maximum buffers to receive congestion onset
38 Prompt: RXDISCARD=
Enter: maximum buffers to receive congestion message discard
The system shows the congestion level parameters.
40 Prompt: LINKOO*S=
Enter: M2PA link out-of-service duration
41 Prompt: ASSORETRAN=
Enter: SCTP associated retransmitted chunks
The system shows the traffic measurement marginal threshold parameters.
Constraints
Data tables
The system retrieves data from the MTP link set number (Y45) data table.
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
Note: Perform the Display CCS link status before performing this procedure.
1 Prompt: >
Enter: STATUS SCTP ASSOC
2 Prompt: PRC*SUBT=
Enter: IPLK
3 Prompt: IPLK*PRC*NUM=
Enter: [0-63]
Enter the processor number.
4 Prompt: REF*RESH=
Enter: [YES, NO, Y, N, R, or NR]
If you enter N, NO, or NR, go to Step 6; otherwise, continue.
The default is NO.
5 Prompt: FREQ*UENC=
Enter: [5-255]
The default is 5 seconds.
Constraints
Data tables
The following data tables are affected when IP system parameters are copied:
Procedure
BEGIN PROCEDURE
Note: The link has to be assigned to IPLK. To assign a link, use the Assign links to a link
set procedure.
1 Prompt: >
Enter: COPY CCS IPLKPA
2 Prompt: L*INK=
Enter: [0-3071]
3 Prompt: LINKNODEST=
Enter: destination link ID
Constraints
Data tables
The system retrieves IP connection parameters from the following data tables:
Procedure
BEGIN PROCEDURE
Note: The link has to be assigned to IPLK. To assign a link, use the Assign links to a link
set procedure.
1 Prompt: >
Enter: DISPLAY CCS IPLKPA
2 Prompt: L*INK
Enter: [0-3071]
3 Prompt: DPARAGROUP=
Enter: (one of the following choices)
0 (ALL groups)
1 (M2PA)
2 (SCTP timing)
3 (SCTP sizing)
4 (congestion)
5 (TMM threshold)
Constraints
Data tables
The following data table is affected when IP system parameters are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE CCS IPSYSP
The system displays the parameters.
2 Prompt: WIN*SIZE=
Enter: advertised receiver window size
3 Prompt: MEM*ORY=
Enter: total memory allocated for the SCTP stack
4 Prompt: INIT*RTO=
Enter: initial retransmission timeout
5 Prompt: MIN*RTO=
Enter: minimum retransmission timeout
6 Prompt: MAX*RTO=
Enter: maximum retransmission timeout
7 Prompt: COOK*LIF=
Enter: valid cookie life
The system shows the IP system parameters.
Constraints
Data tables
The system retrieves IP system parameters from the following data table:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS IPSYSP
BEGIN PROCEDURE
1 Prompt: >
Enter: DEACTI CCS LINK
2 Prompt: L*INK=
Enter: link ID
The following message appears when the link is deactivated:
DISK ENTRY AND PROCESSOR(S) UPDATED
3 Prompt: L*INK=
Enter: <CTRL+A>
4 Prompt: >
Enter: ACTIVA CCS LINK
5 Prompt: L*INK=
Enter: link ID
6 Prompt: DISTRIBUTE=
Enter: Y
7 Prompt: L*INK=
Enter: <CTRL+A>
END PROCEDURE
An application server consists of one or more ASPs. In the initial phase, one ASP serves one
application server. A subsequent phase will allow an ASP to serve one or more application
servers. An application server is a logical entity serving a specific set of SS7 traffic identified
by a routing key. The routing key is DPC initially. An application server process serves as an
active or backup process of an application server.
The M3UA at the 5070 SSG uses the existing SCTP software as the lower layer protocol,
allowing the 5070 SSG to function as the signaling gateway between the SS7 and IP networks.
The following topics provide information about SS7 over IP using M3UA:
• Application server
• Display the SCTP association status of IPUA
• UIP parameters
Application server
Use the following procedures when initially provisioning application server parameters:
Use the following procedures for ongoing administration and maintenance of the application
servers:
Constraints
Data tables
When a new application server is added to the database, the application server (U45) and the
application server name (V45) data tables are updated.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN CCS AS
2 Prompt: ASNAME=
Enter: application server name to be assigned
Enter application server names of 1-16 alphanumeric characters.
3 Prompt: TRAFF*MODE=
Enter: [O, L, or B]
O (override)
L (load sharing)
B (broadcast)
If you enter O, go to Step 6.
If you enter B, go to Step 5.
If you enter L, go to Step 4.
4 Prompt: ACTTHRESH=
Enter: [1-8]
Enter the active threshold number.
5 Prompt: NOTTHRESH=
Enter: [1-8]
Enter the notify threshold number.
6 Prompt: INB*AS=
Enter: [YES, NO, Y, or N]
YES or Y (allow a message to be received from another application server)
NO or N (do not allow a message to be received from another application
server)
Enter the inbound application server allowed flag.
7 Prompt: OUT*AS=
Enter: [YES, NO, Y, or N]
YES or Y (allow a message to be sent to another application server)
NO or N (do not allow a message to be sent to another application server)
Enter the outbound application server allowed flag.
8 Prompt: SUP*DUNA=
Enter: [YES, NO, Y, or N]
YES or Y (suppress DUNA messages from being sent to this AS)
NO or N (do not suppress DUNA messages)
Enter a suppress DUNA broadcast flag.
9 Prompt: PRE*DUNA=
Enter: [YES, NO, Y, or N]
YES or Y (convert a DRST message to a DUNA message)
NO or N (do not convert a DRST message to a DUNA message)
Enter a preventive DUNA flag.
10 Prompt: INS*TFR=
Enter: [YES, NO, Y, or N]
YES or Y (send a TFR due to insufficient active ASPs)
NO or N (do not send a TFR due to insufficient active ASPs)
Enter a insufficient TFR flag.
11 Prompt: DEF*ACTREQ=
Enter: [YES, NO, Y, or N]
YES or Y (use default activation request)
NO or N (do not use default activation request)
Enter the default activation request flag.
The maximum number of ASPs that can be assigned to an IPUA processor is eight, and the
maximum number of ASPs that can be assigned to an AS is eight in the UIP system parameter
database.
Constraints
• The application server name or ID that is being used must exist in the application server
database.
• The IPUA ID must be in the allowed IPUA processor range, but not necessarily equipped.
Data tables
The following data tables are updated when a new application server process is added:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN CCS ASP
2 Prompt: ASPNAME=
Enter: application server process name to be assigned
Enter application server process names of 1-16 characters.
3 Prompt: AS*NAMENUM=
Enter: application server name or number
Enter application server name of 1-16 characters or number.
4 Prompt: RPNUM=
Enter: [0-47]
Enter the routing processor number.
5 Prompt: ACT*IVATE=
Enter: [Y or N]
Enter the activation request of the processor.
6 Prompt: ADESTIPA*DDRESS=
Enter: destination IP address
7 Prompt: ADESTP*ORT=
Enter: [1-65535]
Enter the destination port number.
8 Prompt: ASOURCEP*ORT=
Enter: [1-65535]
Enter the source port number.
9 Prompt: RESTART=
Enter: [Y or N]
Enter the activation request of the application server.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ACTIVATE CCS AS
2 Prompt: AS*ACT=
Enter: application server to be activated
Enter the application server names or ID of 1-16 characters.
Constraints
Data tables
The system reads and updates the ASP (U34) data table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ACTIVATE CCS ASP
2 Prompt: ASP*NAMEID=
Enter: application server process to be activated
Enter application server process names of 1-16 characters or an ID between the range
1-384.
3 Prompt: LAS_ID=
Enter: [0-7]
Enter the logical application server ID.
Enter an ID or ALL for all the logical application server IDs.
4 Prompt: DOWN_LD=
Enter: [Y or N]
Enter download ASP UIP parameters.
Constraints
Data tables
The application server (U45) and the application server name (V45) data tables are updated.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS AS
2 Prompt: ASCHANGE=
Enter: application server name or ID to be changed
Enter application server name of 1-16 alphanumeric characters or ID.
3 Prompt: NASN*AME=
Enter: new application server name
Enter application server name of 1-16 alphanumeric characters.
4 Prompt: TRAFF*MODE=
Enter: [O, L, or B]
O (override)
L (load sharing)
B (broadcast)
If you enter O, go to Step 7.
If you enter B, go to Step 6.
If you enter L, go to Step 5.
5 Prompt: ACTTHRESH=
Enter: [1-8]
Enter the active threshold number.
6 Prompt: NOTTHRESH=
Enter: [1-8]
Enter the notify threshold number.
7 Prompt: INB*AS=
Enter: [YES, NO, Y, or N]
YES or Y (allow a message to be received from another application server)
NO or N (do not allow a message to be received from another application
server)
Enter the inbound application server allowed flag.
8 Prompt: OUT*AS=
Enter: [YES, NO, Y, or N]
YES or Y (allow a message to be sent to another application server)
NO or N (do not allow a message to be sent to another application server)
Enter the outbound application server allowed flag.
9 Prompt: SUP*DUNA=
Enter: [YES, NO, Y, or N]
YES or Y (suppress DUNA messages from being sent to this AS)
NO or N (do not suppress DUNA messages)
Enter a suppress DUNA broadcast flag.
10 Prompt: PRE*DUNA=
Enter: [YES, NO, Y, or N]
YES or Y (convert a DRST message to a DUNA message)
NO or N (do not convert a DRST message to a DUNA message)
Enter a preventive DUNA flag.
11 Prompt: INS*TFR=
Enter: [YES, NO, Y, or N]
YES or Y (send a TFR due to insufficient active ASPs)
NO or N (do not send a TFR due to insufficient active ASPs)
Enter a insufficient TFR flag.
12 Prompt: DEF*ACTREQ=
Enter: [YES, NO, Y, or N]
YES or Y (use default activation request)
NO or N (do not use default activation request)
Enter the default activation request flag.
13 Prompt: ACT*REQLASK=
Enter: [YES, NO, Y, or N]
YES or Y (use activation request per LAS parameter)
NO or N (do not use activation request per LAS parameter)
Enter the activation request per logical application server.
Constraints
• The application server name or ID that is being used should exist in the application server
database.
• ASPs assigned to the particular AS should be deleted first before deleting the AS.
• If an AS is assigned to the route set master, you cannot delete the last ASP assigned to the
AS unless you delete the AS assignment to the route set master.
Data tables
The application server (U45) and the application server name (V45) data tables are updated.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: Delete the ASPs assigned to the AS before performing this procedure.
1 Prompt: >
Enter: DELETE CCS AS
2 Prompt: ASDEL=
Enter: application server to be deleted
Enter application server names or IDs of 1-16 characters.
Constraints
Data tables
The system reads the application server (U45) and the application server name (V45) data
table to show the data.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS AS
2 Prompt: ASDISP=
Enter: application server to be displayed
Enter application server names or ID of 1-16 characters.
Enter a single name, ID, or ALL for all the application server names and IDs.
If you enter name or ID, go to Step 4; otherwise, continue.
3 Prompt: DIS*ORD=
Enter: [N or I]
N (AS name order)
I (AS ID order)
Enter the application server display order.
4 Prompt: FORM*AT=
Enter: [B or D]
B (brief format)
D (detailed format)
Constraints
• The application server process name or ID must exists in the ASP database.
• The application server name or ID that is being used must exist in the AS database.
• The IPUA ID must be in the configured IPUA processor range, but not necessarily equipped.
Data tables
The following data tables are updated when a new application server process is changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE CCS ASP
2 Prompt: ASP_NAMID=
Enter: application server process name or ID to be changed
Enter application server process names of 1-16 characters or the ASP ID.
3 Prompt: ASPNAME=
Enter: new application server process
Enter application server process names of 1-16 characters.
4 Prompt: AS*NAMEID=
Enter: application server name or ID
Enter application server names of 1-16 characters or the AS ID.
5 Prompt: RPNUM=
Enter: [0-47]
6 Prompt: ACT*IVATE=
Enter: [Y or N]
Enter the activation request of the processor.
7 Prompt: ADESTIPA*DDRESS=
Enter: destination IP address
8 Prompt: ADESTP*ORT=
Enter: [1-65535]
Enter the destination port number.
9 Prompt: ASOURCEP*ORT=
Enter: [1-65535]
Enter the source port number.
10 Prompt: RESTART=
Enter: [Y or N]
Enter the activation request of the application server.
Constraints
• The application server process name or ID must exist in the ASP database.
Data tables
The following data tables are updated when a new application server process is changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE CCS ASP
2 Prompt: ASPNAMID=
Enter: application server process name or ID to be deleted
Enter application server names or IDs of 1-16 characters.
3 Prompt: RESTART=
Enter: [Y or N]
Enter the activation request of the application server.
Constraints
The application server process name or ID must exist in the ASP database.
Data tables
The system reads the ASP (U34) and ASP name (V34) data tables to show the data.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS ASP
2 Prompt: ASPDISP=
Enter: application server process name or ID to be displayed
Enter application server process names or ID of 1-16 characters.
Enter a single name, ID, or ALL for all the application server process names and IDs.
If you enter name or ID, go to Step 5; otherwise, continue.
<RETURN> to continue.
3 Prompt: PROCID=
Enter: [0-47]
Enter the processor number. Enter a single number, list, range, or ALL for all the
processor numbers.
4 Prompt: DIS*ORD=
Enter: [N or I]
N (ASP name order)
I (ASP ID order)
P (Proc ID order)
Enter the application server process display order.
5 Prompt: FORM*AT=
Enter: [B or D]
B (brief format)
D (detailed format)
Enter the application server process display format.
Constraints
The application server name or ID must exist and be activated in the AS database.
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DEACTIVATE CCS AS
2 Prompt: AS*DEACT=
Enter: application server to be deactivated
Enter application server names or ID of 1-16 characters.
Constraints
Data tables
The system reads the AS (U45) and AS name (V45) data tables to display the status.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: STATUS CCS AS
2 Prompt: AS*STAT=
Enter: application server to be displayed
Enter application server names or ID of 1-16 characters.
Enter a single name, ID, or ALL for all the application server names and IDs.
If you enter name or ID, go to Step 4; otherwise, continue.
3 Prompt: DIS*ORD=
Enter: [N or I]
N (AS name order)
I (AS ID order)
Enter the application server display order.
4 Prompt: REF*RESH=
Enter: [YES, NO, Y, N, R, or NR]
YES, Y, or R (allow the refresh required flag)
NO, N, or NR (do not allow the refresh required flag)
If you enter N, NO, or NR, go to Step 6; the AS status is displayed. Otherwise, continue.
Enter the refresh flag.
5 Prompt: FREQ*UENC=
Enter: [5-240]
Enter the refresh frequency in seconds.
6 To display the status of another application server name or ID, go to Step 2; otherwise,
continue.
Constraints
The ASP name or ID must exist and be activated in the ASP database.
Data tables
The system reads and updates the ASP (U34) data table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DEACTIVATE CCS ASP
2 Prompt: ASP*NAMEID=
Enter: application server process to be activated
Enter application server process names of 1-16 characters or an ID between the range
1-384.
3 Prompt: LAS_ID=
Enter: [0-7]
Enter the logical application server ID.
Enter an ID or ALL for all the logical application server IDs.
Constraints
Data tables
The system reads the ASP (U34) and ASP name (V34) data tables to display the status.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: STATUS CCS ASP
2 Prompt: ASP*NAMID=
Enter: application server process name or ID to be displayed
Enter application server process names or ID of 1-16 characters.
Enter a single name, ID, or ALL for all the application server process names and IDs.
If you enter ALL, go to Step 4.
If you enter ASP name or ID, go to Step 5.
<RETURN> to continue.
3 Prompt: PROCID=
Enter: [0-47]
Enter the processor number. Enter a single number, range, list, or ALL for all the
processor numbers.
4 Prompt: DIS*ORD=
Enter: [N or I]
N (ASP name order)
I (ASP ID order)
P (Proc ID order)
Enter the application server process display order.
5 Prompt: REF*RESH=
Enter: [YES, NO, Y, N, R, or NR]
YES, Y, or R (allow the refresh required flag)
NO, N, or NR (do not allow the refresh required flag)
If you enter N, NO, or NR, go to Step 7; the ASP status is displayed. Otherwise,
continue.
Enter the refresh flag.
6 Prompt: FREQ*UENC=
Enter: [5-240]
Enter the refresh frequency in seconds.
7 To display the status of another application server process name or ID, go to Step 2;
otherwise, continue.
Constraints
Data tables
The system retrieves data from the MTP link set number (Y45) data table.
Procedure
BEGIN PROCEDURE
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: STATUS SCTP ASSOC
2 Prompt: PRC*SUBT=
Enter: IPUA
3 Prompt: IPUA*PRC*NUM=
Enter: [0-47]
Enter the processor number.
4 Prompt: REF*RESH=
Enter: [YES, NO, Y, N, R, or NR]
If you enter N, NO, or NR, go to Step 6; otherwise, continue.
The default is NO.
5 Prompt: FREQ*UENC=
Enter: [5-255]
The default is 5 seconds.
UIP parameters
Use the following procedure when initially provisioning UIP parameters:
Use the following procedures only if you must change the default UIP settings.
Use the following procedures for ongoing administration and maintenance of the UIP
parameters:
Constraints
Data tables
The system displays audit processing messages during audit execution and an execution
summary at the end of the audit. The audit is performed on the information in the AS, ASP,
and M3UA UIP data tables.
Procedure
BEGIN PROCEDURE
! ALERT
ALERT! Contact your next level of support before changing any UIP default settings.
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: AUDIT UIP DATABA
The following message is displayed:
**************************************************
* *
* SS7 UIP DATABASE AUDIT *
* *
**************************************************
INITIALIZING STATISTICS
STATISTICAL SUMMARY
===================
+-------------------------------------------------------------------+
| | | Utilization | Audit Results |
| File | Entity Set | Max. Total %Full | Error Warn Fixed |
+-------------------------------------------------------------------+
| ATU45 | AS | 129 4 3.1% | |
| ATV45 | AS Name | 129 4 3.1% | |
| ATU34 | ASP | 384 7 1.8% | |
| ATV34 | ASP Name | 384 7 1.8% | |
| ATU31 | UIP Timers | 3 3 100.0% | |
| ATY51 | Route Set Mster | 600 4 0.6% | |
+-------------------------------------------------------------------+
| Totals | 1629 29 1.7% | N/A N/A N/A |
+-------------------------------------------------------------------+
THIS IS A SUMMARY OF DATABASE UTILIZATION.
**************************************************
* *
* SS7 UIP DATABASE AUDIT *
* *
**************************************************
INITIALIZING STATISTICS
CHECKING AS TABLES
STATISTICAL SUMMARY
===================
+-------------------------------------------------------------------+
| | | Utilization | Audit Results |
| File | Entity Set | Max. Total %Full | Error Warn Fixed |
+-------------------------------------------------------------------+
| ATU45 | AS | 129 4 3.1% | 0 0 0 |
| ATV45 | AS Name | 129 4 3.1% | 0 0 0 |
| ATU34 | ASP | 384 7 1.8% | 0 0 0 |
| ATV34 | ASP Name | 384 7 1.8% | 0 0 0 |
| ATU31 | UIP Timers | 3 3 100.0% | 0 0 0 |
| ATY51 | Route Set Mster | 600 4 0.6% | 0 0 0 |
+-------------------------------------------------------------------+
| Totals | 1629 29 1.7% | 0 0 0 |
+-------------------------------------------------------------------+
YOUR DATABASE IS VERY GOOD
Constraints
Data tables
The system updates the M3UA UIP parameter (V49) data table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE CCS UIPPAR
2 Prompt: ASP*NAMNUM=
Enter: application server process name or number
Enter an application server process name of 1-16 characters or an ID between the range
1-384.
3 Prompt: PARAGROUP=
Enter: (one of the following choices)
1 (SCTP timing); go to Step 4.
2 (SCTP sizing); go to Step 11.
3 (Congestion); go to Step 16.
4 (Traffic measurement marginal threshold); go to Step 28.
5 (All the above groups); go to Step 4.
Enter the parameter group. The parameter group is displayed.
4 Prompt: SCTP*T1=
Enter: [0-65535]
Enter the SCTP timer T1.
5 Prompt: SCTP*T2=
Enter: [0-65535]
Enter the SCTP timer T2.
6 Prompt: B*DELAY=
Enter: [0-65535]
7 Prompt: IDLE*TIMER=
Enter: [0-65535]
8 Prompt: S*TIMER=
Enter: [0-65535]
Enter the sack timer.
9 Prompt: COO*KIE=
Enter: [0-65535]
Enter the cookie preservative.
10 Prompt: MAXHB=
Enter: [1-100]
Enter the maximum heart beat misses.
If you entered 1 in Step 3, go to Step 30; otherwise, continue.
11 Prompt: MIN*SZ=
Enter: [0-65535]
Enter the minimum building message size.
12 Prompt: I*SZ=
Enter: [0-4294967295]
Enter the inbound buffer message.
13 Prompt: O*SZ=
Enter: [0-4294967295]
Enter the outbound buffer message.
14 Prompt: SS*T=
Enter: [0-65535]
Enter the slow start threshold.
15 Prompt: CWD=
Enter: [0-4294967295]
16 Prompt: TXL1AB*AT=
Enter: [0-100]
Enter the TX congestion L1 abatement.
17 Prompt: TXL1ON*SET=
Enter: [0-100]
Enter the TX congestion L1 onset.
18 Prompt: TXL1DI*SCARD=
Enter: [0-100]
Enter the TX congestion L1 discard.
19 Prompt: TXL2AB*AT=
Enter: [0-100]
Enter the TX congestion L2 abatement.
20 Prompt: TXL2ON*SET=
Enter: [0-100]
Enter the TX congestion L2 onset.
21 Prompt: TXL2DI*SCARD=
Enter: [0-100]
Enter the TX congestion L3 discard.
22 Prompt: TXL3AB*AT=
Enter: [0-100]
Enter the TX congestion L3 abatement.
23 Prompt: TXL3ON*SET=
Enter: [0-100]
Enter the TX congestion L2 onset.
24 Prompt: TXL3DI*SCARD=
Enter: [0-100]
Enter the TX congestion L3 discard.
25 Prompt: RXABA*T=
Enter: [0-100]
Enter the receive congestion abatement.
26 Prompt: RXONSE*T=
Enter: [0-100]
Enter the receive congestion onset.
27 Prompt: RXDISCARD=
Enter: [0-100]
Enter the receive congestion L2 discard. Go to Step 30.
If you entered 3 in Step 3, go to Step 30; otherwise, continue.
28 Prompt: ASSDOWNTRAN=
Enter: [1-65535]
Enter the SCTP association down duration threshold.
29 Prompt: ASSORETRAN=
Enter: [1-65535]
Enter the SCTP association retransmission threshold.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE CCS UIPSYS
The system displays the UIP system parameters.
2 Prompt: WIN*SIZE=
Enter: [0-1,000,000]
Enter the new advertised receiver window size in bytes.
3 Prompt: MEM*ORY=
Enter: [0-1,000,000,000]
Enter the new total memory allocated for the SCTP stack in bytes.
4 Prompt: INIT*RTO=
Enter: [0-65,535]
Enter the new initial retransmission time-out in milliseconds.
5 Prompt: MIN*RTO=
Enter: [0-65,535]
Enter the new minimum retransmission time-out in milliseconds.
6 Prompt: MAX*RTO=
Enter: [0-65,535]
Enter the new maximum retransmission time-out in milliseconds.
7 Prompt: COOK*LIF=
Enter: [0-120,000]
Enter the new valid cookie life in milliseconds.
Constraints
Data tables
The system updates the M3UA UIP system timer (U31) data table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE CCS UIPTMR
The system displays the UIP timer parameters.
2 Prompt: TIMER*TYPE=
Enter: (one of the following choices)
1 (T (r) timer); go to Step 3.
2 (T (scon) timer); go to Step 5.
3 (T (tcp) timer); go to Step 7.
4 (T (act) timer); go to Step 9.
3 Prompt: R*SECONDS=
Enter: [0 or 1]
Enter the number of seconds for T (r) timer.
4 Prompt: R*TENTHS=
Enter: [0-9]
Enter the number of tenths of seconds for T (r) timer. Go to Step 10.
5 Prompt: S*SECONDS=
Enter: [1, 2, or 3]
Enter the number of seconds for T (scon) timer.
6 Prompt: S*TENTHS=
Enter: [0-9]
Enter the number of tenths of seconds for T (scon) timer. Go to Step 10.
7 Prompt: T*SECONDS=
Enter: [0 or 1]
Enter the number of seconds for T (tcp) timer.
8 Prompt: T*TENTHS=
Enter: [0-9]
Enter the number of tenths of seconds for T (tcp) timer.
9 Prompt: A*SECONDS=
Enter: [1-60]
Enter the number of seconds for T(act) timer.
Constraints
Data tables
The system updates the M3UA UIP parameter (V49) data table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: COPY CCS UIPPAR
2 Prompt: A*SP=
Enter: [1-384]
Enter application server process ID.
3 Prompt: ASPNODEST=
Enter: [1-384]
Enter destination application server process ID.
Enter a single ID, list of IDs, range, or combination of IDs.
Constraints
Data tables
The system reads the ASP UIP parameter (V49) data table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY CCS UIPPAR
2 Prompt: ASP*NAMNUM=
Enter: application server process name or number
Enter an application server process name of 1-16 characters or an ID between the range
1-384.
3 Prompt: DPARAGROUP=
Enter: (one of the following choices)
0 (All groups)
1 (SCTP timing)
2 (SCTP sizing)
3 (Congestion)
4 (Traffic measurement marginal threshold)
Enter the parameter group. The parameter group is displayed.
The display fields vary based on the parameter group selected in Step 3.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY CCS UIPSYS
Constraints
Data tables
The system updates the UIP system timer (U31) data table.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY CCS UIPTMR
A route set master number identifies a group of link sets that constitute a route from the local
node to a distant node.
A route set master identifies as many as six link sets. Each link set is assigned a priority level
(1, 2, or 3). The priority determines the order in which the link sets are activated. Only two
link sets in a route are active at a time. Only two link sets are assigned the same priority in the
route set at one time.
Constraints
These constraints apply to adding a link set or application server to a route set master:
• The AS ID must be an application server that has been created and not be used in any
route set master.
Data tables
When a new route set master is added to the database, the route set master (Y51) data table is
changed.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN CCS RSMAST
2 Prompt: ROUT*ESET=
Enter: route set to be added
3 Prompt: LS*CAT=
Enter: (one of the following choices)
S (super link set); go to Step 5.
N (normal link set); go to Step 4.
AS (application server); go to Step 6.
4 Prompt: LINKS*ET=
Enter: a link set name or number
Go to Step 7.
5 Prompt: SUPERLS*NUM=
Enter: a super link set number
Go to Step 7.
6 Prompt: APPS*SER=
Enter: an application server name or number
7 Prompt: PRI*ORITY=
Enter: priority number
The system shows the link sets and other values assigned to this route set.
Constraints
These constraints apply to changing a link set or application server in a route set master:
• Two link sets in a route set master may be assigned the same priority level. A direct link
set (terminating at a specified node) should be assigned a higher priority than an indirect
link set (terminating at an intermediate node such as the mate 5070 SSG). However, if a
super link set is used as a route in a route set master, then that must be the only route
with that priority level. (Super link set: For future use.)
• A link set must have at least one link to be assigned to a route set.
• If two link sets are to be assigned the same priority, and one of them is combined, they
must all be combined.
• Link sets must be defined before assigning a route set master.
• All the link sets assigned to one route set master must be of the same logical network.
• The AS ID must be an application server that has been created and not be used in any
route set master.
Data tables
When an existing route set master is changed, the route set master (Y51) data table is
changed.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS RSMAST
2 Prompt: ROUT*ESET=
Enter: route set to be changed
3 Prompt: LS*CAT=
Enter: (one of the following choices)
S (super link set); go to Step 5.
N (normal link set); go to Step 4.
AS (application server); go to Step 6.
4 Prompt: LINKS*ET=
Enter: a link set name or number
Go to Step 7.
5 Prompt: SUPERLS*NUM=
Enter: a super link set number
Go to Step 7.
6 Prompt: APPS*SER=
Enter: a application server name or number
7 Prompt: CLS*CAT=
Enter: [S, N, or AS]
If you enter S, go to Step 8.
If you enter N, go to Step 9.
If you enter AS, go to Step 10.
If you enter S in Step 3 and <RETURN> in Step 7; go to Step 8.
8 Prompt: CSUPERLS*NUM=
Enter: new super link set number
Go to Step 11.
9 Prompt: CLINKS=
Enter: new link set name
Go to Step 11.
10 Prompt: CAPPS*SER=
Enter: new application server name or number
11 Prompt: CPRIOR=
Enter: (one of the following choices)
A new priority level
<RETURN> (keep the same priority level)
The system shows the link sets and other parameters.
Constraints
These constraints apply to removing a route set master from the SS7 database:
• When a route set master number is deleted, the 5070 SSG can no longer route traffic to
any node served by that route.
Data tables
The system changes the route set master (Y51) table when an existing route set master is
deleted.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE CCS RSMAST
2 Prompt: ROUT*ESET=
Enter: route set to be deleted
3 Prompt: DLS*CAT=
Enter: (one of the following choices)
S (super link set); go to Step 5.
N (normal link set - default); go to Step 4.
AS (application server); go to Step 6.
<RETURN>; go to Step 7.
4 Prompt: LINKS*ET=
Enter: a link set name or number
Go to Step 7.
5 Prompt: SUPERLS*NUM=
Enter: a super link set number
Go to Step 7.
6 Prompt: APPS*SER=
Enter: a application server name or number
7 Prompt: DLINKS=
Enter: link set name, number, or ALL
Constraints
Data tables
The system reads the route set master (Y51) data table to show the data.
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS RSMAST
2 Prompt: DROUT*SE=
Enter: (one of the following choices)
A route set number
ALL
The system shows the link sets assigned to the route and their priority levels.
Routing
• Member (full point code) routing - routes messages based on the network number, cluster
number, and cluster member number of the DPC
• Cluster (partial point code) routing - routes messages based on the network number and
cluster number of the DPC
The system performs member routing by assigning a route set master to the point code. A
route set master is a grouping of all link sets that carry traffic from the 5070 SSG to a distant
node.
The route set master includes the link sets that terminate at the node and any other link set
transferring messages to the node. All routes include the link set to the mate 5070 SSG. If the
primary link set to the node is inaccessible, the message traffic is forwarded through the mate
5070 SSG.
Note: If both member routing and cluster routing functions are assigned to a node, the 5070
SSG uses member routing.
• Routing procedures
• Destination point code route sets
Routing procedures
You can perform the following routing tasks procedures:
• Establish routing
• Delete routing for nonadjacent point codes
• Delete routing for adjacent point codes
Establish routing
Use this procedure to establish MTP routing.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Add one or more link sets to a route set master (Route set master form).
2 Add a route.
END PROCEDURE
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 If the point code is used as a destination for GTT, remove it from the GTT tables.
2 If the point code is part of a subsystem or point code address assigned to a CSP group,
remove the concerned point code.
3 If the point code is a member of a CSP group, remove the point code from the group.
4 If the point code is assigned as a mated application, remove it from the mated
application tables.
5 If the point code is assigned a subsystem name, remove the subsystem name.
6 Remove the routing for this point code by deleting the ordered route.
END PROCEDURE
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 If the point code is used as a destination for GTT, remove it from GTT and from the GTT
tables.
2 If the point code is part of a subsystem or point code address assigned to a CSP group,
remove the concerned point code.
3 If the point code is a member of a CSP group, remove the point code from the group.
4 If the point code is assigned as a mated application, remove it from the mated
application tables.
5 If the point code is assigned as a subsystem name, remove the subsystem name.
6 Remove the routing for this point code by deleting the ordered route.
7 Remove the link set terminating in the adjacent node from any route set master in
which it appears.
The mate 5070 SSG is usually included in each route set because it can transmit messages to
the distant node if the direct link set fails.
Constraints
• All routes originate at the 5070 SSG. Each route must terminate at a distant node.
• If the cluster routing feature is enabled, a node can have member routing or cluster
routing.
• If both member routing and cluster routing are assigned to a node, then member routing
must be used.
• The route set master number must be assigned before assigning the route to the ordered
route. When routes are created, a route set master of zero is automatically assigned.
• If the node is a final destination for GTT, routing must be assigned to the node.
• The DPC router set does not allow a route set master that contains an application server
to be referenced by more than one point code.
Data tables
When a new route is added to the database, the following data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN CCS DPCRS
2 Prompt: ANO*DE=
Enter: a node name
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters associated with the distant node.
5 Prompt: ARS*MASTER=
Enter: route set master number
Constraints
• Assign the route set master number before assigning the route to the ordered route. When
routes are created, a route set master of zero is automatically assigned.
• A point code cannot be modified in the DPC to route set data table (Y52) if the point code
is used in the point code and SSN table (W53). The parameters of the point code can be
modified.
• If the node appears in the adjacent node name data table (S27), the node name must be
changed there before the node name can be modified in the node name table (Y55).
• The DPC router set does not allow a route set master that contains an application server to
be referenced by more than one point code.
Data tables
When parameters of an existing route are changed, the following data tables are changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS DPCRS
2 Prompt: NODE=
Enter: (one of the following choices)
A node name; go to Step 5. The system shows the current node.
<RETURN>; continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters associated with the distant node.
5 Prompt: CNODE=
Enter: a new node name
If the node is adjacent, go to Step 9; otherwise, continue.
6 Prompt: CLOG*NET=
Enter: logical network name or number
7 Prompt: CPNT*COD=
Enter: point code
8 Prompt: CRS*MASTER=
Enter: [A or C]
A (route set master number)
C (route set number)
The route set master is a number identifying the group of link sets making up the route.
Go to Step 10.
9 Prompt: RS*MASTER=
Enter: route set master number
Constraints
The following constraints apply to removing an ordered route from the SS7 database:
• Deactivate all link sets in the route set before deleting a route.
• To remove an adjacent node, delete the link set to the node before removing the route.
Deleting a link set terminates traffic on the links.
• A point code cannot be deleted from the DPC to route set data table (Y52) and the node
name data table (Y55) if it is used in the multiple point code and SSN data table (W53).
• If a nonadjacent node is removed, remove the route, but do not delete the link sets to the
node. The link sets may also serve an intermediate node adjacent to the 5070 SSG.
• If a node is defined as a GTT address, CSP code, or mated application, the route to that
node cannot be deleted. The SCCP definitions must be deleted before deleting the route.
• A point code cannot be deleted from the DPC to route set data table (Y52) and the node
name data table (Y55) if it is defined as a DEN point code in the PCM database.
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE CCS DPCRS
2 Prompt: NODE=
Enter: (one of the following choices)
A node name; the system shows parameters. Go to Step 5.
<RETURN>; continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters of the member to be deleted.
Constraints
Data tables
The parameters showed are retrieved from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS DPCRS
2 Prompt: NODE=
Enter: (one of the following choices)
A node name; go to Step 5.
ALL; go to Step 5.
<RETURN>; continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
SCCP subsystem
The SS7 database contains configuration information on all subsystems that receive 5070 SSG
messages. A subsystem is identified in the database by any of these forms:
• Subsystem name
• Node name and SSN
• Point code and SSN
Each subsystem identified in the SS7 database has a unique name. The subsystem name
identifies both the node where the subsystem resides and the SSN. The name identifies the
subsystem in system output messages.
Reserved subsystems
The SSN is a decimal number in the range 00-255. The SSN identifies a particular subsystem at
the node. The following SSNs are reserved for special applications:
Delete a subsystem
Use this procedure to delete a subsystem name.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
2 Remove the subsystem name if it is a member of a global title destination data group.
3 Remove a CSP if the CSP group assigned to the specified subsystem name.
Subsystem name
The subsystem name form associates a subsystem name with a node name and an SSN or a
point code and an SSN. A subsystem can then be identified by its subsystem name, node name
and SSN, or by point code and SSN.
Constraints
• When SSNs are duplicated in different nodes, the subsystem name must be unique in each
node.
• A subsystem must not be assigned to a point code that is an alias point code.
• The subsystem name must be selected carefully because it represents both the node
where the subsystem resides and the SSN.
Data tables
The system changes the following data tables to add a subsystem name and its characteristics
to the database:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: ASSIGN SCCP SUBSYS
2 Prompt: NEWN*AME=
Enter: subsystem name
3 Prompt: NODE=
Enter: (one of the following choices)
The node name to be added; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for a
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number to be added
7 Prompt: RE*ROUTE=
Enter: [R or D]
R (reroute - default)
D (disable)
Constraints
• When SSNs are duplicated in different nodes, the subsystem name must be unique for each
node.
• The subsystem number cannot be changed if the subsystem is referenced by a global title
or a mated application.
• The subsystem name must be selected carefully because it represents both the node
where the subsystem resides and the SSN.
Data tables
The system accesses the following data tables to change a subsystem name and its
characteristics:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE SCCP SUBSYS
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number to be changed
The system shows the current configuration of the subsystem identified.
7 Prompt: NEWN*AME=
Enter: new subsystem name
8 Prompt: NEWS*UB=
Enter: new subsystem number
9 Prompt: RE*ROUTE=
Enter: [R or D]
R (reroute)
D (disable)
<RETURN> (current value)
Constraints
Data tables
The system accesses the following data tables to delete a subsystem name and its
characteristics:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE SCCP SUBSYS
2 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
3 Prompt: DSUB*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 7.
<RETURN>; continue.
4 Prompt: DNODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN >; continue.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number to be deleted
Constraints
Data tables
The system retrieves SCCP subsystem parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA SCCP SUBSYS
2 Prompt: DSUB*NAME=
Enter: (one of the following choices)
The subsystem name or ALL; go to Step 7.
<RETURN>; continue.
3 Prompt: DNODE=
Enter: (one of the following choices)
The node name; go to Step 6.
ALL; go to Step 7.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: DSUBNO=
Enter: subsystem number or ALL
The system shows the subsystem name and its parameters
SCCP subsystems are manually deactivated and activated during network maintenance for
these purposes:
• To remove the subsystem from service gracefully and reduce traffic loss or thrashing
caused by a remove and restore procedure
• To return subsystems to service in case of an improper response to a SST message, which
leaves the subsystem prohibited
When a subsystem is activated, the database marks the subsystem status as in service,
regardless of the subsystem's actual state. The system does not test a newly activated
subsystem, but simply resumes sending messages to the subsystem.
When a subsystem is deactivated, the database marks the subsystem status as out of service,
regardless of the subsystem's actual state. The system reroutes all messages to that subsystem
to a backup destination if a backup is configured. If there is no backup, the system returns the
message to the sender or discards the message.
The STATUS SCCP SUBSYSTEM command shows a manual out-of-service condition for manually
deactivated subsystems.
Manual deactivation/activation only affects the 5070 SSG where the command is executed.
Constraints
This command accesses the subsystem status data table (Y83) table.
Data tables
The system writes to the following data tables to activate an SCCP subsystem:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ACTIVA SCCP SUBSYS
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: DSUBNO=
Enter: subsystem number or ALL
Constraints
• The 5070 SSG sends routing messages to systems marked as activated, regardless of their
actual state. If the subsystem is not active, the message is lost.
• For correct operation, deactivate a mate 5070 SSG at the same time.
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DEACTI SCCP SUBSYS
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
6 Prompt: DSUBNO=
Enter: subsystem number or ALL
This topics provide information about regular GTT for global titles translated in an SS7 system.
• GTT
• GTT tasks
• Supported GTTs
• TT definition
• GTM definition
• GTT destination definition
• Regular GTT
GTT
Global title
A global title or GTA is an address that can be translated to a point code and subsystem
address for routing. The SS7 database contains the information that the SCCP software uses to
translate the global title to a network address.
For example, an SS7 message that requests 800 service contains the dialed digits for the node
that handles call setup, not the point code of the node. The 5070 SSG translates the global
title and routes the message to the network node that handles 800 service functions. After the
database lookup is completed for the 800 digits, the 5070 SSG routes the call to the destination
node on the voice network for call setup.
GTT
GTT provides routing information for global titles. When the 5070 SSG receives a message
containing a global title in the routing label, the SCCP software translates the global title to a
destination address (point code and SSN) that the MTP software can use to route the message.
The GTT process determines the GTT destination according to TT, GTA digits, DPC, and SSN
availability, and backup mode.
Translation type
In GTT, the TT directs the precise characteristics of the translation process. When the SCCP
receives a message containing a global title, it checks the message for the TT, and the GTA
digits to determine the routing destination for the call. The 5070 SSG supports 256 TTs.
Shared TTs
Some SS7-based services require GTTs that translate to the same destinations residing in an
existing service database. To avoid duplicate databases, a TT can share the GTT database of
the existing TT.
The system can define as many as eight destinations, including backup destinations. The 5070
SSG supports the following backup modes:
Note: In the shared-replicate mode, if a primary node becomes unavailable, the 5070 SSG
redistributes the traffic in equal proportions to a group of backup destination.
The SCCP GTTDEST command provisions the backup mode, destinations, and weight factors for
the translations database.
Route selection
The load-sharing type is selected in the ASSIGN SCCP GTTDEST command at the BKA*MODE
prompt. This command fills as many as eight slots in the GTT multiple PC and SSN data table
(W53) to identify a load-sharing group. The load-sharing type determines the way the
destinations are entered in the table. The load-sharing type also determines the types of
information requested by the command.
The GTT process selects a route to a GTT destination according to TT, GTA digits, DPC/SSN
availability, and backup mode:
• If a single destination is entered, the backup type is solitary. The system accesses the
single destination if it is available.
• If multiple destinations are entered, and the backup type is dominant replicate, the
system records the order in which the destinations are entered. Routing goes first to the
preferred destination and then to the next preferred destination (based on table order).
• If multiple destinations are entered and the backup type is load-shared, routing rotates
among the destinations in the table.
• If multiple destinations are entered and the load-sharing type is weighted load-shared, the
command requires weighting factors. The system sorts the destinations by point code,
subsystem number, and weighting factor.
• If multiple destinations are entered and the load-sharing type is shared replicate, the
command requires identification of primary and backup destinations. Routing accesses the
primary group before accessing the backup group.
The 5070 SSG software can be configured to perform two types of loop detection tests:
• Point code comparison - This test compares the point code of the incoming message with
the point code resulting from the GTT. If the point codes are identical, the message is
eliminated.
• Common route comparison - This test compares the route to the GTT destination after
translation with the route from the originating node. If a priority one route exists that is
common to both, the message is eliminated.
If the common route comparison test is enabled, the point code comparison test is executed
first.
When GTT looping is detected, the system either discards the message if return-on-error is not
specified, or returns a message with the return cause set to No Translation for This Specific
Address.
GTT tasks
The SCCP databases can be provisioned with the following commands:
• SCCP TRANSL
• SCCP GTTDEST
• SCCP GTT
• SCCP PREGTM
• GLOBAL TRANSL
Define a new TT
Use this procedure to establish a new GTT in the database.
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
! ALERT
ALERT! Deleting a final GTT may result in removal of the associated subsystem, subsequent
failures, and possible service interruption.
Note: To delete GTT entries, delete one or more GTA values or ranges assigned to the
TT.
Note: To delete the TT, delete all GTA entries assigned to the TT.
4 To remove the TT, delete the TT entry (this deletes the translation mechanism
assignment).
Supported GTTs
The 5070 SSG supports the GTT of a GTA containing up to 28 digits. GTTs for ported numbers
are supported when the optional LNP feature is installed.
• Single destination
• 800 or toll-free service
• 6- and 10-digit (optional)
• Split end-office CLASS (optional)
• 12- and 15-digit
Six-digit GTT
The 5070 SSG supports GTT for global titles in the form of XXX-XXX, and provides the
requirements for performing GTT for RA0-0/1XX. The six-digit GTT permits full support for
CLASS features and LIDB services.
When the SEAS feature is enabled, provisioning must be made using the corresponding SEAS
local RC&V command.
TT definition
The TT controls processing for global titles in an SS7 message. The TT is carried in the SS7
message with the GTA. When the SS7 message is received at the 5070 SSG, the translation
mechanism assigned to the TT in the database controls the GTT of the GTA.
• Assign a TT
• Change a TT
• Display a TT
• Delete a TT
Assign a TT
Use this procedure to define a new TT by assigning a translation mechanism and related
parameters.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN SCCP TRANSL
2 Prompt: GTF=
Enter: [1-4]
Enter the global title format.
3 Prompt: TRT*YPE=
Enter: [0-255]
Enter the translation type.
4 Prompt: IPRD=
Enter: [YES, NO, Y, or N]
YES or Y (enable GTT failure IPRs)
NO or N (disable GTT failure IPRs)
5 Prompt: LOOP*DET=
Enter: (one of the following GTT loopback detection methods)
1 - None
2 (the point code match)
3 (the common route match)
4 (the network ID match)
6 Prompt: SHR*DTYPE=
Enter: [0-255]
Enter the shared translation type or <RETURN> to specify bypass database sharing.
The system shows the parameters.
Change a TT
Use this procedure to change a TT entry.
Constraints
Data tables
The system changes the GTT-type data table (Y85) and may change the GTT table (W86) to
change a TT entry. The following changes occur:
• Change an old six-digit destination to a new 28-digit destination; this procedure changes
the GTT table during a maintenance window and backs up tables W86 and Y85.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
! ALERT
ALERT! If translation data is currently assigned to the TT, changing the translation mechanism
may result in service interruption. Be sure to update the GTT table for the new translation
mechanism.
Note: Use the DISPLA GLOBAL TRANSL command to verify that no GTAs are assigned to
the TT.
Note: Use the DELETE GLOBAL TRANSL command to remove the translation data
assigned to the TT.
1 Prompt: >
Enter: CHANGE SCCP TRANSL
2 Prompt: GTF=
Enter: [1-4]
Enter the global title format.
3 Prompt: TRT*YPE=
Enter: [0-255]
Enter the translation type to be changed.
4 Prompt: CIPRD=
Enter: [YES, NO, Y, or N]
YES or Y (enable GTT failure IPRs)
NO or N (disable GTT failure IPRs)
5 Prompt: CLOOP*DET=
Enter: (one of the following GTT loopback detection methods)
1 (no detection)
2 (point code match)
3 (common route match)
4 (network ID match)
<RETURN> (keep the current value)
6 Prompt: CSHR*DTYPE=
Enter: [0-255]
Enter the shared translation type to be changed, <RETURN> to specify no change in
shared translation type, or NS to specify bypass database sharing. The system shows the
parameters.
Display a TT
Use this procedure to show a TT entry.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA SCCP TRANSL
2 Prompt: GTF=
Enter: [1-4]
Enter the global title format.
3 Prompt: DSPT*TYP=
Enter: [0-255]
Enter a single translation type, range, list, or ALL for all the translation types.
The system shows the translation type table entry.
Delete a TT
Use this procedure to delete a TT.
Constraints
Data tables
The system changes GTT-type data table (Y85) to remove a TT from the database.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: Use the DISPLA GLOBAL TRANSL command to verify that no GTAs are assigned to
the TT.
Note: Use the DELETE GLOBAL TRANSL command to remove the translation data
assigned to the TT.
1 Prompt: >
Enter: DELETE SCCP TRANSL
2 Prompt: GTF=
Enter: [1-4]
3 Prompt: TRT*YPE=
Enter: [0-255]
The system shows the translation type entry to be deleted.
A destination group includes as many as eight destinations. The backup mode specified
determines the number of destinations that can be entered. The following list defines the GTT
backup modes and applies only to the routing processor destination database.
Mode... Provides...
Solitary No backup; always routes to the PC+SSN configured. A routing failure occurs if
the PC or SSN is unavailable.
Dominant replicate Routes to a backup destination when the primary destination is unavailable.
This mode always translates to the first PC and SSN. If the PC or SSN is
unavailable, the SCCP translates to the second PC and SSN, to as many as
eight destinations.
Load-shared replicate Load sharing between two to eight destinations. Traffic is divided equally
among the available destinations. A routing failure occurs only if all DPCs and
SSNs are unavailable.
Mode... Provides...
Weighted load share Load sharing between two to eight destinations where traffic is allocated
proportionally to the available destinations according to weight factors.
Shared replicate Routes traffic to two or more primary destinations according to weight
factors. If one or more primary destinations becomes unavailable, traffic
routing to those nodes is divided equally among one or more available backup
destinations.
Constraints
• The destination node (name and PC) and associated routing must first be defined in the
database.
• If the backup type is set to load-shared, dominant replicate, or weighted load share, at
least two GTT destinations must be defined.
• If the backup type is set to shared replicate, at least three GTT destinations must be
defined. At least one backup destination must be defined in the group of three.
• In load-shared/replicate mode, backup destinations are provisioned with a weight value of
0.
• For final translations, the subsystem name or number must first be defined in the
database.
Data tables
The following data tables are affected when a GTT destination pair is added:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
Note: AT1LK, CTLK, DS0LK, and SIPM are for future use.
1 Prompt: >
Enter: ASSIGN SCCP GTTDEST
2 Prompt: GTTA*NAME=
Enter: GTT destination group name
Enter GTT destination group name of 1-8 characters.
The default value is none.
3 Prompt: BKA*MODE=
Enter: (one of the following choices)
0 (solitary, or no replicates)
1 (dominant replicate)
2 (load-shared replicate)
3 (weighted load share)
4 (shared replicate)
The default value is 0.
Enter the backup mode.
Go to the step with the prompt that matches your system.
Note: The prompts in Step 4 through Step 10 repeat to allow as many as eight
destinations. Enter QUIT at a FINxx*TRAN prompt to indicate the end of the sequence.
Note: The xx in the FINxx*TRAN prompt and all subsequent prompts identifies the
sequence number of the destination. The system reorders the destinations from highest
to lowest preference according to the weight factors.
4 Prompt: FIN1A*TRAN=
Enter: [YES, NO, Y, or N]
YES or Y (indicate final translation)
NO or N (indicate subsequent translations)
Go to the prompt that follows that matches the one on your system.
5 Prompt: WEIGHT1A=
Enter: (one of the following choices)
1-100 (backup type - weighted load-shared)
0-100 (backup type - shared replicate)
6 Prompt: SS1A*NAME=
Enter: subsystem name
Enter the subsystem name of 1-6 characters.
Go to Step 4 if additional destinations are allowed or Step 11 if no additional
destinations are allowed.
<RETURN> (specify a node and SSN); continue.
7 Prompt: NOD1A*NAME=
Enter: (one of the following choices)
The node name; go to Step 10.
<RETURN> (specify node point code); continue.
8 Prompt: LOGNET1A=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
9 Prompt: PTCODE1A=
Enter: point code
The point code valid range depends on the point code format that is configured for a
lognet.
10 Prompt: SYS1A*NUM=
Enter: (one of the following choices)
An SSN (final translation); go to Step 11.
0 (nonfinal translation); go to Step 4.
11 Verify the data in the GTT destination group table entry. The system reorders the
destination data in highest to lowest preference. In shared-replicate mode, weight
factors are ordered in highest to lowest preference.
Constraints
Data tables
The following data tables are affected when a GTT destination pair is changed:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE SCCP GTTDEST
2 Prompt: GTTD*NAME=
Enter: (one of the following choices)
A GTT destination group name; go to Step 4.
<RETURN> (identify the GTT group number)
3 Prompt: GTC*NUM=
Enter: [1-1125]
Enter the GTT destination group number.
4 Prompt: GTTA*NAME=
Enter: (one of the following choices)
A new GTT destination group name
<RETURN> (keep the current name)
5 Prompt: BKB*MODE=
Enter: (a backup mode from one of the following choices)
0 (solitary, or no replicates)
1 (dominant replicate)
2 (load-shared)
3 (weighted load-shared)
4 (shared replicate)
<RETURN> (keep the current backup mode)
Go to the step with the prompt that matches your system.
6 Prompt: MENU1A*GTT=
Enter: (a function from one of the following choices)
1 (change/add PC/SSNs); go to Step 9.
2 (delete PC/SSNs); go to Step 7.
<RETURN> (keep all current PC/SSNs); go to Step 16.
Note: The prompts in Step 9 through Step 15 repeat to allow as many as eight
destinations for all backup modes except solitary.
Note: The xx or nA in the following prompts identifies the selection number of the
destination to be changed in the data. The system reorders the destinations in highest
to lowest order.
7 Prompt: GRPA*ORD=
Enter: GTT preference order
Go to the step with the prompt that matches your system.
8 Prompt: SELA*NUM=
Enter: (one of the following choices)
A single value to delete
A list of values to delete
A range of values to delete
Go to the step with the prompt that matches your system.
9 Prompt: FIN1A*TRAN=
Enter: (one of the following choices)
YES or Y (indicate a final translation)
NO or N (indicate a nonfinal translation)
Q (indicate the end of destinations)
<RETURN> (keep the current parameter)
Go to the step with the prompt that matches your system.
Note: The prompt in Step 10 appears when the backup mode is weighted load-shared or
shared replicate.
10 Prompt: WEIGHT1A=
Enter: (one of the following choices)
1-100 (backup type - weighted load-shared)
0-100 (backup type - shared replicate)
<RETURN> (keep the current parameter)
Note: The SSxx*NAME prompt appears for final translations only. For nonfinal
translations, go to Step 11.
11 Prompt: SS1A*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 9 if additional destinations are allowed; go
to Step 16 if no additional destinations are allowed.
<RETURN> (specify a node and SSN); continue.
12 Prompt: NOD1A*NAME=
Enter: (one of the following choices)
The node name; go to Step 15.
<RETURN> (specify node point code); continue.
13 Prompt: LOGNET1A=
Enter: logical network name or number
14 Prompt: PTCODE1A=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
15 Prompt: SYS1A*NUM=
Enter: (one of the following choices)
An SSN (a final destination); go to Step 9 if additional subsystem are allowed.
0 (nonfinal translation); go to Step 16 if no additional subsystem are allowed.
<RETURN> (keep the current parameter); continue.
The system shows the destinations.
16 Verify the GTT destination group table entry. The system reorders the destination data
in highest to lowest preference. In shared-replicate mode, weight factors are ordered
in highest to lowest preference.
Constraints
Data tables
The system reads the GTT destination from the GTT multiple PC/SSN data table (W53).
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA SCCP GTTDEST
2 Prompt: GTTD*NAME=
Enter: (one of the following choices)
A GTT destination group name; go to Step 4.
ALL; go to Step 4.
<RETURN>; continue.
3 Prompt: GTC*NUM=
Enter: [1-1125]
Enter GTT destination group number.
Enter a single number, range, list of number, or ALL for all the numbers.
4 Prompt: DIS2A*FORM=
Enter: [CONT, ASSIGN, C, or A]
CONT or C (GTT destination group contents)
ASSIGN or A (TT and GTAs referencing the group)
Constraints
Data tables
The following data tables are affected when a GTT destination pair is deleted:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
! ALERT
ALERT! Deleting a GTA or range from the database can result in service interruption.
1 Prompt: >
Enter: DELETE SCCP GTTDEST
2 Prompt: GTTD*NAME=
Enter: (one of the following choices)
A GTT destination group name to be deleted
<RETURN> (select GTT group number); continue.
3 Prompt: GTA*NUM=
Enter: [1-1125]
Enter GTT destination group number.
The system shows the table entry.
GTM definition
The GTM definition feature provides the capabilities to modify global title parameters of a
called party address so that the SCCP message can be properly interpreted by the 5070 SSG for
later performing global title translation and can be decoded appropriately by the next
signaling point where it is sent.
Global title modification is performed before the global title translation (pre-GTT GTM), or
after the global title translation (post-GTT GTM), or both.
Constraints
No constraints apply to changing the pre-GTT GTM criteria and GTM parameters.
Data tables
The system accesses these data tables to add the pre-GTT GTM criteria and GTM parameters:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN SCCP PREGTM
2 Prompt: GTF=
Enter: (one of the following choices)
1 (NADDR); go to Step 5.
2 (TRANSTYPE)
3 (TRANSTYPE and NUMPLAN)
4 (TRANSTYPE, NUMPLAN, and NADDR)
3 Prompt: TRA*TYPE=
Enter: [0–255]
If you enter 2 in Step 2, go to Step 6.
This entry specifies the translation type.
4 Prompt: NUM*PLAN=
Enter: [0–14]
If you enter 3 in Step 2, go to Step 6.
This entry specifies the valid numbering plans. The default is 0.
5 Prompt: NAD*DR=
Enter: [0–126]
This entry specifies the nature of address indicators. The default is 0.
6 Prompt: GTTWEA=
Enter: [1–28]
Enter a single number, list of numbers, or range of numbers.
This entry specifies the global title address digits.
7 Prompt: GTMNUM=
Enter: [1-999]
Enter a single value; go to Step 18.
<RETURN>; go to Step 8.
If you entered 1 in Step 2 and default is entered in Step 7, go to Step 10.
8 Prompt: NTRA*TYPE
Enter: (one of the following choices)
[0-255] (single value)
N (no modification)
If you entered 2 in Step 2, go to Step 11.
This entry specifies the new translation type value.
9 Prompt: NNUM*PLAN=
Enter: (one of the following choices)
[0-14] (single value)
N (no modification)
If you entered 3 is entered in Step 2, go to Step 11.
This entry specifies the new numbering plan value.
10 Prompt: NNAD*DR=
Enter: (one of the following choices)
[0-126] (single value)
N (no modification)
This entry specifies the new nature of address value.
11 Prompt: GTADM*TYPE
Enter: (one of the following choices)
N (no modification); go to Step 18.
R (replace); go to Step 12.
I (insert); go to Step 14.
D (delete); go to Step 15.
A (append); go to Step 17.
12 Prompt: DIGRS*LOC=
Enter: [1–28]
13 Prompt: NUMDR=
Enter: [1-28]; go to Step 17.
This entry specifies the number of digits to be replaced in the MSU.
14 Prompt: DIGI*LOC=
Enter: [1-28]; go to Step 17.
This entry specifies the start location from where digit is inserted.
15 Prompt: DIGDS*LOC=
Enter: [1-28]
This entry specifies the start location from where digit is deleted.
16 Prompt: NUMDD=
Enter: [1-28]; go to Step 18.
This entry specifies the number of digits to be deleted.
17 Prompt: NEW*DIG=
Enter: [1-28 digits] (single value)
This entry specifies the new digits.
The system shows the pre-GTT GTM criteria and GTM parameters.
Constraints
Data tables
The system accesses these data tables to change the pre-GTT GTM parameters:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE SCCP PREGTM
2 Prompt: GTF=
Enter: (one of the following choices)
1 (NADDR); go to Step 5.
2 (TRANSTYPE)
3 (TRANSTYPE and NUMPLAN)
4 (TRANSTYPE, NUMPLAN, and NADDR)
3 Prompt: TRA*TYPE=
Enter: [0–255]
If you enter 2 in Step 2, go to Step 6.
This entry specifies the translation type value.
4 Prompt: NUM*PLAN=
Enter: [0–14]
If you enter 3 in Step 2, go to Step 6.
This entry specifies the valid numbering plans.
The default is 0.
5 Prompt: NAD*DR=
Enter: [0–126]
This entry indicates the nature of address.
The default is 0.
6 Prompt: GTTTWEA=
Enter: [1–28]
7 Prompt: GTMNUM=
Enter: [1-999]
Enter a single value; go to Step 18.
<RETURN>; go to Step 8.
If you entered 1 in Step 2 and default is entered in Step 7, go to Step 10.
8 Prompt: CNTRA*TYPE
Enter: (one of the following choices)
[0-255] (single value)
N (no modification)
If you entered 2 in Step 2, go to Step 11.
This entry specifies the new translation type value. The default is the current database
values.
9 Prompt: CNNUM*PLAN=
Enter: (one of the following)
[0-14] (single value)
N (no modification)
If you entered 3 in Step 2, go to Step 11.
This entry specifies the new numbering plan value. The default is the current database
values.
10 Prompt: CNNAD*DR=
Enter: (one of following choices)
[0-126] (single value)
N (no modification)
This entry specifies the new nature of address value. The default is the current
database values.
11 Prompt: CGTADM*TYPE
Enter: (one of the following choices)
N (no modification); go to Step 18.
R (replace); go to Step 12.
I (insert); go to Step 14.
D (delete); go to Step 15.
A (append); go to Step 17.
The default is the current database values.
12 Prompt: CDIGRS*LOC=
Enter: [1–28]
This entry specifies the start location of digit replacement.
13 Prompt: CNUMDR=
Enter: [1-28]; go to Step 17.
This entry specifies the number of digits to be replaced in the MSU.
14 Prompt: CDIGI*LOC=
Enter: [1-28]; go to Step 17.
This entry specifies the start location from where digit is inserted.
15 Prompt: CDIGDS*LOC=
Enter: [1-28]
This entry specifies the start location from where digit is deleted.
16 Prompt: CNUMDD=
Enter: [1-28]; go to Step 18.
This entry specifies the number of digits to be deleted.
17 Prompt: NEW*DIG=
Enter: [1-28 digits] (single value)
This entry specifies the new digits.
The system shows the changed pre-GTT GTM parameters.
Constraints
No constraints apply to deleting the pre-GTT GTM criteria and GTM parameters.
Data tables
The system accesses these data tables to delete the pre-GTT GTM criteria and GTM
parameters:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE SCCP PREGTM
2 Prompt: GTF=
Enter: (one of the following choices)
1 (NADDR); go to Step 5.
2 (TRANSTYPE)
3 (TRANSTYPE and NUMPLAN)
4 (TRANSTYPE, NUMPLAN, and NADDR)
3 Prompt: TRA*TYPE=
Enter: [0–255]
If you enter 2 in Step 2 and a single value is entered in Step 3, go to Step 6.
4 Prompt: NUM*PLAN=
Enter: [0–14]
If you enter 3 in Step 2 and a single value is entered in Step 4, go to Step 6.
This entry specifies the valid numbering plans.
The default is 0.
5 Prompt: NAD*DR=
Enter: [0–126]
This entry specifies the nature of address indicators.
The default is 0.
6 Prompt: GTTTWEC=
Enter: [1–28]
This entry specifies the global title address digits.
Constraints
No constraints apply to displaying the pre-GTT GTM criteria and GTM parameters.
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY SCCP PREGTM
2 Prompt: GTF=
Enter: (one of the following choices)
1 (NADDR); go to Step 5.
2 (TRANSTYPE)
3 (TRANSTYPE and NUMPLAN)
4 (TRANSTYPE, NUMPLAN, and NADDR)
3 Prompt: DTRA*TYPE=
Enter: (one of the following choices)
[0–255] (single value)
ALL; go to Step 7.
If you enter 2 in Step 2 and a single value is entered in Step 3, go to Step 6.
This entry specifies the translation type.
4 Prompt: DNUM*PLAN=
Enter: (one of the following choices)
[0–14] (single value)
ALL; go to Step 7.
If you enter 3 in Step 2 and a single value is entered in Step 4, go to Step 6.
This entry specifies the valid numbering plans. The default is 0.
5 Prompt: DNAD*DR=
Enter: (one of the following choices)
[0–126] (single value)
ALL; go to Step 7.
This entry specifies the nature of address indicators. The default is 0.
6 Prompt: GTTTWEC=
Enter: [1–28]
This entry specifies the global title address digits.
The system shows the pre-GTT GTM criteria and GTM parameters.
Constraints
Data tables
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY SCCP GTMPARAM
2 Prompt: GTMNUM=
Enter: (one of the following choices)
[1–199] (single value); go to Step 13.
ALL; go to Step 13.
<RETURN>; go to Step 3.
3 Prompt: NTRA*TYPE=
Enter: (one of the following choices)
[0–255] (single value)
N (no modification)
ALL
This entry specifies the translation type. The default value is ALL.
4 Prompt: NNUM*PLAN=
Enter: (one of the following choices)
[0–14] (single value)
N (no modification)
ALL
This entry specifies the valid numbering plans. The default is ALL.
5 Prompt: NNAD*DR=
Enter: (one of the following choices)
[0–126] (single value)
N (no MSU modification)
ALL
This entry specifies the nature of address indicators. The default is ALL.
6 Prompt: GTADM*TYPE
Enter: (one of the following choices)
N (no modification); go to Step 13.
R (replace); go to Step 7.
I (insert); go to Step 9.
D (delete); go to Step 10.
A (append); go to Step 12.
ALL; go to Step 13.
The default is the current database values.
7 Prompt: DIGRS*LOC=
Enter: [1–28 or ALL]
1–28(single value)
ALL; go to Step 13.
This entry specifies the start location of digit replacement.
8 Prompt: NUMDR=
Enter: (one of the following choices)
[1-28] (single value); go to Step 12.
ALL; go to Step 12.
This entry specifies the number of digits to be replaced in the MSU.
9 Prompt: DIGI*LOC=
Enter: (one of the following choices)
[1–28] (single value); go to Step 12.
ALL; go to Step 12.
This entry specifies the start location from where digit is inserted. The default is ALL.
10 Prompt: DIGDS*LOC=
Enter: (one of the following choices)
[1–28] (single value); go to Step 11.
ALL; go to Step 12.
This entry specifies the start location from where digit is deleted. The default is ALL.
11 Prompt: NUMDD=
Enter: (one of the following choices)
[1–28] (single value); go to Step 13.
ALL; go to Step 13.
This entry specifies the number of digits to be deleted. The default is ALL.
12 Prompt: NEW*DIG=
Enter: [1–28 digits] (single value)
This entry specifies the new digits.
The system shows the changed pre-GTT GTM criteria and GTM parameters.
Regular GTT
Each SS7 destination that handles SS7 messages must have a TT and GTA. A regular GTT
destination group consists of one or more SS7 destinations.
A regular GTT destination group is assigned to each GTA in a TT. The same GTT destination
group can be assigned to one or more GTAs in a TT and to GTAs in other TTs. A GTA in a TT can
be assigned to only one regular GTT destination group.
Global title data is specified as a single digit or range of digits whose number is determined by
the translation mechanism assigned to the type through the ASSIGN SCCP TRANSL command or
the CHANGE SCCP TRANSL command.
Constraints
• Define the TT, translation mechanism, and the GTT destination group in the database
before adding the GTT destination. The TT cannot be defined as shared in the database.
• A range cannot overlap another range with the same TT.
• Single values cannot be defined more than once. Single values cannot fall on or in the
boundaries of a range defined in the same TT.
• If the number of entered digits is fewer than the number required by the translation
mechanism, the system assigns a range as follows:
– The value entered is right-padded with zeros.
– An ending value is created by right-padding with nines.
Data tables
The following data tables are affected when a GTT destination pair is added:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN GLOBAL TRANSL
2 Prompt: GTF=
Enter: (one of the following choices)
1 (NADDR); go to Step 5.
2 (TRANSTYPE)
3 (TRANSTYPE and NUMPLAN)
4 (TRANSTYPE and NUMPLAN, NADDR)
3 Prompt: TRA*TYPE=
Enter: [0-255]
If you enter 2 in Step 2, go to Step 6; otherwise, continue.
4 Prompt: NUM*PLAN=
Enter: [0-14]
The default is 0.
5 Prompt: NAD*DR=
Enter: [0-126]
The default is 0.
6 Prompt: GTTTWEA=
Enter: [1-28]
7 Prompt: GTTD*NAME=
Enter: (one of the following choices)
Destination group name; go to Step 9.
<RETURN>; continue.
The default is group number.
8 Prompt: GTNA*NUM=
Enter: [1-1125]
The system shows the parameters.
9 Prompt: GTMREQ=
Enter: [YES, NO, Y or N]
If you enter YES, continue; otherwise, go to Step 21.
10 Prompt: GTMNUM=
Enter: (one of the following choices)
[1-199] (single value); go to Step 21.
<RETURN>; go to Step 11.
If you enter 1 in Step 2 and default is entered in Step 10, go to Step 13.
11 Prompt: NTRA*TYPE=
Enter: (one of the following choices)
[0-255] (single value)
N (no modification)
If you enter 2 in Step 2, go to Step 14.
12 Prompt: NNUM*PLAN=
Enter: (one of the following choices)
[0-14] (single value)
N (no modification)
If you enter 2 in Step 2, go to Step 14.
13 Prompt: NNAD*DR=
Enter: (one of the following choices)
[0-126] (single value)
N (no modification)
14 Prompt: GTADM*TYPE=
Enter: (one of the following choices)
N (no modification); go to Step 21.
R (replace); go to Step 15.
I (insert); go to Step 17.
D (delete); go to Step 18.
A (append); go to Step 20.
15 Prompt: DIGRS*LOC=
Enter: [1-28]
16 Prompt: NUMDR=
Enter: [1-28]; go to Step 20.
17 Prompt: DIGI*LOC=
Enter: [1-28]; go to Step 20.
18 Prompt: DIGI*LOC=
Enter: [1-28]
19 Prompt: NUMDD=
Enter: [1-28]; go to Step 21.
20 Prompt: NEW*DIG=
Enter: [1-28]
Enter single value.
This entry specifies the new digits.
This procedure also modifies regular GTT data for 28-digit GTT addresses single destinations.
Constraints
• The TT, translation mechanism, and the GTT destination group must first be defined in the
database. The TT cannot be defined as shared in the database.
• A range cannot overlap another range with the same TT.
• Single values cannot be defined more than once. Single values cannot fall on or in the
boundaries of a range defined in the same TT.
• If the number of entered digits is fewer than the number required by the translation
mechanism, the system assigns a range as follows:
– The value entered is right-padded with zeros.
– An ending value is created by right-padding with nines.
Data tables
The following data tables are affected when a GTT destination is changed:
• TT mapping (W85)
• Regular GTT (W86)
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE GLOBAL TRANSL
2 Prompt: GTF=
Enter: (one of the following choices)
1 (NADDR); go to Step 5.
2 (TRANSTYPE)
3 (TRANSTYPE and NUMPLAN)
4 (TRANSTYPE and NUMPLAN, NADDR)
3 Prompt: TRA*TYPE=
Enter: [0-255]
If you enter 2 in Step 2, go to Step 6; otherwise, continue.
4 Prompt: NUM*PLAN=
Enter: [0-14]
The default is 0.
5 Prompt: NAD*DR=
Enter: [0-126]
The default is 0.
6 Prompt: GTTTWEA=
Enter: [1-28]
Enter a single value or range.
7 Prompt: GTTD*NAME=
Enter: (one of the following choices)
Destination group name; go to Step 9.
<RETURN>; continue.
8 Prompt: GTNB*NUM=
Enter: [1-1125]
The system shows the parameters.
9 Prompt: CGTMREQ=
Enter: [YES, NO, Y, or N]
If you enter YES, continue; otherwise, go to Step 21.
10 Prompt: CGTMNUM=
Enter: (one of the following choices)
[1-199] (single value); go to Step 21.
<RETURN>; go to Step 11.
If you enter 1 in Step 2 and default is entered in Step 10, go to Step 13.
11 Prompt: CNTRA*TYPE=
Enter: (one of the following choices)
[0-255] (single value)
N (no modification)
If you enter 2 in Step 2, go to Step 14.
12 Prompt: CNNUM*PLAN=
Enter: (one of the following choices)
[0-14] (single value)
N (no modification)
If you enter 2 in Step 2, go to Step 14.
13 Prompt: CNNAD*DR=
Enter: (one of the following choices)
[0-126] (single value)
N (no modification)
14 Prompt: CGTADM*TYPE=
Enter: (one of the following choices)
N (no modification); go to Step 21.
R (replace); go to Step 15.
I (insert); go to Step 17.
D (delete); go to Step 18.
A (append); go to Step 20.
15 Prompt: CDIGRS*LOC=
Enter: [1-28]
16 Prompt: CNUMDR=
Enter: [1-28]; go to Step 20.
17 Prompt: CDIGI*LOC=
Enter: [1-28]; go to Step 20.
18 Prompt: CDIGI*LOC=
Enter: [1-28]
19 Prompt: CNUMDD=
Enter: [1-28]; go to Step 21.
20 Prompt: CNEW*DIG=
Enter: [1-28]
Enter single value.
This entry specifies the new digits.
Constraints
Data tables
• TT mapping (W85)
• Regular GTT (W86)
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GLOBAL TRANSL
2 Prompt: GTF=
Enter: (one of the following choices)
1 (NADDR); go to Step 5.
2 (TRANSTYPE)
3 (TRANSTYPE and NUMPLAN)
3 (TRANSTYPE and NUMPLAN, NADDR)
3 Prompt: DSPT*TYP=
Enter: [0-255 or ALL]
If you enter ALL; go to Step 7.
If you enter 3 or 4 in Step 2, go to Step 4.
If you enter 2 in Step 2, go to Step 6.
4 Prompt: DNUM*PLAN=
Enter: [0-14 or ALL]
If you enter ALL; go to Step 7.
The default is 0.
5 Prompt: DNAD*DR=
Enter: [0-126 or ALL]
The default value is 0.
6 Prompt: GTTTWEC=
Enter: [1-28 or ALL]
7 Prompt: DIS1A*FORM=
Enter: [BRIEF, DETAIL, B, or D]
Constraints
If regular GTT data assigned to a translation mechanism is deleted, messages are not routed
for those global titles.
Data tables
One or both of the following data tables are changed when a regular GTT destination is
removed from the database:
• TT mapping (W85)
• Regular GTT (W86)
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not execute database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
! ALERT
ALERT! Deleting the last regular GTT may result in removal of the associated subsystem,
subsequent failures, and possible service interruption.
1 Prompt: >
Enter: DELETE GLOBAL TRANSL
2 Prompt: GTF=
Enter: (one of the following choices)
1 (NADDR); go to Step 5.
2 (TRANSTYPE)
3 (TRANSTYPE and NUMPLAN)
3 (TRANSTYPE and NUMPLAN, NADDR)
3 Prompt: TRA*TYPE=
Enter: [0-255]
Enter the translation type.
If you enter 2 in Step 2, go to Step 6.
4 Prompt: NUM*PLAN=
Enter: [0-14]
Enter the numbering plan value.
The default is 0.
5 Prompt: NAD*DR=
Enter: [0-126 or ALL]
6 Prompt: GTTTWEC=
Enter: [1-28]
Enter the global title address digits.
Enter a single value, range, list, or ALL for all the values.
SCCP applications
When a subsystem is duplicated at two different DPCs, the subsystem's DPCs can be assigned as
mated applications in the 5070 SSG. In a mated application, at least one subsystem resides in a
node adjacent to the 5070 SSG. SCCP management uses the mated application feature to
inform the subsystem of a change of status in its mate.
Constraints
Data tables
The system accesses the subsystem status data table (Y83) to add a mated application to the
database.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN SCCP MAP
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number
7 Prompt: MSUB*NAME=
Enter: (one of the following choices)
The mated subsystem name; go to Step 12.
<RETURN>; continue.
8 Prompt: MNODE=
Enter: (one of the following choices)
The mated node name; go to Step 11.
<RETURN>; continue.
9 Prompt: MLOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
10 Prompt: MPNT*COD=
Enter: mated point code
11 Prompt: MSUBNO=
Enter: mated subsystem number
Constraints
Data tables
The system accesses the subsystem status data table (Y83) to change a mated application.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE SCCP MAP
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number
7 Prompt: MSUB*NAME=
Enter: (one of the following choices)
The mated subsystem name to be changed; go to Step 12.
<RETURN>; continue.
8 Prompt: MNODE=
Enter: (one of the following choices)
The mated node name to be changed; go to Step 11.
<RETURN>; continue.
9 Prompt: MLOG*NET=
Enter: logical network name or number
The default value is none.
10 Prompt: MPNT*COD=
Enter: mated point code
11 Prompt: MSUBNO=
Enter: mated subsystem number
Constraints
Data tables
The system retrieves SCCP mated applications from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA SCCP MAP
2 Prompt: LOG*NET=
Enter: logical network name, number, or All
The default value is none.
3 Prompt: DSUB*NAME=
Enter: (one of the following choices)
The subsystem name (the system shows the mated application).
ALL (the system shows all mated applications); go to Step 7.
<RETURN>; continue.
4 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number
The system shows the mated application.
Constraints
Data tables
The system accesses the subsystem status data table (Y83) to delete a mated application.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE SCCP MAP
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name to be deleted; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name to be deleted; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number
A group of SPs can be defined for a DPC of a subsystem. These SPs are notified of a status
change for that subsystem. This group of SPs is called a CSP group.
• CSP tasks
• CSP groups
• CSPs
CSP tasks
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 If a group is to be deleted, remove a CSP for each SSN and DPC where the group is
assigned.
CSP groups
Signaling points that require notification of a subsystem status change are called CSPs.
Signaling points that are concerned about the same subsystem point code are grouped together
and assigned a name in the 5070 SSG database.
Note: Create a concerned signaling point group for a destination group with two or more final
destinations. Each destination should consist of the other final destinations in the destination
group. If the concerned signaling point groups are not defined, the other point codes in the
group do not receive status changes related to the subsystem.
Constraints
• The node name and DPC must be listed on either the ordered route form or the link set
form.
Data tables
The following data tables are updated when a CSP group is added to the database:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN SCCP CSPGRP
2 Prompt: GROUP=
Enter: concerned signaling point group name
3 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
Constraints
• The node name and DPCs must be listed in the ordered route database or the link set
database.
• Nodes in the CSP group must use member (full point code) routing.
Data tables
The system accesses the concerned signaling point code data table (W89) to change a CSP.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE SCCP CSPGRP
2 Prompt: GROUP=
Enter: concerned signaling point group name
3 Prompt: SELECT=
Enter: (one of the following choices)
A selection number (1-n) of the group member to be changed
A list of selection numbers separated by commas
4 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 7.
<RETURN>; continue.
5 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
6 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
Constraints
Data tables
The system retrieves CSP parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA SCCP CSPGRP
2 Prompt: DGROUP=
Enter: (one of the following choices)
A concerned signaling point group name; go to Step 4.
ALL; continue.
3 Prompt: LOG*NET=
Enter: logical network name, number, or ALL
4 Prompt: FORMAT=
Enter: (a character from one of the following choices)
A (group assignments)
B (brief description)
C (group contents)
The system shows the CSP group.
Constraints
Data tables
The following data tables are affected when a CSP group is deleted:
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE SCCP CSPGRP
2 Prompt: GROUP=
Enter: concerned signaling point group name
3 Prompt: SELECT=
Enter: (one of the following choices)
A selection number (1-n) of the group member to be deleted
A list of selection numbers separated by commas
CSPs
The SPs that require notification of a system status change are called CSPs. SPs that are
concerned about the same subsystem are grouped together and associated with the subsystems
in the 5070 SSG database. The system generates a notification to the CSPs when that
subsystem or point code status changes.
• Assign a CSP
• Change a CSP
• Display a CSP
• Delete a CSP
Assign a CSP
Use this procedure to assign a group of concerned signaling points to a subsystem. The
subsystem entered is validated by confirming its existence in the database and assuring it is
not currently assigned to a group. An entry is assigned a group in the database to establish the
relationship between the subsystem and a group of concerned nodes.
Constraints
• The group name must already be defined in the concerned signaling point group database.
• Many point codes can be assigned to the same CSP group, but only one CSP group can be
assigned to a subsystem.
• Subsystem names must already be defined in the subsystem name database.
• The node name must be defined in the ordered route database or the link set database.
Data tables
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ASSIGN SCCP CSP
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
6 Prompt: SUBNO=
Enter: subsystem number
7 Prompt: GROUP=
Enter: CSP group name
Change a CSP
Use this procedure to reassign a group of CSPs from one subsystem to another. The subsystem
is validated by confirming its existence in the database and ensuring it is not currently assigned
to a group. The entry is changed in the database to establish the relationship between the
subsystem and a group of concerned nodes.
Constraints
• The group name must already be defined in the concerned signaling point group database.
• Many point codes can be assigned to the same CSP group, but only one CSP group can be
assigned to a subsystem.
• When a change to a CSP changes its state from ported to nonported, the system does not
remove the CSP from the CSP status data table (W89). The system maintains the CSP with
the nonported flag set to allow the CSP to be changed back to ported at a later date.
Data tables
The subsystem changes the CSP status data table (W89) tables to change a CSP.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE SCCP CSP
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name to be changed; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name to be changed; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number
7 Prompt: GROUP=
Enter: a concerned signaling point group name
Display a CSP
Use this procedure to show a brief or detailed report of one or all subsystems as requested.
The brief report lists basic information about the subsystem and the name of its assigned CSP
group. The detailed report shows all the information shown by the brief report, as well as a list
of all the nodes in the CSP group.
Constraints
Data tables
The system retrieves CSP group parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA SCCP CSP
2 Prompt: DSUB*NAME=
Enter: (one of the following choices)
The subsystem name; go to Step 7.
ALL; go to Step 4.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number
7 Prompt: FORMAT=
Enter: [B or D]
B (brief format)
D (detailed format)
Delete a CSP
Use this procedure to disassociate a subsystem from a group of concerned signaling points.
Constraints
• When a change to a CSP changes its state from ported to nonported, the system does not
remove the CSP from the subsystem status data table (Y83) table. The system maintains
the CSP with the nonported flag set to allow the CSP to be changed back to ported at a
later date.
Data tables
The system accesses subsystem status data table (Y83) to delete a CSP.
Procedure
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: DELETE SCCP CSP
2 Prompt: SUB*NAME=
Enter: (one of the following choices)
The subsystem name to be deleted; go to Step 7.
<RETURN>; continue.
3 Prompt: NODE=
Enter: (one of the following choices)
The node name to be deleted; go to Step 6.
<RETURN>; continue.
4 Prompt: LOG*NET=
Enter: logical network name or number
The default value is none.
5 Prompt: PNT*COD=
Enter: point code
The point code valid range depends on the point code format that is configured for the
lognet.
The default value is none.
The system shows the parameters assigned to the node.
6 Prompt: SUBNO=
Enter: subsystem number
Gateway screening
• Screening features
• Gateway screening supporting tables
• Gateway screening MMI commands
• Gateway link set
• Allowed/blocked OPC
• Allowed SIO
• Allowed/blocked DPC
• Allowed affected destination
• Allowed CGPA global title address
• Allowed calling party address
• Allowed CDPA global title address
• Allowed called party address
• Allowed affected point code
• Gateway screening threshold
• Gateway screening throttle
Screening features
The gateway screening feature provides the 5070 SSG capabilities to screen incoming MTP and
SCCP message traffic received on link sets designated as gateway link sets. This feature
provides protection against unauthorized traffic or traffic sent in error to a network.
The gateway screening feature provides a local MMI interface for operations personnel at the
5070 SSG to provision gateway screening tables. The gateway screening tables contain
parameters from selected fields within received MTP and SCCP messages that are to be
screened as allowed or blocked.
• MTP and SCCP messages with message parameters provisioned as allowed in the gateway
screening tables are routed by MTP and SCCP.
• Messages with message parameters provisioned as blocked in the gateway screening tables
are set as failing screening. An IPR is issued and is counted in TMM. If the screening is
enabled, the message is discarded; otherwise, the message goes through the normal
routing procedure.
• Screening for a message is discontinued if the next screening reference is STOP. The
message is then considered as successfully passing gateway screening.
SSN screening
SSN values that are defined by combining originating and terminiating logical networks are
screened with SSN screening. SCCP messages with non-allowed SSN values are discarded. SSN
screening takes place in the following situations:
• Link set table - this table contains an indicator specifying that the link set is a gateway
link set.
• Gateway screening reference table - entries in this table are created based on the
screening references. These entries provide the link between screening criteria of
different parameter fields tables that screen received messages.
Note: The configuration of gateway screening must be done in the reverse order of the
provision list. For example, the MMIs are executed in the following order to configure the
gateway screening tables:
Constraints
Data tables
The following data tables are affected when gateway link set parameters are assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR GTWYLS
2 Prompt: LSNAME=
Enter: a unique gateway link set name
3 Prompt: LNKGID=
Enter: [01-99]
4 Prompt: NSFI=
Enter: (one of the following choices)
OPC
DPC
BLKOPC
BLKDPC
SIO
STOP
If you enter STOP, go to Step 6; otherwise, continue.
5 Prompt: NSR=
Enter: next screening reference
6 Prompt: REJIPR=
Enter: [Y or N]
Y (enable rejected MSU IPR)
N (disable rejected MSU IPR)
7 Prompt: SCREEN=
Enter: [Y or N]
Y (enable screening)
N (disable screening)
8 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when gateway link set parameters are
changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR GTWYLS
2 Prompt: LSNAME=
Enter: gateway link set name
3 Prompt: NEWLNKGID=
Enter: [1-99]
4 Prompt: NEWNSFI=
Enter: (one of the following choices)
OPC
DPC
BLKOPC
BLKDPC
SIO
STOP
If you enter STOP, go to Step 6; otherwise, continue.
5 Prompt: NEWNSR=
Enter: new next screening reference
6 Prompt: NEWREJIPR=
Enter: [Y or N]
Y (enable new rejected MSU IPR)
N (disable new rejected MSU IPR)
7 Prompt: NEWSCR=
Enter: [Y or N]
Y (enable new screening)
N (disable new screening)
8 Prompt: NEWREM*ARK=
Enter: new remark
Constraints
Data tables
The following data tables are affected when gateway link set parameters are deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR GTWYLS
2 Prompt: LSNAME=
Enter: link set name
The system shows the parameters.
Constraints
Data tables
The system retrieves the gateway link set parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR GTWYLS
2 Prompt: DLSNAME=
Enter: gateway link set name or ALL
The system shows the parameters.
Allowed/blocked OPC
You can perform the following gateway screening OPC procedures:
Constraints
Data tables
The following data tables are affected when OPC gateway screening parameters are assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR OPC
2 Prompt: SF=
Enter: [A or B]
A (allowed)
B (blocked)
3 Prompt: SR=
Enter: screening reference
If you enter A in Step 2, go to Step 5; otherwise, continue.
4 Prompt: NOMATCH=
Enter: [Y or N]
Y (no match record); go to Step 9.
N (blocked record)
The default value is N.
5 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
6 Prompt: PCSR=
Enter: point code start range or ALL
7 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
8 Prompt: NSFI1=
Enter: (one of the following choices)
BLKOPC
SIO
DPC
BLKDPC
CGGTA
CGPA
AFTDES
STOP
If you enter STOP, go to Step 13; otherwise, go to Step 10.
9 Prompt: NSFIB1=
Enter: (one of the following choices)
SIO
DPC
BLKDPC
CGGTA
CGPA
AFTDES
FAIL
STOP
If you enter STOP or FAIL, go to Step 13; otherwise, continue.
10 Prompt: NSR1=
Enter: next screening reference
If you enter CGPA or CGGTA in Step 8 or Step 9, go to Step 11; otherwise, go to Step 13.
11 Prompt: NSFI2=
Enter: (one of the following choices)
CGGTA
CGPA
STOP
FAIL
If you enter STOP or FAIL, go to Step 13; otherwise, continue.
If you enter CGPA in Step 8 or Step 9, then the choices are: CGGTA, STOP, FAIL.
If you enter CGGTA in Step 8 or Step 9, then the choices are: CGPA, STOP, FAIL.
12 Prompt: NSR2=
Enter: next screening reference
13 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when OPC gateway screening parameters
are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR OPC
2 Prompt: SF=
Enter: [A or B]
A (allowed)
B (blocked)
3 Prompt: SR=
Enter: screening reference
If you enter A in Step 2, go to Step 6; otherwise, continue.
4 Prompt: NOMATCH=
Enter: [Y or N]
Y (no match record); go to Step 11.
N (blocked record)
5 Prompt: LOG*NET=
Enter: logical network name or number
6 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 8; otherwise, continue
The point code valid range depends on the point code format that is configured for the
lognet.
7 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
8 Prompt: NEWPCSR=
Enter: (one of the following choices)
New point code start range
ALL; go to Step 10.
<RETURN> (current value).
9 Prompt: NEWPCER=
Enter: (one of the following choices)
New point code end range
ALL; go to Step 2.
<RETURN> (current value).
10 Prompt: NEWNSFI1=
Enter: (one of the following choices)
BLKOPC
SIO
DPC
BLKDPC
CGGTA
CGPA
AFTDEST
STOP
<RETURN> (current value)
If you enter STOP, go to Step 15; otherwise, go to Step 12.
11 Prompt: NEWNSFIB1=
Enter: (one of the following choices)
SIO
DPC
BLKDPC
CGGTA
CGPA
AFTDEST
FAIL
STOP
<RETURN> (current value)
If you enter STOP or FAIL, go to Step 15; otherwise, continue.
12 Prompt: NEWNSR1=
Enter: next screening reference
If you enter CGPA or CGGTA in Step 10 or Step 11, go to Step 13; otherwise, go to
Step 15.
13 Prompt: NEWNSFI2=
Enter: (one of the following choices)
CGPA
CGGTA
STOP
FAIL
If you enter STOP or FAIL, go to Step 15; otherwise, continue.
If you enter CGPA in Step 10 or Step 11, then the choices are: CGGTA, STOP, FAIL.
If you enter CGGTA in Step 10 or Step 11, then the choices are: CGPA, STOP, FAIL.
14 Prompt: NEWNSR2=
Enter: next screening reference
15 Prompt: NEWREM=
Enter: new remark
Constraints
Data tables
The following data tables are affected when OPC gateway screening parameters are deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR OPC
2 Prompt: SF=
Enter: [A or B]
A (allowed)
B (blocked)
3 Prompt: SR=
Enter: screening reference
If you enter A in Step 2, go to Step 6; otherwise, continue.
4 Prompt: NOMATCH=
Enter: [Y or N]
Y (no match record)
N (blocked record)
5 Prompt: LOG*NET=
Enter: logical network name or number
6 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 8; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
7 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
Constraints
Data tables
The system retrieves the OPC gateway screening parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR OPC
2 Prompt: DSF=
Enter: [A or B]
A (allowed)
B (blocked)
ALL; go to Step 8.
3 Prompt: DSR=
Enter: (one of the following choices)
Screening reference
ALL; go to Step 8.
If you enter A in Step 2, go to Step 6; otherwise, continue.
4 Prompt: DNOMATCH=
Enter: (one of the following choices)
Y (no match record); go to Step 8.
N (blocked record)
ALL; go to Step 8.
5 Prompt: LOG*NET=
Enter: logical network name or number
6 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 8; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
7 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
Allowed SIO
You can perform the following gateway screening SIO procedures:
Constraints
• If STOP is configured as NSFID for an SR, SI, PRI, H0, H1 where value of SI = 3, then the
same cannot be configured for a secondary NSFID for the same SR, SI, PRI, H0, H1.
• To configure another NSFI for the same SR, either perform the Delete GWSCR SIO
procedure, delete the entry, and reconfigure, or perform the Change GWSCR SIO
procedure for the same SR, SI, PRI, H0, H1.
Data tables
The following data tables are affected when SIO gateway screening parameters are assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR SIO
2 Prompt: SR=
Enter: screening reference
3 Prompt: PRI=
Enter: priority value or ALL
4 Prompt: SI=
Enter: service indicator or ALL
If you enter 00 or 01, go to Step 5; otherwise, go to Step 7.
5 Prompt: H0=
Enter: heading code or ALL
6 Prompt: H1=
Enter: heading code or ALL
Note: The set of possible next screening functions is based on the service indicator
value entered in Step 4.
7 Prompt: NSFI=
Enter: (one of the following choices)
DPC
BLKDPC
CGGTA
CGPA
CDGTA
CDPA
AFTDES
STOP
If you enter STOP, go to Step 11; otherwise, continue.
8 Prompt: NSR1=
Enter: next screening reference
If you enter CGPA, CDGTA, CGGTA, or CDPA in Step 7, then go to Step 9; otherwise, go
to Step 11.
Note: The set of possible next screening functions is based on the next screening
function value entered in Step 7.
9 Prompt: NSFI2=
Enter: (one of the following choices)
CGGTA
CGPA
CDGTA
CDPA
STOP
FAIL
If you enter STOP or FAIL, go to Step 11; otherwise, continue.
10 Prompt: NSR2=
Enter: next screening reference
11 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when SIO gateway screening parameters
are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR SIO
2 Prompt: SR=
Enter: screening reference
3 Prompt: PRI=
Enter: priority value or ALL
4 Prompt: SI=
Enter: service indicator or ALL
If you enter 00 or 01, go to Step 5; otherwise, go to Step 8.
5 Prompt: H0=
Enter: heading code or ALL
6 Prompt: H1=
Enter: heading code or ALL
7 Prompt: NEWPRI=
Enter: new priority value or ALL
8 Prompt: NEWSI=
Enter: new service indicator or ALL
If you enter 00 or 01, go to Step 9; otherwise, go to Step 11.
9 Prompt: NEWH0=
Enter: new heading code or ALL
10 Prompt: NEWH1=
Enter: new heading code or ALL
Note: The set of possible next screening functions is based on the service indicator
value entered in Step 8.
11 Prompt: NEWNSFI1=
Enter: (one of the following choices)
DPC
BLKDPC
CGGTA
CGPA
CDGTA
CDPA
AFTDEST
STOP
If you enter STOP, go to Step 15; otherwise, continue.
12 Prompt: NEWNSR1=
Enter: new next screening reference
If you enter CGPA, CDGTA, CGGTA, or CDPA in Step 11, then go to Step 13; otherwise,
go to Step 15.
Note: The set of possible next screening functions is based on the next screening
function value entered in Step 11.
13 Prompt: NEWNSFI2=
Enter: (one of the following choices)
CGGTA
CGPA
CDGTA
CDPA
STOP
FAIL
If you enter STOP or FAIL, go to Step 15; otherwise, continue.
14 Prompt: NEWNSR2=
Enter: next screening reference
15 Prompt: NEWREM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected when SIO gateway screening parameters are deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR SIO
2 Prompt: SR=
Enter: screening reference
3 Prompt: PRI=
Enter: priority value or ALL
If you enter ALL, go to Step 7.
4 Prompt: SI=
Enter: service indicator or ALL
If you enter 00 or 01, go to Step 5; otherwise, the system shows the parameters. Go to
Step 7.
5 Prompt: H0=
Enter: heading code or ALL
6 Prompt: H1=
Enter: heading code or ALL
The system shows the parameters.
Constraints
Data tables
The system retrieves the SIO gateway screening parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR SIO
2 Prompt: DSR=
Enter: screening reference or ALL
If you enter ALL, the system shows the parameters; go to Step 7.
3 Prompt: PRI=
Enter: priority value or ALL
If you enter ALL, the system shows the parameters; go to Step 7.
4 Prompt: SI=
Enter: service indicator or ALL
If you enter 00 or 01, go to Step 5; otherwise, the system shows the parameters. Go to
Step 7.
5 Prompt: H0=
Enter: heading code or ALL
6 Prompt: H1=
Enter: heading code or ALL
Allowed/blocked DPC
You can perform the following gateway screening DPC procedures:
Constraints
Data tables
The following data tables are affected when DPC gateway screening parameters are assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR DPC
2 Prompt: SF=
Enter: [A or B]
A (allowed)
B (blocked)
3 Prompt: SR=
Enter: screening reference
If you enter A in Step 2, go to Step 6; otherwise, continue.
4 Prompt: NOMATCH=
Enter: [Y or N]
Y (no match record); go to Step 9.
N (blocked record)
5 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
6 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 8; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
7 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
8 Prompt: NSFI1=
Enter: (one of the following choices)
BLKDPC
CGGTA
CGPA
AFTDEST
STOP
If you enter STOP, go to Step 13; otherwise, go to Step 10.
9 Prompt: NSFIB1=
Enter: (one of the following choices)
CGGTA
CGPA
AFTDES
FAIL
STOP
If you enter STOP or FAIL, go to Step 13; otherwise, continue.
10 Prompt: NSR1=
Enter: next screening reference
If you enter CGPA or CGGTA in Step 8 or Step 9, go to Step 11; otherwise, go to Step 13.
If you enter CGPA in Step 8 or Step 9, then the choices are: CGGTA, STOP, FAIL.
If you enter CGGTA in Step 8 or Step 9, then the choices are: CGPA, STOP, FAIL.
11 Prompt: NSFI2=
Enter: (one of the following choices)
CGPA
CGGTA
STOP
FAIL
If you enter STOP or FAIL, go to Step 13; otherwise, continue.
12 Prompt: NSR2=
Enter: next screening reference
13 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when DPC gateway screening parameters
are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR DPC
2 Prompt: SF=
Enter: [A or B]
A (allowed)
B (blocked)
3 Prompt: SR=
Enter: screening reference
If you enter A in Step 2, go to Step 6; otherwise, continue.
4 Prompt: NOMATCH=
Enter: [Y or N]
Y (no match record); go to Step 11.
N (blocked record)
5 Prompt: LOG*NET=
Enter: logical network name or number
6 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 2; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
7 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
8 Prompt: NEWPCSR=
Enter: (one of the following choices)
New point code start range
ALL; go to Step 10.
<RETURN> (current value)
9 Prompt: NEWPCER=
Enter: (one of the following choices)
New point code end range
ALL; go to Step 2.
<RETURN> (current value)
10 Prompt: NEWNSFI1=
Enter: (one of the following choices)
BLKDPC
CGGTA
CGPA
AFTDEST
STOP
<RETURN> (current value)
If you enter STOP, go to Step 15; otherwise, go to Step 12.
11 Prompt: NEWNSFIB1=
Enter: (one of the following choices)
CGGTA
CGPA
AFTDEST
FAIL
STOP
<RETURN> (current value)
If you enter STOP or FAIL, go to Step 15; otherwise, continue.
12 Prompt: NEWNSR1=
Enter: next screening reference
If you enter CGPA or CGGTA in Step 10 or Step 11, go to Step 13; otherwise, go to
Step 15.
If you enter CGPA in Step 10 or Step 11, then the choices are: CGGTA, STOP, FAIL.
If you enter CGGTA in Step 10 or Step 11, then the choices are: CGPA, STOP, FAIL.
13 Prompt: NEWNSFI2=
Enter: (one of the following choices)
CGPA
CGGTA
STOP
FAIL
If you enter STOP or FAIL, go to Step 15; otherwise, continue.
14 Prompt: NEWNSR2=
Enter: next screening reference
15 Prompt: NEWREM=
Enter: new remark
Constraints
Data tables
The following data tables are affected when DPC gateway screening parameters are deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR DPC
2 Prompt: SF=
Enter: [A or B]
A (allowed)
B (blocked)
3 Prompt: SR=
Enter: screening reference
If you enter A in Step 2, go to Step 6; otherwise, continue.
4 Prompt: NOMATCH=
Enter: [Y or N]
Y (no match record)
N (blocked record)
5 Prompt: LOG*NET=
Enter: logical network name or number
6 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 8; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
7 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
Constraints
Data tables
The system retrieves the DPC gateway screening parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR DPC
2 Prompt: DSF=
Enter: [A or B]
A (allowed)
B (blocked)
ALL; go to Step 8.
3 Prompt: DSR=
Enter: (one of the following choices)
Screening reference
ALL; go to Step 8.
If you enter A in Step 2 and ALL in Step 3, go to Step 6; otherwise, continue.
4 Prompt: DNOMATCH=
Enter: [Y or N]
Y (no match record); go to Step 8.
N (blocked record); go to Step 6.
ALL; go to Step 8.
5 Prompt: LOG*NET=
Enter: logical network name or number
6 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 8; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
7 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
Constraints
Data tables
The following data tables are affected when AFTDES gateway screening parameters are
assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR AFTDES
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when AFTDES gateway screening
parameters are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR AFTDES
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
5 Prompt: PCER=
Enter: point code end range or ALL
The system shows the existing parameters.
6 Prompt: NEWPCSR=
Enter: new point code start range or ALL
If you enter ALL, go to Step 8; otherwise, continue.
7 Prompt: NEWPCER=
Enter: new point code end range
8 Prompt: NEWREM*ARK=
Enter: new remark
Constraints
Data tables
The following data tables are affected when AFTDES gateway screening parameters are
deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR AFTDES
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
Constraints
Data tables
The system retrieves the AFTDES gateway screening parameters from the following data
tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR AFTDES
2 Prompt: DSR=
Enter: (one of the following choices)
Screening reference
ALL; go to Step 6.
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range
The point code valid range depends on the point code format that is configured for the
lognet.
Constraints
Data tables
The following data tables are affected when CGGTA gateway screening parameters are
assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR CGGTA
2 Prompt: SR=
Enter: screening reference
3 Prompt: SUBSYS*NUM=
Enter: subsystem number or ALL
4 Prompt: GTF=
Enter: [1-4]
1 (NADDR); go to Step 8.
2 (TRANSTYPE); go to Step 5.
3 (TRANSTYPE, NUMPLAN, DIGTYPE); go to Step 5.
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR); go to Step 5.
5 Prompt: TRANS*TYPE=
Enter: [0-255 or ALL]
If you entered 2 in Step 4, go to Step 9; otherwise, continue.
6 Prompt: NUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
7 Prompt: DIGIT*TYPE=
Enter: digit type or ALL
If you entered 3 in Step 4, go to Step 9; otherwise, continue.
8 Prompt: NAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
3 (national significant number)
4 (international significant number)
ALL
9 Prompt: HEXGTA=
Enter: hexadecimal global title address
10 Prompt: NSFI1=
Enter: (one of the following choices)
CDGTA
CDPA
STOP
If you enter STOP, go to Step 14; otherwise, continue.
11 Prompt: NSR1=
Enter: next screening reference
If you enter CDPA or CDGTA in Step 10, go to Step 12; otherwise, go to Step 14.
12 Prompt: NSFI2=
Enter: (one of the following choices)
CDPA
CDGTA
STOP
FAIL
If you enter STOP or FAIL, go to Step 14; otherwise, continue.
If you enter CDPA in Step 10, then the choices are: CDGTA, STOP, FAIL.
If you enter CDGTA in Step 10, then the choices are: CDPA, STOP, FAIL.
13 Prompt: NSR2=
Enter: next screening reference
14 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when CGGTA gateway screening
parameters are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR CGGTA
2 Prompt: SR=
Enter: screening reference
3 Prompt: SSN=
Enter: subsystem number or ALL
4 Prompt: GTF=
Enter: [1-4]
1 (NADDR); go to Step 8.
2 (TRANSTYPE); go to Step 5.
3 (TRANSTYPE, NUMPLAN, DIGTYPE); go to Step 5.
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR); go to Step 5.
5 Prompt: TRANS*TYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 4, go to Step 9; otherwise, continue.
6 Prompt: NUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
7 Prompt: DIGIT*TYPE=
Enter: digit type or ALL
If you enter 3 in Step 4, go to Step 9; otherwise, continue.
8 Prompt: NAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
3 (national significant number)
4 (international significant number)
ALL
9 Prompt: HEXGTA=
Enter: hexadecimal global title address
10 Prompt: NEWSSN=
Enter: subsystem number
The default is the current value.
11 Prompt: NEWGTF=
Enter: [1-4]
1 (NADDR); go to Step 15.
2 (TRANSTYPE); go to Step 12.
3 (TRANSTYPE, NUMPLAN, DIGTYPE); go to Step 12.
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR); go to Step 12.
12 Prompt: NEWTRA*NSTYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 11, go to Step 16; otherwise, continue.
13 Prompt: NEWNUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
14 Prompt: NDIGIT*TYPE=
Enter: new digit type or ALL
If you enter 3 in Step 11, go to Step 16; otherwise, continue.
15 Prompt: NEWNAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
2 (national significant number)
3 (international significant number)
ALL
16 Prompt: NEWHEX*GTA=
Enter: hexadecimal global title address
17 Prompt: NEWNSFI1=
Enter: (one of the following choices)
CDGTA
CDPA
STOP
If you enter STOP, go to Step 21; otherwise, continue.
18 Prompt: NEWNSR1=
Enter: new next screening reference
If you enter CDPA or CDGTA in Step 17, go to Step 19; otherwise, go to Step 22.
19 Prompt: NEWSNSF2=
Enter: (one of the following choices)
CDPA
CDGTA
STOP
FAIL
If you enter CDPA in Step 17, then the choices are: CDGTA, STOP, FAIL.
If you enter CDGTA in Step 17, then the choices are: CDPA, STOP, FAIL.
20 Prompt: NEWNSR2=
Enter: next screening reference
21 Prompt: NEWREM*ARK=
Enter: new remark
Constraints
Data tables
The following data tables are affected when CGGTA gateway screening parameters are
deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR CGGTA
2 Prompt: SR=
Enter: screening reference
3 Prompt: SUBSYS*NUM=
Enter: subsystem number or ALL
4 Prompt: GTF=
Enter: [1-4]
1 (NADDR); go to Step 8.
2 (TRANSTYPE)
3 (TRANSTYPE, NUMPLAN, DIGTYPE)
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR)
5 Prompt: TRANS*TYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 4, go to Step 9; otherwise, continue.
6 Prompt: NUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
7 Prompt: DT=
Enter: digit type or ALL
If you enter 3 in Step 4, go to Step 9; otherwise, continue.
8 Prompt: NAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
3 (national significant number)
4 (international significant number)
ALL
9 Prompt: HEXGTA=
Enter: hexadecimal global title address or ALL
The system shows the parameters.
Constraints
Data tables
The system retrieves the CGGTA gateway screening parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR CGGTA
2 Prompt: DSR=
Enter: screening reference or ALL
If you enter ALL, go to Step 10; otherwise, continue.
3 Prompt: DSSN=
Enter: subsystem number or ALL
If you enter ALL, go to Step 10; otherwise, continue.
4 Prompt: GTF=
Enter: [1-4]
1 (NADDR); go to Step 8.
2 (TRANSTYPE)
3 (TRANSTYPE, NUMPLAN, DIGTYPE)
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR)
5 Prompt: TRANS*TYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 4, go to Step 9; otherwise, continue.
If you enter ALL, go to Step 10.
Otherwise, go to Step 6.
6 Prompt: DNUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
7 Prompt: DDT=
Enter: digit type or ALL
If you enter 3 in Step 4, go to Step 9; otherwise, continue.
8 Prompt: DNAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
2 (national significant number)
3 (international significant number)
ALL
9 Prompt: DHEXGTA=
Enter: hexadecimal global title address or ALL
The system shows the parameters.
Constraints
Data tables
The following data tables are affected when CGPA gateway screening parameters are assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR CGPA
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
7 Prompt: LNKGID=
Enter: link set group identifier or ALL
8 Prompt: RI=
Enter: [0 or 1]
0 (route on global title address)
1 (route on PC in the routing label and SSN in CDPA)
9 Prompt: NSFIACG=
Enter: (one of the following choices)
CDPA
CDGTA
STOP
If you enter STOP, go to Step 11; otherwise, continue.
Note: If you enter 1 in Step 8, then the choices are CDPA and STOP; otherwise, CDGTA
and STOP.
10 Prompt: NSR=
Enter: next screening reference
11 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when CGPA gateway screening
parameters are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR CGPA
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
7 Prompt: LNKGID=
Enter: link set group identifier or ALL
8 Prompt: RI=
Enter: [0 or 1]
0 (route on global title address)
1 (route on PC in the routing label and SSN in CDPA)
ALL
9 Prompt: NEWPCSR=
Enter: (one of the following choices)
New point code start range
ALL; go to Step 11.
<RETURN> (current value)
10 Prompt: NEWPCER=
Enter: new point code end range or ALL
<RETURN> (current value)
11 Prompt: NEWSSN=
Enter: new subsystem number or ALL
<RETURN> (current value)
12 Prompt: NEWRI=
Enter: [0 or 1]
0 (route on global title address)
1 (route on PC in the routing label and SSN in CGPA)
13 Prompt: NEWNSFIACG=
Enter: (one of the following choices)
CDPA
CDGTA
STOP
If you enter STOP, go to Step 15; otherwise, continue.
Note: If you enter 1 in Step 12, then the choices are CDPA and STOP; otherwise, CDGTA
and STOP.
14 Prompt: NEWNSR=
Enter: next screening reference
15 Prompt: NEWREM=
Enter: new remark
Constraints
Data tables
The following data tables are affected when CGPA gateway screening parameters are deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR CGPA
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
If you enter ALL, go to Step 9; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
7 Prompt: LNKGID=
Enter: link set group identifier or ALL
8 Prompt: RI=
Enter: [0 or 1]
0 (route on global title address)
1 (route on PC in the routing label and SSN in CDPA)
The system shows the parameters.
Constraints
Data tables
The system retrieves the CGPA gateway screening parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR CGPA
2 Prompt: DSR=
Enter: screening reference or ALL
If you enter ALL, go to Step 9; otherwise, continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 9; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
If you enter ALL, go to Step 9; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: DSSN=
Enter: subsystem number or ALL
If you enter ALL, go to Step 9; otherwise, continue.
7 Prompt: DLNKGID=
Enter: link set group identifier or ALL
8 Prompt: DRI=
Enter: [0 or 1]
0 (route on global title address)
1 (route on PC in the routing label and SSN in CDPA)
ALL
The system shows the parameters.
Constraints
Data tables
The following data tables are affected when CDGTA gateway screening parameters are
assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR CDGTA
2 Prompt: SR=
Enter: screening reference
3 Prompt: SUBSYS*NUM=
Enter: subsystem number or ALL
4 Prompt: GTF=
Enter: [1-4]
1 (NADDR); go to Step 8.
2 (TRANSTYPE); go to Step 5.
3 (TRANSTYPE, NUMPLAN, DIGTYPE); go to Step 5.
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR); go to Step 5.
5 Prompt: TRANS*TYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 4, go to Step 9; otherwise, continue.
6 Prompt: NUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
7 Prompt: DIGIT*TYPE=
Enter: digit type or ALL
If you enter 3 in Step 4, go to Step 9; otherwise, continue.
8 Prompt: NAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
2 (national significant number)
3 (international significant number)
ALL
9 Prompt: HEXGTA=
Enter: hexadecimal global title address
10 Prompt: NSFI1=
Enter: (one of the following choices)
CDPA
STOP
If you enter STOP, go to Step 12; otherwise, continue.
11 Prompt: NSR1=
Enter: next screening reference
12 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when CDGTA gateway screening
parameters are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR CDGTA
2 Prompt: SR=
Enter: screening reference
3 Prompt: SUBSYS*NUM=
Enter: subsystem number or ALL
4 Prompt: GTF=
Enter: [1-4]
1 (NADDR); go to Step 8.
2 (TRANSTYPE); go to Step 5.
3 (TRANSTYPE, NUMPLAN, DIGTYPE); go to Step 5.
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR); go to Step 5.
5 Prompt: TRANS*TYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 4, go to Step 9; otherwise, continue.
6 Prompt: NUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
7 Prompt: DIGIT*TYPE=
Enter: digit type or ALL
If you enter 3 in Step 4, go to Step 9; otherwise, continue.
8 Prompt: NAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
2 (national significant number)
3 (international significant number)
ALL
9 Prompt: HEXGTA=
Enter: hexadecimal global title address
10 Prompt: NSUBSYS*NUM=
Enter: subsystem number or ALL
The default is the current value.
11 Prompt: NEWGTF=
Enter: [1-4]
1 (NADDR); go to Step 15.
2 (TRANSTYPE); go to Step 12.
3 (TRANSTYPE, NUMPLAN, DIGTYPE); go to Step 12.
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR); go to Step 12.
12 Prompt: NEWTRA*NSTYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 11, go to Step 16; otherwise, continue.
13 Prompt: NEWNUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
14 Prompt: NDIGIT*TYPE=
Enter: new digit type or ALL
If you entered 3 in Step 11, go to Step 16; otherwise, continue.
15 Prompt: NEWNAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
2 (national significant number)
3 (international significant number)
ALL
16 Prompt: NEWHEX*GTA=
Enter: hexadecimal global title address
17 Prompt: NEWNSFI1=
Enter: (one of the following choices)
CDPA
STOP
If you enter STOP or <RETURN>, go to Step 19; otherwise, continue.
18 Prompt: NEWNSR=
Enter: new next screening reference
19 Prompt: NEWREM*ARK=
Enter: new remark
Constraints
Data tables
The following data tables are affected when CDGTA gateway screening parameters are
deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR CDGTA
2 Prompt: SR=
Enter: screening reference
3 Prompt: SUBSYS*NUM=
Enter: subsystem number or ALL
4 Prompt: GTF=
Enter: [1-4]
1 (NADDR); go to Step 8.
2 (TRANSTYPE)
3 (TRANSTYPE, NUMPLAN, DIGTYPE)
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR)
5 Prompt: TRANS*TYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 4, go to Step 9; otherwise, continue.
6 Prompt: NUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
7 Prompt: DIGIT*TYPE=
Enter: digit type or ALL
If you enter 3 in Step 4, go to Step 9; otherwise, continue.
8 Prompt: NAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
2 (national significant number)
3 (international significant number)
ALL
9 Prompt: HEXGTA=
Enter: hexadecimal global title address or ALL
The system shows the parameters.
Constraints
Data tables
The system retrieves the CDGTA gateway screening parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR CDGTA
2 Prompt: DSR=
Enter: screening reference or ALL
If you enter ALL, go to Step 10; otherwise, continue.
3 Prompt: DSSN=
Enter: subsystem number or ALL
If you enter ALL, go to Step 10; otherwise, continue.
4 Prompt: GTF=
Enter: [1-4]
1 (NADDR); go to Step 8.
2 (TRANSTYPE)
3 (TRANSTYPE, NUMPLAN, DIGTYPE)
4 (TRANSTYPE, NUMPLAN, DIGTYPE, NADDR)
ALL
5 Prompt: DTRANS*TYPE=
Enter: [0-255 or ALL]
If you enter 2 in Step 4, go to Step 9; otherwise, continue.
6 Prompt: DNUM*PLAN=
Enter: (one of the following choices)
1 (ISDN/telephony)
3 (data)
4 (telex)
5 (maritime mobile)
6 (land mobile)
7 (ISDN/mobile)
ALL
7 Prompt: DDT=
Enter: digit type or ALL
8 Prompt: DNAD*DR=
Enter: (one of the following choices)
1 (subscriber number)
2 (national significant number)
3 (international significant number)
ALL
9 Prompt: DHEXGTA=
Enter: hexadecimal global title address or ALL
The system shows the parameters.
Constraints
Data tables
The following data tables are affected when CDPA gateway screening parameters are assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR CDPA
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
If you enter 1 or ALL or a range that includes 1, go to Step 7; otherwise, go to Step 8.
7 Prompt: SCMG=
Enter: SCMG format identifier or ALL
8 Prompt: NSFIA=
Enter: (one of the following choices)
APCSSN
STOP
If you enter STOP, go to Step 10; otherwise, continue.
9 Prompt: NSR=
Enter: next screening reference
10 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when CDPA gateway screening
parameters are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR CDPA
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
If you enter 1 or ALL or a range that includes 1, go to Step 7; otherwise, go to Step 8.
7 Prompt: SCMG=
Enter: SCMG format identifier or ALL
8 Prompt: NEWPCSR=
Enter: new point code start range or ALL
<RETURN> (current value)
If you enter ALL, go to Step 10.
9 Prompt: NEWPCER=
Enter: new point code end range or ALL
<RETURN> (current value)
10 Prompt: NEWSSN=
Enter: new subsystem number or ALL
<RETURN> (current value)
If you enter 1 or ALL or a range that includes 1, go to Step 11; otherwise, go to Step 12.
11 Prompt: NEWSCMG=
Enter: SCMG format identifier or ALL
<RETURN> (current value)
12 Prompt: NEWREM=
Enter: new remark
<RETURN> (current value)
13 Prompt: NEWNSFIA=
Enter: (one of the following choices)
APCSSN
STOP
<RETURN> (current value)
If you enter STOP, go to Step 15; otherwise, continue.
14 Prompt: NEWNSR=
Enter: next screening reference
The default is the current value.
Constraints
Data tables
The following data tables are affected when CDPA gateway screening parameters are deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR CDPA
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 8; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
If you enter 1 or ALL or a range that includes 1, go to Step 7; otherwise, go to Step 8.
7 Prompt: SCMG=
Enter: SCMG format identifier or ALL
Constraints
Data tables
The system retrieves the CDPA gateway screening parameters from the following data tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR CDPA
2 Prompt: DSR=
Enter: screening reference or ALL
If you enter ALL, go to Step 8.
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
5 Prompt: PCER=
Enter: point code end range or ALL
If you enter ALL, go to Step 8; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: DSSN=
Enter: subsystem number or ALL
If you enter 1 or ALL or a range that includes 1, go to Step 7; otherwise, go to Step 8.
7 Prompt: DSCMG=
Enter: SCMG format identifier or ALL
The system shows the parameters.
Constraints
Data tables
The following data tables are affected when APCSSN gateway screening parameters are
assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR APCSSN
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
The default value is none.
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
7 Prompt: REM*ARK=
Enter: remark
Constraints
Data tables
The following data tables are affected or referenced when APCSSN gateway screening
parameters are changed:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: CHANGE GWSCR APCSSN
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
7 Prompt: NEWPCSR=
Enter: (one of the following choices)
New point code start range
ALL; go to Step 9.
<RETURN> (current value)
8 Prompt: NEWPCER=
Enter: new point code end range or ALL
<RETURN> (current value)
9 Prompt: NEWSSN=
Enter: new subsystem number or ALL
10 Prompt: NEWREM=
Enter: new remark
Constraints
Data tables
The following data tables are affected when APCSSN gateway screening parameters are
deleted:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DELETE GWSCR APCSSN
2 Prompt: SR=
Enter: screening reference
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
The system shows the parameters.
Constraints
Data tables
The system retrieves the APCSSN gateway screening parameters from the following data
tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR APCSSN
2 Prompt: DSR=
Enter: (one of the following choices)
Screening reference
ALL; go to Step 6.
3 Prompt: LOG*NET=
Enter: logical network name or number
4 Prompt: PCSR=
Enter: point code start range or ALL
If you enter ALL, go to Step 6; otherwise, continue.
The point code valid range depends on the point code format that is configured for the
lognet.
5 Prompt: PCER=
Enter: point code end range or ALL
The point code valid range depends on the point code format that is configured for the
lognet.
6 Prompt: SSN=
Enter: subsystem number or ALL
The system shows the parameters.
Constraints
Data tables
The following data tables are affected when gateway screening threshold parameters are
assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR THRESH
2 Prompt: LSNAME=
Enter: link set name
3 Prompt: ACTREJ*ECTIONS=
Enter: [0-999999]
Enter the maximum number of activity rejections per unit time. This is optional.
4 Prompt: MIN*UTES=
Enter: [05, 10, 15, 20, or 30]
Enter the interval over which message and rejection thresholds apply. This is optional.
5 Prompt: MES*SAGES=
Enter: [0-999999]
Enter the maximum number of messages per unit time. This is optional.
6 Prompt: MIN*UTES=
Enter: [05, 10, 15, 20, or 30]
Enter the interval over which message thresholds apply. This is optional.
Constraints
Data tables
The system retrieves the gateway screening threshold parameters from the following data
tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR THRESH
2 Prompt: LSNAME=
Enter: link set name
The system displays the gateway screening threshold parameter values.
Constraints
Data tables
The following data tables are affected when gateway screening threshold parameters are
assigned:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: ASSIGN GWSCR THROTT
2 Prompt: REJ*ECTIONS=
Enter: [0-9999]
Enter the maximum number of rejections to be reported per unit time. This is optional.
3 Prompt: REJ*MINUTES=
Enter: [05, 10, 15, 20, or 30]
Enter the interval over which rejection limit applies. This is optional.
4 Prompt: ERR*ORS=
Enter: [0-9999]
Enter the maximum number of table errors to be reported. This is optional.
5 Prompt: ERRMIN*UTES=
Enter: [05, 10, 15, 20, or 30]
Enter the interval over which table error limit applies. This is optional.
Constraints
Data tables
The system retrieves the gateway screening threshold parameters from the following data
tables:
Procedure
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLAY GWSCR THROTT
2 Verify that the system displays the gateway screening throttle parameter values.
END PROCEDURE
Terms
Note: Move the mouse over a highlighted term in the document to see its definition. If you
clicked the term to get to this page, use the Back button on the browser to return to the page
containing the term.
Term Meaning
ACK Acknowledgement
ACTM Active, main
ADMIN Administration
AE1LK ATM over E1 (high-speed) link (processor)
AERM Alignment error rate monitor
AFTDEST Affected destination
AIN Advanced intelligent network
AIS Alarm inhibit signal
ALF Administration link frame
ALR Application location register
ANPD Application node PMC daughtercard
ANSI American National Standards Institute
AOS Automatic out of service
APCSSN Affected point code subsystem
AS Application server
ASP Application server process
AT1LK ATM/T1 link processor
ATM Asynchronous transfer mode
b/s Bit per second
BLKDPC Blocked destination point cod
BLKOPC Blocked originating point code
CCM Common channel manager
CCS Common channel signaling
CDGTA Called party global title address
Term Meaning
CDPA Called party address
CEDLK Channelized E1 duplex link
CELK Channelized E1 link
CGGTA Calling party global title address
CGPA Calling party address
CLASS Custom local area signaling services
COMM Communications
CP Control point
CSP Concerned signaling point
CTDLK Channelized T1 duplex link
CTLK Channelized T1 link
CTRL Control
DCE Date circuit equipment
DEN Distant end node
DPC Destination point code
DRST Destination restricted
DS0A Digital signal level 0A
DS0LK Digital signal level 0 link
DSS Distributed SS7 services
DTE Data terminal equipment
DUNA Destination unavailable
EQD Equipped
FISO Fault isolation
FLXMGR Flexible routing manager
GTA Global title address
GTF Global title format
GTM Global title modification
GTT Global title translation
GTWYLS Gateway link set
GWSCR Gateway screening
HELK High-speed E1 link
Term Meaning
HSL High-speed link
HSLK High-speed link processor
IP Internet protocol
IPL Initial program load
IPLK Internet protocol link processor
IPR Information and problem report
IPUA Internet protocol user adaptation processor
ISDN Integrated services digital network
ISERM In-service error rate monitor
ISUP ISDN user part
ITU International Telecommunication Union
kb/s Kilobit per second
LAS Logical application server
LED Light-emitting diode
LEF Link expansion frame
LIDB Line identification database
LM Layer management
LNP Local number portability
LSL Low-speed link
LTD Link timing distribution
M2PA MTP2 peer-to-peer adaptation layer
M3UA MTP3 user adaptation layer
MAINT Maintenance
MAP Mated application
MGC Media gateway controller
MMI Man-machine interface
MOPC Multiple originating point code
MOS Manually out of service
MPC Multiple point code
MPCPAR Multiple point code parameters
MRSP Modified restart procedure
Term Meaning
ms Millisecond
MSP Mobile service provider
MSU Message signal unit
MTNC Message transport network controller
MTP Message transfer part
NAK Negative acknowledgment
NIC Network indication controller
NNI Network node interface
NRP Number of retransmitted SSCOP protocol data units
NTP Network time protocol
OOS Out of service
OOSA Out of service automatically
OOSM Out of service manually
OOSMN Out of service manually, not operational
OPC Originating point code
OS Operating system
PC Point code
PCI Peripheral component interface
PCM Point code mapping
PCMAP Point code mapping
PCR Preventive cyclic retransmission
PDU Power distribution unit
PMC PCI mezzanine card
PXP Packet export processor
RCT Remote control terminal
RTT Round trip time
RX Receive
SAAL Signaling ATM adaptation layer
SACK Selective acknowledgement
SCCP Signaling connection control part
SCMG SCCP management
Term Meaning
SCP Signal control point
SCTP Stream control transmission protocol
SD Serial device
SEAS Signaling, engineering, and administration system
SG Signaling gateway
SI Service indicator
SIB Status indication busy
SIO Service information octet
SIP Session initiation protocol
SIPM SIP manager
SIPO Status indication processor outage
SLC Signaling link code
SLS Signaling link selection
SM System Manager
SP Signaling point
SPR Signaling point restart
SRTM Signaling route test message
SRTT Smoothed round trip time
SS7 Signaling system 7
SSCF Service-specific coordination function
SSCOP Service-specific, connection-oriented protocol
SSG Signaling server global
SSN Subsystem number
SSP Signaling selection point
STGE System timing generator for E1
SST Subsystem status test
STP Signal transfer point
SU Signal unit
TCA Transfer cluster allowed
TCP Transfer cluster prohibited
TERMLK Terminal link
Term Meaning
TFA Transfer allowed
TFP Transfer prohibited
TFR Transfer restricted
TLNP Triggerless local number portability
TMM Traffic metering and measurement
TNC Transport node controller
TT Translation type
TTMAP Translation type mapping
TX Transmit
TXL Transmit level
TXP Transmit prohibited
UIP User IP interface
UNEQD Unequipped
VOPC Virtual originating point code
XMIT Transmit
Introduction
This appendix contains the database engineering forms required to configure the 5070 SSG
database. The forms are arranged in the correct order for provisioning.
Table O lists the forms (alphabetically) that are located in this appendix and provides the
corresponding section or appendix where the form is discussed in detail.
Table O. Database configuration forms
Form Figure Section or Appendix
ATM over T1 high speed links Figure 27 thru Figure 29X Processors and links
Location: Date:
Node name:
Network indicator
Point code
Spare bits
Congestion
RCT support
TFR support
Destination lognet
Fields
Use the following list to complete the logical network form.
Constraints
No constraints apply to completing this form.
Location: Date:
Node name:
Logical network
Point code
Fields
Use the following list to complete the local node form.
Note: In smaller networks (those assigned network numbers 1-5), cluster number 0 is not used.
Telcordia determines the range of cluster numbers allowed in networks 1-5.
Constraints
The following constraints apply to completing the local node form:
• If the node is the primary point code, complete the primary point code information only.
• A local node form is required for the primary and each alias.
• The alias node name must be different from the name assigned to the 5070 SSG when the
network configuration is defined.
• The mate 5070 SSG must be assigned the same alias in its database as the local 5070 SSG.
• The mate 5070 SSG alias cannot be changed with this MMI.
Logical network
Point code
DSS alias (Y or N)
Fields
Use the following list to complete the alias for local node form.
Constraints
The following constraints apply to completing the alias for local node form:
• If the node name does not exist in the database, the MMI prompts for a new alias point
code.
• The new alias point code may contain any network number in the range of 1-255. The alias
network does not have to match the primary network.
• If the alias point code does not exist, the ASSIGN CCS ALIAS command adds the new alias
node name and point code to the database.
Node name:
Node role
Logical network
P*COMP
Fields
Use the following list to complete the CCS parameters form.
Constraints
No constraints apply to completing this form.
Logical network
IPR flag
Broadcast flag
Fields
Use the following list to complete the signaling point restart form.
Constraints
No constraints apply to completing this form.
Node name:
Logical network
Point code
SLS conversion (Y or N)
TFP broadcast (Y or N)
SPR enable (Y or N)
Request activation (Y or N)
Fields
Use the following list to complete the link set form:
Constraints
The number of active links must be the same at the 5070 SSG and the distant node.
PCMAP form
Complete one PCMAP form for each point code.
PCMAP form
Node name:
Logical network
Replace DPC
Low circuit ID
High circuit ID
Fields
Use the following list to complete the PCMAP form:
Constraints
No constraints apply to completing this form.
MOPC form
Complete one MOPC form for each point code.
MOPC form
Node name:
Fields
Use the following list to complete the MPC form:
Constraints
No constraints apply to completing this form.
Node name:
Display format (B or D)
Fields
Use the following list to complete the super link set form:
Constraints
No constraints apply to completing this form.
Linkset type
Logical network
Request activation (Y or N)
Format (B or D)
Fields
Use the following list to complete the administration processor form:
Constraints
No constraints apply to completing this form.
CHANGE, DISPLA PROCESS EQUIP * Pair column used for CEDLK or CTDLK only
Fields
Use the following list to complete the AE1LK, CTDLK, CELK, CEDLK, and HELK form:
Constraints
No constraints apply to completing this form.
Figure 15. Default link span form for AE1LK, CELK, CEDLK, and HELK
Default link span form for AE1LK, CEDLK, CELK, and HELK
Company name: Page: of
Location: Date:
CHANGE, DISPLA MAINT LKSPDF
Fields
Use the following list to complete the default link span form for AE1LK, CEDLK, CELK, and
HELK:
Constraints
No constraints apply to completing this form.
Fields
Use the following list to complete the default T1 link span form for CTDLK:
Constraints
No constraints apply to completing this form.
Link span
Use this form to change and display a link span.
Figure 17. Link span form for AE1LK, CTDLK, CEDLK, CELK, and HELK
Link span form for AE1LK, CTDLK, CEDLK, CELK, and HELK
Figure 18. Link span form for AE1LK, CTDLK, CEDLK, CELK, and HELK, part 2
Link span form for AE1LK, CTDLK, CEDLK, CELK, and HELK
Figure 19. Link span form for AE1LK, CTDLK, CEDLK, CELK, and HELK, part 3
Link span form for AE1LK, CTDLK, CEDLK, CELK, and HELK
Short OS threshold:
Short clear period:
Clear short threshold:
Frame slip short minor threshold:
Frame slip short major threshold:
Frame slip short OS threshold:
Frame slip short clear period:
Frame slip short clear threshold:
CRC4 OS one second threshold:
EBIT OS one second threshold:
UAS OS one second threshold:
Fields
Use the following list to complete the link span form for AE1LK, CEDLK, HELK, CTDLK, and
CELK:
Constraints
No constraints apply to completing this form.
Subtype:
Unit:
Link span:
Loopback type:
Fields
Use the following list to complete the link span loopback form:
Entry Link set SLC Link CSLS PSLS Routing Routing Activate
number name no. proc proc no.
subtype
1
Fields
Use the following list to complete the link form:
Constraints
The following constraints apply to completing the link form:
• A link must be assigned the same SLC at the 5070 SSG and the distant node.
• The link set must already be defined in the database.
• If two link sets are combined, the number of links assigned to each link set must be equal.
• A link can be assigned to only one link set.
• The processor associated with the link must be equipped before link assignment.
Entry Link set SLC Link Routing Pair Routing Span Channel Activate
number name no. proc proc no no. no.
subtype
1
Fields
Use the following list to complete the link form:
Constraints
The following constraints apply to completing the link form:
• A link must be assigned the same SLC at the 5070 SSG and the distant node.
• The link set must already be defined in the database.
• If two link sets are combined, the number of links assigned to each link set must be equal.
• A link can be assigned to only one link set.
• The processor associated with the link must be equipped before link assignment.
TX 49-208 9-113
Fields
Use the following list to complete the low-speed E1 link parameters form:
Constraints
The following constraints apply to completing the low-speed E1 link parameters form:
Baud rate (only for CTDLK) Low-speed data transfer rate 4600 b/s
9600 b/s
19.2 kb/s
High-speed data transfer rate 56 kb/s
64 kb/s
N2 octet appears only if the forward error-collection mechanism is selected.
Fields
Use the following list to complete the low-speed T1 link parameters form:
Constraints
The following constraints apply to completing the low-speed T1 link parameters form:
• The signal encoding value is the only link parameters for DS0A channels that can be
defined.
• The default values reflect Telcordia recommendation in TR-NWL-000-246.
Entry value___________
Link number
Parameter group
VPI 0-4095
VCI 0-65535
LINBDO
QSCLASS 0-3
CLKSCE
TXPUTP
ATMSCR
TMRDF D or U
COPTCC 100-2000 ms
25-500 ms
COPTKA
500-2000 ms
COPTNR
25-500 ms
COPTP
25-1000 ms
COPTID
0-1200 s
COPTPV
1-15 s
CFNNIT1
15-180 s
CFNNIT2
CFNNIT3 1000-25000 ms
30-1440 min
LMTRS
LMTNC 1000-6000 ms
LMTSUP 10-600 s
LMTLOS 500-10000 ms
LMTTAU 25-250 ms
EPSOEC 0-65535
SDPRETX 0-65535
HTAUTOC 0-65535
CPSOEC 0-65535
OPMAXCC 1-10
OPMAXPD 5-2120
OPMAXST 3-1021
CFNNIN1 50-50000
LMMXNRP 0-10
LMMEXSF 0-1000
LMQOSTH 100-1000
NUMINTL 1-25
NMITBLK 1-25
CFC1CTR 1-30
Fields
Use the following list to complete the ATM over E1 high-speed link forms:
Constraints
The following constraint apply when completing the ATM over T1 high-speed link forms:
• The congestion values must be set with the following criteria: RXL1AB < RXL1ON < RXL1DS
and TXL1AB < TXL1ON < TXL1DS < TXL2AB < TXL2ON < TXL2DS < TXL3AB < TXL3ON <
TXL3DS, with all values differing by at least 25 messages.
HSL parameters
Use this form to define physical HSL parameters.
TXONSET 240-1890
TXABAT 120-2040
Fields
Use the following list to complete the HSL parameters form:
Fields
Use the following list to complete the IPLK form:
Local IP entity (P or A)
Port ID (1 or 2)
Pair ID (A or B)
IP address
Netmask address
Fields
Use the following list to complete the hosts file form:
Note: After setting up the hosts file, you must remove and restore the affected processors to
pick up the new hosts file.
IP connection parameters
Use this form to define the IP connection parameters.
Link number
Destination IP address
Destination port
Source port
Fields
Use the following list to complete the IP connection parameters form:
Entry value___________
Link number
Parameter group
TXABATELVL1 0-100
TXONSETLVL1 0-100
TXDISCLVL1
0-100
TXABATELVL2 0-100
TXONSETLVL2
0-100
TXDISCLVL2
0-100
TXABATELVL3 0-100
TXONSETLVL3 0-100
TXDISCLVL3
0-100
RXABATE
0-100
RXONSET 0-100
RXDISC
0-100
TXABATE
0-100
TXONSET
0-100
ASSORETRAN
1-65535
Fields
Use the following list to complete the IPLK parameters form:
Constraints
No constraints apply to completing this form.
IP system parameters
Use this form to define the IP system parameters.
Memory 0-1000000000
Fields
Use the following list to complete the IP system parameters form:
Constraints
No constraints apply to completing this form.
AS name
Traffic mode
Inbound AS allowed
Outbound AS allowed
Preventive DUNA
Insufficient TFR
Fields
Use the following list to complete the application server form:
Constraints
The following constraints apply to completing the application server form:
• ASPs assigned to the particular AS should be deleted first before deleting the AS.
• If an AS is assigned to the route set master, you cannot delete the last ASP assigned to the
AS unless you delete the AS assigned to the route set master.
ASP name
AS name or ID
Activate
Destination IP address
Fields
Use the following list to complete the application server process form:
Constraints
The following constraints apply to completing the application server process form:
• The application server name or ID that is being used should exists in the application server
database.
• The IPUA ID must be in the configured IPUA processor range, but not necessarily equipped.
Entry value___________
ASP name or ID
ASSDOWNTRAN 1-65535
ASSORETRAN 1-65535
Fields
Use the following list to complete the UIP parameters form:
Constraints
No constraints apply to completing this form:
Memory 0-1000000000
Fields
Use the following list to complete the UIP system parameters form:
Constraints
No constraints apply to completing this form:
Fields
Use the following list to complete the UIP timers parameters form:
Constraints
No constraints apply to completing this form:
Complete an entry on the route set master form for each route set the 5070 SSG uses.
AS name or number
Priority level
Fields
Use the following list to complete the route set master form:
Constraints
The following constraints apply to completing the route set master form:
• The link set name must be defined on the link set form.
• Two link sets in a route set can have the same priority.
• Two link sets in a route set can be active at one time. Link set priority determines the
order in which the link sets are selected as the active route.
• The AS ID must be an application server that has been created and not used in any route
set master.
Note: Link sets that terminate at the specified node are usually assigned a higher priority
than link sets that terminate at an intermediate node such as the mate 5070 SSG.
Location: Date:
Node name
Logical network
Point code
Fields
Use the following list to complete the DPC route set form:
Constraints
The following constraints apply to completing the DPC route set form:
Note: The same route set master number can be assigned to more than one node.
Subsystem name
Node name
Logical network
Point code
Subsystem number
Reroute
Fields
Use the following list to complete the subsystem name form:
Constraints
The following constraints apply to completing the subsystem name form:
• The node name must be defined on the ordered route form or the link set form.
• When SSNs are duplicated in different nodes, the subsystem name must be unique for
each.
• The subsystem name represents both the node where the subsystem resides and the SSN.
TT form
Use this form to define each translation type in the TT form.
TT form
Node name:
Entry number
GTF
Translation type
Class service
IPR disable
Loop detection
Shared TT type
Fields
Use the following list to complete the TT form:
Constraints
The following constraints apply to completing the TT form:
• Assign one translation mechanism per TT. Each mechanism can be assigned to multiple
TTs. Any translation mechanism can be assigned to any TT. Each TT must be assigned a
translation mechanism.
• Ensure the originating and shared TT mechanisms, if applicable, are the same.
• The GTA value or range on the GTT entry form must be in the format defined by the
assigned translation mechanism on the TT form.
GTM definition
Use the GTM definition form to assign per-GTTGTM criteria and the associated GTM
parameters.
Location: Date:
Translation type
Numbering plan
NADDR
GTTTWEA
GTM number
NNADDR
DIGRS*LOC
NUMDR
DIGI*LOC
DIGDS*LOC
NUMDD
New GT address
Fields
Use the following list to complete the regular GTM form:
Node name:
Backup type
Final translation (Y or N)
Subsystem name
or
or
Logical network
Point code
Subsystem number
Fields
Use the following list to complete the GTT destination form. The form gives three options for
identifying a GTT destination: subsystem name, node name and SSN, and DPC and SSN. Only
one of these options requires data.
Constraints
The following constraints apply to adding a GTT destination entry:
• If the backup type is load-shared, at least two but no more than eight GTT destinations
must be defined.
• If the backup type is dominant replicate, the following constraints apply:
– At least two but no more than eight GTT destinations must be defined.
– The system organizes the destination data in order of highest to lowest preference.
The destination with the lowest cost route is the primary destination.
• If the backup type is weighted load-shared, the following constraints apply:
– At least two GTT destinations must be defined.
– Each destination requires a weight factor.
– The weight factors are not required to total 100.
• If the backup type is shared replicate, the following constraints apply:
– At least three GTT destinations must be defined (two primaries and one backup).
– Each primary destination requires a weight factor
– Each backup destination requires a weight factor of 0.
– The weight factors are not required to total 100.
• Full point code routing for final translations must be used as defined on the ordered route
form.
• The local node cannot be specified as a nonfinal translation destination.
• Check the GTT destination data against entries on other forms, as follows:
– The destination nodes must be defined in the database.
– For final translations, the destination subsystems must be in the database. Refer to
the Subsystem name form.
Translation type
Numbering plan
NADDR
GTTTWEA
Group name
Group number
GTM required
GTM number
NNADDR
DIGDS*LOC
NUMDD
New GT address
Fields
Use the following list to complete the regular GTT form:
Constraints
The following constraints apply to completing the regular GTT form:
• Check the global title translation data against entries on other forms:
– The TT cannot be defined as shared on the TT form.
– The translation mechanism defined on the TT form defines the GTA format required.
– The available GTT destination groups are defined on the GTT destination form.
Entry number
Subsystem name
Node name
Logical network
Point code
Subsystem number
Fields
Use the following list to complete the SCCP MAP form:
Constraints
The following constraints apply to completing the MAP form:
Use the CSP group form to assign the CSP groups to subsystems.
Entry number
Group name
Node name
Logical network
Point code
Fields
Use the following list to complete the CSP group form:
Constraints
The following constraint applies to completing the CSP group form:
• The node name and DPCs must be listed on either the ordered route form or the link set
form.
Entry number
Subsystem name
Node name
Logical network
Point code
Subsystem number
Group name
Fields
Use the following list to complete the CSP assignment form:
Constraints
The following constraints apply to completing the CSP assignment form:
• The group name must already be defined in the CSP assignment form.
• Many point codes can be assigned to the same CSP group, but only one CSP group can be
assigned to a subsystem.
• Subsystem names must already be defined on the subsystem name form.
• The node name must be defined on either the ordered route form or the link set form.
Screen
Remark
Fields
Use the following list to complete the gateway screening GTWYLS form:
Screening function
Screening reference
NOMatch
Logical network
Remark
Fields
Use the following list to complete the gateway screening OPC form:
Screening reference
Priority
Service indicator
Heading code 0
Heading code1
Remark
Fields
Use the following list to complete the regular GWSCR SIO form:
Screening function
Screening reference
NOMatch
Logical network
Remark
Fields
Use the following list to complete the regular GWSCR DPC form:
Screening reference
Logical network
Remark
Fields
Use the following list to complete the gateway screening AFTDES form:
Screening reference
Subsystem number
GTF
Translation type
Numbering plan
Digit type
NADDR
Hexadecimal GTA
Remark
Fields
Use the following list to complete the gateway screening CGGTA form:
Screening reference
Logical network
Subsystem number
Routing indicator
Remark
Fields
Use the following list to complete the gateway screening CGPA form:
Screening reference
Subsystem number
GTF
Translation type
Numbering plan
Digit type
NADDR
Hexadecimal GTA
Remark
Fields
Use the following list to complete the gateway screening CDGTA form:
Screening reference
Logical network
Subsystem number
Remark
Fields
Use the following list to complete the gateway screening CDPA form:
Screening reference
Logical network
Subsystem number
Remark
Fields
Use the following list to complete the gateway screening APCSSN form:
Activity rejections
Minutes 1
Messages
Minutes 2
Fields
Use the following list to complete the gateway screening threshold form:
Rejections
Rejection minutes
Errors
Messages
Error minutes
Fields
Use the following list to complete the gateway screening throttle form:
Location: Date:
T16 (1.4-2.0) s
SCCP timers
T5 (1.0-60.0) s T6 (1.0-60.0) s
Fields
Use the following list to complete the CCS timers form:
Constraints
No constraints apply to completing the CCS timers form.
This topic lists the MTP timers and SCCP timers that can be configured for a specific network
configuration or for testing purposes.
Note: After completing the procedures in this section, update your office records to reflect the
changes.
MTP timers
The MTP level 3 software uses a series of timers for functions such as link alignment,
changeover, changeback, and other procedures involving state changes. Do not confuse MTP
level 3 timers with SCCP timers.
Table P lists the timers, ranges, and definitions for MTP level 3 timers.
Table P. MTP timers
Timer Range Definition
T15 2.0-3.0 s Waiting for repeat signal routing set congestion test
T17 0.8-1.5 s Delay to avoid oscillation of initial alignment failure and link restart
T96 30.0-120.0 s Waiting to repeat signaling route set test message on lower priority route
SCCP timers
The SCCP subsystem uses timers to manage the status and initialization of network
subsystems. Table Q lists the timers, their ranges, and the definition for each SCCP timer.
Table Q. SCCP timers ranges and defaults
Timer Range (seconds) Definition
The system does not allow conflicting information to be entered into the database without
requesting confirmation.
Constraints
• The MTP T96 timer value must be greater than or equal to the T10 timer value if both
timers are enabled.
• The MTP T11 timer value must be at least 5 seconds greater than the T34 timer value if
both timers are enabled.
Data tables
When CCS timers are changed, the following data tables are updated:
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS TIMERS
2 Prompt: SYSTEM*TMR=
Enter: (one of the following choices)
S (system timer); go to Step 9.
L (logical network); continue.
3 Prompt: LOG*NET=
Enter: logical network name or number
Enter the logical network name of 1-16 characters or a number between the range of
0-31.
4 Prompt: TMR*TYP=
Enter: [MTP or SCCP]
MTP (message transfer part timers)
SCCP (signaling connection control part timers)
If you entered the logical network name or number of ITU protocol in Step 3 and MTP or
SCCP in Step 4, go to Step 5.
If you entered the logical network name or number of ANSI protocol in Step 3 and MTP
in Step 4, go to Step 6.
If you entered the logical network name or number of ANSI protocol in Step 3 and SCCP
in Step 4, go to Step 7.
5 Prompt: ITU*TMR=
Enter: (one of the following choices)
An MTP or SCCP timer number for ITU
MENU (description of MTP or SCCP timers)
6 Prompt: MTPC*TMR=
Enter: (one of the following choices)
An MTP timer number
MENU (description of MTP timers)
7 Prompt: SCPC*TMR=
Enter: (one of the following choices)
An SCCP timer number
MENU (description of SCCP timers)
Note: The next prompt depends on the number of the timer. If the timer is measured in
minutes, go to Step 8. If the timer is measured in seconds, go to Step 9.
8 Prompt: MIN*UTES=
Enter: number of whole minutes
9 Prompt: SEC*ONDS=
Enter: (one of the following choices)
An SCCP timer value in whole seconds; go to Step 11.
An MTP timer value in whole seconds; go to Step 10.
<RETURN>; go to Step 11.
If the value is complete, the new system shows the new timer value.
10 Prompt: TEN*THS=
Enter: [0-9]
The new system shows the new timer value.
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS TIMERS
2 Prompt: LOG*NET=
Enter: logical network name or number or ALL
3 Prompt: TMR*TYP=
Enter: [MTP or SCCP]
MTP (message transfer part timers); go to Step 5.
SCCP (signaling connection control part timers); go to Step 6.
If you entered the logical network name or number of ITU protocol in Step 2 and MTP or
SCCP in Step 3, go to Step 4.
If you entered the logical network name or number of ANSI protocol in Step 2 and MTP
in Step 3, go to Step 5.
If you entered the logical network name or number of ANSI protocol in Step 2 and SCCP
in Step 3, go to Step 6.
4 Prompt: ITU*TMR=
Enter: (one of the following choices)
An MTP or SCCP timer number for ITU
MENU (description of MTP or SCCP timers)
The system shows the value for the timer, go to Step 7.
5 Prompt: MTPD*TMR=
Enter: (one of the following choices)
An MTP timer number
MENU (description of MTP timers)
The system shows the value for the timer, go to Step 7.
6 Prompt: SCPD*TMR=
Enter: (one of the following choices)
An SCCP timer number
MENU (description of MTP timers)
The system shows the value for the timer.
The following topics provide information about the transport audit tasks:
• Audit fundamentals
• CCS audit status
Audit fundamentals
The SS7 transport audit ensures that interprocessor communications are operational and
avoids message loss in the network when interprocessor faults are detected. The SS7 transport
audit consists of four internal audits that serve as a backup to the operating system,
maintenance, and SS7 protocol mechanisms to detect and isolate faults. The audits isolate the
switch when multiple duplex failures occur by sending an SIPO signal on the links to the
adjacent nodes. This signal informs the nodes not to send traffic to the 5070 SSG although an
IPR is issued. Even if the audit parameters are set to eliminate SIPO signals, the system still
issues IPRs.
The routing processor to routing processor audit detects and isolates links that cannot be used
because of cluster isolation and multiple device failures. This audit initiates local cluster FISO
when communication to the CCM processors is not available.
The link processor to routing processor audit detects communication failures between link
processors and their routing processors. This audit performs FISO within the detecting link
processor.
The routing processor to link processor audit verifies that each link processor is addressable
from each active routing processors for outgoing SS7 traffic. This audit initiates local cluster
FISO if communication to the CCM processors is not available.
Audit timers
Timers associated with each audit are as follows.
Audit Timer
CCM 1 - CCM to routing processor
2 - CCM to NIC/link processor
Routing processor to 1 - Routing processor to routing processor
routing processor 2 - Routing processor to CCM
Routing processor to link 1 - Routing processor to link processor
processor 2 - Routing processor to CCM
Processor acknowledgment
Each audit requests positive acknowledgment from other processors. When the system fails to
receive positive acknowledgment, another request is issued. Failure on the specified number
of attempts results in the FISO procedures defined under each audit. Provisioning controls the
frequency and the number of retries for each audit occurrence before executing FISO
procedures.
Constraints
Data tables
The transport audit (W27) data table is accessed when the status of a CCS audit is checked.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: STATUS CCS AUDIT
2 Prompt: AU*DIT=
Enter: (one of the following choices)
CCM or 1 (CCM audit)
RPRP or 2 (routing proc to routing proc audit)
RPLK or 3 (routing proc to link proc audit)
Enter a single audit value or ALL to display all the audits.
3 Prompt: REF*RESH=
Enter: (one of the following choices)
Y (refresh the display); go to Step 4.
R (refresh the display); go to Step 4.
N (show the display once); go to Step 5.
NR (show the display once); go to Step 5.
4 Prompt: FREQ*UENCY=
Enter: refresh frequency in seconds
Constraints
Data tables
The transport audit (W27) data table is accessed when the status of a CCS audit is allowed.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: ALLOW CCS AUDIT
2 Prompt: AU*DIT=
Enter: (one of the following choices)
CCM or 1 (CCM audit)
RPRP or 2 (routing proc to routing proc audit)
RPLK or 3 (routing proc to link proc audit)
Enter a single value or ALL to display all the audits.
3 Prompt: OPT*ION=
Enter: (one of the following choices)
A (audit mode)
S (SIPO mode)
B (both audit and SIPO modes)
Constraints
Data tables
The transport audit (W27) data table is changed when a CCS audit is inhibited.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: INHIBIT CCS AUDIT
2 Prompt: AU*DIT=
Enter: (one of the following choices)
CCM or 1 (CCM audit)
RPRP or 2 (routing proc to routing proc audit)
RPLK or 3 (routing proc to routing link audit)
Enter a single value or ALL to display all the audits.
3 Prompt: OPT*ION=
Enter: (one of the following choices)
A (audit mode)
S (SIPO mode)
B (both audit and SIPO modes)
Constraints
Data tables
The transport audit (W27) data table is changed when the CCS audit is set.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: SET CCS AUDIT
2 Prompt: AU*DIT=
Enter: (one of the following choices)
CCM or 1 (CCM audit)
RPRP or 2 (routing proc to routing proc audit)
RPLK or 3 (routing proc to routing link audit)
Enter a single value or ALL to display all the audits.
3 Prompt: OPT*ION=
Enter: (one of the following choices)
A (audit mode)
S (SIPO mode)
B (both audit and SIPO modes)
Constraints
Data tables
The transport audit (W27) data table is changed when a CCS audit is cleared.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CLEAR CCS AUDIT
2 Prompt: AU*DIT=
Enter: (one of the following choices)
CCM or 1 (CCM audit)
RPRP or 2 (routing proc to routing proc audit)
RPLK or 3 (routing proc to link proc audit)
Enter a single value or ALL to clear all the audits.
3 Prompt: OPT*ION=
Enter: (one of the following choices)
A (audit mode)
S (SIPO mode)
B (both audit and SIPO modes)
• Frequency of audit
• Timer 1 and timer 2 expiration values
• Number of retries of the audit before timer 1 times out
• Number of retries of the audit before timer 2 times out
Constraints
Data tables
The transport audit (W27) data table is changed when a CCS audit is changed.
BEGIN PROCEDURE
ALERT
ALERT! Do not enter database provisioning MMIs if both TMM processors are removed from
service or are in the booted state. The data table accessed by an MMI can be corrupted.
1 Prompt: >
Enter: CHANGE CCS AUDIT
2 Prompt: CAU*DIT=
Enter: (one of the following choices)
CCM or 1 (CCM audit)
RPRP or 2 (routing proc to routing proc audit)
RPLK or 3 (routing proc to link proc audit)
3 Prompt: PERIOD1=
Enter: period between audit functions
4 Prompt: T1V*AL=
Enter: expiration timer 1 in seconds
5 Prompt: T1R*ET=
Enter: number of timer 1 retries
6 Prompt: T2V*AL=
Enter: expiration timer 2 in seconds
7 Prompt: T2R*ET=
Enter: number of timer 2 retries
Constraints
Data tables
The transport audit (W27) data table is accessed when a CCS audit is displayed.
BEGIN PROCEDURE
1 Prompt: >
Enter: DISPLA CCS AUDIT
2 Prompt: AU*DIT=
Enter: (one of the following choices)
CCM or 1 (CCM audit)
RPRP or 2 (routing proc to routing proc audit)
RPLK or 3 (routing proc to link proc audit)
Enter a single value or ALL to display all the audits.
The system displays the CCS audit mode.