[asterisk-bugs] [JIRA] (ASTERISK-21486) Call answered by a dynamic agent and then SIP transferred to an external number is not written to CDR

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-21486:
----------------------------------------

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.

                
> Call answered by a dynamic agent and then SIP transferred to an external number is not written to CDR
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21486
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21486
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 11.3.0
>         Environment: CentOS 5 64 bit Intel
>            Reporter: David Brillert
>            Assignee: David Brillert
>         Attachments: extensions.conf.txt, Master(1).csv, Master.csv, messages, messages.txt, modules.conf.txt, queues.conf.txt, sip.conf.txt
>
>
> Incoming call to app_queue is answered by an ACD agent is collected by CDR.
> The agent does SIP transfer to an external number and the CDR is not collected.
> This only effects calls to an ACD queue as far as I can tell.
> For example:
> Incoming call to an extension is collected by CDR
> if the extension does SIP transfer to an external number the CDR is collected.
> I'm attaching verbose asterisk messages log with sip set debug on and the Asterisk master.csv file for the broken scenario.

--
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