Routing
From Yate Documentation
(Difference between revisions)
Line 1: | Line 1: | ||
− | |||
− | You | + | Yate has multiple routing modules. You can set all routing in a module or use a combination of them. A routing module is a module that handles (sees) the call.route message. |
+ | |||
+ | If more than one module is used, then the priority that is set in each configuration file associated to the module will be used. This priority will establish the order in which the modules handle the routing request. A numerically lower priority means a higher actual priority of the route. A module can add/modify parameters without handling the message. | ||
This is the list of the routing modules and a HowTo for each of them: | This is the list of the routing modules and a HowTo for each of them: |
Revision as of 14:40, 4 October 2012
Yate has multiple routing modules. You can set all routing in a module or use a combination of them. A routing module is a module that handles (sees) the call.route message.
If more than one module is used, then the priority that is set in each configuration file associated to the module will be used. This priority will establish the order in which the modules handle the routing request. A numerically lower priority means a higher actual priority of the route. A module can add/modify parameters without handling the message.
This is the list of the routing modules and a HowTo for each of them:
Routing modules in Yate | How to do routing in Yate |
---|---|
Regfile module | How to register users from regfile |
Regular expressions module | Redirecting Calls to another User in the Regex Module |
Javascript routing module | How to do routing using javascript |
Register module | How to register users from register |
Call forker | How to do round-robin routing |
ENUM based routing | |
Clustering support |