> 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-specification.md).

# MTP3 Specification

TelcoBridges' implementation of [MTP3](/telecom-references/ss7-and-signalling/mtp3.md) functionality conforms to the following standards:

* ETS 300 008 – Integrated Services Digital Network; CCITT Signaling System No 7, Message Transfer Part to Support International Interconnection, ETSI.
* GF001-9001 – Technical Specifications of SS7 for National Telephone Network of China, CHINA.
* GR-246, Issue 3, T1.111.4 – Signaling Network Functions and Messages, Bellcore, December 1998.
* GR-246, Issue 3, T1.111.5 - Signaling Network Structure, Bellcore.
* GR-246, Issue 3, T1.111.7 - Testing and Maintenance, Bellcore.
* INTERNET-DRAFT– SS7 MTP3-User Adaptation Layer (M3UA).
* IS 7498 – Open Systems Interconnection – Basic Reference Model, ISO.
* IS 7498 DAD 1 – Open Systems Interconnection – Basic Reference Model Addendum 1: Connectionless, Data Transmission, ISO.
* JT - Q.704 – MTP Signaling Network Functions, Telecommunication Technology Committee (TTC), Japan.
* JT - Q.707 – MTP Testing and Maintenance, Telecommunication Technology Committee (TTC), Japan.
* Q.700 – Introduction to CCITT Signaling System No. 7, CCITT.
* Q.701 – Functional Description of the Message Transfer Part of Signaling System No.7, CCITT.
* Q.702 – Signaling Data Link, CCITT.
* Q.703 – Signaling Link, CCITT.
* Q.704 – Signaling Network Functions and Messages, CCITT.
* Q.705 – Signaling Network Structure, CCITT.
* Q.706 – Message Transfer Part Signaling Performance, CCITT.
* Q.707 – Testing and Maintenance, CCITT.
* Q.708 – Number of International Signaling Point Codes, CCITT.
* Q.709 – Hypothetical Signaling Reference Connection, CCITT.
* Q.710 – Simplified MTP Version for Small Systems, CCITT.
* Q.752 – Monitoring and Measurements for Signaling Systems No.7 Networks, CCITT, 1997.
* Q.782 – MTP Level 3 Test Specification, CCITT.
* Q.2140 – MTP Level 3 Functions and Messages Using the Services of ITU Q.2140, ITU.
* Q.2210 – MTP Level 3 Functions and Messages Using the Services of CCITT Recommendation Q.2140, ITU.
* RFC 2719 – Framework Architecture for Signaling Transport, IETF.
* T1.111.4 – Signaling Network Functions and Messages, ANSI.
* T1.111.5 - Signaling Network Structure, ANSI.
* T1.111.7 - Testing and Maintenance, ANSI.

### Protocol variants

* ANSI (used for ANSI88 and ANSI92)
* ANSI96 (used for ANSI96 and TELCORDIA)
* ITU (used for ITU88, ITU92, ITU97, Q767, SINGAPORE and ETSI)
* CHINA


---

# 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-specification.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.