> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/tcap/tcap-configuration.md). # TCAP configuration Starting with version 2.3, Toolpack fully exposes [SCCP](/telecom-references/ss7-and-signalling/sccp.md) and [TCAP](/telecom-references/ss7-and-signalling/tcap.md) stack functionality in the Toolpack [web portal](https://tmediadocs.telcobridges.com/other-pages/other/web-portal), making it easier to access TCAP, as well as all new Toolpack features, programmatically. ### Prerequisites Fully implementing the revised Toolpack TCAP support will require that your telephony application interface via the Toolpack application programming interface (API). This will also require migrating settings from the configuration file and entering those settings via Toolpack Web portal. Please note that using the new TCAP functionality requires an existing TCAP-based application. While TelcoBridges does not provide a full sample application as with the [TB Media Gateway](/telecom-references/sip-and-voip/h248-mgcp/tb-media-gateway.md) application, there is a sample application that is available to learn how to use the TelcoBridges TCAP API. Prior to configuring TCAP support, you should have configured all relevant [MTP2](/telecom-references/ss7-and-signalling/mtp2.md) and [MTP3](/telecom-references/ss7-and-signalling/mtp3.md) information. You should also have a good idea of how you are going to use TCAP functionality once it is activated. This includes information related to [SSN](/telecom-references/parameter-reference/sub-system-number.md), such as [destination](/telecom-references/ss7-and-signalling/ss7/dpc.md), [origin](/telecom-references/ss7-and-signalling/ss7/opc.md) point codes, etc. ### Steps * The first step is to configure SCCP and TCAP via the Toolpack web portal. * You configure SCCP in **Global > Configurations > Hardware > SS7 > SCCP**. * You configure TCAP support via **Global > Configurations > Hardware > SS7 > TCAP**. * The next step is to Activate the new configuration, which is performed in the configuration in **Global > Systems**. There you select the system to which you want to apply the configuration, clicking **Edit** besides its name. In the new page that opens, click **Activate** in the **Active Configuration** section. * Once SCCP and TCAP are configured, you can start your TCAP application using the tbx\_ss7\_ha\_tcapctrl library. * Please note that the application name must be the name in the TCAP user part configuration, preceded by “TCAP\_CTRL\_” . For example, the TCAP user part configuration name is TCAP\_ITU\_6, then your application name must be TCAP\_CTRL\_TCAP\_ITU\_6.For further information, please refer to the User Guide that is included with the core Toolpack installation as well as the TCAP sample code provided with Toolpack. ### Related actions * [Creating new transaction](https://tmediadocs.telcobridges.com/other-pages/other/creating-new-transaction) * [Adding component portion](https://tmediadocs.telcobridges.com/other-pages/other/adding-component-portion) * [Sending transaction and dialogue portions](/telecom-references/ss7-and-signalling/tcap/sending-transaction-and-dialogue-portions.md) * [Receiving component portion](/telecom-references/ss7-and-signalling/tcap/receiving-component-portion.md) * [Receiving transaction and dialogue portions](/telecom-references/ss7-and-signalling/tcap/receiving-transaction-and-dialogue-portions.md) * [Receiving transaction error indication](/telecom-references/ss7-and-signalling/tcap/receiving-transaction-error-indication.md) ### References * [Wikipedia article](http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part) --- # 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://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/tcap/tcap-configuration.md?ask=&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.