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. Nov 9, 2007 #181 of 282
    rbautch

    rbautch User

    3,629
    0
    Feb 5, 2004
    Chicago, IL
    The current Zipper uses TWP v2.0.0, and NCID v0.67.
     
  2. Nov 9, 2007 #182 of 282
    BTUx9

    BTUx9 back?

    1,596
    0
    Nov 13, 2003
    Rockport, MA
    but as I said in my first post, the latest ncid module is only compatible with TWP bundles made since 8/07. (It relies on a proc - bodytext - that was added to CVS on 7/29)

    Much of this confusion will HOPEFULLY be improved when the TWP beta goes mainstream... it introduces compatibility checking for modules. (a module will need to state what version(s) it's compatible with)
     
  3. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    You did not need to uncomment the cidcall.log line in the ncidd.conf file. It defaults to /var/log/cidcall.log. You do need to make sure the file is there and that its permissions are OK. Touch will create it, if it is missing:
    Code:
    touch /var/log/cidcall.log
    ls -l /var/log/cidcall.log
    The permissions should be: -rw-r--r--
     
  4. djl25

    djl25 C64 hacker

    95
    0
    May 26, 2005
    Providence, RI
    BTUx9 is absolutely right; cidrss only works with TWP 2. The current version is cidrss_v3_1_03(b1) and it works with (almost) all 2.x versions, although be advised that RSS feeds under TWP2.1.b2 are currently broken.
    You can PROBABLY get an RSS feed from cidrss with pre-2.0 TWP (I've never tried) but definitely not the web view. Future versions may rely on TWP for RSS functions too, making even that impossible with older versions.


     
  5. MrPib

    MrPib New Member

    19
    0
    Sep 18, 2002
    Hi. I have a zippered HDVR2 with a working 0.69 NCID install. That is, I get CID messages for my landline (which happens to be via FiOS). I'm trying to get sip2ncid working with my VoIP line, which is through Broadvox Direct. I'm not getting very far. I know that my ethernet device is eth0:

    Code:
    Main_DTiVo# ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:14:6C:85:F4:0B  
              inet addr:192.168.0.200  Bcast:192.168.0.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:835874 errors:9 dropped:0 overruns:0 frame:1
              TX packets:1598818 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:100 
              RX bytes:548119409 (522.7 Mb)  TX bytes:2067490632 (1971.7 Mb)
    I have But sip2ncid doesn't seem to like that device:

    Code:
    Main_DTiVo# sip2ncid  -C /var/hack/etc/ncid/sip2ncid.conf -i eth0 -T
    Test mode
    Skipping: set interface    From config file: /var/hack/etc/ncid/sip2ncid.conf
    Processed config file: /var/hack/etc/ncid/sip2ncid.conf
    Verbose level: 3
    Network Interface: eth0
    pcap_open_live(): socket: Address family not supported by protocol
    Test mode terminated
    Any help would be appreciated.
     
  6. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    If you are using a configuration file with a problem like this, you should also list it. Better yet, do not use one and only use command line options when testing. Then if it works, the trouble is in the configuration file. The error message suggests that a address is specified and it does not like it. If you did give one, it is in the configuration file.

    You might want to list out the interfaces: sip2ncid -l
    and see if eth0 will list out.

    You should do the test without the -C option to see if the configuration file is causing your problem.

    I noticed you were specifying the configuration file when it should be the default, but trying it here, I see the default location is wrong. That will be corrected.
     
  7. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    The binary package for the TiVo mips hardware was built with an incorrect default for the configuration files.. A corrected binary package was just released as ncid-0.69-1.mips-tivo.tgz. Please replace the older package. It also corrects the sip2ncid help option to display one option as '-P' instead of '-p'.
     
  8. MrPib

    MrPib New Member

    19
    0
    Sep 18, 2002
    Thanks for the quick reply! Ok, I installed -1 (and thanks for fixing that.)

    Back to my tale of woe. -l doesn't show anything:

    Code:
    Main_DTiVo# sip2ncid -V
    sip2ncid: Version 0.5 (NCID 0.69)
    Main_DTiVo# sip2ncid -l
    
    -T gives the same error as before, with or without -i:

    Code:
    Main_DTiVo# sip2ncid -T
    Test mode
    Processed config file: /var/hack/etc/ncid/sip2ncid.conf
    Verbose level: 3
    pcap_lookupdev(): no suitable device found
    Test mode terminated
    Main_DTiVo# sip2ncid -i eth0 -T
    Test mode
    Processed config file: /var/hack/etc/ncid/sip2ncid.conf
    Verbose level: 3
    Network Interface: eth0
    pcap_open_live(): socket: Address family not supported by protocol
    Test mode terminated
    
    The config file is the stock one, and has nothing set:

    Code:
    Main_DTiVo# cat /var/hack/etc/ncid/sip2ncid.conf | grep -v "^#" | strings
     
    I'd also like to take a moment to thank you for your work on this package. It's very much appreciated. [The kids flipped when they first saw the CID boxes come up!]
     
  9. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    I am not sure what the problem is. The '-l' list option should at least list the loopback device.

    Here is what sip2ncid -l returns on my Series2:

    Code:
    # sip2ncid -l
    eth0 : No description available
    any : Pseudo-device that captures on all interfaces
    lo : Loopback device
    
    I will do more research into your problem over the weekend. I am assuming that you are able to use other network programs OK. I did notice that your ifconfig command did not list the lo device. If you did not edit it out in your post, you need to add it.

    Thanks for the good word on NCID. It is appreciated.
     
  10. MrPib

    MrPib New Member

    19
    0
    Sep 18, 2002
    Well, I appreciate you looking into it. Yeah, I edited out the lo device. Also, I tried sip2ncid on my other 2 DTiVos, and got the same results.
     
  11. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    Do you know what kernel version your DTiVos use? You can cat /proc/version to get it.
     
  12. MrPib

    MrPib New Member

    19
    0
    Sep 18, 2002
    Hi John.
    Code:
    Main_DTiVo# cat /proc/version
    Linux version 2.4.20 (build@buildmaster5) (gcc version 3.0) #22 Fri Feb 20 18:19:25 PST 2004
    It's AlphaWolf's 6.2 image (62small.mfs) , zippered, with BTX's 6.2->6.2a patch applied.
     
  13. Hichhiker

    Hichhiker Just me.

    480
    0
    Apr 21, 2002
    On John's request I have looked into the issue - seems that af_packet kernel module is not loaded on S2 DTivos by default - so the simple solution is:

    Code:
    # insmod /lib/modules/af_packet.o
    The catch is - (there is always a catch) - I have no idea if af_packet.o kernel module ships with tivo or it was installed when I Zippered my Dtivos. (the down side of using someone else's scripts) As I have no un-zippered DTivos to test on, and I have not researched the matter, you are on your own to locate the kernel module if you are missing it - but it should definately be on all zippered boxes.

    That being said, the only other catch is that you should add that insmod line to your system startup scripts, as it will only work until next reboot. There is might be a better way to make sure the kernel module is loaded on boot time but my mind is currently far from Linux kernel and Tivo's "distro" so thats another homework exercise for you all.

    Enjoy

    -HH
     
  14. MrPib

    MrPib New Member

    19
    0
    Sep 18, 2002
    THANK YOU!! That did it! I hope you didn't waste too much time figuring this out! BTW, I also have no unzippered DTiVos to examine.

    I can receive network packets, so now I can try to get this working with my Broadvox Direct SIP. I'll report back either way.

    Thanks again, and thanks, John, for your help and asking HH to look into this.
     
  15. jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    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.
     
  16. djl25

    djl25 C64 hacker

    95
    0
    May 26, 2005
    Providence, RI
    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


     
  17. Apr 8, 2008 #197 of 282
    unclemoosh

    unclemoosh I Wish I knew Then..

    368
    0
    Sep 11, 2004
    Gulf South
    I have a WRT54GS in place of your RVS4000. I put the Tivo in DMZ, but no luck. No packets, no errors, no go. When I do a sip2ncid -l I get:

    eth0 : No description available
    any : Pseudo-device that captures on all interfaces
    lo : Loopback device

    Is that right?

    Thanks.
     
  18. Apr 8, 2008 #198 of 282
    jlc

    jlc New Member

    149
    0
    Jun 18, 2002
    near...
    The output above shows that your network port is eth0. The sip2ncid test option should show eth0 as the network interface selected.

    You need to try all SIP Invite ports in the test mode. The first line checks port 10000, the second line checks port 5061 and the last liine checks port 5060. Remember that the sip packets are transmitted about 20 seconds apart so I would keep the test active for at least 30 seconds to see packets.
    Code:
    sip2ncid -t
    sip2ncid -ts :5061
    sip2ncid -ts :5060
    
    You can use sip2ncid -T to test for any packets on your network. You should see a lot of packets.

    Some WRT54G routers seem to have problems with SIP. You will need to search for any solutions, but I did find this link that may help. It sets the router up this way:
     
  19. Apr 8, 2008 #199 of 282
    djl25

    djl25 C64 hacker

    95
    0
    May 26, 2005
    Providence, RI
    Do you have your Vonage device before or after the router? The WRT54GS doesn't port mirror (although there may be alternate firmware that does) so I'd think your best bet would be:
    Internet --> ATA --> WRT54GS--> Tivo
    with the port forwarding set as in the posting jlc found. It's very possible, however, that the Vonage device won't even pass the SIP packets. In that case, you might want to look into a hub or different router.



     
  20. unclemoosh

    unclemoosh I Wish I knew Then..

    368
    0
    Sep 11, 2004
    Gulf South
    My Vonage device is after the router. It's a Linksys PAP2, so I don't have the option of putting it before. I forwarded the ports, no luck.

    I bought a hub off eBay and will try it between the router and the PAP2 and put the Tivo on the hub.

    I'll let ya'll know what happens.
     

Share This Page