[asterisk-bugs] [JIRA] (ASTERISK-23493) SIP Attended Transfer CDR record has differing linkedid than associated CDRs from the entire call - conflicts with spec

Rusty Newton (JIRA) noreply at issues.asterisk.org
Wed Mar 19 16:25:19 CDT 2014


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

Rusty Newton reassigned ASTERISK-23493:
---------------------------------------

    Assignee: Matt Jordan  (was: c0rnoTa)

> SIP Attended Transfer CDR record has differing linkedid than associated CDRs from the entire call - conflicts with spec
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23493
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23493
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 12.1.1
>            Reporter: c0rnoTa
>            Assignee: Matt Jordan
>         Attachments: CDR.sql, myDebugLog
>
>
> Attended Transfer CDR as specified in Asterisk 12 CDR specification does not work.
>  Party A calls Party B
>  Party B calls Party C and does an Attended transfer from Party A to Party B
>  CDR has old behavior as in Asterisk 1.4/1.8/11. There is no trace of CDR between Party A to Party C when bridged.



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



More information about the asterisk-bugs mailing list