AWS sipXcom cloud communicationsMore and more frequently we’re (eZuce) being asked to assist with implementing a communications system in ‘the cloud’. This typically means moving to a platform like Amazon Web Services (AWS) or Google Compute Engine. These systems all have quirks that you need to sort out. For instance, if you want to deploy in AWS you’ll want to spend some time understanding the VPC configurations and routing between regions vs. routing between availability zones.

For many organizations, running your communications system from a hosted platform has three major advantages:

Disaster Recovery – The system is off-site and will keep operating even if your physical location(s) can’t. At a minimum your system will take calls and voicemail. If a system’s designed so that users can connect to it from wherever they might be, your users can work from home or some temporary location.

Operate a single system with centralized trunking – The ability to centralize your trunking or bring it into just a couple locations for failover allows for economies of scale, not having to build over capacity at several locations and other benefits.

Reduced maintenance costs – By having a single system fewer servers will be required which will in-turn reduce maintenance costs.

In an effort to help the community get started with systems in the cloud, eZuce published a detailed guide to getting a server setup and running in AWS. This setup includes all of the required detail even setting up AWS’s Firewall and VPC settings.

If your needs are a little more complex and you need assistance getting a production system in the cloud, eZuce would be glad to help!

So, get ready to learn how to build an Open Source Communications System that runs in AWS with this step by step guide:

The Ultimate Guide to creating Your own Cloud Communications System


More About the sipXcom Project:

From 2010 to 2015, sipXecs primary development contributions were provided by the development team at eZuce, Inc. The sipXcom open source communications project was established in January of 2015 from a fork in the sipXecs project by the development team at eZuce, Inc. With the creation of sipXcom, this team shifted its focus to contributing to the new project and no longer maintains sipXecs code nor participate in the SIPfoundry forums.

The experts who have helped to build sipXecs into the incredible product that it is will be found in the Google Groups ( and (