[asterisk-bugs] [JIRA] (ASTERISK-25134) Problem with CDR information with incoming calls

[Rusty Newton (JIRA)]

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

Rusty Newton closed ASTERISK-25134.
-----------------------------------

    Resolution: Suspended

In Asterisk 12 we developed a specification for CDR in Asterisk. Comparing 1.8 to 12 or beyond is not completely useful as there were some big changes.

If you choose to pursue this issue in the future then please compare the behavior to the spec and in a new issue point out where the issue fails to meet the spec. Then provide steps for reproduction of the issue along with full debug logs and corresponding CDR logs.

We need all of that information to examine and investigate the issue. Fixes or changes to CDR are not made lightly as they tend to break more than they fix.


> Problem with CDR information with incoming calls
> ------------------------------------------------
>
>                 Key: ASTERISK-25134
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25134
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/cdr_adaptive_odbc, Functions/func_cdr
>    Affects Versions: 13.3.2
>         Environment: Debian 8.0 Asterisk 13.3.2
>            Reporter: Javier Acosta
>            Assignee: Rusty Newton
>         Attachments: 3_members_queue_incoming_call.txt
>
>
> There is a problem with the CDR information in a incoming call, the Leg-A Channel in the incoming call the information in the Database for the CDR is incorret in the Leg-A (the call disposition is "NO ANSWER" and the billsec and duration is set to 0), in the extension h the DumpChan and NoOp of this variables show the same information.
> In the database the Leg-B that answer the call has duration and billsec bit the others ringing Legs has duration too, the disposition in the Leg-B is correct but no the duration.
> In Asterisk 1.8 the Leg-A disposition is ANSWER and the billsec and duration are correct and the Leg-B is correct in the Database table. I think that maybe there is a bug in the new way to track the CDR information in Asterisk 13.
> Please tell me if that is a bug, in case that is a bug please tell me where to start searching for that bug



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