Toolpack API
From TBwiki
(Difference between revisions)
(initial content) |
(added components) |
||
| Line 6: | Line 6: | ||
Typically, an application only needs to interact with the system through the use of C++ classes indi | Typically, an application only needs to interact with the system through the use of C++ classes indi | ||
| + | |||
| + | |||
| + | == Toolpack API components == | ||
| + | |||
| + | Toolpack API is comprised of the following elements: | ||
| + | *[[CMC Library]] | ||
| + | *[[Toolpack Engine]] | ||
| + | *[[Toolpack System Manager]] | ||
| + | *[[TCAP Control Library]] | ||
Revision as of 14:11, 8 July 2009
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 above 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 Tmedia TMG3200 (flash disk or SATA drive) or the TMG800 (flash disk).
Typically, an application only needs to interact with the system through the use of C++ classes indi
Toolpack API components
Toolpack API is comprised of the following elements:
