Search results

#REDIRECT [[How to find which external modules are loaded from rmanager]]

Yate offers a module that does authentication, registration, routing from database, and it's cal ...er]] module and implement some of the functionality from another module or external script.

If you decide to do the routing from an external script, you add this custom params in call.route message when routing the c To write CDR in the database, module [[register]] can be used.

...g issues that permits you to monitorize the state of the system and of the modules. * at runtime - use [[rmanager]] module that allows you to see logs in real time and control the logging level.

...w - the protocol used by [[External Module|extmodule]] to communicate with external scripts. <br/>Look in share/scripts directory from yate's sources to find l The external user application or script comunicates with the module trough several file descriptors:

* Test your routes before going public. Calls may be routed through external providers instead on your network, and you may never notice. Actually, my D ====Redirecting Calls to another User in the Regex Module====

...n the functionality you want you can use a combination of Yate modules and external scripts. ===Yate modules and scripts for PBX functionality===

; enable: bool: Allow the SIP module to receive MESSAGE requests The [[call.route]] message will be handled by the [[Routing|routing]] module. You won't need to make other configurations if you already allowed SIP cal

... It implements [[External Module]] protocol and is suitable for developing external Yate scripts. More examples in 'examples' directory of this module.

Note that an external firewall, ACL settings on Cisco or [http://en.wikipedia.org/wiki/Selinux SE module=sig,format=Type|Status;count=2;link1=cisco-slt|Normal Alignment,link2=cisco