Toolpack API
From TBwiki
(Difference between revisions)
m (fix link) |
m (fix link) |
||
| Line 16: | Line 16: | ||
*[[Customer Application Framework|Customer Application Framework (CAF)]] | *[[Customer Application Framework|Customer Application Framework (CAF)]] | ||
*[[CMC library|CMC Library]] | *[[CMC library|CMC Library]] | ||
| − | *[[Toolpack Engine]] | + | *[[Toolpack_Application:toolpack_engine|Toolpack Engine]] |
*[[Toolpack_Application:toolpack_sys_manager|Toolpack System Manager]] | *[[Toolpack_Application:toolpack_sys_manager|Toolpack System Manager]] | ||
*[[TCAP Control Library]] | *[[TCAP Control Library]] | ||
Revision as of 15:43, 15 February 2011
The ToolPack API modules are intended to provide the solution developer with a simpler, protocol-agnostic approach to developing telephony applications while providing complete control, including access to system-level functionality.
The graphic below demonstrates Toolpack and a customer developed application running on an external application server such as one would use with the Tdev TMP6400 or the Tdev TMP800. It is also possible to host the application server locally in the Tdev TMP5900 or the Tdev TMP7900.
Typically, an application only needs to interact with the system through the use of C++ classes indicated above via dashed borders.
Toolpack API components
Toolpack API is comprised of the following elements:
