OMNIPC enterprice

Alcatel-Lucent © 1/72 ref: 8AL020033508DRASA

All rights reserved. Passing on and copying of this document, use and communication

of its contents not permitted without ALCATEL-LUCENT written authorization.

Communication Servers Business Unit

Large Enterprise / Product Line Management

ALCATEL-LUCENT OMNIPCX ENTERPRISE

RELEASE 9.0

APPLICATIONS/TERMINALS CROSS COMPATIBILITY




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.11 OmniPCX Enterprise R6.1 /6.1.1 ....................................................................................................11







4.18 OmniPCX Enterprise / application compatibility tables ..........................................................13 4.18.1 Call handling ......................................................................................................................13

4.18.2 OmniMessage ....................................................................................................................14

4.18.3 OmniTouch Contact Center suite ..................................................................................15

4.18.4 OmniTouch cc Premium Edition .....................................................................................16

4.18.5 Alcatel-Lucent OmniTouch Unified Communication .................................................17

4.18.6 Alcatel-Lucent OmniTouch My Teamwork ...................................................................18

4.18.7 Alcatel-Lucent OmniTouch Automated Message Delivery System (AMDS)

Application .........................................................................................................................19

4.18.8 Alcatel-Lucent OmniTouch Fax Server Application....................................................19

4.18.9 Omni Desktop.....................................................................................................................19

4.18.10 API Web Services ...............................................................................................................20

4.18.11 OmniVista 4760...................................................................................................................21




4.18.12 Business integrated Communication Server ( BiCS )...................................................21

4.18.13 Professional Services Applications..................................................................................22

4.18.14 Miscellaneous .....................................................................................................................22

5. OmniPCX Enterprise Hardware compatibility...................................................................................23

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

5.1.1 Legend used in the table.................................................................................................23

5.1.2 System Boards.....................................................................................................................23

5.1.3 Auxiliary Coupler Boards ..................................................................................................24

5.1.4 Extension boards................................................................................................................24

5.1.5 Trunk Interface boards......................................................................................................25

5.1.6 DECT boards .......................................................................................................................25

5.1.7 Voice Mail 4635..................................................................................................................26

5.1.8 Link Interface Optimizer Boards ......................................................................................26

5.1.9 Miscellaneous Boards .......................................................................................................27

5.1.10 Voice Hub and Wall Mounted cabinets .......................................................................27

5.2 Common Hardware/OmniPCX Enterprise compatibilities ......................................................29 5.2.1 Legend used in the table.................................................................................................29

5.2.2 System boards ....................................................................................................................29

5.2.3 Extension boards................................................................................................................30

5.2.4 Trunk Interface boards......................................................................................................31

5.2.5 Mixed boards......................................................................................................................32

5.2.6 External battery racks .......................................................................................................32

5.3 appliance server .............................................................................................................................33 5.3.1 Compatibility between Appliance Server and Software Releases .........................33

5.3.2 Feature loss on IO2/IO2N/ OBCA loss ............................................................................34

6. Internal compatibility issues ...............................................................................................................35

6.1 Compression resource compatibility issues................................................................................35

6.2 Voice over IP compatibility issues when implementing new services ..................................35 6.2.1 Framing 20ms for voice over IP .......................................................................................35

6.2.2 Remote LIO must be upgraded to ACT- IP. ..................................................................35

6.2.3 H323 services introduced since OmniPCX 4400 R4.2..................................................35

6.2.4 Voice over IP and direct RTP switching with OmniPCX Enterprise ...........................36

6.2.5 Direct RTP with H323 equipments ...................................................................................37

6.3 COMPATIBILITIES...............................................................................................................................38

6.3.1 Reminder on boards supporting the Transit function and the direct RTP...............39

6.3.2 Delay (in one direction) introduced by IP gateways .................................................39

6.3.3 Delay (in one direction) from an IP Phone towards a set behind ACT or eMG....39

6.3.4 ABC-F2 compatibility depending on the hardware and the type of configuration

used (with or without compressed voice) ....................................................................39

Notes Description ............................................................................................................................42

6.3.5 USB Key compatibility for CPU7-2, Appliance Server and Blade Server .................43

7. Terminal compatibility .........................................................................................................................44

7.1 WIRED TERMINAL compatibility .....................................................................................................44

7.1.1 Legend used in the table.................................................................................................44

7.1.2 UA 2G & Reflexes Terminals .............................................................................................44

7.1.3 Dedicated Attendant Terminals .....................................................................................44

7.1.4 Options and interfaces for Reflexes/e-Reflexes...........................................................45

7.1.5 Options for 8 & 9 series and Reflexe Terminals .............................................................46

7.1.6 e-reflexes terminals ............................................................................................................46




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

7.1.8 DECT System and Terminals .............................................................................................48

7.1.9 Wireless LAN terminal ........................................................................................................49

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

and applications..................................................................................................................................49

9. OmniPCX applications ........................................................................................................................49

10. Alcatel-Lucent Omnidesktop platform .............................................................................................50

10.1 Alcatel-Lucent 4058/4059 Hardware and software compatibility ........................................50 10.1.1 Windows compatibility .....................................................................................................50

10.1.2 Minimum PC configuration ..............................................................................................51

10.1.3 Migration memo ................................................................................................................51

10.1.4 Related services .................................................................................................................51

10.2 omnitouch unified communicationS hardware and software compatibility .....................52

10.2.1 OmniTouch Unified Communication 3.0 compliant platforms (server side) ..........52

10.2.2 OmniTouch Unified Communication 4.0 & 4.1 compliant platforms (server side)52

10.2.3 OmniTouch Unified Communications 5.0 compliant platforms (server side).........52

10.2.4 OS server compatibility.....................................................................................................52

10.2.5 Mail Servers OS and 46x5 version compatibility...........................................................54

10.3 omnitouch My Teamwork hardware and software compatibility.........................................54 Compliant platforms (server side)................................................................................................54

10.4 omnitouch Automated Message Delivery System (AMDS) hardware and software

compatibility ....................................................................................................................................55 OS server compatibility ..................................................................................................................55

10.5 Omnitouch Fax Server ....................................................................................................................55

Compliant platforms.......................................................................................................................55

10.6 Alcatel-Lucent TAPI Premium Server ...........................................................................................55 Windows compatibility (Server)....................................................................................................55

10.7 Alcatel-Lucent TSAPI Premium Server..........................................................................................56

OS compatibility (Server) ...............................................................................................................56

10.8 XML API (My Web Services) : OS compatibility server (Server)...............................................56

11. Alcatel-Lucent OmniMessage application ......................................................................................57

11.1 Alcatel-Lucent 4635H hardware and software compatibility ................................................57 11.1.1 Boards versus release compatibility ...............................................................................57

11.1.2 Minimum configuration ....................................................................................................57

11.1.3 Migration memo ................................................................................................................58

11.1.4 Recommendation and requirement .............................................................................58

11.2 Alcatel-Lucent 4635J hardware and software compatibility.................................................59 11.2.1 Boards versus release compatibility ...............................................................................59

11.2.2 Minimum configuration ....................................................................................................59

11.2.3 Migration .............................................................................................................................59

11.3 Visual Messenger Hardware and software compatibility .......................................................60

11.3.1 Server SW compatibility ....................................................................................................60

11.3.2 Client SW compatibility.....................................................................................................60

11.3.3 Application SW compatibility..........................................................................................60

11.3.4 Recommended server PC configuration......................................................................60

11.3.5 Recommended client PC configuration ......................................................................60




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

12.1 Omnivista 4760 R3.0 ........................................................................................................................61 12.1.1 Server configuration requirements.................................................................................61

12.1.2 Common requirements ....................................................................................................61

12.2 OmniVista 4760 R3.1 .......................................................................................................................62

12.3 OmniVista 4760 R3.2 .......................................................................................................................62

12.4 OmniVista 4760 R4.0/R4.1 ..............................................................................................................63

12.5 OmniVista 4760 R4.2 .......................................................................................................................63

13. Business integrated Communication Server ( BiCS ) .......................................................................64

13.1 Business integrated Communication Server R1.0......................................................................64 13.1.1 Server configuration requirement ..................................................................................64

13.1.2 Software compatibilities ...................................................................................................64

13.2 Business integrated Communication Server R2.0......................................................................65

13.2.1 Server configuration requirement ..................................................................................65

13.2.2 Software compatibilities ...................................................................................................65

14. Omnitouch Contact center suite Operating System and hardware compatibilities...................66

14.1 OPerating System compatibilies ..................................................................................................66 14.1.1 OmniTouch Contact Center Suite..................................................................................66

14.1.2 OmniTouch Contact Center Premium Edition.............................................................66

14.2 Hardware compatibility: minimum PC requirement ................................................................66

14.2.1 CCS Supervision .................................................................................................................66

14.2.2 CCS Server ..........................................................................................................................67

14.2.3 CCWallboard .....................................................................................................................67

14.2.4 CCA PC client (agent) requirements ............................................................................67

14.2.5 A4400 Call Center agent (CCA) server.........................................................................67

14.2.6 Ccweb CCemail powered by genesys ........................................................................67

14.2.7 CCemail PC platform requirement ................................................................................68

14.2.8 Database requirement.....................................................................................................68

14.2.9 Ccoutbound Platform requirements..............................................................................68

15. APPENDIX ..............................................................................................................................................69

15.1 Actual OmniPCX Enterprise /4400 released software releases ..............................................69




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 and R9

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 R9.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 October 2008. 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 R5.1 ref : 8AL010980098ZZASA

• Previous edition of this document for release R5.1 to R6.0.1.

• 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)

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 4.2) 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 :

