<?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 Security Advisory &#8211; RTP Remote Crash Vulnerability</title>
	<atom:link href="http://voipsa.org/blog/2009/12/04/asterisk-security-advisory-rtp-remote-crash-vulnerability/feed/" rel="self" type="application/rss+xml" />
	<link>http://voipsa.org/blog/2009/12/04/asterisk-security-advisory-rtp-remote-crash-vulnerability/</link>
	<description>Collective thoughts and musings on the state of VoIP security today.</description>
	<lastBuildDate>Fri, 18 May 2012 10:08:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alan Percy</title>
		<link>http://voipsa.org/blog/2009/12/04/asterisk-security-advisory-rtp-remote-crash-vulnerability/comment-page-1/#comment-357248</link>
		<dc:creator>Alan Percy</dc:creator>
		<pubDate>Fri, 04 Dec 2009 22:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://voipsa.org/blog/?p=820#comment-357248</guid>
		<description>We discussed this exact senario in detail during the most recent session on SIP Tunking security during the Spring ITExpo 2009.  

The vunerability is one example of the threats that exist when exposing any IP-PBX (including Asterisk) to the outside world without an SBC with packet inspection playing the role of security guard.  We strongly suggest that our solution designers use our eSBC function in our MSBG platform to secure their point of entry.

If there is a crack, the bad guys will find it - especially in the open source world when they have the source code to your IP-PBX.

No IT manager want a resume-generating event to occur on their IP-PBX.</description>
		<content:encoded><![CDATA[<p>We discussed this exact senario in detail during the most recent session on SIP Tunking security during the Spring ITExpo 2009.  </p>
<p>The vunerability is one example of the threats that exist when exposing any IP-PBX (including Asterisk) to the outside world without an SBC with packet inspection playing the role of security guard.  We strongly suggest that our solution designers use our eSBC function in our MSBG platform to secure their point of entry.</p>
<p>If there is a crack, the bad guys will find it &#8211; especially in the open source world when they have the source code to your IP-PBX.</p>
<p>No IT manager want a resume-generating event to occur on their IP-PBX.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

