March 6, 2018
eZuce is pleased to announce the General Availability of sipXcom 18.12.centos7. This release includes all of the same new features, improvements and fixes from 18.12 but now allows users to operate on CentOS 7.
The developers and QA staff have been incredibly busy as we’ve had to touch every service of the system and get them to compile and start (thanks team!). All services startup has moved to systemctl for service startup so there was lots of scripting work to be done. Additionally we’ve moved to pre-built freeswitch packages (1.6.20~64bit) instead of building our own.
With all CentOS 7 builds we’re moving away from building ISO’s. Users will need to use the CentOS 7 64 Bit minimal ISO and then perform an RPM install. The ISO creation process is a drain on resources and as we move towards a container based deployment would not be used.
We’re almost done with coding for the next release (19.04). This release will include support for the new Polycom x50 VVX phones. We’ll also still have both CentOS 6 and 7 releases but this will be the last release done for CentOS 6. Looking forward to version 19.08, we will release for CentOS 7 only and with no ISO’s.
sipXcom New Features:
sipXcom on CentOS 7
Allow user to choose language in UniteWeb
Move to systemctl for service control
Upgrade Freeswitch to 1.6.20
In UniteWeb allow users to listed to MoH and Greeting files in GUI
Upgraded fail2ban to 0.9.6
Added support for newer Yealink phones (thanks IANT!)
- With the upgrade to CentOS 7, the user must install a fresh install of CentOS 7-64 bit and then use the RPM Installation method.
During configuration you will see some errors being echoed to the screen. There's some issue with CFEngine that the CFE team hasn't resolved yet. The errors are benign. You'll see something like the following:
Who Should Install?
This release is recommended for users who need to run sipXcom on CentOS 7. If you are running a CentOS 6 based release in production, it’s recommended that you test the 18.12.centos7 release on CentOS 7 in your environment thoroughly before upgrading. This is the initial release on CentOS 7 and while we’ve done our best to regression test and test all aspects of the system, issues may arise in different environments and scenarios that are not covered in QA tests. Please post to the sipXcom User Forum if you need assistance.
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.
Download and Install CentOS 7 minimal - https://www.centos.org/download/
Perform an RPM based installation of sipXcom - Installing on Fedora and CentOS
Upgrade from previous versions
To upgrade to this version of uniteme you will need to backup your current installation, install a new CentOS 7 server, install uniteme from RPM and then restore the previous backup. It's safest to do this with a new physical or virtual server so as to have a means to get back to your old installation should you have trouble.
Backup your system - Backup
Download and Install CentOS 7 minimal (or RHEL 7) - https://www.centos.org/download/
Follow above instructions for "Installing from Repository" or refer to the following wiki page - RPM Installation
Restore your system - Restore
If you have questions about updating you can email email@example.com.
Specific Issues Addressed
|Jira #||JIRA Name||RN Content||Enhancement/Fix/Known Issue||Key words|
|SIPX-751||Adapt sipx services / utilities for CentOS 7||Enhancement|
|SIPX-752||Adapt build for CentOS 7||Enhancement|
|SIPX-759||Jitsi preferred transport velocity file||There is an error in the Jitsi velocity file with the Preferred_Transport parameter.|
The correct parameter name in velocity file is:
PREFFERED_TRANSPORT -> PREFERRED_TRANSPORT
|SIPX-779||Remove Freeswitch from submodules||Remove Freeswitch from submodules to not build anymore as we are using already built packages now.||Enhancement||Freeswitch|
|SIPX-774||Add provisioning support for new Yealink T46S T48S ...||Add support for newer Yealink S-Series.|
Old phones are not available anymore (chips will not be produced anymore).
|SIPX-775||Upgrade fail2ban to v0.9.6||The system is currently using an older version of fail2ban (0.8.1) which is known to be buggy and throws iptables errors in the log, such as these:|
2018-11-07 14:54:56,664 fail2ban.actions.action: ERROR iptables -D INPUT -p all -j security-block
iptables -F security-block
iptables -X security-block returned 100
|SIPX-776||Change block size in TFTP service to 1300||Several provisioning problems were tracked to TFTP using 4096 byte UDP blocks which get fragmented and lost on the way in some network environments.||Fix||TFTP|
|SIPX-777||sipxsecurity and firewall logs not appended after rotate||Customer reported that if they put in a filter to watch IP tables for bans, but their sipxsecurity logs show no activity day after day since the last system restart.||Fix||Logs|
|SIPX-778||Grace period is not being read properly by registrar service||The grace period in registrar options does not work as expected. Upon investigation, it became clear that the option is being written in registrar config but not being used. Registrar startup shows value being 0 in 18.04 and later regardless of the setting (SIP_REGISTRAR_EXPIRE_GRACE_PERIOD in /etc/sipxpbx/registrar-config):|
"2018-10-29T14:52:59.016784Z":13:SIP:INFO:18081.iuliu.test::7f57c70c9800:sipxregistry:"RegDB::ensureIndexes existing client: no, expireGracePeriod: 0, expirationTimeIndexTTL: 0"
|SIPX-785||sipxbridge fails to start at system||sipXbridge fails to start at boot time. Upon manual startup, the service stays up. Also, backport this to 18.12 for CentOS 6.||Fix||sipXbridge|
|UC-4761||sipx-dbutil -r not working properly on 18.04 update 1||sipx-dbutil -r is not working on 18.04 update 1, it only returns registrations on the primary.|
Testing indicated that the issue only occurs on servers which are not both Mongo PRIMARY and SIPXCONFIG master. Engineering recommended that line 609 in /bin/sipx-dbutil should be changed from
client = pymongo.Connection('localhost', 27017)
client = pymongo.Connection('localhost', 27017, slaveOk=True)
To allow issuing on SIPXCONFIG master and Mongo PRIMARY or SECONDARY.
|UC-4770||Allow to listen moh and greeting file from user settings||Show audio controls bellow the listen and delete button to be able to pause, change volume, download when listening to the greeting or moh file in user settings instead of opening it in new tab.||Enhancement||UniteWeb|
|UC-4774||Conferences are automatically saved in Inbox||Conferences should be saved in conference folder||Fix||Conference|
|UW-408||Add language support||Add possibility to change language in user portal.||Enhancement||UniteWeb|