Digit Analyzer - Revision history

Allyntree at 13:54, 14 September 2022

2022-09-14T13:54:27Z

← Older revision		Revision as of 09:54, 14 September 2022
Line 1:		Line 1:
			{{DISPLAYTITLE:Digit Analyzer}}
	The digit analyzer is a pre-routing algorithm. It uses a non-linear searching algorithm to find the optimal set of routes with which routing will take place. All routes not required for routing the destination telephone number are therefore screened out. This greatly enhance performances and allows to support virtually any number of routes, since routing is always done on a limited set of routes, matching the destination telephone number.		The digit analyzer is a pre-routing algorithm. It uses a non-linear searching algorithm to find the optimal set of routes with which routing will take place. All routes not required for routing the destination telephone number are therefore screened out. This greatly enhance performances and allows to support virtually any number of routes, since routing is always done on a limited set of routes, matching the destination telephone number.

Sylvain Fontaine: Replaced content with 'The digit analyzer is a pre-routing algorithm. It uses a non-linear searching algorithm to find the optimal set of routes with which routing will take place. All routes not r…'

2010-03-17T21:35:56Z

Replaced content with 'The digit analyzer is a pre-routing algorithm. It uses a non-linear searching algorithm to find the optimal set of routes with which routing will take place. All routes not r…'

Show changes

Cboulanger at 15:39, 8 January 2010

2010-01-08T15:39:36Z

← Older revision		Revision as of 11:39, 8 January 2010
Line 97:		Line 97:
	=== ''NapName''.csv ===		=== ''NapName''.csv ===

	There is ~~'''optionaly '''~~one ''NapName.csv'' for each [[NAP\|NAP]] configured in the system.  Each file, is a list of ''number<''->''routesetname'' association for the [[NAP\|NAP]].  <br>		There is one ''NapName.csv'' for each [[NAP\|NAP]] configured in the system.  Each file, is a list of ''number<''->''routesetname'' association for the [[NAP\|NAP]].  <br>

	*Its name must match the name of a configured [[NAP\|NAP]]<br>		*Its name must match the name of a configured [[NAP\|NAP]]<br>

Cboulanger at 15:38, 8 January 2010

2010-01-08T15:38:13Z

