Introduction

The SS7 network configuration for the EAGLE requires linksets and routes. These entities use point codes, and these point codes must be defined in the destination point code table of the database. A destination is a node in any network that is uniquely identified by a point code in conjunction with a network indicator. The destination is always the node’s true point code.

The EAGLE supports three types of networks and nodes to carry SS7 traffic, using TCP/IP technology:

• ANSI
• ITU International (ITU-I)
• ITU National (ITU-N)

When nodes in different networks wish to communicate, each node must have its own true point code and an alternate point code for each of the network types involved. For example, if node 1 in an ANSI network, node 2 in an ITU-N network, and node 3 in an ITU-I network wish to communicate with each other, node 1 must have an ANSI true point code and one alternate point code each for the ITU-N and ITU-I network. Node 2 must have an ITU-N true point code and one alternate point code each for the ANSI and ITU-I network. Node 3 must have an ITU-I true point code and one alternate point code each for the ANSI and ITU-N network.

Figure 2-1 shows an example of a mixed network with ANSI, ITU-I, and ITU-N nodes. Each node has one true point code and two alternate point codes.

Figure 2-1 Mixed Network with ANSI, ITU-I, and ITU-N Nodes

The node’s true point code is also called the destination point code.

This chapter discusses the method for configuring destination point codes (DPCs) in the database of the EAGLE. Destination point codes can be one of five types:

• Full point codes used for SS7 routing. A full point code is a point code containing numbers in each portion of the point code, for example, 111-011-100. The full point code can be in one of three formats, ANSI, ITU international, or ITU national. See the Point Code Formats section for more information on the point code formats. The EAGLE must have a full point code for each network type (ANSI, ITU-N, ITU-I) it is connected to.
• Secondary point codes, used by the Multiple Point Code Support feature. A secondary point code is a point code assigned to a full point code and used as if they were the actual EAGLE point code. Secondary point codes can be in one of three formats: ANSI, ITU international, or ITU national. The format of the secondary point code must be the same as the format of the full destination point code. See the Multiple Point Code Support section for more information on secondary point codes.
• Cluster destination point codes, used by the cluster routing and management (CRMD) feature and nested cluster routing feature. A cluster point code is an ANSI point code containing numbers in the network identifier and network cluster portions of the point code, and an asterisk (*) in the network cluster member field of the point code, for example, 111-011-*. See the Cluster Routing and Management Diversity (CRMD) section and the Nested Cluster Routing section for more information on cluster point codes.
• Network routing point codes, used by the network routing feature. A network routing point code is an ANSI point code containing a number in the network identifier portion of the point code, and asterisks (*) in the network cluster and network cluster member portions of the point code, for example, 111-*-*. See the Network Routing section for information on network routing point codes.
• Proxy point codes, used by the Proxy Point Code feature. A proxy point code is a point code that assumes the point code of another node in order to ease the migration of deploying an STP in a network with direct-connect links into other networks. See the Proxy Point Codes section for more information about proxy point codes.

The Cluster Routing and Management Diversity (CRMD) feature, the nested cluster routing feature, the multiple point code support feature, and the network routing features are also discussed in this section.

In order to complete the definition of linksets and routes, destination point codes are required to be in the database. Even though linksets use adjacent point codes, the adjacent point code of a linkset must be defined in the destination point code table of the database.

The procedures shown in this chapter use a variety of commands. If more information on these commands is needed, go to Commands User's Guide to find the required information.