Label Routing - Revision history

Serdar Civici at 07:07, 10 February 2020

2020-02-10T07:07:20Z

Serdar Civici at 07:06, 10 February 2020

2020-02-10T07:06:55Z

Luc Morissette: Updated links

2018-06-21T20:48:00Z

Updated links

William Wong: /* Concept */

2018-01-12T07:39:23Z

Concept

Luc Morissette: Added links to 2.8 and 2.9

2016-07-19T12:57:26Z

Added links to 2.8 and 2.9

Cbilodeau: removing provisioning section, need to use reference to web portal tutorial guide instead

2014-07-02T13:22:33Z

removing provisioning section, need to use reference to web portal tutorial guide instead

Cboulanger: Added sample loading time when using different sizes of label/digitmap files

2014-06-30T17:23:36Z

Added sample loading time when using different sizes of label/digitmap files

Luc Morissette: /* Configuration */

2014-01-31T14:28:36Z

Configuration

Cbilodeau: change link name

2012-12-11T13:59:06Z

change link name

Cbilodeau: move configuration content to web portal tutorial guide

2012-12-11T13:58:25Z

move configuration content to web portal tutorial guide

Show changes

@@ Line 60: / Line 60: @@
 *[[Web_Portal_Tutorial_Guide_v2.7#Label_Routing|Label routing for v2.7]]
 *[[Web_Portal_Tutorial_Guide_v2.6#Label_Routing|Label routing for v2.6]]
-*[[Adding NAP Grouping Script]]
 </div>
 == Useful links ==
 *[[Tmedia_Routing|Tmedia Routing]]

@@ Line 60: / Line 60: @@
 *[[Web_Portal_Tutorial_Guide_v2.7#Label_Routing|Label routing for v2.7]]
 *[[Web_Portal_Tutorial_Guide_v2.6#Label_Routing|Label routing for v2.6]]
 </div>
 == Useful links ==
 *[[Tmedia_Routing|Tmedia Routing]]

@@ Line 53: / Line 53: @@
 == Configuration  ==
 *[[Toolpack:Call_Routes_Settings_B#Label_Routing|Label routing for v2.9]]
 *[[Toolpack:Call_Routes_Settings_A#Label_Routing|Label routing for v2.8]]
 *[[Web_Portal_Tutorial_Guide_v2.7#Label_Routing|Label routing for v2.7]]
 *[[Web_Portal_Tutorial_Guide_v2.6#Label_Routing|Label routing for v2.6]]
 == Useful links ==
 *[[Tmedia_Routing|Tmedia Routing]]

@@ Line 8: / Line 8: @@
 #A list of numbers (NPA-NXX) for a specific destination is assigned a [[RouteSet|RouteSet]] name. This list can be very large
-##i.e., 514201,514202,514203, ... -&gt; "Montreal, Qc"
+##i.e., 514201,514202,514203, ... -&gt; Montreal_Qc
 #The list of routes for the destination is assigned the same [[RouteSet|RouteSet]] name. This list usually is limited to the number of [[NAP|network access points (NAP)]] in the system.
-##i.e., Bell, Rogers, Videotron -&gt; "Montreal, Qc"
+##i.e., Bell, Rogers, Videotron -&gt; Montreal_Qc
 <br> Note: No matter how many destination numbers lead to a given destination, only a limited list of routes are selected. At this point, complex, yet efficient, routing rules can take place.
 <br>
 == Implementation  ==

@@ Line 53: / Line 53: @@
 == Configuration  ==
 *[[Web_Portal_Tutorial_Guide_v2.7#Label_Routing|Label routing for v2.7]]
 *[[Web_Portal_Tutorial_Guide_v2.6#Label_Routing|Label routing for v2.6]]

← Older revision		Revision as of 13:22, 2 July 2014
Line 19:		Line 19:

	As previously mentioned, routeset (label) 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.		As previously mentioned, routeset (label) 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.
−
−	~~<br>~~
−
−	~~== Provisioning ==~~
−
−	Provisioning of large amounts of Routeset definition and digitmaps 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.
−
−	~~<br>~~
−
−	~~=== Routeset Definition ===~~
−
−	Each [[NAP]] in the system must be assigned a routesets_definition [http://en.wikipedia.org/wiki/Comma-separated_values CSV] file. A routesets_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.
−
−	~~<br> The routesets_definition file defines a list of [[RouteSet\|RouteSet]] names, with optional attributes.<br>~~
−
−	*One mandatory column: routeset_name (label)
−	*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, routes are created with custom attributes found in the second and third columns. Each custom attribute must be defined by adding a custom column in the gateway Route table.~~
−
−	<br>The [[NAP]] <-> Routeset Definition association is done by setting the [[NAP]] dynamic columns named 'routesets_definition'.  More than one [[NAP]] can point to the same 'routesets_definition' file. This file must be imported in the database using the File Db view in the Toolpack Web Portal.<br>
−
−	~~<br>~~
−
−	~~=== Digitmap ===~~
−
−	Each [[NAP]] in the system can be assigned a routesets_digitmap [http://en.wikipedia.org/wiki/Comma-separated_values CSV] file. It is usual that all NAP uses the same routesets_digitmap file. A routesets_digitmap file gives the association between numbers and [[RouteSet\|RouteSet]] names.
−
−	*Three mandatory columns: route_set_name, called and calling
−
−	~~called,calling,routeset_name~~
−	~~403200, ,"Calgary, AB"~~
−	~~514201, ,"Montreal, Qc"~~
−	~~514202, ,"Montreal, Qc"~~
−	~~514203, ,"Montreal, Qc"~~
−
−	The [[NAP]] <-> Routeset Digitmap association is done by setting the [[NAP]] dynamic columns named 'routesets_digitmap'.   This file must be imported in the database using the File Db view in the Toolpack Web Portal.
−
−	~~<br>~~
−
−	~~== Dynamic Routes ==~~
−
−	~~When provisioning is complete, dynamic routes can be generated by going in the Routetsets menu item, under Gateway menu Item.~~
−
−	~~{\| width="200" cellspacing="1" cellpadding="1" border="0"~~
−	\|-
−	~~\| valign="top" \| [[Image:Routesets.png\|left]]~~
−	~~\| valign="top" \| [[Image:Generate routes.png\|left]]~~
−	\|}

	<br>		<br>

← Older revision		Revision as of 14:28, 31 January 2014
Line 78:		Line 78:

	== Configuration ==		== Configuration ==
		+	*[[Web_Portal_Tutorial_Guide_v2.7#Label_Routing\|Label routing for v2.7]]
		+	*[[Web_Portal_Tutorial_Guide_v2.6#Label_Routing\|Label routing for v2.6]]

−	[[~~Web_Portal_Tutorial_Guide_v2.6#Label_Routing~~\|~~Label routing for v2.6~~]]	+	== Useful links ==
		+	*[[Tmedia_Routing\|Tmedia Routing]]

← Older revision		Revision as of 13:59, 11 December 2012
Line 79:		Line 79:
	== Configuration ==		== Configuration ==

−	[[Web_Portal_Tutorial_Guide_v2.6#Label_Routing\|~~Configuration~~ v2.6]]	+	[[Web_Portal_Tutorial_Guide_v2.6#Label_Routing\|Label routing for v2.6]]