Table of Contents
current_iddb_modedb_urldb_tablecurrent_infoneighbor_infoping_intervalping_timeoutnode_timeoutseed_fallback_intervalsync_packet_max_sizeid_colcluster_id_colnode_id_colurl_colstate_colno_ping_retries_colpriority_colsip_addr_colflags_coldescription_colget_nodes(cluster_id)
free_nodes(list)
set_state(cluster_id, state)
check_addr(cluster_id, su)
get_my_id()
send_to(packet, cluster_id, node_id)
send_all(packet, cluster_id)
get_next_hop(cluster_id, node_id)
free_next_hop(next_hop)
register_module(mod_name, cb, auth_check, accept_clusters_ids, no_accept_clusters)
List of Tables
List of Examples
current_id parameterdb_mode parameterdb_url parameterdb_table parametercurrent_info parameterneighbor_info parameterping_interval parameterping_timeout parameternode_timeout parameterseed_fallback_interval parametersync_packet_max_size parameterid_col parametercluster_id_col parameternode_id_col parameterurl_col parameterstate_col parameterno_ping_retries_col parameterpriority_col parametersip_addr_col parameterflags_col parameterdescription_col parameterclusterer_list usageclusterer_list_topology usageclusterer_list_cap usageThe clusterer module is used to organize multiple OpenSIPS instances into groups(clusters) in which the nodes can communicate with each other in order to replicate, share information or perform distributed tasks. The distributed logic is performed either by different modules that use the clusterer interface (i.e. the dialog module can replicate dialogs/profiles, the ratelimit module can share pipes across multiple instances etc.) or at the script level. The clusterer module itself only provides an interface to send/receive BIN packets and get notifications about node availability. It achieves this by internally learning the cluster topology and state of the nodes. Provisioning the nodes within a cluster is done over the database or through the configuration script. The node-related information can be checked and triggered to be reloaded by sending commands over the MI interface.
The topology established by the clusterer module is an overlay of nodes where the "links" represent communication availability at BIN interface level. For this purpose, a probing mechanism is used, consisting of regular pings to all nodes in a cluster for which replies must be received within a given interval. All nodes in the cluster exchange information about the state of their links with other nodes and compute a "routing table" which gives a next hop for each destination. The metric for the shortest path is the number of hops. When there is no direct link to a destination, the BIN packet sent by a module is transparently routed through the cluster.
Note that an OpenSIPS instance can belong to multiple clusters, communicating and establishing the topology separately for each one. In order to provision this in the database or the script, each node has an unique ID at global level, which can be referenced in each cluster.
An OpenSIPS instance can dynamically learn all the nodes in the cluster that are not provisioned in the database. For instances that do not load any node info from the DB, it is enough to define at least one neigbour in the script in order to discover all the cluster components.
The clusterer module also keeps track of the state of the nodes in terms of data synchronization for the functionalities (or "capabilities") implemented on top by other modules. Some capabilities require a full data sync(at OpenSIPS startup or at runtime via MI) from a valid "donor" node in the cluster that has the full data set. Furthermore, a capability can query the clusterer module in order to partition some distributed logic only over the synchronized nodes in the cluster.
Each node in the cluster starts with an empty dataset and tries to find a suitable node to pull data from. In order to help "bootstrap" the cluster, a "seed" node should be defined. This is done by setting the value seed for the flags column in the clusterer table(or the property with the same name in the my_node_info parameter). The seed node will simply fall back to a "synced" state after a configurable interval( seed_fallback_interval parameter). This interval can also be set to 0, in which case the seed node will be considered already synced from startup. Note that configuring a a seed node is required only for capabilities that synchronize data at startup, so check the corresponding modules documentation.
The clusterer module transparently exposes the sip_addr column from the clusterer table(or the property with the same name in the current_info parameter) to the modules on top so check the corresponding modules documentation for the use of this node related information.
The following modules must be loaded before this module:
a database module - if db_mode is 1.
proto_bin module.
The id of the current instance. This parameter must be equal to one of the node_id fields in the database.
No default value. This parameter must be explicitly set to a value greater than zero.
Specifies whether the node information for the current instance, as well as other instances in the cluster, should be loaded from the database or configured in the script(see current_info and neighbor_info). A value of “0” means that DB is not used and the cluster topology in terms of node information will be discovered dynamically at runtime.
Default value is “1”
The database url.
Default value is “NULL”.
Example 1.3. Set db_url parameter
...
modparam("clusterer", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips")
...
The name of the table storing the clustering information.
Default value is “clusterer”.
Node specification similar to the information provided by a row in the clusterer DB table corresponding to the current instance. This parameter can be set multiple times in order to include the current node in multiple clusters.
Parameter format: multiple "prop=value" property definitions separated by ',' where the name of the properties is the same as the DB column names. At least the cluster_id and url properties must be defined.
This parameter is required if db_mode is set to “0” in order to properly advertise information about the current instance in the dynamic node learning process.
Example 1.5. Set current_info parameter
...
modparam("clusterer", "current_info", "cluster_id=1, url=bin:192.168.0.5:5566")
...
Node specification similar to the information provided by a row in the clusterer DB table corresponding to another instance in the cluster. This node will be the entry point in the cluster for the current instance in the dynamic node learning process. This parameter can be set multiple times to define multiple neigbors to connect to (or the same neighbor but in different clusters).
Parameter format: multiple "prop=value" property definitions separated by ',' where the name of the properties is the same as the DB column names. At least the cluster_id, node_id and url properties must be defined.
This parameter should be set at least once if db_mode is set to 0 in order to properly learn the cluster topology. If not set, the only way to learn the node topology is by other nodes connecting to the current instance.
Example 1.6. Set neighbor_info parameter
...
modparam("clusterer", "neighbor_info", "cluster_id=1,node_id=2,url=bin:192.168.0.6:5566")
...
The interval in seconds between regular pings sent to a neighbour node.
Default value is “4”
The time in milliseconds to wait for a reply to a previously sent ping before retrying or considering the link with the neighbour node down. This is also the interval between successive retries if the send fails.
Default value is “1000”
The time in seconds to wait before pinging is restarted for a failed node.
Default value is “60”
Only relevant for "seed" nodes. The time, in seconds, to wait for a suitable donor node before falling back to a "synced" state, following a node restart or an MI cluster sync command. If set to 0, the node is considered as already synced from startup.
Default value is “0”.
Example 1.10. Set seed_fallback_interval parameter
...
modparam("clusterer", "seed_fallback_interval", 10)
...
The maximum size of the BIN packets sent while doing data synchronization. This is only a suggested value as the actual size of the packets may be slightly larger.
Default value is “65535”.
Example 1.11. Set sync_packet_max_size parameter
...
modparam("clusterer", "sync_packet_max_size", 32765)
...
The name of the column storing an id for the table rows.
Default value is “id”.
The name of the column to store the id of a cluster.
Default value is “cluster_id”.
Example 1.13. Set cluster_id_col parameter
...
modparam("clusterer", "cluster_id_col", "cluster_id")
...
The name of the column to store the id of an instance. The values must be greater than 0.
Default value is “node_id”.
The name of the column containing the instance url. The values must be greater than 0.
Default value is “url”.
The name of the column storing the state of the node(enabled/disabled).
Default value is “state”.
The name of the column containing the maximum number of ping retries before the link with the neighbour node is considered down.
Default value is “no_ping_retries”.
Example 1.17. Set no_ping_retries_col parameter
...
modparam("clusterer", "no_ping_retries_col", "no_ping_retries")
...
The name of the column storing the node priority to be chosen as next hop in case of same length(number of hops) paths when rerouting messages.
Default value is “priority”.
The name of the column containing a SIP address for the node.
Default value is “sip_addr”.
The name of the column containing the node flags.
Default value is “flags”.
This function is used to send a generic, request-like message, containing custom data, to a specific node in a cluster, directly from the script. The message is not a "request" per se but according to the logic on the receiving side, that node can send back a reply. In order to correlate a received reply with the request sent out, the function returns, through the tag parameter, a randomly generated communication tag, which is sent along in the the original message, that can be checked against the tag received in a reply.
Meaning of the parameters is as follows:
cluster_id - the cluster ID of the destination node;
dst_id - the ID of the destiantion node;
msg - actual message payload;
tag - randomly generated communication tag. This is an optional output parameter and must be a variable if provided.
The function can return the following values:
1 - successfully sent message to destination node or a valid next hop
-1 - current node is disabled so sending is impossbile
-2 - destination node is not reachable through any path according to the discovered topology
-3 - destination node or valid next hop appear to be reachable but send failed or other OpenSIPS internal error
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, ONREPLY_ROUTE, BRANCH_ROUTE, LOCAL_ROUTE and EVENT_ROUTE.
Example 1.22. cluster_send_req() usage
...
# send a request
cluster_send_req("1", "1", "Check USER: $fU", "$var(req_tag)");
# wait for reply
$avp(filter) = "tag=" + $var(req_tag);
async(wait_for_event("E_CLUSTERER_RPL_RECEIVED", "$avp(filter)", "5"), rpl_resume);
# done
...
route[rpl_resume] {
xlog("Received reply: $avp(msg)\n");
}
...
This function is used to send a generic, reply-like message, containing custom data, to a specific node in a cluster, directly from the script. The message is marked as a "reply" so this function should ony be used for replying to a previously request-like message received. In order for the other node, which initially sent a request, to be able to correlate it with this reply, a communication tag, received along with the request, should be passed to the function.
Meaning of the parameters is as follows:
cluster_id - the cluster ID of the destination node;
dst_id - the ID of the destiantion node;
msg - actual message payload;
tag - communication tag. This is an input parameter and must be a variable.
The function can return the following values:
1 - successfully sent message to destination node or a valid next hop
-1 - current node is disabled so sending is impossbile
-2 - destination node is not reachable through any path according to the discovered topology
-3 - destination node or valid next hop appear to be reachable but send failed or other OpenSIPS internal error
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, ONREPLY_ROUTE, BRANCH_ROUTE, LOCAL_ROUTE and EVENT_ROUTE.
Example 1.23. cluster_send_rpl() usage
...
event_route[E_CLUSTERER_REQ_RECEIVED] {
fetch_event_params("$avp(cl_id);$avp(src_id);$avp(rcv_msg);$avp(rcv_tag)");
...
cluster_send_rpl("$avp(cl_id)", "$avp(src_id)", "$var(my_reply)", "$avp(rcv_tag)");
}
...
This function has a similar behaviour to the cluster_send_req() function with the exception that the message is sent to all the nodes in the specified cluster.
The function can return the following values:
1 - successfully sent message to at least one node;
-1 - current node is disabled so sending is impossbile;
-2 - all nodes in the cluster are unreachable according to the discovered topology;
-3 - send failed for all nodes in the cluster or other OpenSIPS internal error.
The meaning of the parameters is the same as for cluster_send_req().
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, ONREPLY_ROUTE, BRANCH_ROUTE, LOCAL_ROUTE and EVENT_ROUTE.
Example 1.24. cluster_broadcast_req() usage
...
cluster_broadcast_req("$var(cl_id)", "$var(share_data)");
...
This function checks whether the given IP address belongs to one of the nodes in the cluster.
The addr_type parameter can be set in order to select the address of the node that the comparison is made against, with the possible values of:
bin - node's BIN interface listener;
sip - node's DB provisioned SIP address.
The addr_type parameter is optional and the default behaviour is to compare against the SIP address.
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, ONREPLY_ROUTE, BRANCH_ROUTE, LOCAL_ROUTE and EVENT_ROUTE.
Reloads data from the clusterer database. The currently established topology will be lost and the node will rediscover the new topology.
Name: clusterer_reload
Parameters:none
MI FIFO Command Format:
:clusterer_reload _empty_line_
Lists information(node id, URL, link state with that node etc.) about the other nodes in each cluster.
Name: clusterer_list
Parameters:none
MI FIFO Command Format:
:clusterer_list _empty_line_
Example 1.26. clusterer_list usage
$ ./opensipsctl fifo clusterer_list Cluster:: 1 Node:: 4 DB_ID=4 URL=bin:127.0.0.4:7774 Enabled=1 Link_state=Up Next_hop=4 Description=none Node:: 3 DB_ID=3 URL=bin:127.0.0.3:7773 Enabled=1 Link_state=Down Next_hop=4 Description=none Node:: 2 DB_ID=2 URL=bin:127.0.0.2:7772 Enabled=1 Link_state=Probe Next_hop=4 Description=none Cluster:: 2 Node:: 5 DB_ID=5 URL=bin:127.0.0.4:7775 Enabled=1 Link_state=Up Next_hop=5 Description=none
Lists each cluster's topology from the current node's perspective as an adjacency list. A node appears as a neighbour if the link with that node is up.
Note that if a node id appears in multiple clusters, it refers to the same instance that belongs to different clusters, for which it has a different topology.
Name: clusterer_list_topology
Parameters:none
MI FIFO Command Format:
:clusterer_list_topology _empty_line_
Example 1.27. clusterer_list_topology usage
$ ./opensipsctl fifo clusterer_list_topology Cluster:: 1 Node:: 1 Neighbours=4 Node:: 4 Neighbours=1 2 3 Node:: 3 Neighbours=2 4 Node:: 2 Neighbours=3 4 Cluster:: 2 Node:: 1 Neighbours=5 Node:: 5 Neighbours=1
Sets the status(Enabled/Disabled) of the current node in a specified cluster. A disabled node does not send any messages and ignores received ones thus appearing as a failed node in the topology.
Name: clusterer_set_status
Parameters:
cluster_id - indicates the id of the cluster.
status - indicates the new status(0 - Disabled, 1 - Enabled).
MI FIFO Command Format:
:clusterer_set_status: 1 0 _empty_line_
Dispatches a given MI command to be run on a specific node in the cluster.
Name: cluster_send_mi
Parameters:
cluster_id - id of the cluster.
destination - id of the destination node
cmd_name - name of the MI command to be run
the parameters of the MI command to be run - optional or required, depending on the command
MI FIFO Command Format:
:cluster_mi: 1 3 lb_reload _empty_line_
Dispatches a given MI command to be run on all the nodes in a cluster. The command is also executed locally.
Name: cluster_broadcast_mi
Parameters:
cluster_id - id of the cluster.
cmd_name - name of the MI command to be run
the parameters of the MI command to be run - optional or required, depending on the command
MI FIFO Command Format:
:cluster_mi: 1 dr_reload_status partition_5 _empty_line_
Lists the registered capabilities and their states.
Name: clusterer_list_cap
Parameters:none
MI FIFO Command Format:
:clusterer_list_cap _empty_line_
Example 1.28. clusterer_list_cap usage
$ ./opensipsctl fifo clusterer_list_cap Cluster:: 1 Capability:: dialog-dlg-repl State=Ok Capability:: usrloc-contact-repl State=not synced
This event is raised when a generic, request-like, clusterer message is received. This type of message is sent directly from the script and not by an OpenSIPS module.
Parameters:
cluster_id - The cluster ID of the source node.
src_id - The ID of the source node.
msg - The actual message payload.
tag - The communication tag of this message, generated by the source node. This could be used to send a reply corresponding to the received message by providing the tag to the cluster_send_rpl() function.
This event is raised when a generic, reply-like, clusterer message is received. This type of message is sent directly from the script and not by an OpenSIPS module.
Parameters:
cluster_id - The cluster ID of the source node.
src_id - The ID of the source node.
msg - The actual message payload.
tag - The communication tag of this message. This could be used to match the received reply with a request sent with the cluster_send_req() or cluster_broadcast_req() functions.
This section provides an usage example for replicating ratelimit pipes between two OpenSIPS instances. It uses the clusterer module to manage the replicating nodes, and along with the proto_bin module, to send the replicated information.
The setup topology is simple: we have two OpenSIPS nodes running on two separate machines (although they could run on the same machine as well): Node A has IP 192.168.0.5 and Node B has IP 192.168.0.6. Both have, besides the traffic listeners (UDP, TCP, etc.), BIN listeners bound on port 5566. These listeners will be used for the binary communication.
We insert in the the clusterer table the following:
Example 1.29. Example database content - clusterer table
+----+------------+---------+----------------------+-------+-----------------+----------+----------+-------+-------------+ | id | cluster_id | node_id | url | state | no_ping_retries | priority | sip_addr | flags | description | +----+------------+---------+----------------------+-------+-----------------+----------+----------+-------+-------------+ | 10 | 1 | 1 | bin:192.168.0.5:5566 | 1 | 3| 50 | NULL | NULL | Node A | | 20 | 1 | 2 | bin:192.168.0.6:5566 | 1 | 3| 50 | NULL | NULL | Node B | +----+------------+---------+----------------------+-------+-----------------+----------+----------+-------+-------------+
“cluster_id” - identifier of the cluster. All nodes within a group/cluster should have the same id (in our example, both nodes have ID 1). The values must be greater than 0.
“node_id” - identifier of the machine/node so each instance within a cluster should have a different ID. The values must be greater than 0. In our example, Node A will have ID 1, and Node B ID 2.
“url” - address where all the BIN packets for that instance will be sent to.
“state” - state of the node: 1 means Enabled, 0 means Disabled. A disabled node will not send any BIN packets and will drop received ones.
“no_ping_retries” - maximum number of ping retries before the link with a node is considered down.
“priority” - the priority of a node to be chosen as next hop in case of same length(number of hops) paths when rerouting messages; it is not relevant for this two-node topology example.
“sip_addr” - SIP address for the node that is transparently provided to modules; it has no use for the ratelimit module in our example.
“flags” - used to define a seed node; it has no use in our example.
“description” - an opaque value used to describe the node
After provisioning the two nodes in the database, we have to configure the two instances of OpenSIPS. First, we configure Node A:
Example 1.30. Node A configuration
...
listen = bin:192.168.0.5:5566 # bin listener for Node A
loadmodule "proto_bin.so"
loadmodule "clusterer.so"
modparam("clusterer", "db_url", "mysql://opensips@192.168.0.7/opensips")
modparam("clusterer", "current_id", 1) # node_id for Node A
loadmodule "ratelimit.so"
modparam("ratelimit", "pipe_replication_cluster", 1)
...
Similarly, the configuration for Node B is as follows:
Example 1.31. Node B configuration
...
listen = bin:192.168.0.6:5566 # bin listener for Node B
loadmodule "proto_bin.so"
loadmodule "clusterer.so"
# ideally, use the same database for both nodes
modparam("clusterer", "db_url", "mysql://opensips@192.168.0.7/opensips")
modparam("clusterer", "current_id", 2) # node_id for Node B
loadmodule "ratelimit.so"
modparam("ratelimit", "pipe_replication_cluster", 1)
...
Starting the two OpenSIPS instances with the above configurations provides your platform the ability to used shared ratelimit pipes in a very efficient and scalable way.
This function will return a list of all the reachable nodes(if the direct link is down/probing, a path through intermediary nodes is considered) in the specified cluster.
The returned nodes structure:
...
typedef struct clusterer_node {
int node_id;
union sockaddr_union addr;
str sip_addr;
str description;
struct clusterer_node *next;
} clusterer_node_t;
...
Meaning of the parameters is as follows:
int cluster_id - the cluster id
This function will free the lits of nodes returned by get_nodes.
Meaning of the parameters is as follows:
clusterer_node_t *list - list header
This function sets the state(enabled/disabled) of the current node in the specified cluster.
Meaning of the parameters is as follows:
int cluster_id - the cluster id
enum cl_node_state state - the new state; possible values:
STATE_DISABLED
STATE_ENABLED
This function checks if a given address belongs to one of the nodes in the cluster.
Meaning of the parameters is as follows:
int cluster_id - the cluster id
union sockaddr_union* su - socket address
This functon will send the given BIN packet to the specified node in the cluster. If the direct link is down/probing, it will send the packet to an intermediary node if the destination node is reachable through another path in the cluster topology.
Meaning of the parameters is as follows:
bin_packet_t packet - the packet to be sent
int cluster_id - the cluster id
int node_id - the id of the destination node
The function returns one of the following:
CLUSTERER_SEND_SUCCESS - successfully sent packet to destination node or a valid next hop
CLUSTERER_CURR_DISABLED - current node is disabled so sending is impossbile
CLUSTERER_DEST_DOWN - destination node is not reachable through any path according to the discovered topology
CLUSTERER_SEND_ERR - destination node or valid next hop appear to be reachable but send failed
Send the given BIN packet to all the nodes in the specified cluster. The function operates similarly to send_to.
Meaning of the parameters is as follows:
bin_packet_t packet - the packet to be sent
int cluster_id - the cluster id
The function returns one of the following:
CLUSTERER_SEND_SUCCESS - successfully sent packet to at least one node
CLUSTERER_CURR_DISABLED - current node is disabled so sending is impossbile
CLUSTERER_DEST_DOWN - all nodes in the cluster are unreachable according to the discovered topology
CLUSTERER_SEND_ERR - send failed for all nodes in the cluster
This function returns the next hop from the computed shortest path to the given destination node in the specified cluster. This is the node that is the actual destination for the send_to and send_all functions when the direct link with the intended destination is down. The function returns the same structure as get_nodes.
Meaning of the parameters is as follows:
int cluster_id - the cluster id
int node_id - the node id of the destination for which the next hop is returned.
This function will free the next hop returned by get_next_hop.
Meaning of the parameters is as follows:
clusterer_node_t *next_hop - next hop to be freed
This function registers an OpenSIPS module in order to receive BIN packets and cluster notifications. A certain module can accept packets from multiple clusters and provides a single callback function that will be called for each received packet. This function will also be called to notify cluster events like nodes becoming reachable/unreachable.
Meaning of the parameters is as follows:
char *mod_name - module name
clusterer_cb_f cb - callback function
int auth_check - 0 - no check, 1 - for every BIN packet received check if source IP belongs to one of the nodes in the cluster
int* accept_clusters_ids - array of cluster ids from which packets are accepted
int no_accept_clusters - length of accept_clusters_ids array
The callback function prototype:
...
typedef void (*clusterer_cb_f)(enum clusterer_event ev,bin_packet_t *, int packet_type,
struct receive_info *ri, int cluster_id, int src_id, int dest_id);
...
Possble values for the event signaled through ev parameter of the callback funtion:
CLUSTER_RECV_MSG - received BIN message
CLUSTER_ROUTE_FAILED - failed to route a received BIN packet destined for another node in the cluster
CLUSTER_NODE_UP - a node became reachable
CLUSTER_NODE_DOWN - a node became unreachable
Table 3.1. Top contributors by DevScore(1), authored commits(2) and lines added/removed(3)
| Name | DevScore | Commits | Lines ++ | Lines -- | |
|---|---|---|---|---|---|
| 1. | Vlad Patrascu (@rvlad-patrascu) | 227 | 73 | 9121 | 4570 |
| 2. | Liviu Chircu (@liviuchircu) | 45 | 32 | 614 | 434 |
| 3. | Eseanu Marius Cristian (@eseanucristian) | 45 | 10 | 3142 | 534 |
| 4. | Razvan Crainea (@razvancrainea) | 20 | 14 | 308 | 132 |
| 5. | Bogdan-Andrei Iancu (@bogdan-iancu) | 9 | 7 | 59 | 55 |
| 6. | Ionel Cerghit (@ionel-cerghit) | 8 | 2 | 250 | 212 |
| 7. | Fabian Gast (@fgast) | 4 | 2 | 3 | 3 |
| 8. | Gohar Ahmed (@goharahmed) | 3 | 1 | 6 | 5 |
(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
Table 3.2. Most recently active contributors(1) to this module
| Name | Commit Activity | |
|---|---|---|
| 1. | Vlad Patrascu (@rvlad-patrascu) | Jul 2016 - Jan 2021 |
| 2. | Fabian Gast (@fgast) | Nov 2018 - Jul 2020 |
| 3. | Liviu Chircu (@liviuchircu) | Mar 2016 - Jul 2020 |
| 4. | Bogdan-Andrei Iancu (@bogdan-iancu) | Apr 2016 - Jun 2020 |
| 5. | Razvan Crainea (@razvancrainea) | Nov 2015 - Sep 2019 |
| 6. | Gohar Ahmed (@goharahmed) | Mar 2019 - Mar 2019 |
| 7. | Ionel Cerghit (@ionel-cerghit) | Dec 2016 - Dec 2016 |
| 8. | Eseanu Marius Cristian (@eseanucristian) | Jul 2015 - Sep 2015 |
(1) including any documentation-related commits, excluding merge commits
Last edited by: Vlad Patrascu (@rvlad-patrascu), Fabian Gast (@fgast), Liviu Chircu (@liviuchircu), Bogdan-Andrei Iancu (@bogdan-iancu), Razvan Crainea (@razvancrainea), Eseanu Marius Cristian (@eseanucristian).
doc copyrights:
Copyright © 2015-2017 www.opensips-solutions.com