ISUP Circuit Groups: RSC and GRS Maintenance
ISUP circuit groups connect telephone exchanges through logical circuits identified by Circuit Identification Codes (CICs). When a circuit becomes unusable, signalling must bring both ends back to a known state before the path carries another call. Two important maintenance messages support this process: Reset Circuit (RSC) and Group Reset (GRS).
The distinction matters in SS7 operations. RSC targets one CIC, while GRS resets a consecutive range of circuits. Understanding their message flow, acknowledgements, timers, and operational risks helps engineers maintain PSTN and SIGTRAN-connected networks without creating avoidable call failures.
Circuit Groups In ISUP Networks
An ISUP trunk group contains multiple bearer circuits between exchanges. Each voice path has a CIC, while messages such as IAM, ACM, ANM, REL, and RLC control call establishment and release. MTP3 or an IP-based SIGTRAN stack carries the signalling separately from the bearer channel.
A circuit can remain logically busy after a switch reboot, signalling link failure, or incomplete call release. In that condition, the exchange may block new calls even though the physical timeslot is free. Training material such as these SS7 learning resources helps engineers connect CIC state, ISUP procedures, and lower-layer signalling behaviour.
Reset Circuit For An Individual CIC
RSC is used when maintenance needs to reset one circuit. The message identifies the affected CIC and tells the remote exchange to clear its local state for that bearer. The receiving side normally returns a Reset Circuit Acknowledgement (RLC), confirming that the reset procedure has been accepted.
RSC is appropriate for a single stuck circuit, a suspected bearer fault, or recovery after inconsistent state detection. It should not be treated as a general substitute for call release. Engineers must check whether a live call exists, whether the circuit is locally blocked, and whether the remote switch has responded within the relevant timer period.
Group Reset For A Circuit Range
GRS applies to a group or contiguous range of CICs. Its message includes the starting CIC and the range or number of circuits covered. The remote exchange resets each applicable circuit and responds with Group Reset Acknowledgement (GRA), subject to the vendor’s implementation and network profile.
This is useful after a trunk restart, signalling restoration, or broad state mismatch. It also carries greater risk: a poorly specified range can interrupt active calls or place healthy circuits into an unavailable state. Engineers should verify CIC numbering, trunk direction, and the intended circuit count before sending GRS.
Comparing RSC And GRS Behaviour
The choice between the two messages should match the fault scope. A single anomalous CIC favours RSC, while a restart affecting many circuits may justify GRS. Both procedures require coordination between local and remote circuit states.
| Aspect | RSC | GRS |
|---|---|---|
| Target | One CIC | A defined CIC range |
| Typical use | Individual stuck or faulty circuit | Trunk recovery or broad state mismatch |
| Acknowledgement | RLC | GRA |
| Operational risk | Usually limited | Higher if the range is wrong |
| Verification | One circuit state | Every circuit in the specified range |
After acknowledgement, the exchange should show the circuit or range as idle and available, unless a separate blocking condition remains. A successful response does not prove that the bearer, transmission path, or remote switch is healthy; it only confirms completion of the reset procedure.
Maintenance Workflow And Timers
A sound workflow begins with alarms, CIC state records, and recent call traces. Confirm the affected trunk, identify whether the issue is isolated or widespread, and check for signalling link instability. The operator should then select RSC or GRS, transmit it through the correct signalling route, and watch for RLC or GRA.
Timers prevent the process from waiting indefinitely. If an acknowledgement does not arrive, capture MTP3 and ISUP traces, inspect link-set status, and check whether the far end supports the expected message. Repeated resets can conceal a transport, configuration, or hardware fault, so escalation should follow a defined threshold.
Checks For Safe Circuit Recovery
Maintenance teams can reduce service impact by checking the following before and after a reset:
- Confirm the CIC range and trunk direction
- Check active calls and local blocking states
- Record the reset time and acknowledgement
- Verify idle, available, and continuity status afterwards
Useful evidence for a fault record includes:
- ISUP message traces with timestamps
- MTP3 link and route status
- Switch alarms and bearer-channel results
- The operator, change reference, and affected CICs
In a SIGTRAN environment, also inspect SCTP associations, ASP or SGP status, and routing-key configuration. An IP transport path can be established while an application or signalling route remains unavailable, so circuit maintenance should be correlated with the full protocol stack.
Australian Network Considerations
Australian operators manage a mixture of modern IP infrastructure and legacy signalling interworking. A fault affecting a metropolitan trunk in Sydney or Melbourne may be handled quickly through central operations, while a regional path near Cairns, Darwin, or Perth can involve longer restoration windows and different transmission dependencies.
The local market also includes long-distance traffic, mobile interconnects, hosted voice, and enterprise services built across carrier boundaries. Engineers often need plain, direct coordination—“check the far end” and “confirm the CIC range”—because a reset on one network can affect another provider’s service state. Planned work should account for Australian time zones and peak calling periods.
Resilience planning matters for hospitals, emergency services, and distributed facilities. Guidance on edge resilience planning is relevant when signalling systems connect to geographically dispersed applications that cannot tolerate an unexplained circuit outage.
Practical Takeaways For Engineers
RSC is a precise tool for one CIC; GRS is a controlled reset for a defined circuit group. Neither should be sent casually, and neither replaces investigation of failed links, incorrect routing, bearer faults, or persistent remote state problems.
Keep the operational sequence simple: identify the scope, validate the CIC details, send the appropriate reset, confirm the acknowledgement, and prove service availability with traces and test calls. The next concrete step is to create a runbook entry showing the exact RSC and GRS procedure for one production trunk group.
