Configuring SS7 Point Code Types Across Telecom Networks
Point codes are the addressing system of Signaling System No. 7. They allow signaling transfer points, service switching points, signal control points, and other network elements to identify one another during call setup, mobility procedures, database queries, and service activation.
Correct configuration depends on the numbering plan in use, the signaling network indicator, and the relationship between national and international signaling domains. A point code that is valid inside one operator’s network may be meaningless or ambiguous when presented to an international gateway.
Understanding Point Code Scope
An international point code identifies a signaling point within the global SS7 network. ITU-T signaling uses a 14-bit point code, commonly displayed in a 3-8-3 format. The fields represent a signaling region, network, and signaling point, although exact administrative interpretations can vary by numbering authority.
A national point code is assigned for use inside a country or national signaling domain. It may use the same 14-bit capacity as an ITU international point code, but the national numbering plan determines how the bits are allocated. The national or international meaning is therefore controlled by the network context and signaling indicator, not simply by the decimal appearance of the code.
Reading SS7 Point Code Formats
MTP3 carries the destination point code, originating point code, and signaling link selection information in the routing label. The service information octet also includes the network indicator, which helps a node determine whether a message belongs to an international, national, spare, or operator-defined network.
ANSI networks generally use 24-bit point codes displayed as three eight-bit values, such as 123-45-67. In this structure, the fields are commonly described as network, cluster, and member. ITU-T networks usually use 14-bit codes, while regional systems can apply local display conventions that should never be assumed without checking the operator’s numbering plan.
| Point Code Context | Typical Size | Common Display | Main Use |
|---|---|---|---|
| ITU international | 14 bits | 3-8-3 | Global signaling relationships |
| ITU national | 14 bits | Nationally defined | Domestic signaling networks |
| ANSI | 24 bits | 8-8-8 | North American and compatible networks |
| ANSI cluster | Part of 24 bits | Network-cluster-member | Grouping related signaling points |
| Gateway translation | Varies | Configured by operator | Mapping between signaling domains |
Planning National And International Assignments
Begin with an authoritative inventory of every signaling point, including STPs, MSCs, HLRs, service control points, media gateways, and signaling gateways. Reserve separate ranges for production, disaster recovery, laboratory systems, and future expansion. Avoid assigning codes from an unapproved range merely because they appear unused.
International gateways require particular care. A gateway may translate or filter point codes between a national network and an international signaling network. The destination point code, originating point code, global title translation rules, and network indicator must agree with the adjacent carrier’s configuration.
A numbering spreadsheet should record the point code, node name, physical location, signaling role, linkset, adjacent nodes, and routing status. Keeping this information synchronized with MTP3 configuration reduces errors during rerouting and maintenance.
Configuring ANSI Cluster And Member Codes
In an ANSI-style point code, the cluster identifies a logical group of signaling points, while the member identifies an individual node within that group. For example, several STPs or service platforms may share a network and cluster value while using unique member values. The exact operational meaning depends on the carrier’s engineering rules.
Cluster planning should reflect actual routing and redundancy. Nodes that serve the same geographic or logical area can be grouped consistently, but a member code must never be duplicated within the scope where routing decisions are made. Duplicate codes can create message loops, unreachable destinations, or incorrect route selection.
When connecting ANSI and ITU equipment, do not copy the displayed decimal code directly between systems. Use a signaling gateway or protocol adaptation layer that understands the different point-code lengths, formats, and network indicators.
Validating Routing And Network Behavior
After assigning codes, verify local routing tables, linksets, route sets, and adjacent point-code definitions. Confirm that the destination point code for each test message is reachable through the intended signaling link, while the originating point code identifies the correct node in returned messages.
Use MTP3 management procedures to observe transfer prohibited, transfer allowed, transfer restricted, and signaling route-set test events. These messages reveal whether a point code is correctly advertised and whether alternate routes operate as designed.
Testing should include normal traffic, link failure, STP failover, gateway translation, and restoration. Call routing alone is insufficient: SCCP, TCAP, ISUP, SMS, roaming, and database transactions may exercise different destinations and routing rules.
Avoiding Common Configuration Errors
A frequent mistake is treating national and international point codes as interchangeable. Another is confusing a global title, subsystem number, or telephone number with an SS7 point code. These identifiers can work together, but they serve different layers and are configured in different tables.
Operators should also review software defaults. A platform may display codes in decimal, hexadecimal, or a vendor-specific notation, and an incorrectly selected network indicator can cause valid messages to be discarded. Documentation from the national numbering authority and adjacent carrier should take priority over generic examples.
For vendor-specific interpretation, migration planning, or troubleshooting, the SS7 training team can help clarify how point codes interact with MTP3, SIGTRAN, and gateway architecture.
Recommended Configuration Practices
Use a controlled engineering process before enabling new point codes:
- Maintain one approved inventory for national, international, and cluster assignments.
- Document the point-code format and network indicator for every signaling domain.
- Reserve separate ranges for production, testing, recovery, and planned expansion.
- Test routing failures and gateway translation before carrying live traffic.
- Monitor MTP3 management messages and audit configuration changes regularly.
Well-designed point-code administration creates a stable foundation for ISUP call control, SCCP addressing, TCAP transactions, and SIGTRAN transport. Apply the numbering plan consistently, validate every route across network boundaries, and keep operational records aligned with the live configuration. For assistance with SS7 addressing, protocol behavior, or deployment planning, use the available contact channel to arrange expert guidance.
