La

Communication Servers Business Unit
Large Enterprise / Product Line Management
ALCATEL-LUCENT OMNIPCX ENTERPRISE

RELEASE 10
APPLICATIONS/TERMINALS CROSS
COMPATIBILITY
Alcatel-Lucent © 1/88 ref: 8ALxxxxxxxxxDRASA ED 00

All rights reserved. Passing on and copying of this document, use and communication
of its contents not permitted without ALCATEL-LUCENT written authorization.
Table of contents
1. Introduction........................................................................................................................ 6
1.1 Purpose of the document........................................................................................... 6

1.2 Improvements and add-ons.......................................................................................6
2. Related documents........................................................................................7
2.1 OmniPCX software phase-out policy..........................................................................7

2.2 Technical documents.................................................................................................. 7
3. How to use this document..............................................................................8
3.1 Which application must be migrated during OmniPCX Software upgrade?................8

3.1.1 Prerequisite.................................................................................................... 8
3.1.2 Elements of methodology...............................................................................9
4. Compliance of application versions & terminals with OmniPCX Enterprise releases

................................................................................................................... 10
4.1 Early Alcatel-Lucent 4400 software releases............................................................10

4.2 Alcatel-Lucent 4400 R3.0......................................................................................... 10
4.3 OmniPCX 4400 R3.2/3.2M........................................................................................ 10
4.4 OmniPCX 4400 R4.1.1..............................................................................................10
4.5 OmniPCX 4400 R4.2.................................................................................................10
4.6 OmniPCX 4400 R5.0 Ux...........................................................................................10
4.7 OmniPCX Enterprise R5.0 lx.....................................................................................10
4.8 OmniPCX Enterprise R5.1.2......................................................................................11
4.9 OmniPCX Enterprise R6.0........................................................................................11
4.10 OmniPCX Enterprise R6.0.1......................................................................................11
4.11 OmniPCX Enterprise R6.1 /6.1.1..............................................................................11
4.15 OmniPCX Enterprise R8.X........................................................................................11
4.18 OmniPCX Enterprise R10.........................................................................................12
4.19 OmniPCX Enterprise / application compatibility tables............................................13
4.19.1 Call handling................................................................................................ 13
4.19.2 OmniMessage............................................................................................... 14
4.19.3 OmniTouch Contact Center suite..................................................................15
4.19.4 OmniTouch cc Premium Edition....................................................................18
4.19.5 Alcatel-Lucent OmniTouch Unified Communication / Instant Communications
Suite............................................................................................................. 19
4.19.6 Alcatel-Lucent OmniTouch My Teamwork......................................................20
4.19.7 Alcatel-Lucent OmniTouch 8670 Automated Message Delivery System (AMDS)
Application................................................................................................... 21
4.19.8 Alcatel-Lucent OmniTouch Fax Server Application........................................22
4.19.9 Alcatel-Lucent OmniTouch 8440 Messaging Services...................................23
4.19.10................................................................................................................ Omni Desktop
..................................................................................................................... 23
4.19.11...........Alcatel-Lucent OmniTouch 8410 Instant Communications Web Services
..................................................................................................................... 24

4.19.12............................................................................................................. OmniVista 4760
..................................................................................................................... 26
4.19.13............................................................................................................. OmniVista 8770
..................................................................................................................... 26
4.19.14............................................. Business integrated Communication Server ( BiCS )
..................................................................................................................... 27
4.19.15............................................................................. Professional Services Applications
..................................................................................................................... 28
4.19.16................................................................................................................. Miscellaneous
..................................................................................................................... 28
5. OmniPCX Enterprise Hardware compatibility.................................................29
5.1 Crystal Hardware vs Release OmniPCX Enterprise Compatibility.............................29

5.1.1 Legend used in the table..............................................................................29
5.1.2 System Boards............................................................................................. 29
5.1.3 Auxiliary Coupler Boards..............................................................................30
5.1.4 Extension boards.......................................................................................... 30
5.1.5 Trunk Interface boards.................................................................................31
5.1.6 DECT boards................................................................................................. 31
5.1.7 Voice Mail 4635............................................................................................ 32
5.1.8 Link Interface Optimizer Boards...................................................................32
5.1.9 Miscellaneous Boards...................................................................................33
5.1.10 Voice Hub and Wall Mounted cabinets..........................................................34
5.2 Common Hardware/OmniPCX Enterprise compatibilities..........................................35
5.2.2 System boards.............................................................................................. 35
5.2.3 Extension boards.......................................................................................... 36
5.2.4 Trunk Interface boards.................................................................................37
5.2.5 Mixed boards................................................................................................ 38
5.2.6 External battery racks..................................................................................38
5.2.7 Compatibility between Appliance Server and Software Releases.................40
5.2.8 Compatibility between Blade Server and Software Releases........................41
5.2.9 Feature loss on IO2/IO2N/ OBCA loss............................................................41
6. Internal compatibility issues.........................................................................43
6.1 Compression resource compatibility issues..............................................................43

6.2 Voice over IP compatibility issues when implementing new services.......................43
6.2.1 Framing 20ms for voice over IP....................................................................43
6.2.2 Remote LIO must be upgraded to ACT- IP.....................................................43
6.2.3 H323 services introduced since OmniPCX 4400 R4.2...................................43
6.2.4 Voice over IP and direct RTP switching with OmniPCX Enterprise.................44
6.2.5 Direct RTP with H323 equipments................................................................45
6.3 compatibility issues when USING SIP-TLS SIP Gateway............................................45
6.4 CONDITIONS FOR INSTALLATION IN NETWORK.........................................................45
6.5 Installation of Release R9.1/R10.0 in network with Releases 5.1.x, 6.x, 7.x.............47
6.6 Installation of Release 9.1/10.0 in network Release 8.0, 8.0.1, 9.0..........................48
6.7 Audit/Broadcast....................................................................................................... 48
6.8 Compatibility of external applications......................................................................48
6.9 COMPATIBILITIES...................................................................................................... 49
6.9.1 Reminder on boards supporting the Transit function and the direct RTP......49
6.9.2 Delay (in one direction) introduced by IP gateways......................................49
6.9.3 Delay (in one direction) from an IP Phone towards a set behind ACT or eMG50
6.9.4 ABC-F2 compatibility depending on the hardware and the type of configuration
used (with or without compressed voice).....................................................50
6.9.5 USB Key compatibility for CPU7-2, Appliance Server and Blade Server........52
6.9.6 Common hardware compatibility..................................................................52
6.9.7 IOIP hardware compatibility..........................................................................52

7. Terminal compatibility..................................................................................53
7.1 WIRED TERMINAL compatibility...............................................................................53

7.1.2 UA 2G & Reflexes Terminals.........................................................................53
7.1.3 Dedicated Attendant Terminals....................................................................53
7.1.4 Options and interfaces for Reflexes/e-Reflexes............................................54
7.1.5 Options for 8 & 9 series and Reflexe Terminals............................................55
7.1.6 e-reflexes terminals......................................................................................55
7.1.7 e-reflexes and Alcatel-Lucent 8 and 9 series................................................56
7.1.8 MyICTouch 8081........................................................................................... 56
7.1.9 OmniTouch 4135.......................................................................................... 57
7.1.10 DECT System and Terminals.........................................................................57
7.1.11 Wireless LAN terminal..................................................................................58
8. Alcatel-Lucent enterprise/4400 release upgrades: impact on the 4400 system

components and applications.......................................................................58
9. OmniPCX applications..................................................................................58
10. Alcatel-Lucent Omnidesktop platform...........................................................59
10.1 Alcatel-Lucent 4058/4059 Hardware and software compatibility.............................59

10.1.1 Windows compatibility..................................................................................59
Minimum PC configuration.......................................................................................60
10.1.2 Migration memo........................................................................................... 60
10.1.3 Related services........................................................................................... 61
10.2 omnitouch unified communicationS / Instant Communications Suite hardware and
software compatibility..............................................................................................61
10.2.1 OmniTouch Unified Communication 3.0 compliant platforms (server side)...61
10.2.2 OmniTouch Unified Communication 4.0 & 4.1 compliant platforms (server side)
..................................................................................................................... 61
10.2.3 OmniTouch Unified Communications 5.0 compliant platforms (server side). 61
10.2.4 OmniTouch Unified Communications 6.0 compliant platforms (server side). 61
10.2.5 OS server compatibility................................................................................61
10.2.6 Mail Servers OS and 46x5 version compatibility...........................................62
10.3 omnitouch My Teamwork hardware and software compatibility...............................63
Compliant platforms (server side)...........................................................................63
10.4 omnitouch Automated Message Delivery System (AMDS) hardware and software
compatibility............................................................................................................ 63
OS server compatibility........................................................................................... 63
10.5 Omnitouch Fax Server..............................................................................................64
Compliant platforms................................................................................................ 64
10.6 Alcatel-Lucent TAPI Premium Server........................................................................64
Windows compatibility (Server)...............................................................................64
10.7 Alcatel-Lucent TSAPI Premium Server......................................................................66
OS compatibility (Server)......................................................................................... 66
10.8 OmniTouch 8410 Instant Communications Web Services: OS compatibility server
(Server).................................................................................................................... 66
10.9 Omnitouch 8440 Messaging Software.....................................................................67
Compliant platforms................................................................................................ 67
11. Alcatel-Lucent OmniMessage application.......................................................68
11.1 Alcatel-Lucent 4635H hardware and software compatibility....................................68

11.1.1 Boards versus release compatibility.............................................................68
11.1.2 Minimum configuration.................................................................................68
11.1.3 Migration memo........................................................................................... 69
11.1.4 Recommendation and requirement..............................................................69

11.2 Alcatel-Lucent 4635J hardware and software compatibility......................................70
11.2.1 Boards versus release compatibility.............................................................70
11.2.2 Minimum configuration.................................................................................70
11.2.3 Migration...................................................................................................... 70
11.3 Visual Messenger Hardware and software compatibility..........................................71
11.3.1 Server SW compatibility...............................................................................71
11.3.2 Client SW compatibility................................................................................71
11.3.3 Application SW compatibility........................................................................71
11.3.4 Recommended server PC configuration........................................................71
11.3.5 Recommended client PC configuration.........................................................71
12. Omnivista 4760 Hardware and software compatibilities.................................72
12.1 OmniVista 4760 R4.0/R4.1.......................................................................................72

12.2 OmniVista 4760 R4.2............................................................................................... 73
12.3 OmniVista 4760 R5.0 R5.1 R5.1.1............................................................................74
12.4 OmniVista 4760 R5.2............................................................................................... 75
13. Omnivista 8770 Hardware and software compatibilities.................................76
13.1 OmniVista 8770 R1.0............................................................................................... 76
14. Business integrated Communication Server ( BiCS ).......................................77
14.1 Business integrated Communication Server R1.0....................................................77

14.1.1 Server configuration requirement................................................................77
14.1.2 Software compatibilities...............................................................................77
14.2 Business integrated Communication Server R2.0 , R2.1, R2.2.................................78
14.2.1 Server configuration compatibility R2.0, R2.1, R2.2.....................................78
14.2.2 Additional server compatibility from R2.1.1, R2.2........................................78
14.2.3 Software compatibilities R2.0.......................................................................79
14.2.4 Software compatibilities R2.0.1....................................................................79
15. Omnitouch Contact center suite Operating System and hardware compatibilities
................................................................................................................... 82
15.1 OPerating System compatibilies..............................................................................82

15.1.1 OmniTouch Contact Center Suite..................................................................82
15.1.2 OmniTouch Contact Center Premium Edition................................................82
15.2 Hardware compatibility: minimum PC requirement..................................................82
15.2.1 CCS Supervision........................................................................................... 82
15.2.2 CCS Server................................................................................................... 83
15.2.3 CCWallboard................................................................................................. 83
15.2.4 CCA PC client (agent) requirements.............................................................83
15.2.5 A4400 Call Center agent (CCA) server..........................................................83
15.2.6 Ccweb CCemail powered by genesys...........................................................83
15.2.7 CCemail PC platform requirement................................................................84
15.2.8 Database requirement..................................................................................84
15.2.9 Ccoutbound Platform requirements..............................................................84
16. APPENDIX.................................................................................................... 85
16.1 Actual OmniPCX Enterprise released software releases...........................................85

1. INTRODUCTION
1.1 PURPOSE OF THE DOCUMENT

This document covers compatibility between OmniPCX Enterprise software releases and
Alcatel-Lucent Enterprise applications.
The goal of this document is to provide relevant information regarding compatibility of the
Omni product to marketing, sales and pre-sales people, and project managers or
leaders of Alcatel-Lucent Business Partners in order to manage evolution of
customer configurations.
This document does not replace ACTIS regular configuration tools which must be used
to define hardware and software changes when migrating former software releases of
OmniPCX Enterprise, R6.1, R6.2, R7.0, R7.1, R8.0, R8.0.1, R9.0, R9.1and R10.0.
This document does not replace feature lists or product descriptions for the various Omni
Products mentioned above.
This document is limited to:
Released application (Technical Releases).
Released OmniPCX Enterprise Releases.
Alcatel-Lucent Enterprise strongly recommends that customers upgrade to the
latest software release (OmniPCX Enterprise R10.0)
Regarding applications, Alcatel-Lucent recommends upgrading the applications
to the last release, in order to benefit from the latest improvements. This
document will be revised at each new OmniPCX Enterprise software version (Technical
Release)
1.2 IMPROVEMENTS AND ADD-ONS

Phase-out policy
Information in this document conforms to the phase-out policy defined by eND CSBU/
Product Marketing in July 2000.
Information given in this documentation is provided only for products that are still
supported as of December 2009. Maintaining customer configurations that include
outdated products is not feasible, as they no longer have any support from Alcatel-Lucent
Enterprise.

2. RELATED DOCUMENTS
2.1 OMNIPCX SOFTWARE PHASE-OUT POLICY

Product Communication Note “OmniPCX 4400 Life Cycle Policy” ref:
8AL020033139TCASA.
Archive document cross compatibility for releases prior to R6.2 ref :
8AL010980098ZZASA
Cross compatibility document for releases R6.2 to R7.1 ref: 8AL020033175TCARA
Cross compatibility document for release R8.0 ref: 8AL020043263DRASA
Cross compatibility document for release R9.0 ref: 8AL020033508DRASA
Eflash EF-389-1220 release policy information.
2.2 TECHNICAL DOCUMENTS

Information in these documents is based on the following documents:
Releases Compatibility PABX/Applications B Rynders 3BA 29000 1878 XZZA ed. 55.
This document is obsolete for R6.0 and next releases.
OmniTouch Suite Software Compatibility ed. 09 Source: Alcatel-Lucent eND-TSS.
Communication technique : OmniPCX 4400/Enterprise Compatibilités & Evolutions
ed.02 (TCO 418).
OmniPCX /4400/Enterprise compatibilités DECT (TCO 274).
Procédure de mise en service de la version f3.301.10 Release 6.2 (TCO 711 ed. 1)
Technical release note for VoWLAN Release 3.0 offer (TCO940)
Technical release note for OmniPCX Enterprise Release 7.0 – Version F4.401.12
(TC0775)
Installation procedure for version f4.401.13 Release 7.0 (TC0 776)
Technical release note for VoWLAN Release 2.1 offer (TCO774 ed02)
Technical release note for OmniPCX Enterprise Release 7.1 – Version F5.401.7 (TC0837)
Installation procedure for Version F5.401.21f Release 7.1 (TC0968)
Technical Release Note for OmniPCX Enterprise Release 8.0 - Version G1.302.5
(TC0942)
Installation procedure for Version G1.302.6e Release 8.0 (TC0987)
Technical release note for OmniPCX Enterprise Release 8.0.1 - Version G1.503.9
(TC1017)
Installation procedure for Version G1.503.9 Release 8.0.1 (TC1018)
Technical Release Note for OmniPCX Enterprise Release 9.0 – Version H1.301.24
(TC1088)
Installation procedure for Version H1.301.24 Release 9.0 (TC1089)
Installation procedure for Version H1.301.31.d Release 9.0 (TC1205)
Installation procedure for Version H1.301.34 Release 9.0 (TC1222)
Technical Release Note for OmniPCX Enterprise Release 9.1 – Version I1.605.12
(TC1243)
Installation procedure for Version I1.605.12 - Release 9.1 (TC1244)
Technical Release Note for OmniPCX Enterprise Release 10.0 – Version J1.410.27.c
(TC1448)
Installation procedure for Version Version J1.410.27.c Release 10.0(TC1449)
Refer to the Technical Release Document edited by Alcatel-Lucent Enterprise/CSBU/TSS for

released applications and OmniPCX software.
3. HOW TO USE THIS DOCUMENT
Contents of document:
This document summarizes information used to prepare a customer for an OmniPCX
Enterprise/4400 software upgrade.
Determine the target OmniPCX software release you want to provide to your customer.
For each OmniPCX software release, you will find:
Hardware compatibility versus OmniPCX Enterprise release.
The minimum version of application which runs with the targeted release.
Information about application environments (operating system, minimum PC
configuration, etc.) and the way to upgrade such an environment.
This document is a Business Partner document and should not be given directly to end-
users.
3.1 WHICH APPLICATION MUST BE MIGRATED DURING OMNIPCX

