SS7 Point Code Format: 14-Bit, 24-Bit, And Variable Length
Point codes identify signaling nodes within Signaling System No. 7 networks. They allow MTP3 and related signaling layers to determine where a message originated and where it must be delivered. A point code may represent a signaling point, signal transfer point, or service switching point, depending on the network design.
The number of bits used for a point code depends on the SS7 variant, geographic standard, and equipment configuration. ITU-T networks commonly use 14-bit codes, while ANSI-based deployments generally use 24-bit codes. Variable-length references also appear in software interfaces, provisioning systems, and protocol adaptations such as SIGTRAN.
Understanding these formats is essential when configuring links, routing tables, signaling point names, and M3UA or SUA associations. A mismatch can cause rejected messages, inaccessible destinations, or routing loops even when the physical or IP connection is working correctly.
Why Point Codes Matter In SS7
An SS7 point code is similar to an address within a signaling network, but it should not be confused with an IP address or telephone number. MTP3 uses the originating point code (OPC) and destination point code (DPC) in its routing label to forward signaling messages between nodes.
The DPC identifies the intended signaling destination. The OPC identifies the node that sent the message. Together with the service indicator and signaling link selection value, these fields help the network select the appropriate route and maintain load sharing across available links.
Point codes are significant for ISUP call setup, SCCP transactions, MAP signaling, and many other SS7 applications. A correctly formatted code must be interpreted consistently by every signaling point involved in the route.
The 14-Bit ITU-T Format
The traditional international SS7 point code uses 14 bits. In common ITU-T notation, these bits are displayed as three decimal components, often written in a pattern such as zone-area-member. A frequently encountered division is 3 bits, 8 bits, and 3 bits, giving component ranges of 0–7, 0–255, and 0–7.
A point code such as 2-145-6 is therefore a structured representation of a binary value, not three independent addresses. The punctuation is a human-readable convention used in provisioning tools, network diagrams, and operations manuals. Vendors may display the same code with different separators or leading zeros.
International and national networks can apply local conventions to the available 14-bit space. For that reason, engineers should confirm the exact bit ordering and component interpretation in the applicable ITU-T recommendation and vendor documentation.
The 24-Bit ANSI Format
ANSI SS7 networks commonly use a 24-bit point code. The best-known presentation divides the code into three eight-bit fields: network-cluster-member. Each component can range from 0 through 255, producing a much larger address space than the 14-bit ITU-T model.
For example, an ANSI point code may appear as 245-18-7. The first value can identify a network, the second a cluster, and the third an individual signaling point. This hierarchy makes the format useful for large national networks containing many switches and signal transfer points.
The exact interpretation still depends on the carrier and implementation. Some equipment uses terms such as network, cluster, and member, while other systems expose the code primarily as a 24-bit integer. Engineers should verify whether a management interface expects dotted, hyphenated, decimal, or hexadecimal notation.
| Characteristic | ITU-T Point Code | ANSI Point Code | Variable-Length Representation |
|---|---|---|---|
| Common size | 14 bits | 24 bits | Depends on protocol or implementation |
| Typical display | 3-8-3 components | 8-8-8 components | Decimal, hexadecimal, or packed field |
| Common use | International and many national networks | North American networks and variants | Software, gateways, and adaptations |
| Main risk | Incorrect component order | Wrong network/cluster/member value | Ambiguous padding or truncation |
What Variable Length Means
Variable length does not always mean that an MTP3 routing label can contain an arbitrary number of point-code bits. In many cases, the signaling standard defines a fixed field for a particular network variant, while administration software accepts point codes in different textual forms.
A gateway might store a point code as a 32-bit integer even when only 14 or 24 bits are valid. Another platform may use a configurable point-code length, allowing the same signaling stack to support ITU-T, ANSI, or regional variants. Unused high-order bits must be handled consistently so that two systems do not interpret the same value differently.
SIGTRAN introduces another layer of abstraction. M3UA transports SS7 user-part traffic over IP, but its signaling point code parameters still have to match the selected SS7 variant. The IP transport does not remove the need to define point-code size, format, and routing context correctly.
Point Codes And Global Titles
A global title is a different addressing concept used primarily by SCCP. It can contain digits such as a telephone number, service access code, or other translated address. A signaling point code identifies a node, while a global title may identify a subscriber, application, or service that must be translated to a destination point code.
Global title translation (GTT) can convert a digit string into a DPC and subsystem number. This makes SCCP capable of routing a message even when the sender does not initially know the final signaling point. Confusing a global title with a point code often leads to incorrect SCCP routing rules.
For broader study of MTP3, ISUP, signaling links, and protocol behavior, the SS7 learning resource provides related training material. It is useful to compare point-code addressing with the other identifiers present in a complete SS7 message.
Configuration Checks For Engineers
Before activating an SS7 route or SIGTRAN association, verify the point-code format at every interface. The following checks reduce errors during interconnection and migration:
- Confirm whether the network uses ITU-T 14-bit, ANSI 24-bit, or another regional format.
- Check the component order, permitted ranges, separators, and leading-zero rules.
- Compare the local point code, remote point code, OPC, and DPC in every routing entry.
- Verify how the signaling gateway stores and transmits unused bits.
- Test SCCP global title translation separately from MTP3 point-code routing.
Operational logs should display both the formatted point code and its numeric or hexadecimal value when possible. This makes it easier to detect a byte-order problem, an incorrect field width, or a configuration copied from a different SS7 variant.
Avoiding Common Interworking Errors
A frequent mistake is copying an ANSI point code into an ITU-T field without converting its structure. Another is treating a displayed value such as 3-12-4 as a universal three-part format. The same punctuation can represent different bit allocations on different platforms.
Interworking gateways also require careful attention to point-code translation. A gateway may present one code toward an external carrier and another internally, while maintaining OPC and DPC mappings across the boundary. Routing keys, application servers, and M3UA traffic modes must reflect those translations.
Accurate documentation should state the standard, bit width, component layout, and numerical representation. Recording only a short point-code value leaves too much room for interpretation during troubleshooting or network expansion.
Use the correct point-code model as the foundation for every SS7 routing decision, then validate it through signaling traces and gateway logs. Study the binary layout, confirm the vendor’s notation, and test both local and interworking paths before carrying production traffic.
