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. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    This is a line order problem in the ncid.conf file. It is due to a bug in the tivosh program supplied by TiVo. Easiest fix is to rename it to ncid.conf-bad. The file is located at /var/hack/etc/ncid/ncid.conf

    Code:
    # external called program
    set Program     [list $ProgDir/$EXTPROG]
    If you rather fix the file, move the above two lines to the end of the file. The "set Program ..." line must be last.
     
  2. harpegw

    harpegw Occasional Poster

    235
    0
    Feb 28, 2001
    Northwest...
    That fixed the problem... thanks for the information. Everything is working, I'm going to go play with the /var/hack/etc/out2osd.conf settings.
     
  3. Dec 1, 2006 #103 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    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.
     
  4. Dec 2, 2006 #104 of 282
    MisterEd

    MisterEd Very Large Member

    645
    0
    Jun 6, 2001
    TV Land
    Does .67 do anything with HR10-250 6.3A issues?
     
  5. Dec 6, 2006 #105 of 282
    mskreis

    mskreis New Member

    52
    0
    May 9, 2004
    I just installed version 0.67 over version 0.65 (I believe this was the version included in the zipper) on my HR10-250. I'm also using NCIDpop. Caller information is being displayed on my TV and via NCIDpop. However, none of the calls are being recorded in the log file. I like the ability to view this file. Any suggestions?

    Thanks
     
  6. Dec 7, 2006 #106 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    No, it just fixes other TiVo issues. Version 0.66 uncovered a tivosh bug and the configure file had to be removed for TiVoCID or TiVoNCID to function. Version 0.67 fixes that plus some other minor issues.
     
  7. Dec 7, 2006 #107 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    The call log file is called cidcall.log. It must exist for NCID to log calls. The install package usually creates a zero length file so calls will be logged.

    If you have Perl installed, you can use cidcall to view the log file, or if you installed the NCIDmod package you can use TivoWebPlus to view the call log. Also included in the package is ncidcall, a command line script to view the call log. Cidcall is a Perl script and ncidcall is a tcl script that do the same thing.
     
  8. Dec 7, 2006 #108 of 282
    MisterEd

    MisterEd Very Large Member

    645
    0
    Jun 6, 2001
    TV Land
    :(
     
  9. Dec 7, 2006 #109 of 282
    mskreis

    mskreis New Member

    52
    0
    May 9, 2004
    Yes, I understand this. When I view cidcall.log using either TWP or bash there are no entries despite having received multiple calls.
     
  10. drfever

    drfever New Member

    4
    0
    Nov 11, 2006
    Is there a FAQ for morons on NCID? I got it installed on my tivo, but no idea how to use it. :)
     
  11. JWThiers

    JWThiers Smartypants

    2,611
    0
    Apr 12, 2005
    Cocoa, Florida
    Have you tried reading post #1 of this thread?
     
  12. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    If your Tivo displays calls but does not log them, run ncidd in debug mode at verbose level 4 and make sure the CID logfile line shows the log file you are looking at. The debug output will also indicate if ncidd fails to open the output file. It is possible you have a permissions problem or it is trying to open a file that does not exist. If these suggestions do not help you, could you either post a debug output or email it to me at jlc@users.sourceforge.net?
     
  13. headcase

    headcase New Member

    43
    0
    Jun 27, 2005
    Raleigh, NC
    I've got two HR10-250's running freshly zippered InstantBake 6.3b images, running fine. I'm able to start up the version of NCID that came with the zipper installation on each box, and display the caller ID on that particular box just fine when that box is directly connected to the phone line.

    My problem is, when I try to start up TIVOCID on a box striclty as a client pointing to the other box, I get a timed out error:

    tivocid -R -V 192.168.2.101
    Connecting to 192.168.2.101:3333
    192.168.2.101:3333 - error reading "sock10": connection timed out
    Connecting to 192.168.2.101:3333
    192.168.2.101:3333 - error reading "sock10": connection timed out
    Connecting to 192.168.2.101:3333
    192.168.2.101:3333 - error reading "sock10": connection timed out
    Connecting to 192.168.2.101:3333

    I'm assuming I'm running the lastest version of NCID (.67), since I just installed this via zipper , but I'm not sure how to check the version. As I'm a bit of a Linux newbie, any tips on next steps would be great.
     
  14. headcase

    headcase New Member

    43
    0
    Jun 27, 2005
    Raleigh, NC
    Well, I did a little digging on my TiVo's, and in the NCID directory, I found the release notes and answered one of my questions. Looks like the zipper installed v.65 of NCID.

    So any next steps recommended?
     
  15. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    You are running the latest version of NCID. You do not need the -R option, but otherwise your command line is good.

    The error you are getting indicates that the client is not seeing the server. This usually indicates either the server is not running or there is a network problem.

    If it is the server aborting, it probably means the phone line is not connected. Maybe it is connected to he TiVo you want to use as a client. If server OK, then check network, check IP addresses using 'ifconfig' on each TiVo. Try to ping each TiVo from each box.

    Hope these suggestions help, or at least point you in the right direction.
     
  16. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    Install the latest version. There was a problem with the client and it might be effecting you. You can install over zipper, but save your config files if you made any changes.
     
  17. luder

    luder New Member

    245
    0
    Sep 7, 2006
    Chicago, IL
    I have two questions. I took a good look at box today and I notice the modem uses four copper lines can ncid use all four copper lines? Second can this handle voip caller id thanks..
     
  18. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    NCID can only handle one modem at a time. If the modem supports distinctive ring lines, NCID does also. I expect if the modem handles multiple POTS lines NCID will also, but no one has tried this as far as I know.

    NCID does handle multiple VoIP lines using a SIP client instead of a modem. The SIP client requires libpcap, Perl, and two Perl modules to function on the TiVo. No one has ported the Perl modules to the TiVo, so the SIP client only works on Linux, Cygwin, and the Macintosh. Once the Perl modules are ported, the SIP client should be functional.
     
  19. cheer

    cheer Registered Offender

    1,406
    0
    Nov 13, 2005
    Gurnee, IL
    For what purpose? Anyway it's not up to NCID; it's up to the modem in question. But if you're thinking for multiple phone lines...probably not.
    Yep.

    EDIT: jlc beat me to it.
     
  20. luder

    luder New Member

    245
    0
    Sep 7, 2006
    Chicago, IL
    your both right
    i ran multiple tests using 2 pots line and the result is the modem only listens in line 1 ..
     

Share This Page