SOFTWARE UPGRADE?
This document will help you to check the Omni application and related hardware platform,
which must be upgraded when upgrading OmniPCX Enterprise/4400 software.
3.1.1 Prerequisite
Before quoting any “Omni” software upgrade, you must first make an on-site check of the
installed configuration.
All upgrade processes require the following information:
OmniPCX 4400/Enterprise configuration, i.e. MAO, .SW… file of the customer
installed configuration in order to use them with ACTIS configuration tool.
Existing Alcatel-Lucent 4400 Crystal hardware/Common hardware, such as CPU
type, installed board, …
Carefully check the 4635 Voice Mail system, if applicable.
For all existing Alcatel-Lucent applications, major release number (such as R10.0)
and minor suffix number (ftxx).
For non-Alcatel-Lucent applications, you may need to contact the software editor in
order to define the operation to be carried out to allow their application to work
properly with the new OmniPCX Enterprise. Alcatel-Lucent commitment for
interoperability with non-Alcatel-Lucent applications is limited to AAPP
registered application (see: http://www.Alcatel-Lucent.com/partners/)
Remember that the Alcatel-Lucent “Professional Services” organization is able to
provide a “proof of concept” service which tests the target configurations and
appropriate acceptance tests with your end user customer. For more information
and associated quotation, please contact :
Professional.services@Alcatel-Lucent.fr

3.1.2 Elements of methodology
Verify:
If the existing application release works with the targeted OmniPCX Enterprise
release.
The phase-out status of every component of the installed configuration.
The impact on the end-user of this upgrade in order to define a training plan
according to your service portfolio.
Provide a quotation for:
Upgrade with the last released ACTIS with use of collected .MAO, .SW, … file.
Application upgrade according to information provided in this document.
Manpower needed to process the various application upgrades. You may need to
discuss this issue with your field operation organization.

4. COMPLIANCE OF APPLICATION VERSIONS & TERMINALS
WITH OMNIPCX ENTERPRISE RELEASES
For more details about release cycle policy, see the latest edition of the document “Eflash
EF-389-1220 release policy information”, ref. 8AL020033139TCASA
4.1 EARLY ALCATEL-LUCENT 4400 SOFTWARE RELEASES

Software Release 1.3.x, 1.4.1 (A9series), 1.5.x and 2.0 software releases are being phased
out.
Do not upgrade existing configurations to this earlier software release. Only limited add-
ons are allowed.
Compatibility data will no longer be maintained by eND/CSBU for these versions.
4.2 ALCATEL-LUCENT 4400 R3.0

This version is at end of life as of December 2002
No customer configurations should be upgraded to this release.
This document does not include any information regarding this release.
4.3 OMNIPCX 4400 R3.2/3.2M

This version is at end of life as of March 2004
4.4 OMNIPCX 4400 R4.1.1

This version is at end of life as of November 2004
4.5 OMNIPCX 4400 R4.2

This version is at end of life as of June 2004
4.6 OMNIPCX 4400 R5.0 UX

This version is at end of life as of September 2005
4.7 OMNIPCX ENTERPRISE R5.0 LX

This version is at end of life as of December 2004

4.8 OMNIPCX ENTERPRISE R5.1.2
This version is at end of life since March 2007
4.9 OMNIPCX ENTERPRISE R6.0

This version is at end of life since September 2007
4.10 OMNIPCX ENTERPRISE R6.0.1

This version is at end of life since September 2007
4.11 OMNIPCX ENTERPRISE R6.1 /6.1.1

This version is at end of life since May 2008

This version is a minor version regarding the OmniPCX Enterprise 6.1/6.1.1
This release is at end of life since October 2008

This version is a major version regarding the OmniPCX Enterprise 6.2
This release is at end of life since April 2009
Its support version is R7.1

This version is a minor version regarding the OmniPCX Enterprise 7.0 and is also a
maintenance version for OmniPCX Enterprise R7.0
This release is at end of life since November 2009
4.15 OMNIPCX ENTERPRISE R8.X

The R8.0 version is a major version regarding the OmniPCX Enterprise R7.1.
The R8.0.1 version is the maintenance version of the OmniPCX Enterprise R8.0.
This release will be in phased out in October 2011

This version is a major version regarding the OmniPCX Enterprise R8.0

This release will be in phase out in November 2011

This version is a minor version regarding the OmniPCX Enterprise R9.0
This release will be in phase out in January 2012
4.18 OMNIPCX ENTERPRISE R10

This version is a major version regarding the OmniPCX Enterprise R9.1
This release will be in phase out in July 2013
Refer to release policy document for more information

4.19 OMNIPCX ENTERPRISE / APPLICATION COMPATIBILITY TABLES
The following chart provides the minimum required application release for each OmniPCX
software release. You can check if you need to upgrade this application when you
upgrade the OmniPCX release.
Minimum application release assumes that when migrating an OmniPCX Enterprise r “x”
to OmniPCX Enterprise r “y”, services available on the target configuration will be
at the level that was available before migration. Careful analysis must be
performed when supplementary services are required on target configurations. Such
requirements may imply application migration to a more recent release.
Note that it is strongly recommended to upgrade applications to the latest software

release. By doing so, customers benefit from feature and application improvements. This
information conforms with the phase-out policy.
4.19.1Call handling
Call Handling
OmniPC OmniPC OmniPC OmniPC OmniPC
X X X X X OmniPCX
Enterpri Enterpri Enterpri Enterpri OmniPCX Enterpri OmniPCX Enterpris
se se se se Enterprise se Enterprise e
R6.1 / R8.0/R8.0
6.1.1 R6.2 R7.0 R7.1 1 R9.0 R9.1 R10.0
4058
(W95/WN
T) R4.016.1 R4.016.1
MigrationR4.016.1 R4.016.3 R4.016.3 R4.016.5 R4.016.5 2 R4.016.12 2
Not Not Not Not
supporte supporte Not supporte Not supporte
4059 MGT R4.016.1 R4.016.3 d d supported d supported d
4059
MAC/BLF
and
Migration R4.016.1 R4.016.3 R4.016.3 R4.016.5 R5.0.4 R5.1.1 R5.1.5 R5.2.4
Not Not Not Not
supporte supporte supporte supporte
4059 IP d d d d R5.0.4 R5.1.1 R5.1.5 R5.2.4

4.19.2OmniMessage
OmniMessage
OmniPCX OmniPCX OmniPCX OmniPCX
OmniPCX Enterpris Enterpris Enterpris OmniPCX Enterpris OmniPCX OmniPCX
Enterprise e e e Enterprise e Enterprise Enterprise
R6.1/R6.1. R8.0/R8.0.
1 R6.2 R7.0 R7.1 1 R9.0 R9.1 R10.0
Not Not Not Not
supporte supporte supporte Not supporte Not Not
4615 3.0.24 d d d supported d supported supported
4635H-2 Not
(VPM 35) Not supporte Not Not
R5.1 R5.1.5 R5.1.5 R5.1.5 R5.1.5 supported d supported supported
R5.2.2 and
should be
updated to
R5.2.6 to
allow blind
transfer
4635H-2 and spatial
R5.2.10
(VPM 35) redundanc R5.4.4
R5.2 y R5.2.6 (note 2) R5.3.0 R5.3.0 (note3) R5.4.6 R5.5.1
Replaced
by 4635J – Not Not Not Not
4635J – (VPU5-8 supporte supporte supporte Not supporte Not Not
(VPS 35) ports) d d d supported d supported supported
R5.2.2 and
should be
updated to
R5.2.6 to
allow blind
transfer
4635J – and spatial
R5.2.10
(VPU5-16 redundanc R5.4.4
ports) y R5.2.6 (note 2) R5.3.0 R5.3.0 (note3) R5.4.6 R5.5.1
4635J –
(VPU6-16 R5.4.4
ports) R5.3.0 R5.3.0 R5.3.0 R5.3.0 R5.3.0 (note3) R5.4.6 R5.5.1
Visual
Messenger
for 4635
R2 R2.015 R2.015 Note 1 Note 1 Note 1 Note 1 Note 1 Note 1
Note 1 : End of life has been pronounced by April 2006 – No more technical support is provided.
The alternative solution is the OmniTouch Unified Communication “My Messaging”
Note 2 : The Release R7.0 is compatible with the version R5.2.10 of 4635H2 or 4635J (VPU5).
Restriction : the IMAP4 function must be used with the version R5.2.6 of 4635’s
Note 3: The next release R5.4.5 release will be available by end of 2008

4.19.3OmniTouch Contact Center suite
Extract from Alcatel-Lucent Omnitouch Contact Center Standard Edition Suite. Software
compatibility matrix:
 Compatible
Blank (empty) : Not compatible
NR : not relevant
(1) Standard Edition / 32 bits edition

(2) Only for Slave server / Easy server
(3) Version g13026+ minimum
(4) Nomadic multimedia mode cannot be applied
(5) - Internet browser security level should be set for each Windows user
- In case of simple sharing Citrix mode (not Isolation environment) CCO SE can be only
used by one user.
(6) - Server side of CCA
Alcatel-Lucent © 15/88 ref: 8AL020033508DRASA

4.19.4OmniTouch cc Premium Edition

4.19.5Alcatel-Lucent OmniTouch Unified Communication / Instant Communications
Suite
OmniTouch Unified Communications

OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX
OmniPCX Enterpris Enterpris Enterpris Enterpris Enterpris Enterpris OmniPCX
Enterprise e e e e e e Enterprise
R8.0/8.0.
R6.1/6.1.1 R6.2 R7.0 R7.1 1 R9.0 R9.1 R10.0
Unified
Communicatio
n R3.0 (1): My
Assistant, My
Messaging and
My Phone Not Not Not Not Not Not
applications R3.0.7 R3.0.7 supported supported supported supported supported supported
Unified
Communicatio
n R3.0 (2): My
Teamwork Not Not Not Not Not Not
application R3.0 R3.0 supported supported supported supported supported supported
Unified
Communicatio
n R4.0 (1): My
Assistant, My
Messaging and
My Phone Not Not Not Not
applications R4.0 R4.0 R4.0(3) R4.0(3) supported supported supported supported
Unified
Communicatio
n R4.0 (2): My
Teamwork Not Not Not Not
application R4.0 R4.0 R4.0(3) R4.0(3) supported supported supported supported
Unified
R4.1 R4.1 R4.1
Communicatio
n R4.1 (1): My
Assistant, My
Messaging and Not Not Not
My Phone compliant compliant compliant Not
applications R4.1 R4.1 R4.1 R4.1 XL XL XL supported
Unified R4.1 R4.1 R4.1
Communicatio Not
n R4.1 (2): My Not Not Not supported
Teamwork compliant compliant compliant
application R4.1 R4.1 R4.1 R4.1 XL XL XL
Unified
Communicatio R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 R5.0/ R5.0/ Not
ns R5.0 (1) R5.0/R5.01 1 1 1 1 R5.01(4) R5.01(4) supported
Unified
Communicatio Not
ns R5.1 (1) - - R5.1 R5.1 R5.1 R5.1 R5.1 supported
OmniTouch
8400 Instant
Communicatio
ns Suite R6.0
(1)(5) - - - - R6.0 R6.0 R6.0 R6.0(6)
OmniTouch
8400 Instant
Communicatio
ns Suite R6.1
(1)(5) - - - - R6.1 R6.1 R6.1 R6.1(6)
OmniTouch
8400 Instant
Communicatio
ns Suite R6.2
(1)(5) R6.2 R6.2 R6.2 R6.2(6)

(1) My Messaging (Unified Messaging model) and My Assistant require an OmniPCX Enterprise Gateway (at
least R6.0.1 – latest release strongly recommended) if a G.723/G.729 codec is used. See also the “PBX
Gateway” section below.
(2) Requires an OmniPCX Enterprise Gateway (at least R6.0.1 – latest release strongly recommended) if
G.723/G.729 codec is used. See also the “PBX Gateway” section below.
(3) OmniPCX enterprise R7.1 & R8.0/8.0.1/9.0/9.1 and OmniTouch UC R4.0 are compliant in the same feature
level as OmniPCX Enterprise R7.0
(4) OmniPCX enterprise R9/R9.1 and OmniTouch UC R5.0 are compliant in the same feature level as OmniPCX
Enterprise R8.0/R8.0.1
(5) Mobility solution is supported from OmniPCX Enterprise R9.0 only
(6) OmniPCX enterprise R10.0 and OmniTouch UC R6.0, R6.1 & R6.2 are compliant in the same feature level
as OmniPCX Enterprise R9.0/R9.1
 Note that some OmniTouch UC features require a dedicated OmniPCX Enterprise release (refer to the
OmniTouch UC Feature List documents).
 For information about phase out status of Alcatel-Lucent OmniTouch Unified Communications services,
please refer to the Alcatel-Lucent OmniPCX Enterprise lifecycle policy (ref. 8AL020033139TCASA).
4.19.5.1 PBX Gateway

The following table provides, for each application included in the Alcatel-Lucent OmniTouch Unified Communication
software suite, the compatibility with the Alcatel- Lucent OmniPCX Enterprise systems available in the field.
Other PBX Other PBX

OmniTouch UC My Assistant, My PBX Front-end
nodes in the nodes in sub-
Messaging and My Phone applications or PBX Gateway
same Network network
My Phone for Omnitouch Unified
Not used R3.2 R3.2
Communication R3.0 R4.0 and R4.1
My Messaging for Omnitouch Unified
R4.2 R3.2
>= R7.1 *
My Assistant for Omnitouch Unified
R5.0 Ux R5.0 Ux
* Refer also to the OmniTouch UC Feature List documents to check applicable restrictions
Two types of link are available when inter-connecting My Teamwork to PBX systems:
 SIP connection, which requires an OmniPCX Enterprise Gateway (software must be at
least Release 7.1) for inter-connecting to:
 Other PBX vendors.
 OmniPCX Enterprise/4400 < Release 6.0.1
 PSTN link, based on AudioCodes cards
 An OmniPCX Enterprise Gateway is not required in such context.

4.19.6Alcatel-Lucent OmniTouch My Teamwork
OmniTouch My Teamwork
OmniPCX OmniPCX
OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX Enterpris Enterpris
Enterprise Enterprise Enterprise Enterprise Enterprise Enterprise e e
R6.1/6.1.1 R6.2 R7.0 R7.1 R8.0/8.0.1 R9.0 R9.1 R10.0
Unified
Communication
R5.0/ R5.0/ R5.0/ R5.0/ R5.0/ R5.0/ R5.0/ Not
R5.0 (2): My
R5.01 R5.01 R5.01 R5.01 R5.01 R5.01 R5.01 supported
Teamwork
application
Unified
Communication
Not
R5.1 (2): My R5.1 R5.1 R5.1 R5.1 R5.1 R5.1 R5.1 supported
Teamwork
application
OmniTouch 8660
MyTeamwork
- - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
Conferencing &
Collaboration R6.0
OmniTouch 8660
MyTeamwork
- - R6.1 R6.1 R6.1 R6.1 R6.1 R6.1
Conferencing &
Collaboration R6.1
OmniTouch 8660
MyTeamwork
- - R6.2 R6.2 R6.2 R6.2 R6.2 R6.2
Conferencing &
Collaboration R6.2
(2) Requires an OmniPCX Enterprise Gateway (at least R6.0.1 – latest release strongly recommended) if
G.723/G.729 codec is used. See also the “PBX Gateway” section below.
Two types of link are available when inter-connecting My Teamwork to PBX systems:
An OmniPCX Enterprise Gateway is not required in such context.
4.19.7Alcatel-Lucent OmniTouch 8670 Automated Message Delivery System (AMDS)

Application
OmniTouch Automated Message Delivery System

OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX
Enterpris Enterpris Enterpris OmniPCX Enterpris Enterpris Enterpris Enterprise
e e e Enterprise e e e
R6.1/6.1. R8.0/R8.0
R6.2 R7.0 R7.1 R9.0 R9.1 R10.0
1 1
Not
AMDS R3.2 R3.2 R3.2 R3.2 R3.2 R3.2 R3.2 R3.2 supported
R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 Not
R5.0/R5.01
AMDS R5.0 1 1 1 1 1 1 supported
AMDS R5.1 R5.1 R5.1 R5.1 R5.1 R5.1 R5.1 R5.1 Not

supported
OmniTouch
8670
Automated
Message - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
delivery
System
R.6.0
OmniTouch
8670
Automated
Message - - R6.1 R6.1 R6.1 R6.1 R6.1 R6.1
delivery
System
R.6.1
OmniTouch
8670
Automated
Message - - R6.2 R6.2 R6.2 R6.2 R6.2 R6.1
delivery
System
R.6.2
Two types of link are available when inter-connecting AMDS to PBX systems:
An OmniPCX Enterprise Gateway is not required in such context.

4.19.8Alcatel-Lucent OmniTouch Fax Server Application
OmniTouch Fax Server Application

OmniPC OmniPC
X X OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX
Enterpri Enterpri Enterpris Enterpris Enterpris Enterpris Enterpris Enterpris
se se e e e e e e
R6.1/6.1. R8.0/R8.0
1 R6.2 R7.0 R7.1 .1 R9.0 R9.1 R10.0
Fax
Server R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 Not
5.0 - - 1 1 1 1 1 supported
Fax
Server R5.0/R5.0 R5.0/R5.0 R5.0/R5.0 Not
5.1 - - 1 1 1 R5.1 R5.1 supported
OmniTouc
h 8450
Fax
Software
R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
OmniTouc
h 8450
Fax
Software
R6.1 - - R6.1 R6.1 R6.1 R6.1 R6.1 R6.1
OmniTouc
h 8450
Fax
Software
R6.2 - - R6.2 R6.2 R6.2 R6.2 R6.2 R6.2
Fax Server is embedded in UC server for a configuration under 500 users
The link between the Fax Server and OXE / UC is SIP.
4.19.9Alcatel-Lucent OmniTouch 8440 Messaging Services
OmniTouch 8440 Messaging Services

OmniPC OmniPC
X OmniPCX OmniPCX OmniPCX OmniPCX X OmniPCX OmniPCX
Enterpri Enterpris Enterpris Enterpris Enterpris Enterpri Enterpris Enterpris
se e e e e se e e
R6.1/6.1. R8.0/R8.0
1 R6.2 R7.0 R7.1 .1 R9.0 R9.1 R10.0
OmniTouch
8440
Messaging
Services
R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
OmniTouch
8440
Messaging
Services
R6.1 - - R6.1 R6.1 R6.1 R6.1 R6.1 R6.1
OmniTouch
8440
Messaging
Services
R6.2 - - R6.2 R6.2 R6.2 R6.2 R6.2 R6.2

4.19.10 Omni Desktop
Omni Desktop
OmniPC
OmniPCX X OmniPCX OmniPCX
Enterpris Enterpri OmniPCX Enterpris OmniPCX OmniPCX OmniPCX Enterpris
e se Enterprise e Enterprise Enterprise Enterprise e
R6.1 /
6.1.1 R6.2 R7.0 R7.1 R8.0/R8.0.1 R9.0 R9.1 R10.0
XML Not Not
telephony support Not supporte Not Not Not Not
R1.0 R1.1 ed supported d supported supported supported supported
TSAPI Not
Premium Not supporte Not Not Not Not
server R4.x R4.2.3.1 R4.2.3.1 supported d supported supported supported supported
TSAPI Not
Premium Not supporte Not Not Not Not
server R5.x R5.0.11 R5.0.11 supported d supported supported supported supported
TSAPI R6.3.0 / R6.3.0 / R6.3.0 / Not
Premium R6.3.1 R6.3.1 R6.3.1 supported
server R6.3.0 / R6.3.0 / R6.3.0 / R6.3.0 / R6.3.1 for R6.3.1 for R6.3.1 for Not
R6.3.x R6.3.1 R6.3.1 R6.3.1 R6.3.1 XL XL XL supported
TSAPI
Premium
R6.4.3 R6.4.3 R6.4.3 R6.4.3 R6.4.3 R6.4.3 R6.4.6 R6.4.6
server
R6.4.x
IP Touch and WLAN Phone not supported

4.19.11 Alcatel-Lucent OmniTouch 8410 Instant Communications Web Services
API Web Services

OmniPCX X X X OmniPCX X X OmniPCX
Enterpris Enterpri Enterpri Enterpri Enterpris Enterpri Enterpri Enterpris
e se se se e se se e
R6.1/R6.1 R8.0/R8.0
.1 R6.2 R7.0 R7.1 .1 R9.0 R9.1 R10.0
My IP Touch
Web Services
R2.x R2.1/R2.2 R2.2 - - - - - -
My Phone
Web Services
R2.x R2.1/R2.2 R2.2 - - - - - -
My Assistant
Web Services
R2.x R2.1/R2.2 R2.2 - - - - - -
My Messaging
Web Services
R2.x R2.1/R2.2 R2.2 - - - - - -
My
Management
Web Services
R2.x R2.1/R2.2 R2.2 - - - - - -
Not
R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 supported
My IP Touch Not Not Not Not
Web Services compliant compliant compliant supported
R3.x R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 XL XL XL
Not
My Phone Not Not Not Not
Not
My Assistant Not Not Not Not
Not
My Messaging Not Not Not Not
Not
My R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 supported
Management Not Not Not Not
Not
XML R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 supported
FrameWork Not Not Not Not
Management compliant compliant compliant supported
My TeamWork Not
Web Services supported
R3.x - - R3.1 R3.1 R3.1 R3.1 R3.1
IP Touch Web Not
Services R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01 supported
Telephony Not
R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01

One Number Not
R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01
Messaging Not
R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01
Management Not
R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01
XML Not
FrameWork supported
Management
R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01
TeamWork Not
R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01
IP Touch Web Not
Services R5.1 - - R5.1 R5.1 R5.1 R5.1 R5.1 supported
Telephony Not
R5.1 - - R5.1 R5.1 R5.1 R5.1 R5.1
One Number Not
R5.1 - - R5.1 R5.1 R5.1 R5.1 R5.1
Messaging Not
R5.1 - - R5.1 R5.1 R5.1 R5.1 R5.1
Management Not
R5.1 - - R5.1 R5.1 R5.1 R5.1 R5.1
XML Not
FrameWork supported
Management
R5.1 - - R5.1 R5.1 R5.1 R5.1 R5.1
TeamWork Not
R5.1 - - R5.1 R5.1 R5.1 R5.1 R5.1
IP Touch Web
Services R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
Telephony
Web Services
R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
One Number
Web Services
R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
Messaging
Web Services
R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
Management
Web Services
R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
XML
FrameWork
Management
R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
TeamWork
Web Services
R6.0 - - R6.0 R6.0 R6.0 R6.0 R6.0 R6.0
IP Touch Web
Services
R6.1/R6.2 - - R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2
Telephony
Web Services
R6.1/R6.2 - - R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2
One Number
Web Services
R6.1/R6.2 - - R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2
Messaging
Web Services
R6.1/R6.2 - - R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2
Management
Web Services
R6.1/R6.2 - - R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2
XML
FrameWork
Management
R6.1/R6.2 - - R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2
TeamWork
Web Services
R6.1/R6.2 - - R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2 R6.1/R6.2
WLAN Phone not supported
4.19.12 OmniVista 4760

Note: Configuration of several OmniPCX 4400/Enterprise at the same time available only
for OmniPCX 4400/Enterprise with same patch and release.
OmniVista
OmniPC
X OmniPCX OmniPCX OmniPCX
Enterpri Enterpris OmniPCX Enterpris Enterpris OmniPCX OmniPCX OmniPCX
se e Enterprise e e Enterprise Enterprise Enterprise
R6.1/R6. R8.0/R8.0
1.1 R6.2 R7.0 R7.1 .1 R9.0 R9.1 R10
Not Not Not
Wizard supporte Not supporte
Not Not supporte Not
R6 R6.1.2 d supported d
supported supported d supported
R5.0.07.02
4760 b
OmniVist R3.1.07. R3.2.04.0 R4.0.11.01 R4.1.08.0 R4.2.06.0 R5.1.04.00 R5.1.06.03
a 00 0.a .a 0.c 1a .B .c R5.2.01
4760
OXE
patch
downloa
d no no no R4.1 R4.2 R5.0 / R5.1 R5.1.1 R5.2
4760
PCS
patch
downloa
d no no no R4.2 R4.2 R5.0 / R5.1 R5.1.1 R5.2
4760
OXE
Audit no no no R5.0 R5.0 R5.0 / R5.1 R5.1.1 R5.2
4760 SIP R5.1.1/R5.
Manager no no no no no R5.0 / R5.1 R5.1.1 2 (note 1)
Note 1 : 4760 Sip manager not supported on R5.2 with W2008 and W7

4.19.13 OmniVista 8770
OmniVista
OmniPCX
OmniPCX OmniPCX Enterpris OmniPCX
Enterprise Enterprise e Enterprise
R8.0/R8.0.1 R9.0 R9.1 R10
OmniVist
a 8770 R1.0 R1.0 R1.0 R1.0
4.19.14 Business integrated Communication Server ( BiCS )
BiCS
OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX
Enterprise Enterprise Enterprise Enterprise Enterprise Enterprise Enterprise
R6.2 R7.0 R7.1 R8.0 R8.0.1 R9.0 R9.1
Not Not Not
BiCS supported supported supported R1.0 R1.1 R2.0, R2.1 R2.2

4.19.15 Professional Services Applications
Other Applications
X X X X OmniPCX X OmniPCX
Enterpri Enterpri Enterpri Enterpri Enterpris Enterpri OmniPCX Enterpris
se se se se e se Enterprise e
R6.1 / R8.0/R8.0
R6.1.1 R6.2 R7.0 R7.1 .1 R9.0 R9.1 R10.0
IP Desktop MIPD MIPD MIPD IPDSP IPDSP IPDSP IPDSP
N/A
Softphone V2.0.3 V2.0.3 V2.0.3 V9.x V9.x V9.x V9.x
IP Desktop MIPD MIPD MIPD IPDSP IPDSP IPDSP IPDSP
N/A
Agent V2.0.3 V2.0.3 V2.0.3 V2.0 V9.x V9.x V9.x
IP Desktop MIPD MIPD MIPD MIPD MIPD MIPD MIPD
N/A
Attendant V2.0.3 V2.0.3 V2.0.3 V2.x V3.x V3.x V3.x
Free
V1.0.4 V1.0.4 V1.0.4 V2.1.3 (1) V9.x V9.x
Desktop N/A V9.x
Ringtone
Customizati N/A N/A N/A N/A V1.x V1.x V1.x
V1.x
on
Wall Board
Manager for V1.5.0.7
N/A N/A N/A V5.x V5.x V5.x V5.x
OTCC (3)
Premium
CCIVR
integration
N/A V7.1 (4) V7.1 (4) V7.1 (4) V7.1 (4) V7.1 (4) V9.0 N/A
for OTCC
Premium
(1) V 2.1.3 from R8.0 use the same compatibility rules than XML
API
(2) V 1.2.7 use the same compatibility rules than API
(3) V1.5.0.7 follow the Premium
versions
Release 1.0 (technique) = Version 7.0 (commercial) -> wbm
1.5.0.7
Release 1.1 (technique) = Version 7.1 (commercial) -> wbm 1.5.1 (compatible also with
Release 1.0)
Release 1.0.2 (technique) = Version 7.1 (commerciale) -> from wbm 1.5.2.3 and less than
2.0.0.0
Release 2.0.X (technique) = Version 8.0 (commerciale) -> from wbm 2.0.0.0
and above
From wbm 1.5.2 only compatible with Version 7.1.
(4) V7.1 follow the Premium versions
IPTouch DoorCam no more supported (Phase out)

4.19.16 Miscellaneous
Miscellaneous
OmniPC
OmniPCX OmniPCX OmniPCX X OmniPCX
Enterpris Enterpris Enterpris Enterpri OmniPCX Enterpris OmniPCX
e e e se Enterprise e Enterprise
R6.1/R6.1.
1 R6.2 R7.0 R7.1 R8.0/R8.0.1 R9.0 R9.1/R10.0
Notification Server
R2 R2.08d R2.08d Note 1 Note 1 Note 1 Note 1 Note 1
Alcatel-Lucent
Audio Station
(AAS) 7.2 7.2.1 7.2.2 7.2.3 7.2.3 7.2.3 7.2.3
Netop (Replace IRC
client) – remote 7.65
connection for IVR 7.65 7.65 7.65 7.65 7.65 (Note2) 7.65 (Note2)
Translator Tool for
OXE Strings. (TSL) R4.1.0 R4.1.0 R4.1.0 R4.1.0 R4.2.0 R4.2.0 R4.3.0
Note 1 : Product is in phase out since April 2006
Note 2 : Product is Phase-out. No more in the catalogue.

5. OMNIPCX ENTERPRISE HARDWARE COMPATIBILITY
5.1 CRYSTAL HARDWARE VS RELEASE OMNIPCX ENTERPRISE
COMPATIBILITY
5.1.1 Legend used in the table
Phase Status set to “Out”: no longer in OmniPCX Enterprise catalog
Y = Supported by the Release and still in the catalog
S = Supported by the Release but no longer in the catalog
N = Not supported by the Release
* = Only in case of Add-On
5.1.2 System Boards
System Board
OmniPC OmniPC OmniPC
OmniPCX OmniPCX OmniPCX X X X
Enterpris Enterpris Enterpris Enterpri Enterpri Enterpri
Phase e e e se se se
Board Statu R6.1/ R6.2/R7. R8.0/ R9.0/R9.
Type s R6.1.1 0 R7.1 R8.0.1 1 R10.0 Notes
CPU5 step (1) HDD 6 Gb with
3 Out S (1) S (1) S (1) N N N 128 MB RAM
(2) HDD 6 Gb with
128 MB RAM
CPU6 step (3) HDD 10 Gb with
2 Out Y (2) Y (2) Y (2) S (3) S(3) S(3) 128 MB RAM
(4) Disk  6 Gb with
256 MB RAM
CPU7 step (5) Disk10 Gb with
1 Out Y (4) Y (4) Y (5) Y (5) S (5) S (5) 256 MB RAM
(6)Disk  10 Gb with
CPU7 step 256 MB RAM, no
2 - N N Y (6) Y (6) Y (6) Y (6) hardkey
ECX1 Out S S S S S S
Replaced by IO2N with
IO2 Out S S S S S S CPU7
IO2N - Y Y Y Y Y Y
OBCA-2 Out S S S S S S
VMU-OBCA Out S S S S S S
VMU-OBCA
2 Out S S S S S S
Couple INTOF-A with
INTOF Out Y Y Y S S S INTOF-B
Couple INTOF2-A with
INTOF2 - Y Y Y Y Y Y INTOF2-B
no Alcatel-Lucent
RT2 Out S S S S S S series 9 sets behind
RT2-1 Out Y Y Y Y S S RT2 /RT2-1
MMSFD Out S S S S S S
RMAB - Y Y Y Y Y Y
SRMA Out S S S S S S
NX64 Out S S S S S S

5.1.3 Auxiliary Coupler Boards
Auxiliary Coupler Boards

OmniPC OmniPC OmniPC OmniPC
OmniPCX X X OmniPCX X X
Phas Enterpris Enterpri Enterpri Enterpris Enterpri Enterpri
e e se se e se se
Board Statu R6.1/R6.1 R6.2/R7. R8.0/R8.0 R9.0/R9.
Type s .1 0 R7.1 .1 1 R10.0 Notes
GPA Out S S S S S S
GPA2 - Y Y Y Y Y Y VG + Conference
only
SU Out S S S S (1) S (1) S (1) (1) Only used for
SUVG Out S S S S (1) N N auxiliaries. 4300
migration not
supported in R8.0
VG Out S S S S N N
Z20/VG Out S S S S S S
5.1.4 Extension boards
Extension boards
OmniPC
OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX X
Phas Enterpris Enterpris Enterpris Enterpris Enterpris Enterpri
e e e e e e se
Board Statu R6.1/R6.1 R6.2/R7. R8.0/R8.0
Type s .1 0 R7.1 .1 R9.0/R9.1 R10.0 Notes
eUA32 - Y Y Y Y Y Y
eZ32-2 - N N N N N Y
eZ32 Out Y Y Y Y Y S
Configured
on VH step
UA/ZP Out S S S S S S 2 (90w)
UA16 Out S S S S S S
UA32NV Out S S S S S S
Z12 Out S S S S S S
Z12-2 Out S S S S S S
Z24 Out S S S S S S
Z24-2 Out S S S S S S
Z32 Out S S S S S S

5.1.5 Trunk Interface boards
Trunk Interface boards

e e se se e se se
Type s .1 0 R7.1 .1 1 R10.0 Notes
ACEM Out Y Y Y Y S S
BPRA Out S S S S S S
BPRA2 Out S S S S S S
BPRA2-
1 Out S S S S S S
BRA Out S S S S S S
BRA2-1 - Y Y Y Y Y Y
DPT1 Out Y Y Y Y S S
No more A-Mu
conversion on
DPT1-2, E1 &
DPT1-2 can't be
used on the same
DPT1-2 - N N N Y Y Y system.
EMTL - Y Y Y Y Y Y
NDDI Out Y Y Y S (1) S S
NDDI2 Out Y Y Y S (2) S S
NDDI2-
2 - Y Y Y Y (3) Y (3) Y (3) (3) UK included
+DPNSS and
NPRAE Out Y Y Y Y S S DASS2
NPRAE- +DPNSS and
2 - N N N Y Y Y DASS2
PCM Out S S S S S S
PCM2 - Y Y Y Y Y Y
PRA Out S S S S S S
PRA2 Out Y Y Y S S S

5.1.6 DECT boards
DECT Boards
e e se se e se se
Type s .1 0 R7.1 .1 1 R10.0 Notes
No more
synchro CSP
with
DECT2&DECT
DECT2 Out S S S S S S 4 from R4.2
No more
synchro CSP
with
DECT2&DECT
DECT4 Out S S S S S S 4 from R4.3
DECT4H
B Out S S S S S S
DECT8 - Y Y Y Y Y Y
DTM Out S S S S S S
Note: Since R9.1 the INTIP3 in CPU position can assure the DTM (DECT Timing Module)
function.
5.1.7 Voice Mail 4635
Voice Mail 4635

OmniPC
OmniPCX OmniPCX OmniPCX OmniPCX X OmniPCX
Enterpris Enterpris Enterpris Enterpris Enterpri Enterpris
Phase e e e e se e
Type s .1 0 R7.1 .1 1 R10.0 Notes
MSBI - Y Y Y Y Y Y
SPA3 - Y Y Y Y Y Y
VPM35 Out S S S S S S
VPM35-
1 Out Y Y Y Y Y S
VPU5 Out S S S S S S
VPU6 - Y Y Y Y Y Y
5.1.8 Link Interface Optimizer Boards

Link Interface Optimizer boards
OmniPC
Phas Enterpris Enterpris Enterpris Enterpris Enterpri Enterpris
e e e e e se e
Type s .1 0 R7.1 .1 R9.0 0 Notes
GIP4-1 - Y Y Y Y Y Y
GIP4-4 - Y Y Y Y Y Y
GIP6 Out S S S S S S
GIP6A Out S S S S S S
ARMADA - N N N N N Y
INTIP Out S S S S S S
Y in R9.1
and R10.0
INTIP-2 - Y Y Y Y Y S for IOIP
INTIP-3 - N N N N N Y
LIOB Out S S S S N N
LIOB-2 Out S S S S S S
LIOP Out S S S S N N
with
LIOP-2 Out S S S S S S COMP2
LIOX Out S S S S N N daughter
LIOX-2 Out S S S S S S board
5.1.9 Miscellaneous Boards
Miscellaneous Boards
OmniPC
Phas Enterpris Enterpris Enterpris Enterpris Enterpri Enterpris
e e e e e se e
Statu R6.1/R6.1 R6.2/R7. R8.0/R8.0 R9.0/R9.
Board Type s .1 0 R7.1 .1 1 R10.0 Notes
IRC Out S S S N N N
TNLO1 Out S S S S S S
TNLO2 Out S S S S S S
TNLO11 - Y Y Y Y Y Y
TNLO21 - Y Y Y Y Y Y
Alcatel-
Lucent
security
SSM-box - N Y Y Y Y Y module
Alcatel-
Lucent
security
MSM-box - N Y Y Y Y Y module
Alcatel-
Lucent
security
SSM-RM - N N N Y Y Y module
Alcatel-
Lucent
security
MSM-RM - N N N Y Y Y module

5.1.10Voice Hub and Wall Mounted cabinets
Voice Hub and Wall Mounted cabinets

e e se se e se se
Type s .1 0 R7.1 .1 1 R10.0 Notes
(1) 10 Base
T only.
10 BaseT
connector
(3BA 23182
AA) has been
phased out by
VH55W Out S (1) S (1) S (1) S (1) S (1) S (1) April 2006
(2) Basically,
all cabinets
were only
compatible
VH48V Out Y (2) Y (2) Y (2) S S S with 10BaseT.
Since the
reference
listed in the
table "Rack
references"
below, the VH
and WM1
cabinets are
compatible
with the
VH90W Out Y (2) Y (2) Y (2) S S S 10/100BaseT.
WM1 –
48V Out Y (2) Y (2) Y (2) S S S
WM1 –
110/230
V Out Y (2) Y (2) Y (2) S S S

Rack references
Designation Reference
VH (10/100BaseT) Basic Rack 48V 3BA 56191 AN

VH (10/100BaseT) Basic Rack 48V – USA 3BA 56191 UN
VH (10/100BaseT) Basic Rack 90W 3BA 56193 AN
VH (10/100BaseT) Basic Rack 90W – USA 3BA 56193 UN
VH (10/100BaseT) Extension Rack 48V 3BA 56192 AN
VH (10/100BaseT) Extension Rack 48V – USA 3BA 56192 UN
VH (10/100BaseT) Extension Rack 90W 3BA 56194 AN
VH (10/100BaseT) Extension Rack 90W – USA 3BA 56194 UN
WM1 (10/100BaseT) Basic Packed 110/230V 3BA 27112 AN
WM1 (10/100BaseT) Basic Packed 110/230V – USA 3BA 27112 UN
WM1 (10/100BaseT) Basic Packed 48V 3BA 27113 AN
WM1 (10/100BaseT) Basic Packed 48V – USA 3BA 27113 UN
WM1 Battery package (battery autonomy 1.2 Ah) 3BA 57106 UB
5.2 COMMON HARDWARE/OMNIPCX ENTERPRISE COMPATIBILITIES

* = Only in case of Add-On
5.2.2 System boards
System Board
OmniPCX X X OmniPCX X OmniPCX
Phas Enterpris Enterpri Enterpri Enterpris Enterpri Enterpris
e e se se e se e
Type s .1 0 R7.1 .1 R9.0 0 Notes
(1) Disk10 Gb
with 256Mb
minimum for PCS
(2) Disk10 Gb
with 256Mb
CS Y Y Y (1) Y (2) S (2) S (2) minimum
(3) minimum
R9.0>H1.301.3
CS-2 N N N N Y (3) Y 1

GD Out S S S S S S
GD-2 Y Y Y Y Y S
GD-3 - N N N N N Y (1)
GA Out S S S S S S
GA-2 Y Y Y Y Y S
GA-3 - N N N N N Y (1)
MEX Y Y Y Y Y S
PowerME
X - N N N N N Y (1)
MCV8-I Out S S S S S S
MCV24-I Out S S S S S S
MADA3 Y Y Y Y Y Y
MADA1 Y Y Y Y Y Y
ARMADA - N N N N N Y (1)
HSL2 Y Y Y Y Y Y
HSL1 Y Y Y Y Y Y
S-LANX4 Y Y Y Y Y Y
LANX8 Out S S S S S S
LANX16-
1 Out S S S S S S
LANX16-
2 Y Y Y Y Y Y
AFU-1 Y Y Y Y Y Y
XMEM-1 Y Y Y Y Y Y
RMA Y Y Y Y Y Y
MODB Y Y Y Y Y Y
Note :
(1) : Mix of GD3, GA3, PowerMEX and ARMADA with former GD/GD2, GA/GA2, MEX,
MADA1, MADA3 in a same Cabinet (meaning Rack and interconnected Rack through HSL
link) is not allowed.
5.2.3 Extension boards
Extension Boards
OmniPC
Phase e e e e se e
Type s .1 0 R7.1 .1 R9.0 0 Notes
UAI16 Out S S S S S S
SLI16 Out S S S S S S
UAI16-1 - Y Y Y Y Y Y
UAI8 - Y Y Y Y Y Y
UAI4 - Y Y Y Y Y Y
SLI16-1 Out Y Y Y Y Y Y

SLI16-2 - N N N N N Y (1)
SLI8-2 - N N N N N Y (1)
SLI4-2 - N N N N N Y (1)
Note :
(1) Support from OXE R9.1 2010 Spring Offer (i1.605.16.c).
5.2.4 Trunk Interface boards
Trunk Interface boards

e e se se e se se
Type s .1 0 R7.1 .1 1 R10.0 Notes
APA4 - Y Y Y Y Y Y
HU
APA4 Out S S S S S S
LCG
APA4 - Y Y Y Y Y Y
TBR21
APA4 - Y Y Y Y Y Y
US
APA8 - Y Y Y Y Y Y
HU
APA8 Out S S S S S S
LCG
APA8 - Y Y Y Y Y Y
TBR21
APA8 - Y Y Y Y Y Y
US
METCLI Out S S S S S S
GSCLI - Y Y Y Y Y Y
CLIDSP - Y Y Y Y Y Y
DDI2 Out S S S S S S US market
DDI4 - Y Y Y Y Y Y US market
BRA2 - Y Y Y Y Y Y
BRA4 - Y Y Y Y Y Y
BRA8 - Y Y Y Y Y Y
DIGITAL - Y Y Y Y Y Y
ACCESS
E1
DASS2
DIGITAL - Y Y Y Y Y Y
ACCESS
PCM-R2
ISDN - Y Y Y Y Y Y
ACCESS
E1 PRA-
T2
PRA-T1 - Y Y Y Y Y Y
T1-CAS - Y Y Y Y Y Y
IRAD- Out Y Y Y S S S Not available
CH for US market

5.2.5 Mixed boards
Mixed boards
OmniPC
e e e e se e
Board Phase R6.1/R6.1 R8.0/R8.0 R9.0/R9.
Type Status .1 R6.2/R7.0 R7.1 .1 1 R10.0 Notes
8UA +
MIX084 Out S S S S S S 4Z
4UA +
4UA +
4T0 /
8UA +
MIX484 Y Y Y Y Y Y 4Z
4T0 /
4UA +
MIX448 Y Y Y Y Y Y 4Z
2T0 /
4UA +
MIX244 - Y Y Y Y Y Y 4Z
5.2.6 External battery racks

Module Racks and External battery
OmniPC
OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX X
Enterpris Enterpris Enterpris Enterpris Enterpris Enterpri
e e e e e se
R6.1/R6.1. R8.0/R8.0.
Board Type 1 R6.2/R7.0 R7.1 1 R9.0/R9.1 R10.0 Notes
Module Rack
S (MR1) Y Y Y Y Y Y
Module Rack
L (MR3) Y Y Y Y Y Y
External The
Battery Rack Y Y Y Y Y Y minimum
External technical
Battery Rack releases of
12V Cherokee Y Y Y Y Y Y MR1and
External MR3 racks
Battery Rack compatible
36V Cherokee Y Y Y Y Y Y with the
external
battery rack
are in the
"Rack
External reference"
Battery Box Y Y Y Y Y Y table below

Designation Reference
Rack 1U MR1 (without battery) 3EH 76020 AEAB

Rack 3U MR3 230 V (without battery) 3EH 76027 AEAB (*)
Rack 3U MR3 110 V (without battery) 3EH 76027 BEAB (*)
Rack 1U MR1 48V (assembled) 3EH 76172 AAAB
Rack 3U MR3 48V (assembled) 3EH 76170 AAAA
Extension Battery Rack 3EH 76187 AAAA
Charger Rack 48V / 14 Ah W/O Rectifier 3EH 76181 AAAA
Rectifier 500W for Charger Rack 3EH 76185 AAAA
(*) Rack 3U MR3 230V/110 V variants ABxx, BBxx, ACxx and BCxx are not allowed to be used
with GD-3 and GA-3 boards.

appliance server
5.2.7 Compatibility between Appliance Server and Software Releases
Appliance Server
OmniPCX X X OmniPCX X OmniPCX
Phas Enterpris Enterpri Enterpri Enterpris Enterpri Enterpris
e e se se e se e
Type s .1 0 R7.1 .1 R9.0 0 Notes
Out S S S S (2) S (2) S (2) (2) Memory size =
IBM 305 1Go
IBM Out S S S S (2) S (2) S (2) (2) Memory size =
X306 1Go
N S (1) S S (2) S (2) S (2) (1) Version
Out minimum =
F3.301.16.d
IBM (2) Memory size =
X306M 1Go
IBM Out N N Y (2) Y (2) Y (2) Y (2) (2) Memory size =
X3250 1Go
HP N N N Y (2) (3) Y (2) Y (2) (2) HP DL320 G5
DL320 Memory size =
G5p 1Go
(3) G1.503.20
minimum (R8.0.1)
IBM N N Y (5) Y (4) Y Y (4) 8.0.1 Only
X3250- (=>G1.503.20
M2 minimum)
(5) F5.401.36.d
minimum
HP N N N N Y (6) Y (7) (6) H1.301.42.a
DL320 minimum
G6 (7) I1.605.16.c
minimum
IBM N N N N Y (6) Y (7) (6) H1.301.42.a
X3250 minimum
M3 (7) I1.605.16.c
minimum

5.2.8 Compatibility between Blade Server and Software Releases
Please contact Central Pre-Sales for any question related to compatibility between Blade Server
and Software Releases.
5.2.8.1 Modifications/restrictions when an Alcatel-Lucent crystal CPU is replaced by an

Appliance Server
Note: Only use Alcatel-Lucent recommended Appliance Servers. Alcatel-Lucent has validated an
Appliance Server as OEM from IBM. BP who wants to buy AS directly from IBM should consult
"Alcatel-Lucent Application Partner program" for the current Appliance Server reference
supported.
The following hardware/features are not supported when the existing ACT CPU is replaced by an
Appliance Server during a migration:
Hardware / feature Alternative with Appliance Server
Voice Guide on CPU6 GPA2
Q23 on CPU6 GPA2
External Music on Hold on CPU Z port
4615 / VMU-OBCA 4635J
DTM for DECT on CPU6 / INTIP3 in CPU position DECT8 Board / INTIP3 in CPU position
Additional V24 ports or SPB for Additional V24 ports V24-IP Module
IO2/ OBCA Boards (see next section) No Alternative or V24-IP box
Remote Maintenance Access (RMA) RMA with rack 1U
5.2.9 Feature loss on IO2/IO2N/ OBCA loss

The IO2 and OBCA boards are no longer available when the Communication Server
Software runs on Appliance Server because:
The IO2 board is linked to ACT CPU via a front panel bus not available between an
Appliance Server and an Auxiliary Crystal Gateway.
The OBCA Board is a daughter board of the CPU3/6.
Some applications / features are not available when the hardware platform of the R5.1
Communication Server is an Appliance Server:
Data Communication in B Channel:
Example with OmniPCX 4400 :
PRA
4760 B PSTN PRA
server CPU
IO2/OBCA
CPU
Ethernet
IO2 / OBCA
B : B Channel with Data bearer capability
: OmniPCX 4400 Board
Following Signaling Support for ABC Hybrid Link:

Signaling channel through synchronous data communication.

Signaling in B channel not switched (see also multi-direction ABC accesses).
Signaling in switch B channel through permanent connection of public network (no
signaling backup via IDSN and no secured access).
Direct Access to Communication Server Application via IO2 is not available with Appliance
Server but can be replaced by IP/V24 Box:
Example with OmniPCX 4400 :

IO2 / OBCA
Application
UA
terminal CPU
(hotel menu,
AHLink, UA set + TA
wallboard CCD,...)
Example with OmniPCX Enterprise and A/S :
INTIP
Application
terminal
(hotel menu,
AHLink,
wallboard CCD,...)
V24/IP Box

6. INTERNAL COMPATIBILITY ISSUES
6.1 COMPRESSION RESOURCE COMPATIBILITY ISSUES

When upgrading a networked configuration where voice compression service is
implemented, the pre-sales and sales force must be aware of the following compatibility
issues:
INTIP3/GD3/GA
LIO P/B/X LIO/P/B/X-2 LIO E INT IP /GD/GA 3
LIO P/B/X Comp6 Y Y (Note 1) N N N
Y (See Y (See
restriction restriction
LIO/P/B/X-2 Comp 2 Y Y below) below)
LIO E Comp 2 Y N (note 2) N (note 2)
INT IP GIP 6/GIP4 Y Y
GD / GA MCV/MADA Y Y
INTIP3/GD3/GA
3 ARMADA Y Y
Note 1: Possible voice quality issues.
Note 2: see commercial package for upgrade toward INT IP
6.2 VOICE OVER IP COMPATIBILITY ISSUES WHEN IMPLEMENTING NEW

SERVICES
6.2.1 Framing 20ms for voice over IP
Voice framing occurs every 20ms when using the G729A or G711 algorithm.
This improvement provides a:
Significant decrease in transit delay in networked configurations. Thus providing the
same transit speed as "direct switching over ABC network" provides. But transit
is only available on INT IP (not on GD/GA, nor on INTIP3/GD3/GA3)
This framing rate is available only on INT IP and GD boards and is not compatible with any
former LIO compression resources.
Note the following:
Configuration of "framing 20ms" is a "per system" configuration parameter per algo.
(This means that every VOIP communication on the system is framed every
20ms).
20ms framing is only available on INT IP and GD boards and is not available on other
LIO devices.
This means that activating 20ms framing on an existing network replaces all compression
resources over the ABC network, including:
LIO-E and LIO-TSC.
LIO-P, LIOB, and LIO X (comp 6 based).
6.2.2 Remote LIO must be upgraded to ACT- IP.

20 ms framing will not be compatible with VoATM based on BBC 2. Interoperability
between VoATM and VOIP is not released on OmniPCX Enterprise.
6.2.3 H323 services introduced since OmniPCX 4400 R4.2

OmniPCX 4400 R4.2 provides new H323 services (see release description) allowing the
use of the H323-compliant protocol in ABC F2 over IP (H323 inter-node feature) and

services such as "fast start", External Gatekeeper, Internal Gatekeeper, services… for ABC
F2 over IP communications.
When requiring this operating mode, users must consider the following issues:
"H323 inter-node" feature is only available on INT IP. Since R5.1.2 on GD/GA.
"H323 inter-node" is a per system configuration parameter.
Every node of a network must be configured according to this operating mode, this
implies that every OmniPCX 4400 R4.2 running this feature for ABC F2 over IP
must be configured with INT IP boards.
6.2.4 Voice over IP and direct RTP switching with OmniPCX Enterprise
Echo cancellation depth is 64 ms as of R6.0 / R6.0.1/ R6.1/R6.2/R7.0 (32 ms before R6.0 /
R6.0.1)
Echo cancellation depth is 128 ms in R7.0 using GIP4 / MADA daughter boards and in R9.1
using ARMADA daughter boards.
Echo cancellation depth

OmniPCX OmniPCX
OmniPCX Enterprise OmniPCX
Enterprise Enterprise
R6.0/R6.0.1 Enterprise
R5.1/R5.1.1/ R7.0/R7.1/R8.0/8.
R6.1/R6.1.1/ R6.2 R9.1
R5.1.2 0.1/R9.0
GIP6/MCV24 32ms 32ms 32ms 32 ms
GIP4/MADA 64ms 128ms 128 ms
ARMADA 128 ms
Direct IP switching in network

Direct RTP is a feature that allows direct RTP communication between endpoints without
requiring the use of a compression resource from the call server.
Direct RTP is available in the following cases:
Between two endpoints belonging to the same node.
Between two endpoints belonging to different nodes connected by IP VPN internodes
links. This configuration is called "direct RTP in network".
The advantage of direct RTP, especially in a network, is that RTP flow does not transit in
any way through call server compression resource, transmission delay is minimum and
only related to voice processing (at endpoint level) and network delay.
Direct RTP mode must be configured for these reasons and particularly when a Common
Hardware (GD board) is used. This is due to the fact that configuring transit across this
resource involves a compression/decompression cycle that often leads to unacceptable
overall transit delay.
Configuration of Direct RTP must follow these "rules":
Direct RTP must be activated across the entire IP PCX network
H323 "fast start" mode is mandatory
Not compatible with LIO-E
Since R9.1, direct RTP is always activated.

Before R7.0, direct RTP cannot be used in the following cases:
Communication involving pure H323 devices like softphone application, or Z over IP

devices such as Audiocodes MP1xx devices.
Communication will transit on the Call Server and a compression resource will be
allocated during the communication, in this case careful design of the network
dimensioning must be performed.
Mixed OmniPCX Enterprise and OmniPCX 4400 nodes due to the fact that Direct RTP
in network is not available before OmniPCX Enterprise R5.0 Lx.
6.2.5 Direct RTP with H323 equipments
Release 7.0 allows using Direct RTP for H323 equipments and all OmniPCX Enterprise H323
Gateways (MGDs, GA, INTIP) for voice and Fax T38.
H323 direct RTP is also available for equipment supporting the Fax over IP (Audiocode MP1xx),
H323 Gateways of carriers, the My Phone application in VoIP Nomadic.
The management of H323 direct RTP on OmniPCX Enterprise must be carefully enabled since
all H323 terminals of the installation must be able to reroute the H245 RTP flow called
"Empty Terminal Capability Set" or "Voice Path Replacement".
In ABC-F networked configuration, all the nodes must be in Release 7.0 or higher to
benefit the direct RTP for H323 terminals on all the nodes.
No direct RTP between SIP set and a H323 terminal.
No direct RTP between H323 terminals with different compression algorithms (for instance case
of H323 terminal in G723 or G729 calling a 4645 in G711).
Management
 IP/IP Parameters/Direct RTP = True
 IP/IP Parameters/Direct RTP For H323 Terminals = True
6.3 COMPATIBILITY ISSUES WHEN USING SIP-TLS SIP GATEWAY

As of Release 10.0, TLS protocol is supported on SIP/ISDN Gateways.
When voice encryption is activated (SIP-TLS/sRTP), the network encryption must be deactivated
and encryption of applications (ACS/MyTeamwork, AVST external voice mail) is not supported
(Meaning MSM on front of applications must be removed).
Those restrictions don’t exist in case of SIP-TLS/RTP (no voice encryption on SIP Trunk).
6.4 CONDITIONS FOR INSTALLATION IN NETWORK
As of Release 10.0, when the SIP-TLS/sRTP SIP Gateway is activated (Voice

encrypted along with SIP Signaling) the encryption in Network must be
deactivated. See section 6.3 for details.
As of Release 9.1, the RTP direct mode in network is activated by default and
can’t be de-activated (the parameter has been removed).
In case of migration to Release 9.1, the RTP direct mode will be automatically
activated.
The complete ABC-F network must be managed in accordance and all devices /
boards incompatible with RTP direct mode in network removed before the
migration. As a consequence, systems in Release up to 5.0 Ux can not be in a
network having a PBX in Release 9.1.
As of Release 8.0, the limit capacities of the system have changed.
The increase of these capacities can generate an increase in the number of
equipment by Call Server.
Beyond 27000 equipments, a system is regarded as XL or "Large Capacity".
This limit is determined by Actis. If this limit is exceeded, Actis sets the
PARA_MAO 24 to 1 (Large Capacity configuration).
Two types of systems are to be considered as of Release 8.0:
 System of which the number of equipment does not exceed 27000 (identified
with 2 bytes) : idem Release 7.1
 System of which the number of equipment exceeds 27000 (identified with 4
bytes): System considers as XL or 'Large Capacity"
Network interworking
Each node of a network must be in Release 8.0 or higher if one of conditions
below exist on one of node of the network:
 A R8.0 node or higher in XL mode
 50 000 users and more in network
 1000 entities and more on a node of network
 200 DDI translator ranges and more on one node of network
 50 NPD and more on one node of network
 30 DCT and more on one node of network
As the T38 fax mode between Media Gateways is implemented only in Releases
8.0.1 (since patch G1.503.35), 9.0 and 9.1, no faxes exchange will be possible
via IP between a Release 9.1/10.0 node with GD3/INTIP3 boards and nodes in
Release prior to 8.0.1 during the temporary progressive migration phase.
Networked interworking rules for a system in Release 9.1 of which the number of
equipment does not exceed 27000 (identified with 2 bytes), have evolve compared to a
system in Release 7.1 as described hereafter.
As of Release 7.0 and with the implementation of name using UTF-8 format, the
networked interworking rules have evolved.
It is authorized to operate a Release 9.1/10.0 in a single sub-network only with systems
having at least the versions below:
 R9.0 : H1.301.24
 R8.0.1 : G1.503.9
 R8.0 : G1.302.5
 R7.1 : F5.401.7
 R7.0 : F4.401.13
 R6.2 : F3.301.16.e (patch for compatibility UTF-8)
 R6.1.1 : F2.502.12.d (patch for compatibility UTF-8)
 R6.0.1 : F1.603.1.z (patch for compatibility UTF-8)
Cohabitation in a single sub-network of a Release 9.1/10.0 with Releases 5.1.x, 6.x, 7.x is
only authorized temporarily to allow progressive migration to the latest supported
release (in case of 5.1.x and 6.0, UTF-8 must not be activated in the network).
Cohabitation in a single sub-network of a Release 9.1/10.0 with Releases < 5.0 Ux, 5.0
Ux, 5.0 Lx is not authorized.

During progressive migration and depending on certain topologies and
hardware used, there may be poor audio quality; see chapter 6.4
If using a CCS multi-site, each node must be in Release 9.1/10.0.
As of Release 7.0, the number of entities and IP domains changes to 1000 (in
Releases < 6.2, the number of entities is 255 and the number of IP domains is
128). In a network, these limits are allowed only if each node of the network is
in Release 6.2 or higher.
In Release 9.1/10.0 and on each node of the network (whatever their version)
cohabiting with R9.1/10.0:
LIOE and TSC-LIOE boards must be replaced by INTIP or INTIP3 boards.
INT1and INT2 boards must be replaced by INTOF/INTOF2 boards.
If using Gigabit sets, refer to the technical communication TC1090 Wrong IP

Touch Ethernet port speed negotiation to know the versions to be used on the
nodes in release lower then 9.1.
From Release 7.1 and on each node of the network (whatever their version) cohabiting
with R9.1/R10.0:
LIOE and TSC-LIOE boards must be replaced by INTIP boards.
INT1and INT2 boards must be replaced by INTOF/INTOF2 boards.
If one node of the network is in XL configuration, all the nodes MUST at least
be in release R8.0.
As of Release R9.0, in case of heterogeneous network topology with ABC-IP trunks, the
transit node must be in Release R9.0 for the ABC-IP feature. Heterogeneous versions
that are allowed on other nodes can be only R8.0/R8.0.1 or R7.1.
6.5 INSTALLATION OF RELEASE R9.1/R10.0 IN NETWORK WITH

RELEASES 5.1.X, 6.X, 7.X
During the cohabitation period you must prohibit:
broadcasting of the database and not carry out any audit,
 on the Release R9.1/R10.0 node, sending of the names in UTF-8 format in the network
(set the Enable UTF8 in ABCF network system parameter to False) if a node is not
in a UTF-8 compatible version (see above).
Releases 5.1.x, 6.x, 7.x are allowed to cohabite temporarily in a sub-network
environment with Release 9.1/10.0 to allow progressive migration, with the following
restrictions:
 The Enhanced Voice Quality (Framing VoIP) parameter must be identical on
each node of the network.
 The LIOE and TSC-LIOE boards are not authorized in heterogeneous network
functioning.
 The H323 Inter-node protocol parameter must be set to Yes.
 The Direct RTP (in network) parameter must be set to Yes.
 See table in 6.9.4.2.
 If GD3/INTIP3 boards are present in the Release 9.1/10.0 node, no faxes exchange
via IP will be possible between this Release 9.1/10.0 node and nodes in Releases
5.1.x / 6.x / 7.x, as these releases don’t support the T38 fax mode between Media
Gateways.
Note
Release 5.0 Ux cannot cohabite, even shortly, in a sub-network environment with
Release 9.1/10.0, as it does not support RTP direct mode in network.
6.6 INSTALLATION OF RELEASE 9.1/10.0 IN NETWORK RELEASE 8.0,

8.0.1, 9.0
Releases 8.0, 8.0.1, 9.0 are compatible with Release 9.1/10.0 in a sub-network
environment, with the following restrictions:
Minimum compatible versions:
 R9.0 : H1.301.24
 R8.0.1 : G1.503.9
 R8.0 : G1.302.5
The H323 Inter-node protocol parameter must be set to Yes.
The Direct RTP (in network) parameter must be set to Yes.
The T38 only parameter has to be managed in coherency amongst the sub-network. This
parameter for the protocol to be used when sending faxes between Media Gateways is
supported in all patches of Releases 9.0, 9.1, 10.0 and in 8.0.1 only from patch
G1.503.35. GD3/GA3/INTIP3 boards support only the T38 fax mode between Media
Gateways.
6.7 AUDIT/BROADCAST
Audit
All the tables not implemented in a Release generate the message below in the
results of the audit for these tables:
Not Audited: Not implemented in the version but does not cause a
blockage of the audit.
Broadcast
On receipt of an unknown object in a Release, an error is signaled and an incident is
generated.
Note
Although the audit and the broadcasting must be inhibited during the period of
cohabitation, for information purposes, these errors can be deleted by the versions
below or higher:
 E2.404.b
 E2.502.2.e
 E2.504.1.e
The following tables are not broadcast:
 inst/desc/SIO parameters
 data/data prefix
 inst/desc/free numbers range list
6.8 COMPATIBILITY OF EXTERNAL APPLICATIONS
In a heterogeneous network, it is essential to align the application versions with

those of Release 9.1.
See paragraph 4.19 for the versions of applications compatible with Release
9.1.
As of OXE R10.0, some restrictions exits when the feature SIP-TLS/sRTP SIP
Gateway is activated see section 6.3 for details.

6.9 COMPATIBILITIES
6.9.1 Reminder on boards supporting the Transit function and the direct RTP
The Transit function allows a reduction in the time introduced by a compression and
decompression. This function is only available with the G723 and G729 algorithms.
Support of transit function (4) Support of direct RTP function

LIO P/B/X COMP6 (1) (2) No Not applicable
LIO P/B/X COMP2 (2) Yes Not applicable
LIOe (3) No No
INTIP or INTIP2 Yes Yes
GD, GD2, GD3, GA, No Yes
GA2, GA3 or INTIP3
(1) The LIO-COMP6 board is not compatible in R6.x and R7.x. It is not authorized in a network with
INTIP or GA/GD.
(2) The LIOP/B/X boards are supported by Release 7.1 but can no more be configured for addition
or for new installation.
(3) The LIOe board is no more authorized in heterogeneous network.
(4) There is no transit in G711 but packetization/depacketization.
6.9.2 Delay (in one direction) introduced by IP gateways
In G711: Average delay of 100 ms for GD/GD2/GA/GA2/INTIP/INTIP2

Average delay of 71 ms for GD3/GA3/INTIP3
(60 ms for an IP Phone (e-Reflexes/ series 8))
In addition to the here above mentioned full “GD3/INTIP3” and full "GD/INTIP"
configurations, the mixed case between a GD3/GA3/INTIP3 board and a
GD/GD2/GA/GA2/INTIP/INTIP2 board will introduce the following one way average delay:
In G711 In G729 In G723

85 ms 93 ms 130 ms
Transit in INTIP boards: approx. 20 ms (there is no transit in G711)

Note: All the figures given for the delay have been measured in a case without
background noise and IP disturbance.

6.9.3 Delay (in one direction) from an IP Phone towards a set behind ACT or eMG
For GD/GD2/GA/GA2/INTIP/INTIP2 boards:

In G711 In G729 In G723
approx. 80 ms approx. 100 ms approx. 120 ms
For GD3/GA3/INTIP3 boards:

In G711 In G729 In G723
approx. 71 ms approx. 72 ms approx. 95 ms
6.9.4 ABC-F2 compatibility depending on the hardware and the type of configuration
used (with or without compressed voice)
The table in paragraph 6.9.4.2 presents cases of connection allowing an acceptable

audio quality to be obtained (greater than index 3 of the MOS). The prohibitions in the
table are not linked to problems setting up calls, only to obtaining an acceptable audio
quality.
In this table you will find a summary of the different configurations authorized in ABC-F2
(from an audio point of view) between Releases 5.1 and 9.1. This table takes into account
both a connection in VoIP and a T2, T0 or T1 type wire connection.
6.9.4.1 Rules used in the tables
Note
In this document, "Direct RTP" corresponds to "Direct RTP in network".
 A maximum delay of 200 ms "One way" (one way, IP equipment + network) is
authorized through IP (400 ms in Round Trip Delay). Beyond that, voice quality
deteriorates.
 There can not be more than two passages in G711 during a call.
 The LIO P/B/X boards are prohibited once there are Media Gateway boards (except in
certain cases where the connection is made through a Crystal IP Media Gateway).
 The LIOE are not supported since Release 6.0 nor on any node of a network
cohabiting with Release 7.1 (whatever their versions even they allow it) minimum.
 H323 terminals are only compatible with configurations which allow to have a
maximum delay of 200 ms "One way".
 Direct RTP is available for H323 equipment and all OmniPCX Enterprise Gateways
(GDx, GAx, INTIPx) for voice and Fax T38.
 The management of H323 direct RTP on OmniPCX Enterprise must be carefully
enabled since all H323 terminals of the installation must be able to reroute the H245
RTP flow called "Empty Terminal Capability Set" or "Voice Path Replacement".
 In ABC-F networked configuration, all the nodes must be in Release 7.1 minimum to
benefit the direct RTP for H323 terminals on all the nodes.
 No direct RTP between SIP set and a H323 terminal.
 No direct RTP between H323 terminals with different compression algorithms (for
instance case of H323 terminal in G723 or G729 calling a 4645 in G711).
 Only a single compression & decompression is authorized with GD/INTIP boards (use
of the G723/G729 algorithm and one or two transits). Two
compressions/decompressions are authorized only in cases of a call on VPN overflow
(only used in an emergency).
 In configuration full GD3/GA3/INTIP3, a double compression & decompression will
correspond to a MOS of 3.4 (resp. 3.6) in G729 (resp. G723). Configurations with more
compression & decompression will lead to a one way delay higher than 200 ms and
thus are not authorized.
 In mixed configurations, ie with IP connections between GD3/INTIP3 and GD/INTIP
boards, only a single compression & decompression is authorized in case G723 is
used, due to delay considerations. In case of G729, a double compression &
decompression will correspond to a MOS of 3.4. In this last case, configurations with
more compression & decompression will lead to a one way delay higher than 200 ms
and thus are not authorized.
 In case of TDM link between two nodes, in order to limit the number of
compression/decompression when sets of both nodes are involved in MyTeamwork
conferences (and keep an acceptable voice quality), it is required to use G711
between the TDM link and MyTeamwork server (mandatory rule).
 The table takes into account configurations using the G723/G729
compression/decompression algorithm or configurations that do not use compression
or which are in G711.
 With the IP rack server, there are considered to be at least two IP items of equipment
(1 GD + 1 IP Phone or 2 GDs).
6.9.4.2 Table of ABC-F2 compatibility
In case a Release 9.1 node (I1.605.14.e minimum) or more a recent release is connected
in VoIP ABC-F2 (with or without compression) with another node in Release lower or equal
to Release 9.1, there is no restriction as the Direct RTP in network is used.
The following table refers to the use of a TDM (T0/T1/T2) link between a Release 9.1 (or
more a recent release) node and another node in Release lower or equal to Release 9.1.
(1) In case Crystal IP (ACT) Media gateway with INTIP boards is present on both nodes,
transit function can be used and thus the configuration is authorized. In all other cases, it
is not authorized, except if Crystal IP (ACT) Media Gateway with INTIP can be added in
order to use transit function.
(2) In case the TDM access is declared on a GD3/INTIP3 Media Gateway, there is no
restriction. Otherwise, if the TDM access is declared on a non GD3/INTIP3 Media Gateway
and there is another non GD3/INTIP3 Media Gateway in this node, the configuration is not
authorized (too important one way delay) unless the transit function can be used (case of
INTIP).
Notes:
1. In the here above table, non NGP stands for GD/GD2/GA/GA2/INTIP/INTIP2 and NGP
for GD3/GA3/INTIP3. “Mix” corresponds to a node with a mix of NGP and non NGP
Media Gateways (Common hardware and/or Crystal).

2. As a general remark, in case of nodes linked with TDM link, it is recommended,
when it is possible, to declare the access of this link on Crystal IP (ACT) Media
Gateway with exclusively INTIP board, in order to benefit from the transit function
of INTIP (reminder: this function is not present on INTIP3).
 If the ACT, where the TDM access is declared, contains a mix of INTIP and INTIP3
(and on the other node, the access is declared on an ACT with INTIP or a mix of
INTIP and INTIP3), as all compressors are considered as part of a single set, transit
function will be available only if a compressor on INTIP is used. Otherwise a
compression / decompression or packetisation / depacketisation will be done due
to the use of the INTIP3. In the above table, for this specific configuration, refer to
the INTIP3 case.
6.9.5 USB Key compatibility for CPU7-2, Appliance Server and Blade Server
USB keys are compatible with the CPU7 step2, Appliance Server and Blade Server only.
This is available from OmniPCX Enterprise R7.1 Release.
6.9.6 Common hardware compatibility
Mix of GD3/GA3/PowerMEX with old GD/GD2/GA/GA2/MEX is not allowed in the same MGW (main
and extension racks).
6.9.7 IOIP hardware compatibility
IOIP can only be used on INTIP2.
7. TERMINAL COMPATIBILITY
7.1 WIRED TERMINAL COMPATIBILITY

7.1.2 UA 2G & Reflexes Terminals
OmniPCX Enterprise
Phase R6.0/R6.0.1/R6.1/R6.1.1/R
out 6.2/R7.0/R7.1/R8.0/R8.0.1/
Terminal Type status * R9.0/ R9.1/R10.0 Notes
UA 2G sets Out S -
See minimum
condition on
UA 2G subdevices Out S subdevices PROM
UA 3G sets
First 4004). Easy (4010) Out S -
UA 3G sets
Premium (4020). Advanced
(4035) Out S -

