DavidW522
Posts: 9
Joined: Sun Aug 12, 2012 1:34 pm

Network caller id

Tue Nov 20, 2012 5:49 pm

Has anyone found software that will work as a network caller id for the pi? I would like to connect my usb modem up to my pi and have it transmit the caller id info out to all the computers in the house.

bgirardot
Posts: 517
Joined: Wed Oct 10, 2012 6:20 am
Location: Switzerland

Re: Network caller id

Wed Nov 21, 2012 1:40 am

Sounds like a cool idea and might be more challenging than it sounds at first.

This thread has a few good links and ideas:
http://ubuntuforums.org/showthread.php?t=326036

mgetty is available for the rpi and you might be able to script something that grabs the CID and then IM's it to other computers depending on what OS they are running.

DavidW522
Posts: 9
Joined: Sun Aug 12, 2012 1:34 pm

Re: Network caller id

Mon Dec 10, 2012 8:35 pm

Thanks looking into it.

cerebro
Posts: 17
Joined: Sun Feb 03, 2013 10:32 pm

Re: Network caller id

Mon Feb 04, 2013 12:19 am

Hi, did you guys every get this working? I have tried to get NCID working on the pi with no luck, I am basically looking for a way to get a USB modem working on the pi so any landline calls could then have the callers id transmitted to PC's around the house, so far I am getting no where so any pointers would be great.

DavidW522
Posts: 9
Joined: Sun Aug 12, 2012 1:34 pm

Re: Network caller id

Mon Feb 04, 2013 8:21 am

No as I recall none of that was in the apt-get database for the pi or something like that.

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Sat Mar 16, 2013 6:43 pm

It is easy to get NCID running on a pi if you know the right "magical incantations". In a nutshell, you need to install libpcap and then you can compile the NCID source on your RPi.

First, we need to install libpcap before compiling NCID. From a command prompt, on the RPi:

Code: Select all

sudo apt-get install libpcap0.8*
Second, download and compile NCID on the Raspberry Pi:

Code: Select all

wget http://downloads.sourceforge.net/ncid/ncid-0.85-src.tar.gz
tar xvf ncid-0.85-src.tar.gz
cd ncid
sudo make ubuntu-install
Finally, configure NCID on the RPi:
Since Raspberri Pi’s OS is Debian based, the ubuntu install guide seems to be working without any changes.

If you need a USB modem, the Zoom USB Modem 3095 works well. No need to install drivers, and the RPi sees it as a serial port; it showed up as /dev/ttyACM0 for me. NCID has no problem at all talking to it when it is configured properly.

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Mon Mar 25, 2013 12:37 am

NCID 0.86 is now available as a downloadable package for installation on the RPi. It is not yet part of the Raspbian repository so you will need to download the package from sourceforge and install it with gdebi. For example, to install the ncid server (ncidd):

Code: Select all

sudo apt-get update
sudo apt-get install gdebi
wget http://downloads.sourceforge.net/ncid/ncid_0.86-1_armhf.deb
sudo gdebi ncid_0.86-1_armhf.deb
NCID installation instructions specific to RPi are available at: http://ncid.sourceforge.net/ncid/INSTALL-Raspbian.txt

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Mon Apr 29, 2013 3:23 am

NCID just released a major update to LCDncid that includes support for the Raspberry Pi.

LCDncid allows you to display Caller ID and user messages on a hd44780 compatible LCD attached to a Raspberry Pi either through i2c using the Adafruit LCD PiPlate http://www.adafruit.com/products/1115 or a direct connection via a 4-bit parallel bus connection. Both configurations utilize LCDproc, so folks interested in getting LCDproc running on the Raspberry Pi will find the link below useful.

Pictures along with full instructions are available at http://ncid.sourceforge.net/lcdncid/lcdncid.html.

lee
Posts: 14
Joined: Sat Mar 03, 2012 3:38 pm

Re: Network caller id

Wed Jul 10, 2013 9:02 pm

priority wrote:If you need a USB modem, the Zoom USB Modem 3095 works well. No need to install drivers, and the RPi sees it as a serial port; it showed up as /dev/ttyACM0 for me. NCID has no problem at all talking to it when it is configured properly.
I read this post and got a Zoom 3095 based off of it - whilst it does work in raspbian without needing any drivers or anything (it appears at /dev/ttyACM0 automagically), caller ID for me did NOT work - modem was reporting CID enabled, but also no caller ID info was coming through, /var/log/cidcall.log showed "CID: *DATE*07082013*TIME*1832*LINE*POTS*NMBR*RING*MESG*NONE*NAME*No Caller ID*" (I also tried changing init strings with no joy). I am in the UK (ish). This blog post is what I wish I'd read first. I ended up getting a £8 more expensive USR805637 / US Robotics 5637 which is currently working fine - again, it appears automagically with no extra work needed. I am not experiencing this problem either - ncid is successfully retrieving every call so far with no fuss at all, using the default init string and CID init strings (i.e. initstr/initcid is commented out in /etc/ncid/ncidd.conf).

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Wed Jul 24, 2013 1:52 pm

