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

[Asterisk Team (JIRA)]

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

Asterisk Team updated ASTERISK-28610:
-------------------------------------

    Assignee: Asterisk Team  (was: Schneur Rosenberg)
      Status: Triage  (was: Waiting for Feedback)

> 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: Asterisk Team
>            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)