Scriptable Routing Engine - Revision history

Luc Morissette: Updated link to Routing scripts

2019-08-21T15:45:48Z

Updated link to Routing scripts

← Older revision		Revision as of 11:45, 21 August 2019
Line 43:		Line 43:

	TelcoBridges provide a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps.		TelcoBridges provide a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps.
			*[[Toolpack:Call_Routes_Settings_D\|Configuring routing script]]
			<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
	*[[Web_Portal_Tutorial_Guide_v2.7#Routing_Script\|Configuring routing script for v2.7]]		*[[Web_Portal_Tutorial_Guide_v2.7#Routing_Script\|Configuring routing script for v2.7]]
	*[[Web_Portal_Tutorial_Guide_v2.6#Configuring_Routing_script\|Configuring routing script for v2.6]]		*[[Web_Portal_Tutorial_Guide_v2.6#Configuring_Routing_script\|Configuring routing script for v2.6]]
	*[[Web_Portal_Tutorial_Guide_v2.5#Configuring_Routing_script\|Configuring routing script for v2.5]]		*[[Web_Portal_Tutorial_Guide_v2.5#Configuring_Routing_script\|Configuring routing script for v2.5]]
			</div>

	== Tutorial guide ==		== Tutorial guide ==

Allyntree: Needs revising edit

2018-04-19T12:37:12Z

Needs revising edit

← Older revision		Revision as of 08:37, 19 April 2018
Line 1:		Line 1:
	[[Toolpack]] [[Version 2.3\|v2.3]] introduces a scriptable routing engine that complements the existing approach to building [[Call routing\|call routes]]. This new approach is based on the [http://www.ruby-lang.org/en/ Ruby] programming language, which offers a high-level, natural language-like approach to programming known as [http://en.wikipedia.org/wiki/Scripting_language scripting]. With Ruby, no code compilation is required to use routing scripts; in fact, you write scripts within your web browser. A high-level overview of how to write scripts is available upon request by contacting the TelcoBridges [mailto:support@telcobridges.com support team].		[[Toolpack]] [[Version 2.3\|v2.3]] introduces a scriptable routing engine that complements the existing approach to building [[Call routing\|call routes]]. This new approach is based on the [http://www.ruby-lang.org/en/ Ruby] programming language, which offers a high-level, natural language-like approach to programming known as [http://en.wikipedia.org/wiki/Scripting_language scripting]. With Ruby, no code compilation is required to use routing scripts; in fact, you write scripts within your web browser. A high-level overview of how to write scripts is available upon request by contacting the TelcoBridges [mailto:support@telcobridges.com support team].

	As part of the initial release, TelcoBridges is providing a number of ready-to-use scripts such as percentage routing, round-robin routing, least-cost routing, [[SIP trunking]], PRI reselling with over-subscription, ~~etc~~.~~, with additional~~ scripts to be made available as we go forward. This new approach is meant to supplement the current approach to building routes. It should also make it possible for your service provider customers, once properly trained by you, to modify routing tables on their own.		As part of the initial release, TelcoBridges is providing a number of ready-to-use scripts such as percentage routing, round-robin routing, least-cost routing, [[SIP trunking]], PRI reselling with over-subscription, and others. Additional scripts will be made available as we go forward. This new approach is meant to supplement the current approach to building routes. It should also make it possible for your service provider customers, once properly trained by you, to modify routing tables on their own.

	<br>		<br>
Line 15:		Line 15:
	== Routing Scripts overview ==		== Routing Scripts overview ==

	The Scriptable Routing Engine ~~is asked~~, for every incoming call leg, ~~to take~~ a routing decision ~~which indicates~~ how the outgoing call leg ~~must~~ be created. The script will match one or multiple routes based on information from the incoming call leg		The Scriptable Routing Engine, for every incoming call leg, takes a routing decision thatindicates how the outgoing call leg will be created. The script will match one or multiple routes based on information from the incoming call leg

	*calling number		*calling number
Line 38:		Line 38:
	*etc.		*etc.

	An outgoing call ~~will be~~ made based on the first matching route. If this call fails with that route (maximum capacity reached, network or protocol error), another outgoing call attempt ~~will be~~ made using the next matching route. Note: This [[Route retry]] feature is available only in Toolpack version 2.5 and up.		An outgoing call is made based on the first matching route. If this call fails with that route (maximum capacity reached, network or protocol error), another outgoing call attempt is made using the next matching route. Note: This [[Route retry]] feature is available only in Toolpack version 2.5 and up.

	== Routing script Examples ==		== Routing script Examples ==
Line 94:		Line 94:
	*[[Tmedia_Routing\|Tmedia Routing]]		*[[Tmedia_Routing\|Tmedia Routing]]
	*[[Routing script tutorial]]		*[[Routing script tutorial]]

	~~[[Category:Needs revising‏‎]]~~

Luc Morissette: Added link to Tmedia routing

2014-01-31T14:26:49Z

Added link to Tmedia routing

← Older revision		Revision as of 10:26, 31 January 2014
Line 91:		Line 91:
	<br>		<br>

	== ~~References~~ ==		== Useful links ==
			*[[Tmedia_Routing\|Tmedia Routing]]
	*[[Routing script tutorial]]		*[[Routing script tutorial]]

	[[Category:Needs revising‏‎]]		[[Category:Needs revising‏‎]]

Luc Morissette: /* Routing script pool */

2014-01-29T16:20:44Z

Routing script pool

← Older revision		Revision as of 12:20, 29 January 2014
Line 40:		Line 40:
	An outgoing call will be made based on the first matching route. If this call fails with that route (maximum capacity reached, network or protocol error), another outgoing call attempt will be made using the next matching route. Note: This [[Route retry]] feature is available only in Toolpack version 2.5 and up.		An outgoing call will be made based on the first matching route. If this call fails with that route (maximum capacity reached, network or protocol error), another outgoing call attempt will be made using the next matching route. Note: This [[Route retry]] feature is available only in Toolpack version 2.5 and up.

	== Routing script ~~pool~~ ==		== Routing script Examples ==

	TelcoBridges provide a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps.		TelcoBridges provide a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps.

Luc Morissette: /* Mini development guide */

2014-01-29T16:19:50Z

Mini development guide

← Older revision		Revision as of 12:19, 29 January 2014
Line 55:		Line 55:
	== Mini development guide ==		== Mini development guide ==

	To learn about the parameters available in for each object go read the [[Routing script tutorial:Mini Development Guide\|Script ~~Routing~~ Mini Development Guide]].		To learn about the parameters available in for each object go read the [[Routing script tutorial:Mini Development Guide\|Routing Script Mini Development Guide]].

	<br>		<br>

	== Testing this feature ==		== Testing this feature ==

Luc Morissette: /* Tutorial guide */

2014-01-29T16:19:38Z

Tutorial guide

← Older revision		Revision as of 12:19, 29 January 2014
Line 49:		Line 49:
	== Tutorial guide ==		== Tutorial guide ==

	To learn how to use the Scriptable Routing Engine, click the following link to go to the [[Routing script tutorial\|Script ~~Routing~~ Tutorial]].		To learn how to use the Scriptable Routing Engine, click the following link to go to the [[Routing script tutorial\|Routing Script Tutorial]].

	<br>		<br>

	== Mini development guide ==		== Mini development guide ==

Luc Morissette: Added link to Script Parameters

2014-01-29T16:19:03Z

Added link to Script Parameters

← Older revision		Revision as of 12:19, 29 January 2014
Line 13:		Line 13:
	<br>		<br>

	== ~~Script routing~~ overview ==		== Routing Scripts overview ==

	The Scriptable Routing Engine is asked, for every incoming call leg, to take a routing decision which indicates how the outgoing call leg must be created. The script will match one or multiple routes based on information from the incoming call leg		The Scriptable Routing Engine is asked, for every incoming call leg, to take a routing decision which indicates how the outgoing call leg must be created. The script will match one or multiple routes based on information from the incoming call leg
Line 19:		Line 19:
	*calling number		*calling number
	*called number		*called number
	*NAP		*NAP (Networks Access Point)
			*Other incoming parameters as described here: [[Routing_script_tutorial:Mini_Development_Guide#Script_parameters_protocol_mapping\|Script parameters]]

	Each route determines NAP to use to make outgoing call, and may modify some of the call parameters:		Each route determines NAP to use to make outgoing call, and may modify some of the call parameters:
Line 37:		Line 38:
	*etc.		*etc.

	An outgoing call will be made based on the first matching route. If this call fails with that route (maximum capacity reached, network or protocol error), another outgoing call attempt will be made using the next matching route. Note: This [[Route retry]] feature is available only in Toolpack version 2.5 and up.		An outgoing call will be made based on the first matching route. If this call fails with that route (maximum capacity reached, network or protocol error), another outgoing call attempt will be made using the next matching route. Note: This [[Route retry]] feature is available only in Toolpack version 2.5 and up.

	== Routing script pool ==		== Routing script pool ==

Luc Morissette: /* Routing script pool */

2014-01-29T16:15:32Z

Routing script pool

← Older revision		Revision as of 12:15, 29 January 2014
Line 42:		Line 42:

	TelcoBridges provide a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps.		TelcoBridges provide a wide variety of routing script examples which customers can apply directly in their web configuration according to their needs by following just a few simple steps.
			*[[Web_Portal_Tutorial_Guide_v2.7#Routing_Script\|Configuring routing script for v2.7]]
			*[[Web_Portal_Tutorial_Guide_v2.6#Configuring_Routing_script\|Configuring routing script for v2.6]]
	*[[Web_Portal_Tutorial_Guide_v2.5#Configuring_Routing_script\|Configuring routing script for v2.5]]		*[[Web_Portal_Tutorial_Guide_v2.5#Configuring_Routing_script\|Configuring routing script for v2.5]]
	*[[Web_Portal_Tutorial_Guide_v2.6#Configuring_Routing_script\|Configuring routing script for v2.6]]

	== Tutorial guide ==		== Tutorial guide ==

Abrassard at 15:30, 21 August 2013

2013-08-21T15:30:19Z

@@ Line 68: / Line 68: @@
 The following are known limitations with the Scriptable Routing Engine as of version 2.5:
-*Scripts (including script sub-components provided by TelcoBridges) are not modified when Toolpack is upgraded to new version (for example, to the release version of v2.3.0, v2.3.1, etc.). This means that if there is an update of the basic script, you will need to manually update any existing scripts:
+*Scripts (including script sub-components provided by TelcoBridges) are not modified when Toolpack is upgraded to new version (for example, to the release version of v2.3.0, v2.3.1, etc.). This means that if there is an update of the basic script, you will need to manually update any existing scripts.
-** Re-create a new set of default routing script:
+**See [[#Updating_routing_scripts|Updating routing scripts]] below for instructions.
-*** Click "Routing scripts" tab on the left menu of the web portal
 *If you are using dynamic fields (using the '''Creating New Route Column '''or the '''Create New Nap Column''' option) with routing scripts and you plan to use NAP names, those NAP names need to be '''''all capital''''' letters (i.e.: not just the first letter needs to be capitalized.)
 <br>

Abrassard: Added short steps to update routing scripts

2013-08-21T15:28:02Z

Added short steps to update routing scripts

@@ Line 68: / Line 68: @@
 The following are known limitations with the Scriptable Routing Engine as of version 2.5:
-*Scripts (including script sub-components provided by TelcoBridges) are not modified when Toolpack is upgraded to new version (for example, to the release version of v2.3.0, v2.3.1, etc.). This means that if there is an update of the basic script, you will need to manually update any existing scripts.
+*Scripts (including script sub-components provided by TelcoBridges) are not modified when Toolpack is upgraded to new version (for example, to the release version of v2.3.0, v2.3.1, etc.). This means that if there is an update of the basic script, you will need to manually update any existing scripts:
 *If you are using dynamic fields (using the '''Creating New Route Column '''or the '''Create New Nap Column''' option) with routing scripts and you plan to use NAP names, those NAP names need to be '''''all capital''''' letters (i.e.: not just the first letter needs to be capitalized.)