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
paulc d462b9d886 Fixed a check in ysigchan component creation (probably harmless).
Bug spotted by Allan Sandfeld Jensen.


git-svn-id: http://yate.null.ro/svn/yate/trunk@3374 acf43c95-373e-0410-b603-e72c3f656dc1
2010-06-11 13:01:59 +00:00
clients Raise a window when activate it (activate might not bring it to front). 2010-05-28 13:28:38 +00:00
conf.d Documented the infix operator \| that matches either expression. 2010-06-11 12:33:28 +00:00
docs When started in interactive mode (not daemonified) shutdown on receiving SIGHUP since the console was closed. 2010-01-27 12:07:51 +00:00
engine Use the sdbm string hashing algorithm from http://www.cse.yorku.ca/~oz/hash.html 2010-06-11 12:29:00 +00:00
libs Spelling cleanup of a very common error: Retrive -> Retrieve 2010-06-11 11:25:10 +00:00
modules Fixed a check in ysigchan component creation (probably harmless). 2010-06-11 13:01:59 +00:00
packing Added portage ebuild script. 2010-05-07 15:55:58 +00:00
share Spelling cleanup of a very common error: Retrive -> Retrieve 2010-06-11 11:25:10 +00:00
tools Generate a full (including variable values) backtrace on the core. 2008-11-10 16:41:19 +00:00
windows Added xml library usage settings to sipfeatures Windows project. 2010-06-03 13:51:46 +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 No longer require to be root to run rpmbuild. 2010-05-02 21:08:49 +00:00
README Minor documentation additions. 2006-12-17 19:20:45 +00:00
autogen.sh Generate yate-config.in dynamically to add support for arbitrary parameters. 2009-06-10 13:43:42 +00:00
configure.in Fixed minor typo. 2010-05-27 13:44:27 +00:00
main.cpp Updated copyright and FSF address. 2006-05-27 15:08:43 +00:00
run.in Added multi thread backtrace output via ./run --backtrace 2008-09-16 12:34:16 +00:00
yate-config.sh Suppress the MODULE_ parameters since they can be retrieved by other means. 2009-06-10 14:16:44 +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 Spelling cleanup of a very common error: Retrive -> Retrieve 2010-06-11 11:25:10 +00:00
yateclass.h Spelling cleanup of a very common error: Retrive -> Retrieve 2010-06-11 11:25:10 +00:00
yateiss.inc.in Include code status in installer. 2008-01-08 19:22:51 +00:00
yatemime.h Made a lot of constructors explicit to prevent undesirable automatic conversions. 2010-06-08 15:25:05 +00:00
yatengine.h Spelling cleanup of a very common error: Retrive -> Retrieve 2010-06-11 11:25:10 +00:00
yatephone.h Spelling cleanup of a very common error: Retrive -> Retrieve 2010-06-11 11:25:10 +00:00
yateversn.h.in Added Qt4 package and status tag. 2008-01-07 21:07:07 +00:00

README

		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:
  ./configure
  make
  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.