> 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/configuration/web-portal-3-3/protocol-stack/status/sigtran/sigtran-m3uaaspstatus.md).

# M3UA ASP Status

\_\_FORCETOC\_\_

***Applies to version(s): v2.9, v2.10***

This article illustrates how to view M3UA ASP status. This can be done from either the Status menu or the Navigation panel.

#### Status menu

1- Click **Status** in the navigation panel.

2- Click the **SIGTRAN M3ua** tab.

* Note that SCTP is used as the Transport Layer for this protocol, if any firewall is sitting between Telcobridges device and Sigtran network, this firewall needs to be set to allow SCTP traffic to pass through, and enabling the basic connectivity for sigtran link to be up

The status of the M3UA protocol stack is displayed.

StatusM3UA\_SGP\_0.png

#### Navigation Panel

1- Click **M3UA** from the navigation panel.

2- Click the **Status** tab.

3- To configure a periodic refresh of the M3UA status, select a value from **Refresh Every**.

* To view the M3UA SAPS, click the **Saps** tab.

4- To view the status of an M3UA SAP, select an M3UA SAP.

The M3UA SAP status is displayed.

5- To view the status of an M3UA Network, select an M3UA Network.

6- Select a userpart to view its detailed status.

Detailed status is displayed.

7- Select a PSP to view its detailed status.

Detailed PSP status is displayed.

8- Select a PRSV to view its detailed status.

Detailed PSRV status is displayed. (In this example local)

Detailed PSRV status is displayed. (In this example remote)

9- Select a Route to view its detailed status.

Detailed Route status is displayed. (In this example local)

Detailed Route status is displayed. (In this example remote)

**Path**

```
/configurations/@[configuration_name]/m3ua_stacks/@[m3ua_name]/status
```


---

# 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/configuration/web-portal-3-3/protocol-stack/status/sigtran/sigtran-m3uaaspstatus.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.
