> 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/telecom-references/ss7-and-signalling/mtp3/mtp3-flow-control.md).

# MTP3 Flow Control

The [MTP3](/telecom-references/ss7-and-signalling/mtp3.md) software aids to data flow control are based on [layer 2](/telecom-references/ss7-and-signalling/mtp2.md) inputs. When a link is congested, as indicated by a flow control indication from layer 2, MTP3 starts queuing traffic meant for that link. MTP3 also maintains thresholds for the queued messages. For each threshold, MTP3 performs one of the following actions:

* Send a transfer controlled message at an STP in response to a data received from the adjacent point code for routing to a remote point code
* Send a status indication to its service users at an SP in response to a data transfer request received from user
* Drop the data if the priority with which the data to be sent is lower than the current congestion threshold (only for national networks with multiple congestion priorities).

The above actions allow the data originating entities to take appropriate actions in case of heavy loads and also prevents system crashes due to lack of resources.


---

# 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/telecom-references/ss7-and-signalling/mtp3/mtp3-flow-control.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.