mirror of
				https://github.com/asterisk/asterisk.git
				synced 2025-10-31 18:55:19 +00:00 
			
		
		
		
	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 ........ ................ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.0@250049 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
		| @@ -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 | ||||
|   | ||||
		Reference in New Issue
	
	Block a user