The following modules must be loaded before this module:

The following libraries or applications must be installed before running Kamailio with this module loaded:

Number of worker processes to be started to handle incoming messages from remote applications. If the value is 0, the handling of the incoming message is done by the evapi dispatcher process.

Default value is 1.

...
modparam("evapi", "workers", 2)
...

Local IP and port to listen on for incoming TCP connections.

Default value is "127.0.0.1:8448".

...
modparam("evapi", "bind_addr", "1.2.3.4:8228")
...

Control if messages on the socket (to and from clients) are encapsulated in netstring format.

Default value is 1 (netstring format).

...
modparam("evapi", "netstring_format", 0)
...

The name of the function in the kemi configuration file (embedded scripting language such as Lua, Python, ...) to be executed instead of event_route[...] blocks.

The function receives a string parameter with the name of the event, the values are: 'evapi:connection-new', 'evapi:connection-closed', 'evapi:message-received'.

Default value is 'empty' (no function is executed for events).

...
modparam("evapi", "event_callback", "ksr_evapi_event")
...
-- event callback function implemented in Lua
function ksr_evapi_event(evname)
	KSR.info("===== evapi module triggered event: " .. evname .. "\n");
	return 1;
end
...

Maximum number of clients that can connect to evapi socket.

Default value is 8.

...
modparam("evapi", "max_clients", 4)
...

How many micro-seconds to wait on idle, when no evapi messages are in the processing queue.

Default value is 500 000 (0.5 seconds).

...
modparam("evapi", "wait_idle", 100000)
...

Increase wait_idle by itself till its value becomes initial value multiplied with wait_increase. The increase is done only consecutive cycles without any evapi message. When a new evapi message is received, wait_idle is reset to initial value. If wait_increase is set to 1, then wait_idle is used with its initial value always.

Default value is 3.

...
modparam("evapi", "wait_increase", 1)
...

Relay the event data given as parameter to connected applications.

The format on the network is netstring with evdata payload if netstring_format parameter is set to 1 or bare evdata if netstring_format parameter is set to 0.

The function is passing the task to evapi dispatcher process, therefore the SIP worker process is not blocked. Also, it doesn't wait for any response, therefore the processing of the configuration continues very fast when executing evapi_relay().

This function can be used from ANY_ROUTE.

...
evapi_relay("{ \"event\": \"test\",\n \"data\": { \"fU\": \"$fU\" }\n}");
...

The above example will send the following message over tcp:

...
47:{
 "event": "test",
 "data": { "fU": "test" }
},
...

Relay the event data given as parameter to connected applications. Before evaluating the parameter, the request processing is suspended using tm module (using the t_suspend()/t_continue() framework). The routing of the SIP request can be continued once event_route[evapi:message-received] is triggered. After evapi_async_relay() returns true, no relaying should happen in request_route(), it should be followed by exit;.

The format on the network is netstring with evdata payload if netstring_format parameter is set to 1 or bare evdata if netstring_format parameter is set to 0.

This function can be used from REQUEST_ROUTE.

...
evapi_async_relay("{ \"event\": \"suspend\",\n \"data\":"
        " { \"index\": \"$T(id_index)\", \"label\": \"$T(id_label)\" }\n}");
...

Relay the event data given as parameter to connections that match the tag provided by etag value. The etag can be a variable. For more see evapi_relay() and evapi_set_tag().

...
evapi_multicast("{ \"event\": \"test\",\n \"data\": { \"fU\": \"$fU\" }\n}", "tagx");
...

Async relay the event data given as parameter to connections that match the tag provided by etag value. The etag can be a variable. For more see evapi_async_relay() and evapi_set_tag().

...
evapi_async_multicast("{ \"event\": \"suspend\",\n \"data\":"
    " { \"index\": \"$T(id_index)\", \"label\": \"$T(id_label)\" }\n}", "tagx");
...

Relay the event data given as parameter to the first connection that match the tag provided by etag value. The etag can be a variable. For more see evapi_relay() and evapi_set_tag().

...
evapi_unicast("{ \"event\": \"test\",\n \"data\": { \"fU\": \"$fU\" }\n}", "tagx");
...

Async relay the event data given as parameter to the first connection that match the tag provided by etag value. The etag can be a variable. For more see evapi_async_relay() and evapi_set_tag().

...
evapi_async_unicast("{ \"event\": \"suspend\",\n \"data\":"
    " { \"index\": \"$T(id_index)\", \"label\": \"$T(id_label)\" }\n}", "tagx");
...

Close evapi current client connection.

This function can be used from ANY_ROUTE.

...
event_route[evapi:connection-new] {
  if($evapi(srcaddr)!="127.0.0.1") {
    evapi_close();
    exit;
  }
}
...

Set tag name for current client connection. The parameters has to be a string up to 64 characters. It can also be a variable holding such string.

This function can be used from ANY_ROUTE.

...
event_route[evapi:connection-new] {
  if($evapi(srcaddr)=="127.0.0.1") {
    evapi_set_tag("local");
    exit;
  }
}
...

If defined, the module calls event_route[evapi:connection-new] when a new client is connected.

...
event_route[evapi:connection-new] {
    xlog("new connection from $evapi(srcaddr):$evapi(srcport)\n");
}
...

If defined, the module calls event_route[evapi:connection-closed] when a client connection is closed.

...
event_route[evapi:connection-closed] {
    xlog("connection closed by $evapi(srcaddr):$evapi(srcport)\n");
}
...

If defined, the module calls event_route[evapi:message-received] when a message is received from a client.

...
event_route[evapi:message-received] {
    xlog("received [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n");
}
...