[asterisk-bugs] [JIRA] (ASTERISK-28677) CDR billsec is always 0 for transferred calls

Asterisk Team (JIRA) noreply at issues.asterisk.org
Wed Sep 9 11:16:47 CDT 2020


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

Asterisk Team updated ASTERISK-28677:
-------------------------------------

    Target Release Version/s: 18.0.0

> CDR billsec is always 0 for transferred calls
> ---------------------------------------------
>
>                 Key: ASTERISK-28677
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28677
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General, Channels/chan_sip/Transfers
>    Affects Versions: 13.29.0, 13.30.0, 16.6.1, 16.7.0
>         Environment: Centos 7.7
>            Reporter: Maciej Michno
>            Assignee: George Joseph
>            Severity: Minor
>      Target Release: 13.31.0, 16.8.0, 17.2.0, 18.0.0
>
>         Attachments: cdr.conf, Custom.csv, extensions.conf, full, Master.csv, pg.png, sip.conf, users.conf
>
>
> Hi,
> There is a bug in CDR, starting from Asterisk 13.29.0. Billsec is set to 0 for transferred call.
> Scenario:
> A is calling B.
> B is answering A and blindtransferring call to C.
> Effect:
> Two CDR's entries are created, one for call A to B, and second one for transferred call A to C.
> Second entry is created correctly, with correct duration and billsec for A to C call.
> Duration for the first call is set correctly, but billsec is always 0, no matter of time spended on first call (A to B).
> The same effect is observed in both - database and csv/custom CDR.
> Problem does not occur in previous versions of Asterisk, before 13.29.0 (tested on exactly the same configuration).



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



More information about the asterisk-bugs mailing list