Signaling Point Code Formats Across Global SS7 Networks
Signaling Point Codes (SPCs) identify nodes in Signaling System No. 7 networks, allowing switches, signal transfer points, service control points, and other elements to exchange messages. Their format varies by signalling standard and national telecommunications environment, so a code that looks valid in one network may be meaningless or misrouted in another.
For engineers working with SS7, SIGTRAN, MTP3, and SCCP, understanding these differences is essential. The distinction matters in Australian carrier interconnects, international gateways, roaming arrangements, and migrations from traditional TDM signalling to IP-based transport.
| Variant | Common length | Typical structure | Main deployment |
|---|---|---|---|
| ITU-T | 14 bits | Zone–area–member, often 3-8-3 | International and many national networks |
| ANSI | 24 bits | Network–cluster–member, often 8-8-8 | United States, Canada, and related deployments |
| China | 24 bits | Three 8-bit fields, with national conventions | Mainland Chinese domestic networks |
Why Point Codes Matter
An SPC is an address at the MTP3 layer. It tells the signalling network where a message originated, where it should finish, or which signalling transfer point should relay it. MTP3 uses the destination point code, originating point code, and signalling link selection information to support routing and load sharing.
The code is not a telephone number, subscriber identity, or IP address. A mobile number used in Sydney or Melbourne may be translated through several signalling layers before an ISUP, MAP, or SCCP message reaches its destination. Australian operators such as Telstra and Optus also maintain network-specific routing policies that are not visible from the point code alone.
For training records and change control, an engineering team may keep code assignments beside diagrams and interface notes in shared network documentation. This helps prevent a correctly formatted code from being applied to the wrong signalling domain.
ITU-T Point Code Structure
The ITU-T format uses 14 bits and is commonly written as three decimal components, often described as zone, area, and signalling point. The familiar representation is 3-8-3, although display conventions can differ between equipment suppliers. The complete value is more important than the punctuation used to show it.
A typical ITU-T point code might appear as 5-231-4. The first field identifies a broad region, the second provides a more detailed area value, and the final field identifies the node. These fields are bit groupings rather than universal geographic labels, so engineers should confirm the operator’s allocation plan before interpreting them literally.
ITU-T codes are widely encountered in international signalling and in networks influenced by European or Asia-Pacific standards. An Australian international gateway may communicate with an ITU-T-based partner while using a separate national numbering and routing scheme internally.
ANSI Point Code Structure
ANSI point codes contain 24 bits and are commonly displayed as three eight-bit fields, such as 245-16-7. These fields are often called network, cluster, and member. Each component can range from 0 to 255, although individual administrations reserve values and apply local allocation rules.
The larger address space supports detailed national network design. An ANSI network may assign clusters to geographic regions, switching platforms, or carrier domains, while member values identify individual signalling points. This arrangement is common in North American systems and in equipment that supports ANSI-style interconnection.
A frequent configuration error occurs when a 14-bit ITU-T value is entered into an ANSI field, or when an ANSI point code is shortened during conversion. The result may pass basic syntax checks while still identifying the wrong node. Translation tables should therefore record the source format, destination format, and any gateway rule.
China Point Code Conventions
Mainland Chinese SS7 networks generally use a 24-bit point code divided into three eight-bit sections. The written form may resemble an ANSI code, but the field names and operational meaning can follow Chinese national standards and carrier-specific allocation plans.
This similarity creates a practical risk. Engineers should not assume that an 8-8-8 code has ANSI semantics simply because it contains three values between 0 and 255. A Chinese operator may document the fields using national, regional, and signalling-point concepts, while a vendor interface may use different labels.
International interconnect projects should capture the exact notation, bit order, and translation behaviour supplied by the Chinese carrier. This is particularly important for roaming, international SMS, and gateway links where messages cross from an ITU-T environment into a domestic 24-bit network.
Translation, SCCP, and SIGTRAN
Point-code translation is often performed at a signalling gateway or STP. In SIGTRAN deployments, SCTP transports the signalling connection over IP, but MTP3 or an M3UA adaptation layer still needs consistent point-code information. Changing the transport medium does not remove the addressing rules.
SCCP adds another layer through subsystem numbers and global titles. A point code may identify the next signalling node while a global title identifies a service destination such as a home location register. The relationship between these values is explained in this guide to SCCP routing combinations.
In Australia, routing plans must also fit the Telecommunications Act 1997, ACMA requirements, carrier agreements, and operational controls for services such as emergency communications. NBN migration changes access technology, but it does not automatically eliminate SS7 dependencies in mobile core, legacy interconnect, or enterprise voice platforms.
Practical Checks for Australian Networks
A reliable point-code register should distinguish the signalling standard from the equipment vendor’s display format. It should also identify whether a value belongs to a national network, an international gateway, an STP pair, or a test environment.
Useful checks include:
- Confirm whether the interface expects ITU-T, ANSI, or a China-specific 24-bit format.
- Record both the displayed value and its binary or decimal representation.
- Validate originating and destination point codes together with the routing context.
- Check SCCP global-title and subsystem-number translations separately.
- Test failover across paired STPs, signalling gateways, or SIGTRAN associations.
- Keep production, laboratory, and partner-network assignments clearly separated.
Legacy documentation can contain unrelated pages and misleading labels, especially on older portals. A page about casino audio settings, for example, should never be treated as evidence for a signalling parameter merely because it sits beside telecom material in a search result.
The key principle is simple: an SPC is meaningful only within its numbering plan and signalling context. Always identify the format, verify the bit structure, confirm the operator’s allocation rules, and test translations before placing a point code into a live Australian or international network.