[email protected]




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




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 will be at end of life in October 2008


This version is a major version regarding the OmniPCX Enterprise 6.2

This release is in phase out in December 2007

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 will be in phase out in November 2009


This version is a major version regarding the OmniPCX Enterprise R7.1

This release will be in phase out in October 2010





This version is the maintenance version of the OmniPCX Enterprise 8.0.

This release will be in phased out in October 2010


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

This release will be in phase out in October 2011




4.18 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.18.1 Call handling

Call Handling

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1 / 6.1.1 R6.2 R7.0 R7.1 R8.0/R8.01 R9.0

4058 (W95/WNT) Migration R4.016.1 R4.016.3 R4.016.3 R4.016.5

R4.016.5

R4.016.12

4059 MGT R4.016.1 R4.016.3 Not

supported Not

supported Not

supported Not

supported

4059 MAC/BLF and

Migration R4.016.1 R4.016.3 R4.016.3 R4.016.5 R5.0.4 R5.1.1

4059 IP Not

supported Not

supported Not

supported Not

supported R5.0.4 R5.1.1




4.18.2 OmniMessage

OmniMessage

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/R6.1.1 R6.2 R7.0 R7.1 R8.0/R8.0.1 R9.0

4615 3.0.24 Not

supported Not

supported Not

supported Not

supported Not

supported

4635H-2 (VPM 35) R5.1 R5.1.5 R5.1.5 R5.1.5 R5.1.5

Not supported

Not supported

R5.2.10 4635H-2 (VPM 35) R5.2

R5.2.2 and should be updated to R5.2.6 to

allow blind transfer and spatial

redundancy R5.2.6 (note 2) R5.3.0 R5.3.0 R5.4.4 (note3)

4635J – (VPS 35)

Replaced by 4635J – (VPU5-8 ports)

Not supported

Not supported

Not supported

Not supported

Not supported

R5.2.10 4635J – (VPU5-16 ports)

R5.2.2 and should be updated to

R5.2.6 to allow blind transfer and spatial

redundancy R5.2.6 (note 2) R5.3.0 R5.3.0 R5.4.4 (note3)

4635J – (VPU6-16 ports) R5.3.0 R5.3.0 R5.3.0 R5.3.0 R5.3.0

R5.4.4 (note3)

Visual Messenger for 4635 R2 R2.015 R2.015 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

Alcatel-Lucent © version : 31/10/08 15/72 ref: 8AL020033175TCARA 10



4.18.3 OmniTouch Contact Center suite

CCD R6.2

CCD R7.0

CCD 7.1

CCD R8.0

w/o

XL

CCD 8.0 w

ith X

L

CCD R9.0

Win

2000

Srv

(1)

Win

2000

Pro

Win

XP Pro

SP1

Win

XP Pro

SP2

Win 20

03 sr

v (1)

Win 20

03 S

P1 srv

(1)

Win

2003

R2 s

rv (1

)

Win

2008

serve

r

Win

2000

Pro

Win

XP Pro

SP2

Win

Vista B

usine

ss E

d.

Version OS CompatibilityOXEOther compatiblity

requirement

CCSupervision / CCSupervision light

CCS 7.0 7.0.90.0 √ √ √ √ √ N R N R N R N R N R N R N R √ √ Excel 2003, Excel 2000 CCS 7.1 7.1.90.0 √ √ √ √ √ N R N R N R N R N R N R N R √ √ Excel 2003, Excel 2000 CCS 8.0 8.0.90.2 √ √ √ √ √ N R N R N R N R N R N R N R √ √ Excel 2007, Excel 2003 CCS 8.0 8.0.90.4 √ √ √ √ √ √√√√ N R N R N R N R N R N R N R √ √ Excel 2007, Excel 2003

CCS 9.0 √√√√ √√√√ √√√√ √√√√ N R N R N R N R N R N R N R √√√√ √√√√ Excel 2007, Excel 2003

CCAgent CCA R7.0 7.0.8.1 √ √ √ √ √ N R N R N R √ √ √ √

CCA R7.1 7.1.8.2 √ √ √ √ √ N R N R N R √ √ √ √ √

CCA R8.0 8.0.8.2 √ √ √ √ √ √ N R N R N R √ √ √ √ √

CCA R8.0 8.0.8.4 √ √ √ √ √ √√√√ √ N R N R N R √ √ √ √ √

CCA R8.0 √√√√ √√√√ √√√√ √√√√ √√√√ N R N R N R √√√√ √√√√ √√√√ √√√√ √√√√

CCOutbound

CCO R7.0 7.0.0.2 √ √ √ √ √ N R N R N R √ √ √ √

CCO R7.1 7.1.0.2 √ √ √ √ √ N R N R N R √ √ √ √ √

CCO R8.0 8.0.2.0 √ √ √ √ √ √√√√ √ N R N R N R √ √ √ √ √ CCLB 8.0.0.2 also Vista compatible

CCO R8.0 8.0.4.0 √ √ √ √ √ √√√√ √ N R N R N R √ √ √ √ √ CCLB 8.0.0.4 also Vista compatible

CCO R9.0 √√√√ √√√√ √√√√ √√√√ √√√√ N R N R N R √√√√ √√√√ √√√√ √√√√ √√√√

CCOutbound agent scripting editor

Scripting R7.0 7.0.0 √ √ √ √ N R N R N R N R N R N R N R √ √

Scripting R7.1 7.1.0 √ √ √ √ N R N R N R N R N R N R N R √ √

Scripting R8.0 8.0.0 √ √ √ √ √ √√√√ N R N R N R N R N R N R N R √ √

Scripting R8.0 8.0.4 √ √ √ √ √ √√√√ N R N R N R N R N R N R N R √ √

Scripting R9.0 √√√√ √√√√ √√√√ √√√√ N R N R N R N R N R N R N R √√√√ √√√√

CCWeb

CCW R5.1 / R5.1.1 5.1.1.40 √ N R N R N R √ minimum CCS : 4.7.75.3

CCEmail

CCE R6.1 6.1.0.0 √ √(3) √ √(3) √ N R N R N R √ √ minimum CCS : 4.7.75.3

CCIvr CCIVR R7.0 7.0.0. √ √ √ √ √ √ (2) √ (2) √ √ √ √

CCIVR R7.1 7.1.0 √ √ √ √ √ √ √ √ √

CCIVR R8.0 8.0.1 √ √ √ √ √ √√√√ √ √ √

CCIVR R9.0 √√√√ √√√√ √√√√ √√√√ √√√√ √√√√ √√√√

Server ACR ext. ACR R7.0 7.0.0 √ √ √ √ √ √ √ √ N R N R N R

ACR R8.0 8.0.0 √ √ √ √ √ √√√√ √ √ √ √ √ √ N R N R N R

Server CCS Serv. CCS 7.0 7.0.0 √ √ √ √ √ √ √ √ √ √ √ N R N R N R

Serv. CCS 7.1 7.1 √ √ √ √ √ √ √ √ √ √ √ √ N R N R N R

Serv. CCS 8.0 8.0 √ √ √ √ √ √√√√ √ √ √ √ √ √ √ N R N R N R

Serv. CCS 9.0 √√√√ √√√√ √√√√ √√√√ √√√√ √√√√ √√√√ √√√√ √√√√ √√√√ √√√√ N R N R N R

WBM / Wall Board Manager

WBM R7.0 7.0.0.0 √ √ √ √ √ N R N R N R N R N R N R N R √ √

WBM R8.0 8.0.0.0 √ √ √ √ √ √√√√ N R N R N R N R N R N R N R √ √ √

WBM R8.0 8.0.4.0 √ √ √ √ √ √√√√ N R N R N R N R N R N R N R √ √

WBM R9.0 √√√√ √√√√ √√√√ √√√√ N R N R N R N R N R N R N R √√√√ √√√√

√ : √ : √ : √ : compatible blank: not compatible NR: Not Relevant (1) Standard Edition / 32 bits edition

(2) Only for Slave server / Easy server

(3) Version g13026+ minimum

Version OS CompatibilityClient side

OXEServer side

Other compatiblity

requirement




4.18.4 OmniTouch cc Premium Edition

OXE R 6.2 (1

)

OXE R 7.0 ( 2

)

OXE R 7.1( 3

)

OXE R 8.0 w

/o XL (5

)

OXE R 8.0 w

ith X

L (5)

OXE R 9.0 w

/o XL

OXE R 9.0 w

ith X

L

Win 2003 S

P1 srv (4

)

Win 2003 R

2 srv (4

)

Win 2008

Win 2000 P

ro S

P4

Win X

P Pro

Win X

P Pro

SP2

Win V

ista Business E

dition

MSSQL 2000 Std

Ed. S

P3

MSSQL 2005 Std

Ed.

MSSQL 2008

Excel 2003 S

P1/SP3 (6

)

Excel 2007 (6

)

Internet E

xplorer 6

.x

Internet E

xplorer 7

.x

PBX CompatibilityOTCC PE

Version

IE

Compat.

Others compatibility

requirements

MSSQL

Compatibilit

Excel

Compat.

OS Compatibility

R7.0 1.0.00.07002F √ √ √ √ √ √ √

R7.1 1.0.01.03002C2 √ √ √ √ ( 5) √ √ √ √ √

R7.1.1 1.0.02.00003B √ √ √ √ ( 5) √ √ √ √ √

R7.1.1 1.0.02.00004C √ √ √ √ √ √ √ √ √ √

R8.0 2.00.205 √ √ √ √ √ √ √ √ √ √ √ √ √ √

R8.0 2.00.206 √ √ √ √ √ √ √ √ √ √ √ √ √ √

