Please note that 2.11 splits the database upgrade into two parts. "enswitch_upgrade" adds new tables and fields required by the new version. "enswitch_after_upgrade" removes old tables and fields no longer required by the new version. This allows some components to be running the old version while others are running the new version. It is not recommended to do this for any significant length of time, but it does allow telephony, the web interface, and the SOAP API to continue to be available to users while the upgrade is running. Therefore the upgrade can be done with only a few seconds outage.

2.11 makes no changes to the "cdrs" or "cdrcosts" tables, so the database upgrade should run in less than a minute on most installations.

To upgrade from Enswitch 2.10 to Enswitch 2.11

1. On all machines, check out /opt/enswitch/branches/2.11.
2. On all machines, update the /opt/enswitch/current symlink.
3. On the primary database machine, do:
   • /opt/enswitch/current/bin/enswitch_upgrade
4. On all Asterisk machines, do:
   • /etc/init.d/enswitch_routed restart
   • asterisk -rx reload
5. On all web machines, do:

   Debian / Ubuntu:

   • invoke-rc.d apache2 restart

   Others:

   • service httpd restart
6. If still running enswitch_soapd, please note that this is now obsolete. Please contact level 3 support for advice.
7. If there is only a single OpenSER machine, do:
   • /etc/init.d/enswitch_sipd restart
   • /etc/init.d/openser restart
8. If there are a pair of OpenSER machines using heartbeat, do:
   • /etc/ha.d/resource.d/enswitch_sipd restart
   • /etc/ha.d/resource.d/openser restart
9. Test calls and the web interface.
10. On the primary database machine, do:
    • /opt/enswitch/current/bin/enswitch_after_upgrade