#17 cidcall.log entries are an hour off

[Anonymous]

Not a biggie but the call timestamp is an hour off.
I've checked and rechecked my timezone and it's correct.
thanks for your help....great application!

My hard drive failed so I've upgraded to the latest version:
Started: 08/12/2019 10:45:53
Server: ncidd (NCID) 1.10.1
API: 1.8 Feature Set 1 2 3 4 5
Sysname: Linux
Nodename: ncid
Machine: x86_64
Release: 5.0.0-23-generic
Version: #24-Ubuntu SMP Mon Jul 29 15:36:44 UTC 2019

RING
CIDINFO: LINEPOTSRING1TIME10:59:43*

DATE = 0812
TIME = 1159
NMBR = 9016516787
NAME = DOE JOHN
calltype=CID hangup=3 hupmode=0 cidline=POTS lineid=POTS
cidline == lineid: check whitelist
Checked Whitelist for match flag=0 ret=1 nmbrmatch=2
Whitelist Match #08: 9016516787 number: 9016516787 name: DOE JOHN
Name or number on the whitelist: skip hangup check
CID: DATE08122019TIME1159LINEPOTSNMBR9016516787MESGNONENAMEDOE JOHN*

[Ed Attfield]

I'm not sure, from what you've written, which time is correct for your location.

The lines you've shown
DATE = 0812
TIME = 1159
come from the phone company with the caller ID NMBR and NAME.

The other times that you are seeing are coming from your computer. Its clock runs in UTC and a time zone offset is applied before it is displayed.

You can check the current time and default time zone on your computer with timedatectl. The timedatectl command is not affected by the TZ variable, while the date command and ncidd are.

e.g. I'm in EDT but I'm using TZ=PDT to change the displayed time zone

+ export TZ=PDT
+ timedatectl
Warning: ignoring the TZ variable, reading the system's timezone setting only.

      Local time: Mon 2019-08-12 21:26:58 EDT
  Universal time: Tue 2019-08-13 01:26:58 UTC
        Timezone: America/Toronto (EDT, -0400)
     NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2019-03-10 01:59:59 EST
                  Sun 2019-03-10 03:00:00 EDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2019-11-03 01:59:59 EDT
                  Sun 2019-11-03 01:00:00 EST
+ date
Tue Aug 13 01:26:59 PDT 2019

ncidd does not have an option for shifting the time that comes from your phone company.

[Anonymous]

CIDINFO: LINEPOTSRING1TIME10:59:43 has the correct time. This reflects my timezone.
yet, when it's written to cidcall.log, an hour is added to the time.
CID: DATE08122019TIME1159LINEPOTSNMBR9016516787MESGNONENAMEDOE JOHN

My guess is the application is using two different methods for the current time.

[Todd Andrews]

The date/time you see in CID: DATE08122019TIME1159 is taken directly from the DATE/TIME from the modem which comes from the phone company. The modem does not report a date/time on each ring so CIDINFO is in real time based on the computer's clock.

Do you have any caller-id devices connected that are capable of showing the date/time? If so, their date/time should match the modem.

[Anonymous]

ok! thanks for the help, yes the modem time is off. I'll call the telephone service.

[Todd Andrews]

Could you let us know what the telephone service says or does? I'm just curious.

[John L. Chmielewski]

The Caller ID time sent by the modem is not correct.