Most changes in Enswitch 4.1 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.

• Asterisk 11 is no longer supported.
• Customers' three digit credit card verification numbers are no longer stored in the database, and are not sent to credit card processing gateways when customers are charged. If you use a credit card processing service, please ensure that it accepts charges without verification numbers.
• Backups of the Enswitch database are no longer sent by email.
• For improved security, the defaults for passwords have been strengthened:
  • Users' passwords are encrypted. This cannot be changed.
  • Users' and telephone lines' passwords must be at least seven characters. This can be changed in global configuration settings.
  • Users and telephone lines are locked out after six incorrect passwords. This can be changed in global configuration settings.
• Busy lamps using enswitch_blfd has been removed and enswitch_messaged will be used instead.
• Provisioning returns an HTTP 404 error if the MAC address is not found.
• The Enswitch Perl libraries have been refactored. Any custom Perl code using them must be updated.
• Voicemail always selects INBOX when a user logs in their mailbox, irrespective of the number of messages in other folders.
• Customer pseudo-user logins are not allowed, unless the "User pseudo-logins are allowed" configuration setting is changed.
• The behavior of the sql() subroutine in lib/Database.pm is to NOT die() when there is an SQL error. This will allow the execution of the script calling sql() or any other database-altering subroutine from lib/Database.pm to continue execution. To revert to the previous behavior where the script would die() in case of an SQL error, the global configuration variable "Die on SQL errors" has been introduced.
• As usual, some JSON API functions have changed. If using the JSON API, these should be reviewed before upgrading.