Upgrade

ShoreTel: ShoreGear T1 and BRI Switch Failure after Upgrade

Affected Version(s):

ShoreTel 14.2 build 19.45.8701.0

Problem Details:

ShoreTel ShoreGear T1 and BRI switches using CAS or BRI trunk types have experienced switch failures after upgrading to ShoreTel 14.2 build 19.45.8701.0. Customers who have upgraded to this build might have noticed the following issues:

• Inbound calls do not work, but outbound calls do work
• ShoreGear T1 and BRI switches that host CAS or BRI trunks might crash and reboot every 5 minutes

Cause:

Upgrading to ShoreTel 14.2 build 19.45.8701.0.

Solution:

The current solution is to download the patch provided on ShoreTel’s website: http://bit.ly/1WCN2Wc

You should only apply this patch to the switches that are running build 19.45.8701.0 and have experienced this issue. Detailed instructions for applying the patch are provided as part of the download file.

Avaya IP Office: Virtual Essential Edition License

Introduction

This How-To covers the upgrade process required to generate the Virtual Essential Edition License when upgrading an from below Release 8.0.

Steps:

1: Upgrade the system to Release 7.0

If your system is running at Release 6 or below, upgrade to the last build of Release 7.0: 7.0 (36). If you are already running an earlier build of Release 7.0, then you must upgrade to 7.0(36) as well.

2: Upgrade the system to Release 8.0

Once the system is running Release 7.0(36), upgrade the system to the last build of Release 8.0: 8.0(66).

Conclusion

This should now show the system as having a Virtual Essential Edition License. Please note that this license will not show in offline configs and will likely display an error.

If the license did not generate, an Essential Edition License will need to be purchased.

Please note, should the chassis fail at any point in the future and you need to migrate to a new chassis, an Essential Edition License will need to be purchased as this license is tied to the chassis.

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.