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 e88f37919c Multiple media channels related changes.
git-svn-id: http://yate.null.ro/svn/yate/trunk@492 acf43c95-373e-0410-b603-e72c3f656dc1
2005-09-02 16:39:00 +00:00
clients Removed old Gtk-1 and Qt clients, added hashed lists. 2005-07-15 20:48:06 +00:00
conf.d Early 183 can be disabled from config file or routing. 2005-08-18 22:06:45 +00:00
contrib Multiple media channels related changes. 2005-09-02 16:39:00 +00:00
docs Added Stream and File classes, fixed a data related bug in extmodule. 2005-08-06 19:37:31 +00:00
engine Multiple media channels related changes. 2005-09-02 16:39:00 +00:00
modules Multiple media channels related changes. 2005-09-02 16:39:00 +00:00
scripts Added Stream and File classes, fixed a data related bug in extmodule. 2005-08-06 19:37:31 +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 *** empty log message *** 2005-05-03 18:27:14 +00:00
tools Added some usefull tools. 2005-05-05 14:50:34 +00:00
windows no message 2005-08-18 09:08:58 +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 Client related changes. 2005-05-05 17:02:18 +00:00
Makefile.in Added skinnable Gtk2 client. 2005-07-04 22:04:47 +00:00
README Updated informations. 2005-01-25 12:31:02 +00:00
autogen.sh Bugfix. 2004-12-22 00:06:58 +00:00
configure.in Moved skin files in their own directory. 2005-08-14 23:54:16 +00:00
kdoc-filter.sh *** empty log message *** 2005-05-02 18:31:05 +00:00
main.cpp no message 2005-05-18 12:20:04 +00:00
run.in Comment fixes. 2005-06-17 17:17:24 +00:00
yate-config.8 Added reference to pkg-config. 2005-01-09 06:27:11 +00:00
yate-config.in Bug fix by Daniel Freedman 2005-04-20 11:42:19 +00:00
yate.8 Mutex related changes in engine and channels. 2005-08-02 02:20:00 +00:00
yate.init Updated copyright years, fixed %ll formatting. 2005-04-29 22:05:07 +00:00
yate.pc.in Added a fork of oRTP in contrib, made some changes in the build system 2005-01-29 18:34:34 +00:00
yate.spec.in Version 0.8.7 2005-01-18 01:31:00 +00:00
yatecbase.h *** empty log message *** 2005-08-19 23:21:31 +00:00
yateclass.h Ugly workaround non-multithread capable Windows UI. 2005-08-13 02:02:55 +00:00
yatengine.h Multiple media channels related changes. 2005-09-02 16:39:00 +00:00
yatephone.h Separated check for maximum running threads as canRoute() 2005-08-03 02:02:50 +00:00
yateversn.h.in Version related changes. 2005-04-03 21:29:45 +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. Please report bugs at bugs@voip.null.ro

To build Yate the quick way is:
'./configure'
'make'
'make install'


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