[asterisk-bugs] [JIRA] (ASTERISK-28610) CDR fields in second leg use wrong variables from first leg

[Schneur Rosenberg (JIRA)]

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

Schneur Rosenberg commented on ASTERISK-28610:
----------------------------------------------

I have read the new CDR specs but I dont see my scenerio, also after doing some testing I've realized that I havent reported the problem properly, I saw 2 records and thought they were 2 legs but they were really 2 attempts to dial a outside number through my LCR hence the 2 legs, but my issue is previously when I called in to the system through a outsdide DID and got a disa, the Disa ended up terminating the call to a POTS line, I would get 2 records in the DB, one for the incoming channel that called the disa with the billsecs of the entire call from when the first leg was picked up, and second record would be the number called and the billsec started when the second leg answered, now with the new version of Asterisk it creates only one leg and the billing seconds and duration are for the entire call which makes it imposible for me to bill for those calls because the seconds and the dst are both wrong.



> CDR fields in second leg use wrong variables from first leg
> -----------------------------------------------------------
>
>                 Key: ASTERISK-28610
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28610
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_cdr, Applications/app_dial
>    Affects Versions: 17.0.0
>         Environment: Debian 9
>            Reporter: Schneur Rosenberg
>            Assignee: Schneur Rosenberg
>            Severity: Minor
>
> Hi, I have a platform that when called through a outside DID the caller receives a DISA and can complete a call to a outside line, the system creates 2 legs in the CDR’s one for the incoming channel and one for the dial command to the outside line.
> I recently upgraded from version 11 to 17 and I’ve noticed that the second leg does not store the correct info in the dst , dcontext and channel fields, it copies the data from the original leg instead of using the info from the second leg, and for example if the first leg had the did number in the dst field, then the second field will have the same info and therefore I get almost zero info on the destination of the call besides some hints in the lastdata field, and hence I can’t properly bill for these calls.
> Scott Rosenberg



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