Nice work and FAST! And best of all the screens on HME are not messed up.

Click to expand...

Does NCID / NCIDD mess with HME screens? I'm looking into HME and trying to figure out where to start. I finally just got NCID / NCIDD posting caller-id (seemed to work fine with 6.3b, 6.3c things were messed up again).

Not to drift too far off-topic, but can you start a new thread or place a link here to another one describing if you went with JavaHMO or were able to get Galleon working?

I've successfully set up the latest version of ncid and tivoncid to run on my primary zippered Series 2, and I can also successfully run tivoncid on my second zippered Series 2 box, pointing back to the first box.

But when I try to run tivoncid on my PTVnet (non-zippered) HR-250 w/6.3d, it gives me the following:

I've successfully set up the latest version of ncid and tivoncid to run on my primary zippered Series 2, and I can also successfully run tivoncid on my second zippered Series 2 box, pointing back to the first box.

But when I try to run tivoncid on my PTVnet (non-zippered) HR-250 w/6.3d, it gives me the following:

I've used YAC on my home network for quite a while and always liked the simplicity of setup and use. Even my wife can use it.

I've had NCID working on my HDTivo before but that damn modem causes stability issues (at least for me it did). The feature set of NCID has always been impressive.

And now you guys have married the two and voila, CID works like a charm and is stable. After a few tweaks of the out2osd.conf I have both my HDTivo's dialed in displaying CID perfectly. Thanks, thanks, thanks. While it may seem like a trivial add-on once you get used to it there is no going back. We watch tv and movies mostly in our home theater where it is dark and the phone doesn't display easily what is coming in. Hell just remembering to bring the phone is a miracle.

The only thing I can recommend is putting ncidd, out2osd, tivocid, tivoncid, yac2ncid and basically anything and everything people might want to run this in one tarball and instruct them to copy it /var and tar it off. Also I'd just have all the executables extract to /var/hack/bin but maybe that's just me. i only suggest these things to ease the simple support questions that always come your way. Hell since I didn't read and docs maybe I better check the instuctions before blabbing.

The only thing I can recommend is putting ncidd, out2osd, tivocid, tivoncid, yac2ncid and basically anything and everything people might want to run this in one tarball and instruct them to copy it /var and tar it off. Also I'd just have all the executables extract to /var/hack/bin but maybe that's just me. i only suggest these things to ease the simple support questions that always come your way. Hell since I didn't read and docs maybe I better check the instuctions before blabbing.

Click to expand...

John is working on something that will blow the doors off of that idea and may even completely change Tivo hacking as we know it... but I probably said too much ;-)

If anyone running 6.2 wants easy access to their caller-id history, they can use my cidrss module for TivoWebPlus. It reads the NCID log (or elseed, if you're using that) and outputs it as a feed which can be sent to any computer, or back to your tivo via JavaHMO. There's now a link for it on the NCID page, or go directly to my software page here.

100Tbps said:

Not to drift too far off-topic, but can you start a new thread or place a link here to another one describing if you went with JavaHMO or were able to get Galleon working?

It looks like many basic utilities are missing - which is normal for stock tivos - and the netcat version you have is not fully functional. No worries though - your best bet is to install busybox for S1 tivo and make sure it is in the path before you start yac2ncid. Busybox will include its own netcat as well.

It includes a new SIP gateway, sip2ncid, to replace ncidsip so Perl is no longer required. VoIP support for the TiVo is available when the package is installed. Check out the Release Notes for other improvements and fixes. This is the first release of sip2ncid in the wild, so there may be some problems.

You should look at the Setup-sip2ncid file on the ncid page, not the home page, to see how to configure sip2ncid and ncidd. The FAQ should also help. The hardest part is that you may have to configure your network and check a couple of SIP Invite ports.

On my home LAN, SIP packets were on port 6051, but are now on port 10000. This is for Vonage using a Linksys RT31P2 router. The computer running sip2ncid had to be in the DMZ zone, in order to receive the SIP packets. Port forwarding did not work.

You need to be very careful if you put a TiVo in a router DMZ zone. Make sure your telnet and ftp is password protected, better yet use ssh.

If anyone uses SIP on the TiVo, please provide feedback giving the VoIP company name, the SIP port, the phone hardware, and the network setup.

I should soon release a package of NCID that uses a package manager to install and update it. It will also contain ssh and other Linux utilities. Adding, removing, and updating packages should be very easy.

I have been using Packet8 (VOIP) for a few years so I didn't even think about trying to get this or anything else like it to work with my DirectvTivos (A few Directv Series 2 and one HR10-250). I got my first HR20-100/700 receiver this last summer. Knowing that the HR20 by default has Caller ID I decided to try it. It worked! CAller ID on the screen when using the HR20 and Packet8 Voip.

Yesterday I started looking to spread the fun to my HR10-250. I have all my units hacked with the Zipper. I scanned over this thread. I uninstalled the script included with the Zipper and reran the install to include the NCID installation. I tried it and WHOAAA Caller ID on my HR10-250 with no really no thinking on my part! ;-) You can't ask for more!

I installed the NCIDPOP (CLIENT) on a few of my Windows XP and Windows Vista PCs. It works on there too!

Of course I have one problem and a question.

Looking at the CIDCALL.log file via Tivowebplus shows no history of calls and a file size of zero.

I installed the Tivowebplus add-on (post 171 above). When I click on the Caller-ID link there it comes back with an error -

The ncidd server will not create a log file, if one does not exist. You indicated the name was CIDCALL.log when the name should be cidcall.log (all lowercase). Maybe
that is the problem. If not, check ncidd.conf and make sure the name or location of the cidcall.log file did not change.

The tcl script error message you posted seems to indicate a problem with the module. Hopefully djl25 can help you with it.

Sorry I was just using all caps for emphasis..sorry forget Linux/Unix is case sensitive. Yes it is all lowercase. I let it install using Rbautch's script and it worked right away with no further action needed on the HR10-250.

I did notice the line set cidlog = /var/log/cidcall.log had a # in front of it and removed the #. Maybe the file will be created now? I am not a pro with this stuff so I hope the real brains here can help!