RouteLabel - Revision history

William Wong at 07:46, 12 January 2018

2018-01-12T07:46:03Z

2018-01-12T07:42:16Z

← Older revision		Revision as of 03:42, 12 January 2018
Line 18:		Line 18:


	In this routing table, we have three routes in a RouteSet named ~~"Montreal, Qc"~~. In order words, we have three routes for Montreal, Qc.		In this routing table, we have three routes in a RouteSet named Montreal_Qc. In order words, we have three routes for Montreal, Qc.

	With the routing table in place, the association between a called number and a destination is done by the [[Digit Analyzer]].		With the routing table in place, the association between a called number and a destination is done by the [[Digit Analyzer]].

2011-09-13T19:33:11Z

← Older revision	Revision as of 15:33, 13 September 2011
(No difference)

2010-08-24T20:30:42Z

clean up

← Older revision		Revision as of 16:30, 24 August 2010
Line 1:		Line 1:
	A RouteSet is a group of possible routes for a given destination. Routes are associated to a RouteSet by referring to its name. And each route in the RouteSet refers to a different [[NAP]] that can be used to reach the destination.~~<br>~~		A RouteSet is a group of possible routes for a given destination. Routes are associated with a RouteSet by referring to its name. And each route in the RouteSet refers to a different [[NAP]] that can be used to reach the destination. Here is an example:

	~~Example:~~

	{\| width="200" border="1" cellpadding="1" cellspacing="1"		{\| width="200" border="1" cellpadding="1" cellspacing="1"
Line 18:		Line 17:
	\|}		\|}

	~~In this routing table, we have three routes on RouteSet named "Montreal, Qc".  In order words, we have three routes for Montreal, Qc.~~

	~~Now~~, the association between a called number and a destination is done by the [[~~Digit_Analyzer~~]].		In this routing table, we have three routes in a RouteSet named "Montreal, Qc". In order words, we have three routes for Montreal, Qc.

			With the routing table in place, the association between a called number and a destination is done by the [[Digit Analyzer]].

2010-03-17T21:34:11Z

← Older revision		Revision as of 17:34, 17 March 2010
Line 20:		Line 20:
	In this routing table, we have three routes on RouteSet named "Montreal, Qc".  In order words, we have three routes for Montreal, Qc.		In this routing table, we have three routes on RouteSet named "Montreal, Qc".  In order words, we have three routes for Montreal, Qc.

	Now, the association between a called number and a destination is done by the [[~~DigitAnalyzer~~]].		Now, the association between a called number and a destination is done by the [[Digit_Analyzer]].

2010-03-17T21:33:34Z

← Older revision		Revision as of 17:33, 17 March 2010
Line 20:		Line 20:
	In this routing table, we have three routes on RouteSet named "Montreal, Qc".  In order words, we have three routes for Montreal, Qc.		In this routing table, we have three routes on RouteSet named "Montreal, Qc".  In order words, we have three routes for Montreal, Qc.

	Now, the association between a called number and a destination is done by the [[~~RoutesetsDigitAnalyzer~~]].		Now, the association between a called number and a destination is done by the [[DigitAnalyzer]].

2010-03-17T21:32:45Z

← Older revision		Revision as of 17:32, 17 March 2010
Line 18:		Line 18:
	\|}		\|}

	~~<br>~~		In this routing table, we have three routes on RouteSet named "Montreal, Qc".  In order words, we have three routes for Montreal, Qc.

	In this ~~example~~, we have three routes on ~~the~~ RouteSet named "Montreal, Qc".  In order words, we have three routes for Montreal, Qc.

	Now, the association between a called number and a destination is done by the [[RoutesetsDigitAnalyzer]].		Now, the association between a called number and a destination is done by the [[RoutesetsDigitAnalyzer]].

2010-03-17T21:30:21Z

← Older revision		Revision as of 17:30, 17 March 2010
Line 1:		Line 1:
	A RouteSet is a group of possible routes for a given destination. Routes are associated to a RouteSet by referring to its name. ~~Each~~ route in the RouteSet refers to a different [[NAP]] that can be used to reach the destination.<br>		A RouteSet is a group of possible routes for a given destination. Routes are associated to a RouteSet by referring to its name. And each route in the RouteSet refers to a different [[NAP]] that can be used to reach the destination.<br>

	Example:		Example:

2010-03-17T21:29:16Z

← Older revision		Revision as of 17:29, 17 March 2010
Line 1:		Line 1:
	A RouteSet is a group of possible routes for a given destination. Routes are associated to a RouteSet by referring to its name. Each route in the RouteSet refers to a different [[NAP]] that can be used to reach the destination.		A RouteSet is a group of possible routes for a given destination. Routes are associated to a RouteSet by referring to its name. Each route in the RouteSet refers to a different [[NAP]] that can be used to reach the destination.<br>

	<br>

	Example:		Example:
Line 8:		Line 6:
	\|-		\|-
	! scope="col" \| Nap		! scope="col" \| Nap
	~~! scope="col" \| Match~~
	! scope="col" \| RouteSet		! scope="col" \| RouteSet
	\|-		\|-
	\| Bell		\| Bell
	~~\| 514201~~
	\| Montreal, Qc		\| Montreal, Qc
	\|-		\|-
	\| Videotron		\| Videotron
	~~\| 514201~~
	\| Montreal, Qc		\| Montreal, Qc
	\|-		\|-
	\| Rogers		\| Rogers
	~~\| 514201~~
	\| Montreal, Qc		\| Montreal, Qc
	\|}		\|}

	<br>		<br>

	~~     ~~

	~~Route1 : Bell~~

	~~<br> Example Scenario Destination:~~ "Montreal, Qc" ~~Possible Routes:~~		In this example, we have three routes on the RouteSet named "Montreal, Qc".  In order words, we have three routes for Montreal, Qc.

	~~1: Bell~~		Now, the association between a called number and a destination is done by the [[RoutesetsDigitAnalyzer]].
	~~2: Rogers~~
	~~3: Videtron~~

	~~<br>~~

2010-03-17T21:22:06Z