🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dcom.telecom.tech
Article #223

Re: CALLER ID ~~ MYSTERY

#223
From: tombrown
Date: Sun, 01 Dec 1996 00:00
30 lines
2235 bytes
In article <57pq59$gjm@news.usf.edu> jra@scfn.thpl.lib.fl.us (Jay R. Ashworth) writes:
>Ok, it's like this.
>
>Any decent CNID box not specifically designed for ADSI (caller ID on
>call waiting) will not accept data when the line is off-hook.  So,
>spoofing after pickup is impossible.
>
>There is _NO_ (count 'em, _no_) audio path from the source phone line
>to the destination, on any switch new enough to _have_ CNID, that would
>give a spoofer any way to spoof the box _during_ the ring cycle.
>(Conterexamples better come with documentation cites.)
>
>The _only_ way to spoof CNID is is you have a PBX that connectes with an
>ISDN PRI, _and_ your LEC uses a CO switch that doesn't validate
>outbound CNID IEs from that switch, _and_ the administrators of that
>switch--usually a large company, let's face it--are willing to violate
>what must at least be a tariff provision, if not a law (well, it is in
>Georgia :-), by sending fals information down that line.
>
>So, if you have a stupid LEC with bad taste in switches and judgement
>in programming, yes, it is theoretically _possible_ to spoof CNID, or
>if you have a cheapshit box, it is possible to _have_ your CNID
>spoofed.
>
>But let's face it, if the situation is really that important, at least
>the CNDI box gives you the _switch's_ idea of the call time, so they
>can look in the switch logs of the trap and trace.

Well, that certainly clears things up, eh?
Technical Details
Message-ID: <57ravv$c4l@news.jhu.edu>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <3291A297.636C@worldnet.att.net> <56si1d$8lf@newstand.syr.edu> <57pq59$gjm@news.usf.edu>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10a9ce,8cb9bc158bc4606a
X-Google-Attributes: gid10a9ce,public
X-Google-Thread: 1038e3,b04b4ce7cb859f48
X-Google-Attributes: gid1038e3,public
X-Google-Thread: f4e50,b04b4ce7cb859f48
X-Google-Attributes: gidf4e50,public
X-Google-Thread: 101049,8cb9bc158bc4606a
X-Google-Attributes: gid101049,public
From: tombrown@jhunix.hcf.jhu.edu ()
Subject: Re: CALLER ID ~~ MYSTERY
Date: 1996/12/01
Message-ID: <57ravv$c4l@news.jhu.edu>
X-Deja-AN: 201673482
references: <3291A297.636C@worldnet.att.net> <56si1d$8lf@newstand.syr.edu> <57pq59$gjm@news.usf.edu>
organization: Homewood Academic Computing, Johns Hopkins University, Baltimore, Md, USA
newsgroups: comp.dcom.telecom.tech,misc.legal,dc.general,balt.general