> 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/other-pages/ss7-and-sigtran/sctp.md).

# SCTP

#### ***Applies to version(s): v2.5, v2.6.***

These menus can be accessed through the **SCTP tab** of the system status menu.

General and detailed status information about the SCTP service access points (**SAPs**) and transport service access points (**TSAPs**).

### General view

A list of SCTP SAPs and their states can be viewed in the general window (entries in **red** indicate inactive SAPs).

1- SCTP SAP general view:

![Toolpack v2.5 SCTP SAP Menu](https://docs.telcobridges.com/w/images/d/d3/Toolpack_v2.5_SCTP_SAP_Menu.png)

2- SCTP TSAP general view:

![Toolpack v2.5 SCTP TSAP Menu](https://docs.telcobridges.com/w/images/9/95/Toolpack_v2.5_SCTP_TSAP_Menu.png)

### SCTP SAP Detailed Status

By clicking an active link in the SCTP SAP menu, detailed information concerning SCTP SAPs and TSAPs can be viewed. Status information about the SAP is displayed first, and a complete status description of the associated TSAP is displayed below.

![Toolpack v2.5 SCTP SAP Detailed Menu](https://docs.telcobridges.com/w/images/2/28/Toolpack_v2.5_SCTP_SAP_Detailed_Menu_.png)


---

# 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/other-pages/ss7-and-sigtran/sctp.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.