On Oct 15, 2009 at 02:32, Olle E. Johansson <oej(a)edvina.net> wrote: No, they are completey different. No, the RPC is the generic interface (something similar to MI) and binrpc is one protocol for one "driver" that uses that interface. binrpc is used by the ctl module (similar in its function to mi_datagram+mi_fifo, but it supports unix sockets, udp, tcp and fifo in the same time) and by sercmd (which is the tool used for invoking the rpc from the command line, probably similar to kamunix, but besides supporting udp, tcp and unix sockets, it also have an interactive mode with command completion, history a.s.o) There are 2 "drivers" or transports that implement the RPC interface: the ctl modules (see above) and xmlrpc (to continue the MI analogy, similar to mi_xmlrpc in its function). See http://sip-router.org/docbook/sip-router/branch/master/rpc/ser_rpc.html http://sip-router.org/docbook/sip-router/branch/master/modules/ctl/ctl.html http://sip-router.org/docbook/sip-router/branch/master/modules/xmlrpc/xmlrp… Yes, all the mi commands can now be accessed from the RPC interface (binrpc/ctl/sercmd or xmlrpc + some xmlrpc client). Yes. Yes. For this release and the next one yes. The official plan agreed at the meeting (but seems to be missing in the minutes) is that we will move to RPC and slowly obsolete MIs. This means that any new module that implements a rpcs/management interface _must_ support RPC. It can support MI too, but MI support is optional. Existing MIs can be slowly migrated (if we have volunteers, most of them would be only a few lines of RPC code), but it's something that can wait (one can access them with mi_rpc). No existing MIs will be deleted for at least 2 releases. See http://lists.sip-router.org/pipermail/sr-dev/2009-July/002968.html for the reasons of moving to RPC. Andrei