When the option gencid=1, which it appears to be here, a CID record will be produced on the second RING, since caller ID is expected to come before the second RING on a POTS call.
The timestamp in the record comes from the system clock when ncidd calls gettimeofday(). The same code is used for the timestamps that appear in the ncidd.log file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I checked and my NCIDD system clock is correct, that's why I am confused as to the different call log time reported. I am UTC -4 but the time is off by some unexpected value. Is there a bash command line way to see gettimeofday() for me to check?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are the times in ncidd.log also incorrect, or would it just be wrong for that one call record?
(The code that formats the CID line for the missing caller ID is a bit different fro the other time formatting.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've pulled out the code and tested it by itself. While different from the other places where this is done, it is formatting the time correctly. The time that comes out is timezone shifted from UTC, and will be the same as if ncidd used the 'date' command.
Try comparing the results from 'date' and 'date -u'.
You can throw your own empty test calls into ncidd to check the time by connecting with netcat. e.g. I typed this
~~~
netcat localhost 3333
CALL: ###NMBR6137778888...NAMEtime test+++
GOODBYE
~~~
I sometimes get what I think you call ghost calls. What they are, in my case, are hangup calls where ncidd hungup but the caller side did not hangup, and rings again (actually continuing ringing) with no CID information.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been getting some single ring No Caller ID nuisance calls lately. I am using VOIP with a Grandstream VOIP to POTS device.
ciddata.log just shows
in the log, and NCID records my 4:00am caller as 0104 as the time?
cidcall.log shows
Where does NCIDD get the time stamp from?
The other interesting tidbit is my VOIP provider and my Grandstream VOIP to POTS device log show no callers what-so-ever.
Does anyone have any suggestions or explainations as to what's going on?
In case someone is experiencing a similar issue here's a possible reference to "sip scanner ghost calls"
https://wiki.voip.ms/article/Sip_Scanner_Ghost_Calls
When the option gencid=1, which it appears to be here, a CID record will be produced on the second RING, since caller ID is expected to come before the second RING on a POTS call.
The timestamp in the record comes from the system clock when ncidd calls gettimeofday(). The same code is used for the timestamps that appear in the ncidd.log file.
I checked and my NCIDD system clock is correct, that's why I am confused as to the different call log time reported. I am UTC -4 but the time is off by some unexpected value. Is there a bash command line way to see gettimeofday() for me to check?
Are the times in ncidd.log also incorrect, or would it just be wrong for that one call record?
(The code that formats the CID line for the missing caller ID is a bit different fro the other time formatting.)
The NCIDD times are normally correct. When I get these ghost calls the time stamps are incorrect
I've pulled out the code and tested it by itself. While different from the other places where this is done, it is formatting the time correctly. The time that comes out is timezone shifted from UTC, and will be the same as if ncidd used the 'date' command.
Try comparing the results from 'date' and 'date -u'.
You can throw your own empty test calls into ncidd to check the time by connecting with netcat. e.g. I typed this
~~~
netcat localhost 3333
CALL: ###NMBR6137778888...NAMEtime test+++
GOODBYE
~~~
and got
CID: *DATE*06072024*TIME*1431*LINE*0968*NMBR*6137778888*MESG*NONE*FNMBR*613-777-8888*NTYPE*FIX/CELL*CTRY*CA*LOCA*Ontario*CARI*ON*NAME*time test*I sometimes get what I think you call ghost calls. What they are, in my case, are hangup calls where ncidd hungup but the caller side did not hangup, and rings again (actually continuing ringing) with no CID information.