TECHNICAL COMMUNICATION No. TC0778 Ed.

04

OmniPCX Enterprise Nb of pages : 24 Date : 27 July 2007

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT: MIGRATION OmniPCX 4400 TO OmniPCX Enterprise

Until Release 6.2, this document corresponded to appendix 3 of the installation procedure of a version.
From Release 7.0, this appendix becomes a technical communication to make easier its search, its
consulting and its update.
History
Edition 03: Update for Release 7.1
Edition 04: Update for Release 8.0

1
 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

MIGRATION OmniPCX 4400

TO
OmniPCX Enterprise

CONTENTS

1. PROCEDURE OF MIGRATION FROM OMNIPCX 4400 TO

OMNIPCX ENTERPRISE R8.0.........................................................5
1.1. Introduction .............................................................................................. 5
1.2. Purpose of the procedure.......................................................................... 5
1.3. Content of the procedure.......................................................................... 5

2. REFERENCES................................................................................6

3. GENERAL RULES OF MIGRATION OF A SYSTEM TO R8.0..............6

3.1. Actis and migration................................................................................... 6
3.2. Synchronizing the operations to be carried out during deployment of the
migration.................................................................................................. 6
3.3. Required method for implementing the migration .................................... 7
3.4. Changeback possibilities .......................................................................... 7
3.5. Rules to be observed................................................................................. 7

4. ACTIS CONFIGURATION .............................................................7

4.1. Replacement of applications and hardware common to both scenarios of
migration.................................................................................................. 7
4.1.1. LIOe / TSC-LIOe................................................................................................7
4.1.2. INT1/INT2 ........................................................................................................8
4.1.3. LIOB/LIOP/LIOX ................................................................................................8
4.1.4. DECT2/DECT4...................................................................................................8
4.1.5. OmniMessage...................................................................................................9

Ed. 04 / 27 July 2007 1 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

4.1.6. OmniVista.........................................................................................................9
4.1.7. OmniTouch Contact Center...............................................................................9
4.1.8. Migration eCC "4980 Web Softphone" to OmniTouch UC R5.0 .........................9
4.1.9. Migration 4635 Visual Messenger to OmniTouch UC........................................9
4.1.10. 2600, 4600, 5400 set equipment...................................................................9
4.1.11. 4300 set equipment.....................................................................................10
4.2. Replacement of applications and hardware specific to each scenario of
migration................................................................................................ 10
4.2.1. Scenario 1: Migration of "ISO" type.................................................................10
4.2.2. Scenario 2: Migration of "Appliance Server" type ............................................11
4.3. Non replacement of applications and hardware by Actis ........................ 11
4.3.1. Common case to both scenarios .....................................................................11
4.3.2. Specific case for scenario 2: Migration of "Appliance Server" type ..................11

5. OPERATIONS TO BE CARRIED OUT ON THE SITE BEFORE

STARTING THE MIGRATION.......................................................12

6. OPERATIONS TO BE CARRIED OUT IN LABORATORY BEFORE

STARTING THE MIGRATION.......................................................12
6.1. Prior deletion of the "phase out" applications and hardware .................. 12
6.2. Replacement of applications and hardware specific to each scenario of
migration................................................................................................ 13
6.2.1. Scenario 1: Migration of "ISO" type.................................................................13
6.2.2. Scenario 2: Migration of "Appliance Server" type ............................................13
6.3. Replacement of applications and hardware common to both scenarios of
migration................................................................................................ 14
6.3.1. OmniMessage.................................................................................................14
6.3.2. OmniTouch Contact Center.............................................................................14
6.3.3. 2600, 4600, 5400 set equipment ....................................................................14
6.3.4. 4300 S/M/L set equipment..............................................................................14
6.4. Moving the shelves 18 and 19 ................................................................ 14
6.5. Preparing the applications and hardware ............................................... 14
6.5.1. Required means..............................................................................................14
6.5.2. Additional management specific to each scenario of migration ......................15

TC0778 2 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

7. SUMMARY FLOW CHART ...........................................................19

8. INTERWORKING IN HETEROGENEOUS NETWORK ....................22

9. SWITCHOVER OF THE INSTALLATION IN R8.0 ON SITE .............22

9.1. Voice mail in network ............................................................................. 22
9.2. System synchronization........................................................................... 22

