> 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/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/cas/create-cas-r2-stack.md).

# Create CAS Stack

> **Applies to:** Tmedia 3.0, 3.2, 3.3

Once the necessary underlying CAS structures have been configured, you must create a new CAS R2 stack.

The TelcoBridges CAS 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 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.

To create a CAS stack:

1- Click **CAS** in the navigation panel

![CASR2 0 A](https://docs.telcobridges.com/w/images/b/b8/CASR2_0_A.png)

2- Click **Create New CAS Stack**

![CASR2 1 B](https://docs.telcobridges.com/w/images/b/bb/CASR2_1_B.png)

3- Configure the new CAS stack:

* Make sure the **Enabled** box is checked
* Enter a **name** for the stack
* Select a **line service**
* Select a **variant script**
* Click **Create**

![CASR2 2 C](https://docs.telcobridges.com/w/images/5/5c/CASR2_2_C.png)

4- Verify that the **"CAS stack was successfully created"** message is displayed.

![CASR2 3 B](https://docs.telcobridges.com/w/images/1/1e/CASR2_3_B.png)

### List of Parameters

* [Enabled](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/sip#e)
* [Name](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Line Service](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/tdm#l)
* [Variant Script](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/tdm#v)


---

# 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/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/cas/create-cas-r2-stack.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.