From: Leif Madsen Date: Tue, 2 Mar 2010 20:51:35 +0000 (+0000) Subject: Update documentation to clarify purpose of unanswered option. X-Git-Tag: 1.4.30-rc3~8 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=19c43ed644c569f908029005d0f284ce839ac9a1;p=thirdparty%2Fasterisk.git Update documentation to clarify purpose of unanswered option. (closes issue #16267) Reported by: elsto Patches: cdr.conf.sample.patch.txt uploaded by lmadsen (license 10) Tested by: davidw, elsto git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@250043 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/configs/cdr.conf.sample b/configs/cdr.conf.sample index 693b280928..5e5ebb0d9c 100644 --- a/configs/cdr.conf.sample +++ b/configs/cdr.conf.sample @@ -21,6 +21,12 @@ ; mode, you will see one CDR, with one of the call targets on one side, and the originating ; channel on the other, and then one CDR for each channel attempted. This may seem ; redundant, but cannot be helped. +; +; In brief, this option controls the reporting of unanswered calls which only have an A +; party. Calls which get offered to an outgoing line, but are unanswered, are still +; logged, and that is the intended behaviour. (It also results in some B side CDRs being +; output, as they have the B side channel as their source channel, and no destination +; channel.) ;unanswered = no ; Define the CDR batch mode, where instead of posting the CDR at the end of