yate − launch the YATE telephony engine
yate [options] [commands]
yate is a telephony engine that supports client, PBX and IVR functions trough plugins.
General
−h, −−help
Display a short help message and exit
−V, −−version
Display program version and exit
−v |
Verbose debugging (you can use more than once) |
|||
−q |
Quieter debugging (you can use more than once) |
|||
−d |
Daemonify, suppress output unless logged |
|||
−s |
Supervised, restart if crashes or locks up |
|||
−r |
Enable rotation of log file (needs -s and -l) |
−l filename
Log to file − should be used whenever running in daemon mode
−p filename
Write PID of the supervisor or primary thread to file
−n configname
Use specified configuration name, overrides default "yate"
−c pathname
Path to conf files directory, overrides compiled-in value
−m pathname
Path to modules directory, overrides compiled-in value
−x relpath
Relative path to extra modules directory (can be repeated)
−w directory
Change working directory
Debugging options (may not be compiled in)
−C |
Enable core dumps if supported by the operating system |
−D[options]
Special debugging options
−Da |
Abort (coredumps if allowed) if bugs are encountered |
||
−Dm |
Attempt to debug mutex deadlocks by setting a maximum 10s limit |
||
−Dl |
Attempt to load modules without having their symbols globally visible |
||
−Dc |
Call dlclose() until it gets an error |
||
−Du |
Do not unload modules, just try to call thier finalization code |
||
−Di |
Reinitialize after first initialization |
||
−Dx |
Exit immediately after initialization |
||
−Dw |
Delay for one second the creation of the first worker thread |
||
−Do |
Colorize the output using ANSI control character sequences |
||
−Ds |
Abort if bugs are encountered even during shutdown |
||
−Dt |
Add start time relative timestamps to debugging messages |
||
−De |
Add EPOCH (1-1-1970 GMT) based timestamps to debugging messages |
||
−Df |
Add GMT timestamps to debugging messages in format YYYYMMDDhhmmss.uuuuuu |
Each command is sent to the YATE modules immediately after initialization. Modules define command syntax so that is not described here. Please look at the documentation for each module.
− SIGTERM and SIGINT (Ctrl−C) will cleanly stop the engine
− SIGHUP and SIGQUIT (Ctrl−\) will reinitialize the modules
− SIGUSR1 will initiate a gracefull restart (when no plugin is busy)
− SIGUSR2 will initiate an immediate restart
Under various *BSD implementations the dlclose() function is broken and may generate a segfault on exit.
Some libpthread implementations are broken and may fail to start the threads or fail to cleanup when the thread terminates.
Paul Chitescu <paulc AT voip DOT null DOT ro>
Diana Cionoiu <diana AT diana DOT null DOT ro>