<?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: HowTo: Securing Elastix</title>
	<atom:link href="http://automation.binarysage.net/?feed=rss2&#038;p=175" rel="self" type="application/rss+xml" />
	<link>http://automation.binarysage.net/?p=175</link>
	<description>Cheap Versatile UK Home Automation</description>
	<lastBuildDate>Mon, 30 Aug 2010 00:09:03 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Adam</title>
		<link>http://automation.binarysage.net/?p=175&#038;cpage=1#comment-130</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Fri, 28 May 2010 06:17:53 +0000</pubDate>
		<guid isPermaLink="false">http://automation.binarysage.net/?p=175#comment-130</guid>
		<description>Justin,

Sorry for that.  It pointed to an article that was scheduled for publication this morning.  This has now happened, so the link to this document on SIP Trunks should work.  It certainly does for me.

When I added the cross link, I forgot it was a scheduled post, oops, definitely my fault.  I often schedule be most of my articles to &#039;published&#039; early on a Friday morning so I can have a &#039;stock&#039; ready to go.  But sometimes I cross reference them before they are published formally.  I will try to be more observant in the future.

Adam.</description>
		<content:encoded><![CDATA[<p>Justin,</p>
<p>Sorry for that.  It pointed to an article that was scheduled for publication this morning.  This has now happened, so the link to this document on SIP Trunks should work.  It certainly does for me.</p>
<p>When I added the cross link, I forgot it was a scheduled post, oops, definitely my fault.  I often schedule be most of my articles to &#8216;published&#8217; early on a Friday morning so I can have a &#8216;stock&#8217; ready to go.  But sometimes I cross reference them before they are published formally.  I will try to be more observant in the future.</p>
<p>Adam.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://automation.binarysage.net/?p=175&#038;cpage=1#comment-129</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Thu, 27 May 2010 20:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://automation.binarysage.net/?p=175#comment-129</guid>
		<description>Your link for &quot;HowTo: Elastix Incoming SIP Trunk Calls&quot; is dead. I did a search for &quot;incoming&quot; and the article wasn&#039;t found that way either. I&#039;d love to read your advice on setting that up if you have the article and just haven&#039;t published it.</description>
		<content:encoded><![CDATA[<p>Your link for &#8220;HowTo: Elastix Incoming SIP Trunk Calls&#8221; is dead. I did a search for &#8220;incoming&#8221; and the article wasn&#8217;t found that way either. I&#8217;d love to read your advice on setting that up if you have the article and just haven&#8217;t published it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
