> 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/ss7-and-signalling/ss7/outgoing-continuity-testing.md). # Outgoing Continuity Testing This new feature for version 2.7 allows users of the TMG unit to generate out of call SS7 ISUP Continuity Tests. Continuity tests are used to make sure that the SS7 ISUP interface circuit groups (CIC) are aligned with the physical links (E1/T1) To do so, go the ISUP interface Circuit group: ``` Status -> SS7 ISUP -> Select Circuit Group -> Start continuity check -> Yes ``` ![CIC group COT](https://docs.telcobridges.com/w/images/e/e2/CIC_group_COT.png) And then ``` Apply States ``` This will send a ISUP CCR messages with the CIC value of these circuits, for every circuit in the group, and will send tones in-band that will be detected if the remote device has put itself in loopback. The results will be shown in the Status page: ``` Last ccr success cnt ``` or ``` Last ccr fail cnt ``` It is also possible to do COT testing per circuit by clicking on **Circuits** ### Related Links * [SS7 ISUP Status Menu](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/ss7-and-sigtran/status-menus-ss7-isup) * [Configuring an ISUP Interface](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-an-isup-interface) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://prosbcdocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7/outgoing-continuity-testing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.