7.1.3 Dedicated Attendant Terminals
OmniPCX OmniPCX OmniPCX

Phase OmniPCX Enterprise Enterprise Enterprise Enterprise
Terminal out R6.0/R6.0.1/R6.1/R6.1 R8.0/R8.0.
Type status * .1/R6.2/R7.0/R7.1 1 R9.0/R9.1 R10.0 Notes
4048 Out S N N N -
4049 Out S S S S
7.1.4 Options and interfaces for Reflexes/e-Reflexes
Options and Interfaces for Reflexes/e-Reflexes

OmniPCX Enterprise
Phase R6.0/R6.0.1/R6.1/R6.
out 1.1/R6.2/R7.0/R7.1/R OmniPCX
status 8.0/ Enterprise
Terminal Type * R8.0.1 R9.0/R9.1/R10.0 Notes
See minimum
Supported only with all Supported only with condition on
4097 TSC DECT Out 3G sets all 3G sets subdevices PROM
TSC IP (4098 RE) Out N N -
4052 ISDN remote
extender Out S N -
4051 ISDN local extender Out S N -
Cannot be
4088 Empty terminal connected behind
adaptator Out S S 9 serie terminals
Cannot be
connected behind
4093 CTI-V24 Out S S 9 serie terminals
Cannot be
connected behind
4094 S0 Out S S 9 serie terminals
Cannot be
connected behind
4095 Analog port Out S S 9 serie terminals
Alcatel-Lucent S0
Interface module - Y Y
Alcatel-Lucent AP
Interface module - Y Y
Ref : 3GV27015 AB
(or VA for
V24/CTI Interface module - Y Y Operators)
4090M Addon 20 Out S S -
4090L Addon 40 Out S S -

