> 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/customer-application-framework.md).

# Customer Application Framework

The Customer Application Framework (CAF) library comes in where the [CMC library](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/cmc-library/README.md) left off. The main purpose is to provide a set of optional C++ classes that may be used to easily implement gateway applications. The CAF classes build on CMC legs and provide easier management of calls, CLI, memory, logger, database, etc. CMC samples and applications are built on this framework since the code is easier to understand and the development time is shortened.

### The optional nature of CAF

Clients should not need to integrate in a really big framework just to use one of the framework's helper classes. This is why each individual element of the framework is designed to be optional and independent. For example it is not mandatory to use a routing class to create a call class.

### The customization of CAF

Of course the framework will not address all of the clients needs perfectly. This is why most of the classes may be subclassed or re-implemented to provide a better fit and still be used in the rest of the framework. For example the data access object for a client account may be reimplemented to query a non supported database. This DAO could then be used in the gateway application with minor modifications.

Refer to [Working\_With\_Call\_Legs](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/caf-working-with-call-legs/README.md) for details on how to work with call legs.

### References

* Articles concerning CAF


---

# 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/customer-application-framework.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.