• int bin_send(union sockaddr_union *detcp_workers core parameter.st) - sends the Binary Packet to a given destination over UDP

• int bin_pop_int(void *info) - retrieve an integer from a received Binary Packet

In order to listen for incoming Binary Packets, a bin: interface must be specified. Its number of listener processes can be tuned with tcp_workers core parameter.

• int bin_init(str *mod_name, int packet_type) - begins the construction of a new Binary Packet

In order to listen for incoming Binary Packets, a bin: interface must be specified. Its number of listener processes can be tuned with tcp_children (default: 8)

   listen = bin:10.0.0.150:5062
   ...
   loadmodule "proto_bin.so"

Examples of cluster-enabled modules which use the binary interface are dialog and usrloc, as they can now replicate all run-time events (creation/updating/deletion of dialogs/contacts) to one or more OpenSIPS instances. Configuration can be done as follows:

   modparam("dialog", "dialog_replication_cluster", 1)
   modparam("dialog", "profile_replication_cluster", 2)
   ...
   modparam("usrloc", "location_cluster", 2)

More details can be found in the dialog and usrloc documentation pages.

• int bin_register_cb(char *mod_name, void (*)(int packet_type))

• int bin_pop_str(str *info) - retrieve a string from a received Binary Packet
• int bin_pop_int(void *info) - retrive an integer from a received Binary Packet

Documentation -> Manuals -> Manual 3.5 -> Binary Internal Interface

(:title Binary Internal Interface - 3.5:)

(:allVersions Interface-Binary 3.5:)

The Binary Internal Interface is an OpenSIPS core interface which offers an efficient way for communication between individual OpenSIPS instances. This is especially useful in scenarios where realtime data (such as dialogs) cannot be simply stored in a database anymore, because failover would require entire minutes to complete. This issue can be solved with the new internal binary interface by replicating all the events related to the runtime data (creation / updating / deletion) to a backup OpenSIPS instance.

Configuring the Binary Internal Interface listeners

In order to listen for incoming Binary Packets, an interface must be specified using the bin_listen global script parameter. The number of listener processes can be tuned with the optional bin_children (default: 1)

   bin_listen = 10.0.0.150:5062
   bin_children = 2

Currently, dialog and usrloc are the first modules to make use of this interface, and they can now replicate all run-time events (creation/updating/deletion of dialogs/contacts) to one or more OpenSIPS instances. Configuration can be done as follows:

   modparam("dialog", "accept_replicated_dialogs", 1)
   modparam("dialog", "replicate_dialogs_to", "78.46.64.50:5062")

More details can be found in the dialog and usrloc documentation pages.

C Interface Overview (for module developers)

The interface allows the module writer to build and send compact Binary Packets in an intuitive way.

In order to send packets, the interface provides the following primitives:

• int bin_init(str *mod_name, int packet_type) - begins the contruction of a new Binary Packet
• int bin_push_str(const str *info) - add a string to the Binary Packet that is currently being built
• int bin_push_int(int info) - add an integer to the Binary Packet that is currently being built
• int bin_send(union sockaddr_union *dest) - sends the Binary Packet to a given destination over UDP

In order to receive packets, a module must first register a callback function to the interface:

• int bin_register_cb(char *mod_name, void (*)(int packet_type))

Each time this callback is triggered, the information can be retrieved in the same order it was written using:

• int bin_pop_str(str *info) - retrieve a string from a received Binary Packet
• int bin_pop_int(void *info) - retrive an integer from a received Binary Packet