iSymphony 3.4.2 ChangeLog

Version 6.1 by ryanp on 2021/09/09 18:01
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

The following is a complete list of changes made between iSymphony 3.4.1 and iSymphony 3.4.2.

Failed to execute the [error] macro. Cause: [The required content is missing.]. Click on this message for details.

Resolved Bugs

  • Resolved an issue where asterisk 13 or later would be detected as version 1.8.

  • Resolved an issue where XMPP would attempt to repeatedly connect on error, rather then failing.

  • Resolved an issue where config-vars.sh could be overwritten with the default on rpm upgrade.
  • Resolved an issue where logging out could result in a red spinner requiring a refresh of the page.
  • Resolved an issue causing excessive AsteriskChannelManager failed to locate channel errors in the logs.
  • Resolved an issue where an extension could be assigned to multiple users resulting in users losing their extensions.
  • Resolved an issue where a NPE would be thrown is a contact widget with modified columns exists on a non-selected dashboard on login.
  • Resolved an issue where a server with SSL would receive an error when trying to download the desktop client.

Improvements

  • Updated the User configuration screen to only allow one extension per user. This was previously required but not enforced, resulting in extensions being "stolen" if assigned to multiple users at once.
  • Modified the language module to support UTF encoding on message.properties files.
  • Coupled the desktop module with the standard distribution to streamline installation steps. Support for Desktop Client 1.x has been dropped, v2.x or later will be required.

Desktop Client & Desktop Module

 

  • Major performance improvements to desktop client session management
  • Improved Welcome screen
    • Secure connections are now supported (wss/https support)
      • Added icon to indicate if connection is secure
      • Added icon to inform user if certificate is from a trusted authority
      • Added screen to whitelist untrusted certificates on first connection
    • Connection logic streamlined to determine if valid hostname / port was entered before enabling start.
  • The core server unique name can now be entered after connection.
  • Added additional key listeners to improve navigation.
  • Improved dynamic loading of new desktop client installer packages
    • Files can now be directly written into installers directory
    • Resolved a bug that caused an infinite loop while loading new package (requiring a restart of the server)
  • Improved dependencies to be self contained in the module.
  • Improved the way the application saves the configuration.
  • Improved handling of disconnections, client should now attempt to reconnect for a period of time before returning to the welcome screen.
  • Improved downloading of updates, users will now be presented with a download screen showing the download progress. After the download completes users will be able to start the installation.
  • Changed desktop menu from falling back to the legacy installers on error to instead prompt user with an error dialog notifying them that something has been misconfigured.
  • Resolved the following bugs
    • Resolved an issue where the welcome screen would close if the enter hotkey was used instead of clicking the button.
    • Resolved an issue where the linux extension was incorrect in the installer.properties file.
    • Resolved an issue where the NSIS silent install could not configure the directory.
    • Resolved an issue where the application would throw errors and not start if the configuration was corrupted. An option is now provided to clear a corrupted configuration for the user and return to the welcome screen.
    • Resolved an issue where multi tenant systems would always use default core server, resulting in incorrect server configuration being setup.
    • Resolved an issue where multi tenant systems without default core server would not start.
    • Resolved an issue where the websocket connection could die after a period of inactivity. The websocket will now ping the server to stay alive.
    • Resolved an issue where the application could close before the configuration was updated.
   

Search

Navigation

iSymphony