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 fe9c1c1c98 Added a ClientProxy engine run mode for clients with no local UI.
git-svn-id: http://yate.null.ro/svn/yate/trunk@2759 acf43c95-373e-0410-b603-e72c3f656dc1
2009-07-14 15:49:20 +00:00
clients Changed thread names to be uniform and easily readable. 2009-06-22 14:48:26 +00:00
conf.d Added "address" and "version" settings so MGCP can become operational even if no RSIP is received. 2009-06-25 18:27:24 +00:00
docs Filter YCLASS*() macros when generating documentation, they confuse the parsers. 2009-05-26 14:57:00 +00:00
engine Added a ClientProxy engine run mode for clients with no local UI. 2009-07-14 15:49:20 +00:00
libs Decode generically known but unhandled ISUP messages that have only optional parameters. 2009-06-26 14:40:10 +00:00
modules Added a ClientProxy engine run mode for clients with no local UI. 2009-07-14 15:49:20 +00:00
packing If creating debug info retain symbols of modules. 2008-11-12 18:30:22 +00:00
share utils.outgoing result changed 2009-07-13 17:02:55 +00:00
tools Generate a full (including variable values) backtrace on the core. 2008-11-10 16:41:19 +00:00
windows Added Cisco Session Manager module. 2009-05-10 15:50:08 +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 Generate yate-config.in dynamically to add support for arbitrary parameters. 2009-06-10 13:43:42 +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 Detect prctl availability when configuring. 2009-06-22 12:22:52 +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 Client sounds can now carry a stereo parameter. This parameter is forwarded by utility client channels in the chan.attach message. 2009-06-22 16:09:09 +00:00
yateclass.h Added an unified Thread::idle method, use it instead of arbitrary 2009-06-24 16:47:29 +00:00
yateiss.inc.in Include code status in installer. 2008-01-08 19:22:51 +00:00
yatemime.h Better handling of quoted strings, added parameter to force quoting. 2008-11-24 13:42:06 +00:00
yatengine.h Added a ClientProxy engine run mode for clients with no local UI. 2009-07-14 15:49:20 +00:00
yatephone.h Added flags to data forwarded through DataNodes. 2009-07-02 09:24:33 +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.