Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!csn!ub!dsinc!casbah.acns.nwu.edu!nucsrl!telecom-request From: cyberoid@milton.u.washington.edu (Robert Jacobson) Newsgroups: comp.dcom.telecom Subject: Re: Caller*ID Message-ID: Date: 20 Feb 91 00:22:09 GMT Sender: news@casbah.acns.nwu.edu Organization: Human Interface Technology Lab, Univ. of Wash., Seattle Lines: 24 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 135, Message 8 of 9 Originator: telecom@delta.eecs.nwu.edu Telemarketers often use several rotating numbers, often with different base stations, so Caller*ID (even in its ideal form) provides little enough protection against telemarketing. The number you suppress today will be gone tomorrow. Bob [Moderator's Note: Except that what has been discovered thus far about the passing of the number, be it ANI, Caller*ID, Return /Screen Call or whatever is that quite frequently if a group of related numbers are all billed under one main number, then it is the main listed number which gets passed along. If the telemarketer has all of his phones associated with (let's say) the main number of his switchboard, then there is a likelyhood Caller*IO will pass the switchboard's main listed number. We've found that in some versions of the software, Call Screening will block every trunk on a PBX, even if the only thing entered by the recipient of the unwanted call was the listed phone number for the company. I've a feeling Caller*ID will respond in much the same way, with every telemarketing employee in their little cubicle sending the company's main listed number regardless of what actual outgoing trunk they seize. Obviously it won't happen that way in every case. PAT]