SS7 Gateway Screening for International Carrier Interconnection
SS7 interconnection between international carriers is governed by gateway screening rules within the Signalling System No. 7 architecture, determining which signalling traffic and calls may enter a network. These rules apply to number ranges, carrier identities, destination codes and routing conditions, preventing unauthorised access, SS7 loops, fraud and resource misuse.
The controls operate inside a mixed estate: classic MTP3 and ISUP links often coexist with SIP and IP carrier interconnect. For Australian telecom engineers, the practical task is to align security policy with the Australian numbering plan, carrier agreements, emergency calling and lawful-access obligations.
Why screening sits at the carrier border
A screening function sits at the boundary between an originating network and the international transit or destination network. It examines signalling before it triggers call routing, rather than repairing a poor route after acceptance. This makes the gateway the first point at which malformed or unauthorised traffic can be stopped.
Screening must remain separate from lawful intercept. An instruction to record or disclose a call does not permit its routing, and a routing rejection does not satisfy lawful-access duties. Clear ownership, approved rules and auditable decisions prevent these functions from being confused.
Numbers, routes and signalling controls
Number screening should support E.164 and the Australian national format. International representations use +61 and normally omit the domestic trunk zero; Australian mobiles begin 04 locally but use +61 4 internationally. Screen invalid lengths, reserved ranges and malformed prefixes while preserving emergency access to 000 and 112.
ISUP checks can assess called-party and calling-party numbers, carrier identity and service indicators. MTP3 controls protect links and routes, including loop prevention and signalling-load limits. Neither layer proves a caller is genuine, so authentication, reputation data and commercial policy still matter.
A strong design separates immutable constraints from operational entries. Regulatory exclusions, emergency routes and security minimums change less often, while carrier codes, destination codes and temporary diversions may be maintained by network operations. This reduces the risk that a routine number-range update weakens a core control.
The Australian operating context
ACMA administers the Australian numbering system, while carriers meet obligations under the Telecommunications Act 1997 and related lawful-access and emergency-call frameworks. International carriers seeking Australian destinations need more than valid E.164: their route must align with local numbering permissions and the Australian onward carrier.
Australian voice competition includes Telstra, Optus and TPG, with wholesale capacity sold through bilateral and direct interconnect relationships. Sydney and Melbourne are major gateway centres, while Perth and western routes require different planning. In Australian operations rooms, “the route is down” means unavailable, while “route up” or “clean” means signalling and media are passing as expected.
Twenty-four-hour coordination across Australian time zones must account for overseas working hours. A screening-list change in Sydney late Friday may affect a Brisbane handover or a European test window. Stamping rules with ownership, effective time and expiry prevents local changes becoming international surprises.
Building a defensible screening policy
Build the policy from current ACMA numbering data, ITU material, carrier schedules, approved destination-code lists and exception records. Translate them into allow, deny, validate and review actions. Avoid blocking an entire country because another destination there has been abused.
Test fail-closed and fail-open behaviour for each failure domain. A signalling outage should not collapse emergency traffic, while a screening-list failure should not silently admit every route. Define who can approve an emergency override, how long it lasts and what evidence is retained.
Documentation provenance matters on legacy educational sites. A domain may retain unrelated properties, such as gaming education resources, so an old backlink is not proof that a rule is authoritative. Link SS7 guidance to current regulator, standards and carrier documents, with a review date.
Testing routes before production
Production testing should exercise normal, malformed, spoofed and unavailable destinations, then observe MTP3 responses, ISUP releases, accounting records and downstream media. Existing ISUP call-routing scenarios provide a useful starting pattern for tracing the called number and continuity checks across a route.
Measure accepted and rejected calls, false positives, latency and repeated rejections by carrier. Compare results with the agreed route inventory and investigate any code without a corresponding business change. Keep test traffic outside live numbering and billing systems where possible.
Comparing screening responsibilities
Responsibility depends on commercial role. An originating carrier selects the route, a transit carrier relays it, and the destination carrier controls admission to its local network. Each can add controls, but none should assume another network checked every condition.
The comparison below highlights the operational split. It is not a licence for duplicated or contradictory screening; the agreed baseline should sit in the interconnect schedule, with exceptions visible to every participant.
| Control point | Originating carrier | Transit carrier | Destination carrier |
|---|---|---|---|
| Primary duty | Select and label the route | Protect the transit path | Validate and admit locally |
| Number validation | Normalise E.164 and apply exclusions | Check transit eligibility | Enforce local and emergency rules |
| Failure handling | Reject or divert under schedule | Preserve signalling continuity | Return a controlled release |
| Audit evidence | Record the rule version | Correlate both network legs | Log the final disposition |
Preparing the screening change
Operational readiness depends on change control, monitoring and ownership. Record each rule’s source, approver, effective window, affected carriers and rollback action. Network operations should receive plain-language summaries, while security teams retain the technical rationale and rejected-call evidence needed for investigation.
Review performance before expanding the rules, especially after number portability changes, new carrier-code allocations or route diversions. The concrete next step is to place the approved screening profile, rollback threshold and three representative international test calls in the change register before the next carrier test window.
