Routing
From Yate Documentation
(Difference between revisions)
Line 28: | Line 28: | ||
|[[Late routing Module]] | |[[Late routing Module]] | ||
|[[Example of forking a call using lateroute|Forking a call using lateroute]] | |[[Example of forking a call using lateroute|Forking a call using lateroute]] | ||
+ | |- | ||
+ | |[[Call Counters]] | ||
+ | |[[How to set call counters for incoming calls]] | ||
|- | |- | ||
|} | |} |
Revision as of 13:45, 18 October 2012
Yate has multiple routing modules. A routing module is a module that handles (sees) the call.route message.
You can set all routing in a single module or use a combination of modules. If more than one module is used, then the priority that is set in each configuration file determines the order of the modules processing the message. A numerically lower priority means a higher priority of the route. A module can add/modify parameters without handling the message.
This is the list of the routing modules and a How To's for each of them: