...
- backup SCS database from the current SCS system.
Code Block pg_dump -d SIPXCONFIG -U postgres --attribute-inserts > sipxdata.sql
- copy the SCS database from the SCS machine to another machine on your network.
- wiping the SCS system clean by installing sipXecs from ISO or whatever method you chose.
- copy the SCS database back onto the new sipXecs machine
- restore the SCS database
Code Block dropdb -U postgres SIPXCONFIG createdb -U postgres SIPXCONFIG psql -U postgres SIPXCONFIG < sipxdata.sql
- Migrate SCS database to sipXecs 4.2.1 format using the attached conversion script. (details to follow)
Code Block 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 (you'll get a config server error when you go to the Phones page) they can be reset to standard Bria phones with:
| Code Block |
|---|
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.
...