Routing
From Yate Documentation
(Difference between revisions)
| Line 46: | Line 46: | ||
<div class="tel-desc"> </div> | <div class="tel-desc"> </div> | ||
|} | |} | ||
| + | |||
| + | |||
| + | '''See also''' | ||
| + | |||
| + | * [[Modules| All Yate modules]] | ||
| + | * [[Telephony]] | ||
Revision as of 16:27, 6 December 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:
| Routing modules in Yate | How to do routing in Yate |
|
Module used for autentication, registration, and routing of users from a file.
Module used for routing incoming and outgoing call legs.
Javascript module is a module support for programmatically routing a call step by step.
Module used to write CDR(Call Detail Record) data in the database.
Module used to route a call to multiple alternative targets.
Performs routing using the ENUM protocols that maps phone numbers to VoIP (or even other PSTN) resources.
This module allows building clusters of servers for a single domain.
This module can be used whenever you need to route the calls to one or several numbers or aliases whose addresses are unknown in advance.
This module keeps a count of active calls per user specified context and adds one or all counters to be used in routing decisions.
|
|
See also
