presence/README has:
4.4. pres_refresh_watchers(uri, event, type)
...
* type - it distinguishes between the two different types of events
that can trigger the refresh, depending on its value:
+ 0 - a change in watchers authentication.
+ 1 - a statical update in published state (either through
direct update in db table or by modifying the pidf
manipulation document, if pidf_manipulation parameter is set).
4.5. pres_update_watchers(uri, event)
The function can be used in configuration to triger updates to watchers
status if a change in watchers authorization state occurred (i.e.,
updates of xcap documents change state from pending to active).
then in xcap_server/README there is an example where these two functions
are used:
switch($rm) {
case "PUT":
xcaps_put("$var(uri)", "$hu", "$rb");
if($xcapuri(u=>auid)=~"pres-rules")
{
pres_update_watchers("$var(uri)", "presence");
pres_refresh_watchers("$var(uri)", "presence", 1);
}
exit;
break;
case "GET":
xcaps_get("$var(uri)", "$hu");
exit;
break;
case "DELETE":
xcaps_del("$var(uri)", "$hu");
if($xcapuri(u=>auid)=~"pres-rules")
{
pres_update_watchers("$var(uri)", "presence");
pres_refresh_watchers("$var(uri)", "presence", 1);
}
exit;
break;
}
in PUT and DELETE, why type param value is 1 in pres_refresh_watchers
calls, because xcap operations do not update published state of
presentity?
in DELETE, why pres_update_watchers is called, because xcap delete
cannot change watchers status from pending to active?
-- juha
i have in in-dialog part of config:
if (is_method("NOTIFY")) {
xlog("L_INFO", "Calling set_forward_no_connect()\n");
set_forward_no_connect();
};
xlog("L_INFO", "Routing in-dialog $rm <$ru> from <$fu> to <$du>\n");
t_relay();
i.e., the idea is to avoid trying to set up a new tcp session for
in-dialog notifys. then i restart sip proxy so that all tcp sessions are
dead and issue a publish to presence server that causes in-dialog notify
to be sent to watcher.
as result i get to syslog:
Oct 2 10:43:39 sip /usr/sbin/sip-proxy[14131]: INFO: Calling set_forward_no_connect()
Oct 2 10:43:39 sip /usr/sbin/sip-proxy[14131]: INFO: Routing in-dialog NOTIFY <sip:jh_test_fi@192.98.102.10:5074;transport=tcp> from <sip:test@test.fi> to <sip:192.98.102.10:47339;transport=tcp>
Oct 2 10:43:39 sip /usr/sbin/sip-proxy[14131]: ERROR: tm [../../forward.h:170]: msg_send: ERROR: tcp_send failed
Oct 2 10:43:39 sip /usr/sbin/sip-proxy[14131]: ERROR: tm [t_fwd.c:1381]: ERROR: t_send_branch: sending request on branch 0 failed
what does the error message mean? did tm module try to setup tcp
session even when i have told it not to do it or is tm spitting out the
error messages even when it didn't actually try to send anything?
if the latter, i suggest turning the error messages to debug messages,
since in config i have already accepted the fact that it is ok not to
try to setup new tcp connection if one does not exit.
-- juha
Hello,
for the last versions the alphabetic indexes were not generated - there
were different people doing that in the past, using various self-written
tools. For upcoming version, 3.2.0, I spend some time to structure the
docbook files for modules in order to be easier to get from them the
names for functions, parameters and mi commands.
Therefore, the new wiki system has fresh generated indexes from modules'
documentations. You can find them at:
* http://www.kamailio.org/wiki/alphaindexes:3.2.x:modparameters
* http://www.kamailio.org/wiki/alphaindexes:3.2.x:modfunctions
* http://www.kamailio.org/wiki/alphaindexes:3.2.x:micommands
Being generated from docbook xml files, the indexes contain name, path
to the module in source tree and module name, the last one with link to
html readme file of the module published to kamailio.org site. There is
no link at the moment pointing inside the html readmes to the place
where the item is documented, but each readme has table of content, so
it is easy to spot it.
We have lots lots of modules right now, therefore it was not easy to
check if some parameters, functions or mi commands were not indexed. If
you find some missing, please write back here so we can fix the dockbook
or the indexing tool, depending where the problem is.
Hope the indexes will be helpful for many of you.
Ending the email with another invitation to all of you to port (update
to upcoming v3.2.0) your favorite tutorial from old wiki system
(http://www.kamailio.org/dokuwiki/) and add to the new wiki
(http://www.kamailio.org/wiki/).
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Module: sip-router
Branch: master
Commit: d8a6e606267d2cfd9eaf6343120b7a89046c411f
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=d8a6e60…
Author: Jon Bonilla <manwe(a)aholab.ehu.es>
Committer: Jon Bonilla <manwe(a)aholab.ehu.es>
Date: Sun Oct 2 23:42:00 2011 +0200
mi_xmlrcp: Update dependency in doc.
Acording to the Makefile, libxmlrpc-c3 versions 0.9.10
and 1.06.10-1.06.30 are supported.
Build against version 1.16 fails at the moment.
---
modules_k/mi_xmlrpc/doc/mi_xmlrpc_admin.xml | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/modules_k/mi_xmlrpc/doc/mi_xmlrpc_admin.xml b/modules_k/mi_xmlrpc/doc/mi_xmlrpc_admin.xml
index c521df2..f0d7988 100644
--- a/modules_k/mi_xmlrpc/doc/mi_xmlrpc_admin.xml
+++ b/modules_k/mi_xmlrpc/doc/mi_xmlrpc_admin.xml
@@ -85,12 +85,12 @@
</listitem>
<listitem>
<para>
- <emphasis>libxmlrpc-c3</emphasis> version 0.9.10.
+ <emphasis>libxmlrpc-c3</emphasis> version 0.9.10 or version 1.06.[10-30].
</para>
</listitem>
<listitem>
<para>
- <emphasis>libxmlrpc-c3-dev</emphasis> version 0.9.10.
+ <emphasis>libxmlrpc-c3-dev</emphasis> version 0.9.10 or version 1.06.[10-30].
</para>
</listitem>
</itemizedlist>
@@ -101,8 +101,7 @@
<quote>xmlrpc-c</quote>project
(<ulink url='http://xmlrpc-c.sourceforge.net/'>
http://xmlrpc-c.sourceforge.net/</ulink>). 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!!.
+ to install the library and devel headers from the sources.
</para>
</section>
</section>