SS7 Point Code Management in Nested STP Hierarchies
Signalling System No. 7 still carries most voice and SMS control traffic across Australian networks, even as IP-based alternatives have spread through the National Broadband Network rollouts. Every signalling node in these networks is identified by a numeric address called a point code, and once operators deploy nested Signal Transfer Point hierarchies, the management of those codes becomes a discipline of its own.
In a country where one carrier might operate tandems in Sydney, Perth, Brisbane and Adelaide simultaneously, careful point code administration prevents routing loops, misdelivered ISUP messages and security exposure at the network edge. The same discipline supports the regulatory framework under the Telecommunications Act 1997 enforced by the Australian Communications and Media Authority.
Point Code Fundamentals in STP Design
A point code is the numeric identifier that lets every signalling node reach every other node through the MTP3 layer. In Australia, where Telstra, Optus and TPG assets all coexist under ACMA oversight, codes must be allocated so that no two switches conflict. The structure follows ITU-T recommendations, with 14-bit or 24-bit variants depending on the network origin.
A signalling point acts as an end node or a relay. When it relays, it is treated as a Signal Transfer Point, and STPs are placed in hierarchies so traffic can pass between regions without each end node holding a full routing table. Managing these nested structures is what keeps call setup and short message transit reliable across long corridors such as Sydney to Darwin.
Anatomy of a Nested STP Hierarchy
A nested architecture places one layer of transfer points inside another, usually separated by region or carrier domain. At the top sit national pairs, frequently hosted in Sydney, Melbourne and Brisbane. Below them are regional STPs that aggregate traffic from local tandems, and at the bottom sit the service switching points that originate ISUP or MAP messages.
The deeper the nesting, the more important accurate mapping becomes. A misconfigured member field on a regional STP can cause messages to bounce between layers rather than be delivered, which is why operators align cluster and member values with geographic zones. Some carriers add a third layer for redundancy, turning a tree into a shallow mesh suitable for national traffic volumes.
Addressing Rules and Cluster Allocation
Point codes are usually split into three fields: network indicator, cluster and member. The network indicator separates national from international traffic, while within Australia operators generally use national codes only. The cluster field groups members that share a parent STP, simplifying route aggregation in nested designs.
| Field | Range (14-bit example) | Purpose in nested design |
|---|---|---|
| Network Indicator | 0–3 | Separates national from international routes |
| Cluster | 0–15 or 0–255 | Groups members under a shared parent STP |
| Member | 0–255 | Identifies the signalling point inside the cluster |
| Spare bits | varies | Reserved for future MTP3 expansion |
In nested topologies, cluster numbers are usually aligned with regional boundaries to reduce routing table size at upper-layer STPs, which is useful for carriers with subscribers distributed between Canberra and remote outback exchanges.
Routing Label and MTP3 Behaviour
The routing label in an MSU carries the destination point code, the originating point code and the signalling link selection field. MTP3 uses this label to decide whether to deliver, convert or transfer the message. In a nested hierarchy, a transfer point strips the lower-layer context and forwards based on cluster only, then hands the message to the correct child.
Converters appear where two networks meet, for instance where international signalling enters Telstra's national grid. The converter rewrites the destination point code so the receiving STP can interpret it without ambiguity. A single digit error can break global title translation during caller ID or number portability lookups, so validation is taken seriously by operational teams.
Load Sharing and Alternate Signalling Paths
Nested STPs are usually configured in mated pairs so traffic can be shared across two paths. Load sharing is governed by the SLS bits in the routing label, and operators must ensure adjacent linksets allocate SLS ranges consistently. In Australia, where the NBN and mobile carriers depend on signalling for voice and SMS, consistent SLS assignment prevents congestion at peak hours such as weekend sporting finals.
Alternate routing takes over when a primary link fails. MTP3 timers determine how quickly the failure is detected and how soon traffic moves to the backup path, which matters under the Telecommunications (Interception and Access) Act 1979, since lawful interception must remain available during reroutes.
Operational Risks in Deeply Nested Topologies
The more layers a hierarchy contains, the harder it becomes to debug. A change in one cluster can cascade into unexpected reroutes elsewhere, so audit trails become essential. Australian operators must be careful because of expectations set by the Telecommunications Industry Ombudsman, which requires carriers to respond promptly to service-affecting faults.
Security adds another dimension. Attackers familiar with signalling networks can exploit poorly managed point codes to redirect SMS or intercept location updates. In a nested hierarchy, compromising a single lower-layer STP gives the attacker reach into a wider set of destinations, which makes hardening of inner-layer transfer points a priority.
Recommendations for Point Code Lifecycle Management
- Maintain a centralised registry that maps every assigned cluster and member to its physical location and responsible engineer, especially for sites from Adelaide to Darwin.
- Audit point code assignments at least twice a year, since mergers in the local carrier market routinely introduce new signalling points that must not collide with existing allocations.
- Document SLS-to-link mapping alongside routing configuration so load changes are reviewed against traffic forecasts.
- Apply change windows for any point code retirement and stage cutovers across primary, secondary and tertiary STPs.
Operators exploring this area often find that consolidated learning paths reduce on-the-job errors. A practical resource collection covering MTP3, ISUP and signalling security is available at https://ss7-training.net/products.
The next concrete step is to pull the current point code inventory from each STP in the hierarchy, sort it by cluster, and flag any cluster where more than 60 percent of member addresses are already in use, since those are the candidates for reallocation before the next regional expansion is approved.
