Page tree
Skip to end of metadata
Go to start of metadata


Summary

eZuce is pleased to announce the General Availability Release of uniteme 18.08.

Important - Do not directly upgrade to 18.08 from any version before 18.04 (i.e., do not just change the repo file and run yum update).

The two major features in this release are the Admin GUI Menu restructuring and the addition of the flat file system option for voicemail.

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.

The new flat file option for storing voicemail is important for many customers in different ways. Customers who require encryption for data at rest can store their voicemail on a storage subsystem and mount it to the server. Customers who operate many Uniteme instances can share the storage they already have across multiple instances, storing voicemail for each system in separate folders. We’ve also included scripts for moving voicemail between the two different storage options (mongo and flat file).

Highlights

uniteme New Features:

  • Flat File Storage Option for Voicemail

uniteme Improvements:

  • Admin GUI Restructuring

  • Elasticsearch Audit records cleanup more efficient.

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

Notes

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

  2. The regular release of 18.08 has the ability to upgrade from earlier versions using the upgrade script used in 18.04.

  3. Please note that the upgrade will take extra disk space. The MongoDB upgrade essentially makes a copy of the existing database and then re-mounts it. Please be prepared for this.

  4. Please also note that if you have a multi-server cluster vs. a single server there are specific upgrade instructions.

Who Should Install?

This release is recommended for all 4.6 and later installations except for customers who are running Reachme. 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.

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

System Requirements

For a reasonably performing system, we recommend the following configuration.

Minimum hardware requirements

  • Pentium 4 or Xeon processor @ 2.0 GHz Core 64bit or higher
  • Minimum 8 GB of RAM with sufficient swap space
  • 80 GB disk (75 users depending on usage patterns)

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 6 x86_64 with latest updates is required.

Devices

Phones

  • Polycom VVX Devices with firmware 5.5.2 (split) are recommended for new installations
  • Polycom SoundPoint IP Devices should run firmware 4.0.11 (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, Reach Reference Manuals, 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 Mongodbrequirements 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 ISO image

Download uniteme ISO

Download the ISO image corresponding to your hardware and write the image to a DVD.

Install uniteme

  • Boot from the DVD created with the uniteme ISO image.
  • Press Enter at the boot screen below to begin the uniteme installation.
  • Select Manual Configuration under Enable IPv4 support and select OK.
  • Set a static IPv4 address with the corresponding networking information and click OK.
  • In certain situations, a warning of the use of indicated storage devices will be displayed.
  • Select the language to be used during the installation.
  • Select the keyboard layout to be used.
  • Select the timezone to be used.
  • Set a root password.
  • Login to the system as root with the password you provided earlier and continue on to the Configure of uniteme.

Installing from Repository

uniteme can be installed using the following procedure

  • Download and install CentOS 6.x minimal ISO
  • Run the following command:
yum update && reboot
  • Run the following commands to retrieve and run the eZuce uniteme installer:
curl https://download.ezuce.com/openuc-setup > /usr/bin/openuc-setup
chmod +x /usr/bin/openuc-setup
openuc-setup

This utility will guide you through the process of installing uniteme from the eZuce software repository.

Upgrade from previous versions

New Procedure

We will be utilizing an upgrade script to ensure upgrades proceed as intended and so that customers have the appropriate warnings and information before upgrading.

Warning!

Make sure you backup your system (configuration and voicemail at a minimum) prior to installation. You'll be upgrading mongodb to a new version!

Upgrade to 18.08 for Single Server systems for 17.10 and Older

Backup your System

Login to the Admin GUI and click on System -> Backup and at a minimum backup configuration and voicemail.

Do it now... before you go any further.

Download upgrade.sh

Login to the primary server as root.

Execute the following:

wget https://'USERNAME:PASSWORD'@download.ezuce.com/openuc/upgrade.sh
chmod +x upgrade.sh

Run upgrade.sh

Execute the upgrade script and answer 'Yes' to continue:

./upgrade.sh

 

The following will be displayed:

Uniteme 18.08 Upgrade Script
 
IMPORTANT: If this is a multi-server cluster, all databases except the Primary (which must be on the configuration server) should be removed.
IMPORTANT: You should run a system backup and copy your config and voicemail backups to another system. If the upgrade fails, you will need to build a new server and restore from backup.
IMPORTANT: Ensure that you have enough disk space available for a copy of the Mongo databases. (roughly your Config + Voicemail backups).
IMPORTANT: 18.08 does not have Reachme in it, if you use Reachme on this server or in the cluster, do not continue!
 
This script will do the following:
- Back up mongo config and dbs
- Stop mongo instance and remove old mongo files
- Change 17.10 occurrences in /etc/yum.repos.d with 18.04
- Perform yum update and then reboot the machine
 
On sipxconfig service startup following steps are taken (in case there is a backup still on the disk):
- Restore mongo config and dbs, then remove from disk
- Reboot machine
 
For other cluster servers:
- Run same script
- Re-add databases that were removed.
 
Continue? (you must enter Yes or No as shown and press Enter):

Enter 'Yes' and press Enter to continue. The system will reboot a couple of times as part of the process.

Upgrade to 18.08 for Multi-Server Clusters with Multiple Database Servers for 17.10 and Older

Backup your System

Login to the Admin GUI and click on System -> Backup and at a minimum backup configuration and voicemail.

Do it now... before you go any further.

Remove All Secondary Databases from Cluster Nodes

From the Admin UI remove databases from all nodes except for the primary node. Click on System -> Databases do accomplish this.

Proceed as with Single Server for Primary

Proceed as above with the 'Download upgrade.sh' section and then the 'Run upgrade.sh' section.

Secondary Servers in Cluster

After the Primary Server has completed, repeat for each of the Secondary Servers in the cluster until all are completed. 

Add Database Nodes

After the secondary nodes are complete and done with their reboots, log in to the Admin UI and add back the database nodes that were removed.

Send Server Profiles

Login to web interface as superadmin.

Navigate to System -> Servers page. Place checkmark next to server names and click 'Send Profiles'.

SEC Service Upgrade Note

When upgrading uniteme from openUC 4.6 Update 11 or 14.4.3 to 15.06 follow these steps to ensure the SEC service is correctly running:

  • 1. Upgrade from 4.6 Update 11 or 14.4.3 to 15.06.
  • 2. After the upgrade is complete, perform the usual restart.
  • 3. Once possible, connect via CLI and monitor processes using top. Notice that the SEC process is using a lot of CPU memory.
  • 4. Perform another restart OR restart only the Sipxlogwatcher service.

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

Issues Sorted by Issue Number

Jira #JIRA NameRN ContentEnhancement/Fix/Known IssueKeywords
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 phone.

This configuration works as designed on 14.04 and lower systems.

Fixed firewall settings to allow this traffic through by default.
Fixbla
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 checkbox 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 an 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" : "sip:1900@DOMAIN", "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",)

Workaround:

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

Mind that the rule will get repopulated in Mongo when sending profiles to server
FixAuto-Attendant
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:

filename.pcap0
filename.pcap1
filename.pcap2
...

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:
filename0.pcap
filename1.pcap
filename2.pcap
...
Enhancementpcap
SIPX-744sipxlang-pt.jar schema within spring bean xml uses the 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:
https://docs.mongodb.com/manual/tutorial/configure-a-non-voting-replica-set-member/
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-754Elasticsearch using up too much memory due to the number of transactions in Audit LoggingIf a large number of audit records exist, this exception occurs while trying to clean up old system audit records:

2018-06-30T11:22:24.121000Z":313:JAVA:ERR:sipx01.pnq2.redhat.com:pool-10-thread-1:00000000:SystemAuditCleanup:"Error while doing System Audit cleanup: "...

Here's a way to manually delete entries older than a certain time (and couple of useful commands to count or display documents that will be deleted):

- count documents that will be deleted (older than 1530527703609):
curl -XGET 'http://localhost:9200/audit/_count&#39; -d '{"query" : {"bool":{"must":{"range":{"dateTime":{"lte" : "1530527703609"}}}}}}'

- display documents that will be deleted (older than 1530527703609):
curl -XGET 'http://localhost:9200/audit/_search?pretty&#39; -d '{"query" : {"bool":{"must":{"range":{"dateTime":{"lte" : "1530527703609"}}}}}}'

- delete documents (older than 1530527703609):
curl -XDELETE 'http://localhost:9200/audit/_query&#39; -d '{"query" : {"bool":{"must":{"range":{"dateTime":{"lte" : "1530527703609"}}}}}}'

to obtain timestamp from one year ago (that is for replacing 1530527703609 value) use the command:

date --date="-1 year" +%s
FixAudit
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
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.

https://freeswitch.org/confluence/display/FREESWITCH/mod_local_stream#mod_local_stream-TimeoutExample
EnhancementMoH
UC-4722UC-4744 Move voicemail between Flat File and Mongo GridFSBuild a method to move voicemail files from Mongo GridFS to Flat File storage. Have an option to remove files from GridFS as they are moved.

Build another method to move voicemail files from Flat File to Mongo GridFS. Have an option to remove files from flat file storage as they are moved.
EnhancementVoicemail
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.
FixUniteWeb
UC-4725Greetings are removed by the voicemail aging processUser recorded greetings were not excluded properly from the script that examines the age of files in the user's voicemail storage. As such, they were being 'aged out'.FixVoicemail
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
UC-4743openuc-ivr-gridfs does not delete greetingsWhen using openuc-ivr-gridfs utility to delete a mailbox it will remove all entries in the mongo database, but fails to cleanup greetings stored on the filesystem.FixVoicemail
UC-4744Flat File HA VoicemailUmbrella Task for new Flat File HA Voicemail.

We'll implement a flat file voicemail storage method so that administrators can utilize a distributed file system to store voicemail. Management of the DFS is up to the administrator.
EnhancementVoicemail
UC-4745UC-4744 Evaluate Voicemails saved in Files for the same functionality as in Uniteme's MongoDB based VoicemailEnsure that voicemail aging/deletion is working the same when voicemails are saved in files as in mongoEnhancementVoicemail
UC-4746UC-4744 Ensure that we can easily change the location of VM StorageAn administrator needs to change the location of voicemail to a different mount point.

Make this configurable from Admin GUI in case an administrator wants to use their own storage system.
EnhancementVoicemail
UC-4747UC-4744 Add Uniteme VM storage in a Flat File system optionImplement an option to store voicemail in a flat file system to Uniteme. The option to still store in Mongodb is also there and still the default.EnhancementVoicemail
UC-4748Network Packet Capture Service Admin RoleNetwork Packet Capture Service menu page was not properly controlled by Admin Roles.Fixadmin-roles pcap


Issues Sorted by Keyword

Jira #JIRA NameRN ContentEnhancement/Fix/Known IssueKeywords
UC-4748Network Packet Capture Service Admin RoleNetwork Packet Capture Service menu page was not properly controlled by Admin Roles.Fixadmin-roles pcap
SIPX-749Menu RestructureReorganization of Uniteme / sipXcom menus is needed to simplify the interface.

See attachment for the first swing at this.
EnhancementAdminPortal
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:
https://docs.mongodb.com/manual/tutorial/configure-a-non-voting-replica-set-member/
FixAdminPortal databases
SIPX-404P-Preferred-Identity of Proxy - GUI workCreate a checkbox in proxy setup to pass p-asserted-identity (default should be to not pass (as it operates now): GUI change.EnhancementAdminPortal sipxproxy
UC-4749Elasticsearch using up too much memory due to the number of transactions in Audit LoggingIf a large number of audit records exist, this exception occurs while trying to clean up old system audit records:

2018-06-30T11:22:24.121000Z":313:JAVA:ERR:sipx01.pnq2.redhat.com:pool-10-thread-1:00000000:SystemAuditCleanup:"Error while doing System Audit cleanup: "...

Here's a way to manually delete entries older than a certain time (and couple of useful commands to count or display documents that will be deleted):

- count documents that will be deleted (older than 1530527703609):
curl -XGET 'http://localhost:9200/audit/_count&#39; -d '{"query" : {"bool":{"must":{"range":{"dateTime":{"lte" : "1530527703609"}}}}}}'

- display documents that will be deleted (older than 1530527703609):
curl -XGET 'http://localhost:9200/audit/_search?pretty&#39; -d '{"query" : {"bool":{"must":{"range":{"dateTime":{"lte" : "1530527703609"}}}}}}'

- delete documents (older than 1530527703609):
curl -XDELETE 'http://localhost:9200/audit/_query&#39; -d '{"query" : {"bool":{"must":{"range":{"dateTime":{"lte" : "1530527703609"}}}}}}'

to obtain timestamp from one year ago (that is for replacing 1530527703609 value) use the command:

date --date="-1 year" +%s
FixAudit
SIPX-479Live Attendant not updated in Mongo properlyWhen an 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" : "sip:1900@DOMAIN", "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",)

Workaround:

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

Mind that the rule will get repopulated in Mongo when sending profiles to server
FixAuto-Attendant
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 phone.

This configuration works as designed on 14.04 and lower systems.

Fixed firewall settings to allow this traffic through by default.
Fixbla
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
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-744sipxlang-pt.jar schema within spring bean xml uses the wrong classpathIf the Portuguese language is installed on the server, the system does not work without internet.Fixlanguage
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
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 system to crash.

Administrators would like to add a timeout option for MoH channels.

https://freeswitch.org/confluence/display/FREESWITCH/mod_local_stream#mod_local_stream-TimeoutExample
EnhancementMoH
SIPX-741Change file name extension for Network Packet Capture ServiceNetwork Packet Capture Service generates file names as follows:

filename.pcap0
filename.pcap1
filename.pcap2
...

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:
filename0.pcap
filename1.pcap
filename2.pcap
...
Enhancementpcap
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
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.
FixUniteWeb
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
UC-4722UC-4744 Move voicemail between Flat File and Mongo GridFSBuild a method to move voicemail files from Mongo GridFS to Flat File storage. Have an option to remove files from GridFS as they are moved.

Build another method to move voicemail files from Flat File to Mongo GridFS. Have an option to remove files from flat file storage as they are moved.
EnhancementVoicemail
UC-4725Greetings are removed by the voicemail aging processUser recorded greetings were not excluded properly from the script that examines the age of files in the user's voicemail storage. As such, they were being 'aged out'.FixVoicemail
UC-4743openuc-ivr-gridfs does not delete greetingsWhen using openuc-ivr-gridfs utility to delete a mailbox it will remove all entries in the mongo database, but fails to cleanup greetings stored on the filesystem.FixVoicemail
UC-4744Flat File HA VoicemailUmbrella Task for new Flat File HA Voicemail.

We'll implement a flat file voicemail storage method so that administrators can utilize a distributed file system to store voicemail. Management of the DFS is up to the administrator.
EnhancementVoicemail
UC-4745UC-4744 Evaluate Voicemails saved in Files for the same functionality as in Uniteme's MongoDB based VoicemailEnsure that voicemail aging/deletion is working the same when voicemails are saved in files as in mongoEnhancementVoicemail
UC-4746UC-4744 Ensure that we can easily change the location of VM StorageAn administrator needs to change the location of voicemail to a different mount point.

Make this configurable from Admin GUI in case an administrator wants to use their own storage system.
EnhancementVoicemail
UC-4747UC-4744 Add Uniteme VM storage in a Flat File system optionImplement an option to store voicemail in a flat file system to Uniteme. The option to still store in Mongodb is also there and still the default.EnhancementVoicemail

 

 


  • No labels