Digit Analyzer - Revision history

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

Cboulanger at 15:38, 8 January 2010

2010-01-08T15:38:13Z

Cboulanger at 15:37, 8 January 2010

2010-01-08T15:37:31Z

Cboulanger at 15:36, 8 January 2010

2010-01-08T15:36:53Z

Cboulanger at 15:35, 8 January 2010

2010-01-08T15:35:15Z

Sylvain Fontaine: /* CSV Database */

2010-01-08T15:26:23Z

CSV Database

Sylvain Fontaine at 14:38, 8 January 2010

2010-01-08T14:38:29Z

Sylvain Fontaine at 14:37, 8 January 2010

2010-01-08T14:37:31Z

Sylvain Fontaine at 14:36, 8 January 2010

2010-01-08T14:36:51Z

@@ Line 97: / Line 97: @@
 === ''NapName''.csv  ===
-There is '''optionaly '''one ''NapName.csv'' for each [[NAP|NAP]] configured in the system.&nbsp; Each file, is a list of ''number&lt;''-&gt;''routesetname'' association for the [[NAP|NAP]].&nbsp; <br>
+There is one ''NapName.csv'' for each [[NAP|NAP]] configured in the system.&nbsp; Each file, is a list of ''number&lt;''-&gt;''routesetname'' association for the [[NAP|NAP]].&nbsp; <br>
 *Its name must match the name of a configured [[NAP|NAP]]<br>

@@ Line 97: / Line 97: @@
 === ''NapName''.csv  ===
-There's one ''NapName.csv'' for each [[NAP|NAP]] configured in the system.&nbsp; Each file, is a list of ''number&lt;''-&gt;''routesetname'' association for the [[NAP|NAP]].&nbsp; <br>
+There is '''optionaly '''one ''NapName.csv'' for each [[NAP|NAP]] configured in the system.&nbsp; Each file, is a list of ''number&lt;''-&gt;''routesetname'' association for the [[NAP|NAP]].&nbsp; <br>
 *Its name must match the name of a configured [[NAP|NAP]]<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>
 For example, here's NapSvcProviderA.csv<br>
 <pre>number, route_set_name,  remapped_called, custom_1
 ,  "Montreal, Qc",  "",              ""
@@ Line 109: / Line 109: @@
 ,  "Vancouver, Bc", "/(.*)/1\1/",    10
 , "Toronto, On",   "",              ""
 </pre>
 With very few lines, each file defines:
@@ Line 116: / Line 116: @@
 #All RouteSet&lt;-&gt;NAP associations
 As we'll see later, for each RouteSet&lt;-&gt;NAP association, a dynamic route entry gets created.&nbsp; Moreover, in this example, the route gets created with parameters found in the second and third colum.<br>
 === Naps.csv  ===

@@ Line 85: / Line 85: @@
 This file is the list of all RouteSet names configured in the system.&nbsp; <br>
-*It's name is <u>''route_sets.csv''</u><br>Importing this file to the Toolpack is '''mandatory&nbsp;'''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>
 *Only one column, named '''''route_set_name'''''

@@ Line 85: / Line 85: @@
 This file is the list of all RouteSet names configured in the system.&nbsp; <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&nbsp;'''as it is used to validate the content of the other csv files before applying them.
 *Only one column, named '''''route_set_name'''''

@@ Line 83: / Line 83: @@
 === RouteSets.csv  ===
 This file is the list of all RouteSet names configured in the system.&nbsp; <br>
 *It's name is <u>''route_sets.csv''</u><br>
 *Only one column, named '''''route_set_name'''''
 For example:<br>
 <pre>route_set_name
 "Montreal, Qc"
-"Toronto, On
+"Toronto, On"
 </pre>
 === ''NapName''.csv  ===

@@ Line 71: / Line 71: @@
 In other words, we have three routes grouped under a RouteSet named "Montreal, Qc".&nbsp; In this case, the RouteSet is named after the destination city, but it could be anything.<br>
-== CSV&nbsp;Database <br>  ==
+== Routing CSV&nbsp;Database <br>  ==
 The CSV database is composed of 4 groups of [http://en.wikipedia.org/wiki/Comma-separated_values CSV] files.&nbsp; Those files covers configuration of all aspects required by the routing engine.&nbsp; Files enables all route management, modification, backup and update to take place outside Toolpack webportal, using your favorite software.&nbsp; Once the files are ready, the are imported in the Toolpack system using WebPortal.&nbsp; 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&nbsp;"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.&nbsp; Global routes are always used along with the RouteSet during routing.
 == Dynamic Route Tables  ==

@@ Line 81: / Line 81: @@
 *File content IS case sensitive.<br>
-=== RouteSets.csv File  ===
+=== RouteSets.csv  ===
 This file is the list of all RouteSet names configured in the system.&nbsp; <br>
@@ Line 93: / Line 93: @@
 "Toronto, On
 </pre>
-=== ''NapName''.csv File  ===
+=== ''NapName''.csv  ===
 There's one ''NapName.csv'' for each [[NAP|NAP]] configured in the system.&nbsp; Each file, is a list of ''number&lt;''-&gt;''routesetname'' association for the [[NAP|NAP]].&nbsp; <br>
@@ Line 116: / Line 116: @@
 As we'll see later, for each RouteSet&lt;-&gt;NAP association, a dynamic route entry gets created.&nbsp; 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>
@@ Line 132: / Line 132: @@
 === Routes.csv<br>  ===
-This file is optionnal, and defines static routes.&nbsp; 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.&nbsp; 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>