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...
    NCIDmod contains 2 command line scripts to view the NCID Caller ID log and the server log. It also contains a TivoWebPlus module to view the Caller ID log.

    DJL25 updated the module so it works with any version of TWP. It also finds the Caller ID log file in various locations.

    If you just want view the log file, you can use the ncidmod module. If you want extra features you can use the cidrss module by David.
     
  2. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    The NCID server has been enhanced to support modem output that only consists of a number or name without a date or time.

    The SIP gateway was enhanced to indicate when sip packets are not being received in 1 minute intervals. This makes it easier to configure the SIP gateway for your network, and it alerts you when SIP packets stop for some reason.

    See the Release Notes for all the changes.
     
  3. djl25

    djl25 C64 hacker

    95
    0
    May 26, 2005
    Providence, RI
    Just to clarify: cidrss is bundled with TivoWebPlus 2.1x and is not compatible with earlier versions. As John said, NCIDmod will work with any TWP, or at least 1.3.1 and up.


     
  4. Nov 7, 2009 #244 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    This NCID (Network Caller ID) release fixes problems with the server, SIP gateways, and client. It also adds a new option to the SIP gateway, and a new client output module.

    The server has four important fixes:
    • a corruption problem when sending log files over 2.000 lines
    • a call identification problem for ring and hangup
    • a client causing the server to terminate (this is the reason why the server sometimes dies on the TiVo, scripts to automatically restart the server are no longer needed)
    • the sending of a call duplicate to clients when both a MESG and NAME line was received from a modem.

    The SIP gateway has two important changes:
    • a telephone line label was added to call termination information
    • a option was added to warn if no SIP packets are received in 90 seconds (for troublesome routers that quit sending SIP Invite packets until reset)

    The client has two important changes:
    • a call identification problem on ring and hangup for simultaneous calls
    • the UTF-8 encoding is set because it is not the default in Windows

    The long requested hangup feature was released as a client output module. It uses a modem to hangup the call but works with any NCID gateway. If a call shows a name or number from a blacklist, it will hangup the call and log it. This module requires minicom which is not yet available for the TiVo.

    For a complete list of features and the release notes, see http://ncid.sourceforge.net
     
  5. spnewman

    spnewman New Member

    42
    0
    Feb 14, 2007
    Wisconsin
    I recently updated my ncid to 0.75. Works well, but the program still terminates itself. Is there a log file I can check to see why this is happening?

    Thanks
     
  6. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    I discovered a windows client that was able to terminate ncidd and fixed the problem in 0.75, I assumed this was the cause of the TiVo terminations since I could never reproduce them.

    Check the ncidd.log file to see if it gave a reason for the termination. Are you sure it is the server terminating and not hung? Does it happen often? or at regular times?
     
  7. spnewman

    spnewman New Member

    42
    0
    Feb 14, 2007
    Wisconsin
    It does not say anything about the program being terminated in the log, it seems to stop working after multiple calls. I then have to restart it in order for it to work again.
     
  8. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    Its acting the same as before. Which TiVo are you using? Email me, at sourceforge, a copy of the ncidd.log file where ncidd stopped working and you did a restart.
     
  9. Soapm

    Soapm Active Member

    1,564
    0
    May 9, 2007
    So close,...
    I thought I had it fixed but I guess something strange is happening with my caller id. It seems to be turning itself off.

    I can turn it back on by manually executing the commands in my INIT file but once it's back on the TIVO locks up tight when the phone rings. I have to unplug it to get it to reboot. The CID will work for the first coupe of reboots with the same problem but after several reboots it doesn't start up anymore.

    If this was an old windows machine I would think I had an IRQ conflict with the modem.

    Its been working for close to a year with no problems and this just started about a week ago. Nothing new installed.

    I have a 649DT hacked with Sapper.

    What logs should I be looking in to find clues?
     
  10. Soapm

    Soapm Active Member

    1,564
    0
    May 9, 2007
    So close,...
    I did a mfsassert -please last night before I went to bed and things seem to be okay so far today. No reboots or freeze ups and the CID has been working. I have my fingers crossed.
     
  11. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    When there are problems, first look at ncidd.log. If the server died, hopefully it will tell you why, if the server is hung it should still appear in the process table. If it seems hung, look at cidcall.log and see if it recorded the call. If it did the problem is with the client, if not the problem is either the server or the modem. If you created the ciddata.log file, it contains all the output from the modem. If a call is recorded here but not in the cidcall.log file, then the server is at fault. If you only see ring in the ciddata.log file then the modem is not set for Caller ID or maybe does not support it.
     
  12. Soapm

    Soapm Active Member

    1,564
    0
    May 9, 2007
    So close,...
    Thanks JLC, looks like all my logs along with my VAR partition were wiped when I did the file system fix. How do I create the cidcall.log and make sure it is running if this happens again?
     
  13. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    The cidcall.log file is created by ncidd if it does not exist in NCID version 0.73 or later.

    You can check if any NCID programs are running with:
    Code:
    ps ax | grep ncid
    
     
  14. Soapm

    Soapm Active Member

    1,564
    0
    May 9, 2007
    So close,...
    Looks like I am using v0.67. Do I have any reason to upgrade?
     
  15. Soapm

    Soapm Active Member

    1,564
    0
    May 9, 2007
    So close,...
    It stopped working again.

    I see this when I do PS AX

    2801 ? Z 0:00 [out2osd] <defunct>

    Something is inconsistent comparing my cidcall.log to my ncidd.log. I see calls in one that is not in the other and visa versa.

    What all do I have to upgrade to move to a later version?
     
  16. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    You need to upgrade from your old version to the current version to get fixes specific to the TiVo. See INSTALL-TiVo.txt to help you install it. Before you do, save a copy of all the configuration files in /var/hack/etc/ncid. After you install the new package modify the new configuration files with any changes you made in the old ones. Chances are you did not need to make any changes or you only modified ncidd.conf. Do not replace the new configuration files with old ones, keep the ncidd.conf verbose level at 1.

    If there is a newer version of out2osd, install it also.
     
  17. Soapm

    Soapm Active Member

    1,564
    0
    May 9, 2007
    So close,...
    This is what I got trying to start it up. Any thoughts?

    Code:
    4629 ttyp0    R      0:02 tivosh /var/hack/bin/ncid --no-gui --tivo --mess
    4630 ttyp0    S      0:00 tivosh /var/hack/bin/ncid --no-gui --tivo --mess
    4631 ttyp0    S      0:00 tivosh /var/hack/bin/ncid --no-gui --tivo --mess
    4632 ttyp0    S      0:00 tivosh /var/hack/bin/ncid --no-gui --tivo --mess
    4633 ttyp0    R+     0:00 ps ax
    [3]-  Exit 151                ./ncidd  (wd: /var/hack/sbin)
    (wd now: /var/hack/bin)
    bash# 127.0.0.1:3333 - error reading "sock13": connection refused
    Here are the commands I used.

    # starting NCID CallerID
    touch /var/log/cidcall.log &
    cd /var/hack/sbin; ./ncidd &
    cd /var/hack/bin; ./tivocid &
     
  18. Soapm

    Soapm Active Member

    1,564
    0
    May 9, 2007
    So close,...
    It seems to be ok now after a couple of reboots. Thanks
     
  19. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    It looks like you tried to start NCID multiple times. When you have multiple client processes you need to either kill them or reboot.

    Starting with NCID-0.72 a startup script is provided called "startncid". It will start ncidd and tivocid. It can be configured to start tivoncid in place of tivocid and to start sip2ncid, yac2ncid, ncid-yac, or ncid-page. The local timezone can also be set so when using the gateways, the local time is displayed for the call. It can be called from rc.sysinit.author or manually (/var/hack/bin/startncid).
     
  20. Soapm

    Soapm Active Member

    1,564
    0
    May 9, 2007
    So close,...
    Do I still need the

    touch /var/log/cidcall.log &

    command or can I just use

    /var/hack/bin/startncid rmpid

    and it will start the whole shebang...
     

Share This Page