> 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/apis-and-integration/overview.md).

# Overview

This users’ guide is intended for the users of the TelcoBridges products. It explains the concepts behind the Toolpack modules (also referred to as ’Call and Media control’ \[aka CMC] and ’Custom Application Framework’ \[aka CAF] classes) and how they can be used to build large applications. Some telecommunications knowledge is expected from the reader as well as a basic understanding of the "C++" language.

The ToolPack API modules are intended to give a simpler, protocol agnostic and complete control API to the programmer.

They give access to system-level functionality and provide simpler system management and configuration.

Typically, an application only needs to interact with the system through the use of C++ classes as shown in the figure below:

**MISSING IMAGE**

Toolpack is comprised of a series of modules. They are:

* [CMC Library](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/cmc-library/README.md)
* [Toolpack Engine](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/toolpack-engine/README.md)
* [Toolpack System Manager](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/toolpack-sys-manager/README.md)
* [TCAP Control Library](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-control-library/README.md)

***

Return to the Toolpack [User Guide](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/user-guide/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/apis-and-integration/overview.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.