From b838b15702c8f1c5eb87b451737f5c6bbdee519c Mon Sep 17 00:00:00 2001
From: Leif Madsen <leif@leifmadsen.com>
Date: Tue, 2 Mar 2010 20:52:19 +0000
Subject: [PATCH] Merged revisions 250043 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r250043 | lmadsen | 2010-03-02 15:51:35 -0500 (Tue, 02 Mar 2010) | 7 lines
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/trunk@250045 65c4cc65-6c06-0410-ace0-fbb531ad65f3
---
configs/cdr.conf.sample | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/configs/cdr.conf.sample b/configs/cdr.conf.sample
index 0c0413163b..8cfaea9341 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
--
GitLab