Page tree

Versions Compared

Key

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

...

If you have questions about updating you can email sa@ezuce.com or if you need assistance with the update please contact your account manager or email sales@ezuce.com.

Software Release History

We're currently running on a 4-month release cycle.

  • April release for 2018 is 18.04
  • August release for 2018 is 18.08
  • ...

 

Release Level History

  • 14.04   - April 30, 2014
  • 14.04.1 - June 01, 2014
  • 14.04.2 - July 11, 2014
  • 14.04.3 - October 24, 2014
  • 14.10 - February 5, 2015
  • 15.04 - April 29, 2015
  • 15.05 - May 27, 2015
  • 15.06 - June 30, 2015
  • 15.08 - August 31, 2015
  • 15.10.1 - December 9, 2015
  • 15.12 - January 6, 2015
  • 16.02 - March 14, 2016
  • 16.04 - May 31, 2016
  • 16.08 - October 6, 2016
  • 16.12 - January 17, 2016
  • 17.04 - April 18, 2017
  • 17.08 - September 7, 2017
  • 17.10 - December 7, 2017
  • 18.04 - June 5, 2018
  • 18.08 - September 7, 2018
  • 18.12 - January 15, 2019
  • 19.04 - May 28, 2019
  • 19.08 - October 10, 2019
  • 19.12 - February 13, 2020

System Requirements

For a reasonably performing system, we recommend the following configuration.

Minimum hardware requirements

  • Pentium 4 or Xeon processor @ 2.0 GHz 64bit or higher
  • Minimum 4 GB of RAM with sufficient swap space
  • 40 GB disk (75 users depending on usage patterns, VoiceMail consumes ~ 1 MB per minute so scale appropriately for your user count and anticipated VM retention policy)
  • As with anything server wise, more CPU/RAM/DISK = better.

Notes:

  • uniteme supports an unlimited number of voicemail 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 7 x86_64 minimal with latest updates is required (recommended now).

Devices

Phones

  • Polycom VVX Devices with firmware 5.9.1 (split) are recommended for new installations
  • Polycom SoundPoint IP Devices should run firmware 4.0.14 (split)

Gateways

  • AudioCodes Gateways are recommended for PSTN connectivity

SBCs

  • Frafos, Sangoma, Acme Packet and Ingate SBC's are recommended for SIP Trunking and Remote Worker connectivity (commonly referred to as sipXbridge and MediaRelay services respectively).
  • NOTE: The eZuce uniteme - "Use built-in SIP Trunk SBC" found in Gateway Details for use with Trunking or Remote Worker solutions should be used only for lab purposes. Additionally, sipXbridge does not work in an HA environment.

Documentation

Technical Reference Manuals, User Guides, and other technical and user information can be found under the following link: Documentation Page

Installation and Upgrade Notes

Special MongoDB note

Please be aware of these Mongodb requirements http://docs.mongodb.org/manual/reference/ulimit/ 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 64000
mongodb hard nproc 64000

...

mongodb hard nofile 64000

Special Patch Note

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

Installing from Repository

