Migrating from SCS 4.2.1

Summary

This procedure will work if you're migrating from SCS 4.2.1 to sipXecs 4.4.0 or any future version of sipXecs.

This only covers how to restore the database which holds all the configuration information. It does not cover how to uninstall SCS binaries and install sipXecs binaries. Although it may be possible to do this, I recommend the following procedure to effectively migrate from an SCS 4.2.1 system:

1. backup SCS database from the current SCS system.

   pg_dump -d SIPXCONFIG -U postgres --attribute-inserts > sipxdata.sql

2. copy the SCS database from the SCS machine to another machine on your network.
3. wiping the SCS system clean by installing sipXecs from ISO or whatever method you chose.
4. copy the SCS database back onto the new sipXecs machine
5. restore the SCS database

   dropdb -U postgres SIPXCONFIG
   createdb -U postgres SIPXCONFIG
   psql -U postgres SIPXCONFIG < sipxdata.sql

6. Migrate SCS database to sipXecs 4.2.1 format using the attached conversion script. (details to follow)

   psql -U postgres SIPXCONFIG < de-scs-4.2.1.sql

For sipXecs 4.4 systems or higher, simply startup sipXecs and allow it to automatically migrate database

Voicemail can be copied from existing 4.2.1 server because xml file structure remained the same. Just make sure that user/group on all copied files is sipxchange:sipxchange.

If any of Avaya's softphones were defined they can be reset to standard Bria phones with:

psql -U postgres SIPXCONFIG -c "update phone set model_id = 'counterpathCMCEnterprise' where model_id = 'bria'"

All steps except number 6: "Migrate SCS database to sipXecs 4.2.1" I leave to you to figure out or find respective documentation on this wiki to detail.

Migrate SCS database to sipXecs 4.2.1

1. Download the attached script de-scs-4.2.1.sql to the freshly installed sipXecs 4.2.1 target machine
2. Run

   psql -U postgres SIPXCONFIG < de-scs-4.2.1.sql