ISUP to SIP interworking for Australian telecom networks

An ISUP Call with Interworking to SIP describes a gateway that lets legacy SS7/ISUP callers reach SIP/IP endpoints without losing control of call state. The gateway translates signalling events and selected parameters between ISUP over MTP3 and SIP over UDP, TCP, or TLS.

ISUP is transaction-oriented and number-centric, while SIP is dialog-oriented and URI-centric. A useful design therefore maps semantics rather than identical field names: setup, progress, answer, release, routing, caller presentation, and failure causes all require explicit treatment.

Traffic peaks can expose weak signalling design before media capacity fails. SS7 Training’s guide to automatic congestion control provides useful context for avoiding overload at the SS7 boundary and for understanding why graceful SIP responses matter.

For Australian operators, the details extend beyond basic protocol conversion. Number normalisation, mobile number portability, emergency access, privacy, and wholesale interconnect arrangements make correct behaviour essential in busy metropolitan and regional networks.

How the interworking boundary works

ISUP messages usually travel through the SIGTRAN stack, using MTP3 and SCCP to identify the next signaller, while SIP uses IP routing and transaction matching. The interworking function sits between those control planes and may pass media to an IP media gateway rather than terminating it itself.

Every translated event must retain enough context to prevent duplicate answers, premature releases, or mismatched transactions. Correlation keys, call state, cause values, and timers must be aligned; ISUP timers such as T1 and T2 do not have direct equivalents in SIP Timer A or Timer B.

ISUP event or field SIP equivalent Interworking treatment
Initial Address Message (IAM) INVITE Map the Called Party Number to the Request-URI and apply routing and privacy policies
Address Complete Message (ACM) 180 Ringing Preserve the alerting state and any associated cause
Call Progress (CPG) 183 Session Progress Carry progress details without implying that the call has been answered
Answer (ANM) 200 OK Confirm the answer while keeping SDP and media state consistent
Release (REL) BYE Translate the release reason while retaining transaction context
Cause and presentation indicators Reason, identity, and privacy headers Use controlled gateway policies rather than copying fields blindly

Core message and parameter mapping

During setup, an ISUP Initial Address Message becomes a SIP INVITE. The called party number supplies the Request-URI, the calling party number can feed From and identity headers, and routing information needs a defined policy rather than a blind header copy.

ISUP Calling Party Identification (CPI), Called Party Number (CPN), and presentation or restriction indicators map to SIP identity, display-name, and privacy semantics. Transport, billing, originator, and circuit information require separate treatment. Untrusted SIP headers must never overwrite validated ISUP data, because that could misroute a call or disclose information the originating network restricted.

Setup, progress, and release flows

An ISUP Address Complete Message normally produces a SIP 180 Ringing response, while a Call Progress message can produce 183 Session Progress. An ISUP Answer maps to 200 OK, after which SIP ACK confirms the answer and real-time media can begin under the negotiated SDP offer and answer exchange.

Release handling is less symmetrical. An ISUP Release may become SIP BYE, with the cause expressed through a Reason header where possible. ISUP Release with Unsecured is not a direct substitute for CANCEL, so gateway policy must distinguish caller cancellation, network release, congestion, and endpoint rejection.

Australian numbering and regulatory realities

Australian numbers normally use +61 internationally and a national trunk prefix of 0. Gateways need one documented normalisation rule; otherwise a number may be rejected in Sydney, Melbourne, or Brisbane because its prefix differs from the routing database. Retail VoIP and hosted PBX services over the NBN add further combinations of local, mobile, and international formats.

Mobile number portability means the original mobile range no longer identifies the serving carrier. Emergency access to 000 must follow approved emergency-routing procedures, while privacy and caller-ID restrictions should remain consistent with ACMA expectations and the originating operator’s lawful-intercept obligations. Cause transparency and accurate calling-party information are especially important in Australia’s competitive wholesale market.

Operational recommendations

Before production deployment, operators should validate mappings with representative traffic and failure cases.

  • Test IAM-to-INVITE translation with Australian number formats, including +61, national prefixes, and mobile numbers affected by number portability.
  • Exercise congestion, unanswered-call, busy-endpoint, rejected-media, and release scenarios to confirm that SIP responses reflect the correct ISUP cause.
  • Verify privacy and caller-presentation behaviour for withheld, restricted, unavailable, and spoofed calling-party information.
  • Compare ISUP and SIP timer behaviour under packet delay, retransmission, gateway restart, and signalling congestion.

Trace records should connect ISUP transactions, SIP dialogs, and media sessions so engineers can explain each outcome without changing the live interface. Test evidence should also show whether failures occurred during translation, routing, authentication, or media negotiation.

Security, observability, and deployment choices

Security controls must cover both sides of the gateway. SS7 screening, IP filtering, TLS, strict parsing, and protection against header injection are needed because a trusted ISUP side can still feed unsafe data toward SIP, and vice versa. Logs and counters should be designed to reveal abnormal message rates, repeated translation failures, and transaction state that fails to advance.

SS7 Training’s training solutions can support protocol review and troubleshooting, but the essential principle is straightforward: reliable ISUP-to-SIP interworking depends on disciplined translation of call state, numbers, privacy, causes, and timers, not merely converting one message into another.