the problem i am having is it answers the phone line occasionally the output from NCID is as follows:-
[root@compaq2 ~]# ncidd -Dv3
Started: 08/18/2006 15:52
Server: ncidd 0.65
ncidd logfile: /var/log/ncidd.log
Processed config file: /etc/ncid/ncidd.conf
Configured to send 'cidlog' to clients.
Configured to send 'cidinfo' to clients.
Processed alias file: /etc/ncid/ncidd.alias
Verbose level: 3
CID logfile: /var/log/cidcall.log
Data logfile: /var/log/ciddata.log
TTY port opened: /dev/modem
TTY port speed: 19200
TTY lock file: /var/lock/LCK..modem
TTY port control signals enabled
AT Z S0=0
OK
Try 1 to init modem: return = 0.
Modem initialized.
AT#CID=1
OK
Modem set for CallerID.
TTY in use: releasing modem 08/18/2006 15:52
Client connected, sd: 6, Sent call log: /var/log/cidcall.log
TTY free: using modem again 08/18/2006 15:52
AT Z S0=0
OK
Try 1 to init modem: return = 0.
Modem initialized.
AT#CID=1
OK
Modem set for CallerID.
Client connected, sd: 7, Sent call log: /var/log/cidcall.log
CIDINFO: LINE-RING1
TTY in use: releasing modem 08/18/2006 15:53
CIDINFO: LINE-RING0
Terminated: 08/18/2006 15:54
how do i determine what is "nicking the modem"?
aprt from that it works fine.
it seems that when the modem hangs up is when it throws ncidd off the system and displays:-
TTY free: using modem again 08/18/2006 16:04
Cannot init TTY, Terminated 08/18/2006 16:04
help anyone?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems like the modem is set to autoanswer, however the log file shows s0=0 (autoanswer off).
Maybe you have another program trying to use the modem?
You might want to try to set the lockfile to something that will not be created, then NCID will not release the modem:
set lockfile = NONE
See if this changes anything.
NCID monitors to see if the lock file exists, if it does, it assumes another application is using it. When the lock file foes away, NCID tries to control the modem again, but is not always successful.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay i use cc3.2 slimserver and ncid all on the same box
ncidd runs fine when i try and run the following command NOT IN A TERMINAL i end up with 100% processor usage does any one have any suggestions? if i run it in a termnal it runs fine if i try and run it as a cron job (with options set) i get the same problem (near 100% processor usage) the full command is:-
I am not familiar with slimserver, but a search on google said it was part of slimdevices. I tried to search for slim.pl but was unsuccessful.
Your 100% CPU usage may not be a problem. If slim.pl is running in a loop, the CPU will show 100% since the program is always running and not sleeping, but as other programs run, the CPU will take time away from slim.pl to run them.
Your command line is correct for ncid, but I do not know if you need options on slim.pl.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
modem is a hayes accura 56k 5670GB.
the problem i am having is it answers the phone line occasionally the output from NCID is as follows:-
[root@compaq2 ~]# ncidd -Dv3
Started: 08/18/2006 15:52
Server: ncidd 0.65
ncidd logfile: /var/log/ncidd.log
Processed config file: /etc/ncid/ncidd.conf
Configured to send 'cidlog' to clients.
Configured to send 'cidinfo' to clients.
Processed alias file: /etc/ncid/ncidd.alias
Verbose level: 3
CID logfile: /var/log/cidcall.log
Data logfile: /var/log/ciddata.log
TTY port opened: /dev/modem
TTY port speed: 19200
TTY lock file: /var/lock/LCK..modem
TTY port control signals enabled
AT Z S0=0
OK
Try 1 to init modem: return = 0.
Modem initialized.
AT#CID=1
OK
Modem set for CallerID.
TTY in use: releasing modem 08/18/2006 15:52
Client connected, sd: 6, Sent call log: /var/log/cidcall.log
TTY free: using modem again 08/18/2006 15:52
AT Z S0=0
OK
Try 1 to init modem: return = 0.
Modem initialized.
AT#CID=1
OK
Modem set for CallerID.
Client connected, sd: 7, Sent call log: /var/log/cidcall.log
CIDINFO: LINE-RING1
TTY in use: releasing modem 08/18/2006 15:53
CIDINFO: LINE-RING0
Terminated: 08/18/2006 15:54
how do i determine what is "nicking the modem"?
aprt from that it works fine.
it seems that when the modem hangs up is when it throws ncidd off the system and displays:-
TTY free: using modem again 08/18/2006 16:04
Cannot init TTY, Terminated 08/18/2006 16:04
help anyone?
I too use NCID and Slimserver. All I did was take the script and make the changes as detailed in the Slimserver Forum;
http://forums.slimdevices.com/showthread.php?t=18377
I start ncid with the following command;
nohup ncid --no-gui --all --call-prog --program /mnt/jeroboam/software/Linux/Slimp3/Plugin/CID/cid.pl &
This is running well on FC4, Slimserver 6.5b1 and NCID 0.65
It seems like the modem is set to autoanswer, however the log file shows s0=0 (autoanswer off).
Maybe you have another program trying to use the modem?
You might want to try to set the lockfile to something that will not be created, then NCID will not release the modem:
set lockfile = NONE
See if this changes anything.
NCID monitors to see if the lock file exists, if it does, it assumes another application is using it. When the lock file foes away, NCID tries to control the modem again, but is not always successful.
Thanks it was mgetty.
now works well but i ahave another niggle:-
Okay i use cc3.2 slimserver and ncid all on the same box
ncidd runs fine when i try and run the following command NOT IN A TERMINAL i end up with 100% processor usage does any one have any suggestions? if i run it in a termnal it runs fine if i try and run it as a cron job (with options set) i get the same problem (near 100% processor usage) the full command is:-
[root@compaq2 ~]# ncid --no-gui --all --call-prog --program /usr/local/sbin/slim.pl
anyone advise how to run this properly?
I am not familiar with slimserver, but a search on google said it was part of slimdevices. I tried to search for slim.pl but was unsuccessful.
Your 100% CPU usage may not be a problem. If slim.pl is running in a loop, the CPU will show 100% since the program is always running and not sleeping, but as other programs run, the CPU will take time away from slim.pl to run them.
Your command line is correct for ncid, but I do not know if you need options on slim.pl.