Mirror/Fork of https://github.com/yatevoip/yate (formerly http://yate.null.ro/svn/yate/) with some fixes. We're submitting our patches upstream, but until they actually review/respond, we're collecting them here.
Go to file
Manawyrm 8a6c138dc7 Add new span parameter to zapcard, removing the need for offset calculations
DAHDI has nice readable names for each span, there's no need to do any channel
calculations by hand. This change searches for a span with the specified name
and will use it's offset as the channel offset.






which should be more reliable and less error-prone in the long run.
2022-10-30 12:52:21 +00:00
clients Added some larger client icon files. 2018-04-06 10:12:44 +00:00
conf.d Add support for building and running multiple instances of the same script. 2022-02-09 10:59:28 +00:00
docs Added extmodule support to put a script requested debug message in yate output/logging. Added support to change script's debug level and debug name. 2021-04-01 09:10:07 +00:00
engine Warn (single time per loaded file) if a configuration line exceeds internal buffer length. 2022-02-21 13:58:26 +00:00
libs q931: If we're the network, channelID in ALERTING/CALL_PROC/CONNECT is mandatory 2022-10-17 21:19:26 +02:00
modules Add new span parameter to zapcard, removing the need for offset calculations 2022-10-30 12:52:21 +00:00
packing Added G.722 codec from the WebRTC code. 2019-11-06 18:31:54 +00:00
share Added new function used to escape and concatenate message parameters: old function raises a warning in newer PHP versions. 2022-01-04 13:44:35 +00:00
tools Added support for monitoring services with name other than yate. 2018-11-19 21:07:13 +00:00
windows Bumped version to 6.4.0 release. 2021-08-02 12:12:11 +00:00
.cvsignore Made all YateLocal* to be ignored by SVN/CVS. 2008-02-05 12:25:40 +00:00
COPYING Updated copyright and FSF address. 2006-05-27 15:08:43 +00:00
ChangeLog Bumped version to 1.3.0 2007-08-27 17:26:32 +00:00
Makefile.in Updated files to Rev. 6330. 2018-12-04 10:06:04 +00:00
README Added copyright notices to sources and scripts missing them. 2014-02-05 11:42:17 +00:00
autogen.sh Added copyright notices to sources and scripts missing them. 2014-02-05 11:42:17 +00:00
configure.ac Bumped version to 6.4.1 devel. 2021-08-02 15:13:48 +00:00
main.cpp Added copyright notices to sources and scripts missing them. 2014-02-05 11:42:17 +00:00
run.in Added support for running through the "perf" tool. 2019-08-08 11:38:03 +00:00
yate-config.sh Put path where the library is found before the linked library. 2021-07-26 09:01:33 +00:00
yate.pc.in Added to pkgconfig several custom variables like in yate-config. 2008-10-09 14:53:51 +00:00
yatecbase.h Added copyright notices to sources and scripts missing them. 2014-02-05 11:42:17 +00:00
yateclass.h Implemented NamedCounter method that allows adding a specific value to the counter. 2022-02-03 15:49:57 +00:00
yateiss.inc.in Include code status in installer. 2008-01-08 19:22:51 +00:00
yatemath.h Fixed bug: properly return data pointer when requested offset is not 0. 2016-04-27 08:08:08 +00:00
yatemime.h Added hashing support for MimeSdpBody. 2014-07-02 07:34:19 +00:00
yatengine.h Added support to create arbitrary named lists of shared vars (separate from Engine's global). Added extra functions to shared vars list. Export in javascript. 2021-09-28 10:55:08 +00:00
yatephone.h Added extra parameter used to set relay filter in module install relay. 2021-12-16 11:37:39 +00:00
yateversn.h.in Added copyright notices to sources and scripts missing them. 2014-02-05 11:42:17 +00:00
yatewiresniff.h Update name from wiresniff to yatewiresniff. 2018-11-28 10:13:05 +00:00
yatexml.h Added XPath method used to escape XPath strings. 2022-02-01 10:30:09 +00:00


		YATE - Yet Another Telephony Engine

  The YATE project aims to be a fully featured software PBX.

  It was created to alow developers and users to have more functionality and
  scalability. To reach this goal YATE is built from two kinds of components:
    1. The main engine - telengine.
    2. Modules - routing modules
               - drivers
               - script language bindings
	       - billing modules
  Its license is GPL with exceptions (in case of linking with proprietary
  software). We have chosen this license to help the growth of this project.

Building YATE Software

YATE have been tested on Linux and Windows and was ported to FreeBSD.
Please report bugs at bugs@voip.null.ro

To build Yate the quick way is:
  make install

If you are lacking both doxygen and kdoc you will need to install without the
API documentation:
  make install-noapi

1. Building the engine

You have just to run 'make engine' in the main directory.

2. Building the modules.

Run 'make modules' in the main directory or 'make' in the modules directory.

3. Building the test modules.

Run 'make test' in the main directory or 'make' in the test directory.

After you have create the test modules use 'mktestlinks' in the modules
directory to make links from test modules into modules directory.

4. Building the classes API documentation

Run 'make apidocs' in the main directory. You will need to have kdoc or
doxygen installed.

Alternatively you can just 'make everything' in the main directory which will
build them all.

Running YATE

You can run YATE directly from the build directory - just use 'run' script
from the main directory.
  ./run -vvv

You can also install YATE - then you can run it from anywhere.
  yate -vvv

On the command line you can use '-v' to increase the verbosity level. If in
doubt run "run --help" (or "yate --help" if installed) to get a list of
possible options. There is also a manual page - "man yate" and read.

While running the following signals and keys are trapped and used:
  - SIGTERM and SIGINT (Ctrl-C) will cleanly stop the engine
  - SIGHUP and SIGQUIT (Ctrl-\) will reinitialize the modules
  - SIGUSR1 will gracefully restart a supervised engine
  - SIGUSR2 will forcefully restart a supervised engine

Configuring YATE

Some samples for the configuraton files can be found in the conf.d directory.
Note that you must rename them without the .sample extension or create symlinks
to them.