Label Routing
| Line 22: | Line 22: | ||
=== Routeset Definition === | === Routeset Definition === | ||
| − | Each [[NAP]] in the system must be assigned a routeset_definition [http://en.wikipedia.org/wiki/Comma-separated_values CSV] file. A routeset_definition file gives the association between [[NAP|NAP]] and [[RouteSet|RouteSet]] names. The association between a [[NAP]] and a [[RouteSet|RouteSet]] name is in fact a route! ie: Rogers->"Montreal, Qc" | + | Each [[NAP]] in the system must be assigned a routeset_definition [http://en.wikipedia.org/wiki/Comma-separated_values CSV] file. A routeset_definition file gives the association between [[NAP|NAP]] and [[RouteSet|RouteSet]] names. The association between a [[NAP]] and a [[RouteSet|RouteSet]] name is in fact a route! ie: Rogers->"Montreal, Qc" Thus, for each [[RouteSet]] name<->[[NAP]] association, a dynamic route entry gets created. |
| − | |||
| + | The Routeset Definition file defines a list of [[RouteSet|RouteSet]] names, with optional attributes.<br> | ||
| − | + | *One mandatory column: routeset_name | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | *One mandatory column: | + | |
*Supplementary columns are used to provide optional and custom attributes to dynamically created routes | *Supplementary columns are used to provide optional and custom attributes to dynamically created routes | ||
| Line 45: | Line 37: | ||
In the above example, the routes are getting created with custom attributes found in the second and third column. Each custom attributes must be defined by adding a custom column in the gateway [[NAP]] table. | In the above example, the routes are getting created with custom attributes found in the second and third column. Each custom attributes must be defined by adding a custom column in the gateway [[NAP]] table. | ||
| − | <br> | + | <br>The [[NAP]] <-> Routeset Definition association is done by setting the [[NAP]] dynamic columns named 'routeset_definition'. More than one [[NAP]] can point to the same 'routeset_definition' file. This file must be imported in the database using the File Db view in the Toolpack Web Portal.<br> |
| − | + | ||
| − | <br> | + | |
=== Routeset Digitmap === | === Routeset Digitmap === | ||
Revision as of 10:55, 18 March 2010
Routeset Routing is an algorithm that combines Digit Analyzer and the concept of RouteSet. It is implemented as a RoutingScript in Toolpack Gateway. This algorithm allows complex routing rules, as normally available with RoutingScript, but on a very large number of destination numbers.
Contents |
Concept
The concept is very simple.
- A list of numbers for a specific destination is given a RouteSet name. This list can be very large.
ie: 514201,514202,514203, ... -> "Montreal, Qc" - The list of routes for the destination is given the same RouteSet name. This list usually limits to the number of NAP in the system.
ie: Bell, Rogers, Videotron -> "Montreal, Qc"
No matter how many destination number leading to a specific destination, only a limited list of routes gets selected. Then complex routing rules can take place, efficiently.
Implementation
As previously mentionned, Routeset Routing is implemented as a RoutingScript. It was written as an optional filter, and can be used in any existing scripts. This filter is a before_filter, and reduces the amount of routes the routing script will work with.
Provisioning
Provisioning of large amounts of Routeset Definition and Routeset Digitmap is accomplished by importing CSV files using the WebPortal. Those files are being saved in the HA Database.
Routeset Definition
Each NAP in the system must be assigned a routeset_definition CSV file. A routeset_definition file gives the association between NAP and RouteSet names. The association between a NAP and a RouteSet name is in fact a route! ie: Rogers->"Montreal, Qc" Thus, for each RouteSet name<->NAP association, a dynamic route entry gets created.
The Routeset Definition file defines a list of RouteSet names, with optional attributes.
- One mandatory column: routeset_name
- Supplementary columns are used to provide optional and custom attributes to dynamically created routes
routeset_name, cost, custom_1 "Montreal, Qc", "0.24", "custom_val"
In the above example, the routes are getting created with custom attributes found in the second and third column. Each custom attributes must be defined by adding a custom column in the gateway NAP table.
The NAP <-> Routeset Definition association is done by setting the NAP dynamic columns named 'routeset_definition'. More than one NAP can point to the same 'routeset_definition' file. This file must be imported in the database using the File Db view in the Toolpack Web Portal.
