[asterisk-bugs] [JIRA] (ASTERISK-26359) cdr_mysql: fails to use UTC is so istructed

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon Sep 12 06:18:01 CDT 2016


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

Asterisk Team commented on ASTERISK-26359:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> cdr_mysql: fails to use UTC is so istructed
> -------------------------------------------
>
>                 Key: ASTERISK-26359
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26359
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General
>    Affects Versions: 13.10.0
>            Reporter: Tzafrir Cohen
>            Severity: Minor
>         Attachments: cdr_mysql.diff
>
>
> cdr_mysql's default (an odd one, IMHO) is to insert CDR records in the local time zone. That is: if you happen to change the system's time zone, the records become invalid.
> According to the documentation, you can use UTC by setting timezone=UTC in [global] of cdr_mysql.conf (with an older name: usegmtime=yes).
> The problems are:
> 1. The code doesn't parse the option timezone. It's called 'cdrzone'.
> 2. It has no effect (unless in compat mode).
> A patch attached to fix both.



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



More information about the asterisk-bugs mailing list