> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7/continuity-testing-call-flow-ccr-cot.md).

# Continuity Testing Call Flow (CCR/COT)

> **Applies to:** Tmedia 2.7

Continuity tests are used to test the speech or transmission path of SS7 circuits. It also ensures that the SS7 ISUP interface circuits (CIC) are aligned with the same physical links (E1/T1) on both ends. Toolpack version 2.7 allows users of the TMG to do ISUP Continuity Testing via 3 methods by CIC Group or individual CIC:

### Incoming Continuity Testing Outside a Call

This circuit testing occurs when one of the nodes wants to validate a currently idle circuit. It is recommended that the switch first blocks the circuit to prevent calls from using the circuit during the testing.

For ITU:

```
         Peer SP                     TMG
           |                          |
           |---------- CCR ---------->|
           |                          | (timeslot loopback)
           |---------- Tone ----------\
           |<-------------------------/
           |                          |
           |---------- REL ---------->|
           |<--------- RLC -----------|
```

For ANSI:

```
         Peer SP                     TMG
           |                          |
           |---------- CCR ---------->|
           |                          | (timeslot loopback)
           |<--------- LPA -----------|
           |                          |
           |---------- Tone ----------\
           |<-------------------------/
           |                          |
           |---------- REL ---------->|
           |<--------- RLC -----------|
```

### Incoming Continuity Testing Within A Call

This circuit testing occurs when the forward side (originating side) sets the ‘continuity test required’ field of the ‘nature of connection indicators’ IE into the IAM message.

Successful continuity check:

```
         Peer SP                     TMG
           |                          |
           |---------- IAM ---------->| 'continuity test required'
           |                          |
           |                          | (timeslot loopback)
           |---------- Tone ----------\
           |<-------------------------/
           |                          |
           |---------- COT ---------->| continuity check successful
           .                          .
           .                          .
           .                          .
           |---------- REL ---------->|
           |<--------- RLC -----------|
```

Failed continuity check with retry from Peer SP:

```
         Peer SP                     TMG
           |                          |
           |---------- IAM ---------->| 'continuity test required'
           |                          |
           |                          | (timeslot loopback)
           |---------- Tone ----------\
           |<-------------------------/
           |                          |
           |---------- COT ---------->| continuity check failed
           |                          |
     Retry |---------- CCR ---------->|
           |                          | (timeslot loopback)
           |---------- Tone ----------\
           |<-------------------------/
           |                          |
           |---------- COT ---------->| continuity check successful
           .                          .
           .                          .
           .                          .
           |---------- REL ---------->|
           |<--------- RLC -----------|
```

### Outgoing Continuity Testing

Users of the Tmedia unit can easily generate, out of call, SS7 ISUP Continuity Tests using the web portal.

```
         Peer SP                     TMG
           |                          |
           |<--------- CCR ---------- |
(timeslot  |                          |
 loopback) |                          |
           /---------- Tone ----------|
           \------------------------->| ccr success or fail
           |                          |
           |<--------- REL -----------|
           |---------- RLC ---------->|
```

### Configuration

* [Web Portal v2.7: Outgoing Continuity Testing](/telecom-references/ss7-and-signalling/ss7/outgoing-continuity-testing.md)

### External Sources

* [Q.784-Isup Basic Call Test Specification](ftp://109.167.129.114/doc/ITU-T/Q/Q0784e.pdf)


---

# 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://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7/continuity-testing-call-flow-ccr-cot.md?ask=<question>&goal=<user_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.