> 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/mtp2/mtp2-statistics.md). # MTP2 Statistics Statistics are gathered to measure the [MTP Level 2](/telecom-references/ss7-and-signalling/mtp2.md) software performance. This information can be used to determine the distribution of traffic loads and the quality of service, and to assist in MTP Level 2 software debugging. Statistical information conforms to CCITT standard Q.752. Statistics information can be gathered at any time by the host. Collection of statistics information may or may not result in the counters being reset. The following statistics are available for query/display: * The 'In service duration' parameter indicates the time since the link was aligned last time * The 'Local busy duration' parameter indicates the total time for which link remained locally congested * The 'Number failure counter' indicates the total number of times link has failed for any reason * The 'Number abnormal failure' counter indicates the number of times link has due to 2 out of 3 consecutive abnormal backward sequence numbers or forward indicator bits * The 'Number acknowledgement failure' counter indicates the number of times link has failed due to excessive delay in acknowledgment from the remote end (T7 expiry) * The 'Number error failure' counter indicates the number of times link has failed due to excessive error rate on the link (SUERM threshold reached) * The 'Number congestion failure' counter indicates the number of times link has failed due to excessive congestion on remote end (T6 expired) * The 'Number alignment failure' counter indicates the number of times proving/alignment attempt has failed on the link * The 'Number signal unit error' counter indicates the number of signaling units received in error on the link * The 'Number negative acknowledgment' counter indicates the number of times negative acknowledgment has been received on the link. * The 'Number SIF/SIO transmitted' counter indicates the number of SIF/SIO packets transmitted. * The 'Number bytes retransmitted' counter indicates the number of octets retransmitted on the link. * The 'Number information frame' transmitted counter indicates the number of information frame transmitted on the link. * The 'Number LSSU transmitted' counter indicates the number of LSSU frame transmitted on the link. * The 'Number FISU transmitted' counter indicates the number of FISU frame transmitted on the link. * The 'Number SIF/SIO received' counter indicates the number of SIF/SIO packets received on the link. * The 'Number information frame received' counter indicates the number of information frame received. * The 'Number receive ready frame received' counter indicates the number of "Receive ready" frame received. * The 'Number receive not ready frame received' counter indicates the number of "Receive not ready" frame received. * The 'Received peak bandwidth' parameter indicates the maximum bytes received in one second. * The 'Received current bandwidth' parameter indicates the number of bytes received in the last second. * The 'Transmit peak bandwidth' parameter indicates the maximum bytes transmitted in one second. * The 'Transmitted current bandwidth' parameter indicates the number of bytes transmitted in the last second. --- # 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/mtp2/mtp2-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.