> 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/sub-system-number.md).

# Sub-System Number

The SS7 SCCP sub-system number (SSN): what it identifies, the 1-255 value range, and the full table of assigned SSN values and the SCCP user each one denotes.

The Sub-System Number parameter is used to assign a sub-system number to an object within the SS7 SCCP control layer.

Integer values for this parameter are entered into a field.

Allowable values are from 1 to 255.

| SSN value | SSN SCCP user      | Description                                               |
| --------- | ------------------ | --------------------------------------------------------- |
| 0         | Unknown            | SSN not known or not used.                                |
| 1         | SCCP management    | SCCP management                                           |
| 3         | ISUP               | ISDN user part                                            |
| 4         | OMAP               | Operation, Maintenance and Administration Part            |
| 5         | MAP                | Mobile Application Part                                   |
| 6         | HLR                | Home Location Register (MAP)                              |
| 7         | VLR                | Visitor Location Register (MAP)                           |
| 8         | MSC                | Mobile Switching Center (MAP)                             |
| 9         | EIR                | Equipment Identifier Register (MAP)                       |
| 10        | AUC                | Authentication Center                                     |
| 11        | ISDN supplementary | ISDN Supplementary services                               |
| 13        | BISDNE2EAPP        | Broadband ISDN Edge-to-Edge Application                   |
| 14        | TCTR               | TC Test Responder                                         |
| 142       | RANAP              | Radio Access Network Application Part                     |
| 143       | RNSAP              | Radio Network Subsystem Application Part                  |
| 145       | GMLC               | Gateway Mobile Location Centre (MAP)                      |
| 146       | CAP                | CAMEL application part                                    |
| 147       | gsmSCF             | Global System for Mobile Service Control Function (MAP)   |
| 148       | SIWF               | Serving GPRS Support Node (MAP)                           |
| 149       | SGSN               | Serving GPRS Support Node (MAP)                           |
| 150       | GGSN               | Gateway GPRS Support Node (MAP)                           |
| 249       | PCAP               | Positioning Calculation Application Part                  |
| 250       | BSC BSSAP          | BSC Base Station System Application Part (BSSAP-LE)       |
| 251       | MSC BSSAP          | MSC Base Station System Application Part (BSSAP-LE)       |
| 252       | SMLC BSSAP         | Serving Mobile Location Center (BSSAP-LE)                 |
| 253       | BSSOM              | Base Station System Operation & Maintenance (A-interface) |
| 254       | BSSAP              | Base Station System Application Part (A-interface)        |


---

# 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/sub-system-number.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.