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

# TCAP States

States information, which can be gathered at any time by [TCAP](/telecom-references/ss7-and-signalling/tcap.md), indicates the current state of the userpart. 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 explanation of the TCAP userpart states parameters:

* The **protocol variant field** indicates the TCAP protocol variant of the userpart. Possible values: see the TCAP protocol variant table in [TCAP:Userpart configuration](/telecom-references/ss7-and-signalling/tcap/tcap-userpart-configuration.md)

***

* The **status field** indicates the status of the userpart

| Alarm category | Description                             |
| -------------- | --------------------------------------- |
| Unbound        | Unbound to SCCP user-part               |
| Configured     | User-part configured                    |
| Bound          | Bound to SCCP user-part                 |
| Confirm        | Waiting for SCCP user-part bind confirm |
| Pending        | Bind pending                            |


---

# 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/tcap/tcap-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.