Troubleshooting ISUP Circuit Continuity Check Failures
An ISUP Circuit Continuity Check (COT) verifies that a selected voice circuit has a usable transmission path before call setup proceeds. It is especially important where signalling and bearer traffic travel through separate network elements, such as an SS7 link set controlling a TDM circuit, media gateway, or interconnecting trunk.
A failed COT can appear as a rejected call, delayed call establishment, false answer supervision, or repeated attempts on the same route. The fault may sit in signalling, the voice bearer, a gateway configuration, or an intercarrier interconnection. Engineers supporting Australian networks also need to account for the shift from legacy PSTN infrastructure towards SIP, mobile core networks, and NBN-based voice services.
| Symptom | Likely area | First check |
|---|---|---|
| COT failure on every circuit | Trunk, gateway, or test configuration | COT method and circuit mapping |
| Failure on one circuit only | Physical bearer or timeslot | Timeslot, framing, and loop path |
| Intermittent failures | Timing, transmission quality, or congestion | Error counters and clock source |
| Signalling succeeds but speech is absent | Media path or switch matrix | Two-way audio and bearer continuity |
| Failures after routing changes | CIC or route mismatch | Circuit identification codes |
What COT Tests
During a continuity check, the originating exchange sends a test tone or continuity signal over the speech circuit. The distant exchange detects the signal and returns an indication through the signalling path. Depending on the national profile and network design, the result may be carried in a Continuity message or reflected in the Initial Address Message procedure.
The test is intended to confirm circuit availability, rather than validate the entire call. It does not prove that digits, charging, announcements, codecs, or end-to-end application services will work. A successful check can therefore be followed by a call failure caused by routing, subscriber status, or media negotiation.
Common Causes Of Failure
A frequent cause is a mismatch between the Circuit Identification Code (CIC) in ISUP and the bearer timeslot actually selected by the switching equipment. The signalling node may test circuit 32 while the media gateway connects another timeslot, leaving the tone undetected. Incorrect trunk group provisioning, swapped transmit and receive paths, and inconsistent numbering between two carriers produce similar symptoms.
Transmission faults are equally important. Loss of framing, slips, excessive bit errors, faulty echo cancellers, muted timeslots, or a failed cross-connect can prevent the continuity tone from reaching the far end. In older TDM equipment, a single defective E1 interface can affect multiple circuits, while an individual timeslot fault may appear isolated.
Signalling And Timer Checks
Capture the IAM, the continuity request, the returned result, and any release message at both signalling points. Compare CIC values, point codes, circuit state, and message direction. A COT failure reported by the originating switch should be correlated with what the destination switch received, rather than accepted as proof of a physical fault.
Review the COT timer and related supervision timers against the vendor’s ISUP profile. A timer that is too short can classify a slow but healthy response as a failure; an unsuitable timer can leave circuits blocked for too long. Check whether the network expects a continuity check before every call, only after a circuit seizure, or under a periodic maintenance regime. Engineers can use structured SS7 training resources to compare these procedures with the relevant ISUP and MTP behaviour.
A Practical Fault-Finding Sequence
Start with a controlled test call using a known-good destination and a single affected CIC. Record the exact time, originating and terminating point codes, IAM contents, COT result, release cause, and circuit state. Repeat the test in both directions if the interconnection allows it. This separates a one-way bearer problem from a general trunk configuration error.
Next, compare a failed circuit with a neighbouring circuit on the same route. Inspect E1 or T1 alarms, CRC and bipolar violation counters, slips, clock references, and timeslot cross-connects. If the bearer is carried through a media gateway, verify that the gateway maps the CIC to the intended RTP or TDM resource and that no maintenance block, alarm, or forced release is active.
Australian Interconnection Considerations
Australian operators often combine legacy SS7 and TDM interconnects with SIP trunks, mobile switching, and NBN voice platforms. A call between Melbourne and Sydney may cross several technology domains, while traffic to regional Queensland, Western Australia, or remote mining sites may use longer and less redundant transmission paths. A COT fault can therefore be introduced during an interworking step rather than at the original exchange.
The Australian market also includes major mobile operators, wholesale carriers, and smaller hosted-PBX providers. Many people now make routine calls from mobiles or NBN services, while businesses retain SS7-connected routes for number portability and carrier interconnection. Check the Australian numbering and interconnect profile used by the parties, and verify that any translation between ISUP, SIP, and vendor-specific signalling preserves circuit and continuity status.
Restoring Service Safely
Do not clear a COT failure by permanently disabling continuity testing unless the interconnecting carriers have agreed that behaviour and the risk is understood. Bypassing the check can allow calls onto a broken bearer, resulting in silence, one-way speech, or repeated customer complaints. If service must be maintained, route traffic temporarily through verified circuits and document the change.
After correcting the fault, test several CICs across different times and call directions. Confirm that successful calls provide two-way speech, that failed circuits are marked unavailable, and that release causes are consistent. In Australia, retain event records according to the operator’s operational, privacy, and lawful-access obligations, including requirements that may arise under the Telecommunications (Interception and Access) Act 1979.
The key point is that a COT failure is an observable symptom, not a diagnosis. Correlate ISUP messages with CIC mapping, transmission alarms, timers, and actual bearer audio. Once signalling and media evidence agree, the fault usually narrows to a specific circuit, interface, gateway rule, or interconnection profile.
