sipXcom 21.04 General Availability
November 16, 2021
Summary
CoreDial is pleased to announce the GA release of sipXcom 21.04.
We've made a number of enhancements to the API service for system management to a number of features including Auto Attendants, Web UI Localization/Language, Call Queues, and Time Zone.
We’ve also added a server column within the Web UI for registration entries. This will allow for more in depth troubleshooting and verification by indicating the server that the endpoint is currently registered to.
Last, but certainly not least, our most exciting enhancement for this release is High Availability Configuration Service. We’ve made the configuration service and the underlying database redundant and highly available. This provides a safeguard for the configuration data by replicating it among the cluster server members. In addition we’ve made it possible to migrate the configuration service to a secondary server essentially making it become the primary and assuming control of the cluster.
We’re continuing to look for ways to improve sipXcom and we’re excited about the opportunities that 2022 will bring.
Highlights
sipXcom Enhancements:
- Manage Auto Attendants via API
- Manage Call Queues via API
- Manage Language settings via API
- Manage Time Zone via API
- Configuration service and database is now highly available and redundant
- Ability to recover primary node on secondary server
- Add server column to registration entries
Notes
- 19.08 and later are 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.
- AudioCodes and other gateways may need to have their configuration changed if faxing is used. See SIPX-811.
- For Let's Encrypt certificates to work properly, the server must have a valid outside DNS name and have port 80 and 443 open to LE's servers.
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