<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Asterisk: Tools for peace and quiet</title>
	<atom:link href="http://blogs.digium.com/2008/11/10/asterisk-tools-for-peace-and-quiet/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.digium.com/2008/11/10/asterisk-tools-for-peace-and-quiet/</link>
	<description>A little slice o&#039; Digium.</description>
	<lastBuildDate>Sun, 05 Feb 2012 23:47:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: jtodd</title>
		<link>http://blogs.digium.com/2008/11/10/asterisk-tools-for-peace-and-quiet/comment-page-1/#comment-15443</link>
		<dc:creator>jtodd</dc:creator>
		<pubDate>Fri, 21 Nov 2008 08:18:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.digium.com/?p=1853#comment-15443</guid>
		<description>Tristan - Yes, many voice spammers can spoof their caller ID.  However, most don&#039;t change their numbers to &quot;legitimate&quot; origin caller IDs, because that brings rapid fraud charges.  Many will use &quot;throwaway&quot; caller IDs, but hopefully in a large enough community those numbers will be rapidly discovered and entered into our hypothetical database.

John - DNS blackhole lists are what Brett talked about in his post, using ENUM-ish type technology, though it would be simple enough for a DNS RBL provider to create a shim that fetches numbers into the ENUM tree from some other APIs like HTTP.  Interestingly, the people at 800notes.com and I are in a short conversation about what they might do for an API, but I don&#039;t know where that will lead.  Anyone want to pick up the flag for this?

Brian - Simple dialplan security is a basic fundamental for any SIP gateway on the public internet.  The good news is that security holes like that are VERY quickly solved, since PSTN termination costs money.  SMTP was much more difficult to solve since poor security models didn&#039;t have an obvious and immediate economic penalty.</description>
		<content:encoded><![CDATA[<p>Tristan &#8211; Yes, many voice spammers can spoof their caller ID.  However, most don&#8217;t change their numbers to &#8220;legitimate&#8221; origin caller IDs, because that brings rapid fraud charges.  Many will use &#8220;throwaway&#8221; caller IDs, but hopefully in a large enough community those numbers will be rapidly discovered and entered into our hypothetical database.</p>
<p>John &#8211; DNS blackhole lists are what Brett talked about in his post, using ENUM-ish type technology, though it would be simple enough for a DNS RBL provider to create a shim that fetches numbers into the ENUM tree from some other APIs like HTTP.  Interestingly, the people at 800notes.com and I are in a short conversation about what they might do for an API, but I don&#8217;t know where that will lead.  Anyone want to pick up the flag for this?</p>
<p>Brian &#8211; Simple dialplan security is a basic fundamental for any SIP gateway on the public internet.  The good news is that security holes like that are VERY quickly solved, since PSTN termination costs money.  SMTP was much more difficult to solve since poor security models didn&#8217;t have an obvious and immediate economic penalty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tristan Rhodes</title>
		<link>http://blogs.digium.com/2008/11/10/asterisk-tools-for-peace-and-quiet/comment-page-1/#comment-15393</link>
		<dc:creator>Tristan Rhodes</dc:creator>
		<pubDate>Tue, 18 Nov 2008 15:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.digium.com/?p=1853#comment-15393</guid>
		<description>Are voice spammers able to spoof their caller-ID?  If so, then it would circumvent any caller-id based filtering.  Most email spam comes from spoofed email addresses.</description>
		<content:encoded><![CDATA[<p>Are voice spammers able to spoof their caller-ID?  If so, then it would circumvent any caller-id based filtering.  Most email spam comes from spoofed email addresses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Laur</title>
		<link>http://blogs.digium.com/2008/11/10/asterisk-tools-for-peace-and-quiet/comment-page-1/#comment-15313</link>
		<dc:creator>John Laur</dc:creator>
		<pubDate>Wed, 12 Nov 2008 16:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.digium.com/?p=1853#comment-15313</guid>
		<description>There would be a better solution for blackholing E.164 addresses and SIP spam - DNS blackhole lists. RBL filters could be implemented with ENUM lookups against specific zones for E.164 numbers and via standard methods for IP addresses and done by DNS just as SMTP blackholing is done for spam e-mail RBL&#039;s. It would be generally faster, more efficient, and more scalable than an AGI. The difficulty would be getting sites like whocalled.us to publish their data in ENUM records. This type of solution would be effective (sometimes) at blocking telemarketing and the (rare) SIP telemarketing, but it would also take care of hosts known to be originating malicious SIP activity as mentioned by Brian Jones. I have seen such activity also -- specifically targeting SIP registrations with simple default username/password combinations.</description>
		<content:encoded><![CDATA[<p>There would be a better solution for blackholing E.164 addresses and SIP spam &#8211; DNS blackhole lists. RBL filters could be implemented with ENUM lookups against specific zones for E.164 numbers and via standard methods for IP addresses and done by DNS just as SMTP blackholing is done for spam e-mail RBL&#8217;s. It would be generally faster, more efficient, and more scalable than an AGI. The difficulty would be getting sites like whocalled.us to publish their data in ENUM records. This type of solution would be effective (sometimes) at blocking telemarketing and the (rare) SIP telemarketing, but it would also take care of hosts known to be originating malicious SIP activity as mentioned by Brian Jones. I have seen such activity also &#8212; specifically targeting SIP registrations with simple default username/password combinations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Jones</title>
		<link>http://blogs.digium.com/2008/11/10/asterisk-tools-for-peace-and-quiet/comment-page-1/#comment-15293</link>
		<dc:creator>Brian Jones</dc:creator>
		<pubDate>Tue, 11 Nov 2008 14:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.digium.com/?p=1853#comment-15293</guid>
		<description>I have also been seeing insecured Asterisk boxes being used like &quot;open smtp relay&quot; servers of old.  For example, if a Asterisk box has a sip friend configured in sip.conf without a password, and say it&#039;s a generic username that&#039;s a four digit extension, people are running scripts to find these friends.  Once they find such a friend they start using it to send telemarketing calls to the states, or credit card scams etc.  Usually it&#039;s not caught until someone calls the number that showed up in the caller id, which happens to be the caller id of the Company&#039;s hijacked Asterisk box.

Brian.</description>
		<content:encoded><![CDATA[<p>I have also been seeing insecured Asterisk boxes being used like &#8220;open smtp relay&#8221; servers of old.  For example, if a Asterisk box has a sip friend configured in sip.conf without a password, and say it&#8217;s a generic username that&#8217;s a four digit extension, people are running scripts to find these friends.  Once they find such a friend they start using it to send telemarketing calls to the states, or credit card scams etc.  Usually it&#8217;s not caught until someone calls the number that showed up in the caller id, which happens to be the caller id of the Company&#8217;s hijacked Asterisk box.</p>
<p>Brian.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

