Activity for John L. Chmielewski
-
John L. Chmielewski posted a comment on discussion Open Discussion
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.
-
Hi Chad, A new phonetz.py is available. The attached phonetz.tgz archive contains it. The python3 requirements reduce to python3-phonenumbers, python3-dialog Replace ncid/tools/phonetz.py, build the executable and install it: $ cd <path>/ncid/tools $ tar -xavf <path>/phonetz.tgz $ make clobber phonetz $ sudo cp phonetz /usr/bin/.
-
Hi Chad, Only the 64-bit version of raspios is provided. The 32-bit version needs to be compiled. Surprised you found my script used to build the release. Thanks for the info on changes needed. The python3-pytz was correct until it was depreciated and recently removed. It is still installed so the app install package was built correctly. We need to review and fix the use that pytz provided for ncid. If interested, review pytz_deprecation_shim: Shims to help you safely remove pytz It explains why...
-
This is a good suggestion, but requires a major change of how server blacklist/whitelist code interfaces with the ncid client. It may be implemented in a future release.
-
Ubuntu 22.04.3 build fails: needs libhidapi-dev
-
The INSTALL-DEB section in the website, and also in the source, list the libhidapi-devel package as required From the required section, libhidapi-dev is on the second line as indicated by "-->": The following packages are required: sudo apt install build-essential fakeroot --> sudo apt install libpcre2-dev libhidapi-dev sudo apt install libphonenumber-dev libicu-dev sudo apt install libpcap-dev zstd rename sudo apt install libconfig-simple-perl libdata-hexdump-perl You probably missed it, but thanks...
-
Network Caller ID (NCID) Release 1.16
-
Added tag v1.16 for changeset a46ddda8259b
-
ncid/CHANGES contains the changes.
-
I do not know of anyone doing something similar with ncidd. I am not sure provider filtering is as good as ncidd filtering. It currently uses the fcc list, a fake number script, and a postal code list to detect <city> <state> calls that are mostly SPAM. I have not been following upgrades to provider filtering so it may be a lot better than I remember.</state></city>
-
Building on Debian 12 32-bit (q4od)
-
Problems solved.
-
You need to install libpcap0.8-dev. Refer to INSTALL-DEB (Debian, Raspbian or Ubuntu) in the NCID User Manual for required packages for Ubuntu.
-
Building on Debian 12 32-bit (q4od)
-
Added tag v1.15 for changeset f9aed8bed67a
-
updated VERSION to 1.15 release
-
See doc/CHANGES for 1.15 changes
-
Added tag v1.15 for changeset 104709f6c008
-
NCID Release 1.15
-
Raspberry Pi400 Install help
-
solved
-
I was not clear in my instructions. You should use apt, not dpkg. Apt will use zst and also install any dependent packages. I did verify that apt was able to install ncid-client 1.14 after the zst package was installed. I changed all remaining instances of Raspbian to raspios except when it calls a distribution Raspbian Jessie. I did not find any links for raspios Jessie. Thanks for pointing out that I missed some instances of Raspbian in the user manual. I noticed that Ed already replied about using...
-
I was not clear in my instructions. You should use apt, not dpkg. Apt will use zst and also install any dependent packages. I did verify that apt was able to install ncid-client 1.14 after the zst package was installed. I changed all remaining instances of Raspbian to raspios except when it for calling a distribution Raspbian Jessie. I did not find any links for raspios Jessie. Thanks for pointing out that I missed some instances of Raspbian in the user manual. I noticed that Ed already replied about...
-
After the ncid-client failed, I tried again and got the E: Unsupported error. I then installed zst and continued to get the error instead of it going away. Maybe it's because I am running the 64-bit OS on the Pi400. In any event, if you get the error, you need to clear it, anyway you can. A reinstall will definitely clear it if installing another independent (*_all.deb) package does not clear it. Installing zstd will allow ncid-client to be installed if there is no eror pending from a previous install...
-
Raspberry Pi400 Install help
-
The package was created on a Raspberry Pi 32-bit OS, not the Pi400 running a 64-bit OS. which is what I assume you are running. I do have a NCID package built on the Pi400. The NCID client installs and runs OK. I then tried to install the released client package and got: dpkg-deb: error: archive '/home/jlc/src/ncid/x/ncid-client_1.14-1_all.deb' uses unknown compression for member 'control.tar.zst', giving up dpkg: error processing archive /home/jlc/src/ncid/x/ncid-client_1.14-1_all.deb ( --unpack)...
-
Installation issue with ncid_1.13-1_amd64.deb on Ubuntu 22.04 64-bit
-
The Debian rules make file was modified so build-pkg does not require the symbolic like anymore. Further, build-pkg will build 32-bit or 64-bit binary packages, depending on the OS The new build-pkg will require release 1.15 when it comes out.
-
This release includes the OS release in the binary install files . Previously the version was not listed, but all previous builds were built with the latest version. The installation packages may be able to install under 22.04. A source directory name was changed from Debian to debian and to build the packages debian must be created as a symbolic link to Debian. To be honest, I did not expect any user to try to build packages, I expected the user to just build and install. Attached is the script...
-
NCID Release 1.14
-
Added tag v1.14 for changeset e7e35953e29c
-
See ncid/doc/CHANGES for changes
-
You should be using apt, which also installs dependencies, instead of dpkg, which does not install dependencies. sudo apt install ./ncid_1.13-1_amd64.deb That said, libicu changed the major version, which is why the ncid package is not using it. A new release should be out shortly (final testing), but until then, you can recompile the current release. Just be sure to review DEB Package Install for Debian, Raspbian and Ubuntu and install the compile requirements. Edit: Did not realize I was signed...
-
[Solved] ncid-1.13-1-armhf: Cannot install 'perl:armhf'
-
As the poster noted, the Raspbian distribution is 32 bit. At some point NCID will switch to 64-bit.
-
Server extensions were added in release 1.4. The hangup-calls extension was included in release 1.5. You can upgrade to release 1.5, but as Ed said, you should upgrade to the current supported version. NCID has the current features. Sourceforge has all the NCID releases that were at Sourceforge. If you upgrade to the current release and have problems, we can help, or you can go back to release 1.3, or release 1.5. The Raspberry Pi 4 2B supports 64-bit and the Raspberry Pi OS has a 64-bit distribution....
-
Use HANGUP-CALLS You probably should review the man pages and the user manual: NCID Manual Pages NCID User Manual
-
I tried it on Bullseye 64-bit and ~/.config/autostart was not there. However, it looks like you just need to create ~/.config/autostart. See this reference: https://learn.sparkfun.com/tutorials/how-to-run-a-raspberry-pi-program-on-startup/method-2-autostart After you create ~/.config/autostart, the ncid client can create the autostart file.
-
Thanks for the link to "How to use Autostart - Raspberry Pi OS (Desktop)". It is not something NCID would normally use, but it does seem like it could be useful. Buster has ~/.config/autostart for GUI based applications. Just copy the /usr/share/applications/<app name>.desktop file there and the app will autostart. The ncid client does this for you, plus it can also enable ncid-alert for notifications. As an example, the ncid client copies /usr/share/applications/ncid.desktop to ~/.config/autostart/...
-
ncid-client bug - v1.13-1
-
I am surprised starting from rc.local ever worked. The rc.local file is executed before any users log in, therefore $HOME is undefined, causing ncid to abort. The only way to start ncid in rc.local is to use the --no-gui option, usually with a module. The proper way to autostart ncid is to configure autostart in the File menu: File-->Auto Start->On There are three types of on that you can select. It works with Gnome and should work with other desktops that support ~/config/.autostart. I think that...
-
The *_all.deb packages and the revised source were posted to Sourceforge, as version 1.13-2. The ncid-client package should install for you. Post if there are any problems. The change in the source only effects building DEB files.
-
I removed the install for phone.tz.1.gz in ncid/debian/rules for the client package. The zst compression is from Ubuntu which was built after the Raspberry Pi OS build. The *_all.deb files are the same for both. Did not realize the compression changed only in Ubuntu. Will fix and release shortly. I will post when ncid-client-1.13-2 is released.
-
You should install the official Raspbian Pi OS. The official supported Raspbian Pi OS downloads include 64-bit versions. The NCID armhf and noarch install packages can be used to install NCID. Select the packages you need.
-
Added tag v1.13 for changeset 24809b497674
-
Fixed requirements for ncid in Fedora/ncid.spec
-
NCID Release 1.13
-
Fixed a client dependency problem in Fedora/ncid.spec.
-
Added tag v1.13 for changeset a80ed37308a8
-
Release 1.13
-
Added tag v1.13 for changeset ba3d37aec1b2
-
Changes:
-
NCID Release 1.13
-
No available working CID clients and latest server dep issue
-
The dpkg command does not install dependent packages. Use apt: sudo apt ncid-kpopup_1.12-1_all.deb
-
ncid bug - v1.12-1
-
Fix is accepted and will be in release 1.13
-
ncid-page bug - v1.12-1
-
Fix is accepted and will appear in release 1.13
-
I get the same version of libicu as you. Which version of Raspbian are you using? We assumed it is bullseye.
-
Hi Dan, I assumed you were using Raspbian Bullseye and release 1.12. I downloaded the NCID 1.12 source. on Raspbian Bullseye. Here is how I compiled just ncidd: libcarrier must be installed first when not using the top level Makefile: tar -xzf ncid-1.12-src.tar.gz cd ncid/libcarrier make libcarrier make install The server was compiled next: cd ../server make server The server compiled successfully and ran with no problems using libphonenumber 8. I also rebuilt all the binary packages successfully....
-
Useful-Info
-
Useful-Info
-
A color emojis causes an error in TK, which in turn, causes ncid to fail. Xft emoji support is working to fix the problem: https://gitlab.freedesktop.org/xorg/lib/libxft/-/merge_requests/1 On Thu, Oct 07, 2021 at 02:06:45AM -0000, Ed Attfield wrote: I had noticed much the same thing. Some emojis work fine and some make the ncid client fail. Removing the emoji line from cidcall.log fixes it for a while. [bugs:#46] No available working CID clients and latest server dep issue Status: open Group: v1.0_(example)...
-
No available working CID clients and latest server dep issue
-
The error in ncid is due to an color emoji font. The ncid clients tries to avoid them, but, apparently, not yours. See the bug report I opened and the comments. I included a short script in the bug report to demonstrate the problem: Noto Color Emoji and Noto Emoji fixed fonts cause a X error in a tcl/tk script You can fix the problem by uninstalling the font that causes the error. Do not use dpkg to install ncid. It will not install dependencies. Refer to DEB Package Install for Debian, Raspbian...
-
Useful-Info
-
You need to check your /var/log/ncidd.log file. Here is the important portion of the log file: Modem initialized. Modem Snooping CID (off = 0 on = 1 or 2): 1 Modem set for CallerID and Call Waiting: AT-SCID=1 TTY port changed to ICANON mode. Modem detected Modem used for Caller Not all modems support CID. AT-SCID? should return 1. Here is mincom querying my modem:: at OK at-scid? 1 OK
-
You need to check your /var/log/ncidd.log file. Here is the important portion of the log file: Modem initialized. Modem Snooping CID (off = 0 on = 1 or 2): 1 Modem set for CallerID and Call Waiting: AT-SCID=1 TTY port changed to ICANON mode. Modem detected Modem used for Caller ~~~: Not all modems support CID. AT-SCID? should return 1. Here is mincom querying my modem:: at OK at-scid? 1 OK ~~~
-
Instead of using dpkg -i ./ncid_1.12-1_amd64.deb It is much better to use apt which will pull in dependencies: sudo apt install ./ncid_1.12-1_amd64.deb But that will not fix the libc6 problem. You should be able to compile the source using the installed lib6 library. make ubuntu sudo make ubuntu install Look at the compile requirements in DEB Package Install for Debian, Raspbian and Ubuntu. Don't forget to modify ncid or replace it with your modified version.
-
I have a fix for ncid version 1.12 which will be in release 1.13, if it tests OK for you: Change this if statement in /usr/bin/ncid: if {![info exists $::env(HOME)]} { set UnixLogDir "$::env(HOME)/NCID/client" set UnixRCfile "$::env(HOME)/.ncid" set UnixASfile "$::env(HOME)/.config/autostart/ncid.desktop" } else { set UnixLogDir "/tmp/ncid" } to: if {[catch {info exists $::env(HOME)} oops]} { set delayedMsgs "$delayedMsgs\n$oops" set UnixLogDir "/tmp/ncid" } else { set UnixLogDir "$::env(HOME)/NCID/client"...
-
Fixed ncid install complaining about libcarrier not found.
-
Added tag v1.12-f for changeset f6dea96e9a52
-
NCID Release 1.12 changes
-
Added tag v1.12 for changeset 230aac344f1e
-
Added tag v1.12 for changeset fe4d8b0050e8
-
See doc/CHANGES section 1.12 for updated changes
-
NCID Release 1.12
-
You are correct. The column is called "Line ID" and unfortunately for me and my response, it is a required column because of aliases. On Thu, Jul 29, 2021 at 03:10:36PM -0000, Ed Attfield wrote: I also think that the first part of this request is a non-starter, because a number shown in cidcall.log could have been affected by several alias lines and then allowed by the whitelist. On Thu, Jul 29, 2021, 09:25 John L. Chmielewski, jlc@users.sourceforge.net wrote: status: open --> closed Comment: 1:...
-
Sounds good. On Thu, Jul 29, 2021 at 02:59:13PM -0000, Ed Attfield wrote: In recent reading of documentation for the Connexant modem, I found a feature that might give us indication of another phone going off hook on the line. I was hoping to use it to stop the outgoing hangup message so I didn't have to shout over it to answer a legitimate call from an 800 number. [feature-requests:#30] Line in use for visual or other type of alerts. Status: closed Group: Next_Release_(example) Labels: Line in use...
-
Whozz Calling gateway for serial units using URL_Send/URL_Receive
-
The network version of Whozz Calling is currently supported
-
NCID Android Client Number Format String
-
NCID Android Client Number Format String
-
The ncidd server in NCID 1.12 will format numbers for all (most?) countries using libphonenumber. NCIDandroid will be modified to use the formatted number.
-
1: Configurable columns will be in NCID 1.12 2: Not implementing mysql at this time. The new cidupdate tool is much faster and should resolve your speed problem.
-
2 Feature Requests
-
1: Configable columns will be in NCID 1.12 2: Not implementing mysql at this time. The new cidupdate tool is much faster and should resolve your speed problem.
-
Line in use for visual or other type of alerts.
-
NCID release 1.12 will allow you to configure columns to view on screen. There are four columns that are mandatory. There is a minimum size which I hope will be OK .
-
client window size
-
Start ncidd from the terminal in debug mode. The verbose output should indicate where the problem is. If you want the verbose output to also be sent to /var/log/ncidd.log, start the command with sudo. ncidd -D Ed is probably correct that /etc/ncid/ncidd.whitelist is the problem.
-
Tk is needed for the GUI. You need to also install tcl: sudo apt install tcl
-
Alias, blacklist or whitelist require the telephone number as it appears in /var/log/cidcall.log. The ncid client, up to release 1.11 removes all characters that are not numbers from the telephone number. It assumes ncidd receives digit only numbers, which is not true in your case and most like others. The ncid client in will have that fixed when 1.12 is released. As a workaround until the release, either edit the alias file and create an alias entry or let ncid create the alias and then add the...
-
The ncid-notify client module uses Prowl. The name or alias is sent by ncidd so check if ncid displays the alias. The ncid-notify script gets the name or alias from ncid. If ncid does not display the alias, edit /etc/ncid/ncidd.alias to make sure the alias is there and is correct. It should be: alias NAME * = "<alias>" if "<number>" I am interested in the problems you had with v1.11 on the Raspberry Pi. The release was tested on a Raspberry Pi. Version 1.12 will be released shortly and I need to...
-
The ncid-notify client module uses Prowl. The name or alias is sent by ncidd so check if ncid displays the alias. The ncid-notify script gets the name or alias from ncid. If ncid does not display the alias, edit /etc/ncid/ncidd.alias to make sure the alias is there and is correct. It should be: alias NAME * = "<alias>" if "<number>" I am interested in the problems you had with v1.11 on the Raspberry Pi. The release was tested on a Raspberry Pi. Version 1.12 will be released shortly and I need to...
-
The ncid-notify client module uses Prowl. The name or alias is sent by ncidd so check if ncid displays the alias. The ncid-notify script gets the name or alias from ncid. If ncid does not display the alias, edit /etc/ncid/ncidd.alias to make sure the alias is there and is correct. It should be: alias NAME * = "<alias>" if "<number>"</number></alias> I am interested in the problems you had with v1.11 on the Raspberry Pi. The release was tested on a Raspberry Pi. Version 1.12 will be released shortly...
-
No, you must terminate any other ncidd using port 3333 when you start ncidd in debug mode: ncidd -D3
-
You need to provide /var/log/ncidd.log as an attachment to get help troubleshooting ncidd. If you do not configure ncidd in ncid.conf, it will accept clients connections from everywhere on port 3333. Review ncidd.log to see how the server is configured. When the client is trying to connect, it displays: IPaddress:PortNumber Start ncid in a terminal window to display a log: ncid -v1 to see how ncid is configured. Review the NCID User Manual, especially the installation section for information on how...
1 >