If you are looking for information on how to build, install and use the sipXecs IP PBX, the best place to start is our documentation wiki. Our focus has always been and will always be to develop great software. Most of the developers use Fedora or SUSE Linux as their environment. While portability is a clear objective of the project, we cannot invest a lot of time in keeping binaries up-to-date for many different OSs and distributions. If you want to help you would be very welcome.

1. Downloads provided by the sipXecs IP PBX project team 

We distinguish between "pub", which includes released and therefore stable versions of sipXecs, and "temp", which is for development and nightly builds of the development branch (main repository or head). Sometimes there is confusion with respect to released versions still being included in the "temp" area. The reason is that released versions of the sipXecs software are in maintenance mode for some time after the initial release. From time-to-time a maintenance release is necessary. These builds happen in the "temp" area until the maintenance release is actually released. Therefore, sometimes you can find a fix scheduled for a maintenance release already included in the stable release build in the "temp" area before the maintenance release is made official and moved over to the "pub" area. Hope this clarifies it. 

• Stable Releases "pub"
• Nightly builds and development releases "temp"
  

a) Subversion source access: Source repository access is possible using Atlassian Fisheye. Subversion checkout from http://sipxecs.sipfoundry.org/rep/sipXecs. Source tarballs can be downloaded from the download areas temp or pub.

b) Support for 64-bit hardware: The sipXecs IP PBX is available both for 32 bit and 64 bit CPUs. Respective RPMs can be downloaded below.

c) PowerPC CPU support: The sipXecs IP PBX builds and works on both Intel/AMD ("little endian") and PowerPC ("big endian") CPU architectures. We do not provide PPC binaries but you can easily build them yourself. PPC builds are known to work on OpenSuSE.

d) Virtual machine setups: The sipXecs IP PBX can run in a virtual machine environment. We tested setups based on XEN and VMWare virtualization technology. At high call volumes into sipXecs media services (i.e. ACD, conferencing, voicemail) it is possible that you experience unsatisfying results. Both these virtualization technologies do not provide reliable real-time clock in their virtual machines, which is the main reason why real-time applications requiring media do not run well at high loads. If you have a solution to this or made different experience please say so on the sipx-dev mailing list.

e) sipXecs High-Availability (HA) configurations: Using the ISO CD installer setting up a high-availability configuration that consists of two servers is done automatically as an installation option. HA configurations with 2 or more servers are possible. Install the sipXecs IP PBX master server first. Additional servers are created from the Web admin user interface. For every additioanl server a password is created by the configuration system that is used during installation of the additional server from CD. The password allows a secure hand-shake so that the configuration for the additional server can be downloaded from the master. Starting with release 4.0 sipXecs provides server roles. Using the centralized configuration management system, sipXconfig, you can define a new server, assign a host name and IP address, and then assign a specific role to that server. Installation and configuration of the additional server is then mainly automatic and all done centrally from sipXconfig.

f) Yum repository: Easiest way to do RPM installs or upgrades is to add the sipXecs yum repository. .repo file provided in the pub or temp area, respectively. Copy the .repo file to /etc/yum.repos.d/.

g) After installing from RPM run the 'sipxecs-setup' initialization wizard before starting sipXecs (release 4.0 and higher). This will check your system, generate the necessary certificates, as well as provide the option to run on-board DNS and DHCP services. CD ISO installs do this automatically running the script 'sipxecs-setup-system'.

h) Troubleshooting: For phone & gateway plug & play configuration to work properly you need a correctly configured DHCP server. For sipXecs to work properly, especially in HA mode, you need a properly configured DNS. sipXecs release 4.0 and higher provide DHCP and DNS tests and troubleshooting info from the admin UI. Most common problems after an RPM install include misconfigured DHCP/DNS or port conflicts with other application. sipXecs uses a lot of ports, among them port 80 and the Apache Web server. sipXecs log files are in /var/log/sipxecs.

i) Admin console is at http://<your host>, or https://<your host>:8443/sipxconfig/LoginPage.html. Admin default user is 'superadmin'. Password set at first login. Every user created on the system has a user portal accessible at the same URL. Login using the UserID and PIN.

Downloads for sipXecs IP PBX latest stable release ("pub"):

Operating Ssytem	Repository	SRC Tarball	SRC RPM	RPM	ISO
	Link	Link	n/a	FC7 FC8
	Link	Link	n/a	Centos5
	Link	Link	n/a	10.2	n/a

Downloads for sipXecs IP PBX development release ("temp"):

Operating Ssytem	Repository	SRC Tarball	SRC RPM	RPM	ISO
	Link	Link	FC8	FC8
	Link	Link	Centos5	Centos5
	Link	Link	11.1	11.1	n/a

CD ISO Downloads: 

Installation CD:  The sipXecs IP PBX Installation CD is based on CentOS5 and allows automated installation of the Linux operating system as well as the sipXecs application onto a new machine. Note: Using this CD will erase all data on the system and format your harddisk. ISO images can be accessed from the ISO download directory.  Documentation is on the documentation Wiki.

LiveCD:  Note: There is no current live CD available. We are planning to create a new live CD at some point. This would be a great area to help.

Installing the Fedora operating system:  We often get asked how to install Fedora or CentOS. sipXecs does not require any special setup. We recommend that you install a minimum system without graphical user interface and without the X server. Make sure you disable both the Firewall and SELinux during installation.  More info is on our Wiki.