Installations of sipFoundry Canary that are being upgraded to sipXcom will require a special procedure to ensure full DB compatibility. So, the recommended upgrade method would generally be as follows:
- Install a server with sipXcom ISO
- Create a backup of the sipFoundry Canary system through the UI
- Restore that backup to the new sipXcom server through the UI. Note that although the restore should work, there will still be issues with the DB due to incompatible table names and columns related to the E911/Emergency Dialing functionality. This DB incompatibility will need to be manual corrected as show in step 4.
- Correct DB compatibility issues relating to E911/Emergency Dialing as follows:
psql -U postgres SIPXCONFIG
alter table e911 rename to e911_erl;
ALTER TABLE e911_erl RENAME COLUMN e911_id TO erl_id;
create sequence erl_seq;
ALTER TABLE e911_erl ADD (ip_addr_start character varying, ip_addr_end character varying);
ALTER TABLE e911_erl ADD column ip_addr_start character varying;
ALTER TABLE e911_erl ADD column ip_addr_end character varying;
- service sipxconfig restart
At this point you're installation will have the corrected DB structure for sipXcom and therefore be functioning normally. To confirm that the installation is now functioning correctly from a DB perspective, log into the sipXcom system UI and send profiles to the server. Ensure that this completes without error in the Job Status page.
Note: Testing of this method was not performed for a case where data existed in the original e911 table from the sipFoundry system.