Most changes in Enswitch 3.12 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.
- If you have any resellers who use a different URL for the web interface, please ask them to set the "Web URL base" custom setting for each of their rate plans immediately after the upgrade. Failure to do so will lead to your URL appearing in emails to their customers.
- The default template for PDF invoices has changed to allow calls to be grouped by source, and also various minor layout changes to existing ways of displaying calls. If you have any custom templates in rate plan custom settings, please update these. Please also create a test invoice and check how calls are displayed, even if you have no custom templates.
- The control panel CSS has changed. If you have a custom design, please merge your changes.
- Calls to <number>@<peer> have the number converted to the customer's dial plan before routing. Please update any such numbers after the upgrade.
- The upgrade process deletes all existing busy lamp subscriptions, so busy lamps will stop working until handsets resubscribe.
- Emails sent out from Enswitch now include "Auto-Submitted: auto-generated" and "Precedence: bulk" headers.
- If an outbound fax is retried, a notification email is only sent for the last attempt.
- The wording of the dial by name menu has changed.
- Trace messages of types "api" and "web" are no longer logged by default.
- The customers .csv export has a new "Email on low balance" column.
- Recordings are cleaned up in enswitch_cleanup instead of enswitch_fees, and a new enswitch_integrity program must be run to compare recording files to database entries and clean up any discrepancies.
- Queue event exports now used <end rather than <=end on the table select.
- As always, some SOAP API functions have changed. Please see /opt/enswitch/current/doc/api_changes.txt for a list.