|
![](/i/fill.gif) |
On 10/16/2011 3:43 PM, Jim Henderson wrote:
> On Wed, 12 Oct 2011 01:13:24 +0100, Stephen wrote:
>
>> On 12/10/2011 12:55 AM, Alain wrote:
>>> Le 2011/10/07 15:20, Stephen a écrit :
>>
>>
>>>>> Oh, there's a special circle of hell for telemarketers.
>>>>>
>>>> And r-e-c-o-r-d-e-d –a-n-n-o-u-n-c-e-m-e-n-t-s.
>>>>
>>>>
>>>>
>>> You can get the caller's number. Don't you hate it when that number
>>> turns out to be something like:
>>>
>>> Your number. You receive that recorded message and it pretends to be
>>> comming from YOU!
>>
>> I've not had that particular perversion. Yet.
>
> It's pretty common here in the US, even though it's illegal to spoof
> caller ID. Funny thing about spoofed caller ID - you can't find out
> easily where they're calling from. ;)
>
> Jim
Was an article on that one in at least two recent 2600 magazines. Seems,
there are two numbers that can come up, one is the "local exchange"
number, which can be spoofed, and the other is a number identification
thing, which can't. But, do to how the bloody system is set up, the one
your caller ID box gets is the "local" spoofable one. Spoofing, if I
remember, involves triggering an ID failure on the calling end, such
that the system can't properly figure out where the call is from, then
substituting data into the system, which it takes as a "local exchange"
ID, or.. something like that. I really don't remember.
Basically, there *is* a way to figure out who really called you, but
doing it requires more understanding of the system than like 99.9% of
the people using it, including most of the people at the phone company
you might contact about it, especially certain operators, which have to
rely on the same ID data that just got mis-reported to your own phone.
The only reason this *is* possible, ironically, is because they decided
to design the system with such a flaw, instead of using something less
prone to error, and redirection.
Post a reply to this message
|
![](/i/fill.gif) |