<div dir="ltr"><div>It is what I was thinking. I just wanted to be sure.<br><br></div>Do service providers generally present the CDRs using UTC time or do they adjust them to the customers time zone?<br><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 20 June 2016 at 03:38, Nathan Neulinger <span dir="ltr"><<a href="mailto:nneul@mst.edu" target="_blank">nneul@mst.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">epoch type timestamps are always UTC by definition, it's a universal/exact format.<br>
<br>
-- Nathan<br>
<div><div class="gmail_signature" data-smartmail="gmail_signature"><br>
On 06/19/2016 08:41 PM, vfclists wrote:<br>
><br>
> When I check the relationship between the epochs and the timestamps, eg answer_epoch vs answer_stamp I realize that<br>
> after the daylight saving change the epochs are an hour behind. Is this by design? Are the timestamps supposed to be<br>
> based on the computer's timezone by design, with the epochs based on the UTC value regardless of timezone and daylight<br>
> savings?<br>
><br>
> select<br>
> (julianday('2016-03-30 15:23:00')-2440587.5) * 86400.0, -- 1459351379.999998, answer_epoch is 1459347780<br>
> (julianday('2016-03-30 14:23:00')-2440587.5) * 86400.0, -- 1459347780.000012, value above - 1hr<br>
> (julianday('2016-01-27 11:58:53')-2440587.5) * 86400 --1453895933.000001 - prior to daylight savings<br>
><br>
> The first 2 are from the sqlite CDR and the last from the CSV file.<br>
><br>
><br>
><br>
> --<br>
> Frank Church<br><a href="http://devblog.brahmancreations.com" target="_blank">http://devblog.brahmancreations.com</a></div></div></blockquote></div>
</div></div></div></div>