Child pages
  • sipXcom 14.04

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

eZuce openUC 14.04 Release Notes

Table of Contents


This section describes the eZuce openUC 14.04 software release, including:

Software Release History

Starting with the April 2014 release, OpenUC will have a regular release cycle for new features and a new versioning schema which incorporates the Year and Month of release.

Release Level History

New Features

Release 14.04.4

Release 14.04.3

MongoDB Enhancements

Release 14.04.2

There are no new features delivered in 14.04.2

Release 14.04.1

There are no new features delivered in 14.04.1

Release 14.04

System Requirements

For a reasonably performing system we recommend the following configuration.

Minimum hardware requirements

Note: sipXcom supports an unlimited number of voice-mail boxes,the total number of hours of recorded messages is determined by the size of the hard-disk. As a rule, for every minute of recorded messages you will need 1 MB of disk space (About 3 hours per 10 GB of disk space).

Operating System:

CentOS/RHEL 6 x86_64 with latest updates is required.An i386 version is also provided as is (without any support).


Installation and Upgrade Notes

Installation note for 14.04.3

After sipXcom 14.04.3 is downloaded and installed,the clusterId read tag is unique (same as locationId). Follow these steps to propagate the new read tags to the MongoDB replica set:

  1. In the OpenUC menu, click System>Database.
  2. Click the Add query metadata button.
  3. To verify that the MongoDB replica contains the unique read tags, run in the command line:
mongo rs.config();

Special MongoDB note

Please be aware of this Mongodb requirements“Note: Both the “hard” and the “soft” ulimit affect MongoDB’s performance. The “hard” ulimit refers to the maximum number of processes that a user can have active at any time. This is the ceiling: no non-root process can increase the “hard” ulimit. In contrast, the “soft” ulimit is the limit that is actually enforced for a session or process, but any process can increase it up to “hard” ulimit maximum.Every deployment may have unique requirements and settings; however, the following thresholds and settings are particularly important for mongod and mongos deployments:

ulimit –a
-f (file size): unlimited
-t (cpu time): unlimited
-v (virtual memory): unlimited
-n (open files): 64000
-m (memory size): unlimited
-u (processes/threads): 32000

Always remember to restart your mongod and mongos instances after changing the ulimit settings to make sure that the settings change takes effect.If you limit virtual or resident memory size on a system running MongoDB the operating system will refuse to honor additional allocation requests.After every install/upgrade please check that "cat /proc/$pid_of_mongo/limits" have the recommended value of 655350. To make this value permanent you need to create this file /etc/security/limits.d/99-mongodb-nproc.conf and add the following lines:mongodb soft nproc 64000mongodb hard nproc 64000mongodb soft nofile 64000mongodb hard nofile 64000 .

This note also applies to the 14.04.3 release.

If you have a patch installed to your system a new patch may be required. Please contact if think you may have a patch applied as that may be replaced during the update.


Installing from ISO image

Download sipxcom ISO

Download the ISO image corresponding to your hardware and write the image to a DVD.

Install sipXcom

Installing from Repository

sipXcom can be installed using the below procedure

yum update && reboot

This utility will guide you through the process of installing openUC from the eZuce software repository.

Upgrade from sipXecs 4.4


More information and solutions to the above issues can be obtained by accessing our KnowledgeBase

Upgrade from sipXecs 4.4 is based on the following backup/restore procedure:

  • Create a backup of the current sipXecs 4.4 system
  • Install a fresh sipXcom 14.04 on a new machine. Finish the installation and configuration by running sipxecs-setup to obtain access to WebUI
  • Restore 4.4 configuration on the new sipXcom 14.04 system.

Upgrade from sipXcom 4.6

Upgrade from sipXcom 4.6 is based on the procedure:


Special NOTE for sipXecs 4.6 Versions Older than Update 9

The pymongo package in our sipXecs repository is outdated and should be replaced with the differently named but newer version python-pymongopackage from the EPEL repository. This allows pymongo to upgrade along with other OS packages from the upstream provider (EPEL) rather than sipXcom repository.

Error: Package: pymongo-2.4.2-1.el6.x86_64 (@openuc)
Requires: python-bson = 2.4.2-1.el6
Removing: python-bson-2.4.2-1.el6.x86_64 (@openuc)
python-bson = 2.4.2-1.el6
Updated By: python-bson-2.5.2-3.el6.x86_64 (epel)
python-bson = 2.5.2-3.el6
Available: python-bson-2.1.1-1.el6.x86_64 (epel)
python-bson = 2.1.1-1.el6
You could try using --skip-broken to work around the problem

DO NOT run yum update --skip-broken to proceed!!!!

As mentioned, the pymongo package in our openUC repository is outdated and should be replaced with the differently named but newer version python-pymongo package from the EPEL repository. This allows pymongo to upgrade along with other OS packages from the upstream provider (EPEL) rather than sipXcom repository. To do so, run these commands:

rpm -e --nodeps pymongo
yum install python-pymongo -y
curl > /usr/bin/openuc-setup
chmod +x /usr/bin/openuc-setup

After rebooting the system:

Known Issues

Backup & Restore

Release 14.04.3

Release 14.04.2

Release 14.04.1

Release 14.04


Release 14.04.3

Release 14.04.2

Release 14.04.1

Release 14.04


Release 14.04.3

Release 14.04.2

Release 14.04.1

Release 14.04

Resolved Internally Reported Issues

Release 14.04.3

Resolved Customer Reported Issues

Release 14.04.4

Release 14.04.2

Release 14.04.1

Release 14.04