Using STPs for message routing and GT translation

An STP acts as the message-routing hub of a traditional SS7 network. It examines signalling point codes, service indicators and Global Titles, then selects a path toward the next switch instead of forwarding traffic blindly. Since call-related signalling can cross several STPs, their routing and translation decisions influence service quality, resilience and exposure to abuse.

That function remains relevant where legacy PSTN infrastructure meets IP-based services. A signalling gateway can connect SS7 to SIGTRAN using M3UA or SUA, while translation tables bridge different numbering and addressing schemes. Australian operators therefore need an STP design that understands legacy signalling, modern transport and the regulatory controls surrounding critical communications.

How STPs route SS7 messages

SS7 traffic reaches an STP over MTP3 links, usually from a Service Switching Point or another STP. MTP3 handles link selection, congestion reporting and node-level routing; higher layers such as ISUP and SCCP then use the selected path for call setup, transactional or management information. The STP matches routing labels to its configuration and chooses an available successor.

A well-designed network separates transit from destination STPs and provides redundant paths between them. An A-link connects an SSP to its STP, while B-links carry traffic between STPs; alternate routes can fail over when a link, route or switch fails. The SS7 training resources provide useful background on MTP3 behaviour, timers and the wider signalling architecture.

Where GT translation takes place

A Global Title, or GT, identifies a destination through a numbering plan rather than naming an SS7 node directly. Global Title Translation, commonly called GTT, maps that title to a routable point code, subsystem or gateway address. Translation may occur in an originating STP, a terminating STP or a signalling gateway, depending on the network design and whether the route crosses TDM and IP domains.

For an Australian international call, the destination might begin with country code 61, but the dialled format can still vary. The originating side normalises the number, the GTT selects the appropriate destination, and a reverse translation later restores a format the called network can interpret. In ISUP, incorrect handling of called-party information can leave a call with no valid route; the ISUP indicator guide explains how backward and forward indicators preserve signalling order.

Australian network realities

Australia’s population and business activity are concentrated heavily around Sydney, Melbourne, Brisbane and Perth, while major routes also connect regional and remote communities. Everyday mobile use creates pronounced morning and evening peaks as commuters make calls from trains, trams and cars. STP route capacity and failover design must absorb those bursts without letting one congested destination affect unrelated traffic.

The local market adds further complexity. Telstra, Optus and Vodafone compete for mobile customers, and number portability means a service can retain its Australian number while changing access provider. At the same time, NBN and other IP-based voice deployments are changing the path from customer equipment to legacy exchanges. That environment favours carefully tested interworking between VoIP and SIP networks, SIGTRAN gateways and SS7 STPs rather than a single universal routing model.

ACMA administers carrier registration and sector regulation under the Telecommunications Act 1997, while telecommunications security duties are reinforced by the Telecommunications (Security) Act 2019. Clear boundaries and active supervision are recurring operational themes across sectors; SS7 Training’s wider archive includes safe parallel play guidance, illustrating why parallel activity needs defined limits even outside telecommunications.

Controls for reliable and secure routing

STP resilience depends on disciplined configuration, not merely duplicated hardware. The following controls are particularly useful for engineers maintaining Australian signalling environments:

• Restrict administrative access with least privilege, multi-factor authentication, signed configuration backups and audited change records.
• Allowlist expected point codes, Global Titles and signalling peers, while rate-limiting malformed or unsolicited traffic.
• Synchronise translation tables across every STP in a route, then test both forward and reverse mappings for Australian +61 and domestic number formats.
• Monitor MTP3, SCCP and ISUP errors, congestion, latency, translation failures and unusual route changes as security signals.
• Segment legacy SS7 from IP and management domains, and verify failover paths, 000 and 112 emergency routing, and restoration procedures regularly.

These measures limit the blast radius of a mistranslation, rogue peer or failed route. Operational testing should include a complete call transaction, a deliberately failed primary path and recovery after configuration rollback. Logs should then confirm that each STP selected the intended successor and applied the same translation result.

The point to retain

An STP is more than a message switch. It is a trust point where point codes, Global Titles, traffic priorities and route choices converge. Correct GTT preserves the meaning of a call as it crosses network boundaries, while MTP3 routing determines whether the signalling can reach the next node reliably.

The enduring lesson is to treat routing logic, numbering data and security controls as one system. Australian networks may combine legacy PSTN infrastructure with IP-based services, but the principles remain stable: translate deliberately, route redundantly and verify every change. That is the point to remember when an STP sits at the centre of a signalling flow.