Understanding SS7 Point Codes and Global Title Translation
Signaling System No. 7 relies on structured addressing to move call-control, mobility, and service messages between telecom nodes. Two concepts are central to that process: point codes identify signaling destinations, while Global Title Translation (GTT) converts subscriber-oriented addresses into routes that the signaling network can use.
These mechanisms support services across traditional PSTN environments, mobile networks, international gateways, and IP-based signaling deployments. Although many operators now carry SS7 traffic over SIGTRAN, the underlying addressing logic remains closely connected to MTP3, SCCP, ISUP, and network architecture principles.
Understanding the relationship between a point code, a subsystem number, and a global title makes it easier to troubleshoot routing failures, configure signaling transfer points, and assess exposure to SS7 security threats.
The Role Of A Point Code
A point code is a numerical address assigned to an SS7 signaling point. The address may identify a service switching point, signaling transfer point, service control point, international gateway, or another node participating in the signaling network. MTP3 uses the destination point code (DPC) to select the next signaling destination and the originating point code (OPC) to identify the sender.
Point codes are meaningful within a defined numbering plan. An international point code may differ from a national point code, even when both use similar decimal representations. Operators must therefore know which signaling network, region, or carrier context applies before interpreting an address.
The Signaling Link Selection (SLS) field also affects message distribution. It can balance traffic across parallel links or linksets, while the DPC determines the broader route. This combination allows signaling networks to scale without treating every physical link as a separate end-to-end connection.
Common Point Code Formats
ITU-T international networks commonly represent a point code as three decimal components, often written in a 3-8-3 format. The components identify an area or zone, a network, and a signaling point within that network. The exact presentation can vary by vendor, but the underlying code is a 14-bit value.
ANSI networks generally use a 24-bit point code divided into network, cluster, and member fields. Operators may display it as three decimal values, such as network-cluster-member, although software interfaces sometimes use hexadecimal or a single integer. National implementations can introduce additional conventions and translation rules.
The distinction between formats matters during interconnection. A gateway may need to map or screen point codes between national and international domains. Incorrect assumptions about bit length, field order, or numbering context can cause messages to be rejected or routed toward the wrong signaling point.
| Addressing Element | Primary Purpose | Typical Network Layer | Example Use |
|---|---|---|---|
| Point Code | Identifies a signaling node | MTP3 | Routes traffic to an STP or service node |
| DPC | Identifies the message destination | MTP3 routing label | Selects the next signaling destination |
| OPC | Identifies the message origin | MTP3 routing label | Supports return routing and screening |
| Subsystem Number | Identifies an application at a node | SCCP | Selects HLR, MSC, or service logic |
| Global Title | Represents a logical address | SCCP | Carries a dialed number or subscriber identity |
| GTT Result | Resolves a logical address | SCCP/STP | Produces a point code and often an SSN |
Global Titles In SCCP
A Global Title is an address that does not directly identify a signaling point. It may contain an international mobile subscriber identity, mobile station ISDN number, national directory number, or another digit string used by an application. SCCP carries this information in its Called Party Address so the network can determine where the message should go.
A Global Title includes parameters such as translation type, numbering plan, encoding scheme, and nature of address. These fields tell an STP how to interpret the digits. For example, a mobile-network query might use an E.214 or E.164-related numbering plan, while a service application may use a different national format.
GTT is valuable because the originating node does not need to know the current point code of the destination application. Instead, it sends a logical address to an STP, which applies configured rules and discovers the appropriate route.
How Global Title Translation Works
During translation, an STP examines the called party address and matches it against a translation table. The match can use a complete number, a prefix, numbering-plan indicators, or other address attributes. The result usually supplies a destination point code and subsystem number, and may also modify the Global Title or routing indicator.
The routing indicator determines whether SCCP should continue using the Global Title or route directly by point code and subsystem number. A translated message may therefore leave the STP with a resolved DPC and SSN, ready for delivery to an HLR, VLR, MSC, SCP, or another application endpoint.
Translation tables must account for number ranges, roaming partners, country codes, service identifiers, and fallback routes. A missing prefix, an incorrect translation type, or an unexpected digit format can produce errors such as “no translation for address” or route traffic to an unreachable destination.
Point Codes, SSNs, And SIGTRAN
A point code identifies the host signaling node, while the subsystem number identifies a particular application on that node. For instance, a single signaling point may support several SCCP users, with separate SSNs for mobility management, short message service, or intelligent network functions.
In SIGTRAN deployments, M3UA transports MTP3-user signaling such as SCCP and ISUP over IP. M3UA still uses signaling point codes and routing contexts, so moving links from TDM to Ethernet does not eliminate the need for sound SS7 addressing. SCTP provides transport resilience, but it does not correct an invalid GTT rule or an incorrect DPC.
Network engineers should distinguish physical connectivity from signaling reachability. An SCTP association can be established while SCCP messages fail because the point-code configuration, routing key, ASP state, or translation table is wrong.
Security And Operational Controls
GTT is a powerful routing function and a significant security control point. Inadequate filtering can allow unauthorized parties to send location queries, subscriber-data requests, or message-routing traffic toward sensitive network elements. Exposed signaling interfaces have historically been abused for tracking, fraud, interception, and service disruption.
Operators should apply strict screening based on origin, destination, Global Title ranges, application context, and roaming relationships. Translation rules should follow least-privilege principles: a partner should receive only the routes and services required for legitimate business operations.
Useful operational practices include:
- Maintain an authoritative inventory of point codes, SSNs, linksets, and translation prefixes.
- Validate ITU, ANSI, and national numbering formats before configuring interconnects.
- Log rejected translations and investigate unexpected Global Title patterns.
- Test failover routes without allowing broad wildcard translations.
- Review SIGTRAN access controls, SCTP associations, and firewall policies together.
Regular testing should include normal calls, roaming transactions, SMS routing, database queries, and failure scenarios. Teams needing clarification about training resources or signaling architecture can use training support to request further information.
Point codes and Global Title Translation work together as a layered addressing system. MTP3 uses point codes to route toward signaling nodes, while SCCP uses Global Titles and subsystem numbers to locate applications and services. Once those layers are understood, faults can be isolated more quickly and network changes can be implemented with greater control.
Apply the same discipline to legacy SS7 and SIGTRAN environments: document every address, verify each translation boundary, monitor rejected traffic, and restrict access to trusted signaling relationships. That approach turns a complex routing system into an auditable and manageable part of the telecom network.
