8.12 |
Convert Customer Database |
| There are two procedures for conversion: |
| - | Procedure 1: Upgrading a HW configuration with the same SW version |
| - | Procedure 2: Upgrading a SW Version for compatible HW configurations |
| During a conversion procedure, only one type of conversion is carried out. If both types are required, conversion has to be activated twice. |
Procedure 1: Upgrading a HW configuration with the same SW version |
| The following upgrades are supported: |
| - | Hicom 150 E Office Point to Hicom 150 E Office Com |
| - | Hicom 150 E Office Com to Hicom 150 E Office Pro |
| - | HiPath 3350/HiPath 3300 to HiPath 3550/HiPath |
| For this purpose the stored old customer database is converted into a customer database created offline. |
| Only the following bulk data is transferred during conversion: |
| All non-convertible data are assigned the default values of the respective communication system. The numbering plan is taken over 1:1, and no default call numbers exist. |
Procedure 2: Upgrading a SW Version for compatible HW configurations |
| Generally, data is not lost with this type of upgrade. |
| Exceptions: |
| • | When upgrading to HiPath 3000/5000 V8 or HiPath 2000 V2/HiPath OpenOffice EE, the node number must be entered under Settings | System Parameters | Station Flags following CDB conversion, otherwise IP-networked satellite systems will no longer able to dial into the CO. |
| • | +When upgrading from Release 1.0 to Release 2.0, the system parameters "Tones and ring types" and "Time parameters" are assigned the new default values. This is because the new default values differ from the old default values. |
| • | When upgrading from OfficeStart to HiPath 3150 or from OfficeOne to HiPath 3250, STLS2 is relocated from slot 4 to slot 1. The configured stations and/or lines are lost in the process and must be reconfigured. |
| • | Any online station that may be present (always the last station), is lost in the process. |
| • | In the case of optiPoint 500 Advance devices that are already connected to systems up to and including HiPath 3000 V3.0 SMR1, upgrading to HiPath V3.0 SMR3 or higher may result in problems with key assignments. After Read CDB (System -> PC), these key assignments must be adapted manually. |
| Note: |
| - | Data which is only relevant to the new SW version is initialized beforehand. |
| - | When upgrading from OfficePro to HiPath 37xx, the slave ports remain at the original positions (from position 251 onward). However, the converted CDB must be transferred with the hardware flag set. |
| Compatible HW configuration means: |
| - | OfficeStart to OfficeStart/HiPath 3150 |
| - | OfficeOne to OfficeOne/HiPath 3250 |
| - | OfficePoint to OfficePoint Upgrades from OfficePoint to HiPath 3350/HiPath 3300 must be performed in 2 steps. First, a HW upgrade to OfficeCom with the same SW version and then a SW upgrade to HiPath 3350/HiPath 3300. |
| - | OfficeCom to OfficeCom/HiPath 3550/HiPath 3500 (independent of number of boxes) |
| Note: |
| - | The above mentioned conversions also work form Hicom 150 H V1.2 to HiPath 3000 V1.2. |
Importing IP client data from one or more HG 1500 CDBs |
| After the system CDB has been converted successfully, you can import IP client data from one or more HG 1500 CDBs. The data of the client is automatically transferred from the selected database to the converted system CDB. |
| The following general conditions apply: |
| - | Importing is only possible when converting to HiPath 3000 Version 3.0. |
| - | Only data from customer databases of HG 1500 Version 2.4 can be imported. If required, the CDB or CDBs must first be converted to the appropriate version using Manager I. |
| - | Only the client data that can be uniquely assigned via the DID number and the client type is imported. |
|
| HiPath 3000/5000 V8, Manager E, Administrator Documentation, Issue 11 | up |
|
|
||
| Disclaimer & Copyright | ID: P31003H3580M1000176A9 | 2011-03-18 |