> 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/mtp2-states.md).

# MTP2 States

![Screenshot showing MTP2 status options](https://docs.telcobridges.com/w/images/5/56/Mtp2-status-options-normal.jpg)![Screenshot showing extended MTP2 status options (1/3)](https://docs.telcobridges.com/w/images/6/6d/Mtp2-status-options-extended.jpg)![Screenshot showing extended MTP2 status options (2/3)](https://docs.telcobridges.com/w/images/e/e4/Mtp2-status-options-extended-2.jpg)![Screenshot showing extended MTP2 status options (3/3)](https://docs.telcobridges.com/w/images/c/cb/Mtp2-status-options-extended-3.jpg)States information indicates the current state of the [MTP2](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp2/README.md) Link. This information can be used to determine the quality of service. Status information can be gathered at any time by the host. Collection of status information does not change any information examined.

### Modifiable states

#### Data Link State

The **Data Link State** parameter indicates the current data link functional mode. Changing this value in the Web Portal immediately affects the link state. The following values are allowed:

| Data Link | Description           |
| --------- | --------------------- |
| Enabled   | Data link is enabled  |
| Disabled  | Data link is disabled |

#### Reported status

* The **Up** flag indicates if the current state of a MTP2 link is up or down. Possible values are 'yes' or 'no'
* The **Aligned** flag indicates if the link is aligned or not. Possible values are 'yes' or 'no'
* The **Flow control** flag indicates if flow control is currently being applied to upper layers (i.e. MTP3). Possible values are 'yes' or 'no'. This flag is automatically handled by the Toolpack framework.
* The **Remote congested** flag indicates if a remote congestion status is signaled. Possible values are 'yes' or 'no'
* The **Remote processor outage** flag indicates if the remote-end processor outage is currently declared. Possible values are 'yes' or 'no'

#### Reported extended status

The following additional parameters are visible by clicking on the 'Extended status' checkbox as in the second, third and fourth screenshots on the right:

* The **Local congestion state** flag indicates if a local congestion status is currently active. Possible values are 'on' or 'off'. This condition is automatically updated by the MTP2 link has reached its bandwidth limit.
* The **Alarm generation state** flag indicates if the alarm signal are propagated to the upper layers (i.e. MTP3). Possible values are 'on' or 'off'. This condition is automatically handled by the Toolpack framework.
* The **Local processor outage state** flag indicates if a local congestion status is currently active. Possible values are 'on' or 'off'. This condition is automatically updated by the system when ob-board ressources (memory or CPU) are getting low.
* The **Number outstanding frame** parameter indicates the number of outstanding frames in MTP layer 1
* The **Number dropped frame** parameter indicates the number of frames dropped by the MTP layer 1
* The **Current forward sequence** parameter indicates the current forward sequence number
* The **Current backward sequence** parameter indicates the current backward sequence number
* The **Retransmission count** parameter indicates the retransmission count of MSUs
* The **Transmit queue size** parameter indicates the current transmit queue size


---

# 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/mtp2-states.md?ask=<question>&goal=<endgoal>
```

`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.