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

# Transaction

The [TCAP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap/README.md) service user has to send TCAP messages by fragments. All [components](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/message/README.md#component-portion) of a TCAP message must be sent individually. They are queued until TCAP receives the [transaction](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/message/README.md#transaction-portion) and [dialogue](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/message/README.md#dialogue-portion) portions. TCAP messages are then sent to peer TCAP/service user upon message assembly completion.

**Note:** No TCAP message is sent on the [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) network (no transaction occurs) until a **transaction data send** message is sent by the TCAP service user then received by the TCAP layer.

To [create a new TCAP transaction](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/creating-new-transaction/README.md), send the **initiate** message to register a new transaction identifier. When building TCAP messages, the transaction identifier serves to link the different fragments of a TCAP message (i.e. while adding components to TCAP message). It is not required to send the initiate message for already active outgoing and incoming transactions.

An **active outgoing transaction** is a transaction that has been created locally and hasn’t been terminated. An **active incoming transaction** is a transaction that has been created remotely by peer TCAP/service user and hasn’t been terminated.

* To [add components](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/adding-component-portion/README.md) to a previously created TCAP message, use the Transaction Component Add message.
* To [add transaction and dialogue portions](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sending-transaction-and-dialogue-portions/README.md) and activate TCAP message assembling and transmission, use the transaction data send message.

The peer application will receive a **transaction data received** message then one or more **transaction component received** messages. The **data received indication** contains transaction and dialogue portions of TCAP message. The **component received indication** contains the component portion of a TCAP message. The peer TCAP/service user will receive a **component received indication** for all components that are part of a TCAP message. The TCAP service user has to match the components and the transaction and dialogue portions using the transaction identifier.

### Related actions

* [Create a new transaction](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/creating-new-transaction/README.md)
* [Add a component portion](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/adding-component-portion/README.md)
* [Send transaction and dialogue portions](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sending-transaction-and-dialogue-portions/README.md)
* [Receive component portion](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/receiving-component-portion/README.md)
* [Receive transaction and dialogue portions](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/receiving-transaction-and-dialogue-portions/README.md)
* [Receive transaction error indications](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/receiving-transaction-error-indication/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/transaction.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.