← Older revision		Revision as of 11:38, 8 January 2010
Line 97:		Line 97:
	=== ''NapName''.csv ===		=== ''NapName''.csv ===

	There's one ''NapName.csv'' for each [[NAP\|NAP]] configured in the system.  Each file, is a list of ''number<''->''routesetname'' association for the [[NAP\|NAP]].  <br>		There is '''optionaly '''one ''NapName.csv'' for each [[NAP\|NAP]] configured in the system.  Each file, is a list of ''number<''->''routesetname'' association for the [[NAP\|NAP]].  <br>

	*Its name must match the name of a configured [[NAP\|NAP]]<br>		*Its name must match the name of a configured [[NAP\|NAP]]<br>
	*Two mandatory columns: '''''number''''' and '''''route_set_name'''''<br>		*Two mandatory columns: '''''number''''' and '''''route_set_name'''''<br>
	*Supplementary columns are used to provide optional and custom values to dynamically created routes<br>		*Supplementary columns are used to provide optional and custom values to dynamically created routes<br>

	For example, here's NapSvcProviderA.csv<br>		For example, here's NapSvcProviderA.csv<br>
	<pre>number, route_set_name, remapped_called, custom_1		<pre>number, route_set_name, remapped_called, custom_1
	55521, "Montreal, Qc", "", ""		55521, "Montreal, Qc", "", ""
Line 109:		Line 109:
	55513, "Vancouver, Bc", "/(.*)/1\1/", 10		55513, "Vancouver, Bc", "/(.*)/1\1/", 10
	555131, "Toronto, On", "", ""		555131, "Toronto, On", "", ""
	</pre>		</pre>
	With very few lines, each file defines:		With very few lines, each file defines:

Line 116:		Line 116:
	#All RouteSet<->NAP associations		#All RouteSet<->NAP associations

	As we'll see later, for each RouteSet<->NAP association, a dynamic route entry gets created.  Moreover, in this example, the route gets created with parameters found in the second and third colum.<br>		As we'll see later, for each RouteSet<->NAP association, a dynamic route entry gets created.  Moreover, in this example, the route gets created with parameters found in the second and third colum.<br>

	=== Naps.csv ===		=== Naps.csv ===

Cboulanger at 15:37, 8 January 2010

2010-01-08T15:37:31Z

← Older revision		Revision as of 11:37, 8 January 2010
Line 85:		Line 85:
	This file is the list of all RouteSet names configured in the system.  <br>		This file is the list of all RouteSet names configured in the system.  <br>

	*It's name is <u>''route_sets.csv''</u>~~<br>~~Importing this file to the Toolpack is '''mandatory '''as it is used to validate the content of the other csv files before applying them.		*It's name is <u>''route_sets.csv''</u>
			*Importing this file to the Toolpack is '''mandatory '''as it is used to validate the content of the other csv files before applying them.
	*Only one column, named '''''route_set_name'''''		*Only one column, named '''''route_set_name'''''

Cboulanger at 15:36, 8 January 2010

2010-01-08T15:36:53Z

← Older revision		Revision as of 11:36, 8 January 2010
Line 85:		Line 85:
	This file is the list of all RouteSet names configured in the system.  <br>		This file is the list of all RouteSet names configured in the system.  <br>

	*It's name is <u>''route_sets.csv''</u><br>		*It's name is <u>''route_sets.csv''</u><br>Importing this file to the Toolpack is '''mandatory '''as it is used to validate the content of the other csv files before applying them.
	*Only one column, named '''''route_set_name'''''		*Only one column, named '''''route_set_name'''''

Cboulanger at 15:35, 8 January 2010

2010-01-08T15:35:15Z

← Older revision		Revision as of 11:35, 8 January 2010
Line 83:		Line 83:
	=== RouteSets.csv ===		=== RouteSets.csv ===

	This file is the list of all RouteSet names configured in the system.  <br>		This file is the list of all RouteSet names configured in the system.  <br>

	*It's name is <u>''route_sets.csv''</u><br>		*It's name is <u>''route_sets.csv''</u><br>
	*Only one column, named '''''route_set_name'''''		*Only one column, named '''''route_set_name'''''

	For example:<br>		For example:<br>
	<pre>route_set_name		<pre>route_set_name
	"Montreal, Qc"		"Montreal, Qc"
	"Toronto, On		"Toronto, On"
	</pre>		</pre>

	=== ''NapName''.csv ===		=== ''NapName''.csv ===

Sylvain Fontaine: /* CSV Database */

2010-01-08T15:26:23Z

CSV Database

← Older revision		Revision as of 11:26, 8 January 2010
Line 71:		Line 71:
	In other words, we have three routes grouped under a RouteSet named "Montreal, Qc".  In this case, the RouteSet is named after the destination city, but it could be anything.<br>		In other words, we have three routes grouped under a RouteSet named "Montreal, Qc".  In this case, the RouteSet is named after the destination city, but it could be anything.<br>

	== CSV Database <br> ==		== Routing CSV Database <br> ==

	The CSV database is composed of 4 groups of [http://en.wikipedia.org/wiki/Comma-separated_values CSV] files.  Those files covers configuration of all aspects required by the routing engine.  Files enables all route management, modification, backup and update to take place outside Toolpack webportal, using your favorite software.  Once the files are ready, the are imported in the Toolpack system using WebPortal.  The WebPortal also allows to export [http://en.wikipedia.org/wiki/Comma-separated_values CSV] files.<br>		The CSV database is composed of 4 groups of [http://en.wikipedia.org/wiki/Comma-separated_values CSV] files.  Those files covers configuration of all aspects required by the routing engine.  Files enables all route management, modification, backup and update to take place outside Toolpack webportal, using your favorite software.  Once the files are ready, the are imported in the Toolpack system using WebPortal.  The WebPortal also allows to export [http://en.wikipedia.org/wiki/Comma-separated_values CSV] files.<br>
Line 147:		Line 147:
	#One normal route, adding a special rule on the RouteSet named "Vancouver, Bc", forcing calls incoming NapSvcProviderC to always go out on NapSvcProviderB		#One normal route, adding a special rule on the RouteSet named "Vancouver, Bc", forcing calls incoming NapSvcProviderC to always go out on NapSvcProviderB

	A route is considered global if it does not belong to a RouteSet.  Global routes are always used along with the RouteSet during routing.		A route is considered global if it does not belong to a RouteSet.  Global routes are always used along with the RouteSet during routing.

	== Dynamic Route Tables ==		== Dynamic Route Tables ==

Sylvain Fontaine at 14:38, 8 January 2010

2010-01-08T14:38:29Z

← Older revision		Revision as of 10:38, 8 January 2010
Line 81:		Line 81:
	*File content IS case sensitive.<br>		*File content IS case sensitive.<br>

	=== RouteSets.csv ~~File~~ ===		=== RouteSets.csv ===

	This file is the list of all RouteSet names configured in the system.  <br>		This file is the list of all RouteSet names configured in the system.  <br>
Line 93:		Line 93:
	"Toronto, On		"Toronto, On
	</pre>		</pre>
	=== ''NapName''.csv ~~File~~ ===		=== ''NapName''.csv ===

	There's one ''NapName.csv'' for each [[NAP\|NAP]] configured in the system.  Each file, is a list of ''number<''->''routesetname'' association for the [[NAP\|NAP]].  <br>		There's one ''NapName.csv'' for each [[NAP\|NAP]] configured in the system.  Each file, is a list of ''number<''->''routesetname'' association for the [[NAP\|NAP]].  <br>
Line 116:		Line 116:
	As we'll see later, for each RouteSet<->NAP association, a dynamic route entry gets created.  Moreover, in this example, the route gets created with parameters found in the second and third colum.<br>		As we'll see later, for each RouteSet<->NAP association, a dynamic route entry gets created.  Moreover, in this example, the route gets created with parameters found in the second and third colum.<br>

	=== Naps.csv ~~File~~ ===		=== Naps.csv ===

	This file is optionnal, and defines parameters for each NAP configured in the system.<br>		This file is optionnal, and defines parameters for each NAP configured in the system.<br>
Line 132:		Line 132:
	=== Routes.csv<br> ===		=== Routes.csv<br> ===

	This file is optionnal, and defines static routes.  Static routes are those that were not dynamically created by the import of a [[Digit Analyzer#NapName.csv ~~File~~\|NapName.csv]] file.<br>		This file is optionnal, and defines static routes.  Static routes are those that were not dynamically created by the import of a [[Digit Analyzer#NapName.csv\|NapName.csv]] file.<br>

	*It's name is ''<u>routes.csv</u>''<br>		*It's name is ''<u>routes.csv</u>''<br>

Sylvain Fontaine at 14:37, 8 January 2010

2010-01-08T14:37:31Z

← Older revision		Revision as of 10:37, 8 January 2010
Line 132:		Line 132:
	=== Routes.csv<br> ===		=== Routes.csv<br> ===

	This file is optionnal, and defines static routes.  Static routes are those that were not dynamically created by the import of a [[Digit Analyzer#NapName.csv\|NapName.csv]] file.<br>		This file is optionnal, and defines static routes.  Static routes are those that were not dynamically created by the import of a [[Digit Analyzer#NapName.csv File\|NapName.csv]] file.<br>

	*It's name is ''<u>routes.csv</u>''<br>		*It's name is ''<u>routes.csv</u>''<br>