R8.0 2.00.207 √ √ √ √ √ √ √ √ √ √ √ √ √ √

R7.0 1.0.00.07002F √ √ √ √ √

R7.1 1.0.01.03002C √ √ √ √ √

R7.1.1 1.0.02.00004C √ √ √ √ √

R8.0 2.00.205 √ √ √ √ √ √ √

R8.0 2.00.206 √ √ √ √ √ √ √

R8.0 2.00.207 √ √ √ √ √ √ √

R7.0 1.0.00.07002F √ √ √ √

R7.1 1.0.01.03002C √ √ √ √

R7.1.1 1.0.02.00004C √ √ √ √

R8.0 2.00.205 √ √ √ √

R8.0 2.00.206 √ √ √ √

R8.0 2.00.207 √ √ √ √ √

√ √ √ √ : : : : compatible (1): minimum patch level: R6.2 / F3.301.27 (4): Standard Edition - 32 bit edition only

blank : not compatible (2): minimum patch level: R7.0 / F4.401.21 (5): minimum OXE version : G1.302.8 / G1.503.17

NR N ot relevant (3): minimum patch level: R7.1 / F5.401.21 (6): Same Excel version must be used on OTPE Server and Visual CC

PBX Compatibility

NR

NR

NR

OTPE Server

OTCC PE

Version

IE

Compat.Server side

Others compatibility

requirements Client side

MSSQL

Compatibilit

Excel

Compat.

OS Compatibility

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR

NR NR

NR

NR

NR

NR

NR

NRNR

NR NR

NR NR

NR

NR

NR

NR

NR NR NR

Visual CC

Agent Desktop

NR

NR NR




4.18.5 Alcatel-Lucent OmniTouch Unified Communication

OmniTouch Unified Communications

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/6.1.1 R6.2 R7.0 R7.1 R8.0/8.0.1 R9.0

Unified Communication R3.0 (1): My Assistant, My Messaging and My Phone applications R3.0.7 R3.0.7

Not supported

Not supported

Not supported

Not supported

Unified Communication R3.0 (2): My Teamwork application R3.0 R3.0

Not supported

Not supported

Not supported

Not supported

Unified Communication R4.0 (1):

My Assistant, My Messaging and My Phone applications R4.0 R4.0 R4.0(3) R4.0(3)

Not supported

Not supported

Unified Communication R4.0 (2): My Teamwork application R4.0 R4.0 R4.0(3) R4.0(3)

Not supported

Not supported

R4.1 R4.1 Unified Communication R4.1 (1): My Assistant, My Messaging and My Phone applications R4.1 R4.1 R4.1 R4.1

Not compliant

XL

Not compliant

XL

R4.1 R4.1

Unified Communication R4.1 (2):

My Teamwork application R4.1 R4.1 R4.1 R4.1

Not compliant

XL

Not compliant

XL

Unified Communications R5.0 (1) R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/ R5.01(4)

Unified Communications R5.1 (1) R5.1 R5.1 R5.1 R5.1 R5.1 R5.1

(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 and OmniTouch UC R4.0 are compliant in the same feature level as OmniPCX Enterprise R7.0

(4) OmniPCX enterprise R9 and OmniTouch UC R5.0 are compliant in the same feature level as OmniPCX Enterprise R8.0/R8.0.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).




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.

OmniTouch UC My Assistant, My Messaging and

My Phone applications

PBX Front-end or

PBX Gateway

Other PBX nodes in

the same Network

Other PBX nodes in

sub-network

My Phone for Omnitouch Unified Communication R3.0 R4.0 and R4.1

Not used R3.2 R3.2

My Messaging for Omnitouch Unified Communication R3.0 R4.0 and R4.1

R4.2 R3.2

My Assistant for Omnitouch Unified

Communication R3.0 R4.0 and R4.1

>= R7.1 *

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.18.6 Alcatel-Lucent OmniTouch My Teamwork

OmniTouch My Teamwork

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/6.1.1 R6.2 R7.0 R7.1 R8.0/8.0.1 R9.0

Unified Communication R5.0

(2): My Teamwork

application R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01

Unified Communication R5.1

(2): My Teamwork

application R5.1 R5.1 R5.1 R5.1 R5.1 R5.1

