Search results

... target a ''fork slave'' is created, that generates a ''[[call.execute]]'' message to create the outgoing call leg. * The '''callto''' parameter of the call.execute message must be 'fork'.<br>

; Methods indicated in chan.dtmf message will be intersected with channel capabilities ; in the cleanup queue. Set the limit to zero to disable this check.

The '''chan.startup''' message is sent by channel modules when a new channel is instantiated. ...annot therefore make assumptions about the channel's state at the time the message is received.

... by channel modules when a channel is hung up - typically this is the last message ever seen about that channel. ...annot therefore make assumptions about the channel's state at the time the message is received.

The '''call.drop''' message seems to be emitted by a controlling module (such as rmanager) towards a ch The message seems to have been designed for synchronous processing.

* [[Queues Module|queues]] Queues and distributes incoming calls to operators

; If enabled, an user.auth message will be enqueued to request authentication ; backlog: integer: Maximum length of the queue of pending connections

Calls can also be explicitly picked up from the queue. * '''queue/queuename''' - places the call in the queue named queuename

Sniffer on will dump the message and his parameters, each on a separated line. * you can also add extra filters on message params

Queues notify module has three sections: ... this section configures the status set in resource.notify messages when a queued call status changes;

The '''chan.notify''' message is sent back to a channel driver when a specific event has occurred - usual This message is usually asynchronously queued.

Example: SUBSCRIBE, MESSAGE. For method SUBSCRIBE, you can then set in [[SIP Features Module|sipfeature ; backlog: integer: Maximum length of the queue of pending connections

...nswer is received. Enqueue is done asynchronously. The message is set in a queue and the execution thread continues without waiting for a response. Handlers are message hooks that allow a certain module to receive the message. Each module installs handlers for all the messages it needs to receive.

...echanism for organizing YATE's messages in different queues, identified by message name and some specified filters. In JavaScript a MessageQueue can be created by calling Message.installHook() method.

In order to receive a message you must install a handler. ...d usage of internal Yate's message queue, if you need to handle a specific message, that takes too long to be processed by Yate.

* [[Queues Module|queues]], queue_in.php, queue_out.php - Queues and call distribution to operators ...eration]] message will be emited with a custom "operation" parameter. This message can be handled by a [[javascript]]/external script.

...o generate a message faking a response when a request fails to be sent (in message handler or subsequent failure).<br> Message parameters:

...REQ: The client has send ASP_UP message but it did not received ASP_UP_ACK message from the gateway.<br> ... The client send ASP_ACTIVE message but it did not received ASP_ACTIVE_ACK message from the gateway.<br>

* Message loss detection and sequence control algorithms. * Multi stream message delivery

== Handled message == Message name '''http.request'''.<br>