Toolpack v2.3:Creating Called Number Routes - Revision history

Allyntree: /* To create a called number route */

2009-11-01T17:07:10Z

To create a called number route

Allyntree: /* To create a called number route */

2009-11-01T16:55:42Z

To create a called number route

Allyntree: /* To create a called number route */

2009-11-01T16:52:14Z

To create a called number route

Allyntree: /* To create a called number route */

2009-11-01T16:51:18Z

To create a called number route

Allyntree: Created page with 'To facilitate the routing of calls from and to network access points (NAPs), or between NAPs, routing rules are defined. '''Note:''' Version 2.3 of Toolpack introduced a…'

2009-11-01T16:50:25Z

Created page with 'To facilitate the routing of calls from and to network access points (NAPs), or between NAPs, routing rules are defined. '''Note:''' Version 2.3 of Toolpack introduced a…'

New page

To facilitate the routing of calls from and to [[NAP|network access points]] (NAPs), or between NAPs, routing rules are defined.

'''Note:''' Version 2.3 of Toolpack introduced a new [[Scriptable Routing Engine|script-based routing engine]] that can be used in place of or in addition to the following approach.

== To create a called number route ==

'''1. Select 'Configurations' under 'Gateway' from the navigation panel.'''

[[Image:Menu-configurations.jpg|150px| ]]

'''2. Click 'Edit' to access the routing gateway configuration.'''

[[Image:screenshot-media-gateway-configuration-window.jpg|600px| ]]

'''3. Click 'Create New Route', to access the gateway configuration window.'''

[[Image:Screenshot-create-new-route-option.jpg|600px| ]]

'''4. Enter the called number mask.'''

In this example, a caller dialing 911 will get routed to the Bell NAP.
*Click 'Create' to save the routing rule

[[Image:Screenshot-create-new-route-rule.jpg|600px]]

'''5. Verify that the newly create routing rule appears in the Route listing.'''
*Click 'Create New Route' to add another routing rule.

[[Image:Screenshot-create-2nd-route-rule.jpg|600px]]

'''6. Enter a value for the called number mask and assign it to a NAP.'''

In this example a call starting with an area code originating on the Videotron NAP is routed to the Bell NAP.

*Click 'Create' to save this routing rule.

[[Image:Screenshot-routing-rule-videotron-bell.jpg|600px]]

'''Note:''' The mask fields are designed to accept RegEx (regular expressions) syntax. In the example, shown above, the called number mask is using regular expressions to say that a called number starting with 450 and followed by seven digits, each ranging from 0-9, is to be routed to the Bell NAP.

'''7. Verify that the routing rules appear in the Routes listing.'''

[[Image:Screenshot-list-of-routing-rules.jpg|600px]]

== What You Can Specify in a Route ==
In a route, one may specify the following 3 matching criterion for route selection of an incoming call.
* called number mask
* calling number mask
* NAP: this is the NAP from which the call comes.

If any of the above fields are blank, that criteria is not used.

You can use RegEx (regular expression) in called number mask and calling number mask to specify particular matching rules in this field, e.g. to match only the prefix of the called number. Please refer to the description on [[Toolpack: How to Use RegEx in Called and Calling Number Mask|How to Use RegEx in Called and Calling Number Mask]].

The field "Remapped NAP" specify which NAP the call is routed to when this route is selected.

Digit remapping or digit translation can also be performed on called number and calling number in the outgoing call leg when the call is routed. The remapping rules are specified on per route basis. Under the Advanced Parameters there are 2 fields, Remapped Called Number Mask and Remapped Calling Number Mask. You can use RegEx to specify the rules in these 2 fields. Please refer to the description on [[Toolpack: How to Use RegEx in Remapped Called and Calling Number Mask|How to Use RegEx in Remapped Called and Calling Number Mask]].

== Disclaimer ==
The use of Bell and Videotron--two Canadian service providers--here is for demonstrative purposes only and implies no pre-existing relationship with TelcoBridges or endorsement of it on the part of either company.)

@@ Line 29: / Line 29: @@
-[[Image:Screenshot-create-new-route-rule.jpg|600px]]
+[[Image:Web_Portal_v2.3_Creating_Route.png|700px]]
@@ Line 36: / Line 36: @@
-[[Image:Screenshot-create-2nd-route-rule.jpg|600px]]
+[[Image:Web_Portal_v2.3_Create_Route_2.png|700px]]
@@ Line 46: / Line 46: @@
-[[Image:Screenshot-routing-rule-videotron-bell.jpg|600px]]
+[[Image:Web_Portal_v2.3_Creating_Route_2.png|700px]]
 '''Note:''' The mask fields are designed to accept RegEx (regular expressions) syntax. In the example, shown above, the called number mask is using regular expressions to say that a called number starting with 450 and followed by seven digits, each ranging from 0-9, is to be routed to the Bell NAP.
@@ Line 53: / Line 53: @@
 '''7. Verify that the routing rules appear in the Routes listing.'''
+[[Image:Web_Portal_v2.3_Route_Created.png|700px]]
-[[Image:Screenshot-list-of-routing-rules.jpg|600px]]
 == What You Can Specify in a Route ==

← Older revision		Revision as of 16:55, 1 November 2009
Line 20:		Line 20:


−	[[Image:~~Screenshot-create-new-route-option~~.~~jpg\|600px~~\| ]]	+	[[Image:Web_Portal_v2.3_Create_Route.png\|700px]]

← Older revision		Revision as of 16:52, 1 November 2009
Line 14:		Line 14:


−	[[Image:~~screenshot-media-gateway-configuration-window~~.~~jpg\|600px~~\| ]]	+	[[Image:Web_Portal_v2.3_Edit_Configuration.png\|700px]]

← Older revision		Revision as of 16:51, 1 November 2009
Line 8:		Line 8:


−	[[Image:~~Menu-configurations~~.~~jpg\|150px\|~~ ]]	+	[[Image:Navigation_Panel_v2.3_Configurations.png]]