(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.18.7 Alcatel-Lucent OmniTouch Automated Message Delivery System (AMDS) Application

OmniTouch Automated Message Delivery System

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/6.1.1 R6.2 R7.0 R7.1 R8.0/8.01 R9.0

AMDS R3.2 R3.2 R3.2 R3.2 R3.2 R3.2 R3.2

AMDS R5.0 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01

AMDS R5.1 R5.1 R5.1 R5.1 R5.1 R5.1 R5.1

Two types of link are available when inter-connecting AMDS to PBX systems:






An OmniPCX Enterprise Gateway is not required in such context.

4.18.8 Alcatel-Lucent OmniTouch Fax Server Application

OmniTouch Fax Server Application

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/6.1.1 R6.2 R7.0 R7.1 R8.0/8.0.1 R9.0

Fax Server 5.0 - - R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.0/R5.01

Fax Server 5.1 - - R5.0/R5.01 R5.0/R5.01 R5.0/R5.01 R5.1

Fax Server is embedded in UC server for a configuration under 500 users

The link between the Fax Server and OXE / UC is SIP only today, in the future we also will have

H323.




4.18.9 Omni Desktop

Omni Desktop

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1 / 6.1.1 R6.2 R7.0 R7.1 R8.0/8.0.1 R9.0

XML telephony R1.0 R1.1

Not supporte

d

Not supporte

d

Not supporte

d Not

supported Not

supported

TSAPI Premium server R4.x R4.2.3.1 R4.2.3.1

Not supporte

d

Not supporte

d Not

supported Not

supported

TSAPI Premium server R5.x R5.0.11 R5.0.11

Not supporte

d

Not supporte

d Not

supported Not

supported

R6.3.0 / R6.3.1

R6.3.0 / R6.3.1

TSAPI Premium server R6.x R6.3.0 / R6.3.1

R6.3.0 / R6.3.1

R6.3.0 / R6.3.1

R6.3.0 / R6.3.1

R6.3.1 for XL

R6.3.1 for XL

• IP Touch and WLAN Phone not supported

4.18.10 API Web Services

API Web Services

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/R6.1.1 R6.2 R7.0 R7.1 R8.0/R8.0.1 R9.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 - - - -

R3.0/R3.1 R3.0/R3.1

My IP Touch Web Services R3.x R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 Not compliant XL Not compliant

XL

R3.0/R3.1 R3.0/R3.1

My Phone Web Services R3.x R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 Not compliant XL Not compliant

XL

R3.0/R3.1 R3.0/R3.1

My Assistant Web Services R3.x R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 Not compliant XL Not compliant

XL

R3.0/R3.1 R3.0/R3.1 My Messaging Web Services R3.x R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 Not compliant XL

Not compliant XL

R3.0/R3.1 R3.0/R3.1 My Management Web Services R3.x R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 Not compliant XL

Not compliant XL

XML FrameWork Management R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1 R3.0/R3.1




R3.x Not compliant XL

Not compliant XL

My TeamWork Web Services R3.x - - R3.1 R3.1 R3.1 R3.1

IP Touch Web Services R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01

Telephony Web Services R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01

One Number Web Services R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01

Messaging Web Services R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01

Management Web Services R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01

XML FrameWork Management R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01

TeamWork Web Services R5.0 - - R5.0/5.01 R5.0/5.01 R5.0/5.01 R5.0/5.01

IP Touch Web Services R5.1 - - R5.1 R5.1 R5.1 R5.1

Telephony Web Services R5.1 - - R5.1 R5.1 R5.1 R5.1

One Number Web Services R5.1 - - R5.1 R5.1 R5.1 R5.1

Messaging Web Services R5.1 - - R5.1 R5.1 R5.1 R5.1

Management Web Services R5.1 - - R5.1 R5.1 R5.1 R5.1

XML FrameWork Management R5.1 - - R5.1 R5.1 R5.1 R5.1

TeamWork Web Services R5.1 - - R5.1 R5.1 R5.1 R5.1

• WLAN Phone not supported

4.18.11 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

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/6.1.1 R6.2 R7.0 R7.1 R8.0 R9.0

4760 OmniVista R3.1.07 R3.2.04.00.a R4.0.11.01.a R4.1.08.00.c R4.2 R5.0

Wizard R6 R6.1.2 Not

supported Not

supported Not

supported Not

supported Not

supported

4760 OmniVista R3.1.07.00 R3.2.04.00.a R4.0.11.01.a R4.1.08.00.c R4.2.06.01a R5.0.07.02b

4760 OXE patch download no no no R4.1 R4.2 R5.0 4760 PCS patch download no no no R4.2 R4.2 R5.0

4760 OXE Audit no no no R5.0 R5.0 R5.0

4760 SIP Manager no no no no no R5.0




4.18.12 Business integrated Communication Server ( BiCS )

OmniVista

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/6.1.1 R6.2 R7.0 R7.1 R8.0 R8.0.1 R9.0

BiCS Not

supported Not

supported Not

supported Not

supported R1.0 R1.1 R2.0 (1)

(1) BICS R2.0 Release will be available on December 2008

4.18.13 Professional Services Applications

Other Applications

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1 / 6.1.1 R6.2 R7.0 R7.1 R8/R8.0.1 R9.0

IPDSP IPDSP IP Desktop Softphone N/A

MIPD V2.0.3 MIPD V2.0.3

MIPD V2.0.3 V2.0 V3.0

IPDSP IPDSP

IP Desktop Agent N/A MIPD V2.0.3 MIPD V2.0.3

MIPD V2.0.3 V2.0 V3.0

IP Desktop

Attendant N/A

MIPD

V2.0.3 MIPD V2.0.3

MIPD

V2.0.3 MIPD V2.0.3 MIPD V2.0.3

Free Desktop N/A V1.0.4 V1.0.4 V1.0.4 V2.1.3 (1) V3.0

IP Touch DoorCam N/A N/A V1.2.7 (2) V1.2.7 (2) V1.2.7 (2) V1.2.7 (2)

Ringtone Customization N/A N/A N/A N/A V1.1 V1.1

Wall Board

Manager for OTCC Premium N/A N/A N/A

V1.5.0.7

(3) V2.0.0.0 (3) V2.0.0.0 (3)

CCIVR integration for OTCC Premium N/A V7.1 (4) V7.1 (4) V7.1 (4) V7.1 (4) V7.1 (4)

(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




4.18.14 Miscellaneous

Miscellaneous

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.1/6.1.1 R6.2 R7.0 R7.1 R8.0/8.0.1 R9.0

Notification Server R2 R2.08d R2.08d 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

Netop (Replace

IRC client) – remote connection for IVR 7.65 7.65 7.65 7.65 7.65

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

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

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase

Status R6.1/R6.1.1 R6.2/R7.0 R7.1 R8.0/8.0.1 R9.0 Notes

CPU5 step 3 Out S (1) S (1) S (1) N N

(1) HDD≥ 6 Gb with 128 MB RAM

(2) HDD≥ 6 Gb with 128 MB RAM

CPU6 step 2 Out Y (2) Y (2) Y (2) S (3) S(3) (3) HDD≥ 10 Gb with 128 MB RAM

(4) Disk ≥ 6 Gb with 256 MB RAM

CPU7 step 1 Out Y (4) Y (4) Y (5) Y (5) S (5) (5) Disk ≥ 10 Gb with 256 MB RAM

CPU7 step 2 - N N Y (6) Y (6) Y (6)

(6)Disk ≥ 10 Gb with 256 MB RAM, no hardkey

ECX1 Out S S S S S

IO2 Out S S S S S Replaced by IO2N with CPU7

IO2N - Y Y Y Y Y

OBCA-2 Out S S S S S

VMU-OBCA Out S S S S S

VMU-OBCA 2 Out S S S S S

INTOF Out Y Y Y S S Couple INTOF-A with INTOF-B

INTOF2 - Y Y Y Y Y Couple INTOF2-A with INTOF2-B

RT2 Out S S S S S no Alcatel-Lucent series 9 sets behind

RT2-1 Out Y Y Y Y S RT2 /RT2-1

MMSFD Out S S S S S

RMAB - Y Y Y Y Y

SRMA Out S S S S S

NX64 Out S S S S S




5.1.3 Auxiliary Coupler Boards

Auxiliary Coupler Boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


GPA Out S S S S S

GPA2 - Y Y Y Y Y VG + Conference only

SU Out S S S S (1) S (1)

SUVG Out S S S S (1) N

(1) Only used for auxiliaries. 4300 migration not supported in R8.0

VG Out S S S S N

Z20/VG Out S S S S S

5.1.4 Extension boards

Extension boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


eUA32 - Y Y Y Y Y

eZ32 - Y Y Y Y Y

UA/ZP Out S S S S S Configured on VH step 2 (90w)

UA16 Out S S S S S

UA32NV Out S S S S S

Z12 Out S S S S S

Z12-2 Out S S S S S

Z24 Out S S S S S

Z24-2 Out S S S S S

Z32 Out S S S S S




5.1.5 Trunk Interface boards

Trunk Interface boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


ACEM Out Y Y Y Y S

BPRA Out S S S S S

BPRA2 Out S S S S S

BPRA2-1 Out S S S S S

BRA Out S S S S S

BRA2-1 - Y Y Y Y Y

DPT1 Out Y Y Y Y S

DPT1-2 - N N N Y Y

No more A-Mu conversion on DPT1-2, E1 & DPT1-2 can't be used on the same system.

EMTL - Y Y Y Y Y

NDDI Out Y Y Y S (1) S

NDDI2 Out Y Y Y S (2) S

NDDI2-2 - Y Y Y Y (3) Y (3) (3) UK included

NPRAE Out Y Y Y Y S +DPNSS and DASS2

NPRAE-2 - N N N Y Y +DPNSS and DASS2

PCM Out S S S S S

PCM2 - Y Y Y Y Y

PRA Out S S S S S

PRA2 Out Y Y Y S S

5.1.6 DECT boards

DECT Boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


DECT2 Out S S S S S

No more synchro CSP with DECT2&DECT4 from R4.2

DECT4 Out S S S S S

No more synchro CSP with DECT2&DECT4 from R4.3

DECT4HB Out S S S S S

DECT8 - Y Y Y Y Y

DTM Out S S S S S




5.1.7 Voice Mail 4635

Voice Mail 4635

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


MSBI - Y Y Y Y Y

SPA3 - Y Y Y Y Y

VPM35 Out S S S S S

VPM35-1 - Y Y Y Y Y

VPU5 Out S S S S S

VPU6 - Y Y Y Y Y

5.1.8 Link Interface Optimizer Boards

Link Interface Optimizer boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


GIP4-1 - Y Y Y Y Y

GIP4-4 - Y Y Y Y Y

GIP6 Out S S S S S

GIP6A Out S S S S S

INTIP Out S S S S S

INTIP-2 - Y Y Y Y Y

LIOB Out S S S S N

LIOB-2 Out S S S S S

LIOP Out S S S S N

LIOP-2 Out S S S S S

LIOX Out S S S S N

LIOX-2 Out S S S S S

with COMP2 daughter board




5.1.9 Miscellaneous Boards

Miscellaneous Boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


IRC Out S S S N N

TNLO1 Out S S S S S

TNLO2 Out S S S S S

TNLO11 - Y Y Y Y Y

TNLO21 - Y Y Y Y Y

SSM - N Y Y Y Y Alcatel-Lucent security module

MSM - N Y Y Y Y Alcatel-Lucent security module

SSM V5 - N N Y Y Y Alcatel-Lucent security module

MSM V5 - N N Y Y Y Alcatel-Lucent security module

5.1.10 Voice Hub and Wall Mounted cabinets

Voice Hub and Wall Mounted cabinets

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


(1) 10 Base T only.

VH55W Out S (1) S (1) S (1) S (1) S (1)

10 BaseT connector (3BA 23182 AA) has been phased out by April 2006

VH48V Out Y (2) Y (2) Y (2) S S

(2) Basically, all cabinets were only compatible with 10BaseT.

VH90W Out Y (2) Y (2) Y (2) S S

Since the reference listed in the table "Rack references" below, the VH and WM1 cabinets are compatible with the 10/100BaseT.

WM1 –48V Out Y (2) Y (2) Y (2) S S

WM1 –110/230V Out Y (2) Y (2) Y (2) 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


• 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.2.2 System boards

System Board

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


(1) Disk ≥ 10 Gb with 256Mb minimum for PCS

CS Y Y Y (1) Y (2) Y (2)

(2) Disk ≥ 10 Gb with 256Mb minimum

GD Out S S S S S

GD-2 Y Y Y Y Y

GA Out S S S S S

GA-2 Y Y Y Y Y

MEX Y Y Y Y Y

MCV8-I Out S S S S S

MCV24-I Out S S S S S

MADA3 Y Y Y Y Y

MADA1 Y Y Y Y Y

HSL2 Y Y Y Y Y

HSL1 Y Y Y Y Y

S-LANX4 Y Y Y Y Y

LANX8 Out S S S S S

LANX16-1 Out S S S S S

LANX16-2 Y Y Y Y Y

AFU-1 Y Y Y Y Y

XMEM-1 Y Y Y Y Y

RMA Y Y Y Y Y

MODB Y Y Y Y Y




5.2.3 Extension boards

Extension Boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


UAI16 Out S S S S S

SLI16 Out S S S S S

SLI8 Out S S S S S

SLI4 Out S S S S S

UAI16-1 - Y Y Y Y Y

UAI8 - Y Y Y Y Y

UAI4 - Y Y Y Y Y

SLI16-1 - Y Y Y Y Y

SLI8-1 - Y Y Y Y Y

SLI4-1 - Y Y Y Y Y




5.2.4 Trunk Interface boards

Trunk Interface boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


APA4 HU - Y Y Y Y Y

APA4 LCG Out S S S S S

APA4 TBR21 - Y Y Y Y Y

APA4 US - Y Y Y Y Y

APA8 HU - Y Y Y Y Y

APA8 LCG Out S S S S S

APA8 TBR21 - Y Y Y Y Y

APA8 US - Y Y Y Y Y

METCLI Out S S S S S

GSCLI - Y Y Y Y Y

CLIDSP - Y Y Y Y Y

DDI2 Out S S S S S US market

DDI4 - Y Y Y Y Y US market

BRA2 - Y Y Y Y Y

BRA4 - Y Y Y Y Y

BRA8 - Y Y Y Y Y

DIGITAL ACCESS E1 DASS2

- Y Y Y Y Y

DIGITAL ACCESS PCM-R2

- Y Y Y Y Y

ISDN ACCESS

E1 PRA-T2

- Y Y Y Y Y

PRA-T1 - Y Y Y Y Y

T1-CAS - Y Y Y Y Y

IRAD-CH Out Y Y Y S S Not available for US market




5.2.5 Mixed boards

Mixed boards

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase


MIX084 Out S S S S S 8UA + 4Z



MIX484 Y Y Y Y Y 4T0 / 8UA + 4Z

MIX448 Y Y Y Y Y 4T0 / 4UA + 4Z

MIX244 - Y Y Y Y Y 2T0 / 4UA + 4Z

5.2.6 External battery racks

Module Racks and External battery

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type R6.1/R6.1.1 R6.2/R7.0 R7.1 R8.0/8.0.1 R9.0 Notes

Module Rack S

(MR1) Y Y Y Y Y

Module Rack L (MR3) Y Y Y Y Y

External Battery Rack Y Y Y Y Y External Battery Rack

12V Cherokee Y Y Y Y Y

External Battery Rack

36V Cherokee Y Y Y Y Y

External Battery Box Y Y Y Y Y

The minimum technical releases of MR1and MR3

racks compatible with the external battery rack are in the "Rack

reference" 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




5.3 APPLIANCE SERVER

5.3.1 Compatibility between Appliance Server and Software Releases

Appliance Server

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

Board Type

Phase

Status R6.1/R6.1.1 R6.2/R7.0 R7.1 R8.0/R8.01 R9.0 Notes

IBM 305 Out S S S S S

IBM X306 Out S S S S S

IBM X306M N S (1) S S S (1) Version minimum

= F3.301.16.d

IBM X3250 N N Y (2) Y (2) Y (2) (2) Memory size = 1Go

Y (2) Y (2) (2) Memory size = 1Go

HP DL320 G5 N N N

Y (3) Y (3) HP DL320 G5p : 8.01 Only

IBM X3250-m2 N N N Y (4) Y (4) 8.0.1 Only

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 DECT8 Board

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.3.2 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:

IO2/ OBCA

PRA

IO2 / OBCA

CPU

PRA

CPU

Ethernet

4760

serverB

Example with OmniPCX 4400 :

B

: OmniPCX 4400 Board

: B Channel with Data bearer capability

PSTN

• 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

CPUUA

Application

terminal

(hotel menu,

AHLink,

wallboard CCD,...)

UA set + TA

Example with OmniPCX Enterprise and A/ S :

INTIPApplication

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:

LIO P/B/X LIO/P/B/X-2 LIO E INT IP GD

LIO P/B/X Comp6 Y Y (Note 1) N N N

LIO/P/B/X-2 Comp 2 Y Y

Y (See restriction below)

Y (See restriction below)

LIO E Comp 2 Y N (note 2) N (note 2)

INT IP GIP 6/GIP4 Y Y

GD MCV/MADA 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:

• Dramatic increase in the speech quality.

• 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)

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. (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.

• "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 blades.

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

Echo cancellation depth

OmniPCX Enterprise

R5.1/R5.1.1/

R5.1.2

OmniPCX Enterprise

R6.0/R6.0.1

R6.1/R6.1.1/ R6.2

OmniPCX Enterprise

R7.0/R7.1/R8.0/8.0.1/R9.0

GIP6/MCV24 32ms 32ms 32ms

GIP4/MADA 64ms 128ms

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 follows these "rules":

• Direct RTP must be activated across the entire IP PCX network

• H323 "fast start" mode is mandatory

• Not compatible with LIO-E




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 to use 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 COMPATIBILITIES

As of Release 7.0 and with the implementation of name using UTF-8 format, the networked interworking rules have changed. Please refer to the Installation procedure for Release 7.0 (TCO776)

• It is authorized to operate a Release 8.0 in a single sub-network only with systems having at least the versions below:

R7.1 : F5.401.13

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 7.1 with Releases 5.0 Ux, 5.1, 5.1.1, 5.1.2,

6.0, 6.1 is only authorized to allow progressive migration to the latest supported release. During the cohabitation period you must prohibit:

o broadcasting of the database and not carry out any audit,

o on the Release 7.1/8.0 node, sending of the names in UTF-8 format in the network must be prohibited (set the Enable UTF8 in ABCF network system parameter to False).

• Cohabitation in a single sub-network of a Release 7.1 with Releases < 5.0 Ux, 5.0 Lx is not authorized.

If using a CCS multi-site, each node must be in Release 8.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). In a network, these limits are allowed only if each node of the network is in Release 6.2 or higher.

From Release 7.1 and on each node of the network (whatever their version) cohabiting with R7.1:

• 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 node MUST be in release R8.0.

As of Release 8.0, some provisioning are increased. To use the new values, all the nodes MUST be in R8.0 or above. Entities: more than 1000 entities can be used only in a release-homogeneous network. Users in network: more than 50 000 users can be used only in a release-homogeneous. DDI Range: more than 200 DDI slices can be used only in a release-homogeneous network. NPD: more than 50 NPD can be used only in a release-homogeneous network. DCT: More than 30 DCT can be used only in a release-homogeneous network. External Voice mail: more than 32 voice mails can be used only in a release-homogeneous network.

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.3.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 or GA No Yes

(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.3.2 Delay (in one direction) introduced by IP gateways

In G711: approx. 100 ms (60 ms for an IP Phone (e-Reflexes/ series 8))



Transit: approx. 20 ms (there is no transit in G711)

6.3.3 Delay (in one direction) from an IP Phone towards a set behind ACT or eMG

In G711 In G729 In G723

approx. 80 ms approx. 100 ms approx. 120 ms

6.3.4 ABC-F2 compatibility depending on the hardware and the type of configuration used (with or

without compressed voice)

The table in paragraph 7.3.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.0 Ux and 7.1. This table takes into account both a connection in VoIP and a T2, T0 or T1 type wire connection.




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 (100 ms + 100 ms).

• 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 with Release 7.1 nor on any node of a network cohabiting with

Release 7.1 (whatever their versions even they allow it).

• H323 terminals are only compatible with configurations which allow to have a maximum delay of 200 ms "One way".

• Release 7.x allows to use Direct RTP for H323 equipments and all OmniPCX Enterprise H323 Gateways (MGDs, GA, INTIP) 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.0 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 (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 certain configurations with two compressions/decompressions, there are palliative solutions to get to a configuration with one compression/decompression + transit.

• 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).

• SIP is not authorized in configurations if the Direct RTP is disabled.

• The internode VoWLAN calls (via VoIP hybrid link) are not authorized if the Direct RTP is disabled.




Below are the different representations of the configurations used:

R4.2

à R5.0.1Ux

OmniPCX 4400

represents an OmniPCX 4400 in R4.2 to R5.0.1 Ux

OmniPCX Enterprise R5.1.2 IP Rack Server

represents an OmniPCX Enterprise controlled by a CS or

AS with common hardware (OXO common hardware)

IP@

OmniPCX Enterprise R5.1.2 Crystal IP Server

Crystal IP Server: represents an OmniPCX Enterprise R5.1.2 controlled by a CPU 5/6 or an AS with 4400 type

hardware

IP

Crystal IP Media Gateway

Crystal IP Media Gateway: represents an ACT Media

Gateway connected to the A4400 type PABX via an

INTIP (Remote IP)

Common hardware IP Media Gateway

represents a Media Gateway connected to thePABX via a GD

, , = OmniPCX 4400 or OmniPCX Enterprise connected in wired ABC-F2 to an OmniPCX Enterprise R7.1. One case with G723/G729 compression (IP terminals or compressed link (LIO P/B/X COMP2) or VoIP (with INTIP)) and one case without using compression (or G711 used) are described.

VoIP

= OmniPCX 4400 or OmniPCX Enterprise connected in VoIP ABC-F2 (with INTIPx only) to OmniPCX Enterprise R8.0. One case with G723/G729 compression (IP terminals or compressed link (LIO P/B/X COMP2)) and one case without using compression (or G711 used) are described.


May 2005 All rights reserved. Passing on and copying of this document, use and communication


Table of ABC-F2 compatibility

OmniPCX Enterprise

IP Rack Server Crystal Server

R8.0/R8.0.1/R9.0 R8.0/R8.0.1/R9.0

Without Crystal IP MGW

With Crystal IP MGW

Without common hardware

With common hardware

G72x G711 G72x G711 G72x G711 G72x G711

(a)

Yes (Note 1)

Yes (Note 1)

Yes (Note 2)

Yes (Note 2)

Yes (Note 1)

Yes (Note

1)

Yes (Note 1)

Yes (Note 2)

G711

/

W/out compr

ession (b)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

(c)

No No Yes

(Note 2)

Yes

(Note 2)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 2)

Yes

(Note 2)

CRYSTAL SERVER

R6.2.x to R9.0

With compression

(d)

Yes (Note 1)

Yes (Note 1)

Yes (Note 1)

Yes (Note 1)

Yes (Note 1)

Yes (Note

1)

Yes (Note 1)

Yes (Note 1)

No

(Note 5)

No

(Note 5)

No

(Note 4)

No

(Note 4)

No

(Note 4)

No

(Note 4)

No

(Note 4)

No

(Note 4) G723

/

G729

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 3)

