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

# SCCP Routing

The [SCCP](/telecom-references/ss7-and-signalling/sccp.md) software routes data based on:

* [DPC](/telecom-references/ss7-and-signalling/ss7/dpc.md) + [SSN](/telecom-references/parameter-reference/sub-system-number.md)
* DPC + [global title](/telecom-references/developer-reference/routing-scripts/global-title.md)
* DPC + global title + SSN
* Global title
* Global title + SSN
* ISNI + Global title (Valid only for ANSI 96 and GR-246-CORE Issue 5).
* INS + Global title (Valid only for GR-246-CORE Issue 5).

When a message is received from SCCP user (upper layer), the point code determines whether the message is processed further locally or sent to a remote node.

When a message is received from [MTP Level 3](/telecom-references/ss7-and-signalling/mtp3.md) (lower layer), the point code is ignored, and the routing indicator determines whether global title translation is required or the message is passed to an SCCP user. Global title translation can result in a remote point code.

SCCP can perform routing based on the ISNI parameter as specified in T1.112.4 (ANSI 1996, GR246-CORE Issue 5, December 2000-Telcordia). SCCP can perform routing based on INS parameter as specified in T1.112.4 (GR246-CORE Issue 5, December 2000 -Telcordia).


---

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