Glen Oakes

I think that explains what I'm seeing in that about half the time no OK is received from my modem. Thanks for the help. I really appreciate it. glen On 5/5/20 8:55 PM, Ed Attfield wrote: I ran it to check; blacklisting and calling myself. In 1.11, ncidd sends the HUP message as soon as it succeeds in going off-hook to send the fax response (and CID if it fails in some way to get the OK back from the modem). With verbose level 7, number redacted, I got the attached output. Attachments: faxmode-HUP...

Ed -- it's strange. I blacklisted my cell and called 5 times. Three were CID and the other two were HUP. All five gave FAX tones. I had one other call <political call=""> which was blocked. The log entry showed HUP for it. For some reason the log entries seem erratic.</political> Thanks for your quick response. glen On 5/5/20 4:29 PM, Ed Attfield wrote: The CID and HUP strings are not configurable, and the clients like ncid and NCIDandroid use them to give different behaviour. Your fax hangup should...

I got that formatting issue re: the cidcall.log resolved. Thanks to everyone who responded and helped. Now, I have a new one -- still related to the log. I was "tinkering" and decided to turn on the "hangup = 2" option -- the one that responds with a FAX sound rather than just hanging up. It works well but the call log entry reflects "CID" rather than "HUP". I'd like to know that the call was actually terminated. What I'd really like to see is "FAX" in that field. 1) Am I missing a setting to make...

I was a bit incorrect on my earlier email. The connection is closed with the message as I said -- after only some 2-3 minutes. After the message is displayed, the cursor drops to the next line and blinks, but with no prompt. After a short period of time the log file is re-scrolled. I suspect that's initiated via the stay-alive setup in the ssh config file. The rPi is running as follows: g On 4/29/20 11:42 AM, Todd Andrews wrote: Hi Glen, I'm not finding in the source where it would generate that...

The connection is wired. I use putty, ssh from my office workstation running Ubuntu 18.04. The Raspi session is run on Raspbian. I can send a screen shot but all there is that one line I sent previously that follows immediately below the last line of the cidcall.log, followed by a Linux prompt. I'll get a screen shot of the next occurrence. g On 4/29/20 11:42 AM, Todd Andrews wrote: Hi Glen, I'm not finding in the source where it would generate that message. Can you attach a screen capture to this...

Todd, this is FWIW. I added stayalive commands in my .ssh/config file. Actually, ssh terminating has not been a problem as I run regularly multiple ssh sessions from my office linux system into both Raspis and our fileserver. They don't terminate. Anyway, after adding and configuring the .ssh/config file, I opened a session into the Raspi and ran <ncid --no-gui=""> from the command line. It terminated that command after about 2 hours with: <127.0.0.1:3333 - CID connection closed>, I take it that...

Todd, thanks for your help. Actually, I don't really have to solve this issue as that piece of code I wrote works well for me. But, the problem is interesting and the solution may help someone else. The following is the output of the commands on the Raspi. fgo-pi: /call_blocker $ xhost >/dev/null 2>/dev/null && echo "GUI" || echo "no-gui" no-gui fgo-pi: /call_blocker $ time xhost xhost: unable to open display "" real 0m0.020s user 0m0.010s sys 0m0.000s fgo-pi: /call_blocker $ On 4/28/20 3:33 PM,...

Todd, your instructions to start the app with <ncid --no-gui=""> displays the info in a meaningful way. But, it times out after a short time. Any way to keep that running, as in "indefinitely".</ncid> thx g