[asterisk-bugs] [JIRA] (ASTERISK-26415) cdr: CDR merged to first call on attended transfer

[Ross Beer (JIRA)]

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

Ross Beer edited comment on ASTERISK-26415 at 10/5/16 4:27 AM:
---------------------------------------------------------------

Basically, when performing an attended transfer, the 'dst', 'dcontext', 'lastapp' and 'lastdata' is not updated to the bridged channel.

Please see the attached example of the current CDR output, this is easy to replicate by making an attended transfer and referring the CDR specification you will see that it is incorrect.

Using a physical phone this can be reproduced:

1) Make an inbound call to a handset such as a SNOM
2) Answer the call, place the call on hold
3) Make a third call, talk to the far end
4) Transfer the held call to the far end (hangup on the SNOM)
5) Let the two calls stay connected for 60 seconds
6) Hangup

When looking at the 3 CDR entries you will see that the last record is incorrect.


was (Author: rossbeer):
Basically, when performing an attended transfer, the 'dst', 'dcontext', 'lastapp' and 'lastdata' is not updated to the bridged channel.

Please see the attached example of the current CDR output, this is easy to replicate by making an attended transfer and referring the CDR specification you will see that it is incorrect.


> cdr: CDR merged to first call on attended transfer
> --------------------------------------------------
>
>                 Key: ASTERISK-26415
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26415
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General
>    Affects Versions: 13.11.2, 14.0.1
>         Environment: Fedora 23
>            Reporter: Ross Beer
>            Assignee: Unassigned
>         Attachments: cdr_example.txt
>
>
> When receiving a call to a handset, then placing the call on hold to perform an attended transfer. The resulting CDR is merged with the original CDR.
> For example:
> A -- > B -- > Hold --> Dial Number --> Transfer Call
> The resulting CDR is a single entry with the original call's information. 
> In my opinion, this should create a second CDR for the second call, containing data relating to that call. This should not be merged with the original call.
> This works fine if the transfer context is used for a blind transfer as it's possible to use the /n in a local channel call which does create two CDRs.
> It is possible to split the two CDRs as this is what happens in previous asterisk releases such as 1.8
> Its worth noting that on an attended transfer, the destination channel is updated, however, the 'dst' or the 'lastdata' column isn't updated.



--
This message was sent by Atlassian JIRA
(v6.2#6252)