[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
Re: BT caller ID(again)
- To: ukha_d@xxxxxxx
- Subject: Re: BT caller ID(again)
- From: patrickl@xxxxxxx
- Date: Mon, 23 Jul 2001 09:18:55 -0000
- Delivered-to: rich@xxxxxxx
- Delivered-to: mailing list ukha_d@xxxxxxx
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
--- In ukha_d@y..., "Justin" <justin@g...> wrote:
> As I have said previously I'm with NTL but I didn't think caller id
stuff
> was that different.
Therein lies the problem. Most NTL areas use the US style of caller
id delivery, whereby the CID information is delivered after the first
ring.
BT's CID delivery triggers a reversal in line polarity when a calls
comes in and delivers the CID information prior to the first ring.
Although the encoding of the CID data is broadly similar, it's the
lack of/accuracy of line reversal detection which causes the problem
at the modem end.
I know that people have successfully dismembered off-the-shelf caller
id boxes (the ones with the LCD panel designed for home consumer use)
and extracted the RS232 data. These units are cheap enough to make it
worth having a g if you're handy with a soldering iron (BT were even
giving them away for a while). The data format is easy t guess by
introspection, and is documented in the BT SIN.
HTH
Patrick
____________________________________
Automated Home UK
http://www.automatedhome.co.uk
____________________________________
Your use of Yahoo! Groups is subject t http://docs.yahoo.com/info/terms/
Home |
Main Index |
Thread Index
|