Note1 : Interoperability status is as follow
R7.0/R7.1/R8.0/R8.0.1
R< 7.0
OmniPCX Enterprise R9.0/R9.1/R10.0
Device with With single with With single
Reflexe Series -9 connexion Reflexe Series -9 connexion
Alcatel-Lucent 4095 AP S N S S N S
Alcatel-Lucent Analogue
X N X X X X
interface module
Alcatel-Lucent 4094 ISW S N S S N S
Alcatel-Lucent S0 interface
X N X X X X
module
Alcatel-Lucent 4093 CTI S N S S N S
Alcatel-Lucent V24/CTI
X N X X N X
interface module
Alcatel-Lucent 4091CTI access S N S X N S
Assuming the following conventions:

 With Reflexe: the related sub-device and the terminals are connected to OmniPCX
Enterprise by a single UA device
 With –9 series: the related sub-device and the –9 series terminal are connected to
OmniPCX Enterprise by a single UA device.
 Single connection: a single UA device is dedicated to the connection of the sub-device
Also:
 S: supported, the configuration can be installed or is maintained in the related
configuration
 X: Item is available in the Alcatel-Lucent catalogue and can be installed in the related
configuration.
7.1.5 Options for 8 & 9 series and Reflexe Terminals
Options for 8 & 9 series and Reflexe Terminals

