Revision: 5926
http://openser.svn.sourceforge.net/openser/?rev=5926&view=rev
Author: miconda
Date: 2009-09-24 18:37:43 +0000 (Thu, 24 Sep 2009)
Log Message:
-----------
- setting of brach flags for sip nat pinging
Modified Paths:
--------------
branches/1.5/etc/kamailio.cfg
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Module: sip-router
Branch: master
Commit: cf593d2fd64bcc6a04526beaa228b028e065d304
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=cf593d2…
Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org>
Committer: Andrei Pelinescu-Onciul <andrei(a)iptel.org>
Date: Thu Sep 24 18:20:54 2009 +0200
mi_rpc: doc update
- async mi commands supported
- added the list of the various rpc mi commands versions (mi,
mi_dg, mi_xmlrpc and mi_fifo).
---
modules/mi_rpc/README | 73 ++++++++++++++++++++++++-----------
modules/mi_rpc/doc/mi_rpc_admin.xml | 37 ++++++++++++++---
2 files changed, 80 insertions(+), 30 deletions(-)
diff --git a/modules/mi_rpc/README b/modules/mi_rpc/README
index d2d0fff..5739c28 100644
--- a/modules/mi_rpc/README
+++ b/modules/mi_rpc/README
@@ -18,55 +18,84 @@ Daniel-Constantin Mierla
1. Admin Guide
- 1.1. Overview
- 1.2. Dependencies
+ 1. Overview
+ 2. Dependencies
- 1.2.1. Kamailio Modules
- 1.2.2. External Libraries or Applications
+ 2.1. Kamailio Modules
+ 2.2. External Libraries or Applications
- 1.3. Exported Parameters
- 1.4. Exported Functions
- 1.5. Exported RPC commands
+ 3. Exported Parameters
+ 4. Exported Functions
+ 5. Exported RPC commands
- 1.5.1. mi
+ 5.1. mi mi_dg mi_fifo mi_xmlrpc
Chapter 1. Admin Guide
-1.1. Overview
+ Table of Contents
+
+ 1. Overview
+ 2. Dependencies
+
+ 2.1. Kamailio Modules
+ 2.2. External Libraries or Applications
+
+ 3. Exported Parameters
+ 4. Exported Functions
+ 5. Exported RPC commands
+
+ 5.1. mi mi_dg mi_fifo mi_xmlrpc
+
+1. Overview
The module exports a RPC command to execute MI commands.
The other way around not implemented (MI command to execute RPC) -- to
- be investigated if worth the effort. Also, execution of asynchronous MI
- command is not yet supported.
+ be investigated if worth the effort.
+
+2. Dependencies
-1.2. Dependencies
+ 2.1. Kamailio Modules
+ 2.2. External Libraries or Applications
-1.2.1. Kamailio Modules
+2.1. Kamailio Modules
The following modules must be loaded before this module:
* No dependencies on other Kamailio modules.
-1.2.2. External Libraries or Applications
+2.2. External Libraries or Applications
The following libraries or applications must be installed before
running Kamailio with this module loaded:
* None.
-1.3. Exported Parameters
+3. Exported Parameters
none
-1.4. Exported Functions
+4. Exported Functions
none
-1.5. Exported RPC commands
+5. Exported RPC commands
+
+ 5.1. mi mi_dg mi_fifo mi_xmlrpc
-1.5.1. mi
+5.1. mi mi_dg mi_fifo mi_xmlrpc
Execute a MI command.
+ Depending on the version (e.g. mi, mi_dg) it formats the output in a
+ similar way to the corresponding kamailio mi module:
+ * mi - uses a special, "pretty" format which generates nicer (more
+ readable) output when used with sercmd.
+ * mi_dg - uses an output format similar to the kamailio mi_datagram
+ module.
+ * mi_fifo - uses an output format similar to the kamailio mi_fifo
+ module.
+ * mi_xmlrpc - uses an output format similar to the kamailio mi_xmlrpc
+ module.
+
Name: mi
Parameters:
@@ -77,8 +106,6 @@ Chapter 1. Admin Guide
Example using 'sercmd':
sercmd> mi uptime
-200 OK
-
-+ Now:: Sun Jun 28 12:45:37 2009
-+ Up since:: Sun Jun 28 12:24:27 2009
-+ Up time:: 1270 [sec]
+Now:: Thu Sep 24 18:17:15 2009
+Up since:: Thu Sep 24 17:35:45 2009
+Up time:: 2490 [sec]
diff --git a/modules/mi_rpc/doc/mi_rpc_admin.xml b/modules/mi_rpc/doc/mi_rpc_admin.xml
index 98b7987..514ddd6 100644
--- a/modules/mi_rpc/doc/mi_rpc_admin.xml
+++ b/modules/mi_rpc/doc/mi_rpc_admin.xml
@@ -20,8 +20,7 @@
</para>
<para>
The other way around not implemented (MI command to execute RPC)
- -- to be investigated if worth the effort. Also, execution of
- asynchronous MI command is not yet supported.
+ -- to be investigated if worth the effort.
</para>
</section>
@@ -69,11 +68,37 @@
<section>
<title>
<function moreinfo="none">mi</function>
+ <function moreinfo="none">mi_dg</function>
+ <function moreinfo="none">mi_fifo</function>
+ <function moreinfo="none">mi_xmlrpc</function>
</title>
<para>
Execute a MI command.
</para>
<para>
+ Depending on the version (e.g. mi, mi_dg) it formats the output in a
+ similar way to the corresponding kamailio mi module:
+ <itemizedlist>
+ <listitem>
+ <function>mi</function> - uses a special, "pretty" format
+ which generates nicer (more readable) output when used with
+ sercmd.
+ </listitem>
+ <listitem>
+ <function>mi_dg</function> - uses an output format similar to
+ the kamailio mi_datagram module.
+ </listitem>
+ <listitem>
+ <function>mi_fifo</function> - uses an output format similar
+ to the kamailio mi_fifo module.
+ </listitem>
+ <listitem>
+ <function>mi_xmlrpc</function> - uses an output format similar
+ to the kamailio mi_xmlrpc module.
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
Name: <emphasis>mi</emphasis>
</para>
<para>Parameters:</para>
@@ -90,11 +115,9 @@
</para>
<programlisting format="linespecific">
sercmd> mi uptime
-200 OK
-
-+ Now:: Sun Jun 28 12:45:37 2009
-+ Up since:: Sun Jun 28 12:24:27 2009
-+ Up time:: 1270 [sec]
+Now:: Thu Sep 24 18:17:15 2009
+Up since:: Thu Sep 24 17:35:45 2009
+Up time:: 2490 [sec]
</programlisting>
</section>
</section>
Hello,
I am not sure if everybody is aware of that, but the sip-router core
has inherited a standalone configuration file parser from SER. The
parser lives in files cfg_parser.[ch] and can be used to parse
configuration files of form:
# comment...
[section]
name1 = value1
name2 = value2
...
The format of section identifiers as well as the format of
configuration values are extensible it can be anything from booleans,
integers, strings, and even more complicated compound formats of your
own.
Two SER modules currently use the parser. The tls module uses it to
parse standalone configuration files with TLS related configuration.
The ldap SER module uses the parser to parse a configuration file that
maps LDAP objects to tables and columns for the database API.
Here is an example of a non-trivial configuration file the parse can parse:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob_plain;f=mo…
Some documentation can be found in file sip_router/cfg_parser.c.
For examples how to use it have a look at the following files:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob;f=modules_…http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob;f=modules/…
Jan.
with latest additions that andrei made to s xmlrpc module, i now managed
to get click-to-dial to work using tm.t_uac_wait.
however, one new issue appeared. each time i call t_uac_wait over
xmlrpc, i get to syslog:
Sep 23 18:06:37 localhost /usr/sbin/sip-proxy[18399]: INFO: Handling XMLRPC POST
from <127.0.0.1>
Sep 23 18:06:37 localhost /usr/sbin/sip-proxy[18399]: WARNING: <core> [tcp_read.
c:969]: WARNING: tcp_receive: handle_io: F_TCPCONN connection marked as bad: 0xb
3399dc8 id 51 refcnt 1
it does not seem to have any effect in operation of t_uac_wait. any
idea why that comes and how to get rid of it?
my xmlrpc_requests route looks like this:
route [xmlrpc_requests] { # Handle XMLRPC requests
xlog("L_INFO", "Handling XMLRPC $rm from <$si>\n");
set_reply_no_connect(); # optional
set_reply_close();
dispatch_rpc();
return;
}
-- juha
here is my current list of open problems:
- this warning needs to go away:
Sep 2 21:00:18 localhost sip-router: WARNING: tm [tm.c:502]: WARNING:
on_sl_reply("stateless_reply"): empty/non existing route
when onreply_route [stateless_reply] exist.
- tm.t_uac_wait over xmlrpc generates warning:
Sep 23 18:06:37 localhost /usr/sbin/sip-proxy[18399]: WARNING: <core> [tcp_read.
c:969]: WARNING: tcp_receive: handle_io: F_TCPCONN connection marked as bad: 0xb
3399dc8 id 51 refcnt 1
- not all processes die on sr restart (waiting it to happen again to get
more info).
-- juha
ps. i hope that i'm not the only user currently testing sr, because i
haven't seen many problems reports from other people? if i am, i need a
plan b.
in k or openser there used to be a local_route block that was executed
for locally generated requests, such as those triggered by t_uac_dlg
mi command.
the question is, what is the equivalent in sr? when issuing, for
example, invite using tm.t_uac_wait, i need to be able to set invite
timeout using t_set_fr() call.
there exists onsend_route, but according to wiki, it does not apply:
This route is executed only when forwarding requests - it is not
executed for replies, retransmissions, or locally generated messages
(e.g. via fifo uac).
-- juha