event_rabbitmq Module
     __________________________________________________________

   Table of Contents

   1. Admin Guide

        1.1. Overview
        1.2. RabbitMQ events syntax
        1.3. RabbitMQ socket syntax
        1.4. Dependencies

              1.4.1. OpenSIPS Modules
              1.4.2. External Libraries or Applications

        1.5. Exported Parameters

              1.5.1. heartbeat (integer)
              1.5.2. connect_timeout (integer)
              1.5.3. use_tls (integer)
              1.5.4. timeout (integer)
              1.5.5. server_id (string)

        1.6. Exported Functions

              1.6.1. rabbitmq_publish(server_id, routing_key,
                      message [, [content_type [, headers,
                      headers_vals]]])

        1.7. Example
        1.8. Installation and Running

              1.8.1. OpenSIPS config file

   2. Frequently Asked Questions
   3. Contributors

        3.1. By Commit Statistics
        3.2. By Commit Activity

   4. Documentation

        4.1. Contributors

   List of Tables

   3.1. Top contributors by DevScore^(1), authored commits^(2) and
          lines added/removed^(3)

   3.2. Most recently active contributors^(1) to this module

   List of Examples

   1.1. Set heartbeat parameter
   1.2. Setting the connect_timeout parameter
   1.3. Set the use_tls parameter
   1.4. Set the timeout parameter
   1.5. Set server_id parameter
   1.6. rabbitmq_publish() function usage
   1.7. E_PIKE_BLOCKED event
   1.8. RabbitMQ socket
   1.9. OpenSIPS config script - sample event_rabbitmq usage
   2.1. Event subscription
   2.2. Event subscription

Chapter 1. Admin Guide

