[Hopefully I’m not duplicating myself – sent around eight hours ago via the e-mail option and not seeing it post yet. Using the “Create Topic” option this time.]
Running NCID version 1.13-2 on a Raspberry Pi 3B using Bullseye 64-bit. It appears ncidd.blacklist is not working: I went through the GUI to add a number which it did but two days later the nuisance called again and got through: "3194063261" # Voter survey # Wed Oct 26 18:39:07 2022
So tried some stuff this morning to test with my cell phone – I’m getting through also. (Later thinking maybe because I had put myself in the ncidd.alias list which per the manual is read before the blacklist?)
Quirky side note: If I use NCID GUI to dial to my cell phone it rings my cell once and hangs up! Window pops up with header “Dial Reply” and the text “dial – hungup 563 (the rest of my number) on line “POTS”” . When I manually dial from the landline to my cell phone goes through fully/properly.) Not planning to use the NCID GUI for dialing but may be significant for troubleshooting.
So ncidd.alias and fcc.blacklist appear to work fine. ncidd.blacklist has issues. ncidd.whitelist – not sure as haven’t needed to use yet. These four files are in /etc/ncid (along with ncid.conf and ncidd.conf).
ncidd.conf says:
# The default blacklist file: /usr/etc/ncid/ncidd.blacklist
# set blacklist = /usr/etc/ncid/ncidd.blacklist
I copied ncidd.blacklist to /usr/etc/ncid (had to create from ‘etc’ on), restarted using sudo systemctl restart ncidd (the GUI indicates can’t find then reconnects in a few seconds). My cell still gets through (LIS may be because in alias). Had also tried set blacklist = /etc/ncid/ncidd.blacklist with same result.
At this point have both /etc/ncid/ncidd.blacklist and /usr/etc/ncid/ncidd.blacklist and waiting for a listed spammer to call! (/etc/ncid/fcc.blacklist works fine.) Update: finally one called: telephone rang several times even though was listed in the ncidd.blacklist.
So what do I need to do to correct and get my ncidd.blacklist working?
TIA!
Barry
Last edit: Barry Martin 2022-10-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Look at the bottom of your /var/log/ncidd.log file for the options in effect for the most recent starting of ncidd. This will show the file pathnames and number of lines read in. Also check the hangup settings here.
If you raise the verbose level in ncidd.conf to 7 and restart ncidd, you can log the file contents and see it handle the call.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the leads as to where to start. Looked at my log from last night’s reboot and found these entries of interest (my comments in parenthesis):
Processed alias file: /etc/ncid/ncidd.alias (correct)
Processed blacklist file: /etc/ncid/ncidd.blacklist (correct)
Processed whitelist file: /etc/ncid/ncidd.whitelist (correct)
Calls in the blacklist file will be terminated (good)
Calls in the whitelist file will not be terminated (good)
Leading 1 in call & alias/blacklist/whitelist not ignored
Well there’s a potential problem! I am in the U.S. Alias ‘conversion’ works properly, blacklist not (fcc.blacklist does) – will look at this option more closely.
Will increase the logging level if the ‘1’ investigation doesn’t pan out.
Thanks!
Barry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Ed!
Quick followup: I’ve uncommented the set ignore1 = 1 entry in ncidd.conf. Log now reads Leading 1 ignored in call & alias/blacklist/whitelist. Now just waiting for someone to call!
Barry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The leading-one option should not be an issue because the blacklist matches parts of strings, e.g. 3456 will match 8883456123 and 8881233456.
If you get totally frustrated, you can email me the log file at verbose=7
edit: fixed the 34567 example
Last edit: Ed Attfield 2022-10-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Ed! I tried that and I went right through! Thought maybe because I have my cell phone in the alias list -- suppose I could comment myself out to find out. (I've volunteered to test someone else's project to output Alias CID Data to the telephones.) Barry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Folks!
[Hopefully I’m not duplicating myself – sent around eight hours ago via the e-mail option and not seeing it post yet. Using the “Create Topic” option this time.]
Running NCID version 1.13-2 on a Raspberry Pi 3B using Bullseye 64-bit. It appears ncidd.blacklist is not working: I went through the GUI to add a number which it did but two days later the nuisance called again and got through: "3194063261" # Voter survey # Wed Oct 26 18:39:07 2022
So tried some stuff this morning to test with my cell phone – I’m getting through also. (Later thinking maybe because I had put myself in the ncidd.alias list which per the manual is read before the blacklist?)
Quirky side note: If I use NCID GUI to dial to my cell phone it rings my cell once and hangs up! Window pops up with header “Dial Reply” and the text “dial – hungup 563 (the rest of my number) on line “POTS”” . When I manually dial from the landline to my cell phone goes through fully/properly.) Not planning to use the NCID GUI for dialing but may be significant for troubleshooting.
So ncidd.alias and fcc.blacklist appear to work fine. ncidd.blacklist has issues. ncidd.whitelist – not sure as haven’t needed to use yet. These four files are in /etc/ncid (along with ncid.conf and ncidd.conf).
ncidd.conf says:
I copied ncidd.blacklist to /usr/etc/ncid (had to create from ‘etc’ on), restarted using sudo systemctl restart ncidd (the GUI indicates can’t find then reconnects in a few seconds). My cell still gets through (LIS may be because in alias). Had also tried set blacklist = /etc/ncid/ncidd.blacklist with same result.
At this point have both /etc/ncid/ncidd.blacklist and /usr/etc/ncid/ncidd.blacklist and waiting for a listed spammer to call! (/etc/ncid/fcc.blacklist works fine.) Update: finally one called: telephone rang several times even though was listed in the ncidd.blacklist.
So what do I need to do to correct and get my ncidd.blacklist working?
TIA!
Barry
Last edit: Barry Martin 2022-10-29
Look at the bottom of your /var/log/ncidd.log file for the options in effect for the most recent starting of ncidd. This will show the file pathnames and number of lines read in. Also check the hangup settings here.
If you raise the verbose level in ncidd.conf to 7 and restart ncidd, you can log the file contents and see it handle the call.
Hi Ed!
Thanks for the leads as to where to start. Looked at my log from last night’s reboot and found these entries of interest (my comments in parenthesis):
Processed alias file: /etc/ncid/ncidd.alias (correct)
Processed blacklist file: /etc/ncid/ncidd.blacklist (correct)
Processed whitelist file: /etc/ncid/ncidd.whitelist (correct)
Calls in the blacklist file will be terminated (good)
Calls in the whitelist file will not be terminated (good)
Leading 1 in call & alias/blacklist/whitelist not ignored
Well there’s a potential problem! I am in the U.S. Alias ‘conversion’ works properly, blacklist not (fcc.blacklist does) – will look at this option more closely.
Will increase the logging level if the ‘1’ investigation doesn’t pan out.
Thanks!
Barry
Hi Ed!
Quick followup: I’ve uncommented the set ignore1 = 1 entry in ncidd.conf. Log now reads Leading 1 ignored in call & alias/blacklist/whitelist. Now just waiting for someone to call!
Barry
The leading-one option should not be an issue because the blacklist matches parts of strings, e.g. 3456 will match 8883456123 and 8881233456.
If you get totally frustrated, you can email me the log file at verbose=7
edit: fixed the 34567 example
Last edit: Ed Attfield 2022-10-29
Hi Ed! Not ignoring you but literally waiting for a spam call since our last posts.
Barry
I do my testing by putting my cell phone number into the blacklist and calling myself. :')
Hi Ed! I tried that and I went right through! Thought maybe because I have my cell phone in the alias list -- suppose I could comment myself out to find out. (I've volunteered to test someone else's project to output Alias CID Data to the telephones.) Barry