Tmedia Routing

Revision as of 11:52, 1 February 2011

TelcoBridges has developed a simple and flexible call routing engine.

It is possible to represent the features of the call routing engine in 4 different sections:

• Base Routing
• Standard Routing Scripts
• Scriptable Routing
• Routing Tables

Base Routing

The base routing is configured by default in the VoIP Gateway.

It uses the parameters from the incoming call to find a route and make the routing decision.

Incoming call parameters used by base routing:

• NAP
• Called Number
• Calling Number

NOTE:The route can filter the called and/or calling numbers using a specific number or use a regular expression.

Once there is a route match (subject to NAP availability), the TMG-CONTROL can remap those call parameters to create the outgoing call.

Here are the parameters that can be change for an outgoing calls:

• NAP
• Profile
• Called Number
• Calling Number

The called and calling number can be remapped by using a regular expression.

Route Retry

The routing engine returns all matching routes to the system. The TMG-CONTROL then generate an outgoing call using the first route of the list. If the call fails, the TMG-CONTROL may or may not generate another call according to the error code received.

The route retry will proceed with another route if the return code is:

• Service unavailable
• No route to destination
• Etc.

The route retry will not proceed with another route if the return code is:

• User busy
• Unallocated number
• Etc.

It is worth noting that it is possible to modify when the route retry to and not to proceed using the nap profile. For more information see the route retry page.

NOTE:The route retry feature is available to the other types of routing as well.

Standard Routing Scripts

TMG-CONTROL has a ready-to-use routing script that can address some of the most common routing needs.

NAP Priority Routing

• Choose the route according to NAP priority.
• Each NAP has its own priority setting
  • NAP custom column: prio (the lower the value, the higher the priority)
• If more than 1 route matches, the route with the highest NAP priority will be selected first

Route Priority Routing

• Choose the route according to route priority.
• Each route has its own priority setting
  • Route custom column: prio (the lower the value, the higher the priority)
• If more than 1 route matches, the route with the highest route priority will be selected first

Percentage Routing

• Load share traffic between multiple NAPs
• Each NAP has its own weight setting
  • NAP custom column: percent_target (the higher the weight, the higher the traffic proportion)
• If more than 1 route matches, the outgoing will be generated according to weight and ASR

Scriptable Routing

For customers who requires more complex scenarios, it is possible to use the scriptable routing engine.

Features of the scriptable routing engine

• Scripts are written in Ruby
• Can use the Web Portal for editing the scripts
• Does complex routing and routing translation on a large amount of parameters:
  • Calling Number, Called Number, NOA, NPI, Presentation, Screening, Redirecting Number, Original Called Number, etc.
• Can modify the ready-to-use routing script to add functionality
• Can import and export routing scripts in .rb format
• TMG-CONTROL upgrade doesn't will not modify scripts

Routing Tables

The routing tables are useful for customers that needs to manage a very large number of phone numbers that can be accessible from one or more providers but cannot be easily expressed with a regular expression.

The routing tables can be summarize by the following:

• Breaks the provider/called number relationship (from a regular route) into 2 entities
  • Digit map
  • Routeset definition
• The digit map creates an association for each phone number to 1 or many destinations
• The Routeset definition creates an association for each provider to 1 or many destinations

NOTE: The routing tables support import/export of rouset definition and digit map in CSV file format.