Avaya IP Office: Migrating ContactStore To A New Server

Introduction

This How-To covers the migration of a ContactStore installation onto a new server.

Steps:

1: Backup the ContactStore Database

To backup the ContactStore database, you need to use the following command line procedure:

Log on to the ContactStore server and open a command prompt window

Change the directory to the \bin folder in the ContactStore installation path using the cd (change directory) command

Create a backup file by entering the command:

winbackup <backupfile> (where <backupfile> is the full path name for the backup file)

Make sure there is enough space on the target drive for the backup file. Consider copying the backup file to another server, or external media.

NOTE: The procedure uses the PostgreSQL pg_dump command to extract data from the database. It must be executed while the database is running. Do not stop the ContactStore service or the PostgreSQL service before proceeding.

2: Install ContactStore on the New Server

Once you have taken the backup, install ContactStore onto the new server.

NOTE: For IPO releases up to and including R9.1, Windows Server 2008 32-bit is the only supported operating system for running ContactStore. It is possible that it will work fine on other operating systems but is not something that is supported by Avaya.

3: Restore the ContactStore Database

The following process will erase the default database that exists after a complete re-installation and replaces it with the database that you have previously backed up in Step 1.

First you need to copy the backup from the old server onto the new server. Then stop the ContactStore service and open a command prompt window, changing the directory to the \bin folder in the ContactStore installation path using the cd (change directory) command.

Then you will need to enter the following command:

winbackup <backupfile> restore (where <backupfile> is the full path name for the backup file)

If you receive a warning stating that “pgpsql already exists”, ignore this warning.

Once completed, start the ContactStore service again.

4: Copy the Calls Folder Onto New Server

Once the ContactStore service has started, copy the calls folder used by the previous server to the location (Server | Call Storage Path) set for the new server.

 

Conclusion

 

You should now have all of your calls on the new server, ready to be searched and replayed.

References

Unify OpenScape Business: Upgrading from a HiPath 3000 – Part 2

Introduction

This How-To covers the upgrade process that is needed to migrate a Siemens HiPath 3000 to Unify OpenScape Business.

Steps:

1: Connect all available Handsets

Connect all analogue (A/B) and digital (TDM) phones to the system. For analogue devices, plug them in and lift the handset for it to register there is an analogue device there and ensure numbers are assigned to the handsets. This will ensure you get the right licensing when you complete the upgrade.

2: Upgrade HiPath to Version 9

Upgrade the system to Version 9, preferably the latest release. The system needs to be running Version 9 before you download the KDS.

3: Download KDS

Download the KDS using the latest version of Manager E (Version 10).

4: Migrate Hardware

Migrate the hardware from HiPath 3000 to OpenScape Business, taking out what you don’t need e.g. main board, HG card etc. and then replacing it with the OpenScape Business kit.

5: Run through Initial Wizard

Power up the OpenScape Business and go through Initial Wizard in the Web Based Management (WBM) to setup the system’s default parameters.

6: Upgrade OpenScape Business to the Latest Release

Upgrade the OpenScape Business to latest General Release software.

7: Convert the KDS

Convert the KDS file to OpenScape Business V1 or V2 (depending on the version you are migrating to) using Manager E.

8: Upload converted KDS

Upload the converted KDS into OpenScape Business. This will require a reboot.

9: Fill in Customer Details

Once the system is back up, fill in the customer’s details in the Licensing section through the WBM.

10: Download XML File

Download the XML file from the WBM. Open the XML file, select everything in it apart from the top line, then copy and paste into the Central License Server (CLS). If the XML file is blank, you will need to use Card Manager to re-write the SD card but make sure all previous steps have been followed correctly.

11: Generate License File

Generate the license file through the CLS and apply to the system.

Conclusion

You should now have a fully working OpenScape Business system.

Unify OpenScape Business: Upgrading from a HiPath 3000 – Part 1

Introduction

This How-To covers the licensing, software upgrades and kit that is needed to upgrade a Siemens HiPath 3000 to Unify OpenScape Business.

Steps:

1: Determining Upgrade Licensing and Software Upgrade

If your HiPath 3000 is running Version 5/6/7, you will require the following Software Upgrade licensing (depending on whether you have a 33×0/35×0/3800):

L30251-U600-G593 – HiPath 33×0/35×0  Software Upgrade to V9

L30251-U600-G594 – HiPath 3800  Software Upgrade to V9

You will also require the Upgrade and License Migration license:

L30250-U622-B607 – Upgrade & License Migration HiPath 3000 V9 -> OSB

If your HiPath 3000 is running Version 8, you will require the following Software Upgrade licensing (depending on whether you have a 33×0/35×0/3800):

L30251-U600-G591 – HiPath 33×0/35×0  Software Upgrade to V9

L30251-U600-G592 – HiPath 3800  Software Upgrade to V9

Again, you will also require the Upgrade and License Migration license:

L30250-U622-B607 – Upgrade & License Migration HiPath 3000 V9 -> OSB

If your HiPath 3000 is running Version 9, you will only require the Upgrade and License Migration license:

L30250-U622-B607 – Upgrade & License Migration HiPath 3000 V9 -> OSB

2: Determining Hardware Upgrade

You will not be able to keep your existing motherboard and will need to swap this out for one of the following Unify parts:

If you have a HiPath 3300/3500 and are migrating to an OpenScape Busines X3R/X5R, you will need the following part:

L30251-U600-G616 – HiPath 3300/3500 V9 to OSBiz X3R/X5R

If you have a HiPath 3350/3550 and are migrating to an OpenScape Busines X3W/X5W, you will need the following part:

L30251-U600-G617 – HiPath 3350/3550 V9 to OSBiz X3W/X5W

If you have a HiPath 3800 and are migrating to an OpenScape Busines X8, you will need the following part:

L30251-U600-G618 – HiPath 3800 V9 to OSBiz X8

Conclusion

You should now have everything you need to start the upgrade process from HiPath to OpenScape Business which will be detailed in Part 2.