SIGTRAN SUA as an alternative to SCCP for IP-based applications
Across Australian carrier networks from Brisbane exchanges to Melbourne cores, the move toward IP-based signalling has reshaped how transaction services are carried. SIGTRAN, the IETF-defined family that transports SS7 over IP, offers several adaptation layers, and the SCCP User Adaptation Layer, commonly called SUA, gives architects a streamlined option that does not require relaying every MTP3 message. For teams operating softswitches, signalling gateways, or 5G interconnects with providers like Telstra, Optus, or Aussie Broadband, understanding where SUA fits next to traditional SCCP is now a routine planning question.
The decision matters because each adaptation layer maps to a different slice of the legacy protocol stack. SUA runs on top of SCTP and provides SCCP-like services directly to applications, removing the need for MTP3 routing logic on every IP peer. That single architectural shift changes how routing keys, global titles, and subsystem numbers are exposed to higher-layer protocols.
SCCP and the legacy SS7 signalling layer
SCCP has long served as the transaction-routing backbone of SS7, sitting above MTP3 and offering connectionless and connection-oriented services. In a classic TDM network running through Brisbane's older Telstra exchanges, SCCP handles global title translation, subsystem management for MAP and CAP, and the addressing that lets a home location register find a visiting mobile. It does this through a layered relationship with MTP3, which itself manages link sets and point codes.
When operators wanted to carry SS7 over IP, the obvious first step was to replicate MTP2 and MTP3 over SCTP, leading to M2PA and M3UA. These solutions preserved the point-code addressing model and kept SCCP intact. For many Australian carriers rolling out IP signalling in the early 2000s, M3UA plus SCCP was the default because it mirrored the TDM world they already operated. A walkthrough of SCCP global title translation shows how addressing survives these transitions.
The SIGTRAN stack and SCTP transport
SIGTRAN is not a single protocol but a stack defined across several RFCs, anchored by SCTP as the common transport. SCTP brings multi-homing, message-oriented delivery, and association management that TCP alone cannot offer. M2PA, M3UA, SUA, and others each define how an SS7 layer is adapted to run over that transport.
M2PA preserves MTP2 framing and pairs it with MTP3, while M3UA tunnels MTP3 messages between signalling gateways and IP servers. SUA takes a different path: it adapts SCCP directly, leaving MTP3 entirely outside the IP boundary. An IP-based application peer using SUA never sees point codes, link sets, or MTP3 routing tables. Instead, it talks in terms of SUA layer addresses that map SCCP subsystems and global titles.
Introducing SUA for IP-based applications
SUA, defined in RFC 3868, was designed for environments where IP peers do not need MTP3 services at all. A typical use case is a softswitch or application server inside an Australian data centre exchanging MAP or CAP traffic with a signalling gateway that fronts the legacy PSTN. The gateway terminates MTP3 and SCCP on the TDM side and presents a clean SUA interface to the IP side.
Because SUA bypasses MTP3, peer relationships become simpler. Routing keys in SUA carry the global title or subsystem number along with optional SCCP and ISUP parameters, which can be useful when building redundancy in sites such as a Perth-based gateway cluster serving regional mining operations. Operators also benefit from fewer hops, since messages no longer traverse an MTP3 routing function on the IP side.
Comparing SUA and SCCP at a glance
| Feature | SCCP over M3UA | SUA |
|---|---|---|
| Underlying transport | SCTP via M3UA | SCTP directly |
| MTP3 visibility on IP side | Preserved | Removed |
| Routing basis | Point codes and global titles | Global titles and subsystem numbers |
| Typical use | Backwards-compatible SS7 over IP | Greenfield IP signalling, application servers |
| Subsystem management | Full SCCP | Native SUA CLDT and CLDR |
| Example deployment | Legacy TDM interconnects | Sydney-based softswitch pools |
The table highlights the practical split: SCCP over M3UA suits gradual migrations where point-code addressing must survive, while SUA fits cleaner cutovers and native IP application servers.
Deployment patterns across Australian networks
Australian carriers and integrators have used SUA where IP peers genuinely do not need point-code semantics. A common pattern is in mobile core virtualisation, where virtualised network functions on a Macquarie Park or Clayton cloud platform talk SUA to a signalling gateway fronting older mobile switching centres. TPG and Vocus have also deployed SUA-based links between data centre softswitches and media gateways that handle inbound VoIP peering.
The trade-off is that any IP peer still dependent on MTP3 services, such as link monitoring through MTP3 changeover messages, must remain on M3UA. In practice, mixed deployments dominate, with M3UA for transit across the IP backbone and SUA at the application edges. Refreshing these configurations on a schedule, much like rotating toys and enrichment items throughout the day, keeps stale routing keys from lingering after a softswitch upgrade. A regional guide from Redcliffe illustrates how signalling teams in Queensland have approached similar layer choices.
Migration paths and security posture
Migrating from SCCP to SUA is rarely a wholesale swap. Most Australian teams phase the change by deploying SUA between new IP-native application servers and existing gateways, leaving the M3UA path in place for legacy peers. The benefit is a controlled cutover, with each subsystem tested in isolation.
Security remains a concern. ACMA's increasing focus on signalling firewall deployment, combined with the same SCTP vulnerabilities that affect M3UA, means SUA endpoints need IPsec or TLS wherever feasible. Operators should also audit routing keys and ensure that global titles are tightly filtered, especially as 5G core functions increasingly rely on similar adaptation techniques.
A reasonable first move is to stand up a small SUA testbed in a lab environment using an open-source stack and capture live exchanges with Wireshark to observe how CLDT and CLDR messages flow. Seeing the protocol in action clarifies the differences far faster than reading the RFC alone, and it lays the groundwork before any production cutover.
