Label Routing

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.

Concept

The concept is very simple.  

1. 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"
2. 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 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.

The NAP gets assigned a routeset_name by setting the a filename of the in the NAP dynamic columns named 'routeset_definition'. More than one NAP can use point to the same 'routeset_definition' file. This file must be imported in the database using the File Db view.

For each routeset_name<->NAP association, a dynamic route entry gets created

File Format

Each routeset_name can also be given optional attributes.

• One mandatory column: route_set_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.