OmniPCX Enterprise
OmniPCX R6.0/R6.0.1/R6.1/R6.1
Phase
Enterprise R5.1 / .1/
Terminal Type out Notes
R5.1.1 / R6.2/R7.0/R7.1/R8.0/
status *
R5.1.2 R8.0.1/R9.0/R9.1/R10.
0
External
ringing
Interface
- Yes Yes  3GV28050AA 
module
 The item 3BD11068AB is not compatible with OXE releases > R8.0.1

7.1.6 e-reflexes terminals
e-reflexes terminals
OmniPCX
Enterprise OmniPCX Enterprise
Phase R5.1 / R6.0/R6.0.1/R6.1/R6.1.1/ OmniPCX
out R5.1.1 / R6.2/R7.0/R7.1/R8.0/R8.0. Enterprise
Terminal Type status * R5.1.2 1 R9.0/R9.1/R10.0 Notes
Supported
TSC IP v1s only with all Supported only with all 3G
(4098 FRE) Out 3G sets sets N
e-Reflexe
(IP PHONE V2) Out S S S

7.1.7 e-reflexes and Alcatel-Lucent 8 and 9 series
e-reflexes and Alcatel-Lucent 8 and 9 series

OmniPCX
OmniPCX Enterprise
Enterprise R7.1/R8.0/
Terminal Type Enterprise Enterprise Enterprise Enterprise
R6.0 / R8.0.1/R9.0
R6.1 R6.1.1 R6.2 R7.0
R6.0.1 /
R9.1/R10.0
Alcatel-Lucent IP Touch
No No No No Yes Yes
4008
No No Yes Yes Yes Yes
4018
No Yes Yes Yes Yes Yes
4028
Yes Yes Yes Yes Yes Yes
4038
Yes Yes Yes Yes Yes Yes
4068
A-L IP Touch 4008 EE No No No No Yes Yes (1) (2)
A-L IP Touch 4018 EE No No No Yes (1) Yes Yes (1) (2)
A-L IP Touch 4028 EE No No No Yes (1) Yes Yes (1)
4068 IP-Touch Handset
No No No Yes Yes Yes
Blue-tooth V1.2
4068 IP-Touch Gigabit
No No No Yes Yes Yes
Handset Blue-tooth
Alcatel-Lucent 4019 No No Yes Yes Yes Yes
Alcatel-Lucent 4029 No Yes Yes Yes Yes Yes
Alcatel-Lucent 4039 No Yes Yes Yes Yes Yes
Alcatel-Lucent 8 & 9
series Yes Yes Yes Yes Yes Yes
10 keys module
series Yes Yes Yes Yes Yes Yes
40 keys module
series No Yes Yes Yes Yes Yes
Smart display module
(1) Minimum version level for R6.2/R7.1/R8.0 to be used for this Extended Edition series. Refer
to Technical communication
(2) Can be used as IP touch or SIP device from R9.1.
7.1.8 MyICTouch 8081

