PDA

View Full Version : Better way to Caller ID?



Randall
2005-07-13, 15:35
I've seen all of the posts on how to integrate Caller ID into the squeezeboxes, and it seems that people are able to get it working.... IF THEY ARE CODE-EATING COMPUTER GURUS!!

My question is, could there be an easier way?

JohnQuirk
2005-07-14, 01:30
An easier way to caller ID? I feel your pain. In truth though, the Savard Soft YAK integration is really very easy to implement if you have hardware that is supported in YAK. Worth a look IMO.

max.spicer
2005-07-14, 04:42
Does anyone know of caller id solutions that work with Linux?

Max

CouchPotatoe
2005-07-14, 07:18
Randall wrote:

>I've seen all of the posts on how to integrate Caller ID into the
>squeezeboxes, and it seems that people are able to get it working....
>IF THEY ARE CODE-EATING COMPUTER GURUS!!
>
>My question is, could there be an easier way?
>
>
>
>
Do you want to just display the number of an incoming call ? Or would
you want to display a name and perhaps the location and the call log. If
just having the content of the incoming CID data displayed is adequate
then a simple solution is very possible. In the US I know this data
often includes both number and name but in the UK it is number only.

The Meteor/Pegasus in the UK is a much more capable device than a CID
modem in that they support outgoing DTMF and ON|OFF hook reporting (so
you can track all outgoing calls too) and can even dial them
automatically. Indeed there are very few UK capable CID modems. The
application could perhaps support the NetCallerID units in the US with a
direct to SlimServer link very easily. This would literally display the
number (and name if present) on the Slim displays for a few secs when an
incoming call arrived. The difference here is that xAP normally
presents the CID data, the dial capabilities, the DB lookups and call
history as network resources to all xAP aware applications (including
SlimServer via xAP Slim) and this tends to make the concept a little
more complex but very powerful of course. Very useful if you need the
data available realtime in many places - for example CID displays on my
TV / Tivo and all my PC's inc Windows Media Centre and can be announced
using speech synthesis too and even emailed or SMS'd

For a simple approach perhaps some Perl code should be added to
SlimServer to handle the serially attached NetCallerID and modems directly.

K

kdf
2005-07-14, 09:08
Quoting Kevin Hawkins <lists (AT) ukusa (DOT) demon.co.uk>:

> For a simple approach perhaps some Perl code should be added to
> SlimServer to handle the serially attached NetCallerID and modems directly.

I think Dan's post in an otherwise unrelated thread makes it fairly clear that
this is unlikely to be a likely option.

-kdf

dean
2005-07-14, 09:31
It sounds like a great opportunity for a plugin.

We do consider adding plugins to the main distribution, but only if
they are of benefit to a substantial fraction of our community.

Otherwise, they are easy to install for those who need them...

On Jul 14, 2005, at 9:08 AM, kdf wrote:

> Quoting Kevin Hawkins <lists (AT) ukusa (DOT) demon.co.uk>:
>
>
>> For a simple approach perhaps some Perl code should be added to
>> SlimServer to handle the serially attached NetCallerID and modems
>> directly.
>>
>
> I think Dan's post in an otherwise unrelated thread makes it fairly
> clear that
> this is unlikely to be a likely option.
>
> -kdf
>

Niek Jongerius
2005-07-15, 01:11
> Does anyone know of caller id solutions that work with Linux?

Well, FWIW I run a pretty hacked-up solution. I'm in the Netherlands,
and I have ISDN for my phone line. I used a spare ISDN card in my Linux
server and hooked it up to the ISDN line. Each incoming call triggers a
message on the D channel, and this in turn triggers the device driver of
the ISDN card to fire off a syslog message. This then is picked up by a
proggie that does a lookup to get from caller ID to name-in-the-phonebook,
and this is sent via the CLI to the SlimServer.

This probably does not qualify for easy-to-install though... :-)

OTOH, it wouldn't be a major undertaking to cobble up a Linux daemon to
monitor a serial line for incoming caller ID, and take it from there. I
could take this on, but haven't got access to any such serial beast.

Niek.