-
Yate has multiple routing modules. A routing module is a module that handles (sees) the [[call.route]] message.
...sage. A numerically lower priority means a higher priority of the route. A module can add/modify parameters without handling the message.
3 KB (433 words) - 09:01, 10 March 2016
-
.../local/etc/yate)<br>Path to user files directory (/root/.yate)<br> Path to modules directory (/usr/local/lib/yate)<br><br> (Type “yate -h” in your bash t
...g as a server with the new configuration files, the rest of the neccessary modules being loaded from their standard location.<br>Strongly recommended:<br>
12 KB (1,986 words) - 15:13, 31 October 2013
-
By default Yate loads modules relevant to its current running mode:
* all modules from the base module directory
12 KB (1,662 words) - 13:25, 1 October 2019
-
This module can be used whenever you need to route the calls to one or several numbers
...ently registered location. Other common use is the handling of some [[ENUM Routing|ENUM]] routes pointing back to PSTN.
2 KB (356 words) - 07:22, 23 May 2014
-
Lateroute is used to make a late route decision in Yate's message flow and fork is used to route the call to
...rom Yate 3.3.3, fork with distributive parameters. But in some cases, when routing to more than one user registered in regfile or for reducing the complexity
3 KB (419 words) - 14:03, 31 October 2013
-
...r_expressions|regexroute]]/[[External_Module|external module]]/custom yate module.
...ndle [[xsip.generate]] and send SIP requests of behalf on scripts or other modules.
5 KB (843 words) - 18:34, 13 March 2014
-
'''NOTE: This module is available in private version only.'''
This feature allows the module to generate a message faking a response when a request fails to be sent (in
43 KB (6,355 words) - 13:27, 1 October 2019
