sipXcom should be installed on servers with only a single network adapter.
64 bit builds only are available.
Here's a video walkthrough of a complete RPM installation of 15.06 on CentOS 6.6 64-bit Minimal.
Note: Install sipXcom by using an Install DVD is an easy and fast way to setup a ready-to-go system
- Follow instructions here.
- After installation, run a yum update to get the latest fixes.
1. Install sipXcom over an existring pre-installed Operating System (Fedora 19 or CentOS 6 minimal) through yum
- Install Fedora 19 or CentOS/RHEL 6.6 64 bit by using the minimal installation option.
- Only minimum installation is necessary, in fact this is preferred. All of packages that sipXcom needed will be then installed automatically.
- Be sure to run
yum updatejust after installing your OS and before installing sipXcom applications to ensure the latest RPMs are installed but also to avoid conflict errors when new packages are getting installed.
- CentOS/RHEL 6 is the preferred distribution because it has received the most testing coverage.
- 64 bit version of the distribution as it's preferred by MongoDB: the embedded distributed database package.
NOTES - On CentOS
- Minimal install - be sure to click on "Network Connectivity" button on same screen where you assign the host name. If you don't - you will have to manually configure your Ethernet Interface file!
On first boot - you may need to edit your /etc/sysconfig/network-scripts/YourNICCard Change ONBOOT="no" to ONBOOT="yes"
"yum install wget" to install the wget program required to download your RPM files.
2. Increase Max Number of ulimit open files and max user processes for MongoDB
- edit /etc/sysctl.conf to add fs.file-max = 65536 line
- edit /etc/security/limits.conf to add the following block of text:
3. Add the Repository repo file (example to install sipXcom 17.04, you may need to 'yum install wget' on CentOS Minimal install)
4. Install sipxcom (use "yum install sipxecs" in versions prior to 15.10)
5. Run setup and answer basic questions.
6. After initial setup and before configuring the system, reboot the server.
7. After couple of minutes, the administration web interface should be available at
Note: Some browsers are disallowing self-signed certificates (IE and Chrome). Try using FireFox and adding in the self-signed certificate as trusted to get by. Then get a certificate added as soon as possible. See: Certificates
At this point, you may want to consider reading the Quick Start page skip to the section that starts with logging into administration user interface.