uniteme can be installed using the following procedure

  1. Download CentOS 7 64 bit Minimal ISO from CentOS (https://www.centos.org/download/)
  2. Install CentOS 7. (Installing#InstallRedHatEnterpriseLinux7.xorCentOS7.x)
  3. Install uniteme. (Installing#Installuniteme)

Upgrade from previous versions

New Procedure

We will be utilizing an upgrade script to ensure upgrades proceed as intended and so that customers have the appropriate warnings and information before upgrading.

Warning!

Make sure you backup your system (configuration and voicemail at a minimum) prior to installation.

...

Upgrade 18.12 or later and already on CentOS 7

Modify your yum repo file for Uniteme (it's in the directory /etc/yum.repos.d) for the release you'd like to use.

Upgrade to 18.12 or later CentOS 6 to CentOS 7

Any upgrade to CentOS 7 will require a fresh installation of CentOS 7 and then a restore of uniteme.

Backup your System

Login to the Admin GUI and click on System -> Backup and at a minimum backup configuration and voicemail.

Download the configuration and voicemail backup archives.

Build New CentOS 7 Server

Download CentOS 7 64 bit Minimal ISO from CentOS (https://www.centos.org/download/)

Install CentOS 7. (Installing#InstallRedHatEnterpriseLinux7.xorCentOS7.x)

Install uniteme. (Installing#Installuniteme)

Restore your System

Restore configuration and voicemail.

Remove any secondary servers restored from the Servers page.

Send Server Profile.

Reboot

Add Secondary Servers

Rebuild and re-add any secondary servers.

Upgrade to 19.04 or later for CentOS 6 Single Server systems for 18.04 (CentOS 6) and Older

...

Adjust your /etc/yum.repos.d/openuc.repo file to point to the version of openUC you'd like to upgrade to.

For example:

When you are ready to perform the actual upgrade:

yum update
or
yum update -y

If your system is a highly available cluster of 3 or more servers, update the secondary servers first and the primary server last. Send send all of the server profiles when done update on the primary server.

Upgrade for 18.12 or later CentOS 6 to CentOS 7

Any upgrade to CentOS 7 will require a fresh installation of CentOS 7 and then a restore of uniteme.

Backup your System

Login to the Admin GUI and click on System -> Backup and at a minimum backup configuration and voicemail.

Do it now... before you go any further.

Download

...

Login to the primary server as root.

Execute the following:

wget https://download.ezuce.com/unite-upgrade.sh
chmod +x unite-upgrade.sh

Run upgrade.sh

Execute the upgrade script and answer 'Yes' to continue:

./unite-upgrade.sh

The following will be displayed:

Uniteme 19.12 Upgrade Script
IMPORTANT: If this is a multi-server cluster, all databases except the Primary (which must be on the configuration server) should be removed.
IMPORTANT: You should run a system backup and copy your config and voicemail backups to another system. If the upgrade fails, you will need to build a new server and restore from backup.
IMPORTANT: Ensure that you have enough disk space available for a copy of the Mongo databases. (roughly your Config + Voicemail backups).
IMPORTANT: 18.08 does not have Reachme in it, if you use Reachme on this server or in the cluster, do not continue!
This script will do the following:
- Back up mongo config and dbs
- Stop mongo instance and remove old mongo files
- Change XX.XX occurrences in /etc/yum.repos.d with 19.08
- Perform yum update and then reboot the machine
On sipxconfig service startup following steps are taken (in case there is a backup still on the disk):
- Restore mongo config and dbs, then remove from disk
- Reboot machine
For other cluster servers:
- Run same script
- Re-add databases that were removed.
Continue? (you must enter Yes or No as shown and press Enter):

...

the configuration and voicemail backup archives.

Build New CentOS 7 Server

Download CentOS 7 64 bit Minimal ISO from CentOS (https://www.centos.org/download/)

Install CentOS 7. (Installing#InstallRedHatEnterpriseLinux7.xorCentOS7.x)

Install uniteme. (Installing#Installuniteme)

Restore your System

Restore configuration and voicemail.

Remove any secondary servers restored from the Servers page.

Send Server Profile.

Reboot

Add Secondary Servers

Rebuild and re-add any secondary servers.


Modified Files Upgrade Note

If you have manually modified any system related files or some files are not as yum would expect them to be, the yum update process may not overwrite them. It will instead create 'rpmnew' or 'rpmsave' files and not overwrite the files. The administrator may have previously modified the files knowingly or as part of a patch supplied by TAC.

To check your upgrade.log and search for *.rpmnew *.rpmsave on your system check the upgrade log:

You will be responsible for merging any changes from the old file to the new or contacting Technical Support if you require assistance.

Support Tips and Contact Information 

Please see the Getting Support section for support tips and support contact information

Specific Issues Addressed

...