9.2.3 |
Upgrading from V7 to V8 |
9.2.3.1 |
Introduction |
Prerequisites |
| The following prerequisites must be fulfilled when upgrading software from HiPath 3000/5000 V7 to HiPath 3000/5000 V8: |
| • | There are new licenses available for HiPath 3000/5000 V8. |
| • | All IP workpoints (HFA) in a system or all IP workpoints (HFA) in a network must be EFC-enabled. |
| The CorNet-IP protocol was extended in HiPath 3000/5000 V7 to include the EFC (Extended Fast Connect) protocol variant. |
| EFC is an absolute prerequisite to be able to fully use all features. It is only permitted to deactivate the EFC protocol variant when upgrading a network. Otherwise features can be interrupted. |
| EFC is the basis to be able to use for example the following features: |
| - | Signaling & Payload Encryption SPE |
| Signaling & Payload Encryption is supported in HiPath 3000/5000 V7 R4 and higher. This allows both signaling and payload data to be encrypted at station level. |
| Signaling Encryption = signaling data encryption: The signaling transmission between HiPath 3000/5000 and the connected IP workpoints, e.g. OpenStage, OpenScape Personal Edition, is encrypted using a 128-bit key. The same mechanism is used to encrypt the signaling data between IP-networked systems (HiPath 2000/HiPath OpenOffice EE, HiPath 3000, HiPath 4000, HiPath 5000). |
| Payload Encryption = encryption of the payload data (voice data): The payload data is transmitted using the Secure Real-time Transport Protocol (SRTP) and is encrypted with a 128-bit key. SRTP is also used to encrypt the payload data between IP-networked systems (HiPath 2000/HiPath OpenOffice EE, HiPath 3000, HiPath 4000, HiPath 5000). The Deployment Service DLS distributes the commonly used key for a secure domain. The procedure to swap out the key for SRTP is called Multimedia Internet Keying (Mikey). |
| - | IP/IP E2E payload via enterprise proxy for Internet telephony |
| IP/IP E2E payload via enterprise proxy is supported for Internet telephony in HiPath 3000/5000 V7 R2 or higher. This means that, for Internet telephony, data packets do not need to be processed by the digital signal processors of the system. Calls are routed via LANs, routers and the Internet Telephony Service Providers (ITSP). HiPath 3000 sets up a call to the remote station. |
| Instead, the maximum number of simultaneous calls depends on the codec used and the available bandwidth of the Internet telephony connection. |
|
| The procedure for upgrading software depending on the various scenarios is described in the following sections. |
Individual EVM announcements in the case of upgrades |
| In the case of an upgrade from HiPath 3000 V7 to V8, the individual announcements and messages are deleted. |
9.2.3.2 |
Upgrading a HiPath 3000 Standalone System |
Procedure |
| 1. | Check that all connected IP workpoints (HFA) are EFC-enabled: |
| 2. | Upgrade all IP workpoints with the current EFC-enabled software. |
| Refer to the Release Notes and Sales Release for information on the latest software versions. |
| 3. | Upgrade all HG 1500 boards to V8. |
| 4. | Convert the customer database (CDB) and reload it together with the V8 system software. |
| 5. | Install new licenses. |
| The upgrade is complete. |
9.2.3.3 |
Upgrading a HiPath 5000 RSM Network |
Procedure |
| 1. | Check that all IP workpoints (HFA) in the network are EFC-enabled: |
|
| 2. | Upgrade all IP workpoints with the current EFC-enabled software. |
| Refer to the Release Notes and Sales Release for information on the latest software versions. |
| 3. | Dissolve the network: |
| a) | Remove all systems (nodes) belonging to the network from HiPath 5000 RSM. |
| a) | FeatureStop the server service. |
| 4. | Upgrade each system that belongs to the network: |
| a) | Upgrade all HG 1500 boards to V8. |
| b) | Convert the customer database (CDB) and reload it together with the V8 system software. |
| 5. | Once all standalone systems have been upgraded, you can upgrade HiPath 5000 RSM on site. To do this, add all systems (nodes) belonging to the network to HiPath 5000 RSM. |
| 6. | Put the network into service with HiPath 3000/5000 V8 (commission the Feature server service). |
| 7. | Install new licenses. |
| The upgrade is complete. |
9.2.3.4 |
Upgrading a HiPath 3000 System with HiPath 2000/HiPath OpenOffice EE |
Procedure |
| 1. | Check that all IP workpoints (HFA) in the network are EFC-enabled: |
|
| 2. | Upgrade all IP workpoints with the current EFC-enabled software. |
| Refer to the Release Notes and Sales Release for information on the latest software versions. |
| 3. | Upgrade each system that belongs to the network: |
| • | Upgrade HiPath 3000 systems and the associated HG 1500 boards to V8. Convert the customer database (CDB) and reload it together with the V8 system software. |
| • | Upgrade HiPath 2000 systems to V2/HiPath OpenOffice EE. Convert the customer database (CDB) and reload it together with the V2 system software. |
| 4. | Install new licenses. |
| The upgrade is complete. |
9.2.3.5 |
Upgrading a HiPath 3000 System Networked with HiPath 4000 |
|
Procedure |
| 1. | Check that all IP workpoints (HFA) in the HiPath 3000 system are EFC-enabled: |
|
| 2. | Upgrade all IP workpoints in the HiPath 3000 system with the current EFC-enabled software. |
| Refer to the Release Notes and Sales Release for information on the latest software versions. |
| 3. | Upgrade the HiPath 3000 system: |
| a) | Upgrade all HG 1500 boards to V8. |
| b) | Convert the customer database (CDB) and reload it together with the V8 system software. |
| 4. | Gateway Call Flag "Always Use DSP" in the direction of HiPath 4000 (HiPath 3000 Manager E: Settings - Lines/networking ... - Special). |
| • | Activate flag, if the H.323 protocol is used for networking (old versions of HiPath 4000) Note: As HiPath 4000 is not EFC-enabled, activating this flag sets up gateway connections to the HiPath 4000 system. |
| • | Deactivate flag, if the SIP-Q protocol is used for networking (new versions of HiPath 4000) |
| The upgrade is complete. |
| HiPath 3000/5000 V8, Service Documentation, Issue 10 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3580S100017620 | 2011-01-24 |