> 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/developer-reference/caf/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](/telecom-references/developer-reference/caf/cmc-library.md) * [Toolpack Engine](/telecom-references/developer-reference/toolpack-api/toolpack-engine.md) * [Toolpack System Manager](/telecom-references/developer-reference/toolpack-api/toolpack-sys-manager.md) * [TCAP Control Library](/telecom-references/ss7-and-signalling/tcap/tcap-control-library.md) *** Return to the Toolpack [User Guide](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/getting-around-the-portal/user-guide) --- # 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/developer-reference/caf/overview.md?ask=&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.