6.3 How to Migrate Subscriber Settings from an OpenScape 4000 to a OSV Standard Solution

Proceed as follows to update OpenScape 4000 subscriber settings to OpenScape Voice using the WebCDC tool.
This makes use of the “Import Hipath 4000 REGEN” button on the General tab. This basically imports subscriber data from a H4K installation. The rest of the configuration (IPs, routing.branches, gateways, etc) must be manually entered in WebCDC after the import is completed. (Not all 4K data can be migrated to a OSV due to the significant differences in product architectures).
Prerequisites
•
The subscriber data of the new users is available.
•
The OpenScape 4000 system data is available for import. For supporting details on creating OpenScape 4000 system data suitable for import to WebCDC, see Appendix C, “Converting OpenScape 4000 REGEN File for WebCDC”.
•
A node.cfg file has been preconstructed for the target OSV and is available on the local PC.
Step by Step
1.
Logon to the WebCDC tool.
2.
Open a new project from the My Projects area or open an existing project to reuse.
NOTE:  If reusing an already existing project its data will be overwritten by the Import that is performed in this procedure.
3.
Sync the WebCDC data to the OpenScape 4000 database by importing the data using the Current Project > Import HiPath 4000 REGEN button.
The Import HiPath 4000 REGEN window will open.
4.
Browse to where the HiPath 4000 REGEN file is located on the local PC, select it. It is also possible to optionally browse to an already prepared node.cfg for the target OSV. Once the files(s) are selected, then click the Import Data button in the Import HiPath 4000 REGEN window.
The import of the data will be performed and a message will signal the successful completion. If instead an error message occurs, then determine the reason and repeat until success is achieved.
NOTE:  At this point it is necessary to enter additional data and/or modify the data that has been imported to the WebCDC in order to complete the configuration of the target OpenScape deployment. For example, deleting subscriber data from Subscribers which are not intended to be transferred to the OpenScape Voice System. Also to be done is assigning OSV specific features to the subscribers such as the User Digest Password generation setting (e.g. ’randomize’) and default dialing permissions.
5.
To begin tailoring and supplementing the imported data into the specific OpenScape Voice based deployment go to the Start tab and select Standard Solution (or other target deployment type) from the Deployment Architecture dropdown list.
6.
Select a UC Deployment Architecture value for the target system. If no UC will exist in the migrated target, then select value ’NO UC’.
7.
Select the OpenScape Voice version relevant for your target deployment and also the OpenScape UC App, Branch, SBC and RG8700 versions as applicable in the Start tab.
8.
Use the other tabs to specify the remaining configuration data for the OpenScape deployment target for this H4K migration. Consult the details of the specific tabs and their data elements as necessary.
9.
Once the population of the remaining WebCDC tabs is complete, generate the target configuration by clicking the Generate Config button. If errors occur while the Progress window shows the generation status, then the generation must stop (or be stopped via the Stop button), the errors corrected and this step is repeated until there is an error free run.
10.
Import the updated config files into the OpenScape devices (i.e. OSV, OSB, DLS, Xpressions, UC) by following the applicable guides, e.g. the OpenScape Voice Vx, Administration and Configuration documentation.
OpenScape Solution Set V10, Customer Data Collection with WebCDC V1, Planning Guide, Issue 2, ID: A31003-S11A0-P100-2-76A9
 © 07/2024 Mitel Networks Corporation. -  All rights reserved.
 Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.