[asterisk-bugs] [JIRA] (ASTERISK-21822) Adaptive CDR Not Written When Call Ends In Blind Transfer

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207495#comment-207495 ] 

Rusty Newton commented on ASTERISK-21822:
-----------------------------------------

Ok. Sounds like this is still undefined behavior for CDR then.  We recommend trying [Channel Event Logging|https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=5242932] as it was created due to these issues with CDR.

I'll copy/paste MJordan's comment from the ASTERISK-21486 issue for other viewer's reference:

{quote}
The behavior of CDRs in transfer scenarios is undefined. As Rusty alluded to, this is for two reasons:

# For a long time, people have disagreed about what CDRs should look like when a transfer occurs. The lack of any clear consensus led the Asterisk development team to the creation of CELs, in which a billing system can determine what should be billed and when.
# The Asterisk bridging core in many ways makes determining what a CDR should look like an incredibly brittle operation. Attempts to change the behavior in CDRs in release branches - particularly in transfer scenarios - led to many regressions. Eventually, the developer community decided that it would no longer attempt to change the behavior of CDRs in release branches.

What does that mean?

# While the behavior may not be desirable, the fact that (a) CDRs have undefined behavior in transfer scenarios, and (b) it is not a change in behavior in a release branch (at least, so far as we cna tell) means we will not address this as a 'bug'.
# Any improvement made to CDR code is already being done for [Asterisk 12|https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification]. In particular, externally initiated transfers (both blind and attended) have been specified. Since the bridging code is being completely redone and the CDR engine is being rewritten, there's no real point in keeping this issue open for the current work (particularly since there are ASTERISK issues tracking all of that work, as noted on the [Bridging Project Page|https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+Bridging+Project].

Finally, you may be able to perform a work around to the current situation by using [ForkCDR|https://wiki.asterisk.org/wiki/display/AST/Asterisk+11+Application_ForkCDR]. This application was written specifically for scenarios in which you want a CDR record and one is not created for you automatically by Asterisk, e.g., in transfer scenarios.

Given all of this, I'm going to close out this issue as "Won't Fix". I understand this may not be ideal, but given all of the above, I don't see this issue being addressed in any release branch of Asterisk.

If, however, it can be determined that the behavior of CDRs changed in a release branch in the scenario described above, we can re-open this issue. If that is the case, please contact a bug marshal in #asterisk-bugs and we'll be happy to do so.
{quote}
                
> Adaptive CDR Not Written When Call Ends In Blind Transfer
> ---------------------------------------------------------
>
>                 Key: ASTERISK-21822
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21822
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/cdr_adaptive_odbc
>    Affects Versions: 11.4.0
>            Reporter: JoshE
>            Assignee: JoshE
>
> When a call ends with a blind transfer, cdr_adaptive isn't written at all.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira