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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


August 10, 2018


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

Important - Do not directly upgrade to 18.08 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.

The two major features in this release are the Admin GUI Menu restructuring and the addition of the ability to age voicemail out of the system by user group.

The Admin GUI’s menus have been updated to be sorted alphabetically and with some sub-menus. The menus have always been built dynamically based on which services were enabled. This was what lead to the system menu being as long as it was. Well, we decided to address this issue and bring some structure to the menus. Hopefully, new users of the system will find things more easily and hopefully, our long-term admins don’t want to inflict pain on us.


sipXcom New Features:

  • Automatic Voicemail purging by User Group

sipXcom Improvements:

  • Admin GUI Restructuring

  • Set file names for Network Packet Capture Service so they end in .pcap


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

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


Please post to the sipXcom-users google group if you have questions.!forum/sipxcom-users

Specific Issues Addressed

Jira #JIRA NameRN ContentEnhancement/Fix/Known IssueKey words
SIPX-25Cannot get BLA to work in release 14.10When an incoming internal or external call is placed to the main line on a 14.10 system and one phone answers, there is no solid red light (BLA) that appears on any other other phone.

This configuration works as designed on 14.04 and lower systems.

Fixed firewall settings to allow this traffic through by default.
SIPX-403P-Asserted-Identity of Proxy - SIP SideProxy must pass p-asserted-identity (default should be to not pass (as it operates now)) - proxy code changeEnhancementsipxproxy
SIPX-404P-Preferred-Identity of Proxy - gui workCreate a check box in proxy setup to pass p-asserted-identity (default should be to not pass (as it operates now): GUI change.EnhancementAdminPortal sipxproxy
SIPX-479Live Attendant not updated in Mongo properlyWhen a AA is defined as live AA a new entry is added in MongoDB so registrar will look up routing information from there. When an existing live AA is disabled, MongoDB entry is removed and routing is done according to mappingrules.xml.

In this case customer previously had 1900 configured as live AA, then disabled it. However it seems that in this version the mongo entry does not get cleaned up when doing this action and leaves inconsistent entries in mongo:
{ "_id" : "AttendantRule9", "ident" : "1900@DOMAIN", "uid" : false, "cnt" : "sip:1900@DOMAIN", "locations" : [], "vld" : true, "ent" : "attendantrule", "als" : [ { "id" : "1900", "cnt" : "<sip:1600@DOMAIN;sipx-noroute=Voicemail?expires=50>;q=0.933;sipx-ValidTime=\"88e:a8c:e2e:102c:13ce:15cc:196e:1b6c:1f0e:210c\"", "rln" : "userforward" }, { "id" : "9673", "cnt" : "", "rln" : "alias" } ] }

(other ways for this bug to manifest is generating null contacts as in: "cnt" : "<sip:null@DOMAIN;sipx-noroute=Voicemail;sipx-userforward=false?expires=0>;q=0.933",)


use imdb
db.entity.remove({"_id" : "AttendantRule9"})

Mind that the rule will get repopulated in Mongo when sending profiles to server
SIPX-665Duplicate Syslog Messages in /var/sipxpbx/phonelog/*The rsyslog configuration is duplicating entries in /var/log/sipxpbx/phonelog/* logs. After examining the rsyslog config in /etc/rsyslog.conf, we discovered that this is because the phonelog.conf file is being included twice; once towards the top of the file when the entire rsyslog.d directory is included (line 31), and then again at the end (line 81). We modified the CFEngine scripts to prevent phonelog.conf from being included twice as a workaround.Fixlogging
SIPX-741Change file name extension for Network Packet Capture ServiceNetwork Packet Capture Service generates file names as follows:


This requires that an administrator rename each file to .pcap after download to open properly with Wireshark.

An administrator would like to change the file names to:
SIPX-744sipxlang-pt.jar schema within spring bean xml uses wrong classpathIf the Portuguese language is installed on the server, the system does not work without internet.Fixlanguage
SIPX-746Help text should be added to indicate that voting can be disabled only when priority is 0In the Uniteme Admin GUI -> System -> Database -> Global database a help text should be added on the right after the last paragraph:

"Voting - If you do not want a particular database to participate in the voting process, you can disable this feature for each database. A cluster is limited to 7 voting servers and 12 database servers in total."

Which should be completed with the phrase: "Voting can be disabled only if priority is set to 0 first."

Otherwise, the "disable voting" command does nothing, and the user can find what the error is only by looking manually at Mongo logs. The error in mongo.log reads:

[js] replSetReconfig got BadValue: priority must be 0 when non-voting (votes:0) while validating

More info on this:
FixAdminPortal databases
SIPX-749Menu RestructureReorganization of Uniteme / sipXcom menus is needed to simplify the interface.EnhancementAdminPortal
SIPX-750User/Group based Voicemail cleanupExtend voicemail_clean script to cleanup voicemails using days, path as parameters. Use this to implement User/Group based Voicemail cleanup in open-source sipXcomEnhancementVoicemail
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:
UC-4308Add MoH timeoutThere is a possibility that FS can miss a BYE or CANCEL and MoH will be played indefinitely and will eventually cause the system to crash.

Administrators would like to add a timeout option for MoH channels.
UC-4724The user is unable to save prerecorded greeting unless menu is toggledUpon testing, we found that the new Uniteme interface has a bug in the User portal -> Settings -> User settings.

The drop down menu for the Voicemail->Announcement selection does not have the "Name" field. Furthermore, the SAVE button at the bottom of the page is inactive until this drop down menu is toggled. Looks like a webpage glitch which prevents the upload of prerecorded greetings if the drop down menu is not toggled in any way.
UC-4729g729 in 'selected' codecs by defaultWith g.729 added in the system by default, G.729 is in the 'selected' codecs. It should be set as 'available' by default.Fixg729
  • No labels