ISUP Circuit Supervision: Blocking, Unblocking, and Reset
ISUP circuit supervision keeps voice circuits in a usable, predictable state across switches and signalling points. It tells neighbouring exchanges whether a bearer is available for call setup, temporarily withdrawn from service, or in need of reinitialisation after a fault.
This matters in networks that combine traditional SS7, TDM trunks, and SIGTRAN links. Australian carriers may still rely on interconnect arrangements spanning major exchanges in Sydney and Melbourne, regional Queensland, Western Australia, and remote areas where a single faulty circuit can affect service quality quickly.
| Message | Main purpose | Circuit effect | Common use |
|---|---|---|---|
| BLO | Block one circuit | Prevents new call attempts | Local maintenance or detected fault |
| UBL | Unblock one circuit | Returns one circuit to service | Maintenance completed |
| CGB | Block a circuit group | Withdraws selected circuits | Group maintenance or network protection |
| CGU | Unblock a circuit group | Restores a circuit group | Recovery after planned work |
| RSC | Reset one circuit | Clears inconsistent circuit state | Stuck call or signalling mismatch |
| GRS | Reset a circuit group | Reinitialises multiple circuits | Broad fault recovery |
What circuit supervision controls
A circuit is more than a timeslot or voice path. ISUP associates it with a Circuit Identification Code, or CIC, and maintains a shared view of whether that resource can carry a new call. The originating and terminating exchanges must agree on this state, or one side may attempt to seize a circuit that the other considers unavailable.
Messages such as BLO, UBL, CGB, CGU, RSC, and GRS support this coordination. Training material from SS7 Training is useful when mapping these messages to MTP3 routing, ISUP call handling, and the wider PSTN architecture.
Circuit supervision is separate from call release. An REL message clears a particular call, while a blocking message changes whether the circuit can be selected for future calls. That distinction is essential when troubleshooting repeated call failures.
Blocking and unblocking in ISUP
A BLO message applies to an individual circuit. It can be sent because of planned maintenance, a local hardware alarm, a failed continuity check, or a remote instruction. Once the receiving exchange accepts the block, its call-routing logic should stop selecting that CIC for new outgoing calls.
UBL reverses an individual block after the underlying issue has been resolved. A carrier should not treat an unblocking message as proof that the bearer is healthy; the switching platform, transmission path, and far-end state still need to agree before normal traffic resumes.
For several circuits, CGB and CGU provide group supervision. The message includes a circuit group range and a status bit map, allowing selected CICs to be blocked or restored together. This is practical during planned work on a trunk between, for example, a metropolitan exchange and a regional gateway.
Resetting a troubled circuit
RSC is intended to bring one circuit back to a known state. It is commonly used when one switch believes a call remains active while the other has already released it, or when a circuit is left in an unexpected state after a signalling interruption. The receiving switch should clear relevant call context and update its circuit state.
GRS performs a similar function across a group. It can be valuable after a link outage, processor restart, or major mismatch in circuit status. Because a group reset can affect many resources at once, operators must understand its scope before applying it to a busy route.
Reset is not a substitute for investigating the cause. If RSC or GRS appears repeatedly, examine link stability, CIC mapping, point-code configuration, route alignment, and the behaviour of both signalling endpoints.
How state changes travel through the network
ISUP supervision normally rides over an SS7 signalling relationship, with MTP3 providing message routing and lower layers carrying the signalling link. In IP-based environments, SIGTRAN transports the SS7 user part over networks using protocols such as SCTP and M3UA. The transport may change, but the need for consistent circuit state remains.
A blocked circuit must be excluded from route selection at the correct switch. If only one side records the block, calls may still produce failures such as circuit unavailable, no circuit, or abnormal release. This is why traces should be collected at both ends of an interconnect rather than from a single exchange.
Australian operators also need to account for mixed network generations. A route may connect an IP softswitch to a legacy tandem, with signalling translated or carried through gateways. Number portability, carrier interconnect rules, and the continuing importance of the 000 emergency service make accurate route and state handling especially important.
Timers, alarms, and diagnosis
Timers help prevent a circuit from remaining indefinitely in an uncertain condition. Exact names and values depend on the ISUP variant and vendor, but engineers should correlate timer expiry with IAM, ACM, ANM, REL, BLO, UBL, and reset events. A timer alarm without the surrounding message sequence rarely identifies the real fault.
A practical trace review checks the CIC, point codes, linkset, message direction, and timestamp. Compare the local circuit state with the remote state, then verify whether the switch’s routing tables have removed or restored the circuit as expected. The solutions library can support this kind of protocol-focused review.
Pay attention to patterns rather than isolated alarms. A single RSC after a maintenance window may be harmless; a growing stream of resets on a Perth–Adelaide route, for instance, could indicate transmission errors, a gateway problem, or inconsistent circuit numbering.
Operational checks for Australian networks
Use a disciplined process when a trunk shows blocking, unblocking, or reset activity. In plain Aussie terms, the aim is to find whether the circuit is genuinely crook or whether the signalling view is wrong.
- Confirm the CIC and circuit group against the interconnect record.
- Check both signalling endpoints and the associated bearer path.
- Match message timestamps with alarms and maintenance windows.
- Verify that call routing excludes blocked circuits.
For networks covering long distances or smaller regional exchanges, also review:
- Link quality during peak periods and severe weather.
- SIGTRAN association and SCTP path status.
- Gateway behaviour between TDM and IP domains.
- Emergency, mobile, and ported-number routing impacts.
Document each state change and its operational reason. This helps teams in Brisbane, Hobart, or remote Western Australia distinguish a planned outage from a fault that needs escalation.
A practical path to reliable supervision
Good ISUP operation depends on consistent circuit inventories, matching CIC maps, clear maintenance procedures, and traces that show both signalling and bearer conditions. Blocking should protect the network from bad resources, unblocking should restore only verified resources, and resetting should return a confused circuit to a clean state without hiding a recurring defect.
Begin with one affected CIC, capture the complete message sequence at both ends, compare the local and remote states, and record the result before changing a wider circuit group.
