Download | sipXecs Downloads |
|
|
|
| Written by Martin Steinmann | |||||||||||||||||||||||||||||||||||||||||||||||||
| Monday, 30 October 2006 | |||||||||||||||||||||||||||||||||||||||||||||||||
|
If you are looking for information on how to build, install and use sipXecs 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 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.
a) Subversion source access: b) Support for 64-bit hardware: All the binaries provided below are compiled for 32-bit. They run on both 32-bit and 64-bit hardware and operating systems. If you are interested in a 64-bit version you have to build it yourself. We are still working on it and that is why the 64-bit version of sipXecs is in a dedicated source branch . Over the next little while we will merge the 64-bit branch back into main. It was successfully tested on 64-bit Fedora and SuSE. c) PowerPC CPU support: The current code in main builds and works on both Intel ("little endian") and PowerPC ("big endian") CPU architectures. We do not provide PPC binaries but you can easily build them yourself. d) Virtual machine setups: We tested setups based on XEN and VMWare virtualization technology with 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. 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. The same process can be done manually as described in the HA Setup Guide. HA configurations with 2 or more servers are possible. It is also possible to run media server and sipXconfig on separate server HW, but it needs to be configured manually. Downloads for sipXecs latest stable release ("pub"):
Downloads for sipXecs development release ("temp"):
Why is the installation CD still based on Fedora Core 6? In order to create this CD we reverse engineered the Red Hat Anaconda based installation process, which is a very cumbersome approach. Starting with Fedora 7 Red Hat released their release engineering tool called Pungi. We are in the process of changing the CD creation process to using Pungi, but have been hampered by feature deficiencies of Pungi and bugs. We will keep banging at it and get it done at some point. Help would be appreciated. Installing the Fedora operating system: We often get asked how to install Fedora. 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. 2. Community Supported Downloads for different Operating Systems and Linux Distributions: Since binary packages are provided by different community packagers, they are located in different repositories. Most of the sipXecs developers work on Fedora Core or CentOS. That's why the FC / CentOS distributions are the best supported and tested. Detailed information on different Linux distributions and other operating systems is available on the Wiki. We are looking for maintainers. If you are interested please say so on the sipx-dev mailing list.
FreeBSD builds:
|
|||||||||||||||||||||||||||||||||||||||||||||||||
| Last Updated ( Monday, 17 March 2008 ) | |||||||||||||||||||||||||||||||||||||||||||||||||
| Start Here |
| Unified Communications |
| Screenshots |
| Roadmap |
| sipXecs Datasheet |
| Phones & Gateways |
| SIP Trunking Interop Program |
| How to communicate |
| Jira Issue Tracker |
| sipXecs Google search |
| 2nd User Group Event |
| sipXecs Wiki |
| sipXconfig Manual |
| Phones & Gateways |
| Linux Distributions |
| Presentations |
| HowTo Library |
| SFTF user guide |
| SFTF developer guide |