Yes

(Note 3)

Yes

(Note 3)

Yes

(Note 3)

No (Note 5)

Yes (Note 1)

No (Note 5)

Yes (Note 1)

Yes (Note 1)

Yes (Note 1)

Yes (Note 4)

Yes (Note 4)

COMMON HARDWARE

R6.2.x to R9.0

G711

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 1)

Yes

(Note 3)

Yes

(Note 3)

Yes

(Note 3)

Yes

(Note 3)

Notes Description

(a) Compressed voice is not used (IP terminals or compressed link (LIO P/B/X COMP2) or VoIP (LIOe or INTIP))

on the OmniPCX 4400 or Crystal IP Server or G711 used.

(b) Compressed voice is not used (IP terminals or compressed link (LIO P/B/X COMP2)) on the OmniPCX 4400

or Crystal IP Server or G711 used.

(c) Compressed voice is used (IP terminals or compressed link (LIO P/B/X COMP2) or VoIP (LIOe or INTIP)) on

the OmniPCX 4400 or Crystal IP Server.

(d) Compressed voice is used (IP terminals or compressed link (LIO P/B/X COMP2)) on the OmniPCX 4400 or

Crystal IP Server.

Notes Description

1 Direct RTP enabled

2 Direct RTP enabled It is essential that the T2/T0/T1 access be connected to the Crystal IP (ACT) Media Gateway

