> 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/receiving-transaction-and-dialogue-portions.md).

# Receiving transaction and dialogue portions

The **transaction data received** (event) message is used by [TCAP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap/README.md) to notify and send received transaction and dialogue portions to the TCAP service user. The transaction identifier of a received transaction remains valid until:

* TCAP receives a message among these types and the last component of the TCAP message:
  * End
  * Response
  * User abort
  * Provider abort
  * ANSI user abort
  * ANSI provider abort
* TCAP service user sends TCAP message with one of the following message types:
  * End
  * Response
  * User abort
  * ANSI user abort

If TCAP detects that the received message is incorrect, it sends an abort indication to the TCAP service user. The message type is set to **provider abort** in the case of ITU, and **ANSI provider abort** in the case of ANSI92 and 96. In the case of ANSI88, the TCAP service user is informed by sending the local reject indication using the **component received** message. The **abort cause** parameter is used to indicate the cause of abort.

The **transaction portion** contains the following parameters:

* TCAP userpart handle
* TCAP transaction identifier
* Message type identifier
* Component present indicator
* Calling address
* Called address
* Quality of service parameters
* ISNI parameters
* Abort cause indicator

The **dialogue portion** contains the following parameters:

* Dialogue parameters
* User information buffer


---

# 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/receiving-transaction-and-dialogue-portions.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.