1.1. Overview

   RabbitMQ (http://www.rabbitmq.com/) is an open source messaging
   server. It's purpose is to manage received messages in queues,
   taking advantage of the flexible AMQP protocol.

   This module provides the implementation of a RabbitMQ client
   that supports two primary functionalities:
     * Event-Driven Messaging: It is used to send AMQP messages to
       a RabbitMQ server each time the Event Interface triggers an
       event subscribed for.
     * General Message Publishing: This module also enables
       sending AMQP messages directly to a RabbitMQ server.
       Messages can be easily customized according to the AMQP
       specifications, as well the RabbitMQ extensions.

1.2. RabbitMQ events syntax

   The event payload is formated as a JSON-RPC notification, with
   the event name as the method field and the event parameters as
   the params field.

1.3. RabbitMQ socket syntax

   'rabbitmq:' [user[':'password] '@' host [':' port] '/' [params
   '?'] routing_key

   Meanings:
     * 'rabbitmq:' - informs the Event Interface that the events
       sent to this subscriber should be handled by the
       event_rabbitmq module.
     * user - username used for RabbitMQ server authentication.
       The default value is 'guest'.
     * password - password used for RabbitMQ server
       authentication. The default value is 'guest'.
     * host - host name of the RabbitMQ server.
     * port - port of the RabbitMQ server. The default value is
       '5672'.
     * params - extra parameters specified as key[=value],
       separated by ';':
          + exchange - exchange of the RabbitMQ server. The
            default value is ''.
          + tls_domain - indicates which TLS domain (as defined
            using the tls_mgm module) to use for this connection.
            The use_tls module parameter must be enabled.
          + persistent - indicates that the message should be
            published as persistent delivery_mode=2. This
            parameter does not have a value.
     * routing_key - this is the routing key used by the AMQP
       protocol and it is used to identify the queue where the
       event should be sent.
       NOTE: if the queue does not exist, this module will not try
       to create it.

1.4. Dependencies

1.4.1. OpenSIPS Modules

   The following modules must be loaded before this module:
     * tls_mgm if use_tls is enabled.

1.4.2. External Libraries or Applications

   The following libraries or applications must be installed
   before running OpenSIPS with this module loaded:
     * librabbitmq-dev

1.5. Exported Parameters

1.5.1. heartbeat (integer)

   Enables heartbeat support for the AMQP communication. If the
   client does not receive a heartbeat from server within the
   specified interval, the socket is automatically closed by the
   rabbitmq-client. This prevents OpenSIPS from blocking while
   waiting for a response from a dead rabbitmq-server. The value
   represents the heartbit interval in seconds.

   Default value is “0 (disabled)”.

   Example 1.1. Set heartbeat parameter
...
modparam("event_rabbitmq", "heartbeat", 3)
...

1.5.2. connect_timeout (integer)

   The maximally allowed duration (in milliseconds) for the
   establishment of a TCP connection with a RabbitMQ server.

   Default value is “500” (milliseconds).

   Example 1.2. Setting the connect_timeout parameter
...
modparam("event_rabbitmq", "connect_timeout", 1000)
...

1.5.3. use_tls (integer)

   Setting this parameter will allow you to use TLS for broker
   connections. In order to enable TLS for a specific connection,
   you can use the "tls_domain=dom_name" parameter in the
   configuration specified through the RabbitMQ socket syntax.

   When using this parameter, you must also ensure that tls_mgm is
   loaded and properly configured. Refer to the the module for
   additional info regarding TLS client domains.

   Default value is 0 (not enabled)

   Example 1.3. Set the use_tls parameter
...
modparam("tls_mgm", "client_domain", "rmq")
modparam("tls_mgm", "certificate", "[rmq]/etc/pki/tls/certs/rmq.pem")
modparam("tls_mgm", "private_key", "[rmq]/etc/pki/tls/private/rmq.key")
modparam("tls_mgm", "ca_list",     "[rmq]/etc/pki/tls/certs/ca.pem")
...
modparam("event_rabbitmq", "use_tls", 1)
...

1.5.4. timeout (integer)

   Indicates the timeout (in milliseconds) of any command (i.e.
   publish) sent to the RabbitMQ server.

   NOTE that this parameter is available only starting with
   RabbitMQ library version 0.9.0; setting it when using an
   earlier version will have no effect, and the publish command
   will run in blocking mode.

   Default value is 0 (no timeout - blocking mode)

   Example 1.4. Set the timeout parameter
...
modparam("event_rabbitmq", "timeout", 1000) # timeout after 1s
...

1.5.5. server_id (string)

   Specify configuration for a RabbitMQ server. It contains a set
   of parameters used to customize the connection to the server,
   as well as to the messages sent. The format of the parameter is
   [id_name] param1=value1; param2=value2;. The uri parameter is
   mandatory.

   This parameter can be set multiple times, for each RabbitMQ
   server.

   The following parameters can be used:
     * uri - Mandatory parameter - a full amqp URI as described
       here. Missing fields in the URI will receive default
       values, such as: user: guest, password: guest, host:
       localhost, vhost: /, port: 5672. TLS connections are
       specified using an amqps URI.
     * frames - the maximum size of an AMQP frame. Optional
       parameter, default size is 131072.
     * retries - the number of retries in case a connection is
       down. Optional parameter, default is disabled (do not
       retry).
     * exchange - exchange used to send AMQP messages to. Optional
       parameter, default is "".
     * heartbeat - interval in seconds used to send heartbeat
       messages. Optional parameter, default is disabled.
     * immediate - indicate to the broker that the message MUST be
       delivered to a consumer immediately. Optional parameter,
       default is not immediate.
     * mandatory - indicate to the broker that the message MUST be
       routed to a queue. Optional parameter, default is not
       mandatory.
     * non-persistent - indicates that the message should not be
       persistent in case the RabbitMQ server restarts. Optional
       parameter, default is persistent.
     * tls_domain - indicates which TLS domain (as defined using
       the tls_mgm module) to use for this connection. This must
       be an amqps URI and the use_tls module parameter must be
       enabled.

   Example 1.5. Set server_id parameter
...
# connection to a RabbitMQ server on localhost, default port
modparam("event_rabbitmq", "server_id","[ID1] uri = amqp://127.0.0.1")
...
# connection with a 5 seconds interval for heartbeat messages
modparam("event_rabbitmq", "server_id","[ID2] uri = amqp://127.0.0.1;
heartbeat = 5")
...
# TLS connection
modparam("event_rabbitmq", "server_id","[ID3] uri = amqps://127.0.0.1; t
ls_domain=rmq")
...

1.6. Exported Functions

1.6.1.  rabbitmq_publish(server_id, routing_key, message [,
[content_type [, headers, headers_vals]]])

   Sends a publish message to a RabbitMQ server.

   This function also allows you to attach AMQP headers and values
   in the AMQP message. This is done by specifying a set of
   headers names (in the headers parameter) and the corresponding
   values (in the headers_vals parameter). The number of AVP
   values in the headers must be the same as the one in the
   headers_vals.

   This function can be used from any route.

   The function has the following parameters:
     * server_id (string) - the id of the RabbitMQ server. Must be
       one of the parameters defined in the server_id modparam.
     * routing_key (string) - routing key used to deliver the AMQP
       message.
     * message (string) - the body of the message.
     * content_type (string, optional) - content type of the
       message sent. By default it is none.
     * headers (string, optional) - an AVP containing the names of
       the headers within the AMQP message. If set, headers_vals
       parameter must also be specified.
     * headers_vals (string, optional) - an AVP containing the
       corresponding values of the AMQP headers. If set, headers
       parameter must also be specified.

   Example 1.6. rabbitmq_publish() function usage
        ...
        rabbitmq_publish("ID1", "call", "$fU called $rU");
        ...
        rabbitmq_publish("ID1", "call", "{ \'caller\': \'$fU\',
                                        \'callee\; \'$rU\'", "applicatio
n/json");
        ...
        $avp(hdr_name) = "caller";
        $avp(hdr_value) = $fU;
        $avp(hdr_name) = "callee";
        $avp(hdr_value) = $rU;
        rabbitmq_publish("ID2", "call", $rb, , $avp(hdr_name), $avp(hdr_
value));
        ...

1.7. Example

   This is an example of an event raised by the pike module when
   it decides an ip should be blocked:

   Example 1.7. E_PIKE_BLOCKED event

{
  "jsonrpc": "2.0",
  "method": "E_PIKE_BLOCKED",
  "params": {
    "ip": "192.168.2.11"
  }
}


   Example 1.8. RabbitMQ socket

        rabbitmq:guest:guest@127.0.0.1:5672/pike

        # same socket can be written as
        rabbitmq:127.0.0.1/pike

        # TLS broker connection
        rabbitmq:127.0.0.1/tls_domain=rmq?pike

1.8. Installation and Running

1.8.1. OpenSIPS config file

   This configuration file presents the usage of the
   event_rabbitmq module. In this scenario, a message is sent to a
   RabbitMQ server everytime OpenSIPS receives a MESSAGE request.
   The parameters passed to the server are the R-URI username and
   the message body.

   Example 1.9. OpenSIPS config script - sample event_rabbitmq
   usage
...
loadmodule "signaling.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "uri.so"
loadmodule "acc.so"
loadmodule "event_rabbitmq.so"

startup_route {
        if (!subscribe_event("E_SIP_MESSAGE", "rabbitmq:127.0.0.1/sipmsg
")) {
                xlog("L_ERR","cannot the RabbitMQ server to the E_SIP_ME
SSAGE event\n");
        }
}

route{

        if (!mf_process_maxfwd_header(10)) {
                sl_send_reply(483,"Too Many Hops");
                exit;
        }

        if (has_totag()) {
                if (loose_route()) {
                        if (is_method("INVITE")) {
                                record_route();
                        }
                        route(1);
                } else {
                        if ( is_method("ACK") ) {
                                if ( t_check_trans() ) {
                                        t_relay();
                                        exit;
                                } else {
                                        exit;
                                }
                        }
                        sl_send_reply(404,"Not here");
                }
                exit;
        }

        if (is_method("CANCEL"))
        {
                if (t_check_trans())
                        t_relay();
                exit;
        }

        t_check_trans();

        if (loose_route()) {
                xlog("L_ERR",
                "Attempt to route with preloaded Route's [$fu/$tu/$ru/$c
i]");
                if (!is_method("ACK"))
                        sl_send_reply(403,"Preload Route denied");
                exit;
        }

        if (!is_method("REGISTER|MESSAGE"))
                record_route();

        if (!is_myself("$rd"))
        {
                append_hf("P-hint: outbound\r\n");
                route(1);
        }

        if (is_method("PUBLISH"))
        {
                sl_send_reply(503, "Service Unavailable");
                exit;
        }


        if (is_method("REGISTER"))
        {
                if (!save("location"))
                        sl_reply_error();

                exit;
        }

        if ($rU==NULL) {
                sl_send_reply(484,"Address Incomplete");
                exit;
        }

        if (is_method("MESSAGE")) {
                $avp(attrs) = "user";
                $avp(vals) = $rU;
                $avp(attrs) = "msg";
                $avp(vals) = $rb;
                if (!raise_event("E_SIP_MESSAGE", $avp(attrs), $avp(vals
)))
                        xlog("L_ERR", "cannot raise E_SIP_MESSAGE event\
n");
        }

        if (!lookup("location", "method-filtering")) {
                switch ($retcode) {
                        case -1:
                        case -3:
                                t_newtran();
                                t_reply(404, "Not Found");
                                exit;
                        case -2:
                                sl_send_reply(405, "Method Not Allowed")
;
                                exit;
                }
        }

        route(1);
}


route[1] {
        if (is_method("INVITE")) {
                t_on_failure("1");
        }

        if (!t_relay()) {
                sl_reply_error();
        };
        exit;
}


failure_route[1] {
        if (t_was_cancelled()) {
                exit;
        }
}

...

Chapter 2. Frequently Asked Questions

   2.1.

   What is the maximum lenght of a AMQP message?

   The maximum length of a datagram event is 16384 bytes.

   2.2.

   Where can I find more about OpenSIPS?

   Take a look at https://opensips.org/.

   2.3.

   What is the vhost used by the AMQP server?

   Currently, the only vhost supported is '/'.

   2.4.

   How can I set a vhost in the socket?

   This version doesn't support a different vhost.

   2.5.

   How can I send an event to my RabbitMQ server?

   This module acts as a transport module for the OpenSIPS Event
   Interface. Therefore, this module should follow the Event
   Interface behavior:

   The first step is to subscribe the RabbitMQ server to the
   OpenSIPS Event Interface. This can be done using the
   subscribe_event core function:

   Example 2.1. Event subscription
startup_route {
        subscribe_event("E_RABBITMQ_EVENT", "rabbitmq:127.0.0.1/queue");
}

   The next step is to raise the event from the script, using the
   raise_event core function:

   Example 2.2. Event subscription
route {
        ...
        /* decided that an event should be raised */
        raise_event("E_RABBITMQ_EVENT");
        ...
}

   NOTE that the event used above is only to exemplify the usage
   from the script. Any event published through the OpenSIPS Event
   Interface can be raised using this module.

   2.6.

   Where can I find more information about RabbitMQ?

   You can find more information about RabbitMQ on their official
   website ( http://www.rabbitmq.com/).

   2.7.

   Where can I post a question about this module?

   First at all check if your question was already answered on one
   of our mailing lists:
     * User Mailing List -
       http://lists.opensips.org/cgi-bin/mailman/listinfo/users
     * Developer Mailing List -
       http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

   E-mails regarding any stable OpenSIPS release should be sent to
   <users@lists.opensips.org> and e-mails regarding development
   versions should be sent to <devel@lists.opensips.org>.

   If you want to keep the mail private, send it to
   <users@lists.opensips.org>.

   2.8.

   How can I report a bug?

   Please follow the guidelines provided at:
   https://github.com/OpenSIPS/opensips/issues.

Chapter 3. Contributors

3.1. By Commit Statistics

   Table 3.1. Top contributors by DevScore^(1), authored
   commits^(2) and lines added/removed^(3)
     Name DevScore Commits Lines ++ Lines --
   1. Razvan Crainea (@razvancrainea) 116 77 3598 442
   2. Vlad Patrascu (@rvlad-patrascu) 36 20 1044 412
   3. Alexandra Titoc 27 3 504 1139
   4. Liviu Chircu (@liviuchircu) 16 13 41 76
   5. Ovidiu Sas (@ovidiusas) 15 7 336 290
   6. Maksym Sobolyev (@sobomax) 10 8 21 21
   7. Bogdan-Andrei Iancu (@bogdan-iancu) 6 4 10 10
   8. Peter Lemenkov (@lemenkov) 5 3 2 3
   9. Ionut Ionita (@ionutrazvanionita) 4 2 52 25
   10. franklyfox 4 2 44 5

   All remaining contributors: Jarrod Baumann (@jarrodb), Norman
   Brandinger (@NormB), Eric Tamme (@etamme), Julián Moreno
   Patiño, Ken Rice, Walter Doekes (@wdoekes), Vlad Paiu
   (@vladpaiu).

   (1) DevScore = author_commits + author_lines_added /
   (project_lines_added / project_commits) + author_lines_deleted
   / (project_lines_deleted / project_commits)

   (2) including any documentation-related commits, excluding
   merge commits. Regarding imported patches/code, we do our best
   to count the work on behalf of the proper owner, as per the
   "fix_authors" and "mod_renames" arrays in
   opensips/doc/build-contrib.sh. If you identify any
   patches/commits which do not get properly attributed to you,
   please submit a pull request which extends "fix_authors" and/or
   "mod_renames".

   (3) ignoring whitespace edits, renamed files and auto-generated
   files

3.2. By Commit Activity

   Table 3.2. Most recently active contributors^(1) to this module
                    Name                 Commit Activity
   1.  Razvan Crainea (@razvancrainea) Jan 2017 - Apr 2026
   2.  Norman Brandinger (@NormB)      Apr 2026 - Apr 2026
   3.  Ovidiu Sas (@ovidiusas)         Jun 2015 - Nov 2025
   4.  Ken Rice                        Sep 2025 - Sep 2025
   5.  Alexandra Titoc                 Sep 2024 - Sep 2024
   6.  Vlad Patrascu (@rvlad-patrascu) May 2017 - Jun 2023
   7.  Liviu Chircu (@liviuchircu)     Apr 2018 - May 2023
   8.  Maksym Sobolyev (@sobomax)      Jul 2017 - Feb 2023
   9.  Peter Lemenkov (@lemenkov)      Jun 2018 - Aug 2020
   10. Walter Doekes (@wdoekes)        Apr 2019 - Apr 2019

   All remaining contributors: Bogdan-Andrei Iancu
   (@bogdan-iancu), Jarrod Baumann (@jarrodb), Julián Moreno
   Patiño, Eric Tamme (@etamme), Ionut Ionita
   (@ionutrazvanionita), Vlad Paiu (@vladpaiu), franklyfox.

   (1) including any documentation-related commits, excluding
   merge commits

Chapter 4. Documentation

4.1. Contributors

   Last edited by: Alexandra Titoc, Razvan Crainea
   (@razvancrainea), Liviu Chircu (@liviuchircu), Vlad Patrascu
   (@rvlad-patrascu), Peter Lemenkov (@lemenkov), Ionut Ionita
   (@ionutrazvanionita).

   Documentation Copyrights:

   Copyright © 2011 www.opensips-solutions.com
