Actions

Develop Using Toolpack: Difference between revisions

m (add category)
(Added Toolpack API link to documentation)
Line 3: Line 3:
<br>  
<br>  


== Toolpack Developers<br> ==
== Toolpack Developers<br> ==


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


=== CAF classes  ===
=== CAF classes  ===


[[Customer Application Framework|CAF classes]] are modules of the [[Toolpack API|Toolpack API]] that facilitate application development.  
[[Customer Application Framework|CAF classes]] are modules of the [[Toolpack API|Toolpack API]] that facilitate application development.<br>  
 
<br>  


=== Call Legs  ===
=== Call Legs  ===


[[Call Leg|Call legs]] are a full-duplex media resource and/or its associated signaling entity. To learn more about call legs, see the '[[CAF: Working With Call Legs|working with call legs]]' article.  
[[Call Leg|Call legs]] are a full-duplex media resource and/or its associated signaling entity. To learn more about call legs, see the '[[CAF: Working With Call Legs|working with call legs]]' article.<br>


=== Call Flows  ===


[[Call Flow|Call flows]] are call scenarios that shows the interaction between the [[Customer Application Framework|CAF&nbsp;classes]] and the protocol specific messages.


=== Call Flows ===
=== Status API ===


[[Call Flow|Call flows]] are call scenarios that shows the interaction between the [[Customer Application Framework|CAF&nbsp;classes]] and the protocol specific messages.
[[Status API|Status_API]] allows querying and modifying all states provided by Toolpack system (trunk states, clock status, adapter states, application states, ISUP interface or circuit states, etc.)


=== Status API  ===
=== [[Toolpack API|Toolpack API]] documentation<br> ===


[[Status API|Status_API]] allows querying and modifying all states provided by Toolpack system (trunk states, clock status, adapter states, application states, ISUP interface or circuit states, etc.)
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] for available software releases). Once unzipped, please check folder tb\doc\toolpack\html\index.html<br>


[[Category:Tdev_OAM%26P|Develop]]
[[Category:Tdev_OAM&P|Develop]]

Revision as of 10:43, 14 November 2011

Toolpack is an application development platform that enables developer to create a wide range of Value-added services such as Call routing, prepaid & postpaid, Ringback tones, etc. The  default Toolpack user application is the gateway application which route incoming calls according to naps, 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 are modules of the Toolpack API that facilitate application development.

Call Legs

Call legs are a full-duplex media resource and/or its associated signaling entity. To learn more about call legs, see the 'working with call legs' article.

Call Flows

Call flows are call scenarios that shows the interaction between the CAF classes and the protocol specific messages.

Status API

Status_API 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 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 for available software releases). Once unzipped, please check folder tb\doc\toolpack\html\index.html