Downloads

• Release 4.2.1 RPMs for 32 bit and 64 bit, and distributions CentOS 5.4, RHEL, F11, F12
• Release 4.2.1 CD ISO 32 bit and 64 bit, CentOS 5.4

git source access: Source repository is at github: http://github.com/dhubler/sipxecs

The git repo includes source for the community 4.2.1 builds as well as the current main sipXecs repository.

Community builds include additional features as compared to Avaya builds, include the latest 4.2.1 patches and are made available for more distributions. The CentOS installation CD was updated to the latest CentOS release 5.5 and is available in 32 and 64 bit.

Note: The sipXecs main repository maintained by Avaya is currently unavailailable since May 13th.

Comments regarding all downloads

a) Installation CDs: Community downloads include installation CDs for CentOS 5.5 for both 32 bit and 64 bit OS. Avaya provides an installation CD for CentOS 5.2 / 32 bit only.

b) Other Linux distributions: The main distribution for sipXecs is CentOS / RHEL. Community downloads provide builds for Fedora 12. In addition, community downloads provide preview versions that run on SLES 11, openSUSE 11.1 and openSUSE 11.2. SUSE installation CDs, VMWARE images, Life CDs, XEN images and USB stick images are available as well.

c) Support for 64-bit hardware: The sipXecs IP PBX is available both for 32 bit and 64 bit CPUs.

d) 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 build them yourself.

e) 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.

f) sipXecs High-Availability (HA) configurations: Using the ISO CD installer setting up a high-availability configuration that consists of two or more 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.

g) 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/.

h) 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'.

i) 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.

j) 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.

k) Installing the 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.