Child pages
  • sipXcom 19.04

Versions Compared

Key

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

April 16May 10, 2019

Summary

eZuce is pleased to announce the Beta Release of the General Availability of sipXcom 19.04.

As a beta release, some of these notes may be revised before the actual release.

Important - For Beta Testers - Do not directly upgrade to 19.04 from any version before 18.04. The 18.04 upgrade must be completed first. Please read the release notes for 18.04 if you are not on 18.04 yet.

There again will be 2 releases for 19.04. A CentOS 7 release (19.04.centos7) will follow shortly. While it’s a There are again two releases for sipXcom 19.04, one for CentOS 6 and one for CentOS 7. The documentation around Installations and Downloads is being updated now with CentOS 7 as the recommended OS moving forward. We'll also update the video to cover CentOS 7 Minimal installation. While this is a relatively small update, there are a few interesting things to point out.

When a user is deleted from the system, the configuration services will now go through all phones and remove that user from the phones and re-send phone profiles. If that was the only user on the phone, the phone will go back to the auto-provision ID. What we were finding is that administrators were deleting users but not re-sending phone profiles which would then create . This would result in traffic floods of SIP traffic with bad subscribes to MWI and such invalid registrations to the server.

The new Polycom VVX ‘50’ series phones is are now supported for configuration as well as auto provision! Firmware 3.8-provisioning. Firmware versions 5.9.0 and later are supported.

Also, mongoDB has been updated to 3.6.911. This has had a positive effect in recovery from a node outage. The new mongodb seems much more resilient.

This Please note that this will be the last release for CentOS 6. As of version 19.08 we will only be releasing sipXcom for CentOS 7! To go from a CentOS 6 based system to a CentOS 7 based system will require a backup and restore to a fresh CentOS 7 installation. As such a parallel install will be recommended.

We’ve also decided to put the container (Docker) work on hold for now. There were complexities around networking and implementation that we didn’t feel warranted the effort involved to work past them. Additionally, there wasn't significant customer demand to warrant the effort at this point. We’re pushing ahead with some newer features instead.

Highlights

sipXcom New Features:

  • Support for Polycom VVX 150, 250, 350 and 450
  • Alarm for Certificate Expiration
  • Make mongoDB cache size configurable
  • Remove user from phones automatically after user deleted from system
  • Automatically generate a certificate from Let’s Encrypt.

sipXcom Improvements:

  • Sort alarms alphabetically
  • Upgrade mongodb to 3.6.
  • 9
  • 11
  • Add http provisioning option to DHCP configuration

Notes

  1. Full Beta Release Notes with installation information are located here:  1819.12 04 Full Beta Release Notes
  2. The regular release of 19.04 will have the ability to upgrade from earlier versions using the upgrade script used in 18.04. For the purposes of this beta release, please only do upgrades from 18.04 if you test systems are on a version earlier than 18.04, upgrade to 18.04 first.

Who Should Install?

This is a beta release and not recommended for production use.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 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.

production installations.

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

...

Questions

Please post to the sipXcom-users google group if you have questions.

https://groups.google.com/forum/#!forum/sipxcom-users

Issues Sorted by Issue Number

...