> 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/sccp/sccp-addressing.md).

# SCCP Addressing

The [SCCP](/telecom-references/ss7-and-signalling/sccp.md) software supports the numbering plan contained in the 1996 ITU Q.713 - Q.714 and ANSI T1.112 recommendations. It places no constraints on the numbering scheme except those outlined in the 1996 ITU recommendations.

The figure immediately below illustrates the ITU addressing architecture for SCCP. The SCCP software supports from 1 to 128 digits (64 octets) within the address field.

![SCCP addressing ITU](https://docs.telcobridges.com/w/images/0/0b/SCCP-addressing-ITU.jpg)

***

The second figure illustrates the ANSI addressing architecture in SCCP:

![SCCP addressing ANSI](https://docs.telcobridges.com/w/images/c/c4/SCCP-addressing-ANSI.jpg)

***

The address information can take the following forms:

* [DPC](/telecom-references/ss7-and-signalling/ss7/dpc.md) + ([SSN](/telecom-references/parameter-reference/sub-system-number.md) or [global title](/telecom-references/developer-reference/routing-scripts/global-title.md) or both)
* Global title
* Global title + SSN


---

# 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/sccp/sccp-addressing.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.