How to Perform an ISUP Circuit Continuity Check (COT)
An ISUP Circuit Continuity Check (COT) verifies that the bearer circuit associated with a Circuit Identification Code (CIC) can carry speech or media between two exchanges. Signaling messages may travel successfully across the SS7 network while the corresponding voice path is miswired, blocked, or unavailable, so the check validates both signaling coordination and circuit continuity.
The procedure uses ISUP messages, a controlled continuity tone, and a response from the far-end exchange. Exact message direction and timer behavior depend on the national or carrier-specific ISUP variant, but the operational principles remain consistent.
Purpose And Operating Principle
A COT is normally requested when a call setup requires confirmation that the outgoing circuit is usable. The originating exchange identifies the CIC in the Initial Address Message (IAM), and the continuity procedure is coordinated through messages such as Continuity Check Request (CCR) and Continuity (COT).
The remote switch applies or detects a prescribed test signal through the speech path. A successful result indicates that the circuit, transmission route, and switching connections passed the test. A failed result should prevent normal call completion or trigger circuit blocking, depending on network policy.
Before testing, confirm that the signaling route can correctly carry ISUP traffic. Reviewing MTP3 label routing helps verify that the DPC, OPC, Service Indicator, and CIC-related signaling are reaching the intended exchange.
Prepare The Circuit And Signaling Data
Start by selecting the exact CIC and confirming its administrative state at both ends. The circuit should be idle, provisioned for the same bearer type, and associated with matching trunk-group records. Check that no maintenance block, reset, alarm, or previous continuity test is active.
Capture the IAM and inspect its Continuity Indicator. This field shows whether a continuity check is required, has already been performed on the circuit, or is being handled according to the local signaling variant. Also verify the Called Party Number, Nature of Connection Indicators, Forward Call Indicators, and transmission medium assumptions.
Use a signaling analyzer at both exchanges when possible. The trace should include timestamps, message direction, point codes, CIC, sequence context, and the response to the test request. Synchronizing clocks makes it easier to distinguish a slow response from a message that was never sent.
Execute The Continuity Procedure
A typical exchange sends the IAM and, when required, a CCR toward the remote switch. The far-end equipment connects the continuity test arrangement to the selected bearer circuit. A standard tone or test signal is then transmitted through the circuit, where the originating or terminating equipment detects its return or verifies the expected receive condition.
When the detector confirms the signal, the exchange sends a COT with a successful continuity indication. The call setup can then proceed with messages such as Address Complete Message (ACM) and Answer Message (ANM), subject to normal digit analysis and destination conditions.
If the test fails, the COT carries a failure result or the expected response does not arrive before the applicable timer expires. The switch should release or quarantine the circuit according to its operating rules rather than treating the failed bearer as available for ordinary traffic.
| Observation | Likely Meaning | Immediate Check |
|---|---|---|
| COT success received promptly | Signaling and bearer path passed the test | Continue call setup and record the result |
| CCR sent, no COT received | Remote processing, routing, timer, or bearer problem | Check traces, timers, point codes, and remote state |
| COT failure received | Test tone was not detected correctly | Inspect transmission path, switch mapping, and loop |
| Unexpected CIC or point code | Label, trunk, or provisioning mismatch | Compare both exchanges’ circuit records |
| Repeated failures on one circuit | Physical or logical circuit defect | Block the CIC and begin maintenance testing |
Validate Timers And Message Sequence
ISUP timers control how long the exchange waits for continuity-related responses and subsequent call progress. Do not infer a fault solely from a delayed COT until the configured timer values and retransmission rules have been checked. Different standards and vendor implementations may use different names or values.
The message sequence should be evaluated together with the CIC. A COT for another circuit is not a valid response, even if it arrives from the correct point code. Likewise, a response from an unexpected signaling route may indicate duplicated data, incorrect routing, or a configuration error.
A successful COT does not prove that every later call function will work. It confirms the tested continuity condition at that moment. Echo control, codec negotiation, answer supervision, charging, and release procedures require separate validation.
Investigate Failures Across TDM And IP Networks
For a TDM trunk, inspect physical cross-connects, timeslot assignment, framing, synchronization, impedance, transmission levels, and any intervening echo or tone suppression equipment. A reversed pair, incorrect timeslot, or faulty digital gateway can allow signaling to succeed while preventing the test tone from completing its path.
In an IP-based signaling environment, separate the SS7 signaling transport from the bearer path. M2PA or another SIGTRAN adaptation layer may carry signaling over IP, while media uses TDM gateways, RTP, or a different transport. The material on mapping PSTN to IP is useful for understanding why a healthy IP signaling association does not automatically validate the voice circuit.
Check packet captures, SCTP associations where applicable, M2PA link status, gateway circuit maps, and firewall behavior. A clean MTP3 or SIGTRAN trace alongside a failed COT usually shifts attention toward bearer configuration or gateway interworking rather than the signaling link itself.
Record Results And Protect Service Quality
After testing, document the CIC, exchange pair, test time, IAM continuity indicator, CCR and COT timestamps, result code, timer outcome, and any maintenance action. Repeated tests should be correlated with trunk alarms and customer call statistics.
Do not run intrusive continuity checks on live circuits without an approved maintenance window or a documented service procedure. A test can seize a circuit, interrupt traffic, or leave equipment in a temporary test state. Ensure that successful circuits are returned to service and failed circuits are clearly marked.
Practical Checks Before Closure
- Confirm the CIC and trunk timeslot match at both exchanges.
- Verify the IAM continuity indicator and the expected CCR/COT sequence.
- Compare signaling timestamps against configured ISUP timers.
- Test the bearer path independently when COT failure repeats.
- Release, reset, or block the circuit according to the approved maintenance procedure.
Use a controlled lab circuit or maintenance trunk to reproduce the sequence, then compare the trace with a known-good COT. Apply the same disciplined checks in production, preserve the signaling capture, and escalate recurring failures with the CIC, timestamps, message sequence, and transmission findings attached.
