-
* the '''call.preroute''' message that tries to classify the caller in a context
* the '''call.route''' message that tries to map a called number to a string describing the target channel
20 KB (3,110 words) - 10:27, 4 November 2013
-
:*user.auth: bool: Activate handler on the "user.auth" message. Defaults to no
:*user.register: bool: Activate handler on the "user.register" message. Defaults to no
14 KB (2,155 words) - 10:47, 11 January 2014
-
; handlers priority
...modules then you have to pay attention to the priorities of the call.route message handler for each module.
4 KB (539 words) - 13:59, 31 October 2013
-
...setup '''ulimit -n 8096'''. This will setup the number of open files (file handlers) Yate is allowed to use.
; Methods indicated in chan.dtmf message will be intersected with channel capabilities
13 KB (1,916 words) - 09:08, 4 November 2013
-
'''call.preroute''' is a message sent by a module requesting additional information required to route an inc
...reject) the call if the message is processed and the returned value of the message is set to "error" or "-".
773 B (112 words) - 10:46, 21 January 2013
-
...iguration changes) or because of a local account update (an [[user.login]] message).
Since the message should be observed by multiple modules all handlers ''must'' return false.
888 B (114 words) - 11:00, 21 January 2013
-
=== Message handlers ===
... will set the type, format and callsource parameters of the [[call.route]] message. The 'type' parameter will have the value 'record', the 'format' parameter
17 KB (2,660 words) - 08:04, 21 June 2018
-
===Message handlers===
11 KB (1,770 words) - 10:23, 4 November 2013
-
===Message handlers===
9 KB (1,147 words) - 10:13, 4 November 2013
-
== Message handlers ==
...ge sent from ysipchan module and used to generate a [[resource.subscribe]] message
3 KB (456 words) - 09:16, 9 April 2015
-
...an instance of the voicemail.php script is launched and the "call.execute" message is passed to it (even if it didn't install a handler) so it can pick up use
The application then keeps running, installing message handlers, generating messages and keeping the event loop running.<br>
2 KB (408 words) - 15:09, 31 October 2013
-
The following parameters are interpreted in the [[call.cdr]] message:
In the call.route message:
2 KB (302 words) - 11:11, 4 November 2013
-
===CNAM Message parameters===
===LNP Message parameters===
5 KB (700 words) - 10:31, 4 November 2013
-
To mantain the LNP cache the module implements two [[call.route]] message handlers.<br>
Check for '''querylnp=true''' in handled message.
12 KB (1,922 words) - 10:32, 4 November 2013
-
===Message handlers===
Park any call to 2000 to a newly created parking orbit playing message.gsm
1 KB (174 words) - 11:06, 4 November 2013
-
==Message handlers==
The channels are taken from 'id' and 'targetid' parameters of the message.
1 KB (145 words) - 11:08, 4 November 2013
-
; priority: int: Default priority of message handlers, 0 to disable them
; Handler priorities for each message, override priority from [general]
4 KB (575 words) - 11:09, 4 November 2013
-
: - Query for the initial routing message: '''queryroute'''
; This section holds default settings for each of the following message handlers
2 KB (283 words) - 11:10, 4 November 2013
-
Sniffer on will dump the message and his parameters, each on a separated line.
* you can also add extra filters on message params
17 KB (1,082 words) - 13:07, 18 August 2022
-
* install handlers for messages it wants to process
== What handlers to install ==
3 KB (471 words) - 18:55, 10 March 2014