OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
J1.410.34.c – RELEASE 10.0
Ed. 02 / 22 June 2011 17 TC1449
1 The delivery of a new CPU6 Bios requires to reboot the PABX after installing the dynamic patch.
2 You should connect to swinst to complete its installation.
3 CPU5 Step3 is no longer supported from Release 8.0.
4 SM Modules Thales: this is the reference seen in mgr.
5. BEFORE STARTING
5.1 Applications, functionalities not supported by Release 10.0
REMINDER
As of Release 5.1, some applications and functionalities of Release 5.0 Ux are no more supported,
and will have to be replaced by others.
The table below shows all the applications and functionalities which are no more provided by
OmniPCX Enterprise R10.0, whatever hardware used.
Migration batches exist including a specific rate, which have been defined and taken into account
automatically by Actis R16.1.
Family Type of application Migration to
Compulsory
deletion/
modification
before migrating
to R10.0
Documentation
OmniVista 4760i (3) mgr or OmniVista 4760
Not applicable System Documentation
4715
4730
4740
4740 PTP
OmniVista 4760 R5.2 No TC1479
4730i mgr or OmniVista 4760
Not applicable System Documentation
4755 OmniVista 4760 R5.2
4000 Directory Server 4760 LDAP Server
47xx
Directory PC Client for
4755/4000
4760 Directory Client
No
TCV010
TCV017
TC1479
4630
4635J (default) or
4635H2
Yes TC0298
4620 or VPS35 (1) 4635 VPM35 or VPU6 Yes No
4635 VPCPU 4635 VPM35/VPU6 Yes
Voice mail
4635 VPCPU-1 4635 VPM35/VPU6 Yes
TC0155, TC0259,
TC1373
4300 Manage the equipment in
the new ACT
Yes No
2600, 4600 Delete all equipment and
manage it in a new ACT
Yes No
ACT migration
5400 Delete all equipment and
manage it in a new ACT
Yes No
ACD-V1 CCD R7.1
4735 & 4736 CCS
Yes TC0487
ACD-V1
4961 first party TAPI
middleware
No migration – Not
supported
Not applicable No
To Next Page
Loading...
Need help?
General