3 Direct RTP enabled There must be no LIOe board (compulsory)

4 To lift the prohibition, a Crystal IP (ACT) Media Gateway must be added to the PABX in common

hardware and the T2/T0/T1 connected to it

5

To lift the prohibition, a Crystal IP (ACT) Media Gateway must be added to each PABX and the T2/T0/T1 connected between them

Direct RTP enabled




6.3.5 USB Key compatibility for CPU7-2, Appliance Server and Blade Server

The list below introduces the compatibility of the USB key with the CPU7 step2 , Appliance Server

and Blade Server only .

This is available from OmniPCX Enterprise R7.1 Release.

Only the key listed here have been tested and so declared compliant for this purpose.

� MEMOREX 16MB

� LEXAR MEDIA 256MB

� INTUIX 256MB

� PNY 256MB

� PNY 512MB

� SANDISK 512MB

� SONY 1GB




7. TERMINAL COMPATIBILITY

7.1 WIRED TERMINAL COMPATIBILITY


• 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

7.1.2 UA 2G & Reflexes Terminals

Terminal Type

Phase out

status *

OmniPCX Enterprise

R6.0/R6.0.1/R6.1/R6.1.1/R6.2/R7

.0/R7.1/R8.0/R8.0.1/R9.0 Notes

UA 2G sets Out S -

UA 2G subdevices Out S

See minimum condition on 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

Enterprise

OmniPCX

Enterprise

Terminal Type

Phase out

status *

OmniPCX Enterprise

R6.0/R6.0.1/R6.1/R6.1.1/R6

.2/R7.0/R7.1 R8.0/8.01 R9.0 Notes

4048 Out S N N -

4049 Out S S N




7.1.4 Options and interfaces for Reflexes/e-Reflexes

Options and Interfaces for Reflexes/e-Reflexes

Terminal Type

Phase

out

status *

OmniPCX Enterprise

R6.0/R6.0.1/R6.1/R6.1.1/R

6.2/R7.0/R7.1/R8.0/R8.0.1

OmniPCX Enterprise

R9.0 Notes

4097 TSC DECT Out Supported only with all

3G sets Supported only with all

3G sets

See minimum condition on subdevices PROM

TSC IP (4098 RE) Out N N -

4052 ISDN remote extender Out S N -

4051 ISDN local extender Out S N -

4088 Empty terminal adaptator Out S S

Cannot be connected behind 9 serie terminals

4093 CTI-V24 Out S S


4094 S0 Out S S


4095 Analog port Out S S


Alcatel-Lucent S0 Interface module - Y Y

Alcatel-Lucent AP Interface module - Y Y

V24/CTI Interface module - Y Y

Ref : 3GV27015 AB (or VA for Operators)

4090M Addon 20 Out S S -

4090L Addon 40 Out S S -

Note1 : Interoperability status is as follow

R< 7.0 R7.0/R7.1/R8.0/R8.0.1

R9.0 OmniPCX Enterprise

Device with Reflexe

With Series -9

single connexion

with Reflexe

With Series -9

single connexion

Alcatel-Lucent 4095 AP S N S S N S

Alcatel-Lucent Analogue

interface module X N X X X X

Alcatel-Lucent 4094 ISW S N S S N S

Alcatel-Lucent S0 interface

module X N X X X X

Alcatel-Lucent 4093 CTI S N S S N S

Alcatel-Lucent V24/CTI

interface module X N X X N X

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

Terminal Type

Phase

out

status *

OmniPCX Enterprise

R5.1 / R5.1.1 /

R5.1.2

OmniPCX Enterprise

R6.0/R6.0.1/R6.1/R6.1.1/

R6.2/R7.0/R7.1/R8.0/

R8.0.1/R9.0

Notes

External ringing Interface module

- Yes Yes 3GV28050AA

7.1.6 e-reflexes terminals

e-reflexes terminals

Terminal Type

Phase

out

status *

OmniPCX

Enterprise

R5.1 / R5.1.1 /

R5.1.2

OmniPCX Enterprise

R6.0/R6.0.1/R6.1/R6.1.1/

R6.2/R7.0/R7.1/R8.0/R8.0.1

OmniPCX Enterprise

R9.0 Notes

TSC IP v1s (4098 FRE) Out

Supported only with all 3G sets

Supported only with all 3G 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

Terminal Type

OmniPCX

Enterprise

R6.0 / R6.0.1

OmniPCX

Enterprise

R6.1

OmniPCX

Enterprise

R6.1.1

OmniPCX

Enterprise

R6.2

OmniPCX

Enterprise

R7.0

OmniPCX

Enterprise

R7.1/R8.0/R8.

0.1/R9.0

Alcatel-Lucent IP Touch 4008

No No No No Yes Yes


No No Yes Yes Yes Yes


No Yes Yes Yes Yes Yes


Yes Yes Yes Yes Yes Yes



A-L IP Touch 4008 EE No No No Yes (Note1) Yes Yes (Note1)





4068 IP-Touch Handset Blue-tooth V1.2

No No No Yes Yes Yes

4068 IP-Touch Gigabit Handset Blue-tooth

No No No Yes Yes Yes

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 10 keys module


Alcatel-Lucent 8 & 9 series 40 keys module


Alcatel-Lucent 8 & 9 series Smart display module

No Yes Yes Yes Yes Yes

Note1: Minimum version level for R6.2/R7.1/R8.0 to be used for this Extended Edition series. Refer to Technical communication




7.1.8 DECT System and Terminals

DECT System

DECT SYSTEM

OmniPCX Enterprise

R6.0 / R6.0.1/R6.1/R6.1.1/

R6.2/R7.0/R7.1

OmniPCX Enterprise

R8.0/R8.0.1/R9.0 Notes

Radio coverage GAP Compliant used with Alcatel-Lucent 407x GAP terminals

Y(1) Y(1) (1) (DECT4HB/DECT8

required)

4070 IBS Y Y

4070IO EX IBS EXPLOSION PROOF

Y Y

4070IA RBS INDOOR EUROPE

Y Y

4070IO IBS INDOOR US N Y

4070EO IBS OUTDOOR US

N Y

DECT Terminals

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

OmniPCX

Enterprise

R6.0 / R6.0.1 R6.1/R6.1.1/ R8.0/R8.0.1 R9.0

DECT Terminal

Phase-out

Status R6.2/R7.0/R7.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.9 Wireless LAN terminal

Wireless Lan Terminal

OmniPCX Enterprise

R6.0 / R6.0.1

OmniPCX Enterprise

R6.1 /R6.1.1/R6.2

OmniPCX Enterprise

R7.0/R7.1

OmniPCX Enterprise

R8.0/R8.0.1/R9.0

Spectralink R1.0 R1.1.1 (99.25) R2.x (109.025) (Note

1) R2.x (109.025) (Note 1

)

Mobil Ip Touch 300 S S S S

Mobil Ip Touch 600 S S S S

Mobil Ip Touch 310 N N Y (Note 2) Y

Mobil Ip Touch 610 N N Y (Note 2) Y

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.

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.1 Windows compatibility

Windows

3.11

Windows

95

Windows

98

Windows

NT 4 work

station

Windows

2000

Windows

ME

Windows

XP-SP2

Windows

VISTA

4058 rel. 2.12.X

Yes Yes No No No No No No

4059 MAC 4 No Yes No Yes Note 1 No Note 2 No

4059 BLF No Yes No Yes Note 1 No Note 2 No 4.14.x –

4.15.x 4059 MGT No Yes No Yes No No No No

4059 MAC No No No No Yes No Yes No 4.16.x

4059 BLF No No No No Yes No Yes No

4059 MAC No No No No No No Yes No 5.0.x –

4059 BLF No No No No No No Yes No

4059 MAC No No No No No No Yes Yes

(Note3) 5.1.x –

4059 BLF No No No No No No Yes Yes

(Note3)

Note 1: As of release 4.14.9 Note 3: As of release 5.1.1

Note 2: As of release 4.15.3

Alcatel-Lucent 4058/4059 and Windows software compatibility for R6.0/R6.1 OmniPCX Enterprise

See also the "File and Version list for 4059 MMK management" document (Docman reference : 3BA_29000_2784_XXZZA) for localization details.

Software

delivery based

on 4.015.8

Windows

3.11

Windows

95

Windows

98

Windows

NT 4

workstation

Windows

2000

Windows

ME

Windows

XP-SP2

4059 MAC 4 No Yes No Yes Yes No Yes

4059 BLF No Yes No Yes Yes No Yes

4059 MGT No Yes No Yes No No No

Alcatel-Lucent 4058/4059 4.0.16.x and Windows software compatibility for R6.0/R6.1/R6.2/R7.0

OmniPCX Enterprise

Software delivery

based on 4.016.x Windows

2000

Windows

XP-SP2

4059 MAC Yes Yes

4059 BLF Yes Yes

4058 migration Yes Yes




10.1.2 Minimum PC configuration

CPU RAM size Disk

space

Recommended

Alcatel-Lucent

server

4058/4812 Pentium 133 32Mb 1.2 Gb

Not supported in OmniPCX Enterprise

R6.0/R6.0.1/R6.1

4058 migration Pentium 400 4 Gb Configured by ACTIS (PC4)

4059 MAC/BLF/MGT

Pentium 400

128 Mb Windows 95 Windows NT4

256 Mb Windows 2000

1Gb Windows XP-SP2 4 Gb

Configured by ACTIS (PC4)

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 abovebought in the trade. In both cases, Alcatel-Lucent ensures the Technical Support.

10.1.3 Migration 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

From 4058 to 4059

Items to be ordered: • Migration Package (including Multimedia Keyboard)

• PC & OS upgrade if necessary

No migration is available from 4812 BLF to 4059 BLF related service.

10.1.4 Related services

When installing a 4059, attendant training should be discussed with the customer.




10.2 OMNITOUCH UNIFIED COMMUNICATIONS HARDWARE AND SOFTWARE

COMPATIBILITY

� Get more details in OmniTouch UC Feature List R3, R4 and R5 (“HW & SW requirements” tab).

10.2.1 OmniTouch Unified Communication 3.0 compliant platforms (server side)

Technical communication TC0638 describes the Compliant platforms (server side) with OmniTouch UC R3.0.

10.2.2 OmniTouch 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.3 OmniTouch 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.4 OS server compatibility

Windows 2000

Professional/Server

Windows 2003

Professional/Server

Linux

Red Hat

Unified

Communication

R3.0: My Assistant, My

Messaging and My Phone applications

Yes for My Phone application only


Linux Red Hat 7.3

Unified

Communication R3.0 : My Teamwork application

No No Linux

Red Hat 9.0

Unified

Communication





Linux Red Hat

Enterprise ES v4 (*)

Unified


No No Linux

Red Hat 9.0

Unified

Communication





Linux Red Hat


Unified


No No Linux

Red Hat Enterprise ES v4

Unified

Communications

R5.0 No No

Linux Red Hat





Unified

Communications

R5.1

No No

Linux Red Hat


(*) Hardware agnostic. To check that your OmniTouch UC server is a Red Hat Enterprise Linux 4.0 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.5 Mail Servers OS and 46x5 version compatibility

Mail Server

Microsoft

Exchange

Mail Server

IBM Lotus

Domino

Mail Server

IMAP4

Voice

Mail

4635

Voice Mail

4645

Unified

Communication R3.0 & R4.0: My Assistant, My Messaging and My Phone applications

Exchange 2000 and 2003

Domino R5, R6

Domino R5 & R6 / Exchange 2000 & 2003 / IMail R8.x, GroupWise

R6.0

R5.2.x (*)

>=OXE R5.1.2

Unified

Communication R4.1: My Assistant,

My Messaging and My Phone applications


Domino R5, R6 and R7(*)

Domino R5, R6 & R7 / Exchange 2000 & 2003 / IMail R8.x,

GroupWise R6.0, qmail 1.0.3 under

Debian GNU/Linux OS

R5.2.x (*)

And 5.3

>=OXE R5.1.2

Unified

Communications R5.0


Domino R6 and R7

Domino R6 & R7 / Exchange 2000 & 2003 / IMail R8.x, GroupWise R6.0, qmail 1.0.3 under Debian GNU/Linux OS

R5.2.x (*)

>=OXE R5.1.2

Unified

Communications R5.1


Domino R7 and R8

Domino R7 & R8 / Exchange 2000 & 2003 / IMail R8.x, GroupWise R6.0, qmail 1.0.3 under Debian GNU/Linux OS

R5.2.x (*)

>=OXE R5.1.2

(*) 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)

Windows 2000

Professional/Server

Windows 2003

Professional/Server

Linux

Red Hat

My Teamwork standalone application

No No Linux





10.4 OMNITOUCH AUTOMATED MESSAGE DELIVERY SYSTEM (AMDS) HARDWARE

AND SOFTWARE COMPATIBILITY

OS server compatibility

Windows 2000

Professional/Server

Windows 2003

Professional/Server

Linux

Red Hat

AMDS R3.2 No No

Linux Red Hat

Enterprise ES v4

AMDS R5.0 No No

Linux Red Hat

Enterprise ES v4

AMDS R5.1 No No

Linux Red Hat

Enterprise ES v4

10.5 OMNITOUCH FAX SERVER

Compliant platforms

Linux

Red Hat

Omnitouch Fax Server R5.0 Linux


Omnitouch Fax Server R5.6.3 Linux RHES 4, 32 bits

(not 64 bits )

10.6 ALCATEL-LUCENT TAPI PREMIUM SERVER

Windows compatibility (Server)

Windows

95/98/ME

Windows

XP

Windows

NT 4 Server

(Note 2)

Windows

2000 Server

Windows

2003 Server

TAPI PREMIUM server R3.1.x

No/No/No No Yes

(SP 6 minimum)

Yes

(SP 4 minimum) No

TAPI PREMIUM server R3.2.x

No/No/No No No Yes

(SP 4 minimum)

Yes

Note 2: Does not work with Windows NT Workstation or Windows 2000 Pro.

Remark: On PC client side, TAPI Server R3.0 supports Windows 95/98/ME/XP(SP2)/ NT/NT WS/2000.




10.7 ALCATEL-LUCENT TSAPI PREMIUM SERVER

OS compatibility (Server)

R2.1R3.2

R5.0.1

R5.1.2

R6.0W

in N

T4 SV/W

ST SP6

Win

200

0 SV/W

ST SP4

Win

XP P

ro S

P1

Win

2003

Serv

er

Linux RedHat 7

,3

Linux RedHat 8

Linux RedHat 9

VersionOmniPCX 4400

compatibilityOS Compatibility

TSAPIR3.x R 3.3.8 √ √ √ √ √ √ √

R4.x R 4.2.3.1 √ √ √ √ √ √ √ √ √

R5.x R 5.0.11 √ √ √ √ √ √ √ √ √ √

R6.x R 6.0.1 √ √ √ √ √ √ √ √ √ √ √(1)

√ : available ∃÷� .1available soon

Not available

TSAPI Premium ServerVersion

OmniPCX 4400

compatibilityOS Compatibility

Note: For R6.3.1 the minimum hardware requirements are as follows:

Pentium IV 2GHz, 1GB RAM with 200 MB free Disk space.

Pentium IV 2GHz, 1GB RAM with 200 MB free Disk space.

10.8 XML API (MY WEB SERVICES) : OS COMPATIBILITY SERVER (SERVER)

Windows

95/98/Me

Windows

XP

Windows

NT 4

workstation/

Server

Windows

2000 / 2003 Linux

API framework R2.x

No/No/No No No No / Yes (SP1)

Yes (Red-Hat 7.3)

API framework R3.x


Yes (Red-Hat Es 4.0)

API framework R5.x


Yes (Red-Hat ES 4.x)




11. ALCATEL-LUCENT OMNIMESSAGE APPLICATION

11.1 ALCATEL-LUCENT 4635H HARDWARE AND SOFTWARE COMPATIBILITY

11.1.1 Boards versus release compatibility

4635H OmniPCX Enterprise Release

R5.1 / R5.1.1 / R5.1.2

OmniPCX Enterprise Release

R6.0 / R6.0.1/R6.1/R6.2/R7.0/R7.1/R8.0/R8.0.1/R9.0

SPA3 Yes Yes

MSBI Yes Yes

VPM 35 with 64 MB from 4.0.4 to 5.2.6

Yes Yes

11.1.2 Minimum configuration

4635H RAM size Disk

Release 4 32 MB 1.4 GB IDE (Note 1)

Release 4 & VPIM 64 MB 1.4 GB IDE (Note 1)

Release 5 64 MB

(to support VPIM and /or IMAP4)

2.16 GB

• 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.3 Migration memo

4635H To 4635 H-2 release 4.0 minimum

From 4635H release 1.x

• VPCPU replacement with VPM35

• INT1 replacement with INTOF (see remarks)

• MSB replacement with MSBI if more than one disk

• SCSI disks replacement with ATB2 or ATB3I connector

• Disk conversion (a VPCPU-1 board is needed as tool for this conversion)

From 4635H-1 release 1.x

• VPCPU replacement with VPM35

• INT1 replacement with INTOF (see notes)

• 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.4 Recommendation 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.1 Boards versus release compatibility

4635J Releases

OmniPCX

Enterprise

Releases

R5.1/R5.1.1/

R5.1.2

OmniPCX

Enterprise

Releases

R6.0 / R6.0.1

OmniPCX

Enterprise

Releases

R6.1/R6.2

OmniPCX

Enterprise

Release

R7.0/R7.1

VPS35 with 32 MB RAM

From 4.0.4 to 5.3.0

Yes Yes No No

8 port VPU 5 board From 4.1.5 to

5.3.0 Yes Yes Yes Yes

16 ports VPU5 From 5.0.1 to

5.3.0 Yes Yes Yes Yes

11.2.2 Minimum configuration

4635J RAM size Disk

Release 4 32 MB 1.4 GB

Release 5 64 MB

(to support VPIM and /or IMAP4)

2.16 GB

• 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.3 Migration

R1 to R4, memory expansion from 16 MB to 32 MB minimum.




11.3 VISUAL MESSENGER HARDWARE AND SOFTWARE COMPATIBILITY

11.3.1 Server SW compatibility

Windows NT 4

workstation

Windows NT 4

server

Windows 2000

Pro

Windows 2000

Server

Windows XP

Access Server Yes

(SP4 min.) Yes

(SP4 min.) Yes (SP3)

Yes (SP3)

No

11.3.2 Client SW compatibility

Windows

95/98

Windows NT 4

workstation

Windows

2000

Windows

ME

Windows

XP

Visual Messenger

Yes Yes Yes (*) No Yes

