[asterisk-bugs] [JIRA] Status Changed to Waiting for Development: (ASTERISK-20521) Document CDR behavior on the Asterisk wiki

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-20521:
-----------------------------------

    Status: Open  (was: Triage)

> Document CDR behavior on the Asterisk wiki
> ------------------------------------------
>
>                 Key: ASTERISK-20521
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20521
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: CDR/General
>            Reporter: Matt Jordan
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira