[VOIPSEC] Phone Parrot: The most obnoxious IVR application ever written (for Asterisk)

[Geoff Devine]

The difference is that email SPAM doesn't ring your home telephone at
3AM.

If you don't have your service provider establishing trust, you as an
end-user will have no choice but to filter all calls from unknown
destinations.  I'll no longer be able to call home from a different
telephone since its identity is unknown.

The trust relationship is formed by having a business relationship
between the caller and the service provider.  With ENUM and calling by
URI, you no longer have that.

It's bad enough that you can already hack CallerID on a Primary Rate
ISDN interface.  At least there, the telco can and does police this and
there have been cases where they've shut down telemarketers who have
spoofed CallerID.  With VoIP, it'll be a total free for all.  I don't
view this as a step forwards.

Geoff


Date: Mon, 4 Sep 2006 17:13:21 -0500
From: "Watson, David D." <david.watson at gd-ais.com>
Subject: Re: [VOIPSEC] Phone Parrot: The most obnoxious IVR
	application ever	written (for Asterisk)
To: <Voipsec at voipsa.org>
Message-ID:
	
<91CC20228CD4E2408BF66B4C3C1201CDC880A3 at txsa01-mail01.ad.gd-ais.com>
Content-Type: text/plain;	charset="iso-8859-1"

Spam is in the eye of the beholder. Sometimes mail from my boss meets
common definitions, though I often find it useful to appear interested.
But I didn't perceive Shawn was trying to sell us anything, just info on
a new app with possible relevance to our group's charter.  The voice
change was interesting.  How likely are you to disclose information to a
voice you recognize as a coworker, versus a stranger or known
competitor?  Suppose someone could emulate a colleague's voice to elicit
sensitive info?  Voice recognition as a security measure is fairly
commonly used.