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 d786dc2360 Added to pkgconfig several custom variables like in yate-config.
git-svn-id: http://yate.null.ro/svn/yate/trunk@2255 acf43c95-373e-0410-b603-e72c3f656dc1
2008-10-09 14:53:51 +00:00
clients Handle spin boxes in set/get text. 2008-10-07 15:39:47 +00:00
conf.d Separated config for dumping NET and CPE sides of ISDN monitor to files. 2008-09-18 16:06:27 +00:00
docs New option -F to increase maximum file handle instead of running ulimit -n. 2008-03-10 15:40:54 +00:00
engine Fixed sync engine.start with client init. 2008-10-06 13:51:16 +00:00
libs Q.931 status reports now have local network as location. 2008-10-01 12:57:42 +00:00
modules Reworded the warning message about the HW echo canceller API. 2008-10-06 13:11:18 +00:00
packing Changed position of SVN revision so digits are separated from release code. 2008-09-18 15:48:44 +00:00
share keyecho examples updated 2008-10-02 15:51:06 +00:00
tools Added multi thread backtrace output via ./run --backtrace 2008-09-16 12:34:16 +00:00
windows Uploaded version to keep Windows in synch. 2008-09-19 17:43:25 +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 Added way to put SVN revision in package. 2008-09-18 15:33:08 +00:00
README Minor documentation additions. 2006-12-17 19:20:45 +00:00
autogen.sh Directory reorder #3 2007-11-15 23:06:36 +00:00
configure.in Added way to put SVN revision in package. 2008-09-18 15:33:08 +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.in New option to report code status and release. 2008-02-04 13:37:20 +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 Removed xmpp.iq message handler from client. 2008-10-06 10:23:58 +00:00
yateclass.h Added methods index() to find index of objects in a list. 2008-09-17 12:22:24 +00:00
yateiss.inc.in Include code status in installer. 2008-01-08 19:22:51 +00:00
yatemime.h Fixed some comments. 2008-01-18 07:56:01 +00:00
yatengine.h Config file missing warning can be disabled, use it to silence notices about files that are genuinely missing from a fresh install. 2008-07-25 09:09:12 +00:00
yatephone.h Made Module::itemComplete public, use it in several more places. 2008-09-16 15:30:54 +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.