ISL Tester 4.4.1904.3 for Windows, Linux and Mac (2019-01-22)

 

General Information

On 22nd of January the following was released: 

  • ISL Tester 4.4.1904.3 for Windows (release_date=2019-01-21, build=951e1430f1897a1856c80eb8d35880d002363611, platform=win32, os_version=0x06010000-0x7fffffff)
  • ISL Tester 4.4.1904.3 for Mac (release_date=2019-01-21, build=951e1430f1897a1856c80eb8d35880d002363611, platform=mac, os_version=0x0a0800-0x0affff)
  • ISL Tester 4.4.1904.3 for Linux 64bit (release_date=2019-01-21, build=951e1430f1897a1856c80eb8d35880d002363611, platform=linux64)

Update availability

All updates have release date set to 2019-01-21. Your ESS will need to be  same or higher to be able to update your server. This release is  available to all countries except Japan.

Upgrading to new version

Hosted service users please check Upgrading Hosted Service.

Server license users please check Upgrading Server License.

Improvements

ISL Tester - Desktop - Upgrade mbedTLS from 2.2.1 to 2.7.9 (SECURITY) [ISLTESTER-57] More

Description

Internal library mbedTLS library was updated to version 2.7.9 due to security vulnerabilities.

ISL Tester - Desktop - Added identifier to ATv1 connections in log files (FEATURE) [ISLTESTER-47] More

Description

ISL Tester log now includes identifier for connections made to ISL Conference Proxy.

ISL Tester - libpng warning shown at start (DEFECT) [ISLTESTER-41] More

Description

In previous versions, there was libpng warning in log on startup. This was now redesigned, so that libpng warning should not occur.

The defect was fixed.

ISL Tester - Desktop - Add host header to CONNECT (DEFECT) [ISLTESTER-58] More

Description

Fixed an issue where AutoTransport transports did not include HTTP "Host" header. AutoTransport functionality was redesigned, transports now always include the HTTP "Host" header.

The defect was fixed.

ISL Tester - Desktop - Fix crash on connect timeout (DEFECT) [ISLTESTER-59] More

Description

Fixed an issue where ISL Light could crash when using simple network on windows and when connect_timeout was set to 0. The same crash occurred when the client established the connection at the same time the timeout occurred.

The defect was fixed.

Was this article helpful?