> 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/cas.md). # CAS > **Applies to:** Tmedia 2.7, 2.8, 2.9, 2.10, 3.0, 3.2, 3.3 Channel Associated Signaling (CAS) is a signaling protocol for the set up and tear down of phone calls. It is different from other signaling protocols, such as [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) because it is not message or packet-based but rather based on bit transition for state changing, and tone transmission for information and state information exchange. In many parts of the world, CAS was first replaced by [ISDN](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/isdn/README.md), and in many cases, was ultimately replaced by SS7. Today, CAS is often used with low-density trunks. ### CAS and TelcoBridges TelcoBridges provides support for various CAS R1 and CAS R2 variants. Please contact TelcoBridges regarding support for additional CAS variants. **Note:** CAS support is limited to E1/T1/J1 interfaces. It is not compatible with DS-3 or STM-1 interfaces. ### CAS R1 Toolpack supports various CASR1 variants on T1 and E1 line interfaces. The TelcoBridges CAS R1 stack features a scriptable register signaling engine that allows the complete customization of CAS R1 variants and call flows, including the creation of new variants that are not provided with Toolpack. Refer to [CASR1 script](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/isdn-cas/casr1-scripting/README.md) for detailed information. **Note:** Support for CAS R1 has been introduced in Toolpack release 2.7.42. #### Supported CAS R1 variants The following CAS variants are currently supported by Toolpack: | CASR1 Variant | RELEASE | | -------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | E\&M "Wink start" (delay start, 1 wink or 2 winks) | 2.7 | | [Loop start user side](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/cas-r1-loopstart-user/README.md) | 2.7 | | [Loop start network side](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/cas-r1-loopstart-network/README.md) | 2.7 | | Ground start user side | 2.8 | | Ground start network side | 2.8 | ### CAS R2 Toolpack supports various CASR2 variants E1 line interfaces. The TelcoBridges CAS R2 stack features a scriptable register signaling engine that, in practice, allows the complete customization of communication processes using tones. More specifically, it is possible to modify the timing(s) of the tone exchanges, change the meaning(s) of each tone and dynamically specify the sequence in which the tones are played. The CAS R2 stack also provides integrated interoperability between variants and between other signaling types. For instance, the calling party category can be converted between variants and propagated to a SS7 call leg. **Note:** Support for CAS R2 was introduced in Toolpack release 2.5. #### Supported CAS R2 variants The following CAS variants are currently supported by Toolpack: | CASR1 Variant | RELEASE | | ----------------------- | ------- | | Generic (ITU spec base) | 2.5 | | Brazil | 2.5 | | Mexico | 2.5 | | Venezuela | 2.7 | Use Toolpack's script-based approach to the management of regional variants. Variants supplied by Toolpack can be adapted to address specific requirements and new variant scripts can be created from scratch, without to need to 'patch' or update the underlying system software version. ### H.248 and CAS Starting with version 2.8, CAS support for H.248 has been added. This means TDM CAS lines can be controlled remotely through H.248 CAS messages. Supported packages are described in the [H.248 page](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/h-248-protocol/README.md#h248-package-support). ### Configuration * [Web Portal v3.2, v3.3: CAS Signaling](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-protocol-stacks/README.md#cas) * [Web Portal v3.0: CAS Signaling](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-3-0-protocol-stacks/README.md#cas) * [Web Portal v2.10: CAS Signaling](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-2-10-protocol-stacks/README.md#cas) * [Web Portal v2.9: CAS Signaling](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/web-portal-2-9-protocol-stacks/README.md#cas) * [Web Portal v2.8: CAS Signaling](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/web-portal-2-8-protocol-stacks/README.md#cas) * [Web Portal v2.7: CAS Signaling](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tsig-and-tdev-web-portal-2-7-tutorial-guide/README.md#cas) ### References * CAS Scripting * [CAS R1 Scripting guide](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/isdn-cas/casr1-scripting/README.md) * [CAS R2 Scripting guide](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/cas-r2-scripting/README.md) * [CAS R2 Troubleshooting guide](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/isdn-cas/toolpack-cas-r2-troubleshooting/README.md) * [H.248](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/h-248-protocol/README.md) * [Wikipedia article](http://en.wikipedia.org/wiki/Channel_Associated_Signaling) * [ITU Q.400-Q.490 Specification](http://www.itu.int/rec/T-REC-Q.400-Q.490-198811-I) --- # 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/cas.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.