Mirror of http://yate.null.ro/svn/yate/ with some fixes. We're trying to figure out how to actually submit patches upstream. Meanwhile, collecting them here.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Harald Welte dc005d1fad q931: If we're the network, channelID in SETUP ACK is mandatory 4 months ago
clients Added some larger client icon files. 4 years ago
conf.d Add support for building and running multiple instances of the same script. 5 months ago
docs Added extmodule support to put a script requested debug message in yate output/logging. Added support to change script's debug level and debug name. 1 year ago
engine Warn (single time per loaded file) if a configuration line exceeds internal buffer length. 4 months ago
libs q931: If we're the network, channelID in SETUP ACK is mandatory 4 months ago
modules preserve transfer-capability in Q.931 -> Q.931 calls 4 months ago
packing Added G.722 codec from the WebRTC code. 3 years ago
share Added new function used to escape and concatenate message parameters: old function raises a warning in newer PHP versions. 6 months ago
tools Added support for monitoring services with name other than yate. 4 years ago
windows Bumped version to 6.4.0 release. 11 months ago
.cvsignore Made all YateLocal* to be ignored by SVN/CVS. 15 years ago
COPYING Updated copyright and FSF address. 16 years ago
ChangeLog Bumped version to 1.3.0 15 years ago
Makefile.in Updated files to Rev. 6330. 4 years ago
README Added copyright notices to sources and scripts missing them. 9 years ago
autogen.sh Added copyright notices to sources and scripts missing them. 9 years ago
configure.ac Bumped version to 6.4.1 devel. 11 months ago
main.cpp Added copyright notices to sources and scripts missing them. 9 years ago
run.in Added support for running through the "perf" tool. 3 years ago
yate-config.sh Put path where the library is found before the linked library. 12 months ago
yate.pc.in Added to pkgconfig several custom variables like in yate-config. 14 years ago
yatecbase.h Added copyright notices to sources and scripts missing them. 9 years ago
yateclass.h Implemented NamedCounter method that allows adding a specific value to the counter. 5 months ago
yateiss.inc.in Include code status in installer. 15 years ago
yatemath.h Fixed bug: properly return data pointer when requested offset is not 0. 6 years ago
yatemime.h Added hashing support for MimeSdpBody. 8 years ago
yatengine.h Added support to create arbitrary named lists of shared vars (separate from Engine's global). Added extra functions to shared vars list. Export in javascript. 9 months ago
yatephone.h Added extra parameter used to set relay filter in module install relay. 7 months ago
yateversn.h.in Added copyright notices to sources and scripts missing them. 9 years ago
yatewiresniff.h Update name from wiresniff to yatewiresniff. 4 years ago
yatexml.h Added XPath method used to escape XPath strings. 5 months ago


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