lee wrote:
I read this post and got a Zoom 3095 based off of it - whilst it does work in raspbian without needing any drivers or anything (it appears at /dev/ttyACM0 automagically), caller ID for me did NOT work - modem was reporting CID enabled, but also no caller ID info was coming through, /var/log/cidcall.log showed "CID: *DATE*07082013*TIME*1832*LINE*POTS*NMBR*RING*MESG*NONE*NAME*No Caller ID*" (I also tried changing init strings with no joy). I am in the UK (ish). This blog post is what I wish I'd read first. I ended up getting a £8 more expensive USR805637 / US Robotics 5637 which is currently working fine - again, it appears automagically with no extra work needed. I am not experiencing this problem either - ncid is successfully retrieving every call so far with no fuss at all, using the default init string and CID init strings (i.e. initstr/initcid is commented out in /etc/ncid/ncidd.conf).
Thanks for posting. I guess I should have stated that I am using the zoom modem in the US. Since there is a lot of variation worldwide with callerid encoding, there may not be a "universal" modem.

kets
Posts: 7
Joined: Fri Sep 20, 2013 7:44 pm

Re: Network caller id

Fri Sep 20, 2013 7:49 pm

Any idea how to get caller id from my Vonage ata device then out to my tax clients by any chance?

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Fri Nov 15, 2013 8:41 pm

kets wrote:Any idea how to get caller id from my Vonage ata device then out to my tax clients by any chance?
Not a 100% sure what your requirements/requests are, but that won't stop me from attempting a response. :)

NCID is not limited to the use of a modem for CID information collection. Vonage uses SIP packets for sending communications between from your ATA to/from the internet. You can "sniff" these packets and use them for gathering callerid information for both incoming and outgoing calls to/from your ATA. The relevant program to use is SIP2NCID; you can run SIP2NCID on the same RPi that is running NCID. The challenge is getting the SIP packets to your RPi running NCID. There are two methods that I know work: (1) port mirroring in a router running DD-WRT or (2) using a switch that has built in port mirroring. Option (1) is a bit challenging, but can be done; see http://forums.sagetv.com/forums/showthr ... tcount=105 for the details. The (2) option is the easiest, but does require the purchase of some additional hardware. Dualcomm sells a usb powered 5port switch that mirrors ports 1 and 5. http://www.dual-comm.com/port-mirroring-LAN_switch.htm shows how to set this up. Word of caution: Netgear has some of their lower-cost switches that advertise port mirroring, but it is NOT compatible with this setup.

NCID creates a log of all calls that can be used for historical records. If you want "real time" caller id outside of your home network (via the internet), create a port forward (default NCID port is 3333) from your home router to the RPi running NCID. Then, any NCID client can access the NCID server from your home's IP address on port 3333. If you need a dynamic dns service to keep track of your home's IP address, http://www.changeip.com is free (as in free beer) and works well.

One nice thing about SIP sniffing is you don't have to wait for the second ring to get CID info; it comes in with the first ring. Another nice benefit is that Call Walling ID works; I have never gotten Call Waiting ID to work with a modem due to technical limitations that appear to be present in all dial-up modems available.

kets
Posts: 7
Joined: Fri Sep 20, 2013 7:44 pm

Re: Network caller id

Sat Nov 16, 2013 7:19 am

Ta for the reply mate...good info...i was thinking of ARP poisoning...but not a Linux expert to get it up and running....doesn't need a hub or a router that has port mirroring.

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Sat Nov 16, 2013 8:09 pm

kets wrote:...i was thinking of ARP poisoning...but not a Linux expert to get it up and running....
ARP poisoning should work; there's a commercial VOIP recording solution from Pen Bay Networks that uses ARP "redirection".

I only listed methods personally tested. A while back I was looking at ettercap and asked NCID's developer if he knew if anyone had successfully used ARP poisoning for SIP sniffing, but he was not aware of anyone doing so. I would be very interested in hearing your progress/results; I suspect other NCID users will as well.

kets
Posts: 7
Joined: Fri Sep 20, 2013 7:44 pm

Re: Network caller id

Sat Nov 16, 2013 8:27 pm

Penbaynetworks app is amazing but not flexible to interface off to other applications and costs a fair bit....ettercap should do it!

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Tue Jan 14, 2014 5:17 am

kets wrote:....ettercap should do it!
Finally took the time to rtfm. This works nicely to install ettercap and start it as a daemon:

Code: Select all

sudo apt-get install ettercap-text-only
sudo ettercap -T -D -i eth0 -M arp:remote /IP-OF-SIP-ATA/ /IP-OF-ROUTER/ 
If you are using wifi, change "-i eth0" to "-i wlan0".

kets
Posts: 7
Joined: Fri Sep 20, 2013 7:44 pm

Re: Network caller id

Tue Jan 14, 2014 6:16 am

So U have a fully working solution now with ncid and ettercap with Vonage hardware device? If so can you detail it for the rest if us pls ?

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Tue Jan 14, 2014 6:54 am

kets wrote:So U have a fully working solution now with ncid and ettercap with Vonage hardware device? If so can you detail it for the rest if us pls ?
Yes. Here's a guide...it was embarrassingly simple once I understood the proper incantations!

1) Install ncid and configure on the RPi: see http://ncid.sourceforge.net/doc/NCID_Do ... l_rasp_top. Don't start ncidd until after step 3 below.

2) Install ettercap per my previous post. Note I had to use the actual IP addresses to get it to work. I am using a wired ethernet interface, so I start ettercap as a daemon with

Code: Select all

sudo ettercap -T -D -i eth0 -M arp:remote /192.168.1.50/ /192.168.1.1/ 
3) Setup sip2ncid gateway: http://ncid.sourceforge.net/doc/NCID_Do ... teways_sip. Be sure to verify SIP traffic is being passed through your RPi with "sudo sip2ncid --testall". Once this is working, start the sip2ncid service and set it to run at boot per the ncid instructions in 1).

4) Start ncidd per info in install page.

5) Call your Vonage number to verify everything works.

6) Sit back, contemplate what grand things you have just accomplished, and have a cold one!

One caveat, if you reboot your RPi, you will need to restart ettercap manually. It is not hard to create the proper init.d scripts; but I have been running this for about a week now without a single reboot and just not gotten around to creating the scripts.

kets
Posts: 7
Joined: Fri Sep 20, 2013 7:44 pm

Re: Network caller id

Tue Jan 14, 2014 7:11 am

Boom U da man !!!...will give it a go with the yac server add in....and see if it works with yac clients on windows

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Tue Jan 14, 2014 1:57 pm

ncid2yac works just fine with this setup from my experience as have a couple of YAC listeners.

However, recommend you try NCIDpop (http://ncid.sourceforge.net/ncidpop/ncidpop.html) to replace your windows YAC clients. It does the same job, but has more features including the ability to speak the caller name when a call comes in and viewing the call history.

PaulMJStone
Posts: 2
Joined: Mon Jan 27, 2014 6:37 pm

Re: Network caller id

Mon Jan 27, 2014 9:24 pm

FYI I used a TRIXES USB 56K (http://www.amazon.co.uk/exec/obidos/ASI ... os_product) and although it didn't work first time with NCIDD it eventually caught on and is displaying UK CLI. :D

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Mon Jan 27, 2014 9:47 pm

PaulMJStone wrote:FYI I used a TRIXES USB 56K (http://www.amazon.co.uk/exec/obidos/ASI ... os_product) and although it didn't work first time with NCIDD it eventually caught on and is displaying UK CLI. :D
Any hints you can share about how you got the modem and NCIDD working nicely with each other?

PaulMJStone
Posts: 2
Joined: Mon Jan 27, 2014 6:37 pm

Re: Network caller id

Mon Jan 27, 2014 10:02 pm

Initially it didn't work so I modified the /etc/ncid/ncidd.conf setting for set ttyport =/dev/ttyACM0 (and tried a few others) .... but then eventually put it back to ACM0 and for whatever reason it started talking properly with the "sudo ncidd -Dv3" command.
The Pi had been booted a few times with the modem connected so I'm not quite sure what made them play nice. I don't know if linux loads drivers if you unplug/plug in but I'm likely to have done that as well!

I know when I'd tried 'by hand' to get the modem to do CLI I had to set the code "AT+VCID=1" to disclose it but I can see NCID does that as part of the setup.
priority wrote:Any hints you can share about how you got the modem and NCIDD working nicely with each other?

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Mon Feb 03, 2014 1:42 am

A new version of NCID was released last week with enhancements in usability https://sourceforge.net/p/ncid/news/201 ... -released/.

Also, the documentation for NCID has undergone a major upgrade http://ncid.sourceforge.net/doc/NCID_Do ... evices_top.

NCID is unfortunately not in the Raspbian repository (can't figure out how to get this package in the repository, but would be happy to work with the appropriate folks if someone could point the right way), but there is a .deb Raspbian package available for download to install or update if you don't enjoy compiling the code yourself.

priority
Posts: 22
Joined: Sat Mar 16, 2013 6:26 pm

Re: Network caller id

Wed Apr 16, 2014 8:20 pm

A new release of NCID is now available. See http://sourceforge.net/p/ncid/news/2014 ... -released/.

Several new features are in the update:
  • Have hangup calls answer as a FAX machine.
    New message format for MSG and NOT support.
    Improved handling of aliases.
Download the release here: http://sourceforge.net/projects/ncid/files/ncid/0.89/

Return to “Beginners”

Who is online

Users browsing this forum: No registered users and 2 guests