Copyright © 2006 voice-system.ro
This module implements a xmlrpc server that handles xmlrpc requests and generates xmlrpc responses. When a xmlrpc message is received a default method is executed.
At first, it looks up the MI command. If found it parses the called procedure's parameters into a MI tree and the command is executed. A MI reply tree is returned that is formatted back in xmlrpc. The response is built in two ways - like a string that contains the MI tree nodes information (name, values and attributes) or like an array whose elements are consisted of each MI tree node stored information.
Implementation of mi_xmlrpc module's xmlrpc server is based on Abyss XML-RPC server. Current version of Abyss server "normalizes" CRLF sequence in received XML-RPC strings to LF character, which makes it impossible to pass CRLF sequence from xmlrpc client application to OpenSER modules, such as mi_fifo and pua_mi, that accept requests via MI transport. To overcome this limitation mi_xmlrpc module implements a hack that coverts each LFLF sequence in received XML-RPC strings to CRLF sequence.
Features to be added in the future:
possibility to select the listening IP address
multiple ports per IP address
The following modules must be loaded before this module:
No dependencies on other OpenSER modules.
The following libraries or applications must be installed before running OpenSER with this module loaded:
libxmlrpc-c3 version 0.9.10.
libxmlrpc-c3-dev version 0.9.10.
If libxmlrpc-c3[-dev] package is not available on your system, you may check if packages for your OS are not available on the "xmlrpc-c"project ( http://xmlrpc-c.sourceforge.net/). Otherwise you need to install the library and devel headers from the sources. In both cases, keep in mind to use the 0.9.10 version!!.
The port number used by the XMLRPX server to listen for incoming requests.
The default value is 8080. Ports lower than 1024 are not accepted.
A log file to be used by the internal Abyss html server used by the XMLRPX library.
The default values NONE (no logging).
Given the xmlrpc response specifications that a methodResponse can contain a single params section with a single param section, there is the possibility to choose between a string built response or an array built one.
For a 0 value, a single string parameter will be replied (merging the whole response). For non-0 value, each line from the response will be encoded as an element into an array of strings.
The default option is a string built response (0).
It specifies the maximum length of the buffer used to write in the MI tree node information in order to build the xmlrpc response.
The default value is 8192.
No function exported to be used from configuration file.
This is an example showing the xmlrpc format for the "get_statistics dialog: tm:" MI commad: response.
Example 1-5. XMLRPC request
POST /RPC2 HTTP/1.0 Host: 127.0.0.1 Connection: close User-Agent: OpenSIPg XML_RPC Client Content-Type: text/xml Content-Length: 1000 <?xml version="1.0" ?> <methodCall> <methodName>get_statistics</methodName> <params> <param> <value><string>dialog:</string></value> </param> <param> <value><string>tm:</string></value> </param> </params> </methodCall>
Visit the official site of XMLRPC project at http://xmlrpc-c.sourceforge.net/
Take a look at http://lists.openser.org/.
First at all check if your question was already answered on one of our mailing lists:
User Mailing List - http://lists.openser.org/cgi-bin/mailman/listinfo/users
Developer Mailing List - http://lists.openser.org/cgi-bin/mailman/listinfo/devel
If you want to keep the mail private, send it to
Please follow the guidelines provided at: http://sourceforge.net/tracker/?group_id=139143.