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


September 26, 2019

Summary

eZuce is pleased to announce the GA Release of sipXcom 19.08. 

This will be a fairly light update with only bug fixes for sipXcom.

Highlights

sipXcom Improvements:

  • Bug fixes

Notes

  1. Full Beta Release Notes with installation information are located here: 19.08 Full Beta Release Notes
  2. 19.08 is now released on CentOS 7 only. This will require that administrators install CentOS 7 minimal, then install Uniteme with our single line installer and then restore from a previous version backup.

Who Should Install?

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 IssueKeywords
SIPX-795Copyright year in Admin GUI footer should be dynamicUniteme 19.04 still shows in Admin GUI footer

Copyright (C) 2017 eZuce, Inc.

The year could be set as a variable (server time year or build machine year).
BugAdminGUI
SIPX-805REST bug CDR offsetThere are two types of REST Services that involve CDRs

1. User Rest service, which requires user credentials, that does not have offset param, only limit
example: curl -k -u 200:12345678 https://10.3.0.100/sipxconfig/rest/my/redirect/cdr/200?limit=1

2. Admin rest service:
curl -k -u superadmin:12345678 https://10.3.0.100/sipxconfig/api/cdrs/user/200/history?fromDate=201801000000
or
curl -k -u superadmin:12345678 https://10.3.0.100/sipxconfig/api/cdrs/history?fromDate=201801000000

For section 2, the offset and limit parameters are not effective and fromDate parameter is mandatory: this is a bug in our code. Please open a jira ticket to track this
Support BugCDR
SIPX-806MP3's on 19.04 Centos7 for Voicemail or PromptssipXcom 19.04 (19.04.20190522074125). When a call is transferred to VoiceMail by IVR, instead of the 'beep', the caller is disconnected.

If .mp3 is used as the voicemail format, the call is dropping as soon as the beep to leave a message.
Silence is played for message prompts if an mp3 is used.

Switch the message format back to .wav worked
BugVoicemail
SIPX-807Sendmail queue must be flushed every 15 seconds [Centos 7]Centos 7 uses a different parameter in /etc/sysconfig/sendmail to configure mail queue flushing. It is: SENDMAIL_OPTS

Put SENDMAIL_OPTS=-q15s

instead of QUEUE=p15s which is the Centos 6 corresponding sendmail option for flushing queue
BugVoicemail
SIPX-814Cron doesn't pick up changes unless the service is reloaded

QA has found out that changes in system configuration involving the editing /creation of cron jobs do not reflect in cron operation unless the service or the entire system is restarted on CentOS 7. This includes backups and other such tasks handled by cron.

Changes should be made to restart cron after all configuration changes that involve cron jobs.

BugCron
UC-4823Freeswitch.log not included in CentOS7 snapshotsfreeswitch.log in centos7 moved to /var/log/freeswitch/freeswitch.log rather than /var/log/sipxpbx/freeswitch.log and is missing from snapshots.Support BugSnapshot
UC-4831Regional databases can't be created

Regional databases can't be created from admin GUI. There's no error nor other sign of changes in Mongo log, GUI shows 500 error.

Support BugDatabase
  • No labels