User Activity

  • Posted a comment on discussion Help on Network Caller ID

    One thing that ncidd should be doing and isn't right now, is waiting for the voice output to finish before moving on. If you'd like to try changing the source code and recompiling you can add one line. In the file server/nciddmodems.c near line 3040 you will find these lines close(a_modem->msgfd); logMsg(LEVEL3, "Sent %d bytes to modem for announcement\n", tcnt); ret = initModem(DLEETX, VOICETRY, a_modem); / <dle><etx> </etx></dle>/ Add this new line after the close() and before logMsg() while (...

  • Posted a comment on discussion Help on Network Caller ID

    I'm most surprised by the line of debug output that reads Sent 216941 bytes to modem for announcement ... I didn't think it would have finished stuffing the voice announcement out to the modem when it locked up. Apparently it's gone on to the next part where it swiches back out of voice mode. I have a pi 3B i can mess up, give me a few days to see if i can get it to do the same thing. I'm still puzzled by the way the log files are incomplete after the reboot.

  • Posted a comment on discussion Help on Network Caller ID

    While you could run ncidd in a window instead of having systemd run it, I'm not sure it will tell us much. We already know it's in the middle of the announcement, reading from a file and writing to USB. The strangest thing in your observations is having no log files from the crash. To run ncidd in a console and see the last logs: type Ctrl + Alt + F1 to get a text console log in ... sudo su - systemctl stop ncidd /usr/sbin/ncidd -D -v 7 There is a way to get the kernel logs to come to you at the...

  • Posted a comment on discussion Help on Network Caller ID

    When you change the ncidd.conf file, you will need to systemctl stop and start it again, there is a watcher mechanism for the ncidd.alias, whitelist and blacklist but not for the configuration file. You might also want to inspect the ncidd.log to make sure it picked up the files you expected.

  • Posted a comment on discussion Help on Network Caller ID

    Thats odd. I tried it with curl and wget and got a large tar file both times : wget https://sourceforge.net/projects/ncid/files/ncid/1.18/ncid-1.18-src.tar.gz ls -l first.ncid-1.18-src.tar.gz ncid-1.18-src.tar.gz -rw-r--r-- 1 attfield 12465235 Sep 2 21:05 first.ncid-1.18-src.tar.gz -rw-r--r-- 1 attfield 12465235 May 10 2025 ncid-1.18-src.tar.gz tar -tf ncid-1.18-src.tar.gz gives the expected list of files.

  • Posted a comment on discussion Help on Network Caller ID

    Given that you have two Raspberries Pi with the same behavior, and given that user space programs are not supposed to cause a reboot, I think you're seeing a driver or kernel problem. You might see the kernel panic error message if you use Ctrl + Alt + F1 to get a text console before running the test again, but I suspect that you are not really interested in debugging the USB driver. I'm presuming that you have installed a prebuilt NCID using apt install, so my next suggestion is to do your own compile...

  • Posted a comment on discussion Help on Network Caller ID

    You might try setting the verbose level to 7 in the ncidd.conf file to get more in the ncidd.log but I think the logs will show that it is getting stuck in the voice announcement. The log files should be up-to-date because close() or fflush() is called after each write. The voice message hangup sequence is: /var/log/ncidd.log "Processing hangup request" set voice options on the modem tell modem to go offhook write to /var/log/cidcall.log and flush tell clients about the call log "Sending file %s,...

  • Modified ticket #60 on Network Caller ID

    Namen aus Adressbuch werden nicht mehr angezeigt

View All

Personal Data

Username:
ed_attfield
Joined:
2006-10-24 23:14:14
Location:
Canada

Projects

This is a list of open source software projects that Ed Attfield is associated with:

Personal Tools