Call routing: Difference between revisions
m (modified name to add Tmedia_Call_Routing_Platform_v4) |
(Updated links) |
||
| Line 8: | Line 8: | ||
== Related actions == | == Related actions == | ||
*Creating called number routes (refer to the appropriate Toolpack release): | *Creating called number routes (refer to the appropriate Toolpack release): | ||
**[[ | **[[Toolpack:Call_Routes_Settings_B|Call routes for version 2.9]] | ||
**[[ | **[[Toolpack:Call_Routes_Settings_A|Call routes for version 2.8]] | ||
**[[Web_Portal_Tutorial_Guide_v2.7#Routes|Call routes for version 2.7]] | |||
**[[Toolpack:Creating_a_First_Call_Route_A|Call routes for version 2.5 and 2.6]] | |||
*[[Scriptable Routing Engine|Configure routing via the Toolpack scriptable routing engine]] | *[[Scriptable Routing Engine|Configure routing via the Toolpack scriptable routing engine]] | ||
Revision as of 16:29, 11 August 2016
Call routing refers to the ability to route calls based on criteria such as origin, destination, time of day, service provider rates, etc.
TelcoBridges and Call routing
TelcoBridges supports call routing across all of its Tmedia and Tdev devices. It offers two approaches to routing. The first is via the TMG-CONTROL where you can manually define called number routes. The second approach, introduced in version 2.3 of Toolpack, leverages the Ruby scripting language to provide a scriptable routing engine.
Related actions
- Creating called number routes (refer to the appropriate Toolpack release):
- Configure routing via the Toolpack scriptable routing engine