> 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/tmedia-documentation/other-pages/other/creating-new-transaction.md).

# Creating new transaction

The **transaction initiation** (request/response) message is used to create and initialize a new TCAP transaction. The new transaction instance stays active until the transaction and dialogue portions are sent.

Each transaction must be uniquely identified. The transaction identifier of an outgoing transaction is determined by the TCAP service user and must be within the range 0x80000000 to 0xFFFFFFFF. The transaction identifier of an incoming transaction is determined by the TCAP layer and will always be within the range 0x00000001 to 0x7FFFFFFF.

To complete the TCAP message, components and parameters must be individually added using the transaction component add message. Message type, called and calling addresses, quality of service, dialogue and user information, etc., must be initialized using the **transaction component send** message. The TCAP message assembly and transmission to the SCCP layer occurs only when the TCAP layer receives the **transaction component send** message.


---

# 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/tmedia-documentation/other-pages/other/creating-new-transaction.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.