ISUP continuity check: verifying trunk health before call setup
The ISUP continuity check is a core procedure in telecommunications networks that verifies the integrity of voice trunks before any user traffic is allowed to traverse them. Operating at the ISUP layer of the SS7 protocol stack, it plays a critical role in preventing call setup failures, reducing post-dialling delays, and keeping voice services reliable. Engineers working on legacy PSTN interconnects and modern IP-based signalling paths alike rely on this procedure to maintain quality on routes between exchanges.
In Australia, where carriers such as Telstra operate extensive trunk groups across Sydney, Melbourne, Perth and Brisbane, the continuity check forms part of the daily health monitoring routines maintained by network operations centres. ACMA's technical standards reference ISUP procedures within the framework that operators must follow when interconnecting Class 4 switches. Understanding how the procedure works, and when to apply it, helps both operations staff and security researchers identify misconfigurations and signalling vulnerabilities.
What the continuity check actually tests
The procedure verifies that a circuit from one switch to another remains physically and logically intact across the entire bearer path. It does not simply confirm that a T1 or E1 link is framed correctly; rather, it ensures that a specific timeslot, DS0 channel, or RTP-mapped port can carry encoded voice samples without degradation. A continuity check typically uses a two-tone test signal transmitted at 2010 Hz and 1780 Hz, which the far-end switch detects, loops back, and reports on.
Detection of the looped-back tones must occur within a defined measurement window. If the responding exchange fails to return the expected acknowledgment, the originating switch marks the circuit as potentially faulty and removes it from the available trunk group. Engineers in Adelaide frequently observe this behaviour when fibres are accidentally cut during roadworks, interrupting the bearer path while leaving the signalling link fully operational. Environmental factors across regional exchanges, including temperature swings in remote buildings, can also produce intermittent failures that resolve once air conditioning stabilises.
Message flow between the two exchanges
The signalling procedure begins when the originating switch sends a Continuity (COT) message over the MTP3 transport layer. The far-end switch monitors the specified circuit for the test tones, and upon successful detection, replies with a COT acknowledgment or a Continuity Hand-off (CHG). Both messages travel through the same signalling links used for IAM and ACM, keeping the test within the SS7 protocol family.
In real deployments the time between sending COT and receiving the response is captured in switch logs. Australian carriers commonly export these measurements to centralised performance dashboards that track jitter, post-selection delay, and continuity success rate. Reviewing call-routing-scenarios-using-isup-continuity-check-b8bf provides additional worked examples of how these flows interact with call routing logic in complex networks, including scenarios where multiple exchanges cooperate to validate a single long-haul circuit.
When trunks require mandatory continuity checks
Mandatory continuity checks apply on international routes, on trunks crossing between different operators, and on newly added circuits. The ISUP standard also requires the procedure before any call that involves satellite hops, where propagation delay makes early fault detection essential. National standards bodies aligned with the Australian Communications Industry Forum recommend conservative application of mandatory checks on any interface crossing jurisdictional boundaries.
Optional checks may be enabled on domestic intra-operator trunks to reduce setup time, particularly when the trunk group has been recently exercised and statistics indicate a low historical failure rate. Operators must balance this against the cost of failed calls reaching subscribers and the reputational damage associated with one-way audio or silent lines across backhaul services used in regional National Broadband Network areas.
Operational scenarios and performance impact
Different network configurations produce different continuity check outcomes and performance characteristics. Engineering teams compare scenarios side by side to decide where mandatory testing adds value versus where it introduces unnecessary latency. The table below illustrates typical conditions observed in Australian networks.
| Scenario | Mandatory check | Expected setup overhead | Typical failure mode |
|---|---|---|---|
| Domestic intra-operator trunk | No | 0 ms | DSP misconfiguration |
| Inter-operator interconnect | Yes | 50–150 ms | Echo canceller issue |
| International gateway | Yes | 200–400 ms | Satellite hop degradation |
| New circuit turn-up | Yes | 100–200 ms | Physical layer fault |
| Backup trunk group | Optional | Variable | Clock slip |
Setting these expectations helps operators avoid over-testing high-confidence routes while still catching genuine faults on riskier paths.
Security and compliance considerations
Continuity check procedures interact with broader signalling security frameworks. A compromised ISUP stack could report successful continuity on circuits that have not actually been tested, masking faults or facilitating unauthorised interception. Auditing the procedure across vendor implementations requires both technical diligence and adherence to anti-bribery controls, particularly when contracts with equipment suppliers span multiple jurisdictions. The anti-bribery travel act guidance describes how cross-border procurement decisions should be documented to remain compliant with international anti-corruption standards.
Australian carriers operating under the Telecommunications (Interception and Access) Act 1979 must ensure that continuity check logs are retained for the periods required by law and that access to those logs is strictly controlled. This regulatory layer adds operational weight to what otherwise appears to be a straightforward pre-call verification step, requiring dedicated storage procedures and audit trails.
Network operators reviewing continuity check configurations should start by mapping which trunk groups currently run with checks enabled and correlate that data with recent fault rates. Adjusting the policy on a per-route basis typically yields better audio quality and faster call setup than a uniform mandatory setting across the entire Class 4 switch estate.
