Tmedia Routing
m (change sort key) |
(add standard routing information) |
||
| Line 6: | Line 6: | ||
*Scriptable Routing | *Scriptable Routing | ||
*Routing Tables | *Routing Tables | ||
| + | |||
| + | |||
==Base Routing== | ==Base Routing== | ||
| Line 28: | Line 30: | ||
==Standard Routing Scripts== | ==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|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|route]] with the highest [[NAP]] priority will be selected first | ||
| + | |||
| + | === Route Priority Routing === | ||
| + | |||
| + | *Choose the [[Route|route]] according to [[Route|route]] priority. | ||
| + | *Each [[Route|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|route]] with the highest [[Route|route]] priority will be selected first | ||
| + | |||
| + | === Percentage Routing === | ||
| + | |||
| + | *Load share traffic between multiple [[NAP|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== | ==Scriptable Routing== | ||
Revision as of 10:14, 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
Contents |
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:
The called and calling number can be remapped by using a regular expression.
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
