December 7, 2011 – 6:58 pm | 16 Comments

3CX is pleased to announce a new release of 3CX Phone System 10, build 22686. Service Pack 5 fixes numerous 3CX Wallboard issues and also adds a new and important caller ID feature. To download …

Read the full story »
Releases

3CX Product Releases

VoIP How To

Technical tips to run your VoIP PBX more efficiently

Events

3CX Trainings and Webinars around the world

Docs & FAQ

3CX Documentation how to and FAQ

Phone configuration

3CX, Aastra, Cisco, Yealink, Grandstream, Polycom configs

Home » VoIP How To

Microsoft IIS or Ultidev Cassini – Which do you use?

Submitted by on January 22, 2010 – 1:39 pm5 Comments
Ultidev logo

Ultidev Cassini

3CX can be deployed using Microsoft IIS or Ultidev Cassini as the webserver. For larger environments IIS is recommended but for small installations ( up to 25 extensions) Ultidev Cassini can be used. Ultidev Cassini is a light weight web server developed by UltiDev, using the Microsoft Cassini web server as a base. On Windows XP, 3CX only supports Ultidev Cassini. We would be interested to know which web server you use with 3CX:

It should be noted that in the past we have referred to the Cassini web server as Microsoft Cassini, however it should be referred to as “Ultidev Cassini“. The next build of 3CX Phone System will reflect this change in the setup as well as in the service name.

5 Comments »

  • Jim Green says:

    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

  • Nick Galea says:

    Hi Jim, thanks for the feedback. Yes, we believe its important to have both options based on the size of the implementation.

  • 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.

  • 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’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.

  • Nicky says:

    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 – >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.