> 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/parameter-reference/point-code.md).

# Point Code

A point code is an address in the SS7 network, identifying an SSP, STP or SCP. How origin and destination point codes work, and how length varies by SS7 variant.

A Point Code (PC) is an address in the SS7 network. It can reference a [SSP](/telecom-references/ss7-and-signalling/ss7/sp.md), STP or SCP. Depending on the [SS7 variants](/telecom-references/parameter-reference/m3ua.md#p), point code may have different [Length](/telecom-references/parameter-reference/m3ua.md#d).

The peer SS7 [SSP](/telecom-references/ss7-and-signalling/ss7/sp.md) address is referred as Destination Point Code or [DPC](/telecom-references/ss7-and-signalling/ss7/dpc.md).

The local SS7 [SSP](/telecom-references/ss7-and-signalling/ss7/sp.md) address is referred as Originating Point code or [OPC](/telecom-references/ss7-and-signalling/ss7/opc.md).

We also sometimes use the term Adjacent Point Code (APC) to identify an entity connected directly to the unit with SS7 links.

The Point codes can be represented in different formats, depending on the [SS7 variants](/telecom-references/parameter-reference/m3ua.md#p):

* For ITU variants, the [Point Code length](/telecom-references/parameter-reference/m3ua.md#d) is 14 bits, in a format 3.8.3
* For Japanese variants, the [Point Code length](/telecom-references/parameter-reference/m3ua.md#d) is 16 bits, in a format 7.4.5
* For ANSI and Chinese variants, the [Point Code length](/telecom-references/parameter-reference/m3ua.md#d) is 24 bits, in a format 8.8.8

Some regions use different formats than the dotted notation. It can either be decimal or hexadecimal. For example:

| Variant | Dotted Notation | Decimal  | Hexadecimal |
| ------- | --------------- | -------- | ----------- |
| ITU     | 2.14.1          | 4209     | 1071        |
| ITU     | 7.250.7         | 16343    | 3FD7        |
| ANSI    | 251.3.1         | 16450305 | FB0301      |

You can use the tool Point Code Converter (PCC), from LogMeTT, to convert between the different formats.

* [LogMeTT.com](http://logmett.com/index.php?/download/point-code-converter-13.html)

### Configuration

To configure Point Codes:

* [Toolpack V2.8](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-ss7-point-codes)
* [Toolpack V2.7](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-ss7-point-codes)
* [Toolpack V2.6](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/ss7-isup/creating-ss7-point-codes)


---

# 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/parameter-reference/point-code.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.