Routing
From Yate Documentation
(Difference between revisions)
| Line 11: | Line 11: | ||
|[[Regular expressions]] module || [[Redirecting Calls to another User in the Regex Module]] | |[[Regular expressions]] module || [[Redirecting Calls to another User in the Regex Module]] | ||
|- | |- | ||
| − | |[[Javascript routing]] module || How to do routing using javascript | + | |[[Javascript routing]] module || [[How to do routing using javascript]] |
|- | |- | ||
| − | |[[register|Register module]] || How to register users from register | + | |[[register|Register module]] || [[How to register users from register]] |
|- | |- | ||
|[[Call_Forker|Call forker]] || [[Round_Robin_Routing|How to do round-robin routing]] | |[[Call_Forker|Call forker]] || [[Round_Robin_Routing|How to do round-robin routing]] | ||
Revision as of 13:33, 4 October 2012
How to do routing in Yate? You have to know that it is done by using messages and it can be done from one or more modules. If more than one module it 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 of the execution for each module in Yate. A numerically lower priority means a higher actual priority of the route. What is useful to know is that in each module the parameters can be set without handeling the message.
And now let's see which module are in charge with routing and some how to examples:
| 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 |
