[asterisk-commits] lmadsen: branch 1.6.1 r250048 - /branches/1.6.1/configs/cdr.conf.sample

[SVN commits to the Asterisk project]

Author: lmadsen
Date: Tue Mar  2 14:53:49 2010
New Revision: 250048

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=250048
Log:
Merged revisions 250045 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
  r250045 | lmadsen | 2010-03-02 15:52:19 -0500 (Tue, 02 Mar 2010) | 15 lines
  
  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
  ........
................

Modified:
    branches/1.6.1/configs/cdr.conf.sample

Modified: branches/1.6.1/configs/cdr.conf.sample
URL: http://svnview.digium.com/svn/asterisk/branches/1.6.1/configs/cdr.conf.sample?view=diff&rev=250048&r1=250047&r2=250048
==============================================================================
--- branches/1.6.1/configs/cdr.conf.sample (original)
+++ branches/1.6.1/configs/cdr.conf.sample Tue Mar  2 14:53:49 2010
@@ -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