Ncid

[Phreedom]

I installed NCID (see http://ncid.sourceforge.net/). It works just fine, I even added it to my startup script and that works too. What I'm not sure about is when I do a ps -aux | grep ncid I have three instances of the program running. Shouldn't there only be one? I can kill two off and it still works.

[shutterfriend]

I installed NCID (see http://ncid.sourceforge.net/). It works just fine, I even added it to my startup script and that works too. What I'm not sure about is when I do a ps -aux | grep ncid I have three instances of the program running. Shouldn't there only be one? I can kill two off and it still works.

Phreedom,

What version of Tivo are you running ncid with?

[jlc]

NCID version 0.64 has been released. It has fixes for the server termination problem, and it has new features.

There is a new client, called ncidsip. It uses SIP Invite to obtain VOIP Caller ID information, and then sends it to the server as a CID message. The server now supports multiple lines: one standard telephone line (can have distinctive ring lines), and multiple VOIP lines. The server can be configured without a modem and just use one or more CID clients like ncidsip. The alias configuration command has been expanded to alias the line indicator used by distinctive ring and ncidsip. The ncid client will display the line indicator in its history window, but TiVoCID will not yet display it on the TiVo. See the web page and Release Notes for more information.

The included tools; cidalias, cidcall, cidupdate, and ncidsip are Perl programs. If you put Perl in /var/hack/bin they will find it. I only know of this Perl being available for a series 2: http://marc.abramowitz.info/archive...-tivo-series-2/ there may be another. In addition ncidsip requires the Net-Pcap Perl module: http://search.cpan.org/CPAN/authors....12/Pcap.tar.gz and it requires libpcap: http://sourceforge.net/projects/libpcap/ Hopefully someone can make binaries.

Its possible to rewrite ncidsip using tcl, but you need a interface to libpcap. I found tclpcap at http://tclpcap.sourceforge.net/ so if anyone is interested in doing this, contact me at sourceforge.

The display program, out2osd, still does not work with 7.2. If anyone has modified libosd to work, or if anyone knows of a program that will take a text line and display under 7.2 let me know. TiVoCID can pipe its output to any display program.

[cheer]

I installed NCID (see http://ncid.sourceforge.net/). It works just fine, I even added it to my startup script and that works too. What I'm not sure about is when I do a ps -aux | grep ncid I have three instances of the program running. Shouldn't there only be one? I can kill two off and it still works.
If you're running a newer version of the Tivo software -- 6.x or 7.x -- that's perfectly normal. Leave them be.

[jlc]

NCID version 0.65 has been released.

The TiVo display was fixed and updated to display the optional line indicator and messages.

NCIDsip was improved.

NCID was modified to accept NCIDINFO messages. This allows the VOIP CID client to send a CANCEL message when a call is aborted before pickup. The client can test for this and output to a output module when it receives a CANCEL notification. Thus a cell phone can be sent a message only if the phone is not answered.

[shutterfriend]

NCID version 0.65 has been released.

The TiVo display was fixed and updated to display the optional line indicator and messages.

NCIDsip was improved.

NCID was modified to accept NCIDINFO messages. This allows the VOIP CID client to send a CANCEL message when a call is aborted before pickup. The client can test for this and output to a output module when it receives a CANCEL notification. Thus a cell phone can be sent a message only if the phone is not answered.

jlc,

Does the new version support TiVo 7.2.2b. I know there was some issues with the front buffer and was curious if this has been resolved yet.

Thanks.

[jlc]

jlc,

Does the new version support TiVo 7.2.2b. I know there was some issues with the front buffer and was curious if this has been resolved yet.

Thanks.

Sadly it does not. I tried a fix on libosd and it did not work. If anyone knows of a program that will accepted a pipe for text input and display it on 7.2, it can be used to get TiVoCID working again. TiVoCID allows you to specify the program to pipe its output to with the '--program' option.

[Jamie]

Does this help?
bash-2.02# /tvbin/text2osd --help
/tvbin/text2osd: unrecognized option `--help'
/tvbin/text2osd
--line <line number>
--message <string>
--xscale <number>
--yscale <number>
--bgscolor [<num num num, r-g-b values>][<string,red|green|blue|white|black>]
--fgscolor [<num num num, r-g-b values>][<string,red|green|blue|white|black>]
--clear

It can read the message from stdin, but it appears to only take one line per invocation.

[jlc]

It could help. Does it take over the whole screen or just the line displayed? Once it displays something, do you need to clear it with /tvbin/text2osd --clear? I assume line 1 is at the top? Is line 1 the default?

[Jamie]

It could help. Does it take over the whole screen or just the line displayed?Just the line displayed.Once it displays something, do you need to clear it with /tvbin/text2osd --clear?Seems so.I assume line 1 is at the top? Is line 1 the default?Line zero seems to be the top and is the default.

It might be that with a little effort with gdb and/or strace, we could figure out what text2osd is doing and adapt libosd accordingly.

[jlc]

It might be that with a little effort with gdb and/or strace, we could figure out what text2osd is doing and adapt libosd accordingly.

That is a thought. I think the libosd problem is an ioctl failing.

libosd 0.4.1 and my patches for the cross compilers can be found here: http://dealdatabase.com/forum/showthread.php?t=34159&page=4&highlight=libosd

This is the part of brcm.c that fails and prints: Couldn't find or create shared front buffer


if (bSurfaceGetSharedSurface(5, &surf) != 0) {
//printf(" creating our own...\n");
bSurfaceCreate(&dev_handle, 720, 480, 3, &surf);
bSurfaceShareSurface(surf, 5);
}
if (surf == 0) {
printf("Couldn't find or create shared front buffer\n");
bcmDeviceClose(&dev_handle);
return 0;
}


Here are the 3 ioctl calls, it seems at least 2 are failing.

if(ioctl(fd_gfx, 0xc00c62f2, &data) < 0) return 7; // bSurfaceGetSharedSurface()
if (ioctl(fd_gfx, 0xc01462c1, &data) != 0) return 7; // bSurfaceCreate()
if (ioctl(fd_gfx, 0xc00c62f1, &data) != 0) return 7; // bSurfaceShareSurface()


Could you explore text2osd a bit? Maybe a address or value changed. I do not have a hacked series 2 available.

[Jamie]

That is a thought. I think the libosd problem is an ioctl failing.
...
Could you explore text2osd a bit? Maybe a address or value changed. I do not have a hacked series 2 available.Yes, I spent some time this evening tracking this down. The ioctl to get the shared surface has changed. The first arg in the struct passed in is now a int32_t instead of an int16_t and the value to pass in now seems to be 0x1eb60 instead of 5.

I have a newtext2osd that works now. I still have some problems with libosd. It can create the surface now, and the examples run, but there is a side effect: For some reason all the tivo menus are doubled up now, with the second copy horizonally shifted by 1/2 character. It seems like libosd may be leaving the shared surface in a funny state that messes up the tivo menus. "text2osd --clear" restores the normal menus. I'll look at it further in the next day or two as time permits.

[jlc]

Yes, I spent some time this evening tracking this down. The ioctl to get the shared surface has changed. The first arg in the struct passed in is now a int32_t instead of an int16_t and the value to pass in now seems to be 0x1eb60 instead of 5.

I have a newtext2osd that works now. I still have some problems with libosd. It can create the surface now, and the examples run, but there is a side effect: For some reason all the tivo menus are doubled up now, with the second copy horizonally shifted by 1/2 character. It seems like libosd may be leaving the shared surface in a funny state that messes up the tivo menus. "text2osd --clear" restores the normal menus. I'll look at it further in the next day or two as time permits.

This is good news. It means that programs that use libosd will be able to work in 7.2 once you solve the menu problem.

I looked at the code to get the shared surface and noticed it is defined to return an int, but it returns data.retval which is a long. In fact, the code for all bSurface functions may need checking to see if other variables should be changed from int16_t to int32_t.

[Jamie]

Here's a patch to libosd-0.4.1 (http://www.dealdatabase.com/forum/showthread.php?p=180776#post180776) to get it to work with 7.x on Series2 hardware.

I misdiagnosed this a little bit in my last post. I was wrong about the datatype change. I think I was fooled when examining datastructures in memory because of padding for alignment within a struct.

As usual, AllDeadHomiez has travelled this path before us. In the tivovbi (http://www.dealdatabase.com/forum/showthread.php?t=41313&highlight=tivovbi) distribution, bcmosd.c has already been fixed for the newer tivo software versions and for Series 2.5 hardware.

The fix for 7.x is easy: use surface #1 if #5 fails. The libosd code had an explicit xoffset that was causing the menu shift I saw. I disabled that if surface #1 is used rather than #5.

Even with the attached patch, libosd still doesn't work on Series 2.5 hardware (R10, nightlite models, etc). The ADH changes to tivovbi handle that too, but the changes are more complicated, and I haven't take then time yet to adapt it to libosd.

[singe606]

NCID version 0.64 has been released. It has fixes for the server termination problem, and it has new features.

There is a new client, called ncidsip. It uses SIP Invite to obtain VOIP Caller ID information, and then sends it to the server as a CID message. The server now supports multiple lines: one standard telephone line (can have distinctive ring lines), and multiple VOIP lines. The server can be configured without a modem and just use one or more CID clients like ncidsip. The alias configuration command has been expanded to alias the line indicator used by distinctive ring and ncidsip. The ncid client will display the line indicator in its history window, but TiVoCID will not yet display it on the TiVo. See the web page and Release Notes for more information.

The included tools; cidalias, cidcall, cidupdate, and ncidsip are Perl programs. If you put Perl in /var/hack/bin they will find it. I only know of this Perl being available for a series 2: http://marc.abramowitz.info/archive...-tivo-series-2/ there may be another. In addition ncidsip requires the Net-Pcap Perl module: http://search.cpan.org/CPAN/authors....12/Pcap.tar.gz and it requires libpcap: http://sourceforge.net/projects/libpcap/ Hopefully someone can make binaries.

Its possible to rewrite ncidsip using tcl, but you need a interface to libpcap. I found tclpcap at http://tclpcap.sourceforge.net/ so if anyone is interested in doing this, contact me at sourceforge.

The display program, out2osd, still does not work with 7.2. If anyone has modified libosd to work, or if anyone knows of a program that will take a text line and display under 7.2 let me know. TiVoCID can pipe its output to any display program.
Did you ever get ncidsip to work on the tivo? I think I've got the libpcap compiled correctly... but no way to test it. For fun I also compiled tcpdump, and that does seem to work when I run it on the tivo. Well, as far as I can tell anyway- spits out a whole lot of network info when I run it. That doesnt actually seem to use libpcap though.

No luck at getting the Net::Pcap module for perl. When I try to install it using the CPAN module on the tivo it dies:
Can't locate auto/DynaLoader/dl_findfile.al in @INC

That file doesn't seem to be in the perl 5.8.5 package I got from marc.abramowitz.info. I tried pretty unsuccessfully to build 5.8.8 myself.

Seems like it might be better to go the tcl route. Now I just need to learn tcl... heh :p

[jlc]

Did you ever get ncidsip to work on the tivo? I think I've got the libpcap compiled correctly... but no way to test it. For fun I also compiled tcpdump, and that does seem to work when I run it on the tivo. Well, as far as I can tell anyway- spits out a whole lot of network info when I run it. That doesnt actually seem to use libpcap though.

I did not get ncidsip working on the TiVo yet. I managed to cross compile libpcap, but it is untested also. I have not managed to cross compile Net::Pcap.

No luck at getting the Net::Pcap module for perl. When I try to install it using the CPAN module on the tivo it dies:
Can't locate auto/DynaLoader/dl_findfile.al in @INC

I thought Net::Pcap may depend on other Perl modules not included. You can find the DynaLoader module at CPAN (http://www.cpan.org/)

There is probably another module or two you need to compile. Run "perl -v" to see where Perl expects its lib directories and create them if needed.

That file doesn't seem to be in the perl 5.8.5 package I got from marc.abramowitz.info. I tried pretty unsuccessfully to build 5.8.8 myself.

This is the Perl thread where I found Perl 5.8.5: Anyone able to compile Perl for Series 2? (http://dealdatabase.com/forum/showthread.php?t=39857&highlight=perl)
Msabramo is the one that compiled Perl for the TiVo and he responded to my recent post, so maybe if you post for assistance there he or someone can give you pointers to build Perl 5.8.8

[jlc]

NCID version 0.66 has been released.

The server has a new fix so programs that take control of the modem can not cause it to abort if they release the modem improperly. This should fix all instances of ncidd aborting (hopefully).

The client has improvements and a new option to send messages to the output modules.

There is a new output module called ncid-tivo, that should run on all hacked TiVo hardware and the current OS. A new name for the client is tivoncid. It calls the ncid-tivo output module. This module uses the TiVo text2osd program instead of out2osd.

See the Release Notes and http://ncid.sourceforge.net for more information.

[dcahoe]

Sorry if this is the wrong place for this.

So is out2osd no longer required since txt2osd is used? The ncid-tivo instructions still say that out2osd is required. Is txt2osd already on the TiVo machines, or does it need to be loaded?

[jlc]

So is out2osd no longer required since txt2osd is used? The ncid-tivo instructions still say that out2osd is required. Is txt2osd already on the TiVo machines, or does it need to be loaded?

The client, ncid, can also be called tivocid or tivoncid. Both of these set up ncid with the correct options and output program. TiVoCID uses out2osd for the output, but TiVoNCID uses text2osd which comes with the TiVo OS. If you use TiVoNCID you do not need to load anything other than NCID version 0.66.

The NCID (http://ncid.sourceforge.net) web pages describe both. The INSTALL-TiVo file describes both. If you know of any documentation errors please point them out to me using my sourceforge email address.

[av8rdude]

I'm trying to run ncid on my hacked dvr40 with 6.2. I have the program installed in the default directory /var/hack. When I try to run the tivoncid & command I get the following error:

bash-2.02# invalid command name "0"
while executing
"0"
(procedure "displayLog" line 1)
invoked from within
"displayLog "Connecting to $Host:$Port""
(procedure "connectCID" line 15)
invoked from within
"connectCID $Host $Port"
(file "/var/hack/bin/tivoncid" line 579)

And ideas? TIA!
Scott

[jlc]

I'm trying to run ncid on my hacked dvr40 with 6.2. I have the program installed in the default directory /var/hack. When I try to run the tivoncid & command I get the following error:

bash-2.02# invalid command name "0"
while executing
"0"
(procedure "displayLog" line 1)
invoked from within
"displayLog "Connecting to $Host:$Port""
(procedure "connectCID" line 15)
invoked from within
"connectCID $Host $Port"
(file "/var/hack/bin/tivoncid" line 579)

And ideas? TIA!
Scott
This is a known problem that was just solved. Remove or rename ncid.conf to fix it. It appears that the "set Program ..." line in ncid.conf has to be last or tivosh gets confused. The next release of NCID will contain the fix.

[summerhome]

I have an hr10-250 with 6.3a and ncid 0.66. I don't remember what the previous verison of ncid was, but it all worked with 3.1.5f. I upgraded to 0.66 after upgrading to 6.3a because of this problem, but things act the same.

After an hour or so, ncidd stops working, however it is still running ( no crashes ). The way I can tell that ncidd stops is that I have stopped tivocid or tivoncid and checked the caller id log and after an hour or so no incomming calls are logged. If I restart ncidd, calls will be logged, but will stop being logged after an hour or so. I have looked in the logs and have not found any error to give me a clue as to what is failing. I stopped tivocid or tivoncid to make sure that the problem is not with them.

First, are there specific logs I should look into to see what is failing?

Second, are there any specific changes that need to be made for 6.3a beyond running tivoncid instead of tivocid?

Thanks for any help.

[jlc]

I have an hr10-250 with 6.3a and ncid 0.66.

After an hour or so, ncidd stops working, however it is still running ( no crashes ). The way I can tell that ncidd stops is that I have stopped tivocid or tivoncid and checked the caller id log and after an hour or so no incomming calls are logged. If I restart ncidd, calls will be logged, but will stop being logged after an hour or so. I have looked in the logs and have not found any error to give me a clue as to what is failing. I stopped tivocid or tivoncid to make sure that the problem is not with them.

First, are there specific logs I should look into to see what is failing?
The log file to look at is ncidd.log. It should tell you if it stopped and why. You may have to increase versose to 3 or 4 in ncidd.conf. If you see no indication of why it is not working, try to send a message and see if that works. You can use ncid on a pc to send the message or netcat on the TiVo:
echo "TiVo Test" | nc -w1 localhost 3333 > /dev/null

Second, are there any specific changes that need to be made for 6.3a beyond running tivoncid instead of tivocid?
The hr10-250 with 6.3a is a problem. The older release worked, but the current release has a problem. I am not sure what is causing the problems, but one is that 6.3a does not seem to support the modem lock file. I would be very interested in seeing the ncidd.conf file or the output of ncidd in debug mode: ncidd -Dv4

[summerhome]

Thanks John;

The ncidd.conf is the default file, I have made no changes:
# NCID - Network CallerID Server Config File

################################
# Definitions and Line formats #
################################

# lines can be blank, or start with the words: send, set #
#
# A line is divided into words, separated by spaces
#
# A word is either a string of non-blank characters, everything
# between double quotes, or an equal sign.
#
# SEND LINE FORMAT:
# send DATATYPE [DATATYPE] ...
# where DATATYPE = cidlog, cidinfo
#
# SET LINE FORMAT:
# set ITEM = VALUE [ITEM = VALUE] ...
# where ITEM = cidalias, cidlog, datalog, initcid, initstr,
# lockfile, port, ttyclocal, ttyport, ttyspeed,
# nomodem, noserial, verbose

##########################
# Log file verbose level #
##########################

# Set the verbose level
# The default value is 1, the range is 1-9
# set verbose = 3

############################
# Log and Info for Clients #
############################

# Send the call log to a client when connected
# The default is not to send the call log file
send cidlog

# Send call info (LINE and RING) to a client at each ring
# The default is not to send the call info line
send cidinfo

############################
# NCID Communications Port #
############################

# The default TCP/IP port is 3333
# set port = 3333

#######################
# Alias and Log Files #
#######################

# The default CID alias file: /etc/ncid/ncidd.alias
# set cidalias = /etc/ncid/ncidd.alias

# The default CID call log file: /var/log/cidcall.log
# the log file must exist, ncidd will not create it
# (also make the change in /etc/logrotate.d/ncidd
# and also /etc/ncid/ncidrotate.conf)
# set cidlog = /var/log/cidcall.log

# The default tty data log file: /var/log/ciddata.log
# the log file must exist, ncidd will not create it
# (also make the change in /etc/logrotate.d/ncidd
# and also /etc/ncid/ncidrotate.conf)
# set datalog = /var/log/ciddata.log

#####################
# TTY Configuration #
#####################

# The default tty port: /dev/modem
# set ttyport = /dev/cu.modem # Macintosh OS X
# set ttyport = /dev/ttyS0

# The default tty port speed: 19200
# The tty speed can be one of: 38400, 19200, 9600, 4800
# set ttyspeed = 4800 # NetCallerID port speed

# Ignore tty control signals for internal modems and 3 wire serial cables
# Disable tty control signals: ttyclocal = 1
# Enable tty control signals: ttyclocal = 0 (default)
# set ttyclocal = 1

# The lockfile name is generated automatically
# If tty port is /dev/modem, lockfile is: /var/lock/LCK..modem
# set lockfile = /var/lock/LCK..ttyS0

#######################
# Serial or No Serial #
#######################

# Require a serial device for startup. This is useful if you are
# using a network based plugin
# network: noserial = 1 (do not try to initialize a serial port)
# serial: noserial = 0 (default - Look for a serial port)
# set noserial = 1

#####################
# Modem or No Modem #
#####################

# Obtain CallerID from a CID device or a modem
# device: nomodem = 1 (do not send AT commands)
# modem: nomodem = 0 (default - send AT commands)
# set nomodem = 1

########################
# Modem Initialization #
########################

# The default modem initialization is: "AT Z S0=0 E1 V1 Q0"
# set initstr = "ATE1V1Q0"
#
# Alternate modem initialization string
# set initstr = "AT&FE1V1Q0+VIP"

# The U.S.Robotics USR5631 56K Faxmodem has a +GCI command to set the
# country code to adjust parameters for a particular telephone network
# (perhaps other modems do also). See the following on how to set +GCI
# http://www.usr.com/support/5631/5631-ug/generic.htm
# doc/Modem-init (has a copy of the information needed to set +GCI)

# Addon strings to set modem for Distinctive Ring:
# http://www.modemsite.com/56k/dring.asp
#
# 3Com/USR/TI chipset: ATS41=1
# Reported Ring Codes: RING A, RING B, RING C
# Rockwell/Conexant chipset: AT-SDR=7
# Reported Ring Codes: RING 1, RING 2, RING 3
# Lucent/Agere chipset: AT+VDR=1,0
# Reported DROF/DRON messages: DRON=5 DROF=11, DRON=5 DROF=34
#
# Example adds 3Com DR to the default modem initialization
# set initstr = "ATE1V1Q0S41=1"

# The default for ncidd is to try two CID strings to setup
# CallerID: "AT+VCID=1" and if that fails: "AT#CID=1".
# set initcid = "AT#CID=1"
#
# Alternate CID strings to try if default does not work:
# set initcid = "AT+FCLASS=8;+VCID=1"
# set initcid = "AT-STE=1;+VCID=1"
# set initcid = "AT-STE=1;#CID=1"

#################
# TiVo Settings #
#################
set ttyclocal = 1 # TiVo requires CLOCAL
set ttyport = /dev/ttyS1 # TiVo Modem Port
set lockfile = /var/tmp/modemlock # needed for TiVo Modem Port
#
# To use a modem on the TiVo serial port
# Tivo (stereo mini jack) ->
# -> (stereo mini plug) TiVo serial cable (9-pin male) ->
# -> (9-pin Female) PC modem cable (25-pin Male ->
# -> (25-pin Female) Modem
# if the modem has switches, disable DTR
# Use this string to set the modem before attaching it to the TiVo:
# AT&F0&D0&B1&W
#
# set ttyport = /dev/ttyS3 # TiVo Serial Port
#
# End TiVo Settings


The output from ncidd -Dv4( not in background, not sure if this would make a difference ):
tivo-TiVo# ./ncidd -Dv4
Started: 12/01/2006 14:20
Server: ncidd 0.66
ncidd logfile: /var/log/ncidd.log
Processed config file: /var/hack/etc/ncid/ncidd.conf
Configured to send 'cidlog' to clients.
Configured to send 'cidinfo' to clients.
Processed alias file: /var/hack/etc/ncid/ncidd.alias
Verbose level: 4
CID logfile: /var/log/cidcall.log
Data logfile: /var/log/ciddata.log
TTY port opened: /dev/ttyS1
TTY port speed: 19200
TTY lock file: /var/tmp/modemlock
TTY port control signals disabled
AT Z S0=0 E1 V1 Q0
OK
Try 1 to init modem: return = 0.
Modem initialized.
AT+VCID=1
OK
Modem set for CallerID.
polld[1].revents: 0x1, fd: 5
Client connected, sd: 6, Sent call log: /var/log/cidcall.log
polld[2].revents: 0x1, fd: 6
Client sent text message, sd: 6
MSG: TiVo Test
polld[2].revents: 0x1, fd: 6
Client disconnected, sd: 6
polld[1].revents: 0x1, fd: 5
Client connected, sd: 6, Sent call log: /var/log/cidcall.log
polld[2].revents: 0x1, fd: 6
Client sent text message, sd: 6
MSG: TiVo Test
polld[2].revents: 0x1, fd: 6
Client disconnected, sd: 6
polld[1].revents: 0x1, fd: 5
Client connected, sd: 6, Sent call log: /var/log/cidcall.log
polld[2].revents: 0x1, fd: 6
Client sent text message, sd: 6
MSG: TiVo Test
polld[2].revents: 0x1, fd: 6
Client disconnected, sd: 6
Terminated: 12/01/2006 14:21
tivo-TiVo#


Using ( without the -w1 option, I thought that my busybox was up to date, but the -w option does not exist ):
echo "TiVo Test" | nc -w1 localhost 3333 > /dev/null

The first two nc's were executed just after execution of ncidd, the third was after sitting overnight.
tivo-TiVo# ./ncidd -Dv4
Started: 12/01/2006 14:20
Server: ncidd 0.66
ncidd logfile: /var/log/ncidd.log
Processed config file: /var/hack/etc/ncid/ncidd.conf
Configured to send 'cidlog' to clients.
Configured to send 'cidinfo' to clients.
Processed alias file: /var/hack/etc/ncid/ncidd.alias
Verbose level: 4
CID logfile: /var/log/cidcall.log
Data logfile: /var/log/ciddata.log
TTY port opened: /dev/ttyS1
TTY port speed: 19200
TTY lock file: /var/tmp/modemlock
TTY port control signals disabled
AT Z S0=0 E1 V1 Q0
OK
Try 1 to init modem: return = 0.
Modem initialized.
AT+VCID=1
OK
Modem set for CallerID.
polld[1].revents: 0x1, fd: 5
Client connected, sd: 6, Sent call log: /var/log/cidcall.log
polld[2].revents: 0x1, fd: 6
Client sent text message, sd: 6
MSG: TiVo Test
polld[2].revents: 0x1, fd: 6
Client disconnected, sd: 6
polld[1].revents: 0x1, fd: 5
Client connected, sd: 6, Sent call log: /var/log/cidcall.log
polld[2].revents: 0x1, fd: 6
Client sent text message, sd: 6
MSG: TiVo Test
polld[2].revents: 0x1, fd: 6
Client disconnected, sd: 6
polld[1].revents: 0x1, fd: 5
Client connected, sd: 6, Sent call log: /var/log/cidcall.log
polld[2].revents: 0x1, fd: 6
Client sent text message, sd: 6
MSG: TiVo Test
polld[2].revents: 0x1, fd: 6
Client disconnected, sd: 6
Terminated: 12/01/2006 14:21
tivo-TiVo#

[jlc]

Summerhome,

I assume that the last listing, for overnight, shows messages working while ncidd is ignoring calls. The listings show everything OK so if ncidd is not working then I will assume that somehow the modem turned off the Caller ID mode. I think there is a easy way to check this.

Wait until it appears that ncidd hangs, then do the following:
touch /var/tmp/modemlock
sleep 1
rm /var/tmp/modemlock
The ncidd.log file should indicate ncidd releasing and then using the modem again. After you execute the above command lines, call yourself and see if ncidd is working.

The command lines tell ncidd to detach itself from the modem, wait a second, then reattach itself and initialize the modem. If the modem somehow got out of the Caller ID mode, this will restore it.

[jlc]

NCID version 0.67 has been released.

It mostly fixes TiVo client problems found in the 0.66 release.

NCIDsip has additional options. One is --test so you can test different SIP ports for packets in your network. The other option is --listdevs. This will list all active network devices. It helps when you must specify a network device.

Documentation was improved.

[100Tbps]

Summerhome,

I assume that the last listing, for overnight, shows messages working while ncidd is ignoring calls. The listings show everything OK so if ncidd is not working then I will assume that somehow the modem turned off the Caller ID mode. I think there is a easy way to check this.

Wait until it appears that ncidd hangs, then do the following:
touch /var/tmp/modemlock
sleep 1
rm /var/tmp/modemlock
The ncidd.log file should indicate ncidd releasing and then using the modem again. After you execute the above command lines, call yourself and see if ncidd is working.

The command lines tell ncidd to detach itself from the modem, wait a second, then reattach itself and initialize the modem. If the modem somehow got out of the Caller ID mode, this will restore it.

Thanks for continuing to develop this software! Since the problem is intermittent but service seemingly never returns once it stops working, any suggestion regarding how this should be automated? Or maybe the .67 release is a fix and the timing of the update is not coincidental?

[jlc]

Thanks for continuing to develop this software! Since the problem is intermittent but service seemingly never returns once it stops working, any suggestion regarding how this should be automated? Or maybe the .67 release is a fix and the timing of the update is not coincidental?

I would use a cron job as a workaround. Set it up to run a script with the three commands once a hour or whatever. The problem seems to be that 6.3a does not support a modem lock file anymore or it has another way to indicate when the modem is in use.

The main purpose of the 0.67 release was to fix the TiVoCID and TiVoNCID problems with the 0.66 release, and eliminate the workaround. It also has a improved NCIDsip client to help with configuring it and your network for SIP Invite packets, especially under cygwin. Documentation is a little better also.

Not enough is known about your problem to generate a fix yet, but hopefully the workaround will help for now.

[summerhome]

jlc,

Here are the results of my testing with the things that you had me try( updated to 0.67 ).

The sequence was:
run ncidd -Dv4
nc test - success
make actual call - success
wait for a while
make actual call - fail
nc test - success
make actual call - fail
touch/sleep/remove - success
make actual call - fail
nc test - fail (fails with nc: connect: Connection refused) not sure if I did something wrong here.

The one interesting thing in the logs is the 7092073 line in ncidd.log and ciddata.log. Personal data has been replaced with <removed>. The other thing I noticed is that ncidd was no longer running, but I didn't notice a message that it stopped running and I did not kill the process.

I hope this helps in the debug process, here are the log files:

[jlc]

jlc,
nc test - fail (fails with nc: connect: Connection refused) not sure if I did something wrong here.

The one interesting thing in the logs is the 7092073 line in ncidd.log and ciddata.log. Personal data has been replaced with <removed>. The other thing I noticed is that ncidd was no longer running, but I didn't notice a message that it stopped running and I did not kill the process.

I hope this helps in the debug process, here are the log files:

The nc test failing indicates the server is not running. Not sure why the server should have terminated.

The <removed> indicators is something I have not seen before.

I noticed two things in the ncidd.log file.

One, there is no indication of your touch/sleep/remove sequence. A "TTY in use:" line should be generated by the touch command, and a "TTY free:" line should be generated by the rm command. Either you made a mistake on the lock file name or ncidd is expecting another name. The log file should have two lines:
TTY in use: releasing modem {date & time}
TTY free: using modem again {date & time}
Look at ncidd.conf and make sure this line in the TiVo section is not commented out with a #:
set lockfile = /var/tmp/modemlock # needed for TiVo Modem Port
Two, the ncidd.log file indicates that the modem is not sending the Caller ID at the end. The log file indicates Ring 1 and Ring 2 and no Caller ID information between them. This seems to indicate the modem is loosing the Caller ID mode. Perhaps the modem requires a different init string for Caller ID. Do you know of any information on the modem IC and the command set it supports?

Could you try the touch/sleep/remove test again and make sure the log file records it?

[summerhome]

jlc,

I must have fat-fingered the touch and remove of the lock file. After trying it all again, again there is a weird line in ncidd.log and ciddata.log, this time it is "AT:U70,A100" - I belive that this is the line where ncidd stops responding to the modem. However the creating and removing the lock file seems to release the modem. The <removed> entries are personal information manually removed.

Thanks for your effort in helping to get this working. I will set up a cron job as you suggest for a work-around.

This is the sequence of commands:
tivo-TiVo# echo "TiVo Test" | nc localhost 3333 > /dev/null
tivo-TiVo# echo "TiVo Test" | nc localhost 3333 > /dev/null
tivo-TiVo# touch /var/tmp/modemlock; sleep 1; rm /var/tmp/modemlock
tivo-TiVo# echo "TiVo Test" | nc localhost 3333 > /dev/null
tivo-TiVo#

The following files show the confiuration and log files:

[jlc]

jlc,

I must have fat-fingered the touch and remove of the lock file. After trying it all again, again there is a weird line in ncidd.log and ciddata.log, this time it is "AT:U70,A100" - I belive that this is the line where ncidd stops responding to the modem. However the creating and removing the lock file seems to release the modem. The <removed> entries are personal information manually removed.

Thanks for your effort in helping to get this working. I will set up a cron job as you suggest for a work-around.
When you create the lock file, ncidd will ignore the modem. When you remove the lock file, ncidd will reattach to the modem and initialize it for CID.

It is not ncidd that stopped responding to the modem, it is the modem that quit sending the CID data. The problem becomes how to prevent this. Maybe there is a init sequence for the modem that will prevent it.

Does the modem quit sending the CID after it receives one call, or is it just time related? If it is call related, a simple output module could be developed for ncid to reset the modem every time ringing stops.

[summerhome]

When ncidd stops receiving cid info, it is not related to any of the calls. I have called several times and all call info is sent to ncidd; until I see the "extra" line (which seems to be different each time, from my sample of two); then cid info is not sent for any call received.

More info: it seems that ncidd will crap out after a while, even with touching and removing the lock file. I also didn't see any "extra" lines in the log this time.

TTY in use: releasing modem 12/04/2006 01:17
TTY free: using modem again 12/04/2006 01:17
Modem initialized.
Unable to set modem CallerID: /dev/ttyS1
Terminated: 12/04/2006 01:17
Started: 12/04/2006 03:19
Server: ncidd 0.67

Any other ideas to look into?

[arob]

JLC - Is the NCID/TivoCID client compatible with YAC server broadcasts? Or does it have to use a NCID server?

I have YAC up and running on my network and getting a phone line with CID to my HDTivo isn't in the cards. While the YAC client works on the HDTivo I have display issues with it and am trying to come up with another solution.

[jlc]

JLC - Is the NCID/TivoCID client compatible with YAC server broadcasts? Or does it have to use a NCID server?

I have YAC up and running on my network and getting a phone line with CID to my HDTivo isn't in the cards. While the YAC client works on the HDTivo I have display issues with it and am trying to come up with another solution.

NCID is not compatible with the YAC server broadcasts. Someone was looking at interfacing YAC with the NCID, but I do not know if any work was started. Since the server can now accept CID input from clients, YAC can probably be modified to do this.

[arob]

Thanks John. I'll probably give the NCID server a whirl but in my setup it's a bit of a hassle and redundant. My DSL phone line is a $10 minimum phone line account that is only used by my 2 HDTivo's for dial out. Vonage then rides on the DSL/internet connection and that is where we get CID and the line we use. I have tried using Vonage for the daily call but it is spotty. I have also read that making network calls with a HDTivo on 6.3a is not working or is at least spotty.

From all my reading your NCID prog is working well. I'll give it a try.

[bgreen]

Has anyone else observed artifacts with TivoNCID? After output has been sent to TEXT2OSD and the caller ID info is displayed, Tivo menus "persist" even when they should be sliding in and out from the rights. A minor issue (and probably not NCIDs problem) but I thought I would see if anyone else had the issue.

[arob]

I haven't seen artifacts. In fact after giving up on YAC and plunging into NCID I must say it has worked almost perfectly. There is one nagging issue though.. When ncidd and tivocid are running and I try to dial out either via network or modem it reboots the box (hr10). I work around this but it keeps me from NCID from being a set it and forget it app. I start it via scripts and kill it when not watching.

[jlc]

NCID version 0.68 has been released.

Improvements were made in SIP client, modules and server.

The maximum call log file size can be specified on a command line or in the configuration file.

A YAC gateway and client module were added. NCID can now optain Caller ID information from a YAC server, and NCID can send Caller ID information to YAC listeners.

Documentation was again improved, but needs more work.

[jlc]

The TiVo packages for ncid 0.68 have been updated at sourceforge. The build script for the TiVo packages missed the yac2ncid and yac2ncid.conf files. Please replace the previous package, if you already downloaded it.

[Hichhiker]

The TiVo packages for ncid 0.68 have been updated at sourceforge. The build script for the TiVo packages missed the yac2ncid and yac2ncid.conf files. Please replace the previous package, if you already downloaded it.


I would like to add that there is an issue with yac2ncid gateway running on Tivo in the 0.68.1 package so a temporary patched version is available here (http://www.tivocommunity.com/tivo-vb/showthread.php?p=5277447&&#post5277447)

This fix will be in the next release of the NCID, so if current version of files is beyond 0.68.1, you can safely ignore this message.

-HH

[djl]

What changes need to be made, and to which .conf files, to enable ncid to broadcast to yac listeners? Can this be done while still serving other Tivos in the native ncid format?

[Hichhiker]

What changes need to be made, and to which .conf files, to enable ncid to broadcast to yac listeners? Can this be done while still serving other Tivos in the native ncid format?

I think you need to edit /usr/local/etc/ncid/ncidmodules.conf and all you need to do is list your clients in "YACLIST=" line so if your clients are 192.168.1.2 and 192.168.1.3 you set:

YACLIST="192.168.1.2 192.168.1.3"

You can use DNS names instead of IPs but they have to be resolvable by the box running ncid-yac

Also, ncid-yac is installed just like any other ncid output plugin, and since you can have multiple plugin, you can easily serve both tivos and yac clients from a single NCIDD server

HTH

-HH

[djl]

I set YACLIST, and uncommented extprog="ncid-yac". Then I killed and restarted ncidd and tivocid but no joy. I know I'm missing something minor but haven't found it yet...


I think you need to edit /usr/local/etc/ncid/ncidmodules.conf and all you need to do is list your clients in "YACLIST=" line so if your clients are 192.168.1.2 and 192.168.1.3 you set:

YACLIST="192.168.1.2 192.168.1.3"

You can use DNS names instead of IPs but they have to be resolvable by the box running ncid-yac

Also, ncid-yac is installed just like any other ncid output plugin, and since you can have multiple plugin, you can easily serve both tivos and yac clients from a single NCIDD server

HTH

-HH

[jlc]

I set YACLIST, and uncommented extprog="ncid-yac". Then I killed and restarted ncidd and tivocid but no joy. I know I'm missing something minor but haven't found it yet...
You need to run ncid with the proper options in addition to ncidd and tivocid:
ncid --no-gui --call-prog --program ncid-yac &
TiVoCID is a alias to ncid that uses a display module for the TiVo. The ncid client can only handle one output module at a time, so you need to start another instance of ncid that uses the ncid-yac output module as shown above.

[djl]

Thanks jlc, that did it. Next question: should the alias file be picked up automatically, or does that need a setting change too?


You need to run ncid with the proper options in addition to ncidd and tivocid:
ncid --no-gui --call-prog --program ncid-yac &
TiVoCID is a alias to ncid that uses a display module for the TiVo. The ncid client can only handle one output module at a time, so you need to start another instance of ncid that uses the ncid-yac output module as shown above.

[jlc]

Thanks jlc, that did it. Next question: should the alias file be picked up automatically, or does that need a setting change too?
No need to worry about the alias file. It is only used by the server when a call comes in. All data sent to the clients and logfile will include aliases that were configured. You do need to restart the server everytime you make a change to the alias file.

[djl]

Hmm... is the correct location /var/hack/etc/ncid/ncidd.alias? I ask because it's not picking them up right now (even after restarting everything).
I've got the following in ncidd.conf (I may have changed this without needing to):
set cidalias = /var/hack/etc/ncid/ncidd.alias

Just to be safe, I've been restarting ncidd AND the clients. Strictly speaking, is that necessary? TIA.

No need to worry about the alias file. It is only used by the server when a call comes in. All data sent to the clients and logfile will include aliases that were configured. You do need to restart the server everytime you make a change to the alias file.

[jlc]

Hmm... is the correct location /var/hack/etc/ncid/ncidd.alias? I ask because it's not picking them up right now (even after restarting everything).
I've got the following in ncidd.conf (I may have changed this without needing to):
set cidalias = /var/hack/etc/ncid/ncidd.alias

The location is correct and is the default location so you do not need to set cidalias in the configuration file. Best thing is to stop ncidd and then run it in debug mode at verbose level 5. This will show you where it thinks the alias file is and if it opened it. It will also show you all aliases your created if it reads the alias file. Run it in debug like this:
./ncidd -Dv5
Normally it always runs in verbose level 1. Only use the other levels when troubleshooting. They produce a lot of lines that are normally not needed. I do not know what version you have, but the ncid-0.69 for the TiVo was compiled for /usr/local instead of /var/hack. This was corrected in ncid-0.69-1

Just to be safe, I've been restarting ncidd AND the clients. Strictly speaking, is that necessary? TIA.
This is not necessary, you just need to rerstart ncidd. However, all clients will disconnected and they will start retrying once per minute to connect. Once you restart ncidd, the clients will take up to one minute to reconnect, but you can configure the delay between retries in ncid.conf.

[djl]

Thanks John - The alias problem was all me. I converted my elseed.conf to ncid format, but forgot that elseed was stripping the leading "1" that Vonage puts on all phone numbers. Once I added it to the numbers in ncidd.alias everything worked perfectly.

Is there a limit to how many aliases you can create safely?



Normally it always runs in verbose level 1. Only use the other levels when troubleshooting. They produce a lot of lines that are normally not needed. I do not know what version you have, but the ncid-0.69 for the TiVo was compiled for /usr/local instead of /var/hack. This was corrected in ncid-0.69-1

[jlc]

Thanks John - The alias problem was all me. I converted my elseed.conf to ncid format, but forgot that elseed was stripping the leading "1" that Vonage puts on all phone numbers. Once I added it to the numbers in ncidd.alias everything worked perfectly.

Are you using sip2ncid to get the Caller ID from Vonage? It would be nice to know if someone was using it.

Is there a limit to how many aliases you can create safely?
You can create up to 200 aliases.

[djl]

Are you using sip2ncid to get the Caller ID from Vonage? It would be nice to know if someone was using it.


That's next on the list. BTW, you had a post in the series 3 thread about creating the symlink to /var that allows you to put ncid in any directory. It would be great to give that a prominent place in the docs, as it removes the need for messing around with the config files.
I noticed that I'm getting "nc: Timed out" when calls come in. Everything seems to be working fine, including YAC; is that just a normal byproduct if not all YAC listeners are connected?

[Hichhiker]

That's next on the list. BTW, you had a post in the series 3 thread about creating the symlink to /var that allows you to put ncid in any directory. It would be great to give that a prominent place in the docs, as it removes the need for messing around with the config files.

Personally I always thought it a good idea to put config files in a directory relative to the binary, this way the structure is portable. yac2ncid does that in addition to hard-coded paths.


I noticed that I'm getting "nc: Timed out" when calls come in. Everything seems to be working fine, including YAC; is that just a normal byproduct if not all YAC listeners are connected?

Yes, it is a normal error (if ever there is such a thing). You have to remember that ncid-yac was a byproduct of yac2ncid development and really was done "just because we can" - So it is a pretty dumb in the way it communicates with yac clients. At some point of time it will get fixed, but its not a priority. Is this something that causes problems for you? There is probably a simple way to hide the message, but unless there is a demand for fix, there are more pressing issues to spend time on. :-)

-HH

[djl]

John -
I finally decided to give this a shot, and do have SIP packets forwarding to the Tivo; however, they're not making it the rest of the way to the ncid server. Here's how I'm starting the program:

/hacks/ncid/sbin/ncidd
/hacks/ncid/sbin/sip2ncid
/hacks/ncid/bin/tivocid &
/hacks/ncid/bin/ncid --no-gui --call-prog --program ncid-yac &


If you need it, I can PM my output from sip2ncid --testudp. I've made no changes to config files, other than setting noserial to 1.


Are you using sip2ncid to get the Caller ID from Vonage? It would be nice to know if someone was using it.

[jlc]

John -
I finally decided to give this a shot, and do have SIP packets forwarding to the Tivo; however, they're not making it the rest of the way to the ncid server. Here's how I'm starting the program:

/hacks/ncid/sbin/ncidd
/hacks/ncid/sbin/sip2ncid
/hacks/ncid/bin/tivocid &
/hacks/ncid/bin/ncid --no-gui --call-prog --program ncid-yac &


If you need it, I can PM my output from sip2ncid --testudp. I've made no changes to config files, other than setting noserial to 1.
Your start sequence is good. I would need to see the output of sip2ncid --testudp so I could view the contents of the UDP packets. I should also look at your ncidd.log file for completeness. It would also help me to see the output of "sip2ncid -Dv3" when you call yourself. This debug mode will show the Caller ID packets and the Caller ID line sent to ncidd.

Here is the output of sip2ncid --testudp on my system with the telephone numbers and IP addresses changed to protect the innocent. Please note that these sip packets are sent once every 20 seconds or so:
$ sudo sip2ncid --testudp
Test mode
Processed config file: /etc/ncid/sip2ncid.conf
Verbose level: 3
Network Interface: eth0
Filter: port 10000 and udp
Packet number 1:
Protocol: UDP
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.123.456.78:10000;branch=z3hG4bK-123450c3
From: 555-123-4567 <sip:15551234567@m.voncp.com:10000>;tag=1c7d1d055e128318o0
To: 555-123-4567 <sip:15551234567@m.voncp.com:10000>
Call-ID: a5caf5ef-ae27c37c@10.123.456.78
CSeq: 5871 REGISTER
Contact: 555-123-4567 <sip:15551234567@10.123.456.78:10000>;expires=20
Content-Length: 0

Registered Line Number: 15551234567
Test mode terminated

[whackit]

For the life of me I can't get NCID to function for more than about 24 hours on my boxes.

It works great and then it just craps out. It look likes NCIDD dies when I check ps list.

What to do?

I run it with the yac2ncid server so it's not interacting with modem (as in defined in conf. file).

Using tivocid as display module.

any ideas?

[jlc]

For the life of me I can't get NCID to function for more than about 24 hours on my boxes.

It works great and then it just craps out. It look likes NCIDD dies when I check ps list.

What to do?

I run it with the yac2ncid server so it's not interacting with modem (as in defined in conf. file).

Using tivocid as display module.

any ideas?

More information is needed, especially the version of NCID you are using. The ncidd.log file contains the basic information required so you just need to post it. If it is large, just post from the last 2 or 3 restarts. The log file default is verbose level 1.

See if you can reproduce the dying when you do a ps. If it terminates without a message, increase verbose to level 4 in the config file and, after it dies, either post the log file or email it to me at sourceforge. I assume you removed the comment character from this line in ncidd.conf:
set noserial = 1

[whackit]

here's the log. version .69

yes I have set the serial parameter correctly.

Not sure what is causing this. It happens on both of my machines. I was assuming it was NCIDD since it dissapeared from the PS list but perhaps I am incorrect.

will increase log level and march on.

[jlc]

here's the log. version .69

yes I have set the serial parameter correctly.

Not sure what is causing this. It happens on both of my machines. I was assuming it was NCIDD since it dissapeared from the PS list but perhaps I am incorrect.

will increase log level and march on.
The next release of NCID, 0.70, has a fix to ncidd for a similar problem when using the ncid client under Cygwin. Whenever the client was killed, it also killed ncidd. Attached is a 0.70 prerelease of ncidd for mips. Try it and see if it fixes or your problem. If not, post the log file, using this prerelease at verbose level 4.

Edit: uploaded ncidd configured for /var/hack instead of /usr/local.

[whackit]

The new file seems to be configured for 'nix. I can't for the life of me figure out how to change location of config from command line.

Server: ncidd 0.70pre3
No config file: /usr/local/etc/ncid/ncidd.conf
No alias file: /usr/local/etc/ncid/ncidd.alias

[jlc]

The new file seems to be configured for 'nix. I can't for the life of me figure out how to change location of config from command line.
Sorry about that. I have reconfigured ncidd to use /var/hack and replaced the zip file. You should be able to download and run it now.

[jlc]

This release fixed some problems with the client, the server, and the SIP gateways. New enhancements were also made to the server and SIP gateways. Two output modules were added for the client and most distributions were improved in start/stop and autostart of the client with a output module.

See the Release Notes for specific changes to NCID.

Documentation is a little better and there is now a INSTALL for each distribution.

NCID will also install and run using andLinux after it is installed on Windows. INSTALL-andLinux explains how to do it.

I have also had feedback of a user successfully using sip2ncid with Vonage on the TiVo. It did require some modifications to sip2ncid because Vonage used different SIP packets for him than what they normally used. Perhaps they are changing their system over.

If anyone is using sip2ncid on the TiVo, please post the particluars of how you did it.

[djl]

With the right router, setting up sip2ncid is a snap. I'm using a Linksys RVS4000 with a standard Vonage gateway, wired like so:

Internet --> Cable Modem --> RVS4000 --> VOIP Gateway & Computers

The RVS4000 automatically routes the VOIP packets to the gateway, but it also has built-in port mirroring. (If you have one, look under the heading "L2 Switch"). With the gateway plugged into port 1 and the Tivo in port 2, just mirror port 1 to 2 and you're done.
There are a number of benefits to using sip2ncid:

Removes the final reason for keeping the phone line plugged in
CID information actually pops up BEFORE the phone rings
If you have call-waiting, you get the Caller-ID for the new call even while the previous one is connected



I have also had feedback of a user successfully using sip2ncid with Vonage on the TiVo. It did require some modifications to sip2ncid because Vonage used different SIP packets for him than what they normally used. Perhaps they are changing their system over.

[whackit]

I'm trying to run ncid-yac.

I'm using the line mentioned a few pages ago to run it.

ncid --no-gui --call-prog --program ncid-yac &

and I have set the addresses in the yac section of ncidmodules.conf.

Whenever I call I get the following output in my terminal:

HD TiVo: {/var/hack/share/ncid} % nc: connect: Connection refused

Is there something I am missing?

[jlc]

The connection refused is from netcat. Something is preventing the connection. It could be a firewall, address or port problem.

You can execute the ncid-yac output module directly and show lines as they are executed:
sh -x /var/hack/share/ncid/ncid-yac
It will expect 5 lines of input, you can enter anything one line at a time, I usually enter 1 2 3 4 5, each digit on a separate line. After you enter the last line, the module will show more lines, then exit. If the module found ncidmodules.conf, you will see YACPORT and YACLIST set 2 times. The second time they are set to the values in the ncidmodules.conf file.

Make sure both YACPORT and YACLIST are correct. Also make sure the nc line is correct. For my system, YACLIST=127.0.0.1 and YACPORT=10629, it looks like:
nc -w1 127.0.0.1 10629
If netcat has the correct address and port, it could be your firewall or the YAC Listener.

[whackit]

okay, got that working. not sure why but it just started.

here's my last weird issue. occasionally the clients will quit and when I restart i always get:

couldn't read file "ncid": no such file or directory

Then I go chmod 755 ncid and it works fine. until a quit or restart and I get the same thing when I try to start up. weird.

[jlc]

Then I go chmod 755 ncid and it works fine. until a quit or restart and I get the same thing when I try to start up. weird.
I suspect you might have another version of ncid or a broken symbolic link called ncid in your $PATH so when you try to start it, you get the broken one. Try "cd /" and then "type ncid" to see if it displays the location for ncid. You can also "type -a ncid" to show all ncid locations in its search path.

If I guessed wrong, do "ls -l ncid" before you change permissions and try to start it and see if the permissions really did change.

[whackit]

Only one instance of ncid in my path.

here's the weird thing. permissions are the same (at least listed that way) before and after the chmod. but ncid will only launch after the change.

one more thingthis only happens when I launch "tivocid &" when I launch directly. like "ncid --no-gui --call-prog --program ncid-yac &" it works fine.

[jlc]

one more thingthis only happens when I launch "tivocid &" when I launch directly. like "ncid --no-gui --call-prog --program ncid-yac &" it works fine.
Tivocid is a symbolic link that points to ncid. It is used to set the options needed for the TiVo. A requirement of this is for ncid to be in your $PATH.

I think "export PATH=$PATH:/var/hack/bin ./tivocid &" should work.

[whackit]

Here's what I get, all files have correct permissions:
HD TiVo: {/var/tmp} % cd /var/hack/bin
HD TiVo: {/var/hack/bin} % ls
cidalias cidcall cidupdate ncid out2osd tivocid tivoncid yac2ncid
HD TiVo: {/var/hack/bin} % echo $PATH
/bin:/sbin:/tvbin:/hack/bin:/var/hack/bin:/var/hack/sbin:/hack:/hack/bin:/hack/scripts:/var/hack/bin
HD TiVo: {/var/hack/bin} % tivocid &
[1] 7695
HD TiVo: {/var/tmp} % couldn't read file "ncid": no such file or directory

[1]+ Exit 1 tivocid

[jlc]

You seem to have an unusual problem. Maybe ncid is somewhat corrupt. Try "sh -x tivocid" to see if the shell messages help. You can also try this in place of using tivocid:

ncid --no-gui --tivo --message --call-prog --program /var/hack/bin/out2osd"