<?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: Microsoft IIS or Ultidev Cassini &#8211; Which do you use?</title>
	<atom:link href="http://www.3cx.com/blog/voip-howto/microsoft-iis-or-ultidev-cassini-which-do-you-use/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.3cx.com/blog/voip-howto/microsoft-iis-or-ultidev-cassini-which-do-you-use/</link>
	<description>Information about VOIP, SIP, 3CX Phone System</description>
	<lastBuildDate>Thu, 09 Feb 2012 12:54:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Nicky</title>
		<link>http://www.3cx.com/blog/voip-howto/microsoft-iis-or-ultidev-cassini-which-do-you-use/comment-page-1/#comment-3773</link>
		<dc:creator>Nicky</dc:creator>
		<pubDate>Fri, 29 Jan 2010 17:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.3cx.com/blog/?p=1290#comment-3773</guid>
		<description>Yes Cassini is good because it is independent from Windows Updates. Also it does not have permission problems on the machine. It is lightweight and serves the 3CX Phone System well. It all depends on the amount of extensions you have in your 3CX Phone System.
Golden rule - &gt;40 extensions - Go for Cassini. 
  
Now with 3CX Version 8.0.10824 we made major improvements on the way we register web applications in Cassini making it more reliable and reducing socket problems. 

IIS is faster so for large implementations, IIS is the way to go. Even if you depend on provisioning, and you want to provision the phones with both the provisioning file and their firmware image, IIS is the best solution. Digital receptionists play an important part because these requests are web related with VXML so consider this point when choosing your webserver. If your company makes heavy use of Digital receptionists, queues or voicemail, keep this in mind.</description>
		<content:encoded><![CDATA[<p>Yes Cassini is good because it is independent from Windows Updates. Also it does not have permission problems on the machine. It is lightweight and serves the 3CX Phone System well. It all depends on the amount of extensions you have in your 3CX Phone System.<br />
Golden rule &#8211; &gt;40 extensions &#8211; Go for Cassini. </p>
<p>Now with 3CX Version 8.0.10824 we made major improvements on the way we register web applications in Cassini making it more reliable and reducing socket problems. </p>
<p>IIS is faster so for large implementations, IIS is the way to go. Even if you depend on provisioning, and you want to provision the phones with both the provisioning file and their firmware image, IIS is the best solution. Digital receptionists play an important part because these requests are web related with VXML so consider this point when choosing your webserver. If your company makes heavy use of Digital receptionists, queues or voicemail, keep this in mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lewis Sheridan</title>
		<link>http://www.3cx.com/blog/voip-howto/microsoft-iis-or-ultidev-cassini-which-do-you-use/comment-page-1/#comment-3759</link>
		<dc:creator>Lewis Sheridan</dc:creator>
		<pubDate>Fri, 29 Jan 2010 00:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.3cx.com/blog/?p=1290#comment-3759</guid>
		<description>Cassini nicely sandboxes the web server side from a recover and restore perspective - and also just removes complexity in the troubleshooting process, and windows updates. Most of our deployments are 10-30 extensions owing to our customers size. It does introduce the funny :5481 in the management and provisioning URLs, but convenience always comes with a small cost. Irrespective I&#039;m sure there are those that will be in the IIS camp, and those in the Cassini camp - whatever works easiest in my opinion wins :) and Happy Cassini is available and long may it continue.</description>
		<content:encoded><![CDATA[<p>Cassini nicely sandboxes the web server side from a recover and restore perspective &#8211; and also just removes complexity in the troubleshooting process, and windows updates. Most of our deployments are 10-30 extensions owing to our customers size. It does introduce the funny :5481 in the management and provisioning URLs, but convenience always comes with a small cost. Irrespective I&#8217;m sure there are those that will be in the IIS camp, and those in the Cassini camp &#8211; whatever works easiest in my opinion wins :) and Happy Cassini is available and long may it continue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Hanson</title>
		<link>http://www.3cx.com/blog/voip-howto/microsoft-iis-or-ultidev-cassini-which-do-you-use/comment-page-1/#comment-3736</link>
		<dc:creator>Matthew Hanson</dc:creator>
		<pubDate>Mon, 25 Jan 2010 21:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.3cx.com/blog/?p=1290#comment-3736</guid>
		<description>I tend to use Cassini.  Outside of TLS/SSL email authentication, there seems to be very little difference in feature sets, and we tend to see a good percentage of users already utilizing IIS in other applications.</description>
		<content:encoded><![CDATA[<p>I tend to use Cassini.  Outside of TLS/SSL email authentication, there seems to be very little difference in feature sets, and we tend to see a good percentage of users already utilizing IIS in other applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Galea</title>
		<link>http://www.3cx.com/blog/voip-howto/microsoft-iis-or-ultidev-cassini-which-do-you-use/comment-page-1/#comment-3725</link>
		<dc:creator>Nick Galea</dc:creator>
		<pubDate>Mon, 25 Jan 2010 05:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.3cx.com/blog/?p=1290#comment-3725</guid>
		<description>Hi Jim, thanks for the feedback. Yes, we believe its important to have both options based on the size of the implementation.</description>
		<content:encoded><![CDATA[<p>Hi Jim, thanks for the feedback. Yes, we believe its important to have both options based on the size of the implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Green</title>
		<link>http://www.3cx.com/blog/voip-howto/microsoft-iis-or-ultidev-cassini-which-do-you-use/comment-page-1/#comment-3714</link>
		<dc:creator>Jim Green</dc:creator>
		<pubDate>Sat, 23 Jan 2010 23:51:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.3cx.com/blog/?p=1290#comment-3714</guid>
		<description>Just as noted, when we install a small system or use XP we use Cassini. When we do over 25 stations or  sell over 16 Concurrent Calls,with server software we use IIS</description>
		<content:encoded><![CDATA[<p>Just as noted, when we install a small system or use XP we use Cassini. When we do over 25 stations or  sell over 16 Concurrent Calls,with server software we use IIS</p>
]]></content:encoded>
	</item>
</channel>
</rss>

