> 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-specification.md).

# TCAP Specification

TelcoBridges' implementation of TCAP conforms to the following standards:

* ETS 300 287-1 Transaction Capabilities, Version 2, ETSI 1996
* JT Q.771 Functional Description of Transaction Capabilities, TTC (Japan)
* JT Q.772 Transaction Capabilities Information Element Definitions, TTC (Japan)
* JT Q.773 Transaction Capabilities Formats and Encoding, TTC (Japan)
* JT Q.774 Transaction Capabilities Procedures, TTC (Japan)
* Q.752 Monitoring and Measurements of Signalling System No. 7 Networks, 1993
* Q.771 Functional Description of Transaction Capabilities, ITU (88, 92, and 96)
* Q.772 Transaction Capabilities Information Element Definitions, ITU (88, 92, and 96)
* Q.773 Transaction Capabilities Formats and Encoding, ITU (88, 92, and 96)
* Q.774 Transaction Capabilities Procedures, ITU (88, 92, and 96)
* Q.775 Guidelines for Using Transaction Capabilities, ITU (88, 92, and 96)
* Q.787 Transaction Capabilities (TC) Test Specification, 1993
* T1.114, Signalling System Number 7 - Transaction Capability Application Part (TCAP), ANSI (88, 92, and 96)

TCAP can support the following different protocol variants:

* ITU (used for ITU88, ITU92, and ITU96)
* ANSI (used for ANSI88, ANSI92, and ANSI96)
* ETSI 1996 (ETS 300 287-1)


---

# 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-specification.md?ask=<question>&goal=<endgoal>
```

`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.