> 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/protocols/tcap.md). # TCAP ![Schematic showing TCAP in the OSI model.](https://docs.telcobridges.com/w/images/3/31/TCAP-OSI_model.jpg)The TCAP layer provides communication capabilities for interactive applications in a distributed environment. TCAP originated from ITU Recommendations X.219 and X.229 (ROSE, Remote Operation Service Element). TCAP layer uses transport services provided by [SCCP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sccp/README.md) to implement transaction capabilities application services. TCAP defines the end-to-end protocol between TCAP users, which may be located in a [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) network or in another network supporting TCAP protocol. The graphic on the right show how TCAP fits into the [OSI model](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/osi-model/README.md). ### Features TCAP supports the following features: * Single transaction/dialogue identifier specified by service user * Simultaneous dialogues per application/subsystem number * Components (operations and their replies) and parameters assembly into TCAP messages * Dialogue and user information assembly into [TCAP messages](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/message/README.md) * Association of operations and their replies * Abnormal situations handling * Optional operations/replies timers (ITU) * Unstructured dialogue to send one or more components that do not expect replies * Structured dialogue to send one or more components that expect replies * Structured dialogue supporting the following transaction message types: begin, continuation, end, query with/without permission, conversation with/without permission, response, abort and exception reporting * All classes of structured dialogue operation (class 1: both success and failure are reported, class 2: Only failure is reported, class 3: Only success is reported and class 4: Neither success nor failure is reported) * Statistics information to determine traffic loads and quality-of-service * Point code/subsystem number and/or global title addressing capabilities while using SCCP transport services * Point code/subsystem states change indications while using SCCP transport services ### TelcoBridges and TCAP TCAP support is provided via the [Toolpack](https://telcobridges.com/products/development-platforms-tdev/) web portal. It is also available via the original Toolpack [API](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/api/README.md) as the [TCAP Control Library](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-control-library/README.md). ### Related actions **Refer to the appropriate Toolpack release:** * [SCCP and TCAP Configuration Version 3.0](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-3-0-protocol-stacks/README.md#sccp-tcap) * [SCCP and TCAP Configuration Version 2.10](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-2-10-protocol-stacks/README.md#sccp-tcap) * [SCCP and TCAP Configuration Version 2.9](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/web-portal-2-9-protocol-stacks/README.md#sccp-tcap) * [SCCP and TCAP Configuration Version 2.8](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/web-portal-2-8-protocol-stacks/README.md#sccp-tcap) ### References * [Wikipedia article](http://en.wikipedia.org/wiki/Transaction_Capabilities_Application_Part) * [Architecture](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-architecture/README.md) * [Specification](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-specification/README.md) * [Supported TCAP standards and variants](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-specification/README.md) * [TCAP Alarms](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-alarms/README.md) * [TCAP States](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-states/README.md) * [TCAP Statistics](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-statistics/README.md) * [Userpart statistics](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-userpart-statistics/README.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://prosbcdocs.telcobridges.com/telecom-references/protocols/tcap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.