Latest update
Release Notes
Release 14.2.5450 adds a lot new features, mainly related to integration with third-parties systems
New features
- [PS-1527] - Secure Trunk with Avaya Communication Manager
- [PS-1756] - Support failover on multiple trunks
- [PS-1624] - Single Sign On support for SAML 2.0
- [PS-1609] - Detect ip address and rtp port change during a secure call
- [PS-1694] - PIN protection for clients can be fully configured and managed with provisioning profile
- [PS-1750] - Automatic scheduled daily backup
- [PS-1466] - Install/activation messages can be sent via email in addition to SMS
Improvements
- [PS-1437] - Removes "login" link from error page shown on disabled interface
- [PS-1544] - Improved responsiveness when calling users under bad network
- [PS-1634] - Added logging configuration page
- [PS-1669] - Upgraded OpenSSL 1.0.1
- [PS-1674] - User can have now three states: ONLINE, OFFLINE, Pending activation
- [PS-1802] - Added favicon.ico
Fixed Bugs
- [PS-1621] - During a PGSM call Adding another device, then trying to transfer, transfer acts as if adding a participant
- [PS-1636] - When a user change his own password it is not tracked in security events
- [PS-1647] - Export via SSH of TLS keypair is not tracked in security events
- [PS-1666] - Deleting a backup from "Available backups" is not tracked in security events
- [PS-1676] - If certificate update fails, original certificate is deleted
- [PS-1686] - ArcSight dhost and shost are not a FQDN
- [PS-1688] - "Confirm New Password" field is not checked if blank when expired password.
- [PS-1690] - PrivateServer.log file is created under directory /usr/share/tomcat instead of /var/log/tomcat6
- [PS-1748] - CA certificate wrongly formatted are accepted and inhibits tomcat restart
- [PS-1763] - Changing "Max calls" parameter does not prompt for asterisk restart
- [PS-1767] - Creating or Deleting a SIP trunk does not prompt for asterisk restart
- [PS-1774] - PEM file used by services are not kept in sync with DB after update
- [PS-1804] - ntp server cannot be updated
Updates impact
Here are the impacts upon the update process:
from earlier versions:
server will be rebooted