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

# TCAP TCAP Configuration

General guidelines for configuration of TCAP for proper operation include the following steps:

1. The TCAP [general configuration](/telecom-references/ss7-and-signalling/tcap/tcap-general-configuration.md) must precede all other messages (other configuration TCAP allocation, get, states and stats). The response of this message is a TCAP handle. (**Note:** All fields of a configuration message alloc must be filled unless explicitly optional or not defined for certain variants.)
2. The TCAP [userpart configuration](/telecom-references/ss7-and-signalling/tcap/tcap-userpart-configuration.md) must be made (with the TCAP handle from step 1) for a particular subsystem number. The response of this message is a TCAP userpart handle.

**Note:** For any reconfiguration with a TCAP message, all reconfigurable parameters must be filled appropriately even if the intention is to modify a single parameter.

**Note:** Step 2 must be repeated for each userpart to configure.

### Related actions

* [TCAP general configuration](/telecom-references/ss7-and-signalling/tcap/tcap-general-configuration.md)
* [TCAP userpart configuration](/telecom-references/ss7-and-signalling/tcap/tcap-userpart-configuration.md)


---

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