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.
The user may suggest a given channel in the SETUP, but it's not legal for the network to return a non-mandatory ChannelID. See Q.931 Section 5.1.2 (B-channel selection - Originating): The selected B-channel is indicated in the Channel identification information element coded as "channel is indicated, no acceptable alternative" in the first message returned by the network in response to the SETUP message (i.e. a SETUP ACKNOWLEDGE or CALL PROCEEDING message) In an earlier commit I had only fixed SETUP ACK, but missed that this is a more general problem that needs addressing in whatever is the first message containing a channelID yate sends in response to the SETUP.
|2 months ago|
|clients||5 years ago|
|conf.d||10 months ago|
|docs||2 years ago|
|engine||10 months ago|
|libs||2 months ago|
|modules||9 months ago|
|packing||3 years ago|
|share||11 months ago|
|tools||4 years ago|
|windows||1 year ago|
|.cvsignore||15 years ago|
|COPYING||17 years ago|
|ChangeLog||16 years ago|
|Makefile.in||4 years ago|
|README||9 years ago|
|autogen.sh||9 years ago|
|configure.ac||1 year ago|
|main.cpp||9 years ago|
|run.in||3 years ago|
|yate-config.sh||1 year ago|
|yate.pc.in||14 years ago|
|yatecbase.h||9 years ago|
|yateclass.h||10 months ago|
|yateiss.inc.in||15 years ago|
|yatemath.h||7 years ago|
|yatemime.h||9 years ago|
|yatengine.h||1 year ago|
|yatephone.h||12 months ago|
|yateversn.h.in||9 years ago|
|yatewiresniff.h||4 years ago|
|yatexml.h||10 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
- 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 email@example.com
To build Yate the quick way is:
If you are lacking both doxygen and kdoc you will need to install without the
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
Alternatively you can just 'make everything' in the main directory which will
build them all.
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
- SIGUSR1 will gracefully restart a supervised engine
- SIGUSR2 will forcefully restart a supervised engine
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