Search results

Module mysqldb needs devel packages installed. When Yate is installed at configuration step, normally the libraries needed for MySQL will be corrected detected by ===Configuration file===

Don't forget to check the licensing conditions of the media files or streams used! ===Configuration===

===Enable msgsniff in Yate's main configuration file === * [[Configuration Files]]

...TEAM-MIB] and [http://yate.null.ro/mibs/YATE-MIB.txt YATE-MIB] definitions files (found in the YATE source directory in the ''share/data'' folder). ===Configuration===

...iguration files are text files with a structure similar to the Windows INI files composed of "sections" and "properties".<br> This files can be found in [[Paths and Directories|configuration files directory]]: '''conf.d''' that is in the directory where Yate was build.<br

This module allows writing events and alarms to persistent log files. Apart from that the events in the running instance can be seen through a [ The names of the log files are built by matching the name of the component that generated the event ag

...ki/Call_detail_record CDRs]. CDRs can be collected and output to either '''files''' using [[CDR File Module|cdrfile]], or inserted into a '''database''' usi ...one for the incoming leg and one or more for outgoing leg(s)). There is no configuration file for cdrcombine module. In order to use it set '''combine''' option to

The configuration used for writing this tutorial: You need to modify the configuration files so first locate them on your computer.

...''' directory - this directory specifies the location of the configuration files for YATE or its plugins. ...irectory - directory used for storing shared data (external scripts, audio files, skins for the client)

This example allows chat and short files transfer between Twinkle clients using MESSAGE Request Method. This example explains how to setup chat and short files transfer between Twinkle clients. <br/>

...e source from SVN]] and go to chapter [[#Configuration Files|Configuration Files]]. ** The [http://www.gnu.org/software/autoconf/ autoconf] configuration script builder

... '''listener''', that it is a specific section in [[SIP Configuration File#Configuration File|ysipchan.conf]], that will specify to which network interface Yate wil In [[SIP Configuration File#Configuration File|ysipchan.conf]]:

... preserve Yate's uniformity of the source code. You can find out about the files name conventions or comments style and a few tips for scripts written in PH ===Files organization===

...e modules are not reloaded, only their [[Configuration Files|configuration files]] are read. Also note that some modules have options that are read only on

** The [http://www.gnu.org/software/autoconf/ autoconf] configuration script builder The clean SVN set of sources needs one extra step: you will bootstrap the configuration scripts.

* Yate is installed from SVN source, the needed headers files are obtained in this way ...e's build system with your software package it is recommended to write the files bellow.

:* The [http://www.gnu.org/software/autoconf/ autoconf] configuration script builder. After fetching Yate you will have to run autogen.sh to gene At the end of this stage all Yate binaries and support files are installed in various subdirectories under the /usr/local subdirectory.

:* The [http://www.gnu.org/software/autoconf/ autoconf] configuration script builder. After fetching Yate you will have to run autogen.sh to gene Next step will be to learn more about [[Configuration Files|configuration files]] and the [[modules]] and [[routing]] to configure Yate for your needs.

...on please clean the build and repeat from scratch. Already compiled object files may be good or may be damaged - just stay on the safe side. Yate can be configured by edit files from directory conf.d. Each file has a .sample termination. You have to cre

...oesn't rotate its own logs, but integrates into "logrotate" by providing a configuration file for it. ... will be installed as /etc/logrotate.d/yate/, along with the configuration files for all the other services and programs installed on your system.

* [[Configuration Files]]

|class="yate-header-right"|'''Configuration examples''' * [[Including other files]]

Please do NOT include large log files. Also never include core files - they are useless without the executable that crashed and all its librarie Crashes caused by memory corruptions leave useless core files (since the damage was caused earlier, typically by a different thread). If

* use #include to [[Including other files|include other scripts]] ...QL the configuration file is [[MySQL|mysqldb.conf]] and for PostgreSQL the configuration file is [[PostgreSQL|pgsqldb.conf]].

Reloads module configuration files:

...Yate Client on Windows platforms. You will find where yate's configuration files are located and various command line options to start yate that will help y In this page we assume Yate is installed in the default path: '''c:\Program Files\Yate'''.

===Configuration files for YateClient=== ... cannot be done through the user interface, you can find the configuration files of YateClient inside the YateClient app bundle, in YateClient.app/Contents/

engine.configname (string,readonly) - Name of the master configuration<br/> engine.configpath (string,readonly) - Path to the program config files directory<br/>

...Yate user has his/her own idea of what it means, depending on the existing configuration and the tools they prefer. * [[eventlogs]] - found in /modules/server. Its configuration file is the eventlogs.conf, in the conf.d directory

== Configuration == ; files via #include or #require if no full path is specified

== Configuration == Make sure you don't add this in any of the included files