Search results

Just to make sure that your account is working, you should make a few test calls (both incoming and outgoing). * '''gvoice.yate''' – located in modules. This sends DTMF tones at answer time (the “+1” you need to press to a

...owing section to extmodule.conf (the word after "listener" will become the module name) [listener test]

...r_expressions|regexroute]]/[[External_Module|external module]]/custom yate module. ...ndle [[xsip.generate]] and send SIP requests of behalf on scripts or other modules.

The '''socket.ssl''' message is sent by a module requesting to turn a regular TCP socket into a SSL/TLS encrypted one. ;test

Test an existing PHP script on Windows. <br> ... Windows this is not possible, so a listener in [[External Module|external module]] must be configured to connect to a TCP socket.

* [[Javascript module]] Configuring Javascript module to use routing or global scripts.

* Development libraries for all optional modules in Yate you want to compile '''Note:''' To provide dynamic loading system for modules Yate uses pragmatic dlopen()/dlsym() system calls.

* Development libraries for all optional [[modules]] in Yate you want to compile like: ::* [http://www.mysql.com/ MySQL] library - used by [[MySQL| MySQL Module]].

...ompile please build the "YATE" project - it will build the library and all modules without external dependencies. The "Extra" project holds modules that have external dependencies. You will not be able to build them withou

The processing module will set message's parameters named '''osip_headername''' to be returned in ====How to set X-Test header ====

...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.

...scribes the external module command flow - the protocol used by [[External Module|extmodule]] to communicate with external scripts. <br/>Look in share/script 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 provi * Some test-routes. Starting with 000 - so no overlap with international / local area c

; 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

javascript eval Engine.debug("test") javascript eval=script_name Engine.debug("test"+var_name)

Engine.output("1",1,"test"); Engine.output("1" + " " + 1 + " test");

This message is sent by the [[ISUP Mangler|ISUP Mangler]] module allowing to modify the parameters of an ISUP message passing through the ST * You must not alter the IAM continuity check flags as it would cause the test to fail or the loopback to be left in place indefinitely.

Module ysigchan purposes: This module is based on the [[signalling]] library and uses driver module(s) (e.g. [http://docs.yate.ro/wiki/Zapcard zapcard], [http://docs.yate.ro/w

The '''isup.mangle''' message is sent by the [[ISUP Mangler|ISUP Mangler]] module allowing to modify the parameters of an ISUP message passing through the ST * You must not alter the IAM continuity check flags as it would cause the test to fail or the loopback to be left in place indefinitely.

The module implements sending of HTTP requests to a server.<br> ...ng to check if the request started.<br>Further message processing by other module(s) will stop if this parameter is set to true.