Copyright © 2011 Marius Bucur
Copyright © 2013 Charles Chance, Sipcentric Ltd.
Table of Contents
dmq_load_api(dmq_api_t* api)
register_dmq_peer(dmq_peer_t* peer)
bcast_message(dmq_peer_t* peer, str* body, dmq_node_t* except,
dmq_resp_cback_t* resp_cback, int max_forwards, str* content_type)
send_message(dmq_peer_t* peer, str* body, dmq_node_t* node,
dmq_resp_cback_t* resp_cback, int max_forwards, str* content_type)
List of Examples
Table of Contents
The DMQ module implements a distributed message queue on top of Kamailio in order to enable the passing/replication of data between multiple instances. The DMQ "nodes" within the system are grouped in a logical entity called the DMQ "bus" and are able to communicate with each other by sending/receiving messages (either by broadcast or directly to a specific node). The system transparently deals with node discovery, consistency, retransmissions, etc.
Other entities ("peers") are then able to utlize the DMQ bus to pass messages between themselves. Peers are grouped by name in order to ensure the correct messages are passed to the relevant peers. This grouping of peers can be compared to a topic in a typical pub/sub system.
The local server address. This is the interface over which the DMQ engine will send/receive messages.
Default value is “NULL”.
Example 1.1. Set server_address
parameter
... modparam("dmq", "server_address", "sip:10.0.0.20:5060") ...
The address of another DMQ node from which the local node should retrieve initial information about all other nodes.
Default value is “NULL”.
Example 1.2. Set notification_address
parameter
... modparam("dmq", "notification_address", "sip:10.0.0.21:5060") ...
The number of worker threads for sending/receiving messages.
Default value is “2”.
Handles a DMQ message by passing it to the appropriate local peer (module). The peer is identified by the user part of the To header.
This function can be used from REQUEST_ROUTE.
Sends a DMQ message directly from config file.
Meaning of parameters:
peer - name of peer that should handle the message.
node - the node to which the message should be sent.
body - the message body.
content_type - the MIME type of the message body.
This function can be used from any route.
Example 1.6. dmq_send_message
usage
... dmq_send_message("peer_name", "sip:10.0.0.21:5060", "Message body...", "text/plain"); ...
Table of Contents
dmq_load_api(dmq_api_t* api)
register_dmq_peer(dmq_peer_t* peer)
bcast_message(dmq_peer_t* peer, str* body, dmq_node_t* except,
dmq_resp_cback_t* resp_cback, int max_forwards, str* content_type)
send_message(dmq_peer_t* peer, str* body, dmq_node_t* node,
dmq_resp_cback_t* resp_cback, int max_forwards, str* content_type)
The module provides the following functions that can be used in other Kamailio modules.
This function binds the DMQ module and fills the structure with the exported functions below.
Example 2.1. dmq_api_t
structure
... typedef struct dmq_api { register_dmq_peer_t register_dmq_peer; bcast_message_t bcast_message; send_message_t send_message; } dmq_api_t; ...
Registers an entity as a DMQ peer which permits receiving/sending messages between nodes which support the same peer.
Broadcast a DMQ message to all nodes in the DMQ bus excluding self, inactive nodes and "except" if specified.