Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!lll-winken!telecom-request From: Barton.Bruce@camb.com (Barton F. Bruce) Newsgroups: comp.dcom.telecom Subject: Re: Technological Solution to Caller ID Message-ID: Date: 27 Mar 91 07:55:47 GMT Sender: Telecom@eecs.nwu.edu Organization: Cambridge Computer Associates, Inc. Lines: 29 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 11, Issue 246, Message 6 of 7 In article , owens@gargoyle.uchicago.edu (Christopher Owens) writes: > I've been trying to push this line of reasoning for a while; I'd like > to encourage people to refine it and correct its problems. I suspect Ideally, one should be able to set the mode and latch it whenever you choose. There would be a default for newly installed lines, and you could the flip/flop it as needed. There would be a simpler per call method of giving id or blocking id regardless of the current default. Ideally there would be a test code that would prattle back ALL current settings in case one forgets or needs to verify them. There should be NO additional charge for mode flipping or status inquirys. The ONLY paying folk should be those that RECEIVE the caller ID. If the telcos think they are going to rip folks off $5 here and $5 there for each feature, they will get what they deserve as the alternate dialtone providers arrive. Teleport has 2 #5ess machines in NYC, and should have one here in Boston by the end of the year. It may be a DMS100, but I think they will pick the 5ess. Just think! A phone company that will give you answer supervision! For businesses, there would need to be an optional blocking of the permanent mode flipping, and the business would then have to select the default mode. Per call selection would still work.