Develop Using Toolpack - Revision history

Abrassard: Putting emphasis on the "Working with call legs" link, as most of the doc is there

2012-01-25T18:23:52Z

Putting emphasis on the "Working with call legs" link, as most of the doc is there

Luc Morissette: Bold

2011-11-14T14:46:30Z

Bold

Luc Morissette: Added Toolpack API link to documentation

2011-11-14T14:43:10Z

Added Toolpack API link to documentation

Cbilodeau: add category

2011-02-14T19:59:59Z

add category

Abrassard: /* Call Flows */

2010-05-06T16:26:11Z

Call Flows

Cbilodeau: improve description

2010-03-03T14:26:18Z

improve description

Ktrueman: modified some links and cleaned up

2010-03-01T13:40:15Z

modified some links and cleaned up

Cbilodeau: creation

2010-02-12T13:51:26Z

creation

New page

[[Toolpack]] is a flexible platform that allows its developer to create a wide range of applications ([[Call routing|call routing]], [[Prepaid & postpaid|prepaid & postpaid]], [[Ringback tones|ringback tones]], etc).

== The CAF classes ==

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

<br>

== Call Legs<br> ==

[[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 classes]] and the protocol specific messages.

@@ Line 13: / Line 13: @@
 === 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.<br>
+[[Call Leg|Call legs]] are a full-duplex media resource and/or its associated signaling entity.
 === 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.
 === Status API  ===

@@ Line 25: / Line 25: @@
 === [[Toolpack API|Toolpack API]] documentation<br>  ===
-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>
+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&P|Develop]]

@@ Line 3: / Line 3: @@
 <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>
 === 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 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  ===
+=== 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]]

← Older revision		Revision as of 19:59, 14 February 2011
Line 26:		Line 26:

	[[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\|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.)
		+
		+	[[Category:Tdev_OAM%26P\|Develop]]

← Older revision		Revision as of 16:26, 6 May 2010
Line 22:		Line 22:

	[[Call Flow\|Call flows]] are call scenarios that shows the interaction between the [[Customer Application Framework\|CAF classes]] and the protocol specific messages.		[[Call Flow\|Call flows]] are call scenarios that shows the interaction between the [[Customer Application Framework\|CAF classes]] and the protocol specific messages.
		+
		+	=== Status API ===
		+
		+	[[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.)

← Older revision		Revision as of 13:40, 1 March 2010
Line 1:		Line 1:
−	[[Toolpack]] is ~~a flexible~~ platform that ~~allows its~~ developer to create a wide range of ~~applications (~~[[~~Call routing\|~~call routing]], [[Prepaid & postpaid\|prepaid & postpaid]], [[~~Ringback tones\|~~ringback tones]], etc).	+	[[Toolpack]] is an application development platform that enables developer to create a wide range of [[value-added services]] such as [[call routing]], [[Prepaid & postpaid\|prepaid & postpaid]], [[ringback tones]], etc. Toolpack is comprised of the following:

−	~~== The CAF classes ==~~

−	~~The ~~[[Customer Application Framework\|CAF classes]] are modules of the [[Toolpack API\|Toolpack API]] that facilitate application development.~~<br>~~	+	== CAF classes ==
		+	[[Customer Application Framework\|CAF classes]] are modules of the [[Toolpack API\|Toolpack API]] that facilitate application development.

−	~~<br>~~
−
−	~~== Call Legs<br> ==~~
−
−	[[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 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.