Module: sems Branch: master Commit: 752e0458b843f44744f81e6a986528a1dad86f18 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sems/?a=commit;h=752e0458b843f44744f81e6a986528a1dad86f18
Author: Stefan Sayer <[email protected]> Committer: Stefan Sayer <[email protected]> Date: Thu Sep 29 14:23:58 2011 +0200 sbc: doc update about CDR generation --- doc/Readme.sbc.txt | 32 ++++++++------------------------ 1 files changed, 8 insertions(+), 24 deletions(-) diff --git a/doc/Readme.sbc.txt b/doc/Readme.sbc.txt index 8e3460d..e7ea570 100644 --- a/doc/Readme.sbc.txt +++ b/doc/Readme.sbc.txt @@ -404,35 +404,19 @@ accounting module. CDR generation -------------- -CDR generation can be enabled with the enable_cdr option. +CDR generation can be enabled with loading a CDR call control module. -For writing CDRs, a separate module is used. This allows to plug several types -of CDR generation modules. The accounting module is selected with the -cdr_module option. - -A syslog_cdr module is available, which writes CDRs to syslog(3) to be processed +The cc_syslog_cdr module writes CDRs to syslog(3) to be processed by standard syslog utils, e.g. syslog-ng. -Available in the CDR are - - A leg local tag - - Call-ID - - From Tag (remote tag A leg) - - To Tag (remote tag B leg) - - start TS - - connect TS (0 if not connected) - - end TS (0 if not connected) - -Additionally, values may be configured in the profile to pass to CDR generation; all -values starting with "cdr_" are passed to the CDR generation. - Example: - enable_cdr=yes - cdr_module=cdr - cdr_Calling-Station-Id=$fU - cdr_Called-Station-Id=$tU - cdr_Sip-From-Tag=$ft + call_control=cdr + cdr_module=syslog_cdr + cdr_Calling-Station-Id=$fU + cdr_Called-Station-Id=$tU + cdr_Sip-From-Tag=$ft -See also syslog_cdr module documentation. +See also cc_syslog_cdr module documentation. Refusing calls -------------- _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
