Network Caller ID (NCID) is an open-source client/server software system that shares Caller ID data across multiple computers, phones, and media centers over a local network. Setting up an NCID environment requires installing a central server module (ncidd) to grab telephone signals and connecting individual client devices to display the caller information in real time.
Here is a step-by-step guide to installing, configuring, and testing your NCID network. Hardware and Prerequisites
Before configuring the software, collect the necessary equipment:
A Host Machine: A dedicated computer or a low-cost, low-power option like a Raspberry Pi.
A Caller ID Source: A physical USB modem supporting Caller ID (for traditional analog POTS lines) or a configured VoIP gateway.
Network Connection: Ensure all host machines and user devices share the same local area network (LAN). Step 1: Install the NCID Server (ncidd)
The core server background process daemon is responsible for tracking calls and pushing data out to client screens. On Linux / Raspberry Pi OS
Open a command terminal on your host server machine and run the following packages: sudo apt update sudo apt install ncid ncid-utils Use code with caution. On Windows
Download the latest Windows binary file from the NCID SourceForge Repository.
Extract the downloaded archive package contents to a directory (e.g., C: cid).
Run the setup installer executable to register ncidd as a running background service. Step 2: Configure the Server Settings
You must instruct the server which hardware device or source protocol to monitor for inbound text signals.
Locate Configuration: Open the main text file, typically found at /etc/ncid/ncidd.conf on Linux machines.
Set the Serial Port: If using a physical USB modem, find and uncomment the set ttyport line to define your connection hardware: set ttyport = /dev/ttyACM0 Use code with caution.
Configure VoIP (Optional): If pulling data from a SIP/VoIP setup instead of a modem, scroll to the gateway modules section and activate the SIP flags: set source = sip Use code with caution.
Save and Restart: Save your document changes and restart the active service to load the parameters: sudo systemctl restart ncidd Use code with caution. Step 3: Connect Client Hardware and Software
With your host listening for calls, you can now link client applications across your home or office network. Deploying the Universal Desktop Client
Install the ncid-client software package on your target desktop computer. Launch the application and enter the primary settings menu.
Input the IP address of your master NCID server host machine.
Set the connection port rule (the default system delivery rule relies on Port 3333).
Deploying Integrated Network Devices (e.g., Fritz!Box or SmartCallMonitor)
If utilizing specialized third-party routing appliances or software modules like SmartCallMonitor, use their built-in integration tabs:
Navigate to Settings > Telephony > NCID Settings within the platform interface.
Toggle the Activate NCID option to enable incoming network call scanning.
Provide your server’s assigned LAN IP address to link the devices instantly. Step 4: Test and Verify the Infrastructure
You can verify that your network connections work properly without waiting for an external phone call.
Send a simulated test call string directly from your server command line to connected endpoints: ncid-notify -m “Test Call” -n “555-0199” Use code with caution.
Verify that a pop-up alert displaying the custom phone number appears simultaneously on all active client screens.
To expand your setup, you can check the NCID SourceForge Documentation for modules that log history or automatically hang up on known telemarketers. If you want to tailor your installation, let me know:
What Operating System your primary server will run on (Linux, Windows, macOS)?
Whether your phone line is traditional analog (POTS) or digital VoIP/SIP? If you intend to set up automatic call blocking features? Settings > Telephony > NCID settings – JAM Software
Leave a Reply