Module: sip-router
Branch: master
Commit: caee2ded8d9b39adcf2f5ad91b05e6646941d8fa
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=caee2de…
Author: Timo Reimann <sr(a)foo-lounge.de>
Committer: Timo Reimann <sr(a)foo-lounge.de>
Date: Thu Apr 26 00:54:25 2012 +0200
acc: Improve grammar and stress non-existence of CDR database storage.
---
modules_k/acc/doc/acc_admin.xml | 10 ++++++++--
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/modules_k/acc/doc/acc_admin.xml b/modules_k/acc/doc/acc_admin.xml
index afb4934..0b84cff 100644
--- a/modules_k/acc/doc/acc_admin.xml
+++ b/modules_k/acc/doc/acc_admin.xml
@@ -322,8 +322,8 @@ if (uri=~"sip:+40") /* calls to Romania */ {
<section>
<title>Overview</title>
<para>
- It is possible to generate and log Call Data Records (CDRs) directly from &kamailio;
- in addition to transaction-based logging. Apart from a basic set of CDR fields which
+ In addition to transaction-based logging, it is possible to generate and log Call Data
+ Records (CDRs) directly from &kamailio;. Apart from a basic set of CDR fields which
are always included (covering start time, end time, and duration), the approach allows
flexible specification of additional fields that should be taken into account using
the configuration script. This is very similar to how transaction-based logging may
@@ -348,6 +348,12 @@ if (uri=~"sip:+40") /* calls to Romania */ {
information given will not be stored in the CDR as they cannot be accessed by the
end of the call when the CDR is logged.
</para>
+
+ <para>
+ Note that CDR generation does not involve any kind of database storage (yet). In order
+ to persist the CDRs into a database you will have to set up an exterior process (i.e.,
+ a script living outside of &kamailio;) and implement the storage task yourself.
+ </para>
</section>
<section id="cdr-extra-id">
<title>CDR Extra</title>
Hello,
few hours ago the bug tracker was hit by spammer. It was a valid user
created on the system, via web, ' shiwe' - I deleted it (account email
was a gmail), meanwhile notification flooding stopped.
I'm not sure there will be a way to prevent in the future such people to
create accounts, since registration is over web, with confirmation via
email. If people here have suggestions, just reply here.
Hope the flooding was not too annoying for you.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#221 - nelson
User who did this - sip-router admin (admin)
Reason for closing: Not a bug
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=221
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#224 - Tyler
User who did this - sip-router admin (admin)
Reason for closing: Not a bug
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=224
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi guys,
Out of curiosity, is there actually a wiki page describing the project
policies for new developers, e.g. that git commit messages should have
the module type/name as first element in the first line etc?
Andreas
Hello all,
I'm happy to announce a new developer for the project: Richard Fuchs.
Welcome to the development team!
Richard is working at Sipwise for over 4 years now and has already
contributed many new features and bug fixes for our kamailio packages.
Among those are the period matching in tmrec module, r-uri matching in
lcr module and some IPv6 patches.
He's also the brain behind most of the C based applications you can find
in the Sipwise platforms, like the ngcp-mediaproxy-ng etc.
Best regards,
Andreas
Hello,
from a thread in sip-router user mailing list:
http://lists.sip-router.org/pipermail/sr-users/2012-March/072657.html
This thread talks about reloading lua scripts in runtime context.
>>/ I'm starting to play with lua scripting in Kamailio. It's really cool,
/>>/ some complex stuff in the script becomes really easy this way. The
/>>/ script is becoming quite big, therefore I'd like to use lua_run
/>>/ instead of lua_dofile. My doubt is pretty basic: if i load a script
/>>/ in memory at startup via the "load" parameter and the script is
/>>/ modifed afterwards, is there any way to reload the module so the
/>>/ script is reread?
/>the two contexts created by app_lua were designed one for loading at
>startup and the other for reloading every time. Reloading on demand at
>runtime is not possible. I thought of checking the timestamp of the
>script, but can be a bit risky if saving on intermediary state during
>updates. The scripts are loaded in each process, sending a mi/rpc
>command will require to do some inter-process signaling. Both doable,
>not in my short term plans, though, if someone is contributing, will be
>appreciated.
I have attached a test patch to start playing with this task.
A new function app_lua.runfile is created, and called via sercmd tool to
load some lua script in runtime context.
Some signaling is needed so every kamailio child process would reload
the script too.
Could you give some clues about performing this interprocess signaling
suitably for kamailio?
Best regards,
Vicente.