Alcatel-Lucent MyICTouch 8082 is introduced in OXE R10.0 for Hospitality environment only. It
cannot used as business set. This set requires use of 8770 in place of former 4760 (set
deployment and configuration).

7.1.9 OmniTouch 4135
OmniTouch4135
OmniPCX Enterprise OmniPCX Enterprise

Terminal Type
R6.0 – R9.0 R9.1 / R10.0
OmniTouch 4135 No Yes
7.1.10DECT System and Terminals
DECT System
OmniPCX Enterprise OmniPCX Enterprise
DECT SYSTEM R6.0 / R6.0.1/R6.1/R6.1.1/ R8.0/R8.0.1/R9.0/R9.1/R1 Notes
R6.2/R7.0/R7.1 0.0
Radio coverage GAP
Compliant used with (1) (DECT4HB/DECT8
Y(1) Y(1)
Alcatel-Lucent 407x required)
GAP terminals
4070 IBS Y Y
4070IO EX IBS
Y Y
EXPLOSION PROOF
4070IA RBS INDOOR
Y Y
EUROPE
4070IO IBS INDOOR N Y
US
4070EO IBS N Y
OUTDOOR US
DECT Terminals
Enterprise Enterprise Enterprise Enterprise
R6.0 / R9.0/R9.1/10.
Phase- R6.0.1 R6.1/R6.1.1/ R8.0/R8.0.1 0
out R6.2/R7.0/R7.
DECT Terminal Status 1
4074 series Out S S S N
4073GS PWT - Y Y Y N
Mobile Reflexe 100 & 200 - Y Y Y Y
MOBILE 200EX SET INT. Y Y Y Y
MOBILE 100 SHIFTED SET
CHINA Y Y Y Y
MOBILE 100 SET SHIFTED
FREQUENCY LAT.AM. Out S S S S
MOBILE 300 REFLEXES N Y Y Y
MOBILE 400 REFLEXES N Y Y Y
MOBILE 300EX REFLEXES N Y Y Y
Note: OmniPCX Enterprise/OmniPCX 4400 radio DECT infrastructure is GAP compliant.

This does not imply that any third party GAP handset is able to work with OmniPCX
Enterprise/OmniPCX 4400 call handling due to the GAP standard. Such support should be
announced for specific handset models or vendors through the Alcatel-Lucent Application Partner
Program.

7.1.11Wireless LAN terminal
Wireless Lan Terminal
OmniPCX OmniPCX OmniPCX OmniPCX OmniPCX

Enterprise R6.0 / Enterprise Enterprise Enterprise Enterprise
R6.0.1 R6.1 /R6.1.1/R6.2 R7.0/R7.1 R8.0/R8.0.1 R9.0/R9.1/R10.0
R2.x (109.025) R2.x (109.025) R2.x (109.025)
Spectralink R1.0 R1.1.1 (99.25)
(Note 1) (Note 1 ) (Note 1 )
Mobil Ip Touch
S S S S S
300
Mobil Ip Touch
S S S S S
600
Mobil Ip Touch
N N Y (Note 2) Y Y
310
Mobil Ip Touch
N N Y (Note 2) Y Y
610
OmniTouch8018 Y
N N N N
OmniTouch8028 (Note 3)
Note1 : With the R7.x releases, only the Executive mode is Supported. The Remote Extension
mode is no more supported.
Note2 : Only supported from R7.1.
Note3 : Loudspeaker audio routing supported only in OXE R10.0.
8. ALCATEL-LUCENT ENTERPRISE/4400 RELEASE

UPGRADES: IMPACT ON THE 4400 SYSTEM COMPONENTS
AND APPLICATIONS
System hardware upgrade is defined by the last ACTIS released according to the existing
configuration provided by relevant MAO files.
No other method should be used to define such upgrade.
For specific information about migration from OmniPCX 4400 to OmniPCX Enterprise, refer
to the Pre-sales Communications document "OmniPCX 4400 evolution to OmniPCX
Enterprise 5.1" and "OmniPCX 4400 evolution to OmniPCX Enterprise 6.0" .
9. OMNIPCX APPLICATIONS
General policy regarding to PC platform
The Alcatel-Lucent eND catalog contains various PC workstations and server platforms,
which are tested on the OmniPCX applications.
It is strongly recommended that the Alcatel-Lucent PC platform be sold with
Alcatel-Lucent eND applications.
When using or re-using a customer PC platform to run an Alcatel-Lucent application, it is
the responsibility of the Business Partner to check the compatibility and validity of such
software on the target system in a standalone configuration.

10. ALCATEL-LUCENT OMNIDESKTOP PLATFORM
10.1 ALCATEL-LUCENT 4058/4059 HARDWARE AND SOFTWARE

COMPATIBILITY
10.1.1Windows compatibility
Windows Windows
Window
Windows Windows NT 4 Windows Windows Windows Windows Windows 7
s
95 98 work 2000 ME XP-SP2 XP-SP3 VISTA 32-bit
3.11
station Professional
4058 rel.
Yes Yes No No No No No No No No
2.12.X
4059
No Yes No Yes Note 1 No Note 2 No No No
4.14.x MAC 4
– 4059 BLF No Yes No Yes Note 1 No Note 2 No No No
4.15.x 4059
No Yes No Yes No No No No No No
MGT
4059
No No No No Yes No Yes No No No
4.16.x MAC
4059 BLF No No No No Yes No Yes No No No
4059
No No No No No No Yes No No No
5.0.x – MAC
4059 BLF No No No No No No Yes No No No
4059 Yes
No No No No No No Yes No No
MAC (Note 4)
Yes Yes
5.1.x – 4059 BLF No No No No No No Yes No
(Note 4) (Note 3)
Yes Yes
4059 IP No No No No No No Yes No
(Note 4) (Note3)
4059
No No No No No No Yes Yes Yes No
MAC
5.2.x –
4059 BLF No No No No No No Yes Yes Yes Yes
4059 IP No No No No No No Yes Yes No Yes
Note 1: As of release 4.14.9 Note 3: As of release 5.1.1

Note 2: As of release 4.15.3 Note 4: As of release 5.1.4
See also the "File and Version list for 4059 MMK management" document (Docman
reference : 3BA_29000_2784_XXZZA) for localization details.

Minimum PC configuration
Recommended
Disk
CPU RAM size Alcatel-Lucent
space
server
Not supported in
OmniPCX
4058/4812 Pentium 133 32Mb 1.2 Gb
Enterprise
R6.0/R6.0.1/R6.1
128 Mb Configured by
4058 migration Pentium 400 256 Mb 1Gb 4 Gb
Windows 95 ACTIS (PC4)
Windows Windows
4059 Windows Configured by
Pentium 400 2000 XP-SP2 4 Gb
MAC/BLF/MGT NT4 ACTIS (PC4)
1 GHz
4059 BLF/IP 32-bit 1Gb 15GB
Windows7 (x86)processor
Note :
 The operation of, and the technical support for, the Alcatel-Lucent 4059 is
guaranteed only on the following types of PC:
- hp dc7600/7700/7800 (orderable)
Note: hp dc7900 new serie will be available from December 2008
- hp dc7100 (no more orderable)
- hp Compaq EVO D530 SFF/CMT (no more orderable)
- Compaq EVO D510 SFF/CMT (no more orderable)
- hp VL Series 8 (VLi8), hp VL400 , hp VL410 (no more orderable)
- Compaq Deskpro (no more orderable)
 For the correct operation of the Alcatel-Lucent 4059 application, the Hewlett
Packard - Compaq manufacturer made modifications in Bios of the models listed
above in order to take into account specificities of the keyboard of the Alcatel-
Lucent 4059 application.
 Business Partners can:
- either buy the Alcatel-Lucent 4059 application with PC integrated at the factory,
- or buy only the Alcatel-Lucent 4059 application to install it on a PC of the same
model as those above bought in the trade.
In both cases, Alcatel-Lucent ensures the Technical Support.
 Minimum PC configuration for 4059 on Windows 7 32bit professional:
1 GHz (or higher) 32-bit (x86)processor
1 GB (or higher) of system memory
40 GB hard drive with at least 15 GB of available space
Support for DirectX 9 graphics with:
WDDM Driver
128 MB of graphics memory (minimum)
Pixel Shader 2.0 in hardware
32 bits per pixel
DVD-ROM drive
Audio Output
10.1.2Migration memo
From 4058 to 4059 "Migration" Items to be ordered:

 4059 CD-ROM

(for migration software)
 PC upgrade if necessary
Win OS upgrade to be done if the
application ran under w3.1x
Items to be ordered:
 Migration Package
From 4058 to 4059 (including Multimedia Keyboard)
 PC & OS upgrade if necessary
No migration is available from 4812 BLF to 4059 BLF related service.
10.1.3Related services
When installing a 4059, attendant training should be discussed with the customer.
10.2 OMNITOUCH UNIFIED COMMUNICATIONS / INSTANT

COMMUNICATIONS SUITE HARDWARE AND SOFTWARE COMPATIBILITY
 Get more details in OmniTouch UC Feature List R3, R4, R5, R6 (“HW & SW requirements” tab)
and OmniTouch Instant Communication Suite R6
10.2.1OmniTouch Unified Communication 3.0 compliant platforms (server side)

Technical communication TC0638 describes the Compliant platforms (server side) with OmniTouch
UC R3.0.
10.2.2OmniTouch Unified Communication 4.0 & 4.1 compliant platforms (server side)
Technical communication TC0790 describes the Compliant platforms (server side) with OmniTouch
UC R4.0.
10.2.3OmniTouch Unified Communications 5.0 compliant platforms (server side)

Technical communication TCxxx describes the Compliant platforms (server side) with OmniTouch
UC R5.0 & R5.1
10.2.4OmniTouch Unified Communications 6.0 compliant platforms (server side)

Technical communication TCxxx describes the Compliant platforms (server side) with OmniTouch
UC R6.x
10.2.5OS server compatibility

Windows 2000 Windows 2003
Linux
Professional/Serv Professional/Serv
Red Hat
er er
Unified
Communication
Yes for My Phone Yes for My Phone Linux
R3.0: My Assistant, My
application only application only Red Hat 7.3
Messaging and My Phone
applications
Unified
Linux
Communication R3.0 : My No No
Red Hat 9.0
Teamwork application
Unified
Linux
Communication
Yes for My Phone Yes for My Phone Red Hat
application only application only Enterprise ES v4
(*)
applications

