Skip to content
Snippets Groups Projects
  • Matt Jordan's avatar
    46b2de55
    funcs/func_cdr: Correctly report high precision values for duration and billsec · 46b2de55
    Matt Jordan authored
    When CDRs were refactored, func_cdr's ability to report high precision values
    for duration and billsec (the 'f' option) was broken. This was due to func_cdr
    incorrectly interpreting the duration/billsec values provided by the CDR engine
    in milliseconds, as opposed to seconds. Since the CDR engine only provides
    duration and billsec in seconds, and does not expose either attribute with
    sufficient precision to merely pass back the underlying value, this patch fixes
    the bug by re-calculating duration and billsec with microsecond precision based
    on the start/answer/end times on the CDR.
    
    ASTERISK-25179 #close
    
    Change-Id: I8bc63822b496537a5bf80baf6102c06206bee841
    46b2de55
    History
    funcs/func_cdr: Correctly report high precision values for duration and billsec
    Matt Jordan authored
    When CDRs were refactored, func_cdr's ability to report high precision values
    for duration and billsec (the 'f' option) was broken. This was due to func_cdr
    incorrectly interpreting the duration/billsec values provided by the CDR engine
    in milliseconds, as opposed to seconds. Since the CDR engine only provides
    duration and billsec in seconds, and does not expose either attribute with
    sufficient precision to merely pass back the underlying value, this patch fixes
    the bug by re-calculating duration and billsec with microsecond precision based
    on the start/answer/end times on the CDR.
    
    ASTERISK-25179 #close
    
    Change-Id: I8bc63822b496537a5bf80baf6102c06206bee841
func_cdr.c 20.19 KiB