(*) Available from Visual Messenger R2.008 01 onwards.

11.3.3 Application SW compatibility

4980 Outlook Notes Netscape Internet

Explorer

Visual Messenger

R2 min 97/98/2000/2002 (XP) (Note 1)

4.6/5.0 NA NA

Note 1: Outlook XP to be defined.

11.3.4 Recommended server PC configuration

CPU RAM size Disk

space

Alcatel-Lucent server to be

configured on new order

(Note 1)

Access Server for less than 1000 users

Pentium III 300 MHz

128 MB 2 GB Server Pack 1 Win-NT4 w/s EN

Access Server for more than 1000 users

Pentium III 500 MHz

256 MB 4 GB Server Pack 1 Win-NT4 w/s EN

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.5 Recommended client PC configuration

RAM size

CPU Windows

95/98

WNT4

Workstation

Disk space

Visual Messenger Pentium 133 MHz

32 MB 64 MB 50 MB




12. OMNIVISTA 4760 HARDWARE AND SOFTWARE COMPATIBILITIES

12.1 OMNIVISTA 4760 R3.0

12.1.1 Server configuration requirements

Number of

subscribers

CPU speed

(Intel or

AMD)

RAM

size

Disk

size

Recommended

Alcatel-Lucent

platform

Notes

Non-dedicated server

Less than 250 subscribers /one node / IP connection/

Accounting and config only

1.4 Ghz or higher

512 MB 18 GB Configured by ACTIS

For small capacity

Dedicated server

Up to 5000 subscribers

2 Ghz or higher

640 MB 18 GB Configured by ACTIS

Medium range server

Dedicated server

From 5001 subscribers

Dual processor 2.4 Ghz or higher

1.5 GB

45 GB

Configured by ACTIS

High range server Raid 5

OS Windows Server

12.1.2 Common requirements

Operating system Win 2000 professional or Server SP4 minimum

Win XP SP1 or Win 2003 -

CD-ROM and floppy disk Mandatory -

Video hardware 4 MB –1024 X768 16 Million colors -

Network card Ethernet 10/100bT

Display 17" minimum 19" recommended

Internet Browser Netscape Communicator R4.7 or higher or

Internet Explorer R5 or higher -

Administration client configuration requirements

Administration client installed on another PC than the server is recommended for better performance. Non-dedicated PC.

• Operating system: Win 2000 SP4 professional or Server / Windows XP SP1, Win 2003

• WEB browser: Netscape Communicator 7.0 or Internet Explorer 6.0.

• Hardware:

- CPU Speed 766 MHz or more.

- 384 Mbytes RAM.

- 3 GB hard disk.

- Video Hardware allowing 1024x768 in 16 M colors (4 Mbytes memory or more).

- 17 or 19 inch screen.

- CD-ROM drive.





Minimum hardware configuration:

Model Client Server small

capacity

Server medium

capacity

Server high

capacity

Server very

high

capacity

Capacity (users) < 250, 1 node; IP connection,

Account/Config 250 - 5,000 5,000-20,000 From 20,000

Processor 766 MHz 1.4 GHz 2 GHz Dual 2.4 GHz Dual 3 GHz

Monitor 17" (19" recommended)

Hard disk 3 GB 18 GB 18 GB

45 GB - 15 K rpm - RAID5

with 128 KB cache memory

72 GB - 15 K rpm - RAID5

with 128 KB cache memory

RAM 384 MB 512 MB 640 MB 1.5 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

Netscape version 7.0 and above Internet Explorer version 6.0 and above

Mozilla Firefox R1.0

Disk/CD-ROM Mandatory. DVD is recommended.

Compatibility Non dedicated server (1) Dedicated server (2)

(1) Combined use with other applications (such as Office applications, MS Word, Excel, etc.) on the same PC is

possible, but the PC should not be a server for other applications, except on FTP server.

(2) Domain controller functions, Web server, etc. delivered with the OS must not be installed Nota: ACTIS 9.1 defines a PC Pack 4 (Celeron D330-2,66 GHz/RAM 1 Go/HD 40 Go) for client and a server Pack 3 (Xeon 3GHz/RAM 2Go/HD 216Go for the server)


Minimum hardware configuration: same as OmniVista 4760 R3.1




12.4 OMNIVISTA 4760 R4.0/R4.1



capacity

Server medium

capacity

Server high

capacity

Capacity (users) < 250 250 - 5,000 > 5,000

Processor 766 MHz 2 GHz 2,4 GHz Dual 3 GHz


Hard disk 3 GB 18 GB 18 GB 72 GB - 15 K rpm -

RAID5 with 128 KB cache memory

RAM 384 MB 512 MB 1 GB 2 GB


PFartition NTFS to be able to install Netscape LDAP server

Internet browsers Internet Explorer version 6.0 and above, Mozilla, Firefox R1.0





capacity

Server medium

capacity

Server high

capacity

Capacity (users) Same as Medium 1 - 5,000 > 5,000

Processor 1G Hz Same as Medium 2,4 GHz Dual 3 GHz


Hard disk 40 GB Same as Medium 40 GB 72 GB - 15 K rpm -

RAID5 with 512 KB cache memory

RAM 1 GB Same as Medium 1 GB 2 GB


Partition NTFS to be able to install Netscape LDAP server

Internet browsers Internet Explorer version 6.0 and above, Mozilla, Firefox R1.0





13. BUSINESS INTEGRATED COMMUNICATION SERVER ( BICS )

13.1 BUSINESS INTEGRATED COMMUNICATION SERVER R1.0

13.1.1 Server configuration requirement

BiCS is devivered on a pre integrated PC ( BTCO )

PC is a IBM’s eServer x3250 ( Mabolas )

Config. type Description Qty

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

CD-RW/DVD Combo V Ultrabay Enhanced 1

160GB 7200 RPM 3.5 Simple-Swap SATA HDD 2

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

4365CTO Dual

Core Xeon

2.13GHz 4G-RAM

SS SATA 2x160GB

RAID1 Mouse

x3250 System Planar 1

IBM PREFERRED PRO KEYBOARD - USB

13.1.2 Software compatibilities

Product line delivered with BiCS R1.0 are:

- OXE R8.0

- OmniVista 4760 R4.2




- OTCC R7.1

- OTUC R5.0

13.2 BUSINESS INTEGRATED COMMUNICATION SERVER R2.0

13.2.1 Server configuration requirement

BiCS is devivered on a pre integrated PC ( BTCO )

PC is a IBM’s eServer 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

4194CTO_39Y5533 Rack power cable - 2.8m, 100-240V, C13 to IEC 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

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

4194CTO_44R5766 Dual-Core Intel Xeon E3110 (3.00GHz/1333MHz 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

BICS DC E3110 8GB 2x250GB

4194CTO_44T2004 Riser assembly PCI-E 1

13.2.2 Software compatibilities

Product line delivered with BiCS R2.0 are:

- OXE R9.0

- OmniVista 4760 R5.0 with DMS 1.0.0

- OTCC R8.0.5




- OTUC R5.1 and

- OFS fax server 5.6.3

14. OMNITOUCH CONTACT CENTER SUITE OPERATING SYSTEM AND

HARDWARE COMPATIBILITIES

14.1 OPERATING SYSTEM COMPATIBILIES

14.1.1 OmniTouch Contact Center Suite

See table in section 4.18.3

14.1.2 OmniTouch Contact Center Premium Edition

See table in section 4.18.4

14.2 HARDWARE COMPATIBILITY: MINIMUM PC REQUIREMENT

14.2.1 CCS Supervision

CPU Min/rec RAM size

Min/rec Disk space

Alcatel-Lucent server to be

configured on new order (note 1)

CCSUPERVISION R6.0/R6.0.1

Pentium IV 2 Ghz 512 MB 20GB PC platform 4

CCSUPERVISION R6.1/R6.2/R7.0/R8.0

Pentium IV 2 Ghz

1GB 40GB PC platform 4

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 7.0 up to Excel 2003

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.




14.2.2 CCS Server

CPU Min RAM size Min Disk space Alcatel-Lucent server to be

configured on new order

CCS Server R6.0/R6.0.1

Pentium IV 2 Ghz 512 MB 100 MB available

-

CCS Server R6.1/R7.0/R8.0

Xeon 3,4 Gigas 1GB 144 GBytes PC platform 4

14.2.3 CCWallboard

WBM is installed on CCS platform - see related chapter.

14.2.4 CCA 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 Pentium IV 2 Ghz 512 MB 20Mb available

14.2.5 A4400 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).

CPU RAM size Disk space Alcatel-Lucent

recommended server

OmniPCX Enterprise CCA server R6.0 / R6.0.1

Pentium IV 2 Ghz

512 MB 1Mb available See ACTIS

OmniPCX Enterprise CCA server

R6.1/R6.2/R7.0/R8.0

Xeon 3,4 Gigas

1GB 144 GBytes See ACTIS

14.2.6 Ccweb 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.




14.2.7 CCemail 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

14.2.8 Database requirement

Data base MS SQL MS SQL 7 SP2 or MS SQL 2000 standard edition

14.2.9 Ccoutbound Platform requirements

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




15. APPENDIX

15.1 ACTUAL OMNIPCX ENTERPRISE /4400 RELEASED SOFTWARE RELEASES

As of the 7th January 2008, the following releases are available:

Commercial release Maintenance release

R6.1.1 F2.502.30

R6.2 F3.301.36.a

R7.0 F4.401.24.b

R7.1 F5.401.21.f

R8.0 G1.302.6.e

R8.0/R8.01 G1.503.9

R9.0 H1.301.24

End of document

OMNIPC enterprice

Documents