Label Routing
| Line 1: | Line 1: | ||
| − | Routeset | + | Routeset Routing is an algorithm that combines [[Digit Analyzer|Digit Analyzer]] and the concept of [[RouteSet|RouteSet]]. It is implemented as a [[Scriptable Routing Engine|RoutingScript]] in Toolpack Gateway. This algorithm allows complex routing rules, as normally available with [[Scriptable Routing Engine|RoutingScript]], but on a very large number of destination numbers. |
| − | == | + | == Concept == |
| − | The concept is very simple. | + | The concept is very simple. |
| − | #A list of numbers for a specific destination is given a [[RouteSet|RouteSet]] name. This list can be very large.<br>ie: 514201,514202,514203, ... -> "Montreal, Qc" | + | #A list of numbers for a specific destination is given a [[RouteSet|RouteSet]] name. This list can be very large.<br>ie: 514201,514202,514203, ... -> "Montreal, Qc" |
#The list of routes for the destination is given the same [[RouteSet|RouteSet]] name. This list usually limits to the number of [[NAP|NAP]] in the system.<br>ie: Bell, Rogers, Videotron -> "Montreal, Qc" | #The list of routes for the destination is given the same [[RouteSet|RouteSet]] name. This list usually limits to the number of [[NAP|NAP]] in the system.<br>ie: Bell, Rogers, Videotron -> "Montreal, Qc" | ||
| + | <br> | ||
| + | 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 [[Scriptable Routing Engine|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 [http://en.wikipedia.org/wiki/Comma-separated_values 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 [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" | ||
| + | |||
| + | The routeset_definition file defines a list of [RouteSet|RouteSet]] names. A [[NAP]] is configured to refer to this file. The number of routeset_definition files is not limited, and each [[NAP]] can refer to the same file or to different files. | ||
| + | |||
| + | <br>Each routeset_name can also be given optional attributes. | ||
| + | |||
| + | <br> | ||
| + | |||
| + | === Routeset Digitmap === | ||
Revision as of 10:38, 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"
The routeset_definition file defines a list of [RouteSet|RouteSet]] names. A NAP is configured to refer to this file. The number of routeset_definition files is not limited, and each NAP can refer to the same file or to different files.
Each routeset_name can also be given optional attributes.
