ENSWITCH 4.4 IS IN DEVELOPMENT, AND THIS PAGE HAS NOT YET BEEN COMPLETED.

Most changes in Enswitch 4.4 purely add functionality, but some change or remove functionality. Here is a list of such changes. If any of these adversely affect you, please contact support as soon as possible.

• The Enswitch web interface adds a new HTML meta tag by default to ask search engines not to index it. This can be turned off with a configuration setting.
• Queues never use MySQL transactions. Queues with transactions had been depreciated for several versions.
• Music On Hold classes defined in the /etc/asterisk/musiconhold.conf Asterisk configuration file may need syntax adjustments in its "application" option if it uses the mpg123 player installed from the repositories of recent versions of Rocky Linux or Ubuntu distributions.
• The global configuration variable "Restrict ABANDON queue events to one per call" is now abolished, as only one such event per call is recorded anyway.
• Audit log queries will have the number of results limited by global configuration "Audit log maximum results".
• The global configuration variable "Enforce UTF8 when importing users and features" is now abolished, the UTF8 character set will be enforced when importing users and their features from a text file so that only Latin1 and UTF8 characters will be acceptable.
• The global configuration variable "Callback in advance" is now replaced by an individual setting in each queue.
• There was a code cleanup on the various login parameters in the $me hashref that is returned by json_auth(), so the following policy was applied for those parameters:
  1. The parameters effective_id, effective_username, effective_customer, effective_role refer to the switched-into user.
  2. The parameters login_id, login_username, login_customer, login_role refer to the user that was originally logged in the web interface or is executing a JSON query.
  3. In order to avoid overlap with the above, it is recommended that the parameters id, username, customer, role be used in relation to a user in the people table for eg. as a result of a query to that table.
  Any custom plugins will need to be updated accordingly.
• As usual, some JSON API functions have changed. If using the JSON API, these should be reviewed before upgrading.