> 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-api-states.md).

# SCCP/API States

States information, which can be gathered at any time by SCCP, indicates the current state of the node or route. This information can be used to determine the quality of service. The collection of status information does not affect any of the information examined.

### General States

General explanation of the general state parameters:

* The **Congestion level field** indicates SCCP congestion level. Possible values: 0 to 7.

**Note:** If the congestion level field value is greater than zero, SCCP shall repeatedly generate the SSC message on receipt of every *X* number of messages as specified by the SSC threshold field. If the congestion level field value is zero, SCCP shall stop generating the SSC message.

***

* The SSC threshold field indicates threshold for repeating SSC message in case of SCCP congestion.

**Note:** The SSC threshold field is useful when the value for congestion is greater than zero.

### Route States

General explanation of the SCCP route state parameters:

* The subsystem number field indicates the number of subsystem states in the array SubsystemStates.

#### Point code states

General explanation of the point code states parameters:

* The **Point code state field** indicates the point code status. Possible values:

| Point Code Status | Description                  |
| ----------------- | ---------------------------- |
| Accessible        | Signaling Point Accessible   |
| Inaccessible      | Signaling Point Inaccessible |
| Congested         | Signaling Point Congested.   |

***

* The **Remote state field** indicates the remote SCCP status. Possible values:

| Remote Status | Description                             |
| ------------- | --------------------------------------- |
| Available     | Remote SCCP available                   |
| Unavailable   | Remote SCCP unavailable, reason unknown |
| Unequipped    | Remote SCCP unequipped                  |
| Inaccessible  | Remote SCCP inaccessible                |
| Congested     | Remote SCCP congested                   |

***

* The **Subsystem multiplicity indicator state field** indicates the state of a subsystem multiplicity indicator can have. Possible values:

| SMI Status | Description                 |
| ---------- | --------------------------- |
| Solitary   | Subsystem is not replicated |
| Duplicated | Subsystem is replicated     |
| Unknown    | Unknown                     |

***

* The **Restriction level** field indicates the restriction level for that destination point code. Possible values: 0 to 7.
* The **Restriction sub-level field** indicates the restriction sub-level for that destination point code. Possible values: 0 to 3.
* The **Remote congestion level field** indicates the congestion level for the remote SCCP. Possible values: 0 to 7.
* The **Restricted importance level field** indicates the restricted importance level for that destination point code. This level is passed to user so that user can fill the importance of the subsequent messages to that destination point code. Possible values: 0 to 7.

#### Subsystem states

General explanation of the subsystem states parameters:

* The **Subsystem number field** indicates the subsystem number. Possible values: 1 to 255. See the SCCP SSN value to identify SCCP User table in Toolpack:Create a SCCP route.

***

* The **Subsystem state field** indicates the state of a subsystem can have. Possible values:

| SSN Status                | Description                   |
| ------------------------- | ----------------------------- |
| User out-of-service (OOS) | Subsystem user out of service |
| User in-service           | Subsystem user in service     |
| Unknown                   | Unknown                       |

***

* The **Subsystem multiplicity indicator state field** indicates the state of a subsystem multiplicity indicator can have. Possible values: see the SCCP SMI status from earlier in this page.


---

# 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-api-states.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.