Search results

In some cases modules haven't been well compiled and you will get a message like "unresolved symb -m pathname Path to modules directory (/usr/local/lib/yate)

... Yate in the install directory (with default paths to configuration files, modules ...). -m pathname Path to modules directory (.\modules)

* [[Modules]]

...bstractization between the SIP protocol and the subscriptions and register modules that implement the above functions in a protocol-independent way. ...ip.generate]] message with method=NOTIFY. resource.notify is sent from the modules that follow the events and decide when notifications should be sent (e.g. [

...abase can be configured in [[Modules#Database_Drivers| mysqldb.conf]] or [[Modules#Database_Drivers|pgsqldb.conf]]<br>

By default Yate loads modules relevant to its current running mode: * all modules from the base module directory

* [[Modules]]

[modules] indicating that the fax module was loaded. If not, check your yate.conf / modules directory (do you have it in a compiled state already?)

* [[Modules]]

* [[Modules]]

; If enabled the performance will grow but parameter altering in external modules

The following modules are required:

When Yate starts you can see a list of modules that are loaded. If PostGreSQL does not appear, you must install the devel ...onf'''. If parameter '''modload''' is disabled, then you have to check in [modules] section that module is enabled.

* [[Modules]]

* [[Modules#Resource_subscribe.2Fnotify_modules|Modules]]

When Yate starts you can see a list of modules that are loaded. If MySQL does not appear, you must install the devel packa ...onf'''. If parameter '''modload''' is disabled, then you have to check in [modules] section that module is enabled.

* [[Modules]]

* [[Modules]]

..., for example to be routed via the register module / the database or other modules.

Cdrbuild module reads messages from other channel modules ([[H323_channel_module|h323chan]], [[SIP_Configuration_File|ysipchan]], [[I ...]]" message. This message is caught by different [[Modules#CDR modules|cdr modules]] that intend to write in different mediums ([[CDR_File_Module#Configuratio

* [[Modules]]

...hould have a priority with a value between module(s) doing LNP and routing modules.<br> ...ould have a priority with a value between module(s) doing CNAM and routing modules.<br>

; From outside (e.g. routing modules) mohs are addressed * [[Modules]]

In routing modules like regexroute.conf: * [[Modules]]

* [[Modules]]

* [[Modules]]

... the next steps to know how to see from Telnet the running global external modules. ...''info''''' - provides more detailed information about each of the running modules (no module name is supported)

* [[Modules]]

* [[Modules]]

These modules can be started from Yate and communicate through pipes to the extmodule.<br You can read more about how modules communicates to Yate engine using the [[External module command flow|extern

[modules] Watch parameter 'handlers' to see which modules saw this message and who handled it.

* [[Modules]]

File "yate.conf" controls the loading of [[Modules|modules]] in Yate.<br> Loading of each module is controlled by the base name of each module in the [modules] section from yate.conf.<br>

* [[Modules]]

Yate allows other modules/external scripts to initiate the sending of arbitrary SIP client transactio ...tion. This option should be used together with [[regfile]] or [[register]] modules.

...st years support for various SS7 protocols was added in Yate. Some of this modules are in the public version of Yate while others aren't. ===Documentation for the public SS7 modules===

* [[Modules]]

There are 4 modules for CDR in Yate: ...ke sure the [[CDR Build Module|cdrbuild]], and [[CDR File Module|cdrfile]] modules are loaded.

* '''gvoice.yate''' – located in modules. This sends DTMF tones at answer time (the “+1” you need to press to an * '''regfile.yate''' – located in modules/server

* '''modules''' directory - this directory specifies the location from where YATE plugin ...'extra modules''' directory - specifies an additional path from where YATE modules should be loaded besides the ''module directory''.

...ly because if one module is changing we don't have to change all the other modules that are dependent, and also because we can debug what's happening much eas ...he flexibility and speed needed. When passed to [[External Module|external modules]] the messages are converted to an escaped string encoding that allows hand

...y implements the basics for writing object oriented, event driven external modules (global or channel) using the PHP language and interpreter. ===Handy hints when writing your own PHP modules===

...ther Yate Python Module. It allows to write YATE modules in PYTHON. PYTHON modules comunicate with YATE core via external protocol or run in python interperte

...handled internally in [[ysipchan]] module or generically in other Yate's [[modules]] or in [[External Module|external scripts]]. You can also generate SIP requests from Yate (from other modules/custom scripts) and they will be sent to a specific party.

...ndle [[xsip.generate]] and send SIP requests of behalf on scripts or other modules.

* '''Yate Modules''' - modules of Yate are equal no matter if they are telephony or routing or anything el The most important aspect of Yate is its message-passing system. Modules are passing around messages among them. This allows us to have a bigger fle

The main component of Yate are messages. Modules are passing around messages between them. This allows us to have a bigger f

'''engine.start''' is a notification message sent by the engine to the modules that have a message handler registered for it and tells them that Yate has

'''engine.init''' is a notification message sent by the engine to the modules that have a message handler registered for it just before calling the initi

'''engine.busy''' is a message used by the engine to check if any of the modules is busy when a graceful restart is requested.