diff options
author | lmadsen <lmadsen@f38db490-d61c-443f-a65b-d21fe96a405b> | 2010-03-02 20:51:35 +0000 |
---|---|---|
committer | lmadsen <lmadsen@f38db490-d61c-443f-a65b-d21fe96a405b> | 2010-03-02 20:51:35 +0000 |
commit | 499cf105b678ce88d4b35d542558e3880e3edafc (patch) | |
tree | e28cda693f74d59d4ed32901dbd2165a4e09d3fb | |
parent | 0f574f8716d02dc8016955feb44419088320a723 (diff) |
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: http://svn.digium.com/svn/asterisk/branches/1.4@250043 f38db490-d61c-443f-a65b-d21fe96a405b
-rw-r--r-- | configs/cdr.conf.sample | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/configs/cdr.conf.sample b/configs/cdr.conf.sample index 693b28092..5e5ebb0d9 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 |