Actions

Call routing: Difference between revisions

(add category)
No edit summary
Line 3: Line 3:


== TelcoBridges and Call routing ==
== 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 Toolpack Media Gateway application where you can manually define [[Toolpack:Creating Called Number Routes|called number routes]]. The second approach, introduced in [[Version 2.3|version 2.3]] of [[Toolpack]], leverages the Ruby scripting language to provide a [[Scriptable Routing Engine|scriptable routing engine]].
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 [[Toolpack:Creating Called Number Routes|called number routes]]. The second approach, introduced in [[Version 2.3|version 2.3]] of [[Toolpack]], leverages the Ruby scripting language to provide a [[Scriptable Routing Engine|scriptable routing engine]].





Revision as of 14:39, 21 April 2011

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


References