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. sync_mode (integer)
1.6. Exported Functions
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. Set sync_mode parameter
1.3. E_PIKE_BLOCKED event
1.4. RabbitMQ socket
1.5. 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 for the Event Interface. It is used to send AMQP messages to a RabbitMQ server each time the Event Interface triggers an event subscribed for.

The AMQP protocol is only used as the transport layer for notifications. The content of a message is presented in the next section.

1.2. RabbitMQ events syntax

The raised events will follow the following grammar:

  • event = event_name (argument '\n')*

  • event_name = non-quoted_string'\n'

  • argument = ((arg_name '::')? arg_value)? | (arg_value)

  • arg_name = not-quoted_string

  • arg_value = not-quoted_string | '"' string '"'

  • not-quoted_string = string - {',",\n,\r}

The event name can contain any non-quoted string character, but it is recommended to follow the syntax: E_MODULE_NAME_EXTRA_NAME

1.3. RabbitMQ socket syntax

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


  • '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'.

  • exchange - exchange of the RabbitMQ server. The default value is ''.

  • 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:

  • No dependencies on other OpenSIPS modules.

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. sync_mode (integer)

Specifies whether an event raise operates synchronous or asynchronous relative to the process where the raise is triggered.In synchronous mode the process waits for the status of the raise from the actual worker process.In asynchronous mode the process continues its operation without receiving any confirmation.

Default value is 0 (asynchronous).

Example 1.2. Set sync_mode parameter

modparam("event_rabbitmq", "sync_mode", 1)

1.6. Exported Functions

No function exported to be used from configuration file.

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.3. E_PIKE_BLOCKED event


Example 1.4. RabbitMQ socket


	# same socket can be written as

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.5. 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:")) {
		xlog("L_ERR","cannot the RabbitMQ server to the E_SIP_MESSAGE event\n");


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

	if (has_totag()) {
		if (loose_route()) {
			if (is_method("INVITE")) {
		} else {
			if ( is_method("ACK") ) {
				if ( t_check_trans() ) {
				} else {
			sl_send_reply("404","Not here");

	if (is_method("CANCEL"))
		if (t_check_trans())


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

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

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

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

	if (is_method("REGISTER"))
		if (!save("location"))


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

	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","m")) {
		switch ($retcode) {
			case -1:
			case -3:
				t_reply("404", "Not Found");
			case -2:
				sl_send_reply("405", "Method Not Allowed");


route[1] {
	if (is_method("INVITE")) {

	if (!t_relay()) {

failure_route[1] {
	if (t_was_cancelled()) {


Chapter 2. Frequently Asked Questions


What is the maximum lenght of a AMQP message?

The maximum length of a datagram event is 16384 bytes.


Where can I find more about OpenSIPS?

Take a look at http://www.opensips.org/.


What is the vhost used by the AMQP server?

Currently, the only vhost supported is '/'.


How can I set a vhost in the socket?

This version doesn't support a different vhost.


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:");

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 */

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.


Where can I find more information about RabbitMQ?

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


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:

E-mails regarding any stable OpenSIPS release should be sent to and e-mails regarding development versions should be sent to .

If you want to keep the mail private, send it to .


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)

 NameDevScoreCommitsLines ++Lines --
1. Razvan Crainea (@razvancrainea)46271873199
2. Liviu Chircu (@liviuchircu)751330
3. Vlad Patrascu (@rvlad-patrascu)741488
4. Ovidiu Sas (@ovidiusas)53357
5. Ionut Ionita (@ionutrazvanionita)425225
6. franklyfox42445
7. Jarrod Baumann (@jarrodb)4222
8. Eric Tamme (@etamme)3112
9. Julián Moreno Patiño3111
10. Vlad Paiu (@vladpaiu)2170

All remaining contributors: Bogdan-Andrei Iancu (@bogdan-iancu).

(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

 NameCommit Activity
1. Liviu Chircu (@liviuchircu)Mar 2014 - Jun 2018
2. Vlad Patrascu (@rvlad-patrascu)Jul 2015 - Jul 2017
3. Razvan Crainea (@razvancrainea)Sep 2011 - Apr 2017
4. Jarrod Baumann (@jarrodb)Apr 2015 - Mar 2016
5. Julián Moreno PatiñoFeb 2016 - Feb 2016
6. Ovidiu Sas (@ovidiusas)Jun 2015 - Jun 2015
7. Eric Tamme (@etamme)May 2015 - May 2015
8. Bogdan-Andrei Iancu (@bogdan-iancu)Oct 2014 - Oct 2014
9. Ionut Ionita (@ionutrazvanionita)Jun 2014 - Jun 2014
10. Vlad Paiu (@vladpaiu)Mar 2014 - Mar 2014

All remaining contributors: franklyfox.

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

Chapter 4. Documentation

4.1. Contributors

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

Documentation Copyrights:

Copyright © 2011 www.opensips-solutions.com