Child pages
  • sipXcom 18.12
Skip to end of metadata
Go to start of metadata

December 6, 2018

Summary

eZuce is pleased to announce the Beta Release of sipXcom 18.12. As a beta release, some of these notes may be revised before the actual release.

Important - For Beta Testers - Do not directly upgrade to 18.12 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.

This is a relatively small update as we’re continuing to work on CentOS 7 compatibility. We’ll have a separate 18.12.CentOS7 release coming out shortly after 18.12 becomes available.

The one major new feature in this release is the added ability of users to be able to set their language preference in the New User Portal.

Highlights

sipXcom New Features:

  • Allow user to choose language in UniteWeb

sipXcom Improvements:

  • 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!)

Notes

  1. Full Beta Release Notes with installation information are located here: 18.12 Full Beta Release Notes

  2. The regular release of 18.12 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.

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.

Questions

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

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

 

Specific Issues Addressed


Jira #JIRA NameRN ContentEnhancement/Fix/Known IssueKey words
SIPX-759Jitsi preferred transport velocity fileThere 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
FixJitsi
SIPX-774Add 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).
EnhancementYealink
SIPX-775Upgrade fail2ban to v0.9.6The 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
EnhancementFail2ban
SIPX-776Change block size in TFTP service to 1300Several provisioning problems were tracked to TFTP using 4096 byte UDP blocks which get fragmented and lost on the way in some network environments.FixTFTP
SIPX-777sipxsecurity and firewall logs not appended after rotateCustomer 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.FixLogs
SIPX-778Grace period is not being read properly by registrar serviceThe 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"

FixRegistrar
UC-4761sipx-dbutil -r not working properly on 18.04 update 1sipx-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)
in
client = pymongo.Connection('localhost', 27017, slaveOk=True)

To allow issuing on SIPXCONFIG master and Mongo PRIMARY or SECONDARY.

https://ezuce.zendesk.com/agent/tickets/8020
FixTools
UC-4770Allow to listen moh and greeting file from user settingsShow 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.EnhancementUniteWeb
UC-4774Conferences are automatically saved in InboxConferences should be saved in conference folderFixConference
UW-408Add language supportAdd possibility to change language in user portal.EnhancementUniteWeb
  • No labels