> 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/ss7-and-signalling/mtp3/mtp3-statistics.md). # MTP3 Statistics The [MTP3 layer](/telecom-references/ss7-and-signalling/mtp3.md) can gather statistics information at any time to measure the performance of the MTP3 software. This information can be used to determine the distribution of traffic loads and quality of service (QoS) parameters, and to assist in MTP3 software debugging. The collection of statistics information may or may not result in the counters being reset. ### General statistics The following statistics are available for query/display: * The **Unavailable received message** counter indicates the number of userpart unavailable messages received for a user of this layer * The **Unavailable transmit message** counter indicates the number of userpart unavailable messages transmitted because of an unavailable user at this layer * The **Traffic restart transmit message** counter indicates the number of traffic restart allowed messages transmitted * The **Traffic restart received message** counter indicates the number of traffic restart allowed messages received * The **Traffic restart waiting transmit message** counter indicates the number of traffic restart waiting messages transmitted for the ANSI version * The **Traffic restart waiting received message** counter indicates the number of traffic restart waiting messages received for the ANSI version * The **MSU dropped due to routing error** counter indicates the number of drops that may have occurred for the following reasons: * Self or adjacent restart is in progress * SLS value is wrong * Circular routing * MSU is received at an [SP](/telecom-references/ss7-and-signalling/ss7/sp.md) for some other node (SP cannot route) * The destination is unreachable or unavailable * The layer encounters an illegal routing configuration or a bad packet ### Other statistics * [Link Statistics](/telecom-references/ss7-and-signalling/mtp3/link-statistics.md) * [Route Linkset Statistics](/telecom-references/ss7-and-signalling/mtp3/route-linkset-statistics.md) * [Route Statistics](/telecom-references/ss7-and-signalling/mtp3/mtp3-route-statistics.md) --- # 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/telecom-references/ss7-and-signalling/mtp3/mtp3-statistics.md?ask=&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.