> 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/telecom-concepts/develop-using-toolpack.md).

# Develop Using Toolpack

[Toolpack](https://telcobridges.com/products/development-platforms-tdev/) is an application development platform that enables developer to create a wide range of [Value-added services](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/value-added-services/README.md) such as [Call routing](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/call-routing/README.md), [prepaid & postpaid](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/prepaid-and-postpaid/README.md), [Ringback tones](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/voice-media/ringback-tones/README.md), etc. The  default Toolpack user application is the [gateway application](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/gateway/README.md) which route incoming calls according to [naps](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/nap/README.md), calling number and called number to a destination. It is possible for solution developers to modify default behaviors of the gateway application, or create a new application entirely.

### Toolpack Developers

For all Toolpack developers, learning how to use the caf classes, call legs and call flows are very important.

#### CAF classes

[CAF classes](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/customer-application-framework/README.md) are modules of the [Toolpack API](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/toolpack-api/README.md) that facilitate application development.

#### Call Legs

[Call legs](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/call-leg/README.md) are a full-duplex media resource and/or its associated signaling entity.

To learn more about call legs, see the '[==>working with call legs<==](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/caf-working-with-call-legs/README.md)' article.

#### Call Flows

[Call flows](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/voice-media/call-flow/README.md) are call scenarios that shows the interaction between the [CAF classes](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/customer-application-framework/README.md) and the protocol specific messages.

To learn more about coding with call flows, see the '[==>working with call legs<==](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/caf-working-with-call-legs/README.md)' article.

#### Status API

[Status\_API](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/status-api/README.md) allows querying and modifying all states provided by Toolpack system (trunk states, clock status, adapter states, application states, ISUP interface or circuit states, etc.)

#### [Toolpack API](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/toolpack-api/README.md) documentation

Description and documentation of all APIs are available in the **tb-doc.zip** package of each software release (see <[http://forums.telcobridges.com/viewforum.php?f=23>(http://forums.telcobridges.com/viewforum.php?f=23)](http://forums.telcobridges.com/viewforum.php?f=23>\(http://forums.telcobridges.com/viewforum.php?f=23\)) for available software releases). Once unzipped, please check folder **tb\doc\toolpack\html\index.html**


---

# 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/telecom-concepts/develop-using-toolpack.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.