Summary:	ASTERISK-20521: Document CDR behavior on the Asterisk wiki
Reporter:	Matt Jordan (mjordan)	Labels:
Date Opened:	2012-10-05 11:55:18	Date Closed:	2013-03-15 07:52:41
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	CDR/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	CDRs behavior is tricky.  The fact that its tricky causes a lot of people frustration: * Things that people think should work, don't * People report bugs because CDRs either don't capture the information they want, or do something they don't expect * Those issues either get closed out because the behavior is undefined, or they languish in the issue tracker If we aren't going to support certain CDR behavior - because that behavior is by definition undefined - then we should say so on the Asterisk wiki.  The page should provide: * How CDRs work in 'standard' two party calls * How CDRs work in Queues * How CDRs can be manipulated by using various cdr configuration settings * Where CDRs are undefined and why * A concrete statement that only violations to the defined behavior and to cdr settings are candidates for fixing in release branches. * Changes in CDR behavior only occurs in new versions * We will not attempt to change undefined behavior.
Comments:	By: Andrew Latham (lathama) 2012-10-05 13:11:02.684-0500 I have found a lot of old CDR notes in Doxygen that I am double and triple checking.  Confusion is the word... By: Matt Jordan (mjordan) 2012-10-05 13:21:03.974-0500 Agreed. The fact that there are subtle differences in behavior between, for example, Dial and Queue - even when only two parties may be involved - adds to the confusion.  The goal here would be to at least have something written down for future reference. By: Matt Jordan (mjordan) 2013-03-15 07:52:41.876-0500 CDR specification for Asterisk 12 is up on the wiki here: https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification