1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Network Caller ID (NCID)

Discussion in 'TiVo Underground' started by jlc, May 21, 2003.

  1. Jun 25, 2006 #41 of 282
    Hichhiker

    Hichhiker Just me.

    480
    0
    Apr 21, 2002
    This should be an obvious thing, but when you change software on tivo, remove it from autostartup until it works fine. Case in point, after upgrading a zippered dtivo to NCID 0.64, I lost bash shell on both serial and telnet after reboot. Looking into it, it appears somehow starting ncid locks it up.

    In case any of you run into this, here is a way to resolve this situation without removing hdd - it appears there is a few seconds window between starting bash shells on telnet and serial and starting of ncid. If you time it just right, you can execute a small script in that time to remove ncid from rc.sysinit.author(renaming ncid on hdd may work too, but I did not try this). I used my telnet client's "login scripting" feature to automate the commands, but any method for executing commands on login should work, if you time it right. Serial cable makes timing a lot easier.

    HTH

    -HH
     
  2. Jun 25, 2006 #42 of 282
    roydarc

    roydarc New Member

    3
    0
    May 10, 2006
    Picayune, MS
    Thanks for the info.. will definitely read. But... I think for now I will wait on rbautch to do his upgrade before attempting it on my own...Again thanks!
     
  3. Jul 1, 2006 #43 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    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.
     
  4. Jul 1, 2006 #44 of 282
    rpdre1

    rpdre1 New Member

    273
    0
    Feb 20, 2005
    Do you get Call Waiting Caller ID by using NCIDsip?

    My regular phone shows it every time but it's never displayed on my tivo .. NCIDpop has spoiled me :p
     
  5. Jul 1, 2006 #45 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    NCIDsip will respond to Call Waiting.

    Modems may not have that feature. The NetCallerID standalone device does support it.
     
  6. Jul 1, 2006 #46 of 282
    rpdre1

    rpdre1 New Member

    273
    0
    Feb 20, 2005
    i just read through the docs and realized I have to compile those 2 modules to use NCIDsip on my tivo.

    since nobody has made a binary yet for those modules, can someone teach me how to make the necessary binaries?
     
  7. Jul 1, 2006 #47 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    This is the hard part. NCIDsip is a perl script. It requires Perl, the Net-Pcap Perl module, and
    libpcap. I have found a Perl binary for the TiVo, but I did not find binaries for the module or library. Here is where to get the software:

    Perl for TiVo Series 2: http://marc.abramowitz.info/archives/2004/12/18/perl-for-tivo-series-2/
    Net-Pcap: http://search.cpan.org/~saper/Net-Pcap-0.12/Pcap.pm
    libpcap: http://libpcap.sourceforge.net/
     
  8. Jul 16, 2006 #48 of 282
    floppy_joe

    floppy_joe New Member

    3
    0
    Oct 15, 2005
    I always know I am in trouble when I catch up to the posts that have current dates.

    This ncidsip sounds just what I've been dreaming of, problem is the lack of knowledge on my part and documentation on installing perl, net-Pcap and libpcap.

    I have a hughes s2 dtivo and and sat-t60, I put the above files in /var/hack and untarred them. What next? Fell free to flame away, im use to it and trust me I have searched and searched. Thanks for your pity.
     
  9. Jul 25, 2006 #49 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    The Perl link is a binary so you would put it in /var/hack/bin. The links to Net-Pcap and libpcap are to source code that needs to be compiled. I did manage to cross compile libpcap, but it is untested. I was not able to cross compile Net-Pcap, so I expect it needs to be compiled on a Series 2. Maybe if someone has gcc and Perl on a Series 2, he could compile libpcap and Net-Pcap and make the binaries available.
     
  10. Aug 28, 2006 #50 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    OUT2OSD version 0.9 has been released. It works with all versions of NCID

    OUT2OSD uses libosd to display text on the TiVo. Libosd has been fixed to work with TiVo OS 7.X.
    It should work with all hardware except series 2.5 and newer. The display has problems with menus and applications, but works fine otherwise. See the NCID home page.
     
  11. Aug 28, 2006 #51 of 282
    rbautch

    rbautch User

    3,629
    0
    Feb 5, 2004
    Chicago, IL
    Would it run on a prom modded series 2.5 running 7.x?
     
  12. Aug 29, 2006 #52 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    OUT2OSD will not run on a prom modded series 2.5 running 7.x. Work is continuing on libosd so I expect the problem will be solved. Also, the next release of NCID will include a output module that uses /tvbin/text2osd to display text. This one should run on all TiVo hardware, including the series 2.5. The curious part is this TiVo text display program has the same menu and application problems that OUT2OSD has.
     
  13. Aug 29, 2006 #53 of 282
    EvilMidniteBombr

    EvilMidniteBombr what bomz at midnite

    1,714
    0
    May 25, 2006
    Parts...
    When you say "all TiVo hardware" does that mean all TiVo hardware that is hackable or does it truly mean all TiVo hardware. I'd really love to have this available on my unhackable RS-TX20. Purty puhleeeeze???
     
  14. Aug 29, 2006 #54 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    Yes, I meant all TiVo hardware that is currently hackable. The NCID client must reside on the TiVo, the server can reside elsewhere.

    I think a client can be made as a application and run on a unmodified TiVo, but I do not know if it can be started and stay running when you switch to watch a show. If anyone is interested in doing such a client and experiment with it, the source for NCID contains documention on the protocols used and guidelines to writing a client. I intend to look into this, but have not had the time so far.
     
  15. Aug 30, 2006 #55 of 282
    EvilMidniteBombr

    EvilMidniteBombr what bomz at midnite

    1,714
    0
    May 25, 2006
    Parts...
    DRAT!

    Thanks for the answer though. :)
     
  16. Sep 1, 2006 #56 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    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.
     
  17. Sep 30, 2006 #57 of 282
    Runch Machine

    Runch Machine New Member

    1,048
    0
    Feb 7, 2002
    Minneapolis
    With the Directv upgrade to 6.3a on HD-Tivo HR10-250 I find that the receiver reboots when trying to dial out. If I comment out the lines in the author file that start the NCID program, the problem goes away. A few other people have posted having the same problem. It happens on both of my HD Tivos.

    To be clear, if I tell the Tivo to make a test call, it trys for a few minutes and says modem not responding, unplug the receiver to reset the modem. After this message Caller ID doesn't work.

    Alternately, if I tell the Tivo to dial out and connect with the service, it sits on prepairing to dial out for a minute or so and then the system reboots.

    I'd appreciate any suggestions you have for fixing this. My Tivos were hacked using RBatchs scripts. I used the Slicer 1.3a to update to activate the 6.3a update.
     
  18. Sep 30, 2006 #58 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    Have you tried to kill ncidd with the kill command after it starts and see if it can dial out? What version of NCID are you using?

    Your test call results in a message that that says to reboot the receiver, so I would try to call again after ncidd was killed using the kill command.

    This seems like the TiVo rebooted itself to fix the modem.

    There are two things you could try. The first is to be sure you are using version 0.66. This version fixes the server so it should always restart the modem after a dial out. Different fixes for this have been in previous versions, but none always worked until the current fix. The second is to make sure that the lockfile is set properly. For TiVo distributions, the lock file is set in ncidd.conf:

    Code:
    set lockfile = /var/tmp/modemlock
    Its possible that the cause of your problem is that the lockfile name changed with the upgrade to 6.3a . When the TiVo dials out, it creates this lock file which tells ncidd to ignore the modem. When the lock file goes away, this tells ncidd to reinitialize the modem and again monitor for caller id. Make sure the lockfile name and location is still correct, if not, change it. You can look at ncidd.log and see if there is a waiting message which would indicate it saw the lockfile when the TiVo tried to dial out.

    I have had a report about ncid (tivocid and tivoncid) not working in version 0.66, but it is unclear if this is due to a corrupted configuration file, so if it does not work, use your current ncid client in place of the one in version 0.66, but if you do this, tivoncid will not work, only tivocid. I have also had a report of a TiVo random reboot that seems to be fixed by a upgrade to version 0.66.
     
  19. Sep 30, 2006 #59 of 282
    mrbubbles

    mrbubbles New Member

    51
    0
    Apr 12, 2003

    Wow, excellent information. I am having the same problem as Runch. I upgraded to 0.66 (I was definately on some older version) but the problem remains. I checked and during the call, there is no modemlock file in /var/tmp/ and I don't see any other lock file that is created at that time in /var/tmp. I checked my old T60 with ncid on it and I see the modemlock file in /var/tmp when I call in. So, I think that is the problem. I did some searches for modemlock using ffind during the call but couldn't find it anywhere. How do we track down where the lock file is?

    Thanks again for your help.
     
  20. Sep 30, 2006 #60 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    Normally the lockfile name is based on the TTY port used. Linux will normally create it in /var/lock. If you are using ttyS0, the lock file will be /var/lock/LCK..ttyS0. If you are using ttyS3, the lockfile will be /var/lock/LCK..ttyS3. Tivo did not follow that convention, but ncidd does. Make sure to comment out any lockfile line in ncidd.conf and ncidd will build the lock file as above, based on the TTY port used. Dial out and see if a lock file is generated in /var/lock, with any luck, 6.3 will use the normal lockfile convention. If not, dial out and search for a name using the TTY port. If it only appears during dial out, it is the lock file name to use.

    I have more information on the ncid client in version 0.66. If it does not run, remove the ncid.conf file (you can rename it so ncid does not use it). This seems to fix it .
     

Share This Page