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 &lt;sr(a)foo-lounge.de&gt; Committer: Timo Reimann &lt;sr(a)foo-lounge.de&gt; 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>