Ed. 04 / 27 July 2007 3 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

TC0778 4 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

1. PROCEDURE OF MIGRATION FROM OmniPCX 4400 TO OmniPCX

ENTERPRISE R8.0

1.1. Introduction
This document applies for the migration from OmniPCX 4400 to OmniPCX Enterprise which the
release is 8.0.

1.2. Purpose of the procedure

The purpose of this document is to advise technicians on how to prepare and install the migration
from a Stand-Alone or network OmniPCX 4400 to an OmniPCX-Enterprise R8.0.
This operation can be delicate, since it requires preparation and a methodical approach.
In fact, R8.0 does not support the migration of a certain number of "phase out" internal, external
applications and hardware which were authorized in previous releases.
In a network configuration, interworking rules must also be respected between R8.0 and
heterogeneous releases.
You must replace and upgrade all these items for the date of switch of installation in R8.0.
This document does not deal with simultaneous additions of new functionalities and hardware,
except when "phase out" applications and hardware are concerned.

It is highly unadvisable to cumulate migration and addition operations.

1.3. Content of the procedure

The procedure describes the various stages necessary for the migration of an installation by taking
into account two scenarios.
Scenario 1: Migration of "ISO" type
Migration of a system requiring new R8.0 functionalities without modifying the type of
"Communication Server", in other words it retains its 4400 CPUs. This type of migration is called
"ISO".
Scenario 2: Migration of "Appliance Server" type
Migration of a system requiring new functionalities of R8.0 and an evolution in the type of
"Communication Server" from a CPU 4400 to an Appliance Server that the processing capacities
allows to reduce the number of nodes in the future and to replace them by ACTs over IP. This type of
migration is called "Appliance Server".
The procedure gathers the various stages common to both scenarios and distinguishes the specific
stages to each of them.

Ed. 04 / 27 July 2007 5 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

CHRONOLOGY OF STAGES
1 General rules for the migration of a system to R8.0.
2 Actis configuration:
• Replacement of applications and hardware common to both scenarios.
• Replacement of applications and hardware specific to each scenario.
• No replacement of applications and hardware by Actis.
3 Operations to be carried out on the site before starting the migration.
4 Operations to be carried out in laboratory before starting the migration:
• Operations common to both scenarios.
• Operations specific to each scenario.
5 Summary flow-chart.
6 Interworking in heterogeneous network.
7 Switchover of the installation in R8.0 on site.

2. REFERENCES
TC0155 Compatibility of Alcatel 4635 with OmniPCX 4400 backplanes (Reminder of restrictions)
TC0259 Migration procedures
TC0487 ACD-V1 Migration to CCDistribution
TC0779 Synchronization of a system after migration to OmniPCX Enterprise with Appliance Server
TC0934 Alcatel 4635 Installation procedure for version 5.3.1
TC0943 Installation procedure for version G1.302.5 – Release 8.0

3. GENERAL RULES OF MIGRATION OF A SYSTEM TO R8.0

3.1. Actis and migration

Any system migrating to R8.0 must be configured using Actis ≥11.2 catalogue E08.
Since Actis knows the "phase out" internal and external applications and the hardware that are not
carried over to this version, it deals with the ordering of these applications and hardware.
However, in certain cases, operations may be required that are not taken into account by Actis.

3.2. Synchronizing the operations to be carried out during deployment of the

migration
The deployment of the migration requires perfect synchronization of the operations to be carried out
by the technicians, before, during and after the migration.

TC0778 6 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

3.3. Required method for implementing the migration

The preparation of the migration on a laboratory system will in most cases make the work easier,
reduce the time spent on the site and minimize system disturbance.

3.4. Changeback possibilities

At each stage of the deployment of the migration, provisions must be made for the possibility of a
changeback in the event of a serious problem during the migration.

3.5. Rules to be observed

Due to the obsolescence of applications and hardware, the preparation of an ISO migration must
observe a certain number of rules in order to limit the time for which the system is unavailable
to the client.
Actis migrates the system to R8.0 in a single step, in other words it considers that all the applications
and hardware that cannot be migrated have been replaced. However, the migration planning must
endeavor to limit the cumulation of operations to be carried out at the last minute.
For the migration of network systems, a preliminary study by the Pre-Sales service must be carried
out to show, if necessary, any incompatibility between the different hardware used for voice over IP.
This information must be passed on to the technician in charge of carrying out the migration.

4. ACTIS CONFIGURATION
After the configuration, Actis plans to replace the "phase out" applications and hardware as well as
the replacement of applications and hardware according to the type of migration scenario.
Actis generates licenses and hardware, a part of which can be used immediately in the laboratory by
the technician.
In every case, it will be necessary to plan methodically the operations to be carried out.
− The replacement of applications and hardware common to both scenarios of migration is
detailed in § 4.1 .
− The replacement of applications and hardware specific to each scenario of migration is detailed
in § 4.2 .
− The no replacement of applications and hardware common to both scenarios of migration in
detailed in § 4.3 .

4.1. Replacement of applications and hardware common to both scenarios of

migration
As R8.0 does not accept some "phase out" applications and hardware, Actis plans their replacement
for the both types of migration scenario.

4.1.1. LIOe / TSC-LIOe

LIOe and TSC-LIOe boards are no longer supported as of Release 6.0. When migrating, they are
automatically changed toINTIP2 board.

Ed. 04 / 27 July 2007 7 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

INTIP2 migration packages were create to help the replacement and to reduce the cost.
Note
LIOe and TSC-LIOe boards must also be changed when functioning in heterogeneous network
whatever the node releases facing a R8.0.

4.1.2. INT1/INT2
These boards are no more supported from Release 6.1.
On installations equipped with these boards, Actis replaces automatically the boards:
− INT1A / INT2A by INTOF2–A board,
− INT1B / INT2B by INTOF2–B board.

4.1.3. LIOB/LIOP/LIOX
These boards are in phase out from Release 6.1. Actis 10.1 does not allow the feature for addition
or for new installation.

4.1.4. DECT2/DECT4
DECT2/DECT4 boards configured on installations to be migrated, are supported by OmniPCX
Enterprise Releases 5.1, 6.0.x, 6.1.x, 6.2, 7.x, 8.0 but are not allowed in addition.
Moreover, DECT8 boards are not compatible with DECT2/DECT4 boards. These latter must be
replaced by DECT8 boards.

TC0778 8 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

4.1.5. OmniMessage
The 4630 voice mail is replaced by the 4635J voice mail.
The 4635H and 4635H-1 voice mails are replaced by 4635H-2 voice mails.
46xx hardware status of system to be migrated:

Status before migration Station after migration

VPCPU VPM35-1
VPCPU-1 VPM35-1
VPM35 VPM35-1
VPS35 VPU6
MSB MSBI
MSB2IB ATB2 (if one MSBI board)
MSB2IB ATB3I (if two MSBI boards)
VMU-OBCA (CPU3 board) VMU-OBCA2 (with CPU6 board)
VMU-OBCA (CPU5 board) IO2N (with CPU7 board)

4.1.6. OmniVista
The 4715, 4730, 4740 4755 and OmniVista 4760 R1.0/1.5 applications are replaced by the
OmniVista 4760 Release 4.2 application.
It is mandatory to migrate from OmniVista 4760 R2.x, R3.x, R4.0, R4.1 to Release 4.2.
For more information regarding the OmniVista 4760/OmniPCX Enterprise release compatibility,
refer to the technical communication TC0943 Installation procedure for version G1.302.5 – Release
8.0.

4.1.7. OmniTouch Contact Center

The ACD-V1 is replaced by the CCD.
The supervisors are replaced by the CCS.

4.1.8. Migration eCC "4980 Web Softphone" to OmniTouch UC R5.0

eCC "4980 Web Softphone" application is automatically migrated to OmniTouch Unified
Communication R5.0 application (OmniTouch UC).

4.1.9. Migration 4635 Visual Messenger to OmniTouch UC

4635 Visual Messenger application is no longer supported in Release 8.0. It is replaced by
OmniTouch UC R5.0 application.

4.1.10. 2600, 4600, 5400 set equipment

The 2600, 4600 and 5400 analog equipment is replaced by eZ32 boards.
The 2600, 4600 and 5400 digital equipment is replaced by eUA32 boards.

Ed. 04 / 27 July 2007 9 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

4.1.11. 4300 set equipment

The 4300 analog equipment is replaced by eZ32 boards.
The 4300 digital equipment is replaced by eUA32 boards.

4.2. Replacement of applications and hardware specific to each scenario of

migration
As R8.0 does not accept some "phase out" applications and hardware, Actis plans in addition their
replacement according to the type of migration scenario.

4.2.1. Scenario 1: Migration of "ISO" type

This type of migration is intended to offer new functionalities to the client.
The "Call-Server" remains a 4400 CPU type, but since R8.0 no longer takes into account certain
"phase out" applications and hardware, the operations to be carried out will have to be planned
methodically.

4.2.1.1. Communication Servers

− Migration to OmniPCX Enterprise R8.0 with changing the CPU.
• The systems with CPU3 change to CPU6 with:
♦ automatic replacement of disk if less than 6 GB,
♦ 128 MB SDRAM.
• The systems with CPU5 Step1/CPU5 Step2/CPU5 Step3 change to CPU7 with:
♦ automatic replacement of disk if less than 6 GB,
♦ 256 MB SDRAM.
• The systems with CPU6 remain with CPU6:
♦ automatic replacement of disk if less than 6 GB,
♦ 256 MB SDRAM.

4.2.1.2. IO2
When migrating, IO2 is changed to IO2N board if Actis configures a CPU7.x board.

4.2.1.3. OBCA
CPU7.x board does not support the OBCA2 daughter board. Actis will configure the IO2N board
when the number of channels is different of zero.

TC0778 10 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

4.2.2. Scenario 2: Migration of "Appliance Server" type

This type of migration replaces a 4400 CPU with an Appliance Server and an INTIP2 and implies the
deletion of the IO2, IO2N and OBCA couplers.
As with the ISO type migration, Release 8.0 no longer takes into account certain "phase out" external
applications, internal applications and hardware. These restrictions are more significant due to the
disappearance of the IO2, IO2N or OBCA coupler.

4.2.2.1. Communication Servers

4400 CPUs are deleted and replaced with Appliance Servers.
The IO2s are deleted and replaced with INTIP2s.

4.2.2.2. RMA
The RMA is deleted and replaced with an RMA in an S type cabinet (rack 1U).

4.2.2.3. Particular case of the Appliance Server replacing a CPU6

Addition of a GPA2 board for the voice guides and Q23 generators, if these were provided by the
CPU6s.
The 4615 voice mail on a VMU/OBCA daughter board is replaced by a 4635J voice mail.
The DTM daughter board for the DECT synchronization is deleted and replaced by a DECT8 board
to carry out the same function. If the site was equipped with DECT2 or DECT4 boards, since these
are not compatible with DECT8s, they will be replaced by DECT8 boards.

4.3. Non replacement of applications and hardware by Actis

4.3.1. Common case to both scenarios

Whatever the type of migration, Actis does not plan to replace the SPB daughter boards(extension of
the V24 ports of the system), but enforces the deletion of this circuit. The Actis operator then has the
choice of replacing the old SPB accesses, either with TA V120 accesses or with one or more V24-IP
modules.

4.3.2. Specific case for scenario 2: Migration of "Appliance Server" type

Actis does not plan to replace the SPB daughter boards (extension of the V24 ports of the system),
but enforces the deletion of this circuit. The Actis operator must replace the old SPB accesses with
one or more V24-IP modules. These operations must be carried out manually using Actis.
If removing the IO2, IO2N and OBCA boards, Actis does not configure the hardware that could be
involved in the replacement of the functionalities using these boards.
Level 3 ACTs connected behind an INTOF coupler are no longer authorized. They must be replaced
by ACT-IPs. Since Actis has no knowledge of level 3 ACTs installed on the site, it does not take into
account the replacement of INTOF couplers with INTIP couplers. These operations must be carried
out manually using Actis.

Ed. 04 / 27 July 2007 11 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

5. OPERATIONS TO BE CARRIED OUT ON THE SITE BEFORE

STARTING THE MIGRATION
− Replace the SPB board with V120 accesses on IO2 or IO2N as well as the 4635H and 4635H-1
voice mails. The replacement can be carried out on the site before the migration since they do
not require new licenses.
− Back up the database and the Chorus data on the site () Note).
This database is used for preparing the migration in the laboratory. This means that as of the
moment that the database is backed up, until the site is switched over to R8.0, any modifications
made on the site will not be carried over, unless they have been listed by the client.
Note
There is no automatic translation of Chorus data of Releases below R3.0. You should not restore
the Chorus data of Releases below R3.0 but perform manually a complete netadmin.

6. OPERATIONS TO BE CARRIED OUT IN LABORATORY BEFORE

STARTING THE MIGRATION
Preparing the migration in the laboratory has the advantage of limiting the intervention time and
disturbances to site operation.
CAUTION
It is not possible to migrate a database from a Release below R1.5 to R8.0. As a result, any site
which starts from a Release below r1.5 must go via an intermediate database translation, to a
Release between R1.5 and R5.0.1.Ux.

6.1. Prior deletion of the "phase out" applications and hardware

The "phase out" applications and hardware can not be deleted on the database in R8.0. They
therefore need to be deleted on the current version of the site. This operation must be carried out on
the model in lab.
Required means
− A back-up of the database of the site to be migrated.
− A 4400 ACT.
− A CPU installed with a version equivalent to or greater than that of the site on which the "phase
out" applications and hardware will be deleted.

TC0778 12 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

6.2. Replacement of applications and hardware specific to each scenario of

migration

6.2.1. Scenario 1: Migration of "ISO" type

6.2.1.1. Communication Servers

Modify the type of CPU if this has changed.

REMINDER
You must set the appropriate type of CPU otherwise a initialization problem of DECT
or INTOF couplers can occurs (for instance when changing from CPU3 to CPU6).

6.2.1.2. SPB daughter board

It has been possible to delete and replace the SPB board with V120 accesses on the site before the
migration, and before backing up the database.
If replacing SPB with a V24-IP, the tests can be carried out in the laboratory.

6.2.2. Scenario 2: Migration of "Appliance Server" type

6.2.2.1. Communication Servers

No modification is required since the translation of the database removes the CPU and IO2.

6.2.2.2. SPB daughter board

− Note and delete the data applications connected to SPB and IO2 since the SPB boards and the
IO2s are deleted during the translations. These applications will be created later on V24-IP.
− Removing the IO2, IO2N and OBCA
The functionalities not migrated following the deletion of the IO2, IO2N and OBCA, such as links
on B channels, links via modem, signaling back-up via ISDN, X25 on B channel, must be deleted
if this has not already been done on the site before starting the migration procedure, in other
words before backing up the database.
− Replacement of a CPU6 by an Appliance Server
Delete the voice guides and music on hold on the CPU6.
Delete the users’ 4615 voice mail boxes, then delete the 4615 voice mail.

Ed. 04 / 27 July 2007 13 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

6.3. Replacement of applications and hardware common to both scenarios of

migration

6.3.1. OmniMessage
− Deletion of the 4630 voice mail.
Delete the users’ 4630 voice mail boxes, then delete the 4630 voice mail.
− Migration of the 4635H and 4635H-1 voice mails to 4635H-2.
There is no deletion involved in this operation.

6.3.2. OmniTouch Contact Center

The migration of the ACD-V1 must be prepared in the laboratory.
It is compulsory to delete the ACD-V1 objects before carrying out database translations, as it will no
longer be possible to delete them in R8.0.
Refer to the technical communication TC0487 ACD-V1 Migration to CCDistribution.

6.3.3. 2600, 4600, 5400 set equipment

− The migration of the racks and boards must be prepared in the laboratory.
− The users will be retain after translating into R8.0 but without equipment (255-255-255).

6.3.4. 4300 S/M/L set equipment

− The migration of the racks and boards must be prepared in the laboratory, as it is not possible to
delete them in R8.0.
− Unassign the users and delete the racks and the circuits that are not migrated before carrying out
translations.

6.4. Moving the shelves 18 and 19

The shelves already created in position 18 and 19 must be moved before the translation. If this is not
done, they will not restart. In fact, there is no automatic translation of shelves created in these 2
positions as in migration with Appliance Server. The change can be carried out on site before the
migration. Be careful in the event of remote shelf over IP (Remote IP), do not forget to number les
INTIP boards (using the jumpers on the boards).

6.5. Preparing the applications and hardware

6.5.1. Required means

− A back-up of the database on which the "phase out" applications and hardware have been
deleted.
− A 4400 ACT.
− Scenario 1: Migration of "ISO" type.

TC0778 14 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

A hard disk with a minimum of 6 GB if the site CPU(s) do not need to be changed for the
migration or a CPU6 Step2/CPU7 if it is intended to replace the site CPU.
− Scenario 2: Migration of "Appliance Server" type
Appliance Servers and INTIP2 of client.
− The R8.0 OPS files generated by Actis. There are four or five of these files:
• <offer_id>.zip
• <offer_id>.swk
• <offer_id>.hw
• hardware.mao
• <offer_id>.sw4760 (if 4760 present on the site)
The hardware generated by Actis can be prepared in the laboratory.

6.5.2. Additional management specific to each scenario of migration

6.5.2.1. Scenario 1: Migration of "ISO" type

When the site CPUs no longer comply, Actis orders a CPU6 or CPU7 from the manufacturer. These
CPUs can be used for preparing the migration. The CPUs which come from a factory all have a
CPU_ID flashed from the start.
If the site CPUs comply, the hardware keys can be retained.
In this case, preparation for the migration should be carried out on a CPU with a laboratory
equivalent to the one on the site, the disk for which will be implanted later on the client’s CPU.

6.5.2.1.1. Communication Servers

− Install the R8.0 software on the CPU (1).
− Load the site database (1).
− Load the site Chorus data (1 & 2).
− Do not start the telephone (1).
− Install the OPS files (1).

The procedure for installing OPS files has changed as of R5.0 Lx compared to
previous releases.
It puts together the following steps: RUNMAO, translation of the database and
installation of the OPS files.

(1) Follow the technical communication TC0943 Installation procedure for version G1.302.5 –
Release 8.0.
(2) Do not restore the Chorus data if you come from a Release below R3.0.

Ed. 04 / 27 July 2007 15 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

6.5.2.1.2. LIOe / TSC-LIOe

LIOe and TSC-LIOe boards are no longer supported; refer to paragraph 4.1.1 .
The management of these boards must be removed and replaced by a management of INTIP
boards.
Configure the INTIP MAC addresses with the management.

6.5.2.1.3. INT1/INT2
INT1/INT2 boards are no more supported; refer to the paragraph 4.1.2. The management of these
boards must be removed and changed to INTOF board management.

6.5.2.1.4. OmniMessage
− Replacing the 4630 voice mail by a 4635J voice mail.
The 4635J voice mail can be prepared in the laboratory, once the hardware is received, but
since it is not possible to migrate announcements and messages between the two products, an
agreement needs to be reached with the client for freezing the voice service on the site before the
migration to R8.0, in order to no longer authorize message drops. This is a replacement and not
a migration.
− Migration of the 4635H and 4635H-1 voice mail to the 4635H-2 voice mail.
This migration does not need new locks. It can be carried out on the site before migration to
R8.0. This depends on the compatibility of the VPM35s with the site version.
• If there is compatibility, carrying out this operation before the migration will avoid the
cumulation of operations on the day of the switchover to R8.0.
• If there is no compatibility between the VPM35 and the site version, a part of the migration
can be carried out in the laboratory once the VPM35 board is received. The transferring of
announcements and messages is possible in the laboratory, if the client accepts the freezing
of the voice service for a defined period. If interruption of the service is not possible, the
announcements and messages must be transferred during the migration on the site.
Refer to the technical communications:
TC0155 Compatibility of Alcatel 4635 with OmniPCX 4400 backplanes (Reminder of restrictions)
TC0259 Migration procedures
TC0934 Installation procedure for version 5.3.1

6.5.2.1.5. OmniVista
Migration of 4715, 4730, 4740 and 4755 applications to the OmniVista 4760 Release 4.2
application.
This migration can be carried out on the site, once the hardware is received, as long as it is carried
out in the 21 days preceding the switchover to R8.0.
This is advised in order to avoid cumulating operations on the day of the switchover to R8.0. For
more information regarding the OmniVista 4760/OmniPCX Enterprise release compatibility, refer to
the technical communication TC0943 Installation procedure for version G1.302.5 – Release 8.0.

TC0778 16 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

6.5.2.1.6. OmniTouch Contact Center

The ACD-V1 groups migrate to CCD.
The supervisors migrate to CCS.
Refer to the technical communication TC0487 ACD-V1 Migration to CCDistribution.

6.5.2.1.7. 2600, 4600, 5400 set equipment

The 2600, 4600 and 5400 analog equipment migrates to eZ32.
The 2600, 4600 and 5400 digital equipment migrates to eUA32.
− Create the 4400 ACTs and the eZ32 and eUA32 circuits.
− Assign the analog and digital users.
− Once the hardware is received, it is possible to start installing it on site.

6.5.2.1.8. 4300 S/M/L set equipment

The 4300 analog equipment migrates to eZ32.
The 4300 digital equipment migrates to eUA32.
− Create the 4400 ACTs and the eZ32 and eUA32 circuits.
− Assign the analog and digital users that the equipment was removed by the R8.0 translation.
− Once the hardware is received, it is possible to start installing it on site.

6.5.2.1.9. SPB daughter board

The technician should ensure the presence of the replacement hardware.
− The V24 ports on SPB are replaced by TA V120 accesses via IO2 or by accesses via V24-IP
modules.
− Create the V120 accesses for the applications previously connected on SPB.
− If replacing SPB with a V24-IP, the tests can be carried out in the laboratory.
Note
The SPB board can be deleted and replaced with V120 accesses on the site before the migration, and
before backing up the database.

6.5.2.2. Scenario 2: Migration of "Appliance Server" type

6.5.2.2.1. Communication Servers

− Install the R8.0 software on the Appliance Server (1).
− Load the site database (1).
− Load the site Chorus data (1 & 2).
− Do not start the telephone (1).
− Install the OPS files (1).

Ed. 04 / 27 July 2007 17 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

The procedure for installing OPS files has changed as of R5.0 Lx compared to
previous releases.
It puts together the following steps: RUNMAO, translation of the database and
installation of the OPS files.

(1) Follow the technical communication TC0943 Installation procedure for version G1.302.5 –
Release 8.0.
(2) Do not restore the Chorus data if you come from a Release below R3.0.

6.5.2.2.2. Replacing the CPU6 by an Appliance Server

− Create the GPA2 coupler.
− Create the voice guides on GPA2.
− Create the music on hold on a Z equipment.
− Create a 4635 voice mail and assign the voice mail boxes to the users.
− Create the DECT8 coupler.
CAUTION
If the site has DECT2 or DECT4 couplers, they are incompatible with the DECT8 coupler and must
be replaced by DECT8 couplers.

6.5.2.2.3. Removing the IO2, IO2N and OBCA

The functionalities not migrated following the deletion of the IO2, IO2N and OBCA, such as links on
B channels, links via modem, signaling back-up via ISDN, X25 on B channel, have already been
replaced on the site before starting the migration procedure, in other words before backing up the
database.

6.5.2.2.4. Level 3 ACTs

Delete the couplers connecting the level 3 ACTs to the level 2 ACTs, and replace them with INTIPB
couplers equipped with compressor boards.
CAUTION
Compressors are required at the exchange to ensure audio links with this ACT-IP. They are planned
by Actis.

6.5.2.3. Modifications linked to the installation of the Appliance Servers

It is advisable to test the Appliances Servers and INTIPB sets in the laboratory.
Operating mode
− Create the INTIP2 couplers in INTIPB or IOIP mode in position 6, 20 (or 10) of the old ACT0
which has become ACTx, (check the mode to configure in the Actis file).
Note
The CPUs and IO2s have been deleted during the translation. The INTIPBs and IOIPs both
configure themselves on an INTIP2 coupler.
− Configure the MAC addresses of the INTIP2s through the management.
− Configure the ACTx (old ACT0) as reference Media Gateway.

TC0778 18 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

− Configure the switches giving the position of the ACTx on the INTIP2 couplers.
− Configure the IP data of the INTIP2 couplers (static addressing mode), using a VT100 terminal.
CAUTION
The cable for connecting the terminal to the INTIP2 couplers is different to the cable of the INTIPs. It
is identical to the one for the GD boards, 3EH 75003 AAAA.
Note
In IOIP mode, the INTIP2 couplers can not support a compressor board.

7. SUMMARY FLOW CHART

Ed. 04 / 27 July 2007 19 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

Migration OmniPCX 4400 to OmniPCX Enterprise Release 8.0

Before starting, take stock of:

•. the applications and hardware to be changed (Installation procedure for R8.0 § 5)
•. the installation compatibility in network (Installation procedure for R8.0 § 6)
•. compatibilities (Installation procedure for R8.0 § 7)

