Professional Documents
Culture Documents
04
URGENT
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
CONTENTS
2. REFERENCES................................................................................6
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
1.1. Introduction
This document applies for the migration from OmniPCX 4400 to OmniPCX Enterprise which the
release is 8.0.
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
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 .
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.
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:
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.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.
4.2.2.2. RMA
The RMA is deleted and replaced with an RMA in an S type cabinet (rack 1U).
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).
− 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.
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.
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.
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.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.
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.
− 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.
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
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
Go to B Go to A
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
Back up the current database (§ 9.4). This back-up n°5 (saveref5) will be the one
with the new R8.0 management
END