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 a4de576b90 Now allowing gsm.h to be in any directory.
git-svn-id: http://voip.null.ro/svn/yate@209 acf43c95-373e-0410-b603-e72c3f656dc1
2005-01-17 01:40:20 +00:00
clients Cleaned up Qt client. 2005-01-10 04:13:36 +00:00
conf.d Attempt to autodetect the nonportable pthread kill all other threads. 2005-01-10 01:40:05 +00:00
contrib Fixed URI parser limitation (protocol is now optional). 2005-01-17 00:42:27 +00:00
docs Fixed documentation bug about escaping strings. 2004-09-22 16:38:09 +00:00
engine Worked around a warning / AMD64 va_list initialization error. 2005-01-16 02:32:40 +00:00
modules Now allowing gsm.h to be in any directory. 2005-01-17 01:40:20 +00:00
scripts Added final parameter to disconnect. Renamed most messages. 2004-12-21 04:16:09 +00:00
tables Imported in new CVS 2004-05-22 00:05:20 +00:00
tarballs Imported in new CVS 2004-05-22 00:05:20 +00:00
test Many stability improvments. 2004-12-20 04:11:29 +00:00
.cvsignore *** empty log message *** 2005-01-09 07:29:07 +00:00
COPYING Imported in new CVS 2004-05-22 00:05:20 +00:00
ChangeLog Default config file name matches executable name 2005-01-10 17:57:37 +00:00
Makefile.in Attempt to autodetect the nonportable pthread kill all other threads. 2005-01-10 01:40:05 +00:00
README Imported in new CVS 2004-05-22 00:05:20 +00:00
autogen.sh Bugfix. 2004-12-22 00:06:58 +00:00
configure.in Now allowing gsm.h to be in any directory. 2005-01-17 01:40:20 +00:00
kdoc-filter.sh Fixed problems related to *printf arguments checking and kdoc. 2004-09-11 10:43:49 +00:00
main.cpp Added copyright notice. 2004-11-29 03:56:41 +00:00
run.in Imported in new CVS 2004-05-22 00:05:20 +00:00
yate-config.8 Added reference to pkg-config. 2005-01-09 06:27:11 +00:00
yate-config.in Fixed minor bug in watchdog routine. 2004-10-21 23:11:46 +00:00
yate.8 Build system and packaging changes. 2005-01-09 06:05:02 +00:00
yate.init Added chkconfig enabled init script. Changed apidocs build dependencies. 2004-09-06 09:00:42 +00:00
yate.pc.in Added copyright notice. 2004-11-29 03:56:41 +00:00
yate.spec.in Change log additions and a last minute patch. 2005-01-10 02:59:42 +00:00
yatengine.h Fixed possible ternary operator ? : bug. 2005-01-15 18:34:22 +00:00
yatephone.h Various minor engine improvments. Added more functionality in SIP. 2004-12-28 05:15:11 +00:00
yateversn.h.in Various minor engine improvments. Added more functionality in SIP. 2004-12-28 05:15:11 +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 only on Linux and is in alpha stage yet, so is very
possibile to find bugs (even if we have tried by design to minimize the
chance of introducing bugs). Please report them at bugs@voip.null.ro

1. Building the engine

You have just to run 'make' in the main directory, this will not build any
modules or test cases.

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 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.

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

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


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.