YATE(8)
yate(8) π launch the YATE telephony engine
okay bestie, gather round β this is the page for yate(8), the Telephony Engine main character. No cap, itβs a whole vibe and also a real Unix manual page, so letβs get into it π
β¨ NAME β¨
yate β launch the YATE telephony engine. Thatβs the name, thatβs the job, periodt π
πΈ SYNOPSIS πΈ
yate [options] [commands]
π¦ DESCRIPTION π¦
yate is a telephony engine that supports client, PBX and IVR functions through plugins. Literally the whole description, and itβs giving βsmall sentence, big jobβ energy π«Ά
π OPTIONS π
General
-h,--helpβ Display a short help message and exit. Your βhelp me bestieβ button β¨-V,--versionβ Display program version and exit.-vβ Verbose logging (you can use more than once). Use it again for even more chatter π-qβ Quieter logging (you can use more than once).-dβ Daemonify, suppress output unless logged. Main character goes quiet and runs in the background π-s[=msec]β Supervised, restart if crashes or locks up, optionally sleeps initially.-rβ Enable rotation of log file (needs-sand-l). Yes, itβs a package deal, bestie π-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.-u pathnameβ Path to user data files directory, overrides compiled-in value.-m pathnameβ Path to modules directory, overrides compiled-in value.-e pathnameβ Path to shared directory, overrides compiled-in value.-x dirpathβ Absolute or relative path to extra modules directory (can be repeated). Stack βem if you need to π§-w directoryβ Change working directory.-N nodenameβ Set the name of the node in a cluster.
Debugging options (may not be compiled in)
-Cβ Enable core dumps if supported by the operating system.-Fβ Increase the maximum file handle to compiled value.-Sβ Set size of supervised sanity points pool.-tβ Truncate the log file instead of appending to it.-D[options]β Special debugging options. The little sub-options live below, iykyk π-Daβ Abort (coredumps if allowed) if bugs are encountered.-Dmβ Attempt to debug mutex deadlocks by setting a maximum 10s limit, if repeated halves the limit.-Ddβ Enable some locking debugging and safety features, degrades performance.-Dlβ Attempt to load modules without having their symbols globally visible.-Dcβ Calldlclose()until it gets an error.-Duβ Do not unload modules, just try to call their 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. Cute output, technically speaking π-Dsβ Abort if bugs are encountered even during shutdown.-DOβ Attempt to debug all object allocations by counting objects per plugin, degrades performance.-Dnβ Do not add timestamps to debugging messages.-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 formatYYYYMMDDhhmmss.uuuuuu.-DFβ Add GMT timestamps to debugging messages in formatYYYY-MM-DD_hh:mm:ss.uuuuuu.-Dzβ Add local timezone timestamps to debugging messages in formatYYYYMMDDhhmmss.uuuuuu.-DZβ Add local timezone timestamps to debugging messages in formatYYYY-MM-DD_hh:mm:ss.uuuuuu.
π COMMANDS π
Each command is sent to the YATE modules immediately after initialization. Modules define command syntax, so thatβs not described here β please look at the documentation for each module. Bestie, read the module docs, they said it, not me π
π SIGNALS π
SIGTERMandSIGINT(Ctrl+C) will cleanly stop the engine.SIGQUIT(Ctrl+</kbd>) will reinitialize the modules.SIGHUPwill reinitialize the modules if started in daemon mode (-d).SIGUSR1will initiate a graceful restart (when no plugin is busy).SIGUSR2will initiate an immediate restart. No waiting, no thoughts, just restart π
π BUGS π
Under various*BSDimplementations thedlclose()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.
Yeah, thatβs the warning section, and itβs giving βhandle with careβ energy. Not me pretending I didnβt see it π
π AUTHORS π
Paul Chitescu <paulc@voip.null.ro>Diana Cionoiu <diana@voip.null.ro>
π«Ά SEE ALSO π«Ά
π YATE Β· September 2007 Β· YATE(8) β okay bestie, thatβs the whole page, now go be iconic π β¨
π¦ where this page comes from
- arch rolling: yate 6.4.1-1 Β· GPL
- nixos 26.05: yate 6.4.0-1
- nixpkgs unstable: yate 6.4.0-1
- opensuse-leap 16.0: yate 6.4.0-bp160.1.15 Β· GPL-2.0-or-later
- opensuse-leap 16.0: yate 6.4.0-bp160.1.15 Β· GPL-2.0-or-later
- opensuse-leap 16.0: yate 6.4.0-bp160.1.15 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms