[Asterisk-Users] VoIP hackers gut Caller ID

[Steve Underwood]

The switches already support this. In most parts of the world an end 
user trunk can only use a caller ID within their allocated blocks of 
numbers. Attempts to use other caller IDs usually result in the call 
being rejected. In some cases it results in the call completing, but the 
receiver sees a default caller ID for the sub who initiated the call, 
rather than the one the sub tried to use.

Regards,
Steve


rich allen wrote:

> this is really simple, companies like Nortel, Lucent need to change 
> their code for caller id, if the number should be blocked then dont 
> transmit it to the far end switch
>
> - hcir
>
> On Jul 7, 2004, at 6:00 AM, Kevin Walsh wrote:
>
>> Adam Hart [adam at teragen.com.au] wrote:
>>
>>> Chris Foster wrote:
>>>
>>>> The Register is carrying a article written by Kevin Poulsen of
>>>> Securtiy Focus, calling asterisk  "..the most powerful tool for
>>>> manipulating and accessing CPN data.."
>>>>
>>>> I hope NuFone doesn't drop asterisk-set-able callerid's after this
>>>> article; i've been wanting that feature from voicepluse for a long
>>>> time.
>>>>
>>> These kind of things will be reason (excuse) for Voip to be regulated
>>>
>> Perhaps service providers who allow the Caller*ID to be set should
>> insist that customers provide evidence that they own the phone numbers
>> that they want to publish, and then limit the customers' choices to
>> only the numbers in their approved list.  Calling the customer on the
>> provided number(s) would be an easy way to check, and a setup fee
>> could be levied to cover the provider's time and expenses, if required.
>>
>> Being able to discover a "blocked" Caller*ID is another matter.  Both
>> are good areas for regulation.
>>