ISUP continuity check on satellite links and loop-around testing

The ISUP continuity check, often shortened to COT, is the mechanism that tells a switch whether the bearer path between two exchanges actually carries voice. On terrestrial fibre or copper, this is almost routine, but once the transmission hop includes a satellite link, the timing and behaviour of the test signal change in ways that catch even experienced planners off guard.

In Australia, where remote mine sites, offshore platforms, and pastoral stations often rely on VSAT connectivity from operators such as Telstra, Optus, or specialised providers, getting COT right across a satellite bearer is not an academic exercise. A failed continuity check between Perth and a Pilbara concentrator, or between Darwin and a defence installation, can delay cutover windows and disrupt scheduled maintenance on production traffic.

Why continuity checks behave differently over satellite

The ISDN User Part continuity check uses an in-band tone, typically 2000 Hz, transmitted end-to-end across the bearer channel. On a fibre path, one-way delay sits in the millisecond range, so the sending switch receives its own tone back almost immediately and verifies the loop. Across a geostationary satellite, one-way propagation delay adds roughly 250 ms, which means the test message takes about half a second to return. That latency window can collide with the COT timer values defined in the Q.704 and Q.764 recommendations, producing false negatives if the values are left at default terrestrial settings.

For Australian operators working with NBN Sky Muster or commercial Ka-band services, the additional jitter and occasional FEC retranslations introduce variability that further tightens the margin. Field engineers in Adelaide or Brisbane who previously tuned timers for short-haul inter-state links now find the same parameters unsuitable once a 36,000 km space segment sits in the path.

Anatomy of a loop-around test arrangement

A loop-around, sometimes called loopback, closes the bearer at a defined point along the path so the originating exchange receives the test tone back through the same circuit. In a satellite scenario, the loop is most often configured at the remote earth station's channel unit, at the hub modem, or at the far-end switch's line card. Each placement gives a different diagnostic window: looping at the satellite modem isolates the radio path, while looping at the far switch verifies the entire cross-connect from the source exchange to the destination port.

The test sequence is initiated through the SCCP or MTP3 layer by sending an ISUP COT message, after which the originating switch applies the 2000 Hz probe and waits for confirmation within the configured COT timer. Choosing where to place the loop is therefore the single most important decision when designing the test plan, and it depends on whether the goal is to validate the satellite hop alone or the end-to-end voice path.

Preparing the earth station for a clean measurement

Before sending any ISUP messages, the earth station crew needs to stabilise the carrier. This includes locking the modulator to the hub reference clock, confirming that the forward error correction mode is consistent between ends, and ensuring that the voice codec negotiation has settled on a clear-channel mode rather than a compressed speech path. Compression interferes with the continuity probe because low-bit-rate codecs alter or attenuate the 2000 Hz tone, and the loop-around may report success while the actual bearer would fail voice transmission.

In remote Western Australian sites, where generators supply power and ambient temperatures swing by more than thirty degrees Celsius between night and day, technicians also verify that the BUC and LNB are operating within their nominal temperature envelopes. A drift outside spec adds phase noise that looks like a COT failure even on a perfectly good satellite link.

Running the procedure in sequence

The actual test starts from the local switch issuing a COT request toward the destination point code. The far side receives the request, applies the test, and returns the result through the signalling link. Engineers commonly run three sequential loop-arounds: modem level, channel unit level, and finally switch level. Each successful pass narrows the fault domain and provides documented evidence for the change-management record that ACMA-licensed operators in Australia are expected to maintain.

Between iterations, the COT timer values should be observed on the trace output. If the response arrives close to the timer expiry, the margin is thin and a small environmental change could push the next test into failure. Adjusting the timer by one or two seconds in line with Q.764 guidance is normal practice for geostationary hops.

Reading the result and acting on it

A clean pass on the switch-level loop confirms that the entire path from the originating exchange, through the satellite hop, to the destination switch and back is fit for ISUP bearer traffic. A modem-level pass with a switch-level fail points firmly at the terrestrial interconnect on the far side, which on Australian deployments often means the in-building cabling at a metro PoP in Sydney or Melbourne rather than anything to do with the space segment.

Failures at the channel unit level typically indicate misconfigured DS0 mapping or a misalignment between the satellite frame structure and the E1/T1 framing presented to the switch. Documenting each outcome against the specific loop point is what later allows remote support teams to triage without sending a technician to the site, which can save hours of travel to places such as Tennant Creek or Mt Isa.

Field habits that keep the results trustworthy

Consistency matters more than cleverness. Run the test at the same time of day for repeated comparisons, because satellite link behaviour under clear sky differs from conditions during heavy rain over tropical Queensland. Always capture the full signalling trace, not just the pass or fail summary, and store it alongside the earth station's log of the carrier's Eb/N0 reading at the moment of test. Engineers in Hobart or Geelong who follow this habit build a dataset that makes future faults much easier to interpret.

For those expanding their skills beyond ISUP, the signalling point code spoofing risks guide offers a useful contrast, because the threats described there apply to the same signalling plane that carries the continuity check.

A practical next step is to schedule a controlled loop-around on the next available weekend maintenance window, starting from the modem level and recording the trace output for comparison with the previous quarterly result. The full https://ss7-training.net/products catalogue includes reference timer tables that match Q.764 guidance adapted for geostationary hops.