<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Excalibur Partners, LLC &#124; IT Consulting</title>
	<atom:link href="http://www.excaliburtech.net/feed" rel="self" type="application/rss+xml" />
	<link>http://www.excaliburtech.net</link>
	<description>Technical References</description>
	<lastBuildDate>Sat, 12 Nov 2011 20:24:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Asterisk 1.8 Caller ID Wrong in CDR</title>
		<link>http://www.excaliburtech.net/archives/229</link>
		<comments>http://www.excaliburtech.net/archives/229#comments</comments>
		<pubDate>Mon, 24 Oct 2011 03:46:54 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[VOIP]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=229</guid>
		<description><![CDATA[After upgrading to Asterisk 1.8 from 1.6.1 I noticed the CALLERID() function was not updating the clid and src fields in the CDR. Previously on Asterisk 1.6.1 with FreePBX 2.7 the clid and src would be set to the outbound cid. With Asterisk 1.8 those fields were staying as the sip device id. After looking [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/229/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Installing mcrypt for PHP 5.3 on CentOS 5.6</title>
		<link>http://www.excaliburtech.net/archives/222</link>
		<comments>http://www.excaliburtech.net/archives/222#comments</comments>
		<pubDate>Mon, 24 Oct 2011 03:34:44 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=222</guid>
		<description><![CDATA[With CentOS 5.6 Red Hat added an optional php53 package for those that need a PHP version later than 5.1.6. After removing the php packages and installing php53 you will probably notice that the mcrypt extension is missing. With a few steps we can compile and install this extension. yum install php53-devel libmcrypt-devel gcc cd [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/222/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>pfSense 1.2.3 vs Vyatta 6.1</title>
		<link>http://www.excaliburtech.net/archives/210</link>
		<comments>http://www.excaliburtech.net/archives/210#comments</comments>
		<pubDate>Tue, 28 Dec 2010 04:52:46 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Firewalls]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[pfSense]]></category>
		<category><![CDATA[Vyatta]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=210</guid>
		<description><![CDATA[I have been a long time pfSense user starting back in 2006. Recently I switched my main firewall from pfSense to Vyatta. It was a tough choice as both platforms have their advantages and disadvantages. pfSense is based on FreeBSD and uses the BSD packet filter along with ipfw. The console is used for basic [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/210/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Configuring Vyatta with an IPv6 Tunnel Broker</title>
		<link>http://www.excaliburtech.net/archives/198</link>
		<comments>http://www.excaliburtech.net/archives/198#comments</comments>
		<pubDate>Sun, 10 Oct 2010 02:34:00 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Firewalls]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Vyatta]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=198</guid>
		<description><![CDATA[One way to get connected to the IPv6 network is by using a tunnel broker. The broker provides an IPv4 endpoint to send IPv6 encapsulated packets. This works best if you have a static IPv4 address. The tunnel broker needs to be configured to send packets for your IPv6 address range to your IPv4 address. [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/198/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Disabling IPv6 Stateless Autoconfiguration</title>
		<link>http://www.excaliburtech.net/archives/192</link>
		<comments>http://www.excaliburtech.net/archives/192#comments</comments>
		<pubDate>Sat, 09 Oct 2010 21:12:04 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[IPv6]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=192</guid>
		<description><![CDATA[I have Vyatta setup to send out router advertisements so clients are auto configured with an IPv6 address. This works great for workstations, but I prefer servers to be manually configured. The auto configured address on Linux is built from the MAC address and on Windows it is randomly generated. When assigning a static IPv6 [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/192/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Asterisk Called Party Name</title>
		<link>http://www.excaliburtech.net/archives/183</link>
		<comments>http://www.excaliburtech.net/archives/183#comments</comments>
		<pubDate>Sat, 03 Jul 2010 02:16:39 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[VOIP]]></category>
		<category><![CDATA[FreePBX]]></category>
		<category><![CDATA[Polycom]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=183</guid>
		<description><![CDATA[With a traditional PBX when dialing an extension the name is displayed on the phone. With Asterisk 1.4 and 1.6.x the name is not displayed even though phones, like the Polycom SoundPoint series, have support for it with the Remote-Party-ID SIP header. On the Asterisk issue tracker there was a proposed patch for Asterisk 1.2. [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/183/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Polycom Soft Keys and Exchange UM</title>
		<link>http://www.excaliburtech.net/archives/162</link>
		<comments>http://www.excaliburtech.net/archives/162#comments</comments>
		<pubDate>Sat, 06 Mar 2010 21:32:09 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[VOIP]]></category>
		<category><![CDATA[Exchange UM]]></category>
		<category><![CDATA[Polycom]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=162</guid>
		<description><![CDATA[In Asterisk 1.6, FreePBX, and Exchange UM I mentioned how to setup an extension to transfer a caller to voicemail. Let&#8217;s take this one step further and add a soft key on the Polycom. Instead of having to dial ##407ext, you will be able to press the Xfer VM button and it will prompt for [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/162/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Polycom BLF with Astersisk</title>
		<link>http://www.excaliburtech.net/archives/147</link>
		<comments>http://www.excaliburtech.net/archives/147#comments</comments>
		<pubDate>Sat, 06 Mar 2010 21:06:13 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[VOIP]]></category>
		<category><![CDATA[FreePBX]]></category>
		<category><![CDATA[Polycom]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=147</guid>
		<description><![CDATA[They are two methods of setting up BLF on Polycom phones. The first gives you idle or inuse status only. A ringing phone will show up with a solid inuse light. The good thing about this method is users can create BLF for extensions themselves. If this is all you need start by enabling the [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/147/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Asterisk 1.6, FreePBX and Exchange UM</title>
		<link>http://www.excaliburtech.net/archives/130</link>
		<comments>http://www.excaliburtech.net/archives/130#comments</comments>
		<pubDate>Mon, 01 Mar 2010 04:26:12 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[VOIP]]></category>
		<category><![CDATA[Exchange UM]]></category>
		<category><![CDATA[FreePBX]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=130</guid>
		<description><![CDATA[Setting up Asterisk 1.6.1 and FreePBX 2.5 or 2.6 to work with Exchange 2007 UM is easier than Asterisk 1.4 thanks to Asterisk 1.6 including support for SIP over TCP. However only Asterisk 1.6.1.4 and lower work without modification. The ability to redirect according to Moved Temporarily response from Exchange UM broken in version 1.6.1.5, [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/130/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Asterisk and FreePBX Caller Initiated Blind Transfers</title>
		<link>http://www.excaliburtech.net/archives/126</link>
		<comments>http://www.excaliburtech.net/archives/126#comments</comments>
		<pubDate>Mon, 01 Mar 2010 02:54:51 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[VOIP]]></category>
		<category><![CDATA[FreePBX]]></category>

		<guid isPermaLink="false">http://www.excaliburtech.net/?p=126</guid>
		<description><![CDATA[If you place a call and perform a blind transfer Asterisk will continue dialplan execution with a result of ANSWER. This causes an issue with FreePBX as it thinks dialing on the trunk failed. The transfer will go through, but you receive the all circuits are busy message. The first time I reported this issue [...]]]></description>
		<wfw:commentRss>http://www.excaliburtech.net/archives/126/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