Unified
Linux
Communication R4.0 : My No No
Red Hat 9.0
Teamwork application
Unified
Linux
Communication
Yes for My Phone Yes for My Phone Red Hat
application only application only Enterprise ES v4
(*)
applications
Unified Linux
Communication R4.1 : My No No Red Hat
Teamwork application Enterprise ES v4
Linux
Unified
Red Hat
Communications No No
Enterprise ES v4
R5.0
(*)
Linux
Unified
Red Hat
Communications No No
Enterprise ES v4
R5.1
(*)
Linux RedHat
Instant Communication
No No Enterprise ES v5
Suite R6.0
(*)
Linux RedHat
Suite R6.1
(*)
Linux RedHat
Suite R6.2
(*)
(*) Hardware agnostic. To check that your OmniTouch UC server is a Red Hat Enterprise Linux ES certified platform, use
the Red Hat Hardware Catalogue (a database containing certified and compatible hardware for Red Hat products) at
following URL: http://bugzilla.redhat.com/hwcert .
 Get more details in OmniTouch UC Feature Lists (“HW & SW requirements” tab).
10.2.6Mail Servers OS and 46x5 version compatibility
Mail Mail
Voice
Server Server Mail Server Voice Mail
Mail
Microsoft IBM Lotus IMAP4 4645
4635
Exchange Domino
Domino R5 & R6
Unified
Exchange / Exchange
Communication R3.0 & R4.0: Domino R5.2.x >=OXE
2000 and 2000 & 2003 /
My Assistant, My Messaging and R5, R6 (*) R5.1.2
2003 IMail R8.x,
My Phone applications
GroupWise R6.0
Domino R5, R6
& R7 / Exchange
Unified 2000 & 2003 / R5.2.x
Exchange Domino
Communication R4.1: My IMail R8.x, (*) >=OXE
2000 and R5, R6 and
Assistant, My Messaging and My GroupWise R6.0, R5.1.2
2003 R7(*)
Phone applications qmail 1.0.3 And 5.3
under Debian
GNU/Linux OS

Domino R6 &
R7 / Exchange
2000 & 2003 /
Exchange
Unified Domino IMail R8.x, R5.2.x >=OXE
2000 and
Communications R5.0 R6 and R7 GroupWise R6.0, (*) R5.1.2
2003
qmail 1.0.3
under Debian
GNU/Linux OS
Domino R7 &
R8 / Exchange
2000 & 2003 /
Exchange
Unified Domino IMail R8.x, R5.2.x >=OXE
2000 and
Communications R5.1 R7 and R8 GroupWise R6.0, (*) R5.1.2
2003
qmail 1.0.3
under Debian
GNU/Linux OS
Exchange
Instant Communication Suite Domino R7 R5.2.x >=OXE
2003 and See Feature List
R6.0 and R8 (*) R5.1.2
2007
Exchange Domino R7
Instant Communication Suite R5.2.x >=OXE
2003 and and R8, See Feature List
R6.1 (*) R5.1.2
2007 R8.5
Exchange Domino R7
Instant Communication Suite R5.2.x >=OXE
2003 2007 and R8, See Feature List
R6.2 (*) R5.1.2
and 2010 R8.5
(*) Refer to the latest Technical Release Notes documents for the version(s) that must be used.
 Get more details in OmniTouch UC Feature Lists (“HW & SW requirements” tab).
10.3 OMNITOUCH MY TEAMWORK HARDWARE AND SOFTWARE

COMPATIBILITY
Compliant platforms (server side)
Linux
Red Hat
er er
Linux
My Teamwork standalone
No No Red Hat
application R5.x
Enterprise ES v4
Linux
No No Red Hat
application R6.0
Enterprise ES v5
Linux
No No Red Hat
application R6.1
Enterprise ES v5
Linux
No No Red Hat
application R6.2
Enterprise ES v5

10.4 OMNITOUCH AUTOMATED MESSAGE DELIVERY SYSTEM (AMDS)
HARDWARE AND SOFTWARE COMPATIBILITY
OS server compatibility
Linux
Red Hat
er er
Linux
Red Hat
AMDS R3.2 No No
Enterprise ES
v4
Linux
Red Hat
AMDS R5.0 No No
Enterprise ES
v4
Linux
Red Hat
AMDS R5.1 No No
Enterprise ES
v4
Linux
Red Hat
AMDS R6.0 No No
Enterprise ES
v5
Linux
Red Hat
AMDS R6.1 No No
Enterprise ES
v5
Linux
Red Hat
AMDS R6.2 No No
Enterprise ES
v5
10.5 OMNITOUCH FAX SERVER

Compliant platforms
Linux
Red Hat
Linux
Omnitouch Fax Server R5.0 Red Hat Enterprise ES
v4
Omnitouch Fax Server Linux RHES 4, 32

R5.6.3 bits (not 64 bits )
Omnitouch Fax Server Linux RHES 5, 32

R6.0.1 bits (not 64 bits )

Linux RHES 5, 32
Omnitouch Fax Server R6.1
bits (not 64 bits )
Linux RHES 5, 32
Omnitouch Fax Server R6.2
bits (not 64 bits )
10.6 ALCATEL-LUCENT TAPI PREMIUM SERVER

Windows compatibility (Server)
Windows
Windows Windows Windows Windows
NT 4 Server
95/98/ME XP 2000 Server 2003 Server
(Note 2)
TAPI PREMIUM Yes
No/No/No No No Yes
server R3.3.4 (SP 4 minimum)
Remark: On PC client side, TAPI Server R3.3.x supports Windows

XP(SP2)/2000(SP4)/2003Server.

10.7 ALCATEL-LUCENT TSAPI PREMIUM SERVER
OS compatibility (Server)
Windows Windows
Windows Windows NT 4 2000 Srv/
Linux
95/98/Me XP workstation/ 2003 Srv /
Server 2008 Srv
TSAPI R4.x No/No/No No No Yes / No / No No
Yes
TSAPI R5.x No/No/No No No Yes / No / No
(Red-Hat 7.3)
Yes
TSAPI R6.0 No/No/No No No Yes / Yes / No (Red-Hat 7.3 &
ES 4.x)
Yes
TSAPI R6.4.x No/No/No No No No / Yes / Yes (Red-Hat ES
4.x)
Note: For R6.4.x the minimum hardware requirements are as follows:

Pentium IV 2GHz, 1GB RAM with 200 MB free Disk space.
Remark: On PC client side, TSAPI Client R6.4.x supports Windows XP / 2003 Server / Linux
Redhat 4.x ES.
10.8 OMNITOUCH 8410 INSTANT COMMUNICATIONS WEB SERVICES: OS

COMPATIBILITY SERVER (SERVER)
Windows
Windows Windows NT 4 Windows
Linux
95/98/Me XP workstation/ 2000 / 2003
Server
API framework No / Yes Yes

No/No/No No No
R2.x (SP1) (Red-Hat 7.3)
API framework No / Yes Yes

No/No/No No No
R3.x (SP1) (Red-Hat Es 4.0)
Yes
API framework
No/No/No No No No / No (Red-Hat ES
R5.x
4.x)
Yes
API framework
No/No/No No No No / No (Red-Hat ES
R6.x
5.x)

10.9 OMNITOUCH 8440 MESSAGING SOFTWARE
Compliant platforms
Linux
Red Hat
Omnitouch 8440
Linux RedHat
MESSAGING SOFTWARE
Enterprise ES v5
R6.x

11. ALCATEL-LUCENT OMNIMESSAGE APPLICATION
11.1 ALCATEL-LUCENT 4635H HARDWARE AND SOFTWARE

COMPATIBILITY
11.1.1Boards versus release compatibility
OmniPCX Enterprise Release

OmniPCX Enterprise Release
4635H R6.0 / R6.0.1/R6.1/R6.2/R7.0/R7.1/
R5.1 / R5.1.1 / R5.1.2
R8.0/R8.0.1/R9.0/R9.1/R10.0
SPA3 Yes Yes
MSBI Yes Yes
VPM 35 with 64 MB
Yes Yes
from 4.0.4 to 5.2.6
11.1.2Minimum configuration
4635H RAM size Disk
1.4 GB IDE
Release 4 32 MB
(Note 1)
1.4 GB IDE
Release 4 & VPIM 64 MB
(Note 1)
64 MB
Release 5 (to support VPIM 2.16 GB
and /or IMAP4)
Most systems from R1.3.z were shipped with 2.16 GB disk drives.
6 GB hard disks are fully supported from R3.0.3 onwards (voice storage capacity is
unchanged).
Note 1: Product limits on number of languages and capacity

11.1.3Migration memo
4635H To 4635 H-2 release 4.0 minimum
 VPCPU replacement with VPM35

 INT1 replacement with INTOF (see remarks)
 MSB replacement with MSBI if more than one disk
From 4635H release 1.x
 SCSI disks replacement with ATB2 or ATB3I connector
 Disk conversion (a VPCPU-1 board is needed as tool for
this conversion)
 VPCPU replacement with VPM35
From 4635H-1 release  INT1 replacement with INTOF (see notes)
1.x
 MSBI board could be required depending on the number of
original system disks
Notes:
VPM35 cannot be used to upgrade existing 4635H systems using INT1 boards.
Mandatory replacement of INT1 with INTOF or moving the 4635 to the main
crystal is required.
Alcatel-Lucent 4635 release 2 needs 32 Mb RAM, regardless of the number of ports.
11.1.4Recommendation and requirement

Recommendation is to migrate toward Alcatel-Lucent 4635H R4.1, shipped since March
2002.

11.2 ALCATEL-LUCENT 4635J HARDWARE AND SOFTWARE COMPATIBILITY
11.2.1Boards versus release compatibility

Enterprise Enterprise Enterprise Enterprise
4635J Releases Releases Releases Releases Release
R5.1/R5.1.1/ R6.0 / R6.0.1 R6.1/R6.2 R7.0/R7.1
R5.1.2
VPS35 with 32 MB From 4.0.4 to
Yes Yes No No
RAM 5.3.0
From 4.1.5 to
8 port VPU 5 board Yes Yes Yes Yes
5.3.0
From 5.0.1 to
16 ports VPU5 Yes Yes Yes Yes
5.3.0
11.2.2Minimum configuration
4635J RAM size Disk
Release 4 32 MB 1.4 GB
64 MB
Release 5 (to support VPIM 2.16 GB
and /or IMAP4)
Most systems were shipped with 2.16 GB IDE disk drives.

6 GB hard disks are fully supported from 3.0.3 onwards (voice capacity is
unchanged).
11.2.3Migration
R1 to R4, memory expansion from 16 MB to 32 MB minimum.

11.3 VISUAL MESSENGER HARDWARE AND SOFTWARE COMPATIBILITY
11.3.1Server SW compatibility
Windows NT Windows XP
Windows NT Windows Windows
4
4 server 2000 Pro 2000 Server
workstation
Access Yes Yes Yes Yes
No
Server (SP4 min.) (SP4 min.) (SP3) (SP3)
11.3.2Client SW compatibility
Windows NT
Windows Windows Windows Windows
4
95/98 2000 ME XP
workstation
Visual
Yes Yes Yes (*) No Yes
Messenger
(*) Available from Visual Messenger R2.008 01 onwards.
11.3.3Application SW compatibility
Internet
4980 Outlook Notes Netscape
Explorer
97/98/2000/20
Visual
R2 min 02 (XP) (Note 4.6/5.0 NA NA
Messenger
1)
Note 1: Outlook XP to be defined.
11.3.4Recommended server PC configuration
Alcatel-Lucent server to
RAM Disk be
CPU
size space configured on new order
(Note 1)
Pentium
Access Server for less than Server Pack 1
III 128 MB 2 GB
1000 users Win-NT4 w/s EN
300 MHz
Pentium
Access Server for more than Server Pack 1
III 256 MB 4 GB
1000 users Win-NT4 w/s EN
500 MHz
Note 1: Specification of Alcatel-Lucent server pack or PC platform is subject to evolution
to match standard of PC market. Specification of PC server 4 in ‘98 is not the same as in
’00.
11.3.5Recommended client PC configuration
RAM size
CPU Windows WNT4 Disk space
95/98 Workstation
Pentium
Visual Messenger 32 MB 64 MB 50 MB
133 MHz

12. OMNIVISTA 4760 HARDWARE AND SOFTWARE
COMPATIBILITIES
12.1 OMNIVISTA 4760 R4.0/R4.1

Minimum hardware configuration:
Server small Server medium Server high
Model Client
capacity capacity capacity
Capacity (users) < 250 250 - 5,000 > 5,000
Processor 766 MHz 2 GHz 2,4 GHz Dual 3 GHz
Monitor 17" (19" recommended)
72 GB - 15 K rpm
- RAID5 with 128
Hard disk 3 GB 18 GB 18 GB
KB cache
memory
RAM 384 MB 512 MB 1 GB 2 GB
Graphic board VRAM: 4 MB supporting 1024x768 resolution, 16 M color
PFartition NTFS to be able to install Netscape LDAP server
Internet browsers Internet Explorer version 6.0 and above, Mozilla, Firefox R1.0
Disk/CD-ROM Mandatory. DVD is recommended.

12.2 OMNIVISTA 4760 R4.2
Server small Server medium Server high

Model Client
capacity capacity capacity
Capacity (users) Same as Medium 1 - 5,000 > 5,000
Processor 1G Hz Same as Medium 2,4 GHz Dual 3 GHz
Monitor 17" (19" recommended)
72 GB - 15 K rpm
- RAID5 with 512
Hard disk 40 GB Same as Medium 40 GB
KB cache
memory
RAM 1 GB Same as Medium 1 GB 2 GB
Graphic board VRAM: 4 MB supporting 1024x768 resolution, 16 M color
Partition NTFS to be able to install Netscape LDAP server
Internet browsers Internet Explorer version 6.0 and above, Mozilla, Firefox R1.0
Disk/CD-ROM Mandatory. DVD is recommended.

12.3 OMNIVISTA 4760 R5.0 R5.1 R5.1.1

Minimum hardware requirements for OmniVista 4760 (3)
Common characteristics
1 internal or external DVD drive
128 MB of graphics memory
2 serial V24 interfaces (only for PPP remote connection)
1 network card (Ethernet 10/100bT)
1 screen 17" minimum
Server station (4)

OS: Windows XP® Professional SP2 from R3.2, SP3 from 5.1 (5)
OS: Windows 2003® Server Standard Edition, from R2 in 4.1/4.2, SP2 from 4.2.09
OS: Windows 7® Professionnal 64 bits (6)
OS: Windows 2008® R2 Server Enterprise Edition 64 bits (6)
Medium range Server (up to 5,000 users)

CPU: 1,6 GHz or higher
RAM: 1 GB
Hard Disk: 40 GB
High range Server (more than 5,000 users)

Dual Processor or dual core 2 GHz or higher
RAM: 2 GB (+ 1 additional GB = 3 GB if SIP Manager application installed)
Hard Disk: 80 GB (120 GB if SIP Manager installed)
RAID 5 (1 add. disk needed, 3 disks min.), 512 MB cache memory min. for the controller
Client station, access to the Administration

PC client installed on another PC than the Server is recommended for better performance
Non dedicated PC
OS: Windows XP®, SP3 from 5.1
OS: Windows 2003® Server R2 in 4760 R4.0/4.1, SP2 from 4760 4.2.09
OS: Windows 2008® R2 Server Enterprise Edition 64 bits (8)
OS: Windows Vista® (8)
OS: Windows 7® Professionnal 64 or 32 bits (8)
CPU: 1 GHz or higher
RAM: 1 GB
*Hard Disk : 40 GB
Notes :
(3) For previous 4760 versions (n-1), previous PC HW is supported with same capacity/features -
OS tested in French & English only
(4) Non dedicated PC : for software compatibilities, cf OmniVista 4760 Installation Manual
(5) Windows 2003 Server mandatory on OV 4760 Server for: PPP connectivity, more than 2
simultaneous clients and SIP Manager
(6) Win 7/2008 not supported for: OXO (except Win7 from OMC R7.x), PPP connectivity, SIP
Manager and migration from previous 4760 versions
(8) For OmniPCX Office, Microsoft Windows Vista and 7 are supported as of R7.0 - Windows 2008 is
not supported

13. OMNIVISTA 8770 HARDWARE AND SOFTWARE
COMPATIBILITIES
Minimum hardware requirements for OmniVista 8770
Common characteristics
1 internal or external DVD drive
128 MB of graphics memory
1 network card (Ethernet 10/100bT)
1 screen 17" minimum
Server station (4)

OS: Windows 7® Professionnal 64 bits
OS: Windows 2008® R2 Server Enterprise Edition 64 bits
Medium range Server (up to 5,000 users)

1 processor Dual-Core 2 GHz or higher
RAM: 4 GB
Hard Disk: 80 GB
High range Server (more than 5,000 users)

1 processor Quad-Core 2.5 GHz
RAM: 4 GB
Hard Disk: 80 GB
RAID 5 (1 add. disk needed, 3 disks min.), 1GB cache memory min. for the controller
Client station, access to the Administration

PC client installed on another PC than the Server is recommended for better performance
Non dedicated PC
OS: Windows XP® SP3
OS: Windows 7® Professionnal 64 or 32 bits
CPU: 2 GHz or higher
RAM: 2 GB
*Hard Disk : 40 GB
Notes :
(3) OS tested in French & English only
(4) Non dedicated PC : for software compatibilities, cf OmniVista 8770 Installation Manual
OXO and ppp not supported

14. BUSINESS INTEGRATED COMMUNICATION SERVER ( BICS
)
14.1 BUSINESS INTEGRATED COMMUNICATION SERVER R1.0

14.1.1Server configuration requirement
BiCS is delivered on a pre integrated appliance server ( BTCO )
IBM Server x3250 ( Mabolas )
Qt
Config. type Description
y
OS Customer provided and installed 1
Unknown or not required 1
Rack Kit 1
CPU Retention Module 1
Base Hardware 1
3.5 DASD cage 1
SATA FILLER 3.5 2
BIOS GBM 1
Front Bezel 1
Internal RAID - Cabled and Setup 1
RAID 1 - Primary Array (SATA) - 2 HDDs
required 1
4365CTO Dual
Core Xeon CD-RW/DVD Combo V Ultrabay Enhanced 1
2.13GHz 4G- 160GB 7200 RPM 3.5 Simple-Swap SATA
RAM SS SATA
HDD 2
2x160GB RAID1
Mouse Rack power cable - 2.8m, 100-240V, C13 to
IEC 320-C14 (WW) 1
2.8m, 10A/230V, C13 to CEE7-VII (Europe) 1
IBM 2 Button Optical Wheel Mouse - Black -
USB 1
Dual-Core Intel Xeon 3050
(2.13GHz/1066MHz FSB, 2MB L2) 1
1GB DDR2 667 SDRAM DIMM Memory 4
System Documentation and Software-UK
English 1
System Packaging - EMEA 1
Simple Swap SATA RAID Kit 1
x3250 System Planar 1
IBM PREFERRED PRO KEYBOARD - USB
14.1.2Software compatibilities
Product line delivered with BiCS R1.0 are:
1. OXE R8.0
2. OmniVista 4760 R4.2
3. OTCC R7.1
4. OTUC R5.0
14.2 BUSINESS INTEGRATED COMMUNICATION SERVER R2.0 , R2.1, R2.2
14.2.1Server configuration compatibility R2.0, R2.1, R2.2
BiCS is delivered on a pre integrated appliance( BTCO ) IBM Server x3250 M2 ( Maolin )
Config. type Part number Description Qty

4194CTO_43W5107 Heatsink Retention Module 1
4194CTO_43W5108 x3250 M2 Front Bezel 1
4194CTO_32P8873 Internal SATA RAID - Cabled and Setup by IBM 1
4194CTO_25P2853 Unknown or not required 1
4194CTO_39M4527 250GB 7200 RPM 3.5" Hot-Swap SATA II 2
Rack power cable - 2.8m, 100-240V, C13 to IEC
4194CTO_39Y5533 320-C14 (WW) 1
4194CTO_02R1750 OS Customer provided and installed 1
4194CTO_02R8716 Rack Kit 1
4194CTO_42C1127 3.5" DASD cage 1
4194CTO_43W5074 Base Hardware 1
BICS DC E3110
8GB 2x250GB 4194CTO_43W5073 BIOS GBM 1
4194CTO_39Y6558 2.8m, 10A/230V, C13 to CEE7-VII (Europe) 1
4194CTO_41Y2730 2GB DDR2 667 SDRAM DIMM Memory 4
4194CTO_39R8888 RAID 1 - Primary Array (SATA) - 2 HDDs required 1
4194CTO_43W5077 Hot-Swap SAS/SATA Kit 3.5" 1
4194CTO_43W8263 UltraSlim Enhanced Multi-Burner 1
Dual-Core Intel Xeon E3110 (3.00GHz/1333MHz
4194CTO_44R5766 FSB, 6MB L2) 1
4194CTO_43W5071 x3250 M2 System Planar 1
4194CTO_43W5082 System Documentation and Software-UK English 1
4194CTO_43W5079 System Packaging - WW 1
4194CTO_44T2004 Riser assembly PCI-E 1
14.2.2Additional server compatibility from R2.1.1, R2.2

Appliance server IBM x3250 M3 ( Maokong ) with Xeon X.3430 2,4GHz QuadCore
1333MHz – 8GBRAM - 2x250GB HDD S-ATA – RAID1
ref IBM:4252Z14 (replacing 4194ZAL)
Config. type Part number Description Qty

X3250M3 Quad 4252CTO_02R1750 OS Customer provided and installed 1
Core Xeon 8G-
RAM HS SATA 4252CTO_02R8716 Rack Mount Kit 1
2x250GB RAID1 4252CTO_49Y4615 BIOS GBM 1
4252CTO_49Y4624 3.5 DASD Cage 1
4252CTO_49Y4626 x3250 M3 Front Bezel (IBM) 1
4252CTO_59Y3170 System Labels GBM 1
4252CTO_32P8873 Internal SATA RAID - Cabled and Setup by IBM 1
4252CTO_39Y6558 2.8m 10A/230V C13 to CEE7-VII (Europe) 1
4252CTO_25P2853 OS Unknown or not required 1
4252CTO_39M4527 250GB 7200 RPM 3.5 Hot-Swap SATA II 2
4252CTO_39R8888 RAID 1 - Primary Array (SATA) - 2 HDDs required 1
4252CTO_39Y5533 2.8m 10A/100-250V C13 to IEC 320-C14 Rack 1
Power Cable
4252CTO_49Y4738 ServeRAID-BR10il SAS/SATA Controller v2 1
4252CTO_44T1471 2GB (1x2GB Dual Rank x8) PC3-10600 CL9 ECC 4
DDR3-1333 LP RDIMM
4252CTO_44W3252 UltraSlim Enhanced SATA CD-RW / DVD-ROM 1
Combo
4252CTO_49Y4602 Xeon X3430 2.4GHz/1333MHz-8MB 4C 1
4252CTO_49Y4610 Base Hardware with Fixed Power Supply 1
4252CTO_49Y4619 Hot-Swap SAS/SATA Kit 2x3.5 1
4252CTO_49Y4621 Riser Assembly PCI-E 1
4252CTO_49Y4628 System Packaging - WW 1
4252CTO_49Y4631 System Documentation and Software-UK English 1
14.2.3Software compatibilities R2.0
Based on Red Hat Linux 4.0 U7 Enterprise and VMware server 1.0.7,
BiCS R2.0.1 contains the following product lines :
Product Line Release

OXE_RELEASE 9.0_H1.301.24
nmc4760_RELEASE 5.0.07.02.b
CCx_RELEASE 8.0.8.5
OTUC_RELEASE 5.1.000.574
OFS_RELEASE 5.6.3-25
DMS_RELEASE 1.0.000.060
14.2.4Software compatibilities R2.0.1
Based on Red Hat Linux 4.0 U7 Enterprise and VMware server 1.0.9,

OXE_RELEASE 9.0_H1.301.28.b
nmc4760_RELEASE 5.0.07.05.c
CCA_RELEASE 9.0.8.0
CCS_RELEASE 9.0.90.1
OTUC_RELEASE 5.1.000.582
OFS_RELEASE 5.6.3-27

Based on Red Hat Linux R5.0 ES U3 and VMware server 2.0.1,
BiCS R2.1 contains the following product lines :
OXE_RELEASE 9.0_H1.301.34
nmc4760_RELEASE 5.1.04.00.b on Windows 2003 R2 SP2
CCA_RELEASE 9.0.8.1
6.0.000.683.b AND
Hotfix_6.0.000.683.b.zip
Hotfix_crms00186610.zip
ICS_RELEASE Hotfix_crms00195011.tgz
6.0.1.25 AND
OFS_RELEASE hotfix 6.0.1-25a
MyTW_RELEASE 8.0.0b4583

OXE_RELEASE 9.1_H1.301.36.a
nmc4760_RELEASE 5.1.06.03.c+patch package on Windows 2003 R2 SP2
CCA_RELEASE 9.0.8.1
ICS_RELEASE 6.1.000.100.b
OFS_RELEASE 6.0.1.45
1.1.000.020
With these hotfixes:
Hotfix_DM1.1_crms00178930.zip
DMS_RELEASE ALF0001239117278570.zip


BiCS R2.2 contains the following product lines :
OXE_RELEASE 9.1_I1.605.15
CCA_RELEASE 9.0.8.1
ICS_RELEASE 6.1.000.100.b
1.1.000.020


OXE_RELEASE 9.1_I1.605.21
CCA_RELEASE 9.0.8.4
ICS_RELEASE 6.1.000.102.A
1.1.000.020

15. OMNITOUCH CONTACT CENTER SUITE OPERATING
SYSTEM AND HARDWARE COMPATIBILITIES
15.1 OPERATING SYSTEM COMPATIBILIES

15.1.1OmniTouch Contact Center Suite
See table in section 4.19.3
15.1.2OmniTouch Contact Center Premium Edition

See table in section 4.19.4
15.2 HARDWARE COMPATIBILITY: MINIMUM PC REQUIREMENT

15.2.1CCS Supervision
Alcatel-Lucent server to be
RAM size
CPU Min/rec Disk space configured on new order
Min/rec
(note 1)
CCSUPERVISION Pentium IV 2
512 MB 20GB PC platform 4
R6.0/R6.0.1 Ghz
CCSUPERVISION
Pentium IV 2
R6.1/R6.2/R7.0/R8.0 1GB 40GB PC platform 4
Ghz
/R9.0/R9.1
PC configuration is defined for up to 300 agents and 25 objects per Excel sheet
The following items are needed:
CD-ROM reader
1024x768 17 inch color monitor with small font (minimum)
Keyboard and mouse
1 LAN interface board
Excel 2003 up to Excel 2007 ( for Excel 2007 no service pack )
Use of Alcatel-Lucent PC platform is strongly recommended. It is the Business Partner’s

responsibility to check and to test the compatibility of CCSUPERVISION software on the
target machine when using another PC platform.
Note 1: Characteristics of Alcatel-Lucent server pack or PC platform is subject to evolution

to match standard of PC market. Characteristics of PC server 4 in ’98 are not the same as
in ’02.

15.2.2CCS Server
Alcatel-Lucent server to be
CPU Min RAM size Min Disk space
configured on new order
CCS Server 100 MB

Pentium IV 2 Ghz 512 MB -
R6.0/R6.0.1 available
CCS Server
R6.1/R7.0/R8. Xeon 3,4 Gigas 1GB 144 GBytes PC platform 4
0/R9.0/R9.1
15.2.3CCWallboard
WBM is installed on CCS platform - see related chapter.
15.2.4CCA PC client (agent) requirements
CPU RAM size Disk space
CCA R6.0\R6.0.1 Pentium IV 2 Ghz 512 MB 20Mb available
CCA
R6.1/R6.2/R7.0/R8.0/R9. Pentium IV 2 Ghz 512 MB 20Mb available
0/R9.1
15.2.5A4400 Call Center agent (CCA) server

Alcatel-Lucent Call Center Agent Server was formerly known as the server counterpart of
CCA. It was formerly known as Call Center Manager (CCM).
Alcatel-Lucent
CPU RAM size Disk space recommended
server
OmniPCX Enterprise
Pentium IV
CCA server R6.0 / 512 MB 1Mb available See ACTIS
2 Ghz
R6.0.1
OmniPCX Enterprise
CCA server Xeon 3,4
1GB 144 GBytes See ACTIS
R6.1/R6.2/R7.0/R8.0/R9.0 Gigas
/R9.1
15.2.6Ccweb CCemail powered by genesys

The minimum server configuration is Pentium III 1GHz / RAM: 1 GB / HD: 9 GB.
The server configuration is performed by Actis.
Remark: If for security reasons a DMZ has to be created, the different functional servers
have to be split on different hardware platforms.
MS SQL server: The minimum server configuration is Pentium III 1 GHz / RAM: 512 MB /
HD: 36 GB.

15.2.7CCemail PC platform requirement
Two dedicated server platforms are used:
CCemail server:
The minimum server configuration is Pentium III 1 GHz / RAM: 1 GB / HD: 9 GB
The server configuration is performed by Actis R4.2
MS SQL server:
The minimum server configuration is Pentium III 1 GHz / RAM: 512 MB / HD: 36 GB
15.2.8Database requirement
Data base MS SQL MS SQL 7 SP2 or MS SQL 2000 standard edition
15.2.9Ccoutbound Platform requirements

The minimum server configuration is Pentium IV 2GHz / 512 MB RAM / HD 40 GB.

16. APPENDIX
16.1 ACTUAL OMNIPCX ENTERPRISE RELEASED SOFTWARE RELEASES
As of the April 1st 2011, the following releases are available:
Commercial Maintenance
release release
R6.1.1 F2.502.33.a
R6.2 F3.301.45
R7.0 F4.401.24.b
R7.1 F5.401.36.d
R8.0 G1.302.12
R8.0.1 G1.503.31
R9.0 H1.301.42.a
R9.1 I1.605.16.c
R10.0 J1.410.27.d
End of document


La

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

La

Caricato da

Copyright:

Formati disponibili

Communication Servers Business Unit

Large Enterprise / Product Line Management

ALCATEL-LUCENT OMNIPCX ENTERPRISE

Alcatel-Lucent © 1/88 ref: 8ALxxxxxxxxxDRASA ED 00

1.1 Purpose of the document........................................................................................... 6

2.1 OmniPCX software phase-out policy..........................................................................7

3. How to use this document..............................................................................8

3.1 Which application must be migrated during OmniPCX Software upgrade?................8

4. Compliance of application versions & terminals with OmniPCX Enterprise releases

4.1 Early Alcatel-Lucent 4400 software releases............................................................10

Alcatel-Lucent © 2/88 ref: 8ALxxxxxxxxxDRASA ED 00

5. OmniPCX Enterprise Hardware compatibility.................................................29

5.1 Crystal Hardware vs Release OmniPCX Enterprise Compatibility.............................29

6. Internal compatibility issues.........................................................................43

6.1 Compression resource compatibility issues..............................................................43

Alcatel-Lucent © 3/88 ref: 8ALxxxxxxxxxDRASA ED 00

7.1 WIRED TERMINAL compatibility...............................................................................53

8. Alcatel-Lucent enterprise/4400 release upgrades: impact on the 4400 system

10. Alcatel-Lucent Omnidesktop platform...........................................................59

10.1 Alcatel-Lucent 4058/4059 Hardware and software compatibility.............................59

11. Alcatel-Lucent OmniMessage application.......................................................68

11.1 Alcatel-Lucent 4635H hardware and software compatibility....................................68

Alcatel-Lucent © 4/88 ref: 8ALxxxxxxxxxDRASA ED 00

12. Omnivista 4760 Hardware and software compatibilities.................................72

12.1 OmniVista 4760 R4.0/R4.1.......................................................................................72

13. Omnivista 8770 Hardware and software compatibilities.................................76

13.1 OmniVista 8770 R1.0............................................................................................... 76

14. Business integrated Communication Server ( BiCS ).......................................77

14.1 Business integrated Communication Server R1.0....................................................77

15.1 OPerating System compatibilies..............................................................................82

16.1 Actual OmniPCX Enterprise released software releases...........................................85

Alcatel-Lucent © 5/88 ref: 8ALxxxxxxxxxDRASA ED 00

1.1 PURPOSE OF THE DOCUMENT

1.2 IMPROVEMENTS AND ADD-ONS

Alcatel-Lucent © 6/88 ref: 8ALxxxxxxxxxDRASA ED 00

2.1 OMNIPCX SOFTWARE PHASE-OUT POLICY

2.2 TECHNICAL DOCUMENTS

Refer to the Technical Release Document edited by Alcatel-Lucent Enterprise/CSBU/TSS for

3.1 WHICH APPLICATION MUST BE MIGRATED DURING OMNIPCX

Alcatel-Lucent © 8/88 ref: 8ALxxxxxxxxxDRASA ED 00

The phase-out status of every component of the installed configuration.

Provide a quotation for:

Application upgrade according to information provided in this document.

Alcatel-Lucent © 9/88 ref: 8ALxxxxxxxxxDRASA ED 00

4.1 EARLY ALCATEL-LUCENT 4400 SOFTWARE RELEASES

4.2 ALCATEL-LUCENT 4400 R3.0

4.3 OMNIPCX 4400 R3.2/3.2M

4.4 OMNIPCX 4400 R4.1.1

4.5 OMNIPCX 4400 R4.2

4.6 OMNIPCX 4400 R5.0 UX

4.7 OMNIPCX ENTERPRISE R5.0 LX

Alcatel-Lucent © 10/88 ref: 8ALxxxxxxxxxDRASA ED 00

4.9 OMNIPCX ENTERPRISE R6.0

4.10 OMNIPCX ENTERPRISE R6.0.1

4.11 OMNIPCX ENTERPRISE R6.1 /6.1.1

4.12 OMNIPCX ENTERPRISE R6.2

4.13 OMNIPCX ENTERPRISE R7.0

4.14 OMNIPCX ENTERPRISE R7.1

4.15 OMNIPCX ENTERPRISE R8.X

4.16 OMNIPCX ENTERPRISE R9.0

Alcatel-Lucent © 11/88 ref: 8ALxxxxxxxxxDRASA ED 00

4.17 OMNIPCX ENTERPRISE R9.1

4.18 OMNIPCX ENTERPRISE R10