> 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-addressing.md). # MTP3 Addressing [MTP3](/telecom-references/ss7-and-signalling/mtp3.md) fully supports the use of addresses to identify [Signaling Points](/telecom-references/ss7-and-signalling/ss7/sp.md) (SPs). The following section describes signaling points in detail. ### Signaling points Signaling points are identified using [Destination Point Codes](/telecom-references/ss7-and-signalling/ss7/dpc.md) (DPCs). DPCs can be a number, up to 24 bits, based on the variant (for example, ITU has 14 bit DPC, ANSI has 24 bit DPC). In MTP3 software, each point code can be uniquely identified as a local SS7 point code or a remote SS7 point code. In MTP3 software, each signaling point is additionally identified by a network identifier (ID) which is unique to all signaling point codes within the network. This addressing is useful for simultaneously supporting multiple variants of MTP3 where each signaling point can be addressed by MTP3 using the combination of DPC and network ID. (**Note:** By virtue of the network ID, MTP3 can support the same DPC value for more than one signaling point if each of the signaling points that have the same DPC value belongs to a different network.) The Destination Point Code (DPC), [Origination Point Code](/telecom-references/ss7-and-signalling/ss7/opc.md) (OPC), and [Signaling Link Selection](/telecom-references/ss7-and-signalling/ss7/sls.md) (SLS) fields are part of the routing label in MTP3. The service indicator and network indicator are part of the Service Information Octet (SIO) of the MSU. The service indicator is four bits and can indicate an MTP service user or signaling network management service. The network indicator is two bits and can indicate a national or international network. --- # 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-addressing.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.