RELEASE NOTES
Thirdlane Unified Communications Platform 15.1.4
- Improved DIDs management with various enhancements
- Added Inbound Call Flow visualization diagram
- Added Updates section to display installed packages and available updates
- Added ability to perform system updates from the web GUI
- Added password policy enforcement and improved password generation
- Added Open API integration for Yealink Management Cloud Service v2
- Added global settings to control the number of allowed video streams
- Added per-user settings to limit video streams in user-initiated conferences
- Enhanced configuration options for messaging gateways
- Added BLF hints for special mailboxes
- Fixed issue with tenant-level Thirdlane Connect settings not updating correctly when global values change
- Fixed menu items and permissions for office admin-level users
- Fixed a bug where officemode (day/night) in tenant record, set via dialplan, could be overwritten by cached values
- Fixed stored procedure handling updated_by value in Change Log for deletions
- Fixed IVR API behavior
- Added span (line key count) support for Polycom phone configuration
- Added support for buttons defined as N/A when the corresponding templates are available
- Various enhancements to managed device handling
- Fixed decoding of Unicode strings in JSON
- Fixed UTF-8 display issues for managed devices
- Added IPv6 support to NGINX configuration
- Fixed handling of special characters (including +) in URL encoding
Thirdlane Connect 15.1.4
- Fixed issues in the white-label build process to improve reliability and customization
- Resolved an issue with processing a second incoming call while another call is active
- Fixed a bug where the outgoing call screen was not displaying correctly
- Corrected internal application sounds to improve notification and system audio feedback
- Fixed an issue where the first SMS in a new conversation was not processed correctly
- Fixed ringback and early media handling
- Fixed unread voicemail counter badge display
- Fixed media handling in 3-way calling
- Fixed authentication and certificates management in custom iOS/Android builds
- Fixed an issue where user's do not disturb status was lost after the first call was received and rejected
INSTALLATION PROCEDURE
This version of the Thirdlane platform is supposed to be installed on top of the base AlmaLinux OS version 8.
You should start with minimal AlmaLinux OS version 8 ISO which you can get at https://repo.almalinux.org/almalinux/8/isos/x86_64/AlmaLinux-8-latest-x86_64-minimal.iso
For any cloud installation you should use the AlmaLinux OS version 8 cloud provider’s template.
The installation procedure is simple:
- Install minimal AlmaLinux OS version 8 from vanilla ISO or create AlmaLinux OS version 8 cloud server
- Configure network and check that your server has access to the Internet
- Use SSH to connect to the server and run one of the Thirdlane installation scripts, depending on the type of installation (single or multi-tenant)
- Once the script finishes, login to the GUI at http://xxx.xxx.xxx.xxx or http://domain.tld (where xxx.xxx.xxx.xxx is your server address, and domain.tld is your domain) and follow the Thirdlane Configuration Manager’s Initial Configuration Wizard
Currently, there are 2 scripts for different installations:
- getpbx-ste - Thirdlane Business Phone System (Single Tenant)
curl -o getpbx -s http://lib.thirdlane.com/download/getpbx-el8/getpbx-ste && time sudo bash getpbx
- getpbx-mte - Thirdlane Multi Tenant PBX
curl -o getpbx -s http://lib.thirdlane.com/download/getpbx-el8/getpbx-mte && time sudo bash getpbx
Both scripts are adopted to cloud installations which usually don’t have a root password - they use SSH keys for ssh access. When getpbx-ste or getpbx-mte script determines that your system root user doesn't have a password, it creates temporary credentials (superadmin / superadmin ) to login to the newly created server, and at the end of Thirdlane Configuration Manager’s Initial Configuration Wizard you will be able to create admin credentials (superadmin user will be deleted). Installation scripts also try to simplify domain, HTTPS certificate, and network configuration - when:
- Hostname setting of the server is a valid domain - eg. abc.pbxmanager.com
- The domain is properly configured - DNS of abc.pbxmanager.com has A-record with proper ip of the server
If this criteria is met, Thirdlane Configuration Manager setup wizard will use the simplified scenario - steps with domain and interface configuration will be done automatically - including creation of LetsEncrypt free HTTPS certificate. As always, Thirdlane Connect for Windows, Mac, and Linux desktops can be downloaded using your browser based Thirdlane Connect by going to Settings > Downloads. New Android version of Thirdlane Connect is available on Google Play. New iPhone version of Thirdlane Connect is available on App Store.
Thank you for using Thirdlane!