Enswitch 2.12 no longer uses /etc/enswitch/common.conf; this file is now obsolete. The database configuration now resides in /etc/enswitch/databases.conf, and all other configuration in the database and is configured using the new System » Configuration menu on the web interface.

2.12 adds a column to the "cdrs" table, so the database upgrade may take tens of minutes on larger systems.

To upgrade from Enswitch 2.11 to Enswitch 2.12

1. Ensure that all Asterisk machines are running 1.4.21.1 or later.
2. On all machines, create a new /etc/enswitch/databases.conf file with the following format:

   # Handler, Priority, Weight, Type, Hostname, Port, Database, Username, Password, Enable transactions
   
   default, 1, 100, mysql, 127.0.0.1, 3306, enswitch, enswitch, password, 1

   where the hostname and password fields need edited for each installation. Set this new file to be readable by the enswitch user.
3. On all machines, check out /opt/enswitch/branches/2.12.
4. On all machines, update the /opt/enswitch/current symlink.
5. On the primary database machine, do:
   • /opt/enswitch/current/bin/enswitch_upgrade
6. On all machines except the primary database machine, do the follow to update their local configuration. These can be done simultaneously, but only after the primary database machine has been done:
   • /opt/enswitch/current/bin/enswitch_upgrade
7. On all web machines, do:
   • enswitch restart
8. On the web interface, go to System » Configuration, and set any configuration settings marked as "THIS SETTING NEEDS TO BE SET ON NEW INSTALLATIONS. PLEASE SET IT NOW".
9. Review /etc/enswitch/common.conf on every machine in the system, and set the configuration settings on the web appropriately. It's important to remember that some settings in common.conf may have only been set on some machines in the cluster.
10. If you must have different settings for some machines, create an /etc/enswitch/local.conf file with the same format as the old common.conf file. Any settings in this file override the configuration in the database. Note that it is recommended to use this facility as little as possible, and most systems should not need it at all.

11. On all Asterisk and OpenSIPS/OpenSER machines (unless they are the same machine as the web machine), do:
    • enswitch restart
12. On all Asterisk machines, check that both [from-internal] and [from-external] in extensions.conf have lines that match called numbers of the form "phone_<number>".
13. If still running enswitch_soapd, please note that this is now obsolete. Please contact level 3 support for advice.
14. Test calls and the web interface.
15. On the primary database machine, do:
    • enswitch after_upgrade