Call Routing Scenarios Using ISUP Continuity Check
In traditional PSTN and SS7 networks, call routing depends on more than selecting an available circuit. The network must also verify that the chosen voice path is usable before alerting the destination subscriber. ISUP continuity check procedures provide this assurance for circuit-switched calls carried across trunk groups.
A continuity check can influence route selection, failure handling, and interworking between legacy signaling points and IP-based transport. Understanding the signaling sequence helps engineers distinguish a signaling failure from a bearer-path problem and design more reliable alternate routing.
Why Continuity Checking Matters
ISUP uses the Continuity Check (COT) procedure to test the speech circuit associated with a call. The originating exchange may request the check through information in the Initial Address Message (IAM), depending on network policy, circuit configuration, and national ISUP variant.
The test generally sends a continuity tone over the selected bearer circuit. The remote exchange detects the tone and returns a COT message indicating success or failure. A successful result allows call establishment to continue, while an unsuccessful result prevents the network from presenting a defective route to the called party.
The Core Signaling Sequence
A common sequence begins when an originating exchange selects a circuit identification code (CIC) and sends an IAM toward the destination exchange. The IAM carries called-party information, routing indicators, and the continuity-check request when the circuit requires validation.
After receiving the IAM, the terminating side participates in the bearer test. If the tone is detected correctly, it sends a positive COT response. The originating exchange can then proceed with address completion and alerting messages such as ACM and ANM. If the test fails or times out, the call is cleared or redirected according to the configured routing policy.
Timers are important in this process. A delayed COT response can indicate congestion, a faulty trunk, an interworking mismatch, or a signaling path problem. Engineers should correlate the ISUP trace with circuit alarms and voice-path measurements before assigning blame to a single network element.
Common Routing Scenarios
In a direct route, the originating switch selects a circuit group toward the destination and requests continuity verification. A positive COT confirms that the selected CIC and bearer path are aligned. The call continues through the normal route, preserving the expected sequence of IAM, COT, ACM, and ANM.
An alternate-route scenario begins when the continuity test fails. The originating switch may send a release procedure for the failed circuit and select another trunk group toward the same destination. This route may pass through a different carrier, gateway, or transit exchange, so route-selection logic must prevent repeated use of the same defective circuit.
| Routing condition | Continuity result | Typical network action | Main diagnostic focus |
|---|---|---|---|
| Direct circuit is healthy | Positive COT | Continue call setup | Verify normal ISUP timing |
| Bearer path is unavailable | Negative COT | Release circuit and reroute | Check trunk and transmission alarms |
| COT response is delayed | Timeout | Clear or try an alternate route | Review timers and signaling latency |
| CIC mapping is inconsistent | Unexpected result | Reject, clear, or isolate circuit | Compare switch and gateway configuration |
| IP interworking introduces loss | Failed or missing COT | Use alternate gateway or route | Inspect SIGTRAN and media mapping |
A transit exchange can create another variation. It may receive a call with a continuity requirement, perform the test on its outgoing circuit, and return signaling only after the next leg is validated. This protects the end-to-end route, though it can increase post-dial delay and requires consistent timer values across network boundaries.
ISUP Over IP Transport
SIGTRAN transports SS7 signaling over IP, but it does not automatically validate the voice bearer. M2PA, M3UA, and SCTP may carry signaling reliably while the associated media path remains misconfigured. Continuity checking therefore remains relevant when ISUP signaling is transported through an IP signaling gateway.
For engineers mapping legacy SS7 procedures into modern networks, this M2PA signaling guide provides useful context for separating signaling transport from circuit behavior. The gateway must preserve CIC identity, continuity indicators, message ordering, and appropriate response handling across the interworking boundary.
Media gateways may also need to generate, detect, or transparently pass the continuity tone. Codec conversion, echo cancellation, packet loss, or an incorrect timeslot-to-RTP mapping can cause a genuine bearer failure even when SCTP associations and SS7 links appear healthy.
Troubleshooting Failures
A missing COT can result from a blocked message, an expired timer, a remote switch that does not support the requested procedure, or a gateway that drops continuity-related information. Packet captures and SS7 traces should be examined at both signaling points to determine where the expected event disappeared.
A negative COT requires a different investigation. It indicates that the test was received but the circuit could not pass correctly. Engineers should inspect transmission quality, timeslot assignment, trunk polarity where applicable, echo-control equipment, and media gateway configuration. Repeated failures on one CIC suggest a circuit-specific fault; failures across an entire route suggest a broader interworking or transport issue.
Deployment Practices For Reliable Routing
A well-designed routing policy treats continuity results as operational data rather than simple call-clearing triggers. Failure counters, CIC-level alarms, route-quality statistics, and alternate-route usage can reveal gradual degradation before customers experience widespread call failures. The SS7 solutions resource can support broader study of signaling architecture and network troubleshooting concepts.
Recommended practices include:
- Keep ISUP, gateway, and trunk-group timer values aligned across interconnected switches.
- Log IAM, COT, ACM, ANM, REL, and RLC messages with CIC and point-code details.
- Exclude recently failed circuits from immediate route reselection when policy permits.
- Test continuity-tone handling after media gateway, codec, or timeslot changes.
- Correlate COT failures with SIGTRAN association health and physical bearer alarms.
Route diversity should be tested under controlled conditions. A backup path is useful only when its signaling translation, CIC ranges, media mapping, and release behavior have been verified. Regular trace reviews also help identify vendor-specific ISUP differences before they become production incidents.
Apply these scenarios to lab traces and live network records to build a clear relationship between ISUP messages, circuit health, and routing decisions. Use structured continuity-check analysis to improve fault isolation, protect call quality, and make SS7-to-IP network operations more predictable.
