> 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/circuit-group-functions.md). # Circuit group functions The [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) protocol offers some circuit group actions which affect more than one circuit at the same time. Amongst those actions are RESET, BLOCK and UNBLOCK. To understand how these work, the end-user must first know that a group is defined by a mutual agreement between two peer [ISUP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/isup/README.md) nodes about which circuits are part of which group. It also means that there is no ‘group ID’ or a similar concept that is carried over to SS7 MSUs. When the ISUP layer receives a group command, it has to calculate which circuits are to be affected according to the configuration it has and three parameters from the received command (current [CIC](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/circuit-identification-code/README.md), range value and the status bit field). In every group event, the “range and status” IE indicates which circuits are affected by the command. Since the command is also received on a specific circuit, the layer calculates which circuits are affected starting from that circuit. (Please refer to the IE definition here.) Please also note that certain third-party models of SS7 hardware require group functions to be sent on the CIC of the first circuit in a circuit group and will simply ignore group commands that are not addressed that way. **NOTE:** For better interoperability with other equipment, you should always send group commands on the first circuit of a circuit group and fill the range (and/or status bit field) accordingly. --- # 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/circuit-group-functions.md?ask=&goal= ``` `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.