#25 custom hangup app

[Anonymous]

Hi,
I created a hangup app in python that was working on the pi before it crashed. I now have debian running on intel. It seems to be mostly working but it is clear that my hangup routine is not getting called. There is code in the routine to lag its activity but no logs are created.

i have not found a way to tell if ncidd is actually calling it. There doesn't seem to be a logging option to report invocations of hangup routines (should there be?)

This is from my conf:

If your extension is not in the default path, specify a full path name.

The default hangup path: /usr/share/ncid/extensions/

The default hangup name: hangup-nohangup

set hupname = hangup-fakenum

set hupname = /root/Apps/hangup-by-keyword

I first had thhe file in /usr/share/ncid/extensions.

Can anyone help me figure this out.

Thanks

[Anonymous]

The bold stuff are the comments (blame the novice in me for not realizing I should have use and not ""

[Anonymous]

Please don't bother with this for the moment. I may have tracked down the problem .

But my comment about perhaps being able to calls to hangup routines still applies

Thanks. I will pick this up again if my diagnosis proves to be incorrect

[Ed Attfield]

Problems with finding the external hangup script are logged as errors at startup. Success is logged in /var/log/ncidd.log at verbose=1 and execution of the script is logged at verbose=3 and 4.

Perhaps you haven't set the hupmode option in the ncidd.conf file to turn it on ?