John

As I mentioned above and you pointed out, this is not a NCID issue. I was hoping someone might have a workaround. Thanks for clarifying how the alert tone/ACK signal process works for Type II Caller ID.

Does ncid support caller id type II (call waiting caller id) if active call is on a caller id type 1 phone? Running ncid 1.13 on ubuntu 20.04. We have an old polycom speaker phone which only supports caller id type 1. We also have hand held phones that support caller id type 2. Using the hand held caller id type 2 phones to answer incoming calls, initial caller id as well as call waiting caller id works fine. NCID clients receive caller id notification of both calls (initial as well as call waiting)....

My log file matched your settings. Turns out the problem was the modem initialization. Thanks for including the comment in ncidd.conf concerning: # The default modem initialization is: "AT Z S0=0 E1 V1 Q0" ATZ was resetting the modem parameter AT+PCW. Unfortunately, the Conexant Systems (Rockwell), Inc. CX93001-EIS_V0.2002-V92 modem defaults to +PCW=2 which is "disable call waiting". While I can manually set with AT+PCW=0 and save the profile, any ATZ will return it to +PCW=2. I updated ncidd.conf...

I'm trying to get call waiting callerid working. (ncid-1.12) on ubuntu 20.04. Regular caller id (1 call) works and my NCID Pop on mac client as well as other platform clients receive/display the correct information. When I query the modem, at+PCW=? returns (0-2) OK. According to the Conexant manual, PCW is used for call waiting detection. It also states, when +PCW = 1 and Caller ID is enabled, the modem will attempt to do Type II Caller ID before hanging up. I also queried the modem with at-scid=?...

John, I applied your fix to ncid release 1.12 without modifications and it works great. Thanks! In my attempt to keep client and server on the same release (e.g. 1.12), I attempted to upgrade my server ncidd to 1.12 & got the following error. dpkg -i ./ncid_1.12-1_amd64.deb (Reading database ... 138459 files and directories currently installed.) Preparing to unpack ./ncid_1.12-1_amd64.deb ... Unpacking ncid (1.12-1) over (1.11-1) ... Job for ncidd.service failed because the control process exited...

As I said in my initial post, my init script was from 4+ years ago since I was upgrading a box. I converted it to systemctl (putting my custom module file in /usr/lib/systemd/system) and still had the issue. Ignoring my custom KODI module, I tried the included client ncid-notify.service and ncid-page.service (both found in /usr/lib/systemd/system) and they too failed to start as a service. This made me consider it wasn't an issue with the files in /usr/lib/systemd/system. While troubleshooting ncid-notify.service,...

seems to be related $::env(HOME) in /usr/bin/ncid. set UnixLogDir $::env(HOME)/NCID/client set UnixRCfile "$::env(HOME)/.ncid" set UnixASfile "$::env(HOME)/.config/autostart/net.sourceforge.ncid.desktop" I hard coded the paths and it seems to address the issue starting as a service.

I have a similar problem running ncid as a service (e.g. /etc/init.d/ncid-<client>) on ubuntu-20.04. Ncid works fine (e.g. make call, modem answers and proper info is displayed) from an interactive shell. It also works fine if I put ncid in the background from an interactive shell. env: ncid - ncid-client_1.11-1_all.deb ncidd - ncid_1.11-1_amd64.deb I read above you made a fix for sandya to get ncid running as a service so I downloaded ncid-1.12.-1_all.deb. I didn't know if the fix was specific to...