[Freeswitch-users] Timestamp and timezone issues in CDR, bug or by design?

vfclists vfclists at gmail.com
Mon Jun 20 15:12:34 MSD 2016


It is what I was thinking. I just wanted to be sure.

Do service providers generally present the CDRs using UTC time or do they
adjust them to the customers time zone?

On 20 June 2016 at 03:38, Nathan Neulinger <nneul at mst.edu> wrote:

> epoch type timestamps are always UTC by definition, it's a universal/exact
> format.
>
> -- Nathan
>
> On 06/19/2016 08:41 PM, vfclists wrote:
> >
> > When I check the relationship between the epochs and the timestamps, eg
> answer_epoch vs answer_stamp I realize that
> > after the daylight saving change the epochs are an hour behind. Is this
> by design? Are the timestamps supposed to be
> > based on the computer's timezone by design, with the epochs based on the
> UTC value regardless of timezone and daylight
> > savings?
> >
> > select
> > (julianday('2016-03-30 15:23:00')-2440587.5) * 86400.0, --
> 1459351379.999998, answer_epoch is 1459347780
> >  (julianday('2016-03-30 14:23:00')-2440587.5) * 86400.0, --
> 1459347780.000012, value above - 1hr
> > (julianday('2016-01-27 11:58:53')-2440587.5) * 86400 --1453895933.000001
> - prior to daylight savings
> >
> > The first 2 are from the sqlite CDR and the last from the CSV file.
> >
> >
> >
> > --
> > Frank Church
> http://devblog.brahmancreations.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20160620/7b05cd8e/attachment.html 


Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users mailing list