February 13, 2020

Summary

eZuce is pleased to announce the General Availability of Uniteme 19.12. 

This will be a fairly light update with mostly bug fixes for Uniteme. This is largely because we decided to update FreeSwitch to version 1.10 to be able to add a new enhancement. This adds additional regression testing overhead.

We've waited a little bit longer with this GA announcement to allow for some additional testing and additional community adoption of 19.12.

Highlights

uniteme New Features:

• Read the user's name for voicemail users who have not recorded a name
• Let's Encrypt Certificate support

uniteme Improvements:

• Upgrade FreeSwitch to 1.10
• Bug fixes

Notes

1. Full Release Notes with installation information are located here: 19.12 Full Release Notes
2. 19.08 and later are now released on CentOS 7 only. This will require that administrators install CentOS 7 minimal, then install Uniteme with our single line installer and then restore from a previous version backup.
3. Customers receiving faxes through AudioCodes devices will need to modify their AudioCodes configurations with the following settings changes:

[Voice Engine Params]

CallerIDType = 0

FaxTransportMode = 0

CNGDetectorMode = 0

[SIP Params]

CHANNELSELECTMODE = 0

ISFAXUSED = 0

SIPTRANSPORTTYPE = 0

[ CodersGroup0 ]

CodersGroup0 0 = "g711Ulaw64k", 20, 0, -1, 0;

4. For Let's Encrypt certificates to work properly, the server must have a valid outside DNS name and have port 80 and 443 open to LE's servers.

Who Should Install?

This release is recommended for all 4.6 and later installations. If you have a patch installed to your system a new patch may be required. Please contact sa@ezuce.com if you think you may have a patch applied as that may be replaced during the update.

eZuce's software products continuously progress through an Agile based development methodology that keeps feature functionality comprehensive and up-to-date in response to evolving market and customer requirements.

New software releases are made at a rate of two to four releases a year. Releases are numbered in the <yy>.<mm>.<uu> format where <yy> and <mm> designate the year and the month, respectively, in which a release is made generally available. Where applicable, <uu> corresponds to an update release relative to a general release on which fixes are made available.

In order to ensure service continuity and stability, customers may keep their production environments unchanged for up to a 6-month period during which release updates or patches are made available. After a release is more than 6-months old, eZuce customers would have to upgrade to the latest generally available release - inclusive of all fixes to date and any new patches.

Questions

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 soft nofile 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

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.

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:

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.

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.

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