yes no
Can the functionalities
deleted in R8.0 be evolved in
the current version?

Back up the current database. This back-up n°1 will be your reference (saveref1)
in the event of a changeback

Replace everything that can be replaced in your current version (without adding new licenses)
- 47x x --> 4760 (TCV036 Operation possible 21 days without official license)
- 4635 --> 4635 H2 (TC0155, TC0259 and TC0934)
- LIOE/TSCLIOE --> INTIP
- OBCA - -> IO2N in case of CPU7
- IO2 - -> IO2N in case of CPU7
- INT1/INT2 - -> INTOF/INTOF2
- Scenario 1: SPB --> IO2, delete the ports used and recreate them on IO2
- Scenario 2: Delete the IO2, IO2N and OBCA boards

Warn the client of the constraints imposed by the change of version:

. Freezing of the management (for a period defined with the client),
. Risk, following your evolution, of losing the messages and announcements in the case of a change of voice mail
(TC0155 - TC0259 - TC0298 -TC0934)
. Replacement of the ACDV1 by CCD (TC0487) on installation of the R8.0

yes Do you have no

other
functionalities
to replace?

no
Is the version of
the site
< R1.5.3

yes
Back up the current database. This back-up n°2 will be your
reference (saveref2) in the event of a changeback

Translate the data in a

Release compatible with 8.0
The following operations must be carried out only in the (R1.5.3 to R5.0.1Ux)
laboratory

Go to B Go to A

TC0778 20 Ed. 04 / 27 July 2007

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

no Is the version of yes

the site
< R1.5.3

Translate the data in a

Release compatible with
R8.0 (R1.5.3 to R5.0.1Ux)

Restore your database savref2 on a CPU loaded with Back up the current database (§ 9.4). This back-up
the same version as the site or a Release lower than or n°3 (saveref3) will be used to carry out translations in
equal to R5.0.1Ux R8.0

Management to be carried out:

2600/5400 shelf: Unassign all the equipment used and delete the 2600/5400 boards and shelves.
ACDV1: Delete the ACDV1
4630: Delete the 4630 (see TC0298)

Back-up the current database (§ 9.4). This back-up n°4

(saveref4) will be used to carry out translations in R8.0

Your management is now ready to be translated to R8.0

You should now have the Actis files for R8.0

A lock request should first have been made by Actis and you
therefore now have four or five files (depending on whether or
not 4760 is present)

Install R8.0, if possible, on a CPU which will be placed on site

Once the system is loaded, install the database (saveref4)

then
load the OPS files (via swinst --> § 12.1)
Translation is carried out automatically after loading the OPS files

Manage the missing functionalities:

. eUA32 and eZ32 equipment replacing the 2600, 4300 and 5400 equipment
. CCD
. Alcatel 4635
. Scenario 1: Manage the correct type of CPU
. Scenario 2: Change the previous access on SPB to V24-IP devices
Change the previous level 3 ACT behind INTOF to ACT behind INTIP

Back up the current database (§ 9.4). This back-up n°5 (saveref5) will be the one
with the new R8.0 management

Your CPU is now loaded in R8.0 with the new functionalities.

It is ready to be placed on site.

END

Ed. 04 / 27 July 2007 21 TC0778

 OmniPCX Enterprise
MIGRATION OmniPCX 4400 TO
OmniPCX Enterprise

8. INTERWORKING IN HETEROGENEOUS NETWORK

Refer to sections 5, 6 and 7 of the technical communication TC0943 Installation procedure for
version G1.302.5 – Release 8.0.

9. SWITCHOVER OF THE INSTALLATION IN R8.0 ON SITE

9.1. Voice mail in network

Modify the type of voice mail box of the users of other nodes if the centralized voice mail was a
4630.

9.2. System synchronization

CAUTION
An Omni_PCX 4400 which migrates to Omni_PCX Enterprise with Appliance Server is from
now on subject to the domain synchronization rules.
Modify the synchronization priorities of the digital accesses.
See technical communication TC0779 Synchronization of a system after migration to OmniPCX
Enterprise with Appliance Server.
The synchronization rules are explained in the "PABX synchronization" section of the system
documentation.

TC0778 22 Ed. 04 / 27 July 2007