Routing

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
Line 29: Line 29:
 
|[[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]] Module
+
|[[Call Counters|Call Counters Module]]  
 
|[[How to use callcounters module to count incoming calls]]
 
|[[How to use callcounters module to count incoming calls]]
 
|-
 
|-
 
|}
 
|}

Revision as of 14:01, 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:

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 module How to do round-robin routing
ENUM route module
Cluster route module Configuring regexp and callto parameters in cluster route module
Late routing Module Forking a call using lateroute
Call Counters Module How to use callcounters module to count incoming calls
Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers