Overview
m (fix link) |
|||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 11: | Line 11: | ||
below: | below: | ||
| − | MISSING IMAGE | + | '''MISSING IMAGE''' |
Toolpack is comprised of a series of modules. They are: | Toolpack is comprised of a series of modules. They are: | ||
*[[CMC library|CMC Library]] | *[[CMC library|CMC Library]] | ||
| − | *[[ | + | *[[Toolpack_Application:toolpack_engine|Toolpack Engine]] |
| − | *[[ | + | *[[Toolpack_Application:toolpack_sys_manager|Toolpack System Manager]] |
*[[TCAP Control Library]] | *[[TCAP Control Library]] | ||
| + | |||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | Return to the Toolpack [[User Guide]] | ||
Latest revision as of 15:43, 15 February 2011
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:
Return to the Toolpack User Guide
