Menu

Question on alias file size limits?

Help
nospam
2022-01-06
2022-01-08
  • nospam

    nospam - 2022-01-06

    I just upgraded to 1.12 on my raspi and I'm finding that numbers in my alias file are showing up as "NO NAME" in the call log. My old alias file is 1600+ lines long and I copied and pasted the old aliases into my new alias file. I see no errors in my ncidd.log file.

    If I manually edit the alias file, do I have to
    sudo systemctl restart ncidd

    To re-read my alias file?
    Also, my cidcall.log file now seems to show extra information

    old version
    CID:*DATE*01042022*TIME*1002*LINE*POTS*NMBR*1XXXXXXXXXX*MESG*NONE*NAME*NO NAME*
    new version
    CID:*DATE*01062022*TIME*1207*LINE*POTS*NMBR*1XXXXXXXXXX*MESG*NONE*FNMBR*+1 XXX-XXX-XXXX*NTYPE*FIX/CELL*CTRY*CA*LOCA*myProvince*CARI*Some Carrier Inc. (Wireless)*NAME*NO NAME*

     

    Last edit: nospam 2022-01-06
  • Ed Attfield

    Ed Attfield - 2022-01-06

    The added information about the call is a 1.12 feature.

    There is no upper bound on the size of the aliases file. ncidd keeps the list in memory to make it somewhat faster to search, but the search is linear because the order is important.

    I would want to set the verbose level to 7 and examine the logs to see why the call isn't showing the alias results.

     
  • bgr_bgr

    bgr_bgr - 2022-01-08

    Could be something to do with the alias format in the alias file ,
    also , check the rw rights on /etc/ncid/ncidd.alias
    do you use regular expressions option ? ( i do )

    here is a (working ) sample of my ncidd.alias :
    alias NAME .* = "John Doe" if "^123456789$" # Wed Jan 5 18:23:24 20

    also in /var/log/ncidd.log you should have (example) :

    Begin: Loading alias, blacklist and whitelist files [03:10:03]
    Processed alias file: /etc/ncid/ncidd.alias
    Alias Table:
    Number of Entries: 166
    SLOT TYPE FROM TO DEPEND
    ---- ---- ---- -- ------

    000  NAMEDEP .*      John Doe              "^0123456789$"
    ......etc
    

    BGR

     

Log in to post a comment.