Re: Re: Meteor Caller ID drivers ?

[Stuart Booth <lists@xxxxxxx>]

On Thu, 1 May 2003 12:31:41 +0100, "Dean Barrett"
<dean@xxxxxxx>
wrote:

>Stuart - you are doing exactly what i asked about when i originated
this
>post - which seems to have digressed a little.
>
>So what do i need to make my Meteor send messages and my Slimp receive
them

I have written three separate xAP based applications that run on my
Server doing this job, although one of them isn't exactly finished
yet!

1. The first deals with my Meteor and broadcasts xAP CID messages.

2. The second picks up the CID messages it's interested in and sends
out OSD messages with the calling number. This is where I can
additionally do number -> name lookups for instance.

3. A third application talks to the SliMP3s and can route the Slim
targetted OSD messages as required.

4. Another app I wrote knows how to talk to my TiVo and can route TiVo
targetted OSD messages, similar to the above.

Each does a separate well defined job, and so can easily be replaced
with something better or more suitable for your setup.

Unfortunately my Meteor xAP app needs a little bit of work as it
currently has a bug that outputs an error message when a Withheld call
arrives. Highly entertaining to be confronted with a debug error
message on the TV whilst watching TiVo, I can assure you :) There's
also another bug I've been meaning to fix for months now to do with
the Meteor sending it an unexpected message.

I haven't yet released the CID->SliMP3/TiVo OSD app, but might do that
tonight.

Stuart


>  -----Original Message-----
>  From: Stuart Booth [mailto:lists@xxxxxxx]
>  Sent: 01 May 2003 12:21
>  To: ukha_d@xxxxxxx
>  Subject: Re: [ukha_d] Re: Meteor Caller ID drivers ?
>
>
>  On Thu, 1 May 2003 11:49:53 +0100, "Nikola Kasic"
<nikola@xxxxxxx>
>  wrote:
>
>  >Patrick,
>  >You often refer to xAP and compare it with Autom8it.
>  >I thought that xAP is just a protocol, not the application.
>  >Or there is some application available that can handle xAP
messages?
>
>  That's right, Nik. There is xAP the protocol, and then there are a
>  large number of applications (or xAPplications if you like ;-) that
>  implement some function utilising the xAP protocol.
>
>  So for instance you can run a xAP application that monitors the
Meteor
>  device plugged into some COM port. It then translates the Meteor
>  events into suitable xAP messages that it sends out.
>
>  Another xAP application somewhere on the network would be listening
>  out for messages of that format and do something with it.
>
>  On my own network my Meteor CallerID xAPplication does just that.
>  Another xAP app picks up the messages and sends out OSD messages.
>  These can then be picked up by SliMP3s, TiVos, etc. All this depends
>  on what software is running at the time though.
>
>  For myself I have a 'connector' application for the SliMP3 and for
the
>  TiVo. These pick up the OSD messages and deals with each of those
>  hardware devices appropriately.
>
>  So there are a serious of small apps that listen/send/receive xAP
>  messages.
>
>  Does that help?
>
>  Stuart
>  --
>  Stuart Booth
>  Somewhere in Buckinghamshire, England, UK
>
>  stuart@xxxxxxx
>
>        Yahoo! Groups Sponsor
>
>
>
>  ** UKHA2003 BE THERE! Details here:
>http://www.automatedhome.co.uk/article.php3?story_id=1110
**
>  http://www.automatedhome.co.uk
>  Post message: ukha_d@xxxxxxx
>  Subscribe:  ukha_d-subscribe@xxxxxxx
>  Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
>  List owner:  ukha_d-owner@xxxxxxx
>
>  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>
>[Non-text portions of this message have been removed]
>
>
>
>
>** UKHA2003 BE THERE! Details here: http://www.automatedhome.co.uk/article.php3?story_id=1110
**
>http://www.automatedhome.co.uk
>Post message: ukha_d@xxxxxxx
>Subscribe:  ukha_d-subscribe@xxxxxxx
>Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
>List owner:  ukha_d-owner@xxxxxxx
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>

--
Stuart Booth
Somewhere in Buckinghamshire, England, UK

stuart@xxxxxxx