> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/protocols/ss7-circuit-group-control.md).

# SS7 Circuit group control

### To force a block on a SS7 CIC group:

\*\*Status -> SS7 Isup -> Click on the CIC group -> Desired group state \[Blocked] -> Apply States \*\*

Tu put back in default mode:

\*\*Status -> SS7 Isup -> Click on the CIC group -> Desired group state \[default] -> Apply States \*\*

Note: "unblocked" mode will disregard phyical trunk condition

This is a good way to test CIC alignment: All CIC groups are blocked, except the one which needs to be tested. With a COT test or a voice call, the CIC alignment can be verified.

###

Two things can cause a locally blocked condition:

1. The physical trunk that carries the CICs is down.

To verify which trunk this is, go to: **Isup -> Isup\_stack \[edit] -> Isup Interface \[edit]** Verify the Line service attached to the CIC group then, go to the main status and check the trunk **Status -> Tdm Lines -> Line Services**

2. The CIC group has been set to block.

To verify: **Status -> SS7 Isup -> Click on the CIC group -> Desired group state \[default]**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/protocols/ss7-circuit-group-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.