The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linux Based Caller ID Solution for the UK



--- In ukha_d@xxxxxxx, "david_dabs" <david_dabs@y...>
wrote:
> Hi guys, looking for a recommendation for a caller id solution for
> the UK.  Ive read around a bit and it seems that getty under linux
> can do this with some modems it just doesnt seem clear which.  I
> guess what Id really like is a dedicated device that will log the
> phone numbers to a flat file that I can script around my own web
> interface etc or that triggers an event that I can catch somehow,
> like on incomming calling run X executable and pass phone number of
> the command line to it.  So please any suggestions and shameless
> plugs to products others are using would be truly helpful.
>
> If it helps my current ha system is all X10 based
> switches /sockets/sensors with heyu2/xtend/bluelava running from a
> redhat linux machine.


http://patrick.lidstone.net/ha/xAP/xAP%20Projects/Applications/meteor

will do what you are looking for, using a Meteor caller id box from
Pegasus. Caller ID details are broadcast on the network and can by
acted on by any application capable of receiving those events.
There's a simple web and wap front end here:

http://patrick.lidstone.net/ha/xAP/xAP%20Projects/Applications/cache

If you run two apps on the same machine you'll need to install a xAP
hub, such as this:

http://patrick.lidstone.net/ha/xAP/xAP%20Projects/Infrastructure/hub

The same software should work with little or no modification against
a hand-modified caller id box such as those that you can find in The
Link for a fiver (you just need to add a serial driver chip).

Patrick




Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.