Summary: | ASTERISK-26359: [patch] cdr_mysql: fails to use UTC if so instructed | ||
Reporter: | Tzafrir Cohen (tzafrir) | Labels: | |
Date Opened: | 2016-09-12 06:16:34 | Date Closed: | 2016-09-21 17:13:08 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | Addons/cdr_mysql |
Versions: | 13.10.0 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Attachments: | ( 0) cdr_mysql.diff | |
Description: | 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. | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-09-12 06:16:35.328-0500 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]. |