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

• Custom provisioning templates under /etc/enswitch/templates/<language>/provision/* are no longer used. If you have any custom templates in these directories, please copy your changes to Features » Provisioning after the upgrade.
• The menu system has changed, and the CSS has been changed to match, so please update any custom CSS files after the upgrade.
• If you've changed the names of any menus, your changes will be lost during the upgrade. Please go to System » Menus after the upgrade and redo your changes.
• The "Ask web URL" destination type has been migrated to its own menu, and its own database table. Where possible, data has been migrated automatically, but this has not been possible in 100% of cases. Please ask your customers to review and update any PBX features that use this destination type. Until they do, their calls should continue to work.
• Data in the database is now explicitly expected to be UTF-8 encoded.
• Only one web user may be downloading recordings at any time to prevent excessive load on the web and NFS servers.
• Users are warned when saving telephone lines if any telephones in other customers have the same MAC address. They are not told which telephone line(s) or customer(s), merely how many.
• The format of the call history CSV export has changed.
• As always, some SOAP API functions have changed. Please see /opt/enswitch/current/doc/api_changes.txt for a list.