<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Asterisk e SIP: attacco e monitoraggio tramite correlazione di eventi, utilizzando SIPp e SEC</title>
	<atom:link href="http://mikeoverip.wordpress.com/2009/01/13/asterisk-e-sip-attacco-e-monitoraggio-tramite-correlazione-di-eventi-utilizzando-sipp-e-sec/feed/" rel="self" type="application/rss+xml" />
	<link>http://mikeoverip.wordpress.com/2009/01/13/asterisk-e-sip-attacco-e-monitoraggio-tramite-correlazione-di-eventi-utilizzando-sipp-e-sec/</link>
	<description></description>
	<lastBuildDate>Tue, 03 Nov 2009 14:21:52 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Asterisk and SIP: attack and monitoring via event correlation, by using SIPp and SEC &#171; mikeOverIP:~$</title>
		<link>http://mikeoverip.wordpress.com/2009/01/13/asterisk-e-sip-attacco-e-monitoraggio-tramite-correlazione-di-eventi-utilizzando-sipp-e-sec/#comment-77</link>
		<dc:creator>Asterisk and SIP: attack and monitoring via event correlation, by using SIPp and SEC &#171; mikeOverIP:~$</dc:creator>
		<pubDate>Tue, 13 Jan 2009 11:27:12 +0000</pubDate>
		<guid isPermaLink="false">http://mikeoverip.wordpress.com/?p=117#comment-77</guid>
		<description>[...] mikeOverIP:~$     &#171; Asterisk e SIP: attacco e monitoraggio tramite correlazione di eventi, utilizzando SIPp e&#160;SEC [...]</description>
		<content:encoded><![CDATA[<p>[...] mikeOverIP:~$     &laquo; Asterisk e SIP: attacco e monitoraggio tramite correlazione di eventi, utilizzando SIPp e&nbsp;SEC [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
