> 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.md). # Customer Application Framework (CAF) The Customer Application Framework (CAF) library comes in where the [CMC library](/telecom-references/developer-reference/caf/cmc-library.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](/telecom-references/developer-reference/caf/caf-working-with-call-legs.md) for details on how to work with call legs. ### References * Articles concerning CAF ## In this section * [API:Native:VpMgr:ToneDetection](/telecom-references/developer-reference/caf/api-native-vpmgr-tonedetection.md) * [Behaviors](/telecom-references/developer-reference/caf/behaviors.md) * [CAF Bridge class](/telecom-references/developer-reference/caf/caf-bridge-class.md) * [CAF Call interface](/telecom-references/developer-reference/caf/caf-call-interface.md) * [CAF: Caf Call Leg Actions](/telecom-references/developer-reference/caf/caf-caf-call-leg-actions.md) * [CAF: Caf Call Leg Events](/telecom-references/developer-reference/caf/caf-caf-call-leg-events.md) * [CAF: Caf Mixer Actions](/telecom-references/developer-reference/caf/caf-caf-mixer-actions.md) * [CAF: Caf Mixer Events](/telecom-references/developer-reference/caf/caf-caf-mixer-events.md) * [CAF: Call Legs Resync](/telecom-references/developer-reference/caf/caf-call-legs-resync.md) * [CAF: CTBCMCTimer](/telecom-references/developer-reference/caf/caf-ctbcmctimer.md) * [CAF: Filling SDP Structures](/telecom-references/developer-reference/caf/caf-filling-sdp-structures.md) * [CAF: Leg Creation Samples](/telecom-references/developer-reference/caf/caf-leg-creation-samples.md) * [CAF: Working With Caf Call Legs](/telecom-references/developer-reference/caf/caf-working-with-caf-call-legs.md) * [CAF: Working With Call Legs](/telecom-references/developer-reference/caf/caf-working-with-call-legs.md) * [CAF: Working With Cmc Call Legs](/telecom-references/developer-reference/caf/caf-working-with-cmc-call-legs.md) * [CAF: Working With Cmc Mixers](/telecom-references/developer-reference/caf/caf-working-with-cmc-mixers.md) * [Classes](/telecom-references/developer-reference/caf/classes.md) * [CMC Call Leg class](/telecom-references/developer-reference/caf/cmc-call-leg-class.md) * [CMC library](/telecom-references/developer-reference/caf/cmc-library.md) * [CTBCAFCli](/telecom-references/developer-reference/caf/ctbcafcli.md) * [CTBCAFComm](/telecom-references/developer-reference/caf/ctbcafcomm.md) * [CTBCAFDb](/telecom-references/developer-reference/caf/ctbcafdb.md) * [CTBCAFLog](/telecom-references/developer-reference/caf/ctbcaflog.md) * [CTBCAFServiceCmMgmtClient](/telecom-references/developer-reference/caf/ctbcafservicecmmgmtclient.md) * [Customer application framework:play audio files](/telecom-references/developer-reference/caf/customer-application-framework-play-audio-files.md) * [Interfaces](/telecom-references/developer-reference/caf/interfaces.md) * [Overview](/telecom-references/developer-reference/caf/overview.md) * [Services](/telecom-references/developer-reference/caf/services.md) * [Telephony Application](/telecom-references/developer-reference/caf/telephony-application.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 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.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.