> 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/ss7-and-signalling/tcap/receiving-transaction-error-indication.md).

# Receiving transaction error indication

The **transaction error indication** (event) message is used by TCAP to notify the TCAP service user of undelivered TCAP messages as well as the cause(s). This message is passed to the TCAP service user when TCAP receives a status indication from its lower layer. The **cause of status indication** from the lower layer is passed transparently to the TCAP service user. The lower layer uses the status indication message to indicate to TCAP the lower layer's inability to fulfill TCAP's transaction request (which is due to any protocol error or network error).

The transaction error contains the following parameters:

* TCAP userpart handle
* TCAP transaction identifier
* Calling address
* Called address
* ISNI parameters
* Message importance indicator
* Return cause indicator


---

# 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://prosbcdocs.telcobridges.com/telecom-references/ss7-and-signalling/tcap/receiving-transaction-error-indication.md?ask=<question>&goal=<user_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.