Technical Communication Omnipcx Enterprise: NB of Pages: 174 Date: 14 October 2005

TECHNICAL COMMUNICATION No. TC0711 Ed.
01
OmniPCX Enterprise Nb of pages : 174 Date : 14 October 2005
URGENT
NOT URGENT TEMPORARY PERMANENT
SUBJECT : INSTALLATION PROCEDURE FOR VERSION F3.301.10 – RELEASE 6.2
This is the technical release of OmniPCX Enterprise with the version F3.301.10. It corresponds to
Release 6.2.
It is available on Alcatel Business Partner Web Site (www.businesspartner.alcatel.com) and on DVD
only with the references 3BA 27681 AAAA (non secured version) and 3BA 27682 AAAA (secured
version).
Technical modes to change the release, new features, registered restrictions and controlled features
are described in the installation procedure for version F3.301.10.
1
OmniPCX Enterprise
INSTALLATION PROCEDURE
FOR VERSION F3.301.10
Release 6.2
Ed. 01 / 14 October 2005

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
F3.301.10 – RELEASE 6.2
CONTENTS
1. APPLICATION DOMAIN ...............................................................8
2. INTRODUCTION TO RELEASE 6.2 ................................................8
3. CONTENT OF THE SOFTWARE PACKAGE...................................11
4. BEFORE STARTING.....................................................................11
4.1 Applications, functionalities not supported by Release 6.2...................... 11
4.2 Applications and functionalities dependent on CPUs and hardware
platform used ......................................................................................... 13
4.3 VoIP network conformity check ............................................................... 14
4.4 Recommendations and security............................................................... 14
4.5 DECT....................................................................................................... 15
5. CONDITIONS FOR INSTALLATION IN NETWORK.......................15

5.1 Installation in network in Release < 3.0 ................................................. 15
5.2 Installation in network in Release 3.0, 3.1, 3.2, 3.2M, 4.1 and 4.1.1 ...... 15
5.3 Installation in network in Release 4.2 and 4.2.1 ..................................... 16
5.4 Installation in network in Release 5.0 Ux, 5.0.1 Ux, 5.0 Lx ..................... 16
5.4.1 OmniPCX Enterprise compatibility ..................................................................17
5.4.2 Audit/Broadcast ..............................................................................................17
5.4.3 Compatibility of external applications.............................................................18
5.5 Installation in network in Releases 5.1.x, 6.0, 6.0.x and 6.1.x................. 18
5.5.1 Compatibility of external applications.............................................................18
5.5.2 Audit/Broadcast ..............................................................................................18
6. COMPATIBILITIES.......................................................................19
6.1 Reminder on boards supporting the Transit function and the direct RTP . 19
6.2 Delay (in one direction) introduced by IP gateways................................. 19
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
6.3 Delay (in one direction) from an IP Phone towards a set behind ACT or
eMG........................................................................................................ 19
6.4 ABC-F2 compatibility depending on the hardware and the type of
configuration used (with or without compressed voice)........................... 20
6.4.1 Rules used in the tables ..................................................................................20
6.4.2 Table of ABC-F2 compatibility.........................................................................21
6.5 Network & VoIP compatibility ................................................................. 24
6.5.1 ABC-F2 trunk group compatibility summary ...................................................24
6.5.2 Number of compressors/algorithms that can be used with INTIP and GD/GA 25
6.6 Alcatel 4635 voice mail compatibility...................................................... 25
6.7 Hardware compatibility .......................................................................... 26
6.7.1 CPU boards ....................................................................................................26
6.7.2 Appliance Server ............................................................................................27
6.7.3 Hard disk capacity ..........................................................................................27
6.7.4 IO2 board.......................................................................................................27
6.7.5 INTIP board ....................................................................................................27
6.7.6 INT1/INT2 boards...........................................................................................28
6.7.7 Negotiation of speed of Ethernet interfaces ....................................................28
6.8 Subdevices & IP Phone compatibility (Reprom reference/Binary version) 29
6.9 Application compatibility ........................................................................ 30
6.10 OEM/External equipment compatibility................................................... 31
6.10.1 UPS..............................................................................................................31
6.10.2 V24 over IP ("Moxa" unit) .............................................................................31
6.10.3 T38 Fax over IP (MP-102 Audiocodes) .........................................................31
7. CLIENT INFORMATION..............................................................31
7.1 Reminder of changes appeared with R3.0 .............................................. 31
7.2 Reminder of changes appeared with R4.1 .............................................. 32
7.3 Reminder of changes appeared in Release 6.1.1 .................................... 32
8. PREPARATION ...........................................................................32
8.1 Checking compatibility............................................................................ 32
8.2 OmniVista 4760 and Firewall ................................................................. 32
TC0711 2 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
8.3 32
8.4 Voice guides ........................................................................................... 33
8.4.1 System voice guides ........................................................................................33
8.4.2 4645 voice guides...........................................................................................33
8.5 OPS ........................................................................................................ 35
8.6 Saving the database (swinst) .................................................................. 35
8.6.1 Rebuilding the database before saving...........................................................35
8.6.2 Saving the rebuilt database ............................................................................36
8.7 Saving Chorus/Linux data....................................................................... 36
8.8 Saving Actis files in the image of the site ................................................ 37
8.9 Saving the lanpbx.cfg file........................................................................ 37
9. OPERATING MODE ....................................................................37

9.1 New business account ............................................................................ 37
9.2 Updating R5.0 Lx, R5.1.x, R6.0.x, R6.1.x to R6.2 ..................................... 37
9.3 OmniPCX 4400 migration to R6.2 ........................................................... 37
9.3.1 Use of the hardware or software key..............................................................38
9.3.2 Crystal hardware compatibility with an Appliance Server ...............................38
10. LOADING THE SOFTWARE.........................................................38

10.1 Generalities ............................................................................................ 38
10.1.1 Security activated by default during a installation .......................................38
10.1.2 Installation of a secured system for VoIP encryption ("IP Touch Security"
service) 39
10.1.3 Using the Remote Download .......................................................................40
10.1.4 Reading the hardware key or CPU-id of the CPUs .......................................40
10.1.5 Creating a blank database ..........................................................................40
10.2 40
10.3 Restoring the database and site tickets ................................................... 41
10.4 Restoring Chorus/Linux data .................................................................. 41
11. TRANSLATIONS .........................................................................41

11.1 Installing OPS files.................................................................................. 42
Ed. 01 / 14 October 2005 3 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
11.2 Remarks ................................................................................................. 42
12. UPDATING THE BETA TEST SYSTEMS..........................................42
13. SYSTEM MANAGEMENT .............................................................43

13.1 Declaring the automatic start-up of the telephone .................................. 43
13.2 Updating the date and time .................................................................... 43
14. CHECKING START-UP OF CPU/IO1/IO2/IO2N...........................43
15. COMPULSORY MINIMUM ADDITIONAL DATABASE

MANAGEMENT ..........................................................................43
15.1 Reminder for sites migrating from Release < 3.0.................................... 43
15.1.1 IP addressing plan (from R3.0) ....................................................................43
15.1.2 IP routing (from R3.0) ..................................................................................44
15.1.3 ABC network (from R3.0) .............................................................................44
15.1.4 ARS Time Schedule management (from R3.0)..............................................44
15.1.5 Time-outs (from R3.0)..................................................................................44
15.1.6 Accounting (from R3.0) ................................................................................44
15.1.7 Filter table (from R3.0) ................................................................................45
15.2 Additional management for IO2N .......................................................... 45
15.3 Synchronization ...................................................................................... 45
15.4 System parameters to check.................................................................... 45
15.4.1 Direct RTP ....................................................................................................45
15.4.2 Frame VoIP (Enhanced quality voice)...........................................................46
15.4.3 Direct RTP for H323 terminals......................................................................46
15.4.4 Inter-node protocol H323 ............................................................................46
15.4.5 Pre-login (V120) ..........................................................................................46
16. STARTING UP THE CPU IN ITS ENVIRONMENT ON SITE.............46

16.1 Downloading the couplers and sets ........................................................ 46
17. CHECKING CORRECT OPERATION.............................................47
18. REFERENCE DOCUMENTS..........................................................48
TC0711 4 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
Ed. 01 / 14 October 2005 5 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
APPENDIXES
APPENDIX 1 - REMARKS & RESTRICTIONS
APPENDIX 2 - COMPARING THE R5.0 Ux AND R6.2 LICENSES
APPENDIX 3 - OmniPCX 4400 MIGRATION TO OmniPCX Enterprise
RELEASE 6.2
APPENDIX 4 - SYNCHRONIZATION
(Synchronizing the OmniPCX Enterprise after migration
to R6.2 with Appliance Server)
APPENDIX 5 - MAIN FEATURES IN PREVIOUS RELEASES
APPENDIX 6 - NEW FEATURES
APPENDIX 7 - CONTENT OF THE SOFTWARE PACKAGE
APPENDIX 8 - KNOWN DEFAULTS
TC0711 6 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
Ed. 01 / 14 October 2005 7 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
1. APPLICATION DOMAIN
WARNING
This document applies to the OmniPCX Enterprise Release 6.2 in standardized version F3.301.10.
The functionalities, performances, limitations and constraints presented are liable to change in later
versions of this Release. To find out the differences between the new version and the information
given in this document, simply refer to the technical communication TC0710 Technical Release Note
for OmniPCX Enterprise Release 6.2 - Version F3.301.10 accompanying each new version.
This document is based around a central document, the Release 6.2 installation procedure, and
appendices which describe:
− The restrictions and remarks.
− The comparison of licenses from R5.0 Ux to R6.2.
− The migration from an OmniPCX 4400 to an OmniPCX Enterprise.
− The synchronization of the system after migration to Release 6.2 with an Appliance Server.
− The reminder of features released in previous releases.
− The new features.
− The content of the F3.301.10 software package.
− The known defaults.
2. INTRODUCTION TO RELEASE 6.2

Release 6.2 (version F3.301.10) is a minor release maintenance.
The program of certification have been changed by ABPP. They are available on BPWS under
Training and Certification > Training > OK > Post-Sales > Alcatel OmniPCX Enterprise > Release
6.2.
REMINDER
Release 6.0, the OmniPCX Enterprise was an evolution of traditional business telephony services with
the launching of a new range of IP application phones so called Alcatel IP Touch 4068 and 4038
(series 8) open to any business applications thanks to an XML interface.
Releases 6.1 and 6.1.1 made it possible, amongst other things:
− to complete the range of series 8 sets by the introduction of the Alcatel IP Touch 4028 sets (with
black and white display) and of the Alcatel IP Touch 4018 sets (with black and white display),
− to introduce the range of series 9 sets named Alcatel 4019-4029-4039 (TDM sets).
Release 6.2 makes it possible, amongst other things:
− to use the Alcatel IP Touch sets in Hotel function
− to implement the "IP Touch Security" feature
TC0711 8 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
New hardware and features from Release 6.2:
New hardware New features Features under PCS (1)

IP Touch Security Modules Chinese characters on IP Touch IRAD board (2)
(SSM, MSM) series 8 & 9 sets (500 characters)
Installation of ACT shelves in Alcatel series 8 & 9 sets in Hotel
computer cabinets function
Support of Thomson ST2020 SIP
phone
IP Touch Security Solution – Voice
encryption
IP Touch Survivability
New icon of supervision of a
forwarded set
MLA / Private line ringer
differentiation
LDAP Call by name display on
2x30 characters
1000 Domains IP / 1000 Entities
Security improvement (system)
Transit R1.5- Russian market
CLIP DTMF on APA (India, Taiwan)
NDDI2 for Australian market
Dynamic coupler initialization for
SLI
Duplication over Ethernet for CPU7
IP Attendant Softphone
IP CCAgent Softphone
Free Desktop
Statistic tickets over IP
Both CPU in two different subnets
Modem, Fax, Data transparency
over IP
XML IP Touch
(1) Premium Customer Support.

The Premium Customer Support process allows the Partner Businesses to profit an assistance on
features or products whose marketing was announced (DR3) but which are not launched yet on
the market. The PCS process replaces the SDP (Specific Deal Process) previous process; refer to
the eFlash EF_Marketing_003_260704.
(2) Available with OmniVista 4760 R3.2.
Ed. 01 / 14 October 2005 9 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
Hardware not released Feature not released

ACT-CH8
RGD
ECAN 64ms for USA
REMINDER
As of Release 5.1, some applications and functionalities of Release 5.0 Ux are no more supported,
and will have to be replaced by others.
This document indicates the steps necessary for installing version F3.301.10 for:
− a new installation,
− an evolution from R5.0 Lx, R5.1, R5.1.x, R6.0, R6.0.1, R6.1 or R6.1.1 to R6.2,
− a migration from OmniPCX 4400 to OmniPCX Enterprise R6.2 controlled by OmniPCX 4400
CPUs or by installing an Appliance Server (AS).
TC0711 10 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
3. CONTENT OF THE SOFTWARE PACKAGE

The software package contains the OmniPCX Enterprise F3.301.10 application.
The different versions of the OmniPCX Enterprise application modules are:
− Linux : 38.0
− Linux Package : 38.4
− swinst : 2.28.0
− PC Installer : 2.20
− OmniPCX Enterprise R6.2 : F3.301.10:
F3.301 complete version
+ F3.301.10 static patch
+ SF3.301.10 secured patch (Note)
Note
The access to secured patch is only given on request after filing the appropriate document posted on
BPWS Support>Technical Support>Software> select Alcatel OmniPCX Enterprise (including
4400)>Release 6.2>OK> International Multipurpose Letter of Assurance / End-User Certificate Form
File.
From Release 6.1.1, dynamic patches will be no more delivered. They are replaced
by static patches ; refer to the technical communication TC0682 Stop of dynamic
patch delivery from Release 6.1.1.
Reference of compatible CD-ROMs and DVD

REMINDER
As of Release 6.1, the software is only delivered on DVD.
CD-ROM/DVD Reference
Version F3.301.10 (DVD) 3BA 27681 AAAA
Version F3.301.10 Secured (DVD) 3BA 27682 AAAA
System voice guides v5.2 3BA 57423 AAAF
OmniVista 4760 – Release 3.2 Software 3BH 11632 ADAA
4. BEFORE STARTING
4.1 Applications, functionalities not supported by Release 6.2
The table below shows all the applications and functionalities which are no more provided by the
OmniPCX Enterprise R6.2, whatever hardware is used.
Migration batches exist including a specific rate, which have been defined and taken into account
automatically by Actis 9.6.
Ed. 01 / 14 October 2005 11 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
Compulsory
deletion/
Family Type of application Migration to modification Documentation
before migrating
to R6.1.1
47xx 4715
4730
OmniVista 4760 R3.2 No TCV065
4740
4740 PTP
R6.0System
4730i OmniVista 4760i Not applicable
Documentation
4755 OmniVista 4760 R3.2
TCV010
4000 Directory Server 4760 LDAP Server
No TCV017
Directory PC Client for 4760 Directory Client TCV065
4755/4000
Voice mail 4635J (default) or
4630 Yes TC0298
4635H2
4620 or VPS35 (1) 4635 VPM35 or VPU5 Yes No
4635 VPCPU 4635 VPM35/VPU5 Yes TC0155, TC0259 &
4635 VPCPU-1 4635 VPM35/VPU5 Yes TC0666
ACT migration 2600, 4600 Delete all equipment and
Yes No
manage it in a new ACT
5400 Delete all equipment and
Yes No
manage it in a new ACT
ACD-V1 ACD-V1 CCD R6.2
Yes TC0487
4735 & 4736 CCS
4961 first party TAPI No migration – Not
Not applicable No
middleware supported
4973 Telephony Not supported -
Assistant (Replaced by OmniTouch Not applicable
UC My Phone)
Others Alcatel Unified Not supported -
Messaging (Replaced by OmniTouch Not applicable
UC)
SPB IO2, IO2N or IP/V24 R6.0 System
No
module Documentation
Datcol No migration – Not
Not applicable Not applicable
supported
Overflow on QoS (VoIP) Not supported No No
CPU2, CPU3, Replaced by
CPU5 Step1 & Step2 CPU5 Step3 - 128 MB,
CPU6 Step2 - 128 MB
CPU7 – 256 MB No No
or Appliance Server
(depends on the Actis
configuration)
LIOe & TSC-LIOe (2) INTIP Yes No
INT1/INT2 INTOF Yes No
TC0711 12 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
(1) VPS35 board is replaced by the VPU5 board for any migration towards OmniPCX Enterprise
R6.1.1.
(2) The boards are not authorized on the nodes of a network. They are authorized only the time of
migration.
LIO boards are in phase out from Release 6.1.1. They are supported by Release
6.2 but can no more be configured for addition or for new installation.
4.2 Applications and functionalities dependent on CPUs and hardware platform used
Depending on the type of CPU used (CPU5 Step3/CPU6 Step2/CPU7, Appliance Server, Call Server
in rack) and the hardware platform used (Crystal or Alizé), certain applications or functionalities are
not authorized.
Functionalities, hardware and applications not supported by R6.1.1 are not shown in the table
below; see paragraph 4.1.
CPU5 Step3 Controlling Appliance Server

CPU6 Step2 Call Server Common
Crystal hardware
CPU7 hardware
Voice mail 4645 No Yes Yes No
4615 / VMU-OBCA Yes No No No Ö 4635J (VPU5) (2)
4615/VMU-OBCA2 (1) (only with CPU6)
Various Campus DECT Yes No No No (4)
DTM for DECT on Yes No Ö No Ö No Ö DECT8 (2)
CPU6 DECT8 DECT8
VG on CPU6 Yes No No No Ö GPA2 (2)
DTMF Yes No No No Ö GPA2 (2)
(on CPU6 & CPU7)
V24 Yes No No No Ö V24-IP module (3)
Music on hold on CPU Yes Yes No Ö Z port No Ö Z port (3)
IO2/OBCA (5) Yes No No No (5)
(only with
CPU5 & CPU6)
IO2N Yes No No No (5)
SPB No Ö IO2 No No No Ö V24-IP module (3)
3 ACT levels Yes No No No (3)
eRMA No Yes Yes No
(1) Can no more be configured in a new business account.

(2) Replacement is carried out by Actis.
The DECT8 board is not compatible with DECT2/DECT4 boards. If DECT2/DECT4 boards are
present, ACTIS will replace them.
REMINDER
DECT2/DECT4 boards are in phase-out. They are supported by Release 6.2 but can
no more be configured for addition or for new installation.
Ed. 01 / 14 October 2005 13 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
(3) Manual modifications are required.

(4) No alternative possible.
(5) Boards IO2, IO2N (30 B channels), OBCA and OBCA2 (3 B channels) do not exist with an
Appliance Server or Call Server. A certain number of applications and functionalities are
therefore no more supported, such as:
• Extension of V24 physical ports via SPB board on which applications were managed
(greeting management, hotel, login, etc.).
• Direct management of data applications in V120 accessible from a terminal adapter (TA
in V120) locally or from the outside (appli login, SLIP, hotel management, etc.).
− Data transmission in the B channel of a digital support (T2, PCM, etc.).
♦ Link in a B channel of a T2 (switched or not switched).
♦ Link in a B channel of a PCM board (often encountered in South America where T2s are
less common).
♦ Link via TA/Modems.
♦ No more back-up signaling via ISDN.
♦ X25 in a B channel (Tunnel operation in T2 and Centrex operation for centralized
network management via 4740).
♦ Frame Relay in the case of saturation of the signaling channel in D.
In this case, the Tunnel, Broadcast and network incident type X25 applications pass
through a B channel (application of over-reservation coefficient 15 in the D channel of a
link allows Frame Relay not to be carried out, but the mechanism still exists).
4.3 VoIP network conformity check

The OmniPCX Enterprise R6.2 is a native IP product when using a CPU-CS or Appliance Server and
in the case of hardware mixing. All signaling exchanged between the Call Server and the Media
Gateways or ACT Media Gateways is transported over IP. It guarantees a reliable IP connection and
respects the VoIP criteria (delay, jitter, packet loss) for VoIP configurations.
VoIP conformity tests are compulsory before deploying the VoIP solution; consult the VoIP
Engineering section on the BPWS for the methodology, recommendations and tools to secure the
VoIP installation. In particular, the VoIP Assessment tool for VoIP Audit and diagnostic help guide is
strongly recommended (available in the Brest training catalog).
CAUTION
With the "Modem, Fax, Data transparency over IP" feature, it is mandatory that the IP network is
almost perfect; see technical communication TC0712 Modem, Fax, Data transparency over IP.
4.4 Recommendations and security

The security rules and recommendations for securing the access and using the system are described
in the System Documentation "Security" section.
The IP services and port numbers used by the system are also available in this section.
TC0711 14 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
4.5 DECT
Each system equipped with DECT needs a unique PARI configured in the system. To obtain the
PARI, consult the e-Flash eND03007D on the BPWS in the News & Events>eFlashes > select
Archived then keyword eND03007D.
5. CONDITIONS FOR INSTALLATION IN NETWORK

REMINDER
It is authorized to operate different releases (Releases ≥ 5.0 Ux) in the same sub-network.
Cohabitation in a single sub-network with Releases < 5.0 Ux is only authorized to allow progressive
migration to the latest release.
During progressive migration and depending on certain topologies and hardware

used, there may be poor audio quality; see chapter 6 .
If using a CCS multi-site, each node must be in Release 6.2.
5.1 Installation in network in Release < 3.0

Releases < 3.0 are no more supported but in order to allow a progressive migration, Release 6.2
can cohabit in an OmniPCX 4400 sub-network made up of systems in Release 2. However, one of
the minimum versions below must be available in order to have compatibility at ABC-F signaling
level:
− B3.317.33,
− B3.355.6,
− B3.374.1,
− B3.513.10,
− B3.514, B3.515, B3.516, B3.517, B3.519.
During the cohabitation period, the tunnel does not operate as well as the broadcast.
CAUTION
The X25 tunnel is not compatible between OmniPCX Enterprise versions (≥ R5.0 Lx) and networks
with nodes in Releases below 3.0.
If all the nodes of the sub-network are in Release 6.2, this management is of no use, access to the
IP/X25 tunnel is obtained by physical addressing (no management) (as of Release 3.0).
5.2 Installation in network in Release 3.0, 3.1, 3.2, 3.2M, 4.1 and 4.1.1
Releases 3.0, 3.1, 3.2, 3.2M, 4.1 and 4.1.1 are no more supported but in order to allow a
progressive migration, they can cohabit for a time in an OmniPCX Enterprise sub-network made up
of systems in Release 6.2.
During the cohabitation period you must:
− Prohibit broadcasting of the database and not carry out any audit.
Ed. 01 / 14 October 2005 15 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
− Prohibit the use of entity numbers greater than or equal to 127.
During this progressive migration and depending on certain topologies and

hardware used, there may be poor audio quality; see chapter 6 .
During a progressive migration in an IP network, the INTIP board can be connected to an

LIOe board on the condition that the new services provided by INTIP as of Release 4.2 are
not enabled. The Direct RTP parameter must be set to No.
• The Enhanced voice quality parameter, now called Framing VoIP since Release
5.1, must be identical on all the nodes of the network.
• The Inter-node protocol H323....... parameter must be set to No.
• There is no more VPN overflow on QoS in VoIP.
In Release 6.2:
− LIOe and TSC-LIOe boards must be replaced by INTIP boards
− INT1and INT2 boards must be replaced by INTOF/INTOF2 boards
5.3 Installation in network in Release 4.2 and 4.2.1

Releases 4.2 and 4.2.1 are no more supported but in order to allow a progressive migration, they
can cohabit for a time in an OmniPCX Enterprise sub-network made up of systems in Release 6.2.
During the cohabitation period you must:
− Prohibit broadcasting of the database and not carry out any audit.
− Prohibit the use of entity numbers greater than or equal to 127.
During this progressive migration and depending on certain topologies and

hardware used, there may be poor audio quality; see chapter 6 .
In Release 6.2:
− LIOe and TSC-LIOe boards must be replaced by INTIP boards.
− INT1and INT2 boards must be replaced by INTOF/INTOF2 boards.
5.4 Installation in network in Release 5.0 Ux, 5.0.1 Ux, 5.0 Lx

CAUTION
Release 5.0 Lx is no more supported but in order to allow a progressive migration, it can cohabit for
a time in an OmniPCX Enterprise sub-network made up of systems in Release 6.2.
In Release 6.2, the number of entities and IP domains changes to 1000 (in Releases < 6.2,
the number of entities is 255 and the number of IP domains is 128). In a network, these
limits are allowed only if each node of the network is in Release 6.2.
During the cohabitation period you must prohibit broadcasting of the database and not
carry out any audit.
TC0711 16 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
5.4.1 OmniPCX Enterprise compatibility

Releases 5.0 Ux, 5.0.1 Ux and R5.0 Lx are compatible with Release 6.2 in a sub-network
environment, with the following restrictions:
• Minimum compatible versions: D2.314.4.c; D2.314.5; E1.604.9.f.
• The Enhanced voice quality parameter, now called Framing VoIP in R5.1, must be
identical on all the nodes of the network.
• The LIOe and TSC-LIOe boards are authorized only the time of migration. They also must be
replaced in heterogeneous network functioning. There should not be LIOe, TSC-LIOe boards
in a network with nodes in R6.0 and/or R6.2.
• The Inter-node protocol H323 parameter must be set to Yes. It must be set to No if
LIOe boards are used.
• There is no more VPN overflow on QoS in VoIP on the whole network.
• See table in 6.4.2 .
In Release 6.2, INT1and INT2 boards must be replaced by INTOF/INTOF2 boards.
5.4.2 Audit/Broadcast
− Audit
All the tables not implemented in a Release generate the message below in the results of the
audit for these messages:
Not Audited: Not implemented in the version but does not cause a
blockage of the audit.
− Broadcast
On receipt of an unknown object in a Release, an error is signaled and an incident is generated.
To delete these errors, the minimum versions below must be used:
• D2.314.4.c • E1.604.9.f
• D2.314.5
The following tables are not broadcast:

• inst/desc/SIO parameters
• data/data prefix
• inst/desc/free numbers range list
Ed. 01 / 14 October 2005 17 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
5.4.3 Compatibility of external applications
In a heterogeneous network, it is essential to align the application versions with

those of Release 6.2.
See paragraph 6.9 for the versions of applications compatible with Release 6.2.
Certain applications are no more supported by Release 6.2; see paragraph 4.1.
5.5 Installation in network in Releases 5.1.x, 6.0, 6.0.x and 6.1.x

Releases 5.1.x, 6.0.x and 6.1.x are compatible with Release 6.2 in a sub-network environment with
the following restrictions:
• The LIOe and TSC-LIOe boards are authorized only the time of migration. They also must be
replaced in heterogeneous network functioning. There should not be LIOe, TSC-LIOe boards
in a network with nodes in R6.2 (from R6.0).
• The Inter-node protocol H323 parameter must be set to Yes. It must be set to No if
LIOe boards are used.
• In Release 6.2, the number of entities and IP domains changes to 1000 (in Releases < 6.2,
the number of entities is 255 and the number of IP domains is 128). In a network, these
limits are allowed only if each node of the network is in Release 6.2.
5.5.1 Compatibility of external applications
In a heterogeneous network, it is essential to align the application versions with

those of Release 6.2.
See paragraph 6.9 for the versions of applications compatible with Release 6.2.
Certain applications are no more supported by Release 6.2; see paragraph 4.1.
5.5.2 Audit/Broadcast
− Audit
All the tables not implemented in a Release generate the message below in the results of the
audit for these messages:
Not Audited: Not implemented in the version but does not cause a
blockage of the audit.
− Broadcast
On receipt of an unknown object in a Release, an error is signaled and an incident is generated.
To delete these errors, the minimum versions below must be used:
• E2.404.b • E2.504.1.e
• E2.502.2.e
TC0711 18 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
The following tables are not broadcast:

• inst/desc/SIO parameters
• data/data prefix
• inst/desc/free numbers range list
6. COMPATIBILITIES
6.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) Yes No
INTIP or INTIP2 Yes Yes
GD or GA No Yes
(1) The LIO-COMP6 board is not compatible in R6.0.x, R6.1.x and R6.2. It is not authorized in a
network with INTIP or GA/GD.
(2) The LIOP/B/X boards are supported by Release 6.2 but can no more be configured for addition
or for new installation.
(3) The LIOe board is not compatible in R6.0.x, R6.1.x and R6.2. The functioning with a LIOe board
is authorized on an other node only if it is a progressive migration.
(4) There is no transit in G711 but packetization/depacketization.
6.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 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
Ed. 01 / 14 October 2005 19 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
6.4 ABC-F2 compatibility depending on the hardware and the type of configuration
used (with or without compressed voice)
The table in paragraph 6.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 6.2. This table takes into account both a
connection in VoIP and a T2, T0 or T1 type wire connection.
6.4.1 Rules used in the tables

Note
In this document, "Direct RTP" corresponds to "Direct RTP in network".
• A maximum delay of 200 ms "One way" (one way, IP equipment + network) is authorized
through IP (400 ms in Round Trip Delay). Beyond that, voice quality deteriorates.
• There can not be more than two passages in G711 during a call (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 Releases 6.2 (from Release 6.0) nor on any node of a network
even the versions allow it. They are authorized the time of migration.
• H323 terminals are only compatible with configurations which allow to have a maximum delay
of 200 ms "One way".
• 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.
TC0711 20 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
• Below are the different representations of the configurations used.
R4.2
à represents an OmniPCX 4400 in R4.2 to R5.0.1 Ux
R5.0.1Ux
OmniPCX 4400
represents an OmniPCX Enterprise controlled by a CS or

AS with common hardware (OXO common hardware)
mniPCX Enterprise R5.1.2

IP Rack Server
Crystal IP Server: represents an OmniPCX Enterprise

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

IP Gateway connected to the A4400 type PABX via an
Crystal IP Media Gateway
INTIP (Remote IP)
represents a Media Gateway connected to the

PABX via a GD
Common hardware IP Media Gateway
, ,
= OmniPCX 4400 or OmniPCX Enterprise connected in wired
ABC-F2 to an OmniPCX Enterprise R6.2. 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 R6.2. 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.
6.4.2 Table of ABC-F2 compatibility
Ed. 01 / 14 October 2005 21 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
OmniPCX Enterprise
IP Rack Server Crystal Server
R5.0 Lx (a) R6.2 R6.2
Without With Without common With common
Crystal IP MGW Crystal IP MGW hardware hardware
G72x G711 G72x G711 G72x G711 G72x G711 G72x G711
G711
O Yes Yes Yes Yes Yes Yes Yes Yes
(Note 11) (Note 11)
m / (Note 1) (Note 1) (Note 3) (Note 3) (Note 1) (Note 1) (Note 1) (Note 3)
n (b)
VoIP
i R W/out Yes Yes Yes Yes Yes Yes Yes
P 5. compre No No No
(Note 6) (Note 6) (Note 8) (Note 2) (Note 2) (Note 8) (Note 8)
C 0. ssion (c)
X 1
U G723 Yes Yes Yes Yes Yes Yes
4 x No No No No
(Note 3) (Note 3) (Note 1) (Note 1) (Note 4) (Note 4)
4 / (d)
0
Yes Yes Yes Yes Yes
0 G729 No No No No No
VoIP
(e) (Note 8) (Note 2) (Note 2) (Note 8) (Note 8)
C G711
R Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Y R / (Note 1) (Note 1) (Note 1) (Note 1) (Note 3) (Note 3) (Note 1) (Note 1) (Note 1) (Note 3)
5. (b)
S
T 1. W/out Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
A x compre (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1)
L ssion (c)
to
S Yes Yes Yes Yes Yes Yes
No No No No
E R (Note 3) (Note 3) (Note 1) (Note 1) (Note 3) (Note 3)
6. With (d)
R
2 compre
V
ssion Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
E
R (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1)
(e)
R
No No No No No No No No No No
5
0
H G L Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
C A 7 x (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 7) (Note 7) (Note 7) (Note 7)
O R 2 R No No No No No No No No
M D 3 5 No No
(Note 10) (Note 10) (Note 9) (Note 9) (Note 9) (Note 9) (Note 9) (Note 9)
M W / 1
O A G x
N R 7 t
E 2 o Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
9 R (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 7) (Note 7) (Note 7) (Note 7)
6
2
x
R Yes Yes Yes Yes Yes
No No No No No
5 (Note 1) (Note 1) (Note 1) (Note 1) (Note 1)
0
H L Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
C A x (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 7) (Note 7) (Note 7) (Note 7)
O R
G R No
Yes No Yes No Yes Yes Yes Yes Yes
M D
7 5 (Note 1) (Note 10) (Note 1) (Note 10) (Note 1) (Note 1) (Note 1) (Note 9) (Note 9)
M W
1 1
O A
1 x
N R t
E o Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
R (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 1) (Note 7) (Note 7) (Note 7) (Note 7)
6
2
x
TC0711 22 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
(a) Release 5.0 Lx is no more supported.

(b) 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.
(c) 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.
(d) 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.
(e) 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
• Minimum compatible versions: D2.314.4.c; D2.314.5; E1.604.9.f; E2.404.b; E2.502.2.e; E2.504.1.e
2 • Direct RTP disabled
• VoWLAN are not authorized
• SIP is not authorized
• It is essential that the T2/T0/T1 access be connected to the Crystal IP (ACT) Media Gateway
• It is essential that the T2/T0/T1 access be connected to the Crystal IP Server or Crystal IP (ACT) Media
Gateway
5 • To lift the prohibition, the LIOe boards must be replaced by INTIPs
• There must not be more than one passage in G711 PABX end in common hardware
• There must be no LIOe board (compulsory)
• It is essential that the IP trunk group be managed on a Crystal IP (ACT) Media Gateway
9 • 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
10 • 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
• Yes if there is no compression on the OmniPCX 4400
• No if G711 is used on the OmniPCX 4400
Ed. 01 / 14 October 2005 23 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
6.5 Network & VoIP compatibility
6.5.1 ABC-F2 trunk group compatibility summary
Release 6.2 Observation

< Release 4.2 ABC trunk group only Progressive migration to a network is
(No compatibility, but possible, see paragraphs 5.1 and 5.2
progressive migration
authorized (1)
Release 4.2/Release 4.2.1 See table in 6.4.2
Audit/Broadcast: D2.304.4.w minimum
4645 voice mail: centralized 4645 not
supported
Release 5.0 Ux Total See table in 6.4.2
ABC-F compatibility Audit/Broadcast: D2.314.4c - D2.314.5
(2) (3) 4645 voice mail: centralized 4645 not
supported
Release 5.0 Lx (4) Total See table in 6.4.2
ABC-F compatibility Audit/Broadcast: E1.604.9.f minimum
(2) (3)
Releases Total See table in 6.4.2
5.1/5.1.1/5.1.2 ABC-F compatibility
6.0/6.0.1 (2) (3)
6.1/6.1.1
6.2
(1) During progressive migration, voice quality problems may appear.

(2) See Appendix 1.
(3) The use of LIOe board can cause problems of audio quality.
(4) This Release is no more supported. Only the progressive migration is allowed.
TC0711 24 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
6.5.2 Number of compressors/algorithms that can be used with INTIP and GD/GA
The term INTIP concerns INTIP boards as well as INTIP2.
REMINDER
LIO COMP6 and LIOe boards are prohibited as soon as there is a node in R6.0.x, R6.1.x or
R6.2 in the network. Moreover, the LIO-COMP6 boards are not authorized in a network
with INTIP or GA/GD.
G711 G723.1 G729

With or w/out VAD With or w/out VAD With or w/out VAD
INTIP with 32 ms echo GIP6A 14 14 14
2 daughter cancellation GIP6 56 56 56
boards 64 ms echo GIP4-1 16 16 16
(1 & 2) cancellation GIP4-4 60 60 60
GD or GA 32 ms echo MCV8 8 7 7
cancellation MCV24 24 21 21
64 ms echo MADA-1 8 8 8
cancellation MADA-3 24 24 24
(1) It is not authorized to have two daughter boards of different types on a same INTIP board.
(2) The echo delay is not configurable, it depends on the hardware used.
6.6 Alcatel 4635 voice mail compatibility

CAUTION
Check the compatibility of backplanes; refer to the technical communication TC0155 Compatibility
of Alcatel 4635 with OmniPCX 4400 backplanes (Reminder of restrictions).
Below is a reminder of the compatibility between Alcatel 4635 and OmniPCX Enterprise R6.2
software.
OmniPCX Enterprise
VPCPU VPCPU-1 VPS35 VPS35 (Note)
Release
SCSI Disk IDE Disk 16 MB RAM 32 MB RAM
Ø
6.2 Incompatible Incompatible Incompatible Incompatible
OmniPCX Enterprise VPM35 (Note) VPM35 VPU5 (M)

Release 32 MB RAM 64 MB RAM 16 ports
Ø Min. Max. Min. Max. Min. Max.
6.2 4.0.4 5.2.6 4.0.4 5.2.6 5.0.1 5.2.6
Notes
− VPS35 board is replaced by the VPU5 board for any migration towards OmniPCX Enterprise R6.2.
− IMAP (A4635 version 5.2.6 minimum) and VPIM (A4635 version 5.1.4) require 64 MB of RAM.
− Any problem found on a mini or intermediate version as regards maximum version must be the
subject of a realignment of the maximum version before escalating the problem.
Ed. 01 / 14 October 2005 25 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
6.7 Hardware compatibility

As of Release 5.1, the mixing of hardware (crystal hardware & common hardware) is authorized.
− In the case of a CPU-CS or an Appliance Server, a single Crystal IP Media Gateway can be
connected in the main zone to support operations such as 4635H2-J, DECT8, etc. Voice Hub,
M1 or M2 are the supported cabinets.
− In the case of a CPU-CS or an Appliance Server with Crystal IP Media Gateways in the peripheral
zone, there are no restrictions.
− In the case of an Appliance Server controlling crystal hardware in the main zone, there are no
restrictions on the hardware used
REMINDER
As of R5.0 Lx, only 1U and 3U shelf racks can be used: 2U shelf racks are not authorized.
For more details, see technical communications TC0418 Compatibilities & Evolutions.
6.7.1 CPU boards
CPU2, CPU3 Step1/Step2/Step3 and CPU5 Step1/Step2 boards are not compatible
with Release 6.2.
CPU5 Step3 128 MB and CPU6 Step2 128 MB boards can be used with either the hardware
key (dongle) or with the CPU-Id (software key). The CPU7 can only be used with the CPU-
Id.
The table below indicates the editions of compatible boards.
REMINDER
The CPU5 boards have only a 10 Mbits Half Duplex Ethernet interface.
Using the Using the Update possible of the CPUs in

hardware key CPU-Id after-sales service
3BA27038 NAAC Yes No Yes, becomes 3BA27038 NABC
CPU5 Step3
3BA27038 NABC Yes Yes Not applicable
3BA 23197 BAAB Yes No Yes, becomes 3BA 23197 BAWB
3BA 23197 BAWB Yes Yes Not applicable
3BA 23197 BABB Yes No Yes, becomes 3BA 23197 BAXB
3BA 23197 BAXB Yes Yes Not applicable
CPU6 Step2
3BA 23197 BACB Yes No Yes, becomes 3BA 23197 BAYB
3BA 23197 BAYB Yes Yes Not applicable
3BA 23197 BADB Yes No Yes, becomes 3BA 23197 BAEB
3BA 23197 BAEB Yes Yes Not applicable
CPU7 3BA 23259 AA No Yes Not applicable
For more details on the CPU6 Step2, see the technical communication TC0230 CPU6 Step2 board -
3BA 23197 AA.
TC0711 26 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
6.7.2 Appliance Server

Only Alcatel recommended Appliance Servers (X305 and X306 of IBM) are to be used.
• X305:
♦ Alcatel reference: 3BA 00438 AA
♦ IBM reference (in case of external purchase): Model Type : 8673-62X
• X306:
♦ Alcatel reference: 3BA 27582 AB
The installation of X306 can be carried out only as of PC Installer v2.17.
CAUTION
AS X306 must only be ordered by Alcatel.
6.7.3 Hard disk capacity

A hard disk with a minimum of 6 GB must be used.
6.7.4 IO2 board

The IO2 and IO2N boards must be flashed with a boot of at least version 4.0.
6.7.5 INTIP board

The term INTIP concerns INTIP boards as well as INTIP2.
Since Release 5.0 Ux, the INTIP board can be used either in full duplex or in half duplex.
As of Release 5.1, direct RTP is possible with INTIPs.
Since Release 4.2, the INTIP board is multi-functional: IP Phones, Remote IP and VoIP link.
The functioning with a LIOe board is authorized only the time of migration.
As soon as the migration is completed, you should set the IP services so that the new services
provided by the INTIP board since R4.2 can be used; refer to the System documentation.
The INTIPB board can function at 100 Mbits in all types of shelves. For VH and WM1 cabinets, the
operation depends on the version used; see the table below.
The INTIP board does not function with LIOP/B/X COMP6 in a single network.
The LIOe board is not authorized with the IINTIP boards. They are authorized only the time of
migration.
Transit is possible between:
− INTIP - LIOe,
− INTIP - LIO COMP2.
The INTIP board can not be used with the Ethernet embedded (a CBC1 10/100 connector must be
used).
The CBCA connectors of the LIOe board should not be used to connect an INTIP
board.
Ed. 01 / 14 October 2005 27 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
The INTIPA board can be used at 100 Mbits. With a VH, it is essential to use the Patch Panel 10/100
Mbits Reference 3BA23244 AAAA 01.
Compatibility at 100 Mbits of VH and WM1 shelves for use of CPU6 Step2 and CPU7 boards.
The CPU7 board is not allowed in a VH cabinet.
All types of shelves are or will be compatible at 100 Mbits. For VH and WM1 cabinets, compatibility
at 100 Mbits is available with the following 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 Batteries batch 1.2 Ah battery autonomy 3BA 57106 AC
WM1 Batteries batch 1.2 Ah battery autonomy - USA 3BA 57106 UB
Note
If the shelves referenced above are not used, the CPU6 Step2 and CPU7 boards only function at a
maximum of 10 Mbits.
6.7.6 INT1/INT2 boards
6.7.7 Negotiation of speed of Ethernet interfaces

Refer to the technical communication TC0680 Risk of wrong negotiation of speed and duplex mode
of Ethernet interfaces for INTIPs, GA & GD after software upgrades.
TC0711 28 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
6.8 Subdevices & IP Phone compatibility (Reprom reference/Binary version)
Type Use Reprom Reference

Subdevice 2G Asynchronous V24 (4083 ASM) V24/V110/V14 V24 A1 3.01
Asynchronous V24 (4083 ASP) V24/V110/V120 V24 A2 2.06
Asynchronous V24 MAC/PC MPC 3.10
Synchronous V24 (4083 SYV) V24 (adapt. V35/V36) V24 S1 1.04
Synchronous X21 (4083 SYX) X21 X21 1.01
Non-powering S0 (4084 IS) S0 S0 3.14
Z behind UA (4085) Z set 1.09
Subdevice 3G A4091 CTI CTI OSI 4.211
A4093 ASY-CTI V24 (V110, V14) + CTI V24 A1 3.01 / OSI 4.204
A4094 ISW S0 S0 4.05
A4094 ISW-CTI S0 + CTI S0 3.16 / OSI 4.06
A4095 AP Z behind UA OSI 4.211
IP Phone A4097 Subdevice DECT + CTI 1.51
A4098 RE (1) TSC-IP / IP Phone V1 5.2
A4098 FRE TSC-IP / IP Phone V1S 3.0
e-Reflexe IP Phone V2 2.26
IP Touch A4038 & A4068 NOE C IP & NOE D IP 1.29.02
Alcatel series 8 A4018-A4028-A4038-A4068 IP Touch A, B, C, D 3.13.04
Alcatel series 9 A4019-A4029-A4039 Sets A TDM, B TDM, C 3.10.00
TDM
(1) IP V1 (4098 RE) and V1S (4098 FRE) sets are no more supported from Release 6.0. Nevertheless,
it can be connected on Release 6.0.x, 6.1.x or 6.2 but no binary correction will be done.
Ed. 01 / 14 October 2005 29 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
6.9 Application compatibility
Applications Minimum version (Note 1) Released version

PC Installer 2.20 2.20
A4058 (SBC) Migration with version 4.016.2 Migration with version 4.016.2
A4059 (Multimedia operator) 4. 016.2 4.016.2
MMK keyboard (A4059) 3.8 3.8
TA/MAC (A4059) 4.7 4.7
MMK keyboard (A4049) 3.8 3.8
TA/PAC (A4049) 1.11 1.12
4059 Management No more supported
PC client No more supported as of Release 5.1 (see § 4.1)
A4615 3.0.24 3.0.24
A4635H2 5.2.6 5.2.6 (Note 2)
A4635J (VPU5) 5.2.6 5.2.6 (Note 2)
CCA 6.2.8.1 6.2.8.1
CCTA 6.1.10 6.1.10
CCZ 6.1.0.2 6.1.0.2
CCIVR 6.2.0 6.2.0
CCO 6.2.1.0 6.2.1.0
CCS & CCS Light 6.2.90.0 6.2.90.0
CCS Server 6.1.1 6.1.1
ASM External Server 6.1.2 6.1.2
WBM 6.0.1.3 6.0.1.3
A4735 No more supported as of Release 5.1 (see § 4.1)
A4715 (Charging) No more supported as of Release 5.1 (see § 4.1)
A4730/4740 (Management) No more supported as of Release 5.1 (see § 4.1)
OmniVista 4760 3.2.04.00.a 3.2.04.00.a
Alcatel Audio Station (AAS) 7.2.1 7.2.1
Visual Messenger R2 No more supported as of Release 6.0
Alcatel Unified Messaging 2.3 No more supported as of Release 5.1 (see § 4.1)
OmniTouch Unified Communication R2.0 No more supported as of February 2005
OmniTouch Unified Communication R3.0 3.0.6 3.0.6
Notification Server R2 2.08c 2.08d
TAPI Premium Server R3 3.2 3.2
TSAPI Premium Server 6.1 6.1
XML Telephony Enterprise R5.1 2.2 2.2
Wizard for common hardware No supported
Wizard for crystal hardware No supported
Datcol No more supported as of Release 5.1 (see § 4.1)
Notes
1 Allows operation with Release 6.2 but in the event of problem, the update in the released version
will be required before any investigation.
TC0711 30 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
2 The IMAP function is available from A4635 version 5.2.6.

The VPU function is available from A4635 version 5.1.4.
6.10 OEM/External equipment compatibility
6.10.1 UPS
In the case of a local 110 Volt power supply, the following MGE UPSs are compatible with the
Appliance Server concerning power cuts and battery management:
− Pulsar Evolution (Serial)
− Pulsar ESV+
− Pulsar EX
− Pulsar ES+
− Pulsar EXtreme C
− Pulsar / Comet EXtreme
− Comet / Galaxy (Serial)
The UPSs referenced in the catalog are not compatible for countries using 110/127V.
6.10.2 V24 over IP ("Moxa" unit)

On the CPU of the Call Server, a single V24 port is available and reserved for the local console. If
an application needs a V24 connection with the Call Server (AHL over V24, real time alarms, etc.),
then the "Moxa Nport Server Lite" unit must be used.
This item allows V24 calls over IP with the Call Server. Four DB9 connectors are available on the
unit. See the System documentation for management of this equipment.
6.10.3 T38 Fax over IP (MP-102 Audiocodes)

Operation is supported with the MP-102 equipment version 4.0 for Fax transmissions only.
See the technical communication TC0336 Setting the T38 fax over IP application (with MP-102
version 4.0).
7. CLIENT INFORMATION
The purpose of this section is to specify the changes in ergonomics or operation that will be visible to
users after changing versions. It's the same level of changes than R3.0 and 4.1.
7.1 Reminder of changes appeared with R3.0

− Digital sets
• Storage of no replied local/internal calls (consulting using the message key).
• Storage of no replied ISDN calls on all sets with display: 4011, 4012, 4023, 4034, 4010,
4020, 4035.
Ed. 01 / 14 October 2005 31 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
− Attendants
• Call between attendants.
• New call statistic distribution.
− 4040 set
• This set is no more supported from Release 3.
− UA 3G sets
• Following a translation, the existing 3G sets remain in 2G mode emulation. Their change
(where appropriate) to 3G mode is done by management (Users). The UA 3G sets created
from Release 3.2 are in 3G mode by default.
7.2 Reminder of changes appeared with R4.1

− Twin set (Tandem)
• Management of "Partial Busy of the set".
• Enhancement of supervision function.
7.3 Reminder of changes appeared in Release 6.1.1

From Release 6.1.1, new icons of supervisions are available regarding the IP Touch sets; refer to the
Appendix 6.
8. PREPARATION
The purpose of this paragraph is to mention everything that the technician needs to prepare before
starting the change of version.
8.1 Checking compatibility

Before starting, it is essential to review all the applications, hardware and functionalities which
should evolve.
See paragraph 4 .
8.2 OmniVista 4760 and Firewall
If OmniVista 4760 transits via a client network with a Firewall, port 113 (AUTH)
should not be filtered in the Firewall. Otherwise since OmniVista client does not
reply on this port, the connection is made too late and the ftp part of OmniVista
4760 does not work. This implementation of the ftp server did not exist in Chorus.
8.3
TC0711 32 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
8.4 Voice guides

Ensure that you have the voice guides required in Release 6.2.
8.4.1 System voice guides

The version of system voice guides compatible with the OmniPCX Enterprise R6.2 is v5.2 CD-ROM
reference: 3BA 57423 AAAF.
The following files are provided on the CD-ROM:
− Voice guide transfer tool.
− Business generic voice guides in language 1.
− Business standard voice guides in language 1.
− Hotel generic voice guides in languages 2&3.
− Hotel standard voice guides in languages 2&3.
− Alcatel music on hold.
− Voice guide documentation.
They can be downloaded from the BPWS section Support>Technical Support>Software> select
Alcatel OmniPCX Enterprise (including 4400)>System Voice Guides>OK.
8.4.2 4645 voice guides

The version of the 4645 voice guides is v1.5. CD-ROM reference: 3BA 27588 AAAC
The following files are provided on the CD-ROM:
− Voice guide transfer tool.
− Voice guides in 39 languages in law A.
− Voice guides in 20 languages in law µ.
− Voice guide documentation.
They can be downloaded from the BPWS section Support> Technical Support>Software> select
Alcatel OmniPCX Enterprise (including 4400)>Software 4645 Voice Guides>OK.
Ed. 01 / 14 October 2005 33 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
The following languages are available:
Country Code Law A Law µ

Arabic female AR1 x
Arabic male AR0 x
Cantonese CA0 x x
Catalan ES1 x
Croat HR0 x
Czech CS0 x
Danish DA0 x
Dutch NL0 x x
English EN0 x x
English Australia AS0 x
English United States US0 x x
Finnish FI0 x x
Flemish NL1 x
French FR0 x
French Canada FR2 x x
German DE0 x x
Greek GR0 x
Hungarian HU0 x
Icelandic IS0 x
Italian IT0 x x
Japanese JP0 x x
Korean KR0 x x
Latvian LV0 x
Lithuanian LT0 x
Mandarin China CN0 x x
Mandarin Taiwan CN1 x x
Norwegian NO0 x x
Polish PL0 x x
Portuguese PT0 x x
Portuguese Brazil PT1 x x
Romanian RO0 x
Russian RU0 x x
Slovak SK0 x
Slovenian SI0 x
Spanish ES0 x
Spanish United States ES2 x x
Spanish Latin America ES3 x x
Swedish SV0 x x
Turkish TR0 x
TC0711 34 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
8.5 OPS
The Actis version for the OmniPCX Enterprise is 9.6, the catalog is referenced E05.
The locks are based on a software key which is unique. This software key is calculated according to
the licenses and the physical number of the CPU.
For each CPU-CS, Appliance Server or CPU5 Step3, CPU6 Step2, CPU7 a unique physical number
exists (called CPU or CPU-id identifier). This number is engraved in a PROM of each CPU.
Note
In the case of a CPU5 Step3, CPU6 Step2, the "hardware" key can always be used. The CPU7 board
accepts only the CPU-Id.
In the case of a CPU-CS, Appliance Server or 4400 CPU replacement, the license files must be
updated on the system within 30 days. The description of the CPU exchange process is available on
BPWS in the e-Licensing service/Re_Hosting section.
In the event of a migration from ANY Release to R6.2 even without adding of license or
hardware, it is mandatory to reconfigure the system by Actis.
CAUTION
To be able to manage future additions with the Photoconfig process, the 4760 locks must be
installed (manually) on OmniPCX Enterprise in the case of a first installation or in the case of
addition of 4760 locks ; refer to the System documentation.
As of Release 6.2, the Migration Release (165) lock is set to 34.
− Make a configuration request in Release 6.2 with the version OPS E05. Four or five R6.2 OPS
files will be generated:
• <offer_id>.zip
• <offer_id>.swk (this file results from the eLP)
• <offer_id>.hw
• hardware.mao
• <offer_id>.sw4760 (if a 4760 is present)
− In the case of the migration of an OmniPCX4400, the lock files of the site (photoconfig) should
be put in Actis. Actis 9.6 will then allow you to migrate these locks (in "Migration to OXE" Offer)
by proposing migration packages for the functionalities and hardware not supported by R6.2.
8.6 Saving the database (swinst)

In the current version, carry out the following operations.
8.6.1 Rebuilding the database before saving
login mtcl
directory /DHS3data/mao
command /DHS3bin/fab/fichges recover all (if R ≤ 1.5.2)
fichges force_recover_dico (if R > 1.5.2)
This operation may be long and it is essential not to interrupt it while running.
Ed. 01 / 14 October 2005 35 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
8.6.2 Saving the rebuilt database

Carry out the back-up in swinst and transfer it to disk or PC.
CAUTION
− Do not choose the save option "Save for rebuilt".
− Do not use a base saved in "Automatic save".
REMARKS: On the saving of charging tickets.
Sites going from A9.5xx to R6.2 which wish to retain client tickets (hotel or hospital type) in the
‘TABJUSTIF’ files should "empty" the administrative tickets before saving as these are no more
processed as of R3.0. As of R3.0, administrative tickets are stored in compressed files.
Sites going from R1.5.2 to R6.2 which already have compressed files should save them as they will
be compatible.
CAUTION
− The shelves already created in position 18 and 19 must be moved before the translation. If this is
not done, they will not start. In fact, when migrating from OmniPCX 4400 to OmniPCX Enterprise
R6.2 with change of CPU 4400 by an Appliance Server, there is an automatic translation of
shelves created in these 2 positions. This automatic translation does not exist if the CPU of type
4400 are retained.
− There is no automatic translation from Releases below 1.5.3 to Release 6.2. For all these
versions, it is essential to go via an intermediate translation in a release compatible with
translation to R6.2 (from R1.5.3 to R5.1.2).
− There is no automatic translation from the Custom Release 3.0C (C1.580.1) to Release 6.2. It
is essential to carry out an intermediate translation with Custom Release 3.2-C2 (C1.762.18
minimum).
8.7 Saving Chorus/Linux data

REMINDER
If there are no disk drives, the back-up version of the OmniVista 4760 tool must be used; see the
OmniVista 4760 technical documentation.
As the IP addressing plan has changed since Release 3, it is not possible to reuse the Chorus data
from a previous version in its current state.
The restoration of Chorus data from a previous release is possible only in the case of a intermediate
translation in Release ≤ R5.0.1 Ux. A translation is then carried out including the names and
addresses of the CPU and its twin, addressing by role, the local tunnel, SLIP management and
"trusted hosts".
The translation of the tunnel creates static LCNs. For a network where all nodes are in R6.2, the
static LCNs must be deleted.
There is no automatic translation of Chorus data of Releases below R3.0. You should not restore the
Chorus data of Releases below R3.0 but perform manually a complete netadmin.
TC0711 36 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
8.8 Saving Actis files in the image of the site

It is essential to save the site OPS files. They will be required to be able to carry out a migration to
R6.2.
8.9 Saving the lanpbx.cfg file

If the lanpbx.cfg file was used in Release 3.2, it is essential to save it before passing to Release 6.2
(usr2/downbin/lanpbx.cfg). It should be restored after the translations in usr3/mao.
If forgotten, this file should be recreated.
For more information, refer to the System documentation (Functional documentation/IP-PCX
networks/IP Phones section).
Refer to the technical communication TC0150 Configuring the OmniPCX 4400 as "boot server" for IP
Phones attached to networked OmniPCX 4400.
9. OPERATING MODE
9.1 New business account
New business accounts are not dealt with in this document, since in this case all the products
delivered and installed will be in the correct editions and compatible.
Particular attention should be paid in the case of networking.
See paragraphs 5 and 6 .
9.2 Updating R5.0 Lx, R5.1.x, R6.0.x, R6.1.x to R6.2

After updating to R6.2, you will find the same level of functionalities as initial release.
However, certain applications require a minimum version, see paragraph 6.9 .
All the elements required for passage to R6.2 are given in paragraphs 7 to 16.
REMINDER
It is mandatory to reconfigure the system by Actis even if there is no changing of license or
hardware.
9.3 OmniPCX 4400 migration to R6.2

Two possibilities are provided for migration of an OmniPCX 4400 to R6.2:
− Migration of an OmniPCX4400 to R6.2, keeping the 4400 type CPU (called Migration ISO).
− Migration of an OmniPCX4400 to R6.2, changing the 4400 type CPU for Appliance Servers
(called Migration with AS (Appliance Server)).
The migration of an OmniPCX4400 to R6.2 offers the same level of functionalities as the R5.0 Ux,
except for three restrictions:
Ed. 01 / 14 October 2005 37 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
− As of Release 5.1, certain applications, hardware or functionalities are no more supported; see
paragraph 4.1.
− The replacing of 4400 CPUs with Appliance Servers leads to restrictions on the use of certain
functionalities; see paragraph 4.2 .
− In ISO migration, the shelves already created in position 18 and 19 must be moved before the
translation. If this is not done, they will not start. In fact, when migrating from OmniPCX 4400 to
OmniPCX Enterprise R6.2 with change of CPU 4400 by an Appliance Server, there is an
automatic translation of shelves created in these 2 positions. This automatic translation does not
exist if the CPU of type 4400 are retained.
Actis 9.6 is used to migrate locks (resulting from site by photoconfig) of an OmniPCX 4400,
proposing migration packages for functionalities and hardware not supported by R6.2.
9.3.1 Use of the hardware or software key

It is always possible, except on a CPU7, to use the hardware key (dongle) or to use the software key
(cpu-Id) of the CPU. The hardware or software (cpu-Id) key allows a unique encrypted key to be
calculated.
The hardware key should be forwarded in certain cases; see Hardware Support documentation.
For 30 days, a lock file can be used even if the calculated key does not correspond to the key
present on the site (to allow the exchange of CPUs).
9.3.2 Crystal hardware compatibility with an Appliance Server

See the table in paragraph 4.2 .
Appendix 3 describes the steps necessary for transition to Release 6.2.
10. LOADING THE SOFTWARE

10.1 Generalities
Loading is now carried out using the PC Installer tool common to all CPUs (CS, AS and 4400 CPU).
See the technical communication TC0703 Installing and using the OmniPCX Enterprise PC Installer
v2.20 software.
10.1.1 Security activated by default during a installation

During the first standard installation, a list of security levels are displayed before any other
configuration is possible.
This list proposed in a menu on the first login on Call Server, makes it possible to sensitize the
Partner Business on the policy of security which he will have chosen for the system.
The absence of security on the system, which remains always possible, will be under the whole
responsibility for the customer.
TC0711 38 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
Description
On the first login after the standard installation of a Call Server, the question Do you want to
activate server security high level (Y/N) ? is displayed.
An answer (Y or N) is mandatory to quit the menu.
Answer N
The following menu appears:
Select server security level :
R) Configuration to be restored
0) Level_0 = no security feature activated
1) Level_1 = password/aging
2) Level_2 = password/aging + trusted hosts/TCP wrapper
3) Level_3 = password/aging + trusted hosts/TCP wrapper + SSH
Choice R is used to restore Linux data of the system (and thus to retain its levels of security) if this is a
migration from R5.1, R6.0 or R6.1.
Choice 0 is used to initialize the system with no default level of security as in R6.1.
Choices 1, 2, 3 are used to set the various levels of security already existing in R6.1 by mixing
between them if necessary:
• Choice 1 : Modification of passwords of root, swinst, mtcl and adfexc accounts
and enabling of the aging password function
• Choice 2 : Choice 1 + enabling of the trusted hosts and TCP wrapper
• Choice 3 : Choice 2 + enabling of the SSH service
Answer Y
The level of security 3 is automatically set.
10.1.2 Installation of a secured system for VoIP encryption ("IP Touch Security" service)
For reasons of export control of encryption technology, a patch called patch of security is provided in
addition to the generic version.
This patch of security contains only the secured binaries for IP Touch sets and the binaries of "IP
Touch Security Modules".
Installation process
The installation of security on a system in F3.301.10 must be carried in two steps:
1 Installation of system with generic version i.e.:
Installation generic version F3.301 then installation of static patch F3.301.10 with usual tools
(Standard Installation, Installation on inactive partition or Remote Download).
2 Installation of the latest patch of security in addition of the previous installation i.e.:
Installation of the patch of security SF3.301.10 containing the latest secured binaries with usual
tools (Deliveries installation or Remote Download).
Ed. 01 / 14 October 2005 39 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
Note
If installing a generic complete version and patch, for instance F3.301 + F3.301.10, the installation
of the patch of security of the complete version SF3.301 is not needed since the patch of security
SF3.301.10 of static patch has the same binaries but the latest ones.
For more information, refer to the Appendix 6.
10.1.3 Using the Remote Download
In the event of heterogeneous version, the archive to be installed must be located in

a version lower than version F3.301.
Refer to the technical communication TC0669 Compatibility of versions for remote download
feature.
10.1.4 Reading the hardware key or CPU-id of the CPUs
10.1.4.1 Label
For all types of CPU (CS, AS, CPU5/6 and CPU7), a label is visible indicating the CPU-Id number.
10.1.4.2 Command to read the CPU-Id

For all types of CPU (CS, AS, CPU5/6 and CPU7), telephone started or not, run:
login mtcl
command spadmin
option 5 Read the system CPUID
This method is to be applied in particular in the case of an Appliance Server not controlled via
Alcatel (no marking on the server).
10.1.5 Creating a blank database
A blank database should only be created for CPU installation on a new site
login swinst
password SoftInst
option 7 Database tools
option 2 Create an empty database
Enter country name example "zb" for Zimbabwe
10.2
TC0711 40 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
10.3 Restoring the database and site tickets
login swinst
password SoftInst
option 4 Backup & restore operations
option 3 Restore operations menus
option 1 Restore from cpu disk
option 3 Restore from floppy (does not exist in the case of a CS or AS
controlling common hardware)
The system automatically identifies the type of diskette (database) and requests confirmation of the
restitution.
10.4 Restoring Chorus/Linux data

CAUTION
The Chorus data of certain Releases cannot be reused automatically; refer to the section 8.7 .
login swinst
password SoftInst
option 4 Backup & restore operations
option 3 Restore operations menus
option 1 Restore from cpu disk
option 3 Restore from floppy (does not exist in the case of a CS or AS
controlling common hardware)
The system automatically identifies the type of diskette (Chorus data) and requests confirmation of
the restitution.
11. TRANSLATIONS
CAUTION
− Do not create blank database.
− As of Release 5.1, the translation is automatically run after loading the OPS files.
− There is no automatic translation from Releases below 1.5.3 to Release 6.2. For all these
versions, it is essential to go via an intermediate translation in a release compatible with
translation to R6.2 (from R1.5.3 to R6.2).
− Sites in A9.532 should first pass to A9.537.
− There is no automatic translation of Chorus data of Releases below R3.0. You should not restore
the Chorus data of Releases below R3.0 but perform manually a complete netadmin.
− There is no automatic translation from the Custom Release 3.0C (C1.580.1) to Release 6.2. It is
essential to carry out an intermediate translation with Custom Release 3.2-C2 (C1.762.18
minimum).
Ed. 01 / 14 October 2005 41 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
11.1 Installing OPS files
The procedure for installing OPS files has changed as of R5.0 Lx compared to
previous releases. It is essential that it be respected. Any other procedure for
installing OPS files is prohibited, as the system will be in a fraudulent state.
The procedure for installing OPS files puts together the following steps: RUNMAO, translation of
the database and installation of the OPS files.
Procedure
− Copy the OPS files using "ftp" in the directory /usr4/BACKUP/OPS.
− Use the menu swinst/OPS configuration.
The progress of the translations is not visible on the screen.
− At the end of the procedure, the operator is asked whether they wish to start the telephone.
Answer NO.
− Reboot the Call server.
− Check the coherence of the lock file compared to the database using the command spadmin :
• Select 1 Display current counters. The "Panic flag" should be at zero.
• Select 2 Display active file if System CPU-Id not found is displayed. This
means that the CPU_ID of the CPU used does not correspond to the CPU_ID defined in the
software.mao license file. This situation is normal if you have chosen to prepare the
migration on a laboratory CPU.
• Select 3 Check active file coherency. The test should reply File OK.
11.2 Remarks
− Check the value of the Antenna Diversity parameter; see the technical communication
TC0328 Wrong initialization of "Antenna Diversity" after translating from Release 3.0 to Release
3.1, 3.2M, 4.1, 4.1.1.
− To consult the history and the progress of the translations, a new utility exists in swinst; see the
technical communications TC0052 Installation procedure for version C1.705.8.i – Release 3.1
Appendix 4 and TC0148 Facilities 12.19: New features.
12. UPDATING THE BETA TEST SYSTEMS

All the beta test sites should evolve to released version F3.301.10.
TC0711 42 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
13. SYSTEM MANAGEMENT

Use the menu swinst/System management.
13.1 Declaring the automatic start-up of the telephone

Procedure
login swinst
password SoftInst
option 6 System management
option 2 Autostart management
option 1 Set autostart
13.2 Updating the date and time
14. CHECKING START-UP OF CPU/IO1/IO2/IO2N

CAUTION
− On a duplicated installation, if an IO2 or IO2N is declared in the database, it is essential that it
be present when starting up, otherwise the CPU will not restart. In fact, telephone signaling is
now processed by the IO2 or the IO2N when present (otherwise it is processed by the IO1
module of the CPU as in previous versions). It is however possible to start without IO2 or IO2N
using the command
RUNTEL -DNOIO2 in mtcl.
− If this first start-up is carried out on a model, put in place at least one UA or Z coupler in place of
a UA or Z coupler of the site as this will allow the correct operation of the IO1 or the IO2/IO2N
to be checked.
15. COMPULSORY MINIMUM ADDITIONAL DATABASE

MANAGEMENT
15.1 Reminder for sites migrating from Release < 3.0
15.1.1 IP addressing plan (from R3.0)

The new management of the IP interfaces in OmniPCX 4400 does not allow default declaration of
all the interfaces of all the possible network nodes. The management machines that can connect by
Ethernet on all the nodes must therefore be declared on all the nodes.
Ed. 01 / 14 October 2005 43 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
15.1.2 IP routing (from R3.0)

IP routing is validated by default on Release 3.2 installation. This function is handled by the "gated"
process and can only operate if this process is validated for all the nodes. Pay special attention to the
nodes in previous versions using the "routed" process.
These two processes are not compliant between them. In a network in Release 3.2, manage the
same routing protocol (RIP2 or RSL) on all the machines
15.1.3 ABC network (from R3.0)

Management of the number of transits.
There is a parameter used to define a number of transits for a same call across the network. This is a
protection used to avoid call looping.
Procedure :
− Access path : System
− Attribute : Number of transit PABX
− Manage the parameter with a value identical to the number of network nodes.
CAUTION: If this parameter is zero, call transit will not work.
Optimizing the DPNSS network (from R3.0)
To optimize a network, you must create a PABX address in DPNSS (Local Features) prefix. This
prefix must correspond to a directory number that has not been created in the installation.
For each machine, create a PABX address in DPNSS prefix and as many network prefixes
corresponding to the DPNSS addresses of the other machines as there are remote machines.
Example: System with four nodes.
Each node has its PABX address prefix and each will have three network prefixes corresponding to
the different PABX addresses of the three other machines.
15.1.4 ARS Time Schedule management (from R3.0)

Control ARS management to ensure that it meets client requirements.
Refer to the operation manual "ARS" section.
15.1.5 Time-outs (from R3.0)

Control the value of time-out 144 (Timeout for distributed call). It must be greater than or equal to
600.
Control the value of time-out 188 (Timer for Release of set reserved by attendant). It must be greater
than 3000; time-out used for defending sets blocked on networked music on hold.
15.1.6 Accounting (from R3.0)

Access path : Applications/Accounting
Manage all the new parameters according to client requirements.
TC0711 44 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
15.1.7 Filter table (from R3.0)

In order for the attendant not to by-pass filtering, enter the attendant individual call prefix in the filter
tables. Do not enter the attendant physical directory number.
15.2 Additional management for IO2N

For CPU5 and CPU6 equipped with IO2N board, the management of signaling channel for ACT0
only must be as follows:
− Signaling mode = IO2 instead of Nx64
− Signaling Channel N64 Size = 8 instead of 4
Access path
Shelf 0/Signaling mode: IO2
Shelf 0/Signaling Channel N64 Size: 8
For CPU7 equipped with IO2N board, the management of signaling channel for ACT0 only must be
as follows:
− Signaling mode = Ethernet instead of Nx64
Access path: Shelf 0/Signaling mode: Ethernet
This management must be followed by a reboot of the installation.
Note
The IO2N board must be at the edition 07. Refer to the technical communication TC0567 Reboot of
the CPU board after an inopportune shutdown of IO2N board.
15.3 Synchronization
The ACT 99 does not allow synchronization to be passed up to the CPU.
In the event of common hardware, one cannot use a T0 board behind a MEX to synchronize the
shelf.
For migration of an OmniPCX 4400 with change of Appliance Server, it is

compulsory to change synchronization management to IP domain type. The synchro
priority value must be between 200 and 254; see Appendix 4.
15.4 System parameters to check

Use the command compvisu to display the parameters.
15.4.1 Direct RTP

Note
In this document, "Direct RTP" corresponds to "Direct RTP in network".
Ed. 01 / 14 October 2005 45 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
By default the Direct RTP parameter is set to Yes.

In the case of connection of an OmniPCX Enterprise R6.2 opposite an OmniPCX 4400, the Direct
RTP parameter must be set to No; see Compatibility paragraph 6.4.2.
15.4.2 Frame VoIP (Enhanced quality voice)

The Frame VoIP parameter (Enhanced quality voice in previous versions) must be identical
on each node of a network.
It is better to use the Framing 20 ms for G711 or G729.
G723 can only do 30 ms.
15.4.3 Direct RTP for H323 terminals

This parameter must be set to No.
15.4.4 Inter-node protocol H323
The Inter-node protocol H323 parameter must be set to Yes and identical in all the network.
It must be set to No only if a LIOe board is used le time of migration.
15.4.5 Pre-login (V120)

As of Release 5.1, the pre-login path as changed as regards Unix versions. It is located under the
DHS3bin/servers or usr2/servers directory.
16. STARTING UP THE CPU IN ITS ENVIRONMENT ON

SITE
Do not proceed by switchover.
Proceed with a complete system start-up in order to download the new firmware of the couplers.
16.1 Downloading the couplers and sets

The first start-up of the CPU in its site environment requires particular attention since the couplers will
be downloaded with a new firmware.
− To download the INT1B couplers, they must be removed from the secondary ACTs and put in
place of the INT1A couplers of the main ACT.
− Use the downstat command to monitor the evolution of the coupler downloading. The CPU
ensures 25 downloads simultaneously. The state of a coupler during downloading is RUNNING
1.
It is possible to program an automatic reset of the couplers with the option 'r'.
− Reset manually the UA32 or eUA32 boards of shelf 0 if they do not start (do not concern
OmniPCX Enterprise with common hardware or controoled by an Appliance Server).
TC0711 46 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
− Use the downstat i command to monitor the evolution of IP Phones (e-Reflexes, IP Touch
series 8) downloading.
− Use the downstat t command to monitor the evolution of IP Touch TDM (series 9)
downloading.
17. CHECKING CORRECT OPERATION

− Check synchronization.
Ensure that the real synchronization plan corresponds to the managed synchronization plan. Use
the command infocs or clockstat.
As of Release 3.0, the notion of configuration domain is taken into account for
multi-ACTs.
− Check the distribution of calls to operators.
− Check the ARS.
− Check the coherence of the files.
login swinst
option 8 Software Identity Display
option 6 Application Software Validity Checking
Press 0 for the active version, 1 for the unactive one or q to quit
Please wait .....
Checking mode : 1=size & sum 2=size only (default is 1) 1
Checking size and sum of all files , please wait ...
file modified (authorized) : /DHS3data/manager/mtcl.adm
The application software is correct
Press return
− Check start-up of the IBSs behind INTOF.

During transition of a Release 3.2 (with CPU3) to Release 4.1 (with CPU6), the IBSs behind
INTOF do not start up if the Inter ACT Handover or DTM Synchro parameter is set to No
and there is no DECT-Sync category.
Access path: mgr/DECT Parameters/Go down hierarchy/RBS Parameters
− Check start-up of the INTIP used in particular for the remote ACT.
Faced with a board initialization problem, check that the value MTU in the IP Parameters is
correctly managed at 256.
− Check conference type management.
Ed. 01 / 14 October 2005 47 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
Coming from Release 4.1 or 4.11, it is not possible to retain two types of conference: for
example the programmed conference and the conference directed with modulo circuit 30.
The Meet me type relating to the DSP in Add On must be changed via the Modular conference
menu.
Access path: mgr/System/Shelves/Gpa Dsp program/Modular conference
− Check management of the ringing melody on digital sets.
If you migrate from a release below 4.2, you should change the ringing melodies of
internal/external calls; see the technical communication TC0297 Change of external/internal
ringing melodies in Release 4.2.
18. REFERENCE DOCUMENTS

Technical Communications:
TC0148 Facilities 12.19: New features
TC0150 Configuring the OmniPCX 4400 as "boot server" for IP Phones attached to networked
OmniPCX 4400
TC0155 Compatibility of Alcatel 4635 with OmniPCX 4400 backplanes (Reminder of restrictions)
TC0230 CPU6 Step2 board - 3BA23197 AA
TC0259 Migration procedures
TC0297 Change of external/internal ringing melodies in Release 4.2
TC0298 Migration from Alcatel 4630 voice mail to Alcatel 4635 voice mail
TC0328 Wrong initialization of "Antenna Diversity" after translating from Release 3.0 to Release 3.1,
3.2M, 4.1, 4.1.1
TC0336 Setting the T38 fax over IP application (with MP-102 version 4.0)
TC0418 Compatibilities
TC0487 Migration ACD-V1 to CCDistribution
TC0542 ARS routing when the IP domain of a Remote IP a GD is saturated – Release ≥ 5.1.1
TC0545 Problems of VPN over IP
TC0579 XML API R2.0 Technical Release
TC0582 CCD – Release 6.0
TC0594 Coupling a Bluetooth device on Alcatel IP Touch set 4068
TC0666 Alcatel 4635 - Installation procedure for version 5.2.6 - Release 5
TC0680 Risk of wrong negotiation of speed and duplex mode of Ethernet interfaces for INTIPs, GA &
GD after software upgrades
TC0682 Stop of dynamic patch delivery from Release 6.1.1
TC0698 Technical release note for VoWLAN Release 1.1.1 offer
TC0711 48 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
TC0703 Installing and using the OmniPCX Enterprise PC Installer v2.20 software
TC0705 Alcatel 4059 MAC - Installation procedure for version 4.016.2
TC0710 Technical release note for OmniPCX Enterprise Release 6.2 - Version F3.301.10
TC0712 Modem, Fax, Data transparency over IP
TC0715 REC8 board, REC1 box and external bell with binary 3.6 < uanv ≤ 4.4 do not work
TCV065 Installation procedure for version 3.2.04.00.a - Release 3.2
Ed. 01 / 14 October 2005 49 TC0711

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2
TC0711 50 Ed. 01 / 14 October 2005

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION APPENDIX 1
F3.301.10 – RELEASE 6.2 REMARKS & RESTRICTIONS
REMARKS & RESTRICTIONS
CONTENTS
1. SYSTEM........................................................................................3
2. CALL SERVER - APPLIANCE SERVER CPU ......................................6

2.1. Call Server CPU ........................................................................................ 6
2.2. Appliance Server ...................................................................................... 6
2.3. OmniPCX 4400 CPU ................................................................................. 6
3. DUPLICATION .............................................................................7
4. POWER SUPPLY............................................................................8
4.1. 1U and 3U racks with internal batteries.................................................... 8
4.2. New 1U and 3U racks with external batteries........................................... 8
4.3. New 1U and 3U racks -48V ...................................................................... 8
5. IP CRYSTAL MEDIA GATEWAY......................................................8
6. MEDIA GATEWAY ........................................................................9

6.1. GD/GA boards.......................................................................................... 9
6.2. INTIPB board .......................................................................................... 10
6.3. Number of available channels ................................................................ 10
7. VOIP..........................................................................................11
8. SETS ..........................................................................................13
8.1. IP Phone V1 – V1S................................................................................... 13
8.2. IP Phone V2 (e-Reflexe)........................................................................... 13
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
APPENDIX 1 INSTALLATION PROCEDURE FOR VERSION
REMARKS & RESTRICTIONS F3.301.10 – RELEASE 6.2
8.3. Alcatel series 8 & 9 sets .......................................................................... 13

8.4. DECT....................................................................................................... 16
8.5. UA Extender 4051/4052 ......................................................................... 16
9. IP TOUCH SECURITY FEATURE ...................................................16
10. VOWLAN RELEASE 1.1.1............................................................17
11. MISCELLANEOUS.......................................................................17
TC0711 2 Ed. 01 / 14 October 2005

OmniPCX Enterprise
1. SYSTEM
− Bios for Call Server.
As of Release 5.1, the Call Server (CS board) Bios version is higher than 8.17.
This version allows access to certain Bios functions (the main one being the Ethernet boot) which
could not be accessed from the R5.0 Lx since only R&D knew the password.
When booting the CS board:
• press Ctrl B then Ctrl I,
• the system requests a password (Warning: it is empty!) press <Enter>,
• a "light" Bios menu is displayed which allows an Ethernet boot to be carried out, the MAC
address of the board to be displayed, etc.
Bios menu
"
YOU CAN strike Ctrl B to enter in BIOS monitor during several seconds from
NOW !
hit [Ctrl I] for BIOS monitor!
Password?: (password to access the light menu)
Alize BIOS Monitor

*** BIOS Version 3EH30227DRAA bios100/008.017 ***
*** Generated on Jun/13/2003 at 09:25 ***
Monitor Light Menu
01 - Load From Hdisk #0

02 - Load From Ethernet
03 - Load From Flash NAND program
04 - Load From Flash NAND program and Bootp
05 - Load From Hdisk #0 and Bootp
06 - Display MAC address
07 - Display PCMS id
08 - Display System informations
09 - Full Options menu (Reserved for R&D)
10 - Reset System
"
− Maximum number of racks supported is 90. With the common hardware, this means for
example maximum 30 Media gateways with 2 extension racks each.
− BIOS: the command GRUBBOOT ETHER forces a network boot, but be careful, it deactivates the
hard disk ; if the boot fails, the hard disk must be re-installed.
Ed. 01 / 14 October 2005 3 TC0711

OmniPCX Enterprise
− Double-partition.
To facilitate secure software upgrade, a second version can be installed on the second partition;
use of double-partition is strongly recommended. The reboot on the second partition can be
scheduled; refer to System Documentation on how to manage the double-partitioning.
− Ethernet Duplication on CPU7.
In configuration with CPU7 only, and in order to solve certain problems of load with the C1 link
in the case of high traffic (for example in configurations with CCD), it is possible to send on IP,
the messages of telephone duplication via the process iplink as for the Common Hardware CPU
or Appliance Server.
Role management, decision of switch and detection of loss of Main CPU remain carried out by
IO1 board and not by the iplink.
C1 link
Management
Shelf 0 / Mode Signalisation + ETHERNET
Any change of signaling mode requires a reboot of Stand-By CPU then a restarting with
mastercopy.
When Ethernet duplication and IP redundancy are activated, it is necessary to manage timers of
IP redundancy in such a way that switch of CPU is done by IP redundancy before the detection of
loss of IP by iplink.
− Remote Download.
"Remote Install" can cause problems in a heterogeneous network. The archive to be installed
must be located in a version less than F2.500.
Refer to the technical communication TC0669 Compatibility of versions for remote download
feature.
− Hard disk.
• The minimum size is 6 Go for the hard disk.
TC0711 4 Ed. 01 / 14 October 2005

OmniPCX Enterprise
• Only the hard disks provided by Alcatel are compliant; manipulation of the hard disks
(exchange of the hard disks etc.) is not recommended because of the sensitivity of the hard
disks; use preferably the second partition for software upgrades.
− Tftpd contexts for GD/IP sets download: the default value is 24 allowing 24 simultaneous
downloads, but it can be increased to 99 by the management tool.
− Protection against high Ethernet traffic.
• Refer to the technical communication TC0543 Limitations of Ethernet thresholds on OmniPCX
4400/Enterprise CPUs boards.
− Negotiation of speed of Ethernet interfaces.
Refer to the technical communication TC0680 Risk of wrong negotiation of speed and duplex
mode of Ethernet interfaces for INTIPs, GA & GD after software upgrades.
− OmniPCX 4400 applications needing an IO2 are not available with the Call Server or
Appliance Server (hybrid links with signaling in B channel etc.) but always running with CPU5
Step3 128 MB and CPU6 Step2 128 MB.
− IO2N.
In the case of loss of Stand By or incidents related to the IO2N, you must have IO2N boards
Ed07 which will allow a technical investigation. Refer to the technical communication TC0567
Reboot of the CPU board after an inopportune shutdown of IO2N board.
− In ISO migration, the shelves already created in position 18 and 19 must be moved before the
translation. If this is not done, they will not start. In fact, when migrating from OmniPCX 4400 to
OmniPCX Enterprise R5.1.x, R6.0.x or R6.1.x with change of CPU 4400 by an Appliance Server,
there is an automatic translation of shelves created in these 2 positions. This automatic
translation does not exist if the CPU of type 4400 are retained.
− NAT/PAT is globally not compatible with the different elements of the system (e-CS, GD, IP-
Phones).
− Pre-login (V120).
• Since Release R5.1, the path for the pre_login is different from the previous Unix versions.
Pre_login is now located under DHS3bin/servers or usr2/servers .
Ed. 01 / 14 October 2005 5 TC0711

OmniPCX Enterprise
2. CALL SERVER - APPLIANCE SERVER CPU
2.1. Call Server CPU

− Direct connectivity of the Ethernet port of the CS to a port of a switch is mandatory.
− Only auto-negotiation mode is supported on the CS board => to be able to operate in Full-
duplex, the port of the switch used for the connection must be configured in auto-
negotiation. Otherwise, if the port of the switch is forced to full-duplex, the CS will be unable to
detect the full-duplex capability of the switch port and will operate in half-duplex. Rule: the port
of the switch must be in auto-negotiation or forced to half-duplex.
− Protection against high broadcast traffic: available on CPU-CS (an incident is emitted) but it is
not manageable.
2.2. Appliance Server

− Only Alcatel recommended Appliance Servers (X305 and X306 of IBM) are to be used.
• X305:
♦ Alcatel reference: 3BA 00438 AA
♦ IBM reference (in case of external purchase): Model Type : 8673-62X
• X306:
♦ Alcatel reference: 3BA 27582 AB
The installation of X306 can be carried out only as of PC Installer v2.17.
CAUTION
AS X306 must only be ordered by Alcatel.
− In case of an appliance server, a UPS is mandatory to secure the system against abnormal
stops because of power failure (risk to crash the hard disk).
2.3. OmniPCX 4400 CPU

− Only the CPU5 Step3 128 MB, CPU6 Step2 128 MB and CPU7 256 MB can be used in
Releases 6.0.x, 6.1.x and R6.2.
− CPU5 Step3 functions at 10 Mbits Half Duplex.
− CPU6 Step2 functions at 100 Mbits Full Duplex.
− You can manage the mode and the rate CPU7 boards. The setting of CPU7 board and of the
port of the switch on which the CPU7 board is connected, must be the same.
− The use of hard key is always available on CPU5 and CPU6 but not on CPU7.
− The CPU7 board does not support the OBCA daughter board.
− The CPU7 board the IO2 board. Only the IO2N boards are authorized.
− The CPU7 board is not allowed in a VH cabinet.
TC0711 6 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3. DUPLICATION
− In case of CS , the Main and Standby Call Server must not be located in the same rack.
− Do not use SLANX4 but an external switch (LANX16-1 or customer switch) in order to be able to
unplug a Call Server without disturbing other elements.
− The Main and Stand-by CS or Appliance Server can be located in different sub-networks
(feature under PCS).
• Features available on AS and CS:
♦ This feature is supported by following IP equipment:
SIP sets
Alcatel series 8 sets (4028-4038-4068)
GD
GA
INTIP
IOIP
"IP Touch Security Module" : SSM, MSM
Attendant IP Softphone
♦ The applications able to take into account 2 addresses of CPU are:
Alcatel 4635 (R5.2.6)
Alcatel 4645
OmniVista 4760i / 4760 (R3.2)
OmniTouch Contact Center : CCD/CCS/CCA/CCIVR
XML Web services
Application "XML IP Touch"
TSAPI
ACAPI
VoWLAN R1.x
• Features not available on AS and CS:
♦ V1 (4080 RE) - V1S (4080 FRE) - V2 (e-Reflexe IP Phone V2) sets. Only the IP sets of series
8 and SIP sets are able to take into account 2 addresses of CPU.
♦ Genesys applications (CCEmail, CCOutbound, CCWeb)
♦ RSI Synchro Server
♦ TAPI
♦ No OmniTouch Unified Communication
− If a R6.1.1 node is added in a network with nodes less than R6.0, it is essential to continue to use
the addressing by role in case of logical links over IP (the nodes below R6.0 cannot establish
logical links towards two different addresses).
− If an external DHCP server is used, a tftp server must also be used.
Ed. 01 / 14 October 2005 7 TC0711

OmniPCX Enterprise
− Bandwidth required between the 2 CS :
Number of users Minimal bandwidth (Kbps)

500 512
1000 512
2500 1280
5000 2560
− Audit and broadcast must be performed via IP/X25 and not directly via IP.
− In case of a V24-IP Moxa box, the time to recover the connection with the system after a Call
Server switch-over is about 10 to 20 seconds.
4. POWER SUPPLY
− The power consumption is not monitored by the Call Server => the limits supported by the
different racks must be respected; see the "Product Limits" document and the "Express Mapping
Tool" document available on the BPWS section Our Offer > Products > Alcatel OmniPCX
Enterprise > select In Depth Product Insight > English Language > OK > Release 6.2; this last
document describes the power consumption of the different equipments (powered IBS Base
stations, UA sets, etc.).
4.1. 1U and 3U racks with internal batteries

− This type of rack can no longer be ordered on new business from Release 5.1.2 and Actis 8.1.1.
4.2. New 1U and 3U racks with external batteries

• These new racks with external batteries are compliant only from R5.1.2.
• The external battery rack 12V can be connected only on a 1U rack (3EH 76020 AE).
• The external battery rack 36V can be connected only on a 3U rack (3EH 76027 AE or BE).
4.3. New 1U and 3U racks -48V

− These new racks with external batteries are available from Release 5.1.2 and Actis 8.1.1.
5. IP CRYSTAL MEDIA GATEWAY

In the document the name "INTIPA or B" concerns the INTIP board as well as the INTIP2 board.
− Only one Voice Hub or M1 or M2 cabinet is supported for the IP Crystal Media Gateway in the
main zone.
− The GPA2 is supported in the IP Crystal Media Gateway.
− In peripheral zone all 4400 boards are supported.
TC0711 8 Ed. 01 / 14 October 2005

OmniPCX Enterprise
− INTIP board cannot be used with embedded Ethernet (a CBC1 10/100 connector must be used).
− INTIPA board can be used with 100 Mbits. With a VH cabinet you have to use the Patch Panel
10/100Mbits Reference 3BA 23244 AAAA 01.
− 100 Mbits compliance with WM1 and VH cabinets for CPU6 Step2 and CPU7.
The CPU7 board is not allowed in a VH cabinet.
All cabinets are or will be compatible with 10/100BaseT. The VH and WM1 cabinets compatible
10/100BaseT will be available soon with the following 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 AC
WM1 Battery package (battery autonomy 1.2 Ah)- USA 3BA 57106 UB
Note
If the referenced cabinets above are not used, the CPU6 Step2 and CPU7 boards will work at 10
Mbits maximum.
6. MEDIA GATEWAY
6.1. GD/GA boards

− Direct connectivity of the Ethernet port of these boards to a port of a switch is mandatory.
− By default, dynamic IP addressing is active (DHCP) on a GD board.
− The GA board doesn’t support DHCP feature.
− If the GD supports H323 links, a static IP address must be assigned to the GD.
− Now the maximum duration for the GD software downloading is manageable from eMG
binaries:
Ed. 01 / 14 October 2005 9 TC0711

OmniPCX Enterprise
• 16.34 (E2.504.1.r)
• 22.7 (F1.603.1.h)
• 30.9 (F2.500.6.e)
• 40.5.1 (F3.301.9)
By default, the timeout is 20 min. AT the end of this timeout, the GD restarts with its previous
software.
6.2. INTIPB board

In the document the name "INTIPA or B" concerns the INTIP board as well the INTIP2 board
− Direct connectivity of the Ethernet port of the INTIPB board to a port of a switch is mandatory.
− The INTIPB board supports 10/100Mb/s and Half/Full Duplex mode.
− The mode Full-Duplex or Half-Duplex (default mode) of the INTIPB must be configured via the
V24 (auto-negotiation mode is not supported by INTIPB) =>
• If the switch is in auto-negotiation, the switch will operate in the mode configured in the
INTIPB.
• If the switch is configured in Full-Duplex, the INTIPB must be configured in Full-Duplex too.
• If the switch is configured in Half-Duplex, the INTIPB must be configured in Half-Duplex too.
− To configure the INTIPB in static IP addressing mode or Half/Full, you must use the cable 3BA
28112 for INTIP board and the cable 3EH 75003 AAAA for the INTIP2 board.
− The INTIPB board must not be used for H323 links or IP Phones handling.
6.3. Number of available channels
G711 G723.1 G729

With or w/out VAD With or w/out VAD With or w/out VAD
INTIP with 2 32 ms echo GIP6A 14 14 14
daughter cancellation GIP6 56 56 56
boards 64 ms echo GIP4-1 16 16 16
(1 & 2) cancellation GIP4-4 60 60 60
GD or GA 32 ms echo MCV8 8 7 7
cancellation MCV24 24 21 21
64 ms echo MADA-1 8 8 8
cancellation MADA-3 24 24 24
(1) It is not authorized to have two daughter boards of different types on a same INTIP board.
(2) The echo delay is not configurable, it depends on the hardware used.
TC0711 10 Ed. 01 / 14 October 2005

OmniPCX Enterprise
7. VoIP
− IP Domains.
The number of IP domains changes from 128 to 1000.
− Nodes of an IP homogeneous network.
The number of nodes of a backbone IP network changes from 32 to 100.
In a homogeneous IP network, each node of the network can have several adjacent nodes (for a
maximum of 31 adjacent nodes).
− ABC Signaling Link.
It is not necessary to completely mesh the network.
− VPN Jump.
It is advised to completely mesh the network.
− The echo delay can no more be managed. It is set automatically according to the hardware
used:
• GIP6-GIP6A-MCV8-MCV24 board: the echo delay is limited to 32 ms.
• GIP4-1/GIP4-4/MADA-1/MADA-3 board: the echo delay is limited to 64 ms.
− LIOE.
The H323 protocol over LIOe is no longer supported from Release 6.0 since LIOe and TSC-LIOe
boards are no longer supported. When migrating to Release 6.0.x, 6.1.x or 6.2, the LIOe boards
must be replaced by INTIP2 boards. They also must be replaced in case of an heterogeneous
network.
In a network with R6.0.x, R6.1.x or R6.2 nodes, there must not be LIOe and TSC-LIOe boards.
− Direct RTP switching in network:
It is used with IP devices (IP Phones, Alcatel 4980 IP Telephony, GD, GA, 4645 voice mail,
INTIP); it allows to establish a direct RTP communication between the 2 IP-devices over the
network in order to optimize the number of compressions/decompressions.
• The DPNSS prefix for path replacement must be systematically managed.
• The configuration must be homogeneous in the whole network; reboot of the system is
mandatory after activation of this feature.
• Direct RTP switching in network is available with INTIP/GD/GA boards but not with H323
terminals or H323 Gateway.
• RTP flow redirection being not supported by H323 terminals /H323 Gateways, standard
switching will take place with these equipments => one compressor will be allocated by the
system.
• Fast start must be activated with LIOe boards.
− Multi-node transit without compression/decompression like in OmniPCX 4400: this optimization
is not implemented in OmniPCX Enterprise; in place, direct RTP switching in network is provided.
Ed. 01 / 14 October 2005 11 TC0711

OmniPCX Enterprise
− It is not possible to create several IP trunk groups for a GD/GA/INTIP board => use the VPN
Call Limitation feature to limit the number of calls per direction.
− For a GD/GA/INTIP, the number of trunks in a trunk group must not be managed. You must
retain the default configuration (30 trunks created). The limitation of compressors will be carried
out by managing the VPN TS % in the trunk group or by the "VPN Call Limitation" feature.
− From R5.0 Lx, QoS profile control on ABC-F VoIP links is no longer available (with/out direct RTP
switching in network).
− The VoIPstat command is no longer usable.
− Mix of communication with Fax and Voice in a same room: during the voice communication, the
DSP might change to Fax mode; the only workaround is to reduce the volume of the Fax.
− In case of ABC-F VoIP links, the boolean H323 signaling for inter-node links must
be consistent over the whole network.
− When creating or modifying the IP trunk group on a GD, the Media Gateway will reset
in order to take into account the changes.
− UDP port range: UDP base port manageable by a system parameter and taken into account by
all IP equipments (Call Server, INTIP, GD, GA, IP Phone, etc.) except Fast IP Enabler.
CAUTION
This parameter is common for all the installation and is managed only under
IP/IP Phones Parameters/UDP Port
− QoS Tickets (under PCS).
• QoS tickets are provided by GD/GA/INTIP boards, IP Phone V2, IP Touch, My Phone and
4645 voice mail.
− Fax over IP.
• The rate is limited to 9600 b/s in Fax Relay mode with common hardware and Crystal
Hardware.
• Fax T38 interworking with OmniAccess 512 (VSA Interface) is not available.
• Fax V34 is supported.
− Audiocodes MP-102.
• Interworking with MP-102 boxes is supported but only for fax transmissions (analog sets
are not supported); refer to the technical communication TC0336 Setting the T38 fax over IP
application (with MP-102 version 4.0).
• No accounting for fax calls.
− IP Services / Port numbers.
• The port numbers used are listed in the System Documentation.
CAUTION
The System documentation is also applicable for Releases 5.0 Lx and higher.
• For VoIP flows, the range of UDP ports used can be customized in the range 0 to 65535;
supported by all IP equipment like GD, GA, e-Reflexes range (IP-Phone V2) etc. except Fast
IP Enabler (TSC-IP V1S).
TC0711 12 Ed. 01 / 14 October 2005

OmniPCX Enterprise
− G729 40 ms.
CAUTION
The lengthening of the sending framing over IP involves two consequences on the voice:
1 an increase of the time from beginning to end,
2 any loss of package means that larger quantity of information is lost, involving a faster
degradation of the voice.
8. SETS
8.1. IP Phone V1 – V1S

The IP Phone V1 (4098 RE) and V1S (4098 FRE) sets are no more supported from Release 6.0 : it
can be connected on Release 6.0.x, 6.1.x or 6.2, but no correction of binary will be carried out.
The IP Phone V1 set does not work in Direct RTP (Releases 5.1, 6.0.x, 6.1.x and 6.2).
8.2. IP Phone V2 (e-Reflexe)

− The VoIP Technical Characteristics of the IP-Phones are available on the BPWS in the section
Support > Technical Support > Technical Communication > VoIP Engineering.
− Multicast traffic supported before voice degradation, IP Phone reset: 90 Mb/s.
− The initialization duration without binary downloading is about 9 minutes for 2000 IP Phones.
CAUTION
The old 20 and 40 add-on modules are not compliant with the integrated IP Phones V2, the add-
on keys are ignored. These old add-on modules function correctly with TSCIP V1 and V1S sets.
New modules are available and function with TSCIP V1, V1S and IP Phone V2.
These modules are available with the references:
• Add-on 40 keys :
♦ Reflexes module add-on 40 packaged : 3AK 27107 ADAB
♦ Reflexes module add-on 40 : 3AK 26044 ABAA
• Add-on 20 keys :
♦ Reflexes module add-on 20 packaged : 3AK 27107 DDAB
♦ Reflexes module add-on 20 : 3AK 26043 ABAA
These new modules are marked "Add-on UA/IP" on the packaging and on the label pasted under
the module.
8.3. Alcatel series 8 & 9 sets

− The Alcatel series 8 & 9 sets cannot be used as:
• attendant sets
• attendant assistant
• CCD agents
These restrictions will be removed in next versions.
Ed. 01 / 14 October 2005 13 TC0711

OmniPCX Enterprise
− Alcatel series 8 & 9 sets can be used as hotel or hospital sets from Release 6.2.
− The IP configuration on IP Touch series 8 sets can be locked by a password (common for the
installation).
− The series 9 sets cannot access to XML applications.
− In Release 6.2, there is a direct access (no more transit via Call Server) between IP Touch 8series
and the PRS 1.2 (XML Web Services 2.2) for the visualization of images on the sets.
− Only the 4028-4038-4068 sets can access to XML applications.
− The 4018-4028 set cannot access to OmniTouch UC R3.0 (My Phone, My Messaging, My
Assistant).
− No total substitution but only partial.
− No hands-free on 4019 set.
− 4018 & 4019 sets do not support Electronic Add-on modules.
− 4018 & 4019 sets cannot use the call by name feature.
− No add-on module behind series 8 & 9 sets: V24/S0/Z MAC/PC.
− No series 9 set behind a RT2 or LIO board.
− No series 9 set in remote UA (LUTA-RUTA).
− The recording of calls on TDM sets as well as the access to the external ringing are possible with
the series 9 sets only with the following board references:
• REC8 : 3BD 19218 AHAA
• REC1 box : 3BD 19160 AEAA
• External Bell : 3BD 11086 ACAA
These boards remain compatible with the UA sets of Reflexe range.
Refer to the technical communication TC0715 REC8 board, REC1 box and external bell with
binary 3.6 < uanv ≤ 4.4 do not work.
− The Survivability feature is only supported by the IP Touch series 8 sets. The eReflexes sets are not
compatible.
− From Release 6.1, 74 programmable keys are available (72 via the Perso tab of the set and 2
via F1 and F2 keys).
REMINDER
In Release 6.0:
• 40 programmable keys are available,
• the key 43 which was located on the Add-on module will correspond to the key 75 of the
Add-on module in Release 6.1.x or 6.2.
When migrating from R6.0 to R6.2, the networked IP Touch 4038 and 4068 Executive/Secretary
sets must be managed again. The list of IP Touch Executive/Secretary sets to be managed is
supplied automatically in the result of the translation. You can also get it with swinst ; see
below.
TC0711 14 Ed. 01 / 14 October 2005

OmniPCX Enterprise
login swinst
password SoftInst
option 7 Database tools
option 5 About last database operation
“ Altering table KEYBOARD

Copying table files, droping old table, creating new table, done
Preparing to read/insert rows, done
Reading/Inserting rows,
No Translate BOSS/SECRETARY Network DO MANUALLY : Set 64127 Key 047 Sub 64036
No Translate BOSS/SECRETARY Network DO MANUALLY : Set 67889 Key 041 Sub 67881
Table KEYBOARD altered “
− Certain prefixes cannot be used since they available through keys available in the menu page of
the set: language, programming the contrast, no ring.
− It is recommended to use add-on modules when supervising Boss/Secretary and MLA.
− There is no Help key on external applications.
− Each set of he series 8 support the "Statistic tickets over IP" feature as of Release 6.2.
− The migration of a Z set towards an IP Touch set is carried out in two steps:
• Migration of Z set towards an UA or IP set.
• Migration of UA or IP set towards an IP Touch set.
− If using Alcatel IP Touch 4068 set with Bluetooth in a WLAN environment, interferences can be
generated which can degrade the quality of transmission, in particular the audio of these
equipments. Alcatel recommends not to use these two technologies simultaneously.
− You can connect up to 3 Electronic Add-On modules. These modules cannot be mixed with the
other types of Add-on modules.
From Release 6.1, the available configurations are:
• one Add-on module 10 keys
• one Add-on module 40 keys
• one Add-on module 40 keys + one Add-on module 10 keys
• one Electronic Add-On modules
• two Electronic Add-On modules
• three Electronic Add-On modules
− Downloading the series 9 sets.
The loading of a dynamic patch with new binaries regarding the series 9 sets, are initialized
automatically following the type of downloading selected. This can eventually cause an
inconvenience for the client if the installation of the dynamic patch is carried out in the daytime;
you should:
• set the field Download policy (Phone Facilities categories) to Delayed
• install the patch.
Ed. 01 / 14 October 2005 15 TC0711

OmniPCX Enterprise
8.4. DECT
− In the case of common hardware, DECT can be installed on different Media Gateways, but these
Media Gateways must be necessarily located on different sites due to the interferences this
would generate, the Media Gateways being not synchronized from a DECT point of view. You
should not have overlapping between base stations.
− Only frequency number 1, 2, 4, 8 are available for PWT (5 does not work); same as for
OmniPCX 4400.
− The DECT Campus feature is not supported with Call Server or Appliance Server driving common
hardware or Crystal Media Gateway.
− No cohabitation of DECT2 and DECT4 with DECT8.
− 5 digit DECT dialing.
This feature is only allowed for Mobile 100&200 Reflexes, Ascom DECT, 4074 HB in UA2 mode,
GAP sets, TSC DECT, 4073 (PWT).
8.5. UA Extender 4051/4052

The use of UA Extender 4051/4052 is not available through IP.
9. IP TOUCH SECURITY FEATURE

This feature works only in Stand-Alone configuration.
The IP Touch Security feature works with a secured patch, delivered in complement of the generic
version.
To get this secured patch, a request must be made on Alcatel Business Partner Website.
This secured patch has the same name as the generic delivery to which it is referred preceded by the
letter S (for Security).
This secured patch contains only:
• Secured binaries for IP Touch series 8
• Binaries for IP Touch Security Module.
The installation of this secured patch is carried out in a second step after installation of the
generic version and patch.
In multi-SSM duplicated configuration:
• The 4645 must be on a dedicated CPU protected by a MSM
• The encryption of the OmniTouch UC server cannot be done by one of the two SSM but by
the use of a MSM
In multi-SSM spatial redundancy configuration (SSM in blocking mode), it is necessary to define a
specific link between IP physical address of each Call Server and main IP address of the other Call
Server.
TC0711 16 Ed. 01 / 14 October 2005

OmniPCX Enterprise
In multi-SSM traditional duplication configuration (only one main address):

• During module initialization if the Main address was defined on the plain and cipher port, in
established mode the module consider the Main address on its plain port (in normal state, IP
element cannot be at the same time on the plain port and cipher port)
• In a result of the preceding point, the modules must remain in passing mode
Before moving a set of a secured system towards an unsecured system (moved within a ABC network
or changed on another system), unsecured manually the set and remove it from IP network before it
recover again the lanpbx.cfg protected file
After each change of mode (secured / unsecured), Call Server must be restarted.
It is not possible to manage VLAN in "IP Touch Security Modules". As a result, if the "IP Touch
Security" feature is implemented, you are not allowed to manage VLAN on a Call Server protected by
SSM. The management of VLAN must be carried out the level of DATA infrastructure (switch).
10. VoWLAN RELEASE 1.1.1

VoWLAN 1.1.1 offer is released from OmniPCX Enterprise Release 6.1.1.
For any VoWLAN request out of VoWLAN Release 1.1.1 characteristics and limits (other WLAN
infrastructures or exceeding VoWLAN 1.1.1 limits), you must follow the PCS process.
For more information, refer to the technical communication TC0698 Technical release note for
VoWLAN Release 1.1.1 offer.
11. MISCELLANEOUS
− The number of entities for a node or in a network changes from 255 to 1000.
If a network is composed of several nodes with a number of entities higher than 255, each node
of the network must be in Release 6.2.
− MIX board.
This board is not supported in a Rack 3U in central area.
− LIOB/LIOP/LIOX boards.
These boards are in phase out from Release 6.1. They are supported by Release 6.2 but can no
more be configured for addition or for new installation.
− INT1/INT2 boards.
These boards are no more supported from Release 6.1.1. They must be replaced by
INTOF/INTOF2 boards. On a migration, Actis will remove the INT1 or INT2 boards and will
propose a preferential rate on INTOF2 boards.
− INTOF2 board.
The mixing of various generation boards is allowed in a same rack but:
• the couplers in relation to the link must be of the same type
Ed. 01 / 14 October 2005 17 TC0711

OmniPCX Enterprise
• the type of INTOF must be of the same type if the link is doubled or tripled
• the INTOFS and INTOF2S are not compatible between them. If changing from INTOFS to
INTOF2S, you should also change the INTOFS which is faced to this board. No consistency
check is possible with the management because each board is part of a different node.
Nevertheless an anomaly will be sent by the INTOFS2 if the remote coupler is not the same.
− Z sets ringing.
• Maximum number of simultaneous ringing sets in a Rack 1U: 6.
• Maximum number of simultaneous ringing sets Rack 3U: 20.
− In the event where you should use a T1 access and an E1 access on the same system,
the two boards must be on different Media Gateway.
− External LDAP Server.
• LDAP overflow is only available on Alcatel series 8 & 9 sets and Reflexe/e-Reflexe sets with
softkeys.
• LDAP overflow only displays data from LDAP entries "telephone number" and "mobile"; it
displays the "telephone number" entries if they are available; if not, it displays the "mobile"
entries if they are available.
• LDAP overflow is not automatic if local answers are available in the phone book => must be
activated manually by a software key.
− T0 interface on Media Gateway.
• T0 "network mode" is only supported with the BRA board. Refer to the technical
communication TC0495 Using the network mode on T0 accesses of BRA boards on Media
Gateway.
− Number of mini-messages.
• Maximum number of mini-messages is limited to 1000.
− Number of T0.
• Maximum number of T0 is limited to 254.
− S0 interface on Media Gateway.
• Native S0 is not supported on the BRA board => only connection through S0 plugware
is provided.
− 4645 voice mail embedded on Call Server or Appliance Server.
• The number of simultaneous accesses is limited to 16 for a 4645 on a dedicated Call
Server (CS) or embedded on an Appliance Server (AS).
• The voice quality might be impacted by the double compression/decompression on the
network when using a poor IP domain (with G723/G729 codec) between the node of the
voice mail and an other node of the network; even if the 4645 operates in G711, the 4645
will record a G723/G729 compressed/decompressed speech; and again at the restitution,
one G723/G729 compression/decompression will take place.
• The attendant set has not access to the voice mail for consultation of the messages of a voice
mailbox.
• Rerouting of Fax is not supported.
TC0711 18 Ed. 01 / 14 October 2005

OmniPCX Enterprise
− LANX16-1 / SLANX4 / LANX16-2 / LANX8-2.

• These LAN switch boards are not manageable.
− Voice Guides.
• GD/GA boards supports maximum 4 languages for voice guides (including music on hold).
• The USA voice guides are the default A4645voice guides.
− DSP resources per GPA.
• The maximum number of DSP resources per GPA-GD is fixed as following (not
extensible):
♦ DTMF Generation: 16.
♦ R2 detection + DTMF Q23/Q23X Detection + Tone (single and dual) Detection:
payload of 5 % for R2:
maximum 20 detections for R2 when no Tone Detection,
payload of 4 % for Q23/Q23X:
maximum 25 Q23/Q23X detections when no Tone Detection,
payload of 3 % for Tone Detection:
maximum 30 Tone Detections when no Q23/Q23X detection.
♦ Voice Guides Play: 16.
♦ Addition (3-Party conferencing, discrete listening, etc.): 3.
• The maximum number of DSP resources per GPA-MEX is fixed as following (not
extensible):
♦ DTMF Generation: 16.
♦ R2 Detection + DTMF Q23/Q23X Detection + Tone (single and dual) Detection:
payload of 7 % for R2:
maximum 14 detections for R2 when no Tone Detection,
payload of 6 % for Q23/Q23X:
maximum 16 Q23/Q23X detections when no Tone Detection,
payload of 4 % for Tone Detection:
maximum 25 Tone Detections when no Q23/Q23X detection.
• The maximum number of DSP resources per GPA-GA is fixed as following (not
extensible):
♦ Voice Guides Play: 16.
• Mutual aid between Media Gateways regarding DSP resources is not provided (excepted for
Voice Guide Play).
− Call Center and CSTA.
• SOSM (Russia) is only available with 4400 hardware.
• EAU (United Arabian Emirates) is available.
Ed. 01 / 14 October 2005 19 TC0711

OmniPCX Enterprise
− A-Law/µ-Law.
• The A-Law / µ–Law configuration is valid for the whole system.
− PSTN synchronization.
• In case of common hardware, the PSTN access must be in the main rack (not in extension
racks).
• In case of common hardware or IP crystal Media Gateway, the synchronization is local to the
Media-Gateway => synchronization by domain must be configured (Synchro Number 200
to 254).
• ACT 99 can't be synchronizing.
− RMA.
• No hardware remote reset of the e-CS in case of an Appliance Server.
− eRMA.
• No hardware remote reset of the e-CS.
• The connection is lost in case of Call Server switch-over.
• The connection won’t work if the Call Server Application is not running.
• Only one simultaneous connection is possible.
• eRMA connection works only in case of switching network connection on the GD (does
not in case of access work through an ABC-F link).
− Back-up signaling.
• The time to recover the telephonic functions in case of back-up link activation is about 3 to 6
minutes depending on the Media Gateway configuration and the type of signaling link used
for the back-up.
• The number of digits expected when receiving the back-up call must be managed; see the
Technical Documentation.
• The boards used for the establishment of the back-up link must be in the main rack.
• In case of Crystal Server (with CPU5 Step3 or CPU6 Step2), it is mandatory to have a Media
Gateway near the main zone to have the backup feature.
• In case an APA link is used for back-up signaling, this APA link will be dedicated for the back-
up signaling.
• DASS2 or DPNSS links are not supported as back-up links.
• No IP/Phone in dynamic address
• No 4049 nor 4059 attendant station behind a Media Gateway with potential back-up
link.
• Connection of Hybrid link/H323 links behind a Media Gateway with potential back-
up link is possible.
• The following features are not accessible/provided when the back-up link is active:
♦ Feed-back tone to the sets when dialing (except for IP-Phone V2).
♦ Access to voice mail 4635H or 4645.
♦ Call Center.
♦ 4980 PC MM won’t work because the OTS server will not be accessible.
TC0711 20 Ed. 01 / 14 October 2005

OmniPCX Enterprise
♦ Only local calls between the sets attached to the Media Gateway (including the IP-Phones
attached to the Media Gateway) or external calls through the local PSTN connections are
possible.
− SIP (Session Initiation Protocol).
• Direct RTP Switching in network is mandatory when SIP phones are configured.
• A SIP set can be managed in an IP domain from Release 6.1 and Release 6.0.1 (version
F1.603.1.h).
Currently the CAC (Call Admission Control) does not concern SIP towards SIP calls.
• SIP-Phones are supported in:
♦ stand-alone,
♦ in network configurations.
• Support of Pingtel phones (see the feature list for the features available).
− 4760.
• If OmniVista 4760 is connected through a customer IP network with a Firewall, the port
number 113 (AUTH) has not to be filtered in the Firewall. Otherwise as the client don't answer
on this port number, the connection will be done too late and the ftp part of OmniVista 4760
doesn't work.
• ppp connection w/o RMA does not operate with each current Linux versions. The connection
is active but telnet, config, synchro fail.
• Blind attendant can't reach the 4760 directory through Internet Explorer although it was
possible with the A4755.
− 4760i.
− Remote Extension.
• Doesn't work with NDDI, APA, DASS2 and DPNSS.
• In VoIP network with the algorithm G723/G729, the public access has to be in the same
node that the remote extension otherwise there will be DTMF detection problem. It works
correctly with the G711 algorithm.
• H323 terminals (e.g. Netmeeting PC) are not supported. Only IP Touch terminals 300 and
600 for the VoWLAN offer will be authorized.
− ppp.
− CLIP on Z32.
• Calling Line Identification Presentation (CLIP) is only available with analog Z32/eZ32 board
with a Crystal (IP) Media Gateway.
• The protocol ETSI (ETSI 300569 -1/2) and Bellcore (Bellcore TRNWT000030) are supported.
• The CLIP information is presented on an incoming call to an analog terminal that is on-hook
and is receiving ringing.
Ed. 01 / 14 October 2005 21 TC0711

OmniPCX Enterprise
• The feature is released only for 5 countries (USA, China, Taiwan, Pakistan and Hong-Kong).
• A CLIP terminal cannot receive an incoming call during the first 9.5 seconds after it has gone
on-hook.
• CLIP is not available for analog phones associated with the 4980 My Softphone application.
• Some telephones only displayed the calling number and not the calling name.
• The following sets have been validated for the US market: AT&T 9357, Uniden EXAI3781,
Sony IT-ID20, GE ATLINKS 29196GE1-A, Panasonic KX-TC1703, Bell South 900Mhz
MH9942BK
• Alcatel can't test and maintain a list of compatible telephone because there are thousands of
different phones. Business Partner should contact Professional Services to undertake the
validation of specific telephones on a case-by-case basis. Telephone vendors should contact
the Alcatel Business Partner Program to carry out such validation of their product.
− CLIP Bellcore on APA.
• CLIP on APA line (CLIDSP daughter board - 3EH 73034 AB) is available for all markets from
Release 6.1.
− CLIP Bellcore on NDDI2.
CLIP on NDDI2 is available for all markets from Release 6.1.
− CLIP DTMF on APA.
In R6.2 the CLIP DTMF on APA line (CLIDSP daughter board - 3EH 73034 AB) is available for
India and Taiwan.
− In R6.2 NDDI2 board is available for Australia.
− SSH/SSL.
Each node of network must be in Release 6.0.x, 6.1.x or R6.2.
− Modem Multitech MT5600BA V92.
This modem must be connected to an UPS otherwise it can be blocked in case of power supply
failure.
− Call completion on busy trunk group.
• Feature not available on S0 and attendant sets.
• Operates only in overlap mode.
• Does not operate in network.
• Operates with ARS if the trunk group is local.
• Does not operate on shared trunk group.
− Private to public overflow.
• From Release 6.1.1, private to public overflow is subject to the same checks (through Phone
Facilities category) as private to public overflow in network.
• The sets of an inaccessible domain must be accessible in DDI.
• It is required to have at least one public access for each domain.
• All the phone services are lost when changing from a local call towards a public call.
TC0711 22 Ed. 01 / 14 October 2005

OmniPCX Enterprise
− MOXA Box.
The MOXA box is used to increase the number of serial ports of OmnipCX Enterprise. The aim of
this Release 6.1 feature is to make easier the configuration of serial ports of the box: single
management of information in mgr instead of two distinct programs (mgr and npadm).
The firmware version of Moxa box must be 3.0 or higher.
− Multiple Redial list.

• No multiple Redial list with 4035 attendants.
• No save of the name of a local or networked call (homogeneous) in the following cases:
♦ Prefix of entity call.
♦ Attendant call.
♦ Call of an abbreviated number.
• Only available on sets:
♦ MR2 3G (4035, 4036, 4037).
♦ 3G (4020, 4021, 4022).
♦ IP Touch B, C, D.
• No update of the list of calls sent by the Stand-By.
• On each RUNTEL or reset of set, the list of sent calls is initialized.
• No save on the disk.
− Installation of ACT shelves in computer cabinets.
OmniPCX Enterprise ACT shelves must be installed in computer cabinets closed and equipped
with fans.
They must comply with the same CEM and safety standards as the OmniPCX Enterprise ACT
shelves:
• EMC: EN55022 :1998-EN55024: 1998/FCC part15
• Safety EN60950 :2000/IEC 60950 ed03/CSA/UL certification
The authorized configurations in the computer cabinets with 38U and 42U format are:
2 ACT shelves 28 positions or 4 ACT shelves 14 positions.
− Error in checkdb.
During checkdb, if the following message is displayed:
/...............
ERROR 4351 : DATA INCONSISTENCY, Table ENTITY, entity=1 invalid cdt
................/
SUBSDATE File checking in progress ...
66532 Inexistant in Database
67498 Exist in Database
...
64572 Inexistant in Database
SUBSDATE : Nb Instances 4129 Nb Errors 2693
Ed. 01 / 14 October 2005 23 TC0711

OmniPCX Enterprise
SUBSDATE File, used to memorize the date of the modifications of the users by OmniVista 4760,
when the events notification is activated, is incoherent. However the data base is coherent.
To repair this file, use the option [ 3] - Real mode:Correct the Inconsistency of
the checkSUBSDATE tool.
Note
MAO must be Off.
TC0711 24 Ed. 01 / 14 October 2005

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION F3.301.10 APPENDIX 2
RELEASE 6.2 COMPARING THE R5.0 Ux AND R6.2 LICENSES
COMPARING THE R5.0 Ux AND R6.2 LICENSES
The comparison hereafter has been carried out between Releases 5.0 Ux and 6.2 licenses.
REMINDER
The moveable licenses are preceded by the letter M (Move) and yellowed (example : software locks 2, 76, 90, etc.).
R5.0 Ux R6.2
Licenses Possible values Licenses Possible values
1-GroupTelephony 0/5/10/30/…/9999 1-Group Telephony "open" /9999
2-CallByName 0/5/10/30/…/9999 2-M-Phonebook users 0/10/20/…./9990 ( step of 10 )
3-ACD P1: 0/1 P2: 0/10/30/9999 3-Not used
4-HotelBasic 0/50/100/300/9999 4-Hotel guest sets 0/50/80/150/350/500/9999 (>= lock 013 if <>0)
5-HotelLanguage 0/1 5-Multilanguage voice 0/1
6-HotelLink 0/1 6-Hotel : AHL on V24 0/1 ( =lock 126 AHL on IP )
7-Networking Not used (see new software lock 19) 7-Not used
8-Accounting Not used (see new software lock 50) 8-Not used
9-PRA 0/20/9999 9-PSTN B channel "open" /9999
10-VoiceGuides 0/1 10-Voice guide 0/1
11-AutomatedAttendant Not used (see new software lock 20) 11-Not used
12-DISA 0/1 12-DISA 0/1
13-Station 0/128/250/500/1000/1500/2000/9999 13-E-CS engine 0/50/80/150/350/500/9999
14-FinancialReport 0/1 14-Integrated metering 0/1
15-ExternalAccounting Not used (see new software lock 50) 15-Not used
16-OnTheFlyAccounting Not used (see new software lock 51) 16-Not used
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION F3.301.10
COMPARING THE R5.0 Ux AND R6.2 LICENSES RELEASE 6.2
R5.0 Ux R6.2
17-ACDTrafficObs 0/1 17-Not used
18-DistributorType 1 to 4 18-Not used
19-PrivateBChannel 0 to x 19-Corporate networking 0/50/80/150/350/500/9999 (>= lock 013 if <>0)
20-AAVoiceGuide 0/6/9999 20-Automated attendant 0/6/9999
21-VPS 0 to x 21-Number of VPS ports 0/2/4/…/240 ( step of 2 )
22-4635I 0/1 22-Not used
23-ELA 0 to x 23-Not used
24-ELN 0 to x 24-Not used
25-CLI 0 to x 25-Not used
26-CLA 0 to x 26-Not used
27-CSTA_CallCenter (see new software locks 100/101) 27-Not used
28-LockHard p1: 0/1 P2: 0/1 28-Not used
29-DECTAddOn p1: 0/1/2/3 29-DECT/PWT engine 0/1
30-4736ACD 0/1 30-Not used
31-AMIS 0/1 31-Not used
38-InfoCenter 0/1 38-Infocenter link 0/1
39-TrafObs47xx 0/128/250/500/1000/1500/2000/9999 39-Performance 0/50/80/150/350/500/9999 (>= lock 013 if <>0)
40-IncidentsOnFly 0/128/250/500/1000/1500/2000/9999 40-Real Time Incidents 0/50/80/150/350/500/9999 (= lock 47 )
41-DectRegister 0/1 41-DECT register 0/50/80/150/350/500/9999 (= lock 50 )
42-Accounting47xx 0/128/250/500/1000/1500/2000/9999 42-Accounting users 0/50/80/150/350/500/9999 (>= lock 013 if <>0)
43-LockHardDECT 0/1 43-Not used
44-SBC 0 to x 44-4059 SBC 0/1/2/3/………../50
45-BLF 0 to x 45-4059 BLF 0/1/2/3/………../30
46-FaxServer 0/1 46-FAX server ABC-A link 0/1/2/3/…..……/28
47-Alarm47xx 0/128/250/500/1000/1500/2000/9999 47-Alarms 0/50/80/150/350/500/9999 (>= lock 013 if <>0)
48-CSTA_WorkGroup (see new software locks 100/101 ) 48-Not used
49-STAP 0/128/250/500/1000/1500/2000/9999 49-Directory 0/50/80/150/350/500/9999 (>= lock 013 if <>0)
TC0711 2 Ed. 01 / 14 October 2005

OmniPCX Enterprise
R5.0 Ux R6.2
50-MAO47xx 0/128/250/500/1000/1500/2000/9999 50-Configuration 0/50/80/150/350/500/9999 (>= lock 013 if <>0)
51-V24MeteringOnFly 0/128/250/500/1000/1500/2000/9999 51-Real Time Metering on v24 0/50/80/150/350/500/9999 (= lock 042)
52-4635: Basic package 0=none 1=4635J 2=4635H 52-4635: Basic package 0=none 1=4635J 2=4635H
53-OPS4635UpgradeAc 0 to x 53-Not used
54-OPS4635UpgradeHour 0 to x 54-Not used
55-OPS4635UpgradeLang 0 to x 55-Not used
56-4635Network 0 to 2x 56-4635 Networking OctelNet 0/2/4/……./64 ( = lock 057 )
57-4635Fax 0 to 2x 57-4635 Fax manager 0/2/4/……./64
58-4635CallManage 0 to 2x 58-4635 Call manager 0/2/4/……./64 ( = lock 057 )
59-4635Hotel 0 to 2x 59-4635 Hotel manager 0/2/4/……./64 ( = lock 057 )
60-4635Port 0 to 2x 60-4635 Number of ports 0/2/4/……./64
61-4635Hour 0 to x 61-4635 Number of hours 0/5/10/…../40
62-4635Languages 0 to x 62-4635 Number of languages 0/1/2/……./8
63-4635Attendant 0 to 2x 63-4635 Attendant manager 0/2/4/……./64 ( = lock 057 )
64-4635ValueManage 0 to 2x 64-Not used
65-4635Recording 0 to 2x 65-4635 Recording manager 0/2/4/……./64 ( = lock 057 )
66-4635AMIS 0 to 2x 66-4635 Networking AMIS 0/2/4/……./64 (= lock 057)
67-CSTAPredictiveCall 0/1 67-Not used
68-4755BSM Not used 68-Not used
69-4755Fault Not used 69-Not used
70-4755Metering Not used 70-Not used
71-4755Performance Not used 71-Not used
72-4755Directory Not used 72-Not used
73-4755Network4220 Not used 73-Not used
74-4755Network4300L Not used 74-Not used
75-HospitalNetwork 0/1 75-Networking Hospital (France) "open" /1
76-CCDNumberAgents P1: 0/5/10/25/50/500/9999 76-M-CCD agents 0/5/10/……./2000
Ed. 01 / 14 October 2005 3 TC0711

OmniPCX Enterprise
R5.0 Ux R6.2
P2: 0 to 4
77-CCSNumberPCSuperv 0 to x 77-CCS mono-site 0/1/2/3/……/60
78-CCDAccToComRec 0/1 78-CRI Call Record Interface 0/1
79-ISVPN 0/1 79-ISVPN 0/50/80/150/350/500/9999 (= lock 019)
80-ABCVPN 0/1 80-VPN 0/50/80/150/350/500/9999 (= lock 019)
81-Conference29 0/1 81-Meet-me Conference 29 party 0/1/2/……/30
82-NumberDECTLicence 0 to x 82-Number of DECT terminals 0/1/10/20/……/9990 (= lock 175)
83-AccountingEthernet 0/128/250/500/1000/1500/2000/9999 83-Flow Metering on Ethernet 0/50/80/150/350/500/9999 (= lock 042)
84-CentralVoiceMail 0/128/250/500/1000/1500/2000/9999 84-4635 users 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
85-CustomerType 0/1 85-Not used
86-Popup 0 to x 86-Automatic directory pop-up 0/1/2/……../50
87-BetaTest 0 to x 87-Beta test release 0 to x
88-MilitaryType 0 to 8 88-Not used
89-NotificationServer 0/50/300/800/9999 89-Notification Server 0/50/300/800/9999
90-Roaming 0/10/20/……./9999 90-M-Roaming DECT/PWT 0/10/20/……./9999
91-VGRecordOnUA 0/1 91-Voice guide record fr 0/1
92-VH 0/1 92-Not used
93-4635J 0/1 93-Not used
94-WorkForceLink 0/9999 94-WMI Workforce Manager interface 0/1
95-SpecificFeatures 0/8191 95-Not used
96-HotelSuite 0/1 96-Not used
97-CentralizedVPS 0/128/250/500/1000/1500/2000/9999 97-VPS users 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
98-TicketLocalCalls 0/125/500/1000/2000/9999 98-Accounting for local calls 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
99-TicketABCNetCalls 0/125/500/1000/2000/9999 99-Accounting for ABC calls 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
100-CSTAProfile 0/2 100-CSTA profile 0= none 2= Call center
101-CSTAMonitorRequests 0/5/10/15/…../5000 101-M-CSTA monitoring requests 0/5/10/15/…../9995
102-CCS_PCSupMultiSite 0 to x 102-CCS multi-site 0/1/2/……/60
TC0711 4 Ed. 01 / 14 October 2005

OmniPCX Enterprise
R5.0 Ux R6.2
103-CCD_WBI 0 to x 103-RTI Real Time Interface 0/1/2/……/60
104-Release2_SN 0/100 104-Not used
105-CompressedCalls 0 to x 105-Compressed calls 0/1/2/3/………../9999
106-TransfixAccessX24V36 0 to x 106-Transfix Access X24V36 "Open" /9999
107-4635VisualMessager 0 or 2016 107-4635 Visual messenger 0 or 5000 (if lock 057 <> 0)
108-4635WebMessager 0/32/……../1024 108-Not used
109-4635DigitalNetwork 109-4635 IP Octel networking 0/2/4/……./64 (= lock 057)
110-4635HDiskMirroring 0/1 110-4635 Global message redundancy 0/1
111-Ubiquity 0/16/32/64/256/……./1600 111-Ubiquity 0/10/20/……./9990
112-CCSLight 0 to x 0/1/2/…/60
113-CSTAPiloteCCDMonito 0/1 113-CSTA pilots monitoring 0/1
114-TSAPI 0/5/10/15/20/……./2000 114-TSAPI server 0/5/10/15/20/……./2000
115-CCAAgents 0/5/10/15/20/……./500 115-M-CCA softphone 0/5/10/15/20/……./1000 (<= lock 076 if <> 0)
116-4980StdAgents 5/10/20/30/40/……/3000 116-ECC My Softphone (4980 Std) 5/10/20/30/40/..…/3000 (= lock 129)
117-4980ProAgents 0/10/20/30/40/……/3000 117-M-ECC 4980 Option (4980 Adv) 0/10/20/……3000 (<= lock 129 if <> 0)
119-4980NomadicLog 5/10/20/……./600 119-4980 nomadic logged 5/10/20/……./600
120-MigrationRelease 0/1 120-Not used
121-CLIPOnVPS_SL 0/2/4/8/…..30 121-CLIP on VPS 0/2/4/6/8/...…/240 ( = lock 21 )
122-ACAPI 0/128/250/500/1000/1500/2000/9999 122-ACAPI via CMIP 0/50/80/150/350/500/9999 (= lock 050)
123-IVR_Z_PCM 0/5/10/15/20/……./9999 123-M-CSTA IVR ports monitored 0/5/10/15/20/…….../5000
125-CallCenterWebAgents 0/5/10/15/20/……./500 125-M-CCWeb Agents 0/5/10/15/20/………/1000 (<= lock 076 if <> 0)
126-AHLonIP 0/1 126-Hotel AHL link 0/1
127-DECTEncryption 0 to x 127-M-Encryption DECT/PWT users 0/10/20/……./9990
128-4615Ports 0/2/4 128-4615 Nb of Access 0/2/4
129-4980GroupwareAgents 0/5/10/20/30/40/……/3000 129-M-ECC My Softphone (4980 grp) 0/5/10/20/30/40/……/3000
130-CSTANiceRecording 0/1/2 130-CSTA voice recording 0/1
131-RemoteLio 0 to x 131-Remote LIO 0/16/32/……./9984 (step of 16)
Ed. 01 / 14 October 2005 5 TC0711

OmniPCX Enterprise
R5.0 Ux R6.2
132-VoiceOnIP 0 to x 132-IP-Trunk 0/9999 (= lock 187)
133-AddOnConference 0/128/250/500/1000/1500/2000/9999 133-Mastered conference 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
134-MultiCompanies 0/128/250/500/1000/1500/2000/9999 134-Multi-tenant 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
135-G729Algorithm 0 to x 135-G729A Server 0/1/2/3/………../9999 (= lock 469 if <> 0)
136-Priority 0/128/250/500/1000/1500/2000/9999 136-Priority 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
137-CallRestriction 0/128/250/500/1000/1500/2000/9999 137-Call restriction 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
138-IPEquipment 0/10/20/30/40/……/9999 138-IP Clients 0/10/20/……./9990 (= lock 176 + 317)
143-TAPIPremiumServer 0/5/10/20/30/40/……/5000 143-TAPI premium server 0/5/10/20/30/40/……/5000
144-4980ManagementR2 x1 / x2 / x3 / x4 / x5 144-Not used
145-BitChannelRecord 0/5/10/15/20/……./600 145-M-CSTA Recording B channel 0/5/10/15/20/……./600
146-UTAM 0/1 146-PWT mobility (UTAM) 0/1 (1=USA market)
147-IPDevice 0 to x 147-Not used
148-IPCallServer 0/1 148-IP Call Server 0/1
149-4980Dispatcher 0 to x 149-Not used
151-4635VPIM 151-4635 VPIM 0/2/4/……/64 (=lock 057)
152-Ith_radio 0/1 152-Ith Radio 0/1
153-SNMP 0/1 153-SNMP trap 0/1
154-Additional S0 feature 0/1 154-Additional S0 feature 0/1
155-Additional safety features 0/1 155-Additional safety features 0/1
156-Ith 0/1 156-Interphony features 0/1
157-CCANomadic 0/1 157-CCA Nomadic 0/1
158-CSTAByPass 0 to x 158-CSTA by-pass 500/1000/1500/…../9500
160-CCE 0/5/10/15/20/……./1000 160-M-CCEmail Agents 0/5/10/15/20/……./1000
161-CCO 0/5/10/15/20/……./1000 161-M-CCOutbound Agents 0/5/10/15/20/……./1000
162-CCOPredictif 0/5/10/15/20/……./1000 162-M-CCOutpredial Agents 0/5/10/15/20/……./1000
164-NiceRemoteBChanRec 0/5/10/15/20/……./600 164-M-CSTA Record networked 0/5/10/15/20/……./600
165-Release4400 0 to x 165-OmniPCX Enterprise 4400 release 34=R6.2
TC0711 6 Ed. 01 / 14 October 2005

OmniPCX Enterprise
R5.0 Ux R6.2
166-4980MultiDevice 0/5/10/20/30/……./3000 (=lock 129) 166-4980 Multi Device 0/5/10/20/30/……./3000 (=lock 129)
167-ACR SQL 0/1 167-ACR Data base read 0/1
168-Number of HPOV nodes 0/1/2/…../100 168-Number of HPOV nodes 0/1/2/…../100
169-VAD 0/9/18/27/……./315 (step of 9) 169-Voice detection channels 0/1/2/3/4/……../315
170-SMSNotifServer 0/1 170-Not used
171-CentralNotifServer 0/1 171-Not used
173-M-Advanced Reflexes users 0/10/20/30/……/9990 (step of 10)
174-M-Analog users 0/10/20/30/……/9990 (step of 10)
175-M-Mobile users 0/10/20/30/……/9990 (step of 10)
176-M-Advanced e-Reflexes users 0/10/20/30/……/9990 (step of 10)
177-M-SIP users 0/10/20/30/……/9990 (step of 10)
178-4645 Voice mail engine 0/1/2/3
179-M-4645 users 0/50/80/150/350/500/9999
181-OmniPCX Enterprise (=1) 0/1
182-4645 networking 0/1
183-4645 additional language 0/1/2/3/4/5/6/7
184-Integrated gatekeeper 0/1
185-SIP Gateway 0/1
186-E-CS redundancy 0/1
187-H323 (G711) network link 0/1/2/3/4/…../1000
188-SIP network links 0/1/2/3/4/…../1000
189-CCTI 0/5/10/15/20/25/…../9999 189-M-CCTI agents 0/5/10/15/20/25/…../1000
190-RSINumberAgents 0/5/10/15/20/25/…../1000 190-M-RSI call center agents 0/5/10/15/20/25/…../2000
191-CampusDect 0/1 191-Campus DECT 0/1
192-DREX 0/1 192-T2 D_REX protocol 0/1
193-VoiceGuidesOnCpu6 0/1 193-Embedded voice guides 0/1
194-4645 My Messaging 0/10/20/30/……/1000 (step of 10) (<= lock 179 if <>0)
Ed. 01 / 14 October 2005 7 TC0711

OmniPCX Enterprise
R5.0 Ux R6.2
195-CCD Profile 0/1/2
196-RSIBusiness 0/5/10/15/20/25/…../5000 196-RSI Business agents 0/5/10/15/20/25/…../1000
197-G729A Client 0 to x 197-M-G729A Client 0/10/20/30/……/4000 (step of 10)
198-G723.1 Client 0 to x 198-G723.1 Client 0/10/20/30/……/4000 (step of 10)
199-Version 4400-R5.0 Ux 0/1
200-4400 Mobiles migration 0/1/2/3/4/…../5000
201-4400 Reflexes migration 0/1/2/3/4/…../5000
202-4400 Analog migration 0/1/2/3/4/…../5000
203-Upgrade CCS light to CCS Monosite 0/1/2/…../60
301-Clé hard 1 sur CPU 4400 N° de la clé hard
302-Clé hard 2 sur CPU 4400 N° de la clé hard
308-M-Remote extension and MIPT 0/5/10/15/20/25/……/9990
309-XML Telephony 0/10/20/30/……/3000 (step of 10)
310-M-CLIP Z 0/10/20/30/……/5000 (step of 10)
311-Networking ACR 0/1
312-Scripting agents 0/5/10/15/20/25/……/1000
313-eCC Gateway 0/1/2/3
314-4635 My Messaging users 0/10/20/30/……/5000(step of 10)
315-Migration clé hard 4400 0/1
316-M-Standard Reflexe User (Not used) 0/10/20/...../5000
317-M-Standard IP User (Not used) 0/10/20/...../5000
318-XML IP Touch-IP engine 0/1/2/...
322-CSTA Over 9999
325–IP Touch Security Engine 0/1
326–M-Secured IP-Touch Phones 0/10/20/...../5000
327–M-IP-Touch Security MCM 0/1/2/.../120
328–M-IP-Softphone Attendants 0/1/2/.../50
TC0711 8 Ed. 01 / 14 October 2005

OmniPCX Enterprise
R5.0 Ux R6.2
329–M-IP-Softphone Agents 0/1/2/.../tbd
467-ARS 0/128/250/500/1000/1500/2000/9999 467-ARS 0/50/80/150/350/500/9999 (>= lock 013 if <> 0)
468-ProductType 1/2/3/4/9999 468-Product type 9999
469-G723Algorithm 469-G723.1 Server 0/1/2/3/……/9999 (=lock 135 if <>0)
Ed. 01 / 14 October 2005 9 TC0711

OmniPCX Enterprise
TC0711 10 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2 OmniPCX 4400 MIGRATION TO
OmniPCX Enterprise RELEASE 6.2
OmniPCX 4400 MIGRATION TO

CONTENTS
1. MIGRATING AN OMNIPCX 4400 TO AN OMNIPCX ENTERPRISE

R6.2.............................................................................................3
1.1. Interworking of R6.2 with previous releases of OmniPCX 4400/Enterprise 3
1.2. Purpose of the document .......................................................................... 3
1.3. Content of the document .......................................................................... 5
1.3.1. Migration scenarios ..........................................................................................5
1.3.2. Actis and migration...........................................................................................5
1.3.3. Synchronizing the operations to be carried out during deployment of the
migration .......................................................................................................................5
1.3.4. Required method for implementing the migration ............................................5
1.3.5. Changeback possibilities ..................................................................................5
1.4. Rules to be observed................................................................................. 5
2. ISO TYPE MIGRATION..................................................................6

2.1. Actis configuration .................................................................................... 6
2.1.1. Replacement of applications and hardware by Actis.........................................6
2.1.2. Non replacement of applications and hardware by Actis..................................8
2.2. Operations to be carried out on the site before starting............................ 9
2.3. Preparing the migration in the laboratory................................................. 9
2.3.1. Prior deletion of the "phase-out" applications and hardware ............................9
2.3.2. Communication Servers ....................................................................................9
2.3.3. Moving the shelves 18 and 19 ........................................................................10
2.3.4. Preparing the applications and hardware.......................................................10
2.4. Summary flow chart................................................................................ 13
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
OmniPCX 4400 MIGRATION TO F3.301.10 – RELEASE 6.2
3. APPLIANCE SERVER TYPE MIGRATION .......................................16

3.1. Actis configuration .................................................................................. 16
3.1.1. Replacement of applications and hardware by Actis.......................................16
3.1.2. Non replacement of applications and hardware by Actis................................17
3.2. Operations to be carried out on the site before starting.......................... 18
3.3. Preparing the migration in the laboratory............................................... 18
3.3.1. Prior deletion of the "phase-out" applications and hardware ..........................19
3.3.2. Preparing the applications and hardware.......................................................20
4. CASE OF MIGRATION OF A PABX NETWORK .............................23
5. SWITCHOVER TO R6.2 ON THE SITE ..........................................23

5.1. Voice mail in network ............................................................................. 23
5.2. System synchronization........................................................................... 23
TC0711 2 Ed. 01 / 14 October 2005

OmniPCX Enterprise
1. MIGRATING AN OmniPCX 4400 TO AN OmniPCX ENTERPRISE

R6.2
1.1. Interworking of R6.2 with previous releases of OmniPCX 4400/Enterprise

Alcatel customers can migrate from the OmniPCX 4400 towards the OmniPCX Enterprise, and
benefit from new features and services provided by the new software release.
A smooth transition is made possible by interconnecting nodes in the same ABC F2 network based
on different versions of the OmniPCX 4400 and Enterprise software.
This will allow customers to migrate on a node-by-node basis without compromising
services/features that are already deployed.
The following releases can be supported on the same ABC F2 homogenous network:
− R5.0 Ux
− R5.0 Lx (1)
− R5.1 (1)
− R5.1.1 (1)
− R5.1.2
− R6.0 (2)
− R6.0.1
− R6.1 (3)
− R6.1.1
− R6.2
(1) Releases 5.0 Lx, 5.1 and 5.1.1 are no longer supported; they are replaced by Release 5.1.2.
(2) Release 6.0 is no longer supported; it is replaced by Release 6.0.1.
(3) Release 6.1 is no longer supported; it is replaced by Release 6.1.1.
1.2. Purpose of the document

The purpose of this document is to advise technicians on how to prepare and install the migration
from a Stand-Alone or network OmniPCX 4400 to an OmniPCX-Enterprise R6.2.
This operation can be delicate, since it requires preparation and a methodical approach. In fact,
R6.2 does not support the migration of a certain number of "phase out" internal applications,
external applications and hardware which were authorized in previous releases. An effort must be
made to replace all these items on the day that R6.2 is made available to the client.
This document refers to the technical communication TC0711 Installation procedure for version
F3.301.10 – Release 6.2, which the technician carrying out the migration must have.
It does not deal with migration and simultaneous additions of new functionalities and hardware,
except when "phase-out" applications and hardware are concerned.
It is highly unadvisable to cumulate migration and addition operations.
Ed. 01 / 14 October 2005 3 TC0711

OmniPCX Enterprise
TC0711 4 Ed. 01 / 14 October 2005

OmniPCX Enterprise
1.3. Content of the document
1.3.1. Migration scenarios

To make the migration process easier to understand, two scenarios are described.
1 Migration of a system requiring new R6.2 functionalities without modifying the type of
"Communication Server", in other words it retains its 4400 CPUs. This type of migration is called
"ISO".
2 Migration of a system requiring an evolution in the type of "Communication Server".
Example
Replacing a CPU5 with an "Appliance Server", the processing capacity of which allows the
number of nodes in the future to be decreased, and to replace them with ACTs on IP.
1.3.2. Actis and migration

Any system migrating to R6.2 must be configured using Actis 9.6.
Since Actis knows the "phase out" internal and external applications and the hardware that are not
carried over to this version, it deals with the ordering of these applications and hardware.
However, in certain cases, operations may be required that are not taken into account by Actis.
1.3.3. Synchronizing the operations to be carried out during deployment of the migration
The deployment of the migration requires perfect synchronization of the operations to be carried out
by the technicians, before, during and after the migration.
1.3.4. Required method for implementing the migration

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

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

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

OmniPCX Enterprise
2. ISO TYPE MIGRATION

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

After the configuration, Actis generates licenses and hardware, a part of which can be used
immediately in the laboratory by the technician.
2.1.1. Replacement of applications and hardware by Actis

Actis plans to replace the following applications and hardware.
2.1.1.1. Communication Servers

− Migration to OmniPCX Enterprise R6.2 with changing the CPU.
• The systems with CPU3 change to CPU6 with:
♦ automatic replacement of disk if less than 6 GB,
♦ 128 MB SDRAM.
• The systems with CPU5 Step1/CPU5 Step2 change to CPU7 with:
♦ 256 MB SDRAM.
− Migration to OmniPCX Enterprise R6.2 without changing the CPU.
• The systems with CPU5 Step3 remain with CPU5 Step3:
♦ With automatic replacement of disk if less than 6 GB,
♦ 128 MB SDRAM.
• The systems with CPU6 remain with CPU6:
♦ 256 MB SDRAM.
Note
The CPU5 Step3 board is no longer configurable from Release 6.1 for new business accounts (it is
replaced by the CPU7). Nevertheless, it can be ordered for existing sites when adding a CPU
duplication.
2.1.1.2. LIOe / TSC-LIOe

LIOe and TSC-LIOe boards are no longer supported as of Release 6.0. When migrating, they are
automatically changed toINTIP2 board.
INTIP2 migration packages were create to help the replacement and to reduce the cost.
TC0711 6 Ed. 01 / 14 October 2005

OmniPCX Enterprise
Note
LIOe and TSC-LIOe boards must also be changed when functioning in heterogeneous network. In a
network with R6.0.x or R6.1.x nodes, there must not be LIOe and TSC-LIOe boards.
2.1.1.3. IO2
When migrating, IO2 is changed to IO2N board if Actis configures a CPU7 board.
2.1.1.4. OBCA
CPU7 board does not support the OBCA2 daughter board. Actis will configured the IO2N board
when the number of channels is different of zero.
2.1.1.5. INT1/INT2
These boards are no more supported from Release 6.1.
On installations equipped with these boards, Actis replaces automatically the boards:
− INT1A / INT2A by INTOF2–A board,
− INT1B / INT2B by INTOF2–B board.
2.1.1.6. LIOB/LIOP/LIOX
These boards are in phase out from Release 6.1. Actis 9.6 does not allow the feature for addition or
for new installation.
2.1.1.7. DECT2/DECT4
DECT2/DECT4 boards configured on installations to be migrated, are supported by OmniPCX
Enterprise Releases 5.1, 6.0.x, 6.1.x, 6.2.x but are not allowed in addition.
Moreover, DECT8 boards are not compatible with DECT2/DECT4 boards. These latter must be
replaced by DECT8 boards.
2.1.1.8. OmniMessage
The 4630 voice mail is replaced by the 4635J voice mail.
The 4635H and 4635H-1 voice mails are replaced by 4635H-2 voice mails.
Ed. 01 / 14 October 2005 7 TC0711

OmniPCX Enterprise
46xx hardware status of system to be migrated:
Status before migration Station after migration

VPCPU VPM35-1
VPCPU-1 VPM35-1
VPM35 VPM35-1
VPS35 VPU5
MSB MSBI
MSB2IB ATB2 (if one MSBI board)
MSB2IB ATB3I (if two MSBI boards)
VMU-OBCA (CPU3 board) VMU-OBCA2 (with CPU6 board)
VMU-OBCA (CPU5 board) IO2N (with CPU7 board)
2.1.1.9. OmniVista
The 4715, 4730, 4740 4755 and OmniVista 4760 R1.0/1.5 applications are replaced by the
OmniVista 4760 Release 3.2 application.
It is mandatory to migrate from OmniVista 4760 R2.0, R2.1, R3.0, R3.1 to Release 3.2.
2.1.1.10. OmniTouch
The ACD-V1 is replaced by the CCD.
The supervisors are replaced by the CCS.
2.1.1.11. Migration eCC "4980 Web Softphone" to OmniTouch UC R3.1

eCC "4980 Web Softphone" application is automatically migrated to OmniTouch Unified
Communication R3.1 application (OmniTouch UC).
2.1.1.12. Migration 4635 Visual Messenger to OmniTouch UC

4635 Visual Messenger application is no longer supported in Release 6.2. It is replaced by
OmniTouch UC R3.1 application.
2.1.1.13. 2600, 4600, 5400 set equipment

The 2600, 4600 and 5400 analog equipment is replaced by eZ32 boards.
The 2600, 4600 and 5400 digital equipment is replaced by eUA32 boards.
2.1.2. Non replacement of applications and hardware by Actis

Actis does not plan to replace the following applications and hardware.
2.1.2.1. SPB daughter boards (extension of the V24 ports of the system)
Actis does not plan to replace the SPB board, but enforces the deletion of this circuit. The Actis
operator then has the choice of replacing the old SPB accesses, either with TA V120 accesses or with
one or more V24-IP modules.
TC0711 8 Ed. 01 / 14 October 2005

OmniPCX Enterprise
2.2. Operations to be carried out on the site before starting

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

Preparing the migration in the laboratory has the advantage of limiting the intervention time and
disturbances to site operation.
CAUTION
It is not possible to migrate a database from a Release below R1.5 to R6.2. As a result, any site
which starts from a Release below 1.5 must go via an intermediate database translation, to a
Release between R1.5 and R5.0.1.Ux.
2.3.1. Prior deletion of the "phase-out" applications and hardware

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

Modify the type of CPU if this has changed.
REMINDER
You must set the appropriate type of CPU otherwise a initialisation problem of DECT
or INTOF couplers can occurs (for instance when changing from CPU3 to CPU6).
Ed. 01 / 14 October 2005 9 TC0711

OmniPCX Enterprise
− Deletion of the 4630 voice mail.
Delete the users’ 4630 voice mail boxes, then delete the 4630 voice mail.
− Migration of the 4635H and 4635H-1 voice mails to 4635H-2.
There is no deletion involved in this operation.
2.3.2.2. OmniTouch
The migration of the ACD-V1 must be prepared in the laboratory.
It is compulsory to delete the ACD-V1 objects before carrying out database translations, as it will no
longer be possible to delete them in R6.2.
Refer to the technical communication TC0487 ACD-V1 Migration to CCDistribution.
2.3.2.3. 2600, 4600, 5400 set equipment

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

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

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

Required means
− A back-up of the database on which the "phase-out" applications and hardware have been
deleted.
− A 4400 ACT.
− A hard disk with a minimum of 6 GB if the site CPU(s) do not need to be changed for the
migration, or a CPU6 Step2/CPU7 if it is intended to replace the site CPU.
− The R6.2 OPS files generated by Actis. There are four or five of these files:
• <offer_id>.zip
TC0711 10 Ed. 01 / 14 October 2005

OmniPCX Enterprise
• <offer_id>.swk
• <offer_id>.hw
• hardware.mao
• <offer_id>.sw4760 (if 4760 present on the site)
The hardware generated by Actis can be prepared in the laboratory.
When the site CPUs no longer comply, Actis orders a CPU6 or CPU7 from the manufacturer. These
CPUs can be used for preparing the migration. The CPUs which come from a factory all have a
CPU_ID flashed from the start.
If the site CPUs comply, the hardware keys can be retained.
In this case, preparation for the migration should be carried out on a CPU with a laboratory
equivalent to the one on the site, the disk for which will be implanted later on the client’s CPU.
2.3.4.1. Communication Servers (CPU)

Operating mode
− Install the R6.2 software (1).
− Load the site database (1).
− Load the site Chorus data (1 & 2).
− Do not start the telephone (1).
− Install the OPS files (1).
previous releases.
It puts together the following steps: RUNMAO, translation of the database and
installation of the OPS files.
(1) Follow the technical communication TC0711 Installation procedure for version F3.301.10 –
Release 6.2.
(2) Do not restore the Chorus data if you come from a Release below R3.0.

LIOe and TSC-LIOe boards are no longer supported; refer to paragraph 2.1.1.2 .
The management of these boards must be removed and replaced by a management of INTIP
boards.
Configure the INTIP MAC addresses with the management.
2.3.4.3. INT1/INT2
INT1/INT2 boards are no more supported; refer to the paragraph 2.1.1.5. The management of
these boards must be removed and changed to INTOF board management.
Ed. 01 / 14 October 2005 11 TC0711

OmniPCX Enterprise
− Replacing the 4630 voice mail by a 4635J voice mail.
The 4635J voice mail can be prepared in the laboratory, once the hardware is received, but
since it is not possible to migrate announcements and messages between the two products, an
agreement needs to be reached with the client for freezing the voice service on the site before the
migration to R6.2, in order to no longer authorize message drops. This is a replacement and not
a migration.
− Migration of the 4635H and 4635H-1 voice mail to the 4635H-2 voice mail.
This migration does not need new locks. It can be carried out on the site before migration to
R6.2. This depends on the compatibility of the VPM35s with the site version.
• If there is compatibility, carrying out this operation before the migration will avoid the
cumulation of operations on the day of the switchover to R6.2.
• If there is no compatibility between the VPM35 and the site version, a part of the migration
can be carried out in the laboratory once the VPM35 board is received. The transferring of
announcements and messages is possible in the laboratory, if the client accepts the freezing
of the voice service for a defined period. If interruption of the service is not possible, the
announcements and messages must be transferred during the migration on the site.
Refer to the technical communications:
TC0666 Installation procedure for version 5.2.6
2.3.4.5. OmniVista
− Migration of 4715, 4730, 4740 and 4755 applications to the OmniVista 4760 Release 3.2
application.
This migration can be carried out on the site, once the hardware is received, as long as it is
carried out in the 21 days preceding the switchover to R6.2.
This is advised in order to avoid cumulating operations on the day of the switchover to R6.2.
2.3.4.6. OmniTouch
The ACD-V1 groups migrate to CCD.
The supervisors migrate to CCS.
2.3.4.7. 2600, 4600, 5400 set equipment

The 2600, 4600 and 5400 analog equipment migrates to eZ32.
The 2600, 4600 and 5400 digital equipment migrates to eUA32.
− Create the 4400 ACTs and the eZ32 and eUA32 circuits.
− Assign the analog and digital users.
TC0711 12 Ed. 01 / 14 October 2005

OmniPCX Enterprise
− Once the hardware is received, it is possible to start installing it on site.

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

OmniPCX Enterprise
OmniPCX 4400 migration to OmniPCX Enterprise Release 6.2 - ISO
Before starting, take stock of:

•. the applications and hardware to be changed (Installation procedure for R6.2 § 4)
•. the installation compatibility (Installation procedure for R6.2 § 5)
•. compatibilities (Installation procedure for R6.2 § 6)
yes no
Can the functionalities
deleted in R6.2 be evolved in
the current version?
Back up the current database. This back-up n°1 will be your reference (saveref1)
in the event of a changeback
Replace everything that can be replaced in your current version (without adding new licenses)
- 47x x --> 4760 (TCV036 Operation possible 21 days without official license)
- 4635 --> 4635 H2 (TC0155, TC0259 and TC0666)
- SPB --> IO2 (delete the ports used and recreate them on IO2)
- LIOE/TSCLIOE --> INTIP
- OBCA - -> IO2N in case of CPU7
- IO2 - -> IO2N in case of CPU7
- INT1/INT2 - -> INTOF/INTOF2
Warn the client of the constraints imposed by the change of version:

. freezing of the management (for a period defined with the client),
. risk, following your evolution, of losing the messages and announcements in the case of a change of voice mail (TC0155 -
TC0259 - TC0298 -TC0666)
. replacement of the ACDV1 by CCD (TC0487) on installation of the R6.2
Do you have
yes no
other
functionalities
to replace?
Is the version of no
the site
< R1.5.3
yes
Back up the current database. This back-up n°2 will be your

reference (saveref2) in the event of a changeback
Translate the data in a

Release compatible with R6.2
The following operations must be carried out only in the (R1.5.3 to R5.0.1Ux)
laboratory
Go to B Go to A
TC0711 14 Ed. 01 / 14 October 2005

OmniPCX Enterprise
no Is the version of yes

the site
< R1.5.3
Translate the data in a

Release compatible with
R6.2 (R1.5.3 to R5.0.1Ux)
Restore your database savref2 on a CPU loaded with Back up the current database (§ 8.2). This back-up n°3
the same version as the site or a Release lower than or (saveref3) will be used to carry out translations in R6.2
equal to R5.0.1Ux
Management to be carried out:

2600/5400 shelf: Unassign all the equipment used and delete the 2600/5400 boards and shelves.
ACDV1: Delete the ACDV1
4630: Delete the 4630 (see TC0298)
Back-up the current database (§ 8.2). This back-up n°4

(saveref4) will be used to carry out translations in R6.2
Your management is now ready to be translated to R6.2
You should now have the Actis files for R6.2

A lock request should first have been made by Actis and you
therefore now have four or five files (depending on whether or
not 4760 is present)
See § 7.4
Install R6.2, if possible, on a CPU which will be placed on site
Once the system is loaded, install the database (saveref4)

then
load the OPS files (via swinst --> § 10)
Translation is carried out automatically after loading the OPS files
Manage the missing functionalities:

. eUA32 and eZ32 equipment replacing the 2600 and 5400 equipment
. CCD
. Alcatel 4635
Back up the current database (§ 8.2). This back-up n°5 (saveref5) will be the one
with the new R6.2 management
Your CPU is now loaded in R6.2 with the new functionalities.

It is ready to be placed on site.
END
Ed. 01 / 14 October 2005 15 TC0711

OmniPCX Enterprise
3. APPLIANCE SERVER TYPE MIGRATION

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

After the configuration, Actis generates licenses and hardware, a part of which can be used
immediately in the laboratory by the technician.
3.1.1. Replacement of applications and hardware by Actis

Actis plans to replace the following applications and hardware.

4400 CPUs are deleted and replaced with Appliance Servers.
The IO2s are deleted and replaced with INTIP2s.
3.1.1.2. RMA
The RMA is deleted and replaced with an RMA in an S type cabinet (rack 1U).

LIOe and TSC-LIOe boards are no longer supported; refer to paragraph 2.1.1.2 .
The management of these boards must be removed and replaced by a management of INTIP
boards.
Configure the INTIP MAC addresses with the management.
3.1.1.4. INT1/INT2
INT1/INT2 boards are no more supported; refer to the paragraph 2.1.1.5. The management of
these boards must be removed and changed to INTOF board management.
TC0711 16 Ed. 01 / 14 October 2005

OmniPCX Enterprise
The 4630 voice mail is replaced by a 4635J voice mail.
The 4635H and 4635H-1 voice mails are replaced by 4635H-2 voice mails.
46xx hardware status of system to be migrated:
Status before migration Station after migration

VPCPU VPM35-1
VPCPU-1 VPM35-1
VPM35 VPM35-1
VPS35 VPU5
MSB MSBI
MSB2IB ATB2 (if one MSBI board)
MSB2IB ATB3I (if two MSBI boards)
VMU-OBCA (CPU3 board) VMU-OBCA2 (CPU6 board)
VMU-OBCA (CPU5 board) IO2N (CPU7 board)
3.1.1.6. OmniVista
The 4715, 4730, 4740 and 4755 applications are replaced by the OmniVista 4760 Release 3.2
application.
3.1.1.7. OmniTouch
The ACD-V1 is replaced by the CCD.
The supervisors are replaced by the CCS.
3.1.1.8. 2600, 4600, 5400 set equipment

The 2600, 4600 and 5400 analog equipment is replaced by eZ32 boards.
The 2600, 4600 and 5400 digital equipment is replaced by eUA32 boards.
3.1.1.9. Particular case of the Appliance Server replacing a CPU6

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

Actis does not plan to replace the following applications and hardware.
Ed. 01 / 14 October 2005 17 TC0711

OmniPCX Enterprise
3.1.2.1. SPB daughter boards (extension of the V24 ports of the system)
Actis does not plan to replace the SPB board, but enforces the deletion of this circuit. The Actis
operator must replace the old SPB accesses with one or more V24-IP modules. These operations
must be carried out manually using Actis.
3.1.2.2. Cases linked to the deletion of IO2, IO2N and OBCA

Actis does not configure the hardware that could be involved in the replacement of the functionalities
using IO2, IO2N, and OBCA.
3.1.2.3. Deleting level 3 ACTs

Level 3 ACTs connected behind an INTOF coupler are no longer authorized. They must be replaced
by ACT-IPs.
Since Actis has no knowledge of level 3 ACTs installed on the site, it does not take into account the
replacement of INTOF couplers with INTIP couplers. These operations must be carried out manually
using Actis.
3.2. Operations to be carried out on the site before starting

− Back up the database and the Chorus data on the site () Note).
This database will be used for preparing the migration in the laboratory. This means that as of
the moment that the database is backed up, until the site is switched over to R6.2, any
modifications made on the site will not be carried over, unless they have been listed by the
operator.
Note
There is no automatic translation of Chorus data of Releases below R3.0. You should not restore
− The functionalities not migrated following the deletion of the IO2, IO2N and OBCA, such as links
on B channels, links via modem, signaling back-up via ISDN, X25 on B channel, can be replaced
on the site before starting the migration procedure, in other words before backing up the
database.
Only the data applications via TA V120 access must be transferred to V24-IP accesses after the
translation of the database to R6.2.
3.3. Preparing the migration in the laboratory

Preparing the migration in the laboratory has the advantage of limiting the intervention time and
disturbances to site operation.
CAUTION
It is not possible to migrate a database from a Release below R1.5 to R6.2. As a result, any site
which starts from a Release below 1.5 must go via an intermediate database translation, to a
Release between R1.5 and R5.0.1 Ux.
TC0711 18 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3.3.1. Prior deletion of the "phase-out" applications and hardware

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

No modification is necessary, since the translation of the database deletes the CPU and IO2.
− Deletion of the 4630 voice mail.
− Migration of the 4635H and 4635H-1 voice mails to 4635H-2.
There is no deletion involved in this operation.
3.3.1.3. OmniTouch
The migration of the ACD-V1 must be prepared in the laboratory.
It is compulsory to delete the ACD-V1 objects before carrying out database translations, as it will no
longer be possible to delete them in R6.2.
3.3.1.4. 2600, 4600, 5400 set equipment

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

Delete and note the data applications connected to SPB and IO2. The SPB boards and the IO2s are
deleted during the translations. These applications will be created later on V24-IP.

The functionalities not migrated following the deletion of the IO2, IO2N and OBCA, such as links on
B channels, links via modem, signaling back-up via ISDN, X25 on B channel, must be deleted if this
Ed. 01 / 14 October 2005 19 TC0711

OmniPCX Enterprise
has not already been done on the site before starting the migration procedure, in other words before
backing up the database.
3.3.1.7. Particular case of the Appliance Server replacing a CPU6

Delete the voice guides and music on hold on the CPU6.
3.3.2. Preparing the applications and hardware

Required means
− A back-up of the database on which the "phase-out" applications and hardware have been
deleted.
− A 4400 ACT.
− The client’s INTIP2s and Appliance Servers.
− The R6.2 OPS files generated by Actis. There are four or five of these files:
• <offer_id>.zip
• <offer_id>.swk
• <offer_id>.hw
• hardware.mao
• <offer_id>.sw4760 (if 4760 present on the site)
The hardware generated by Actis can be prepared in the laboratory.
3.3.2.1. Communication Servers (Appliance Servers)

Operating mode
− Install the R6.2 software on the Appliance Server (1).
− Load the site database (1).
− Load the site Chorus data (1 & 2).
− Do not start the telephone (1).
− Install the OPS files (1).
previous releases. It puts together the following steps: RUNMAO, translation of the
database, moving the ACT0 to the first available ACT and installation of the OPS
files.
(1) Follow the technical communication TC0711 Installation procedure for version F3.301.10 –
Release 6.2.
(2) Do not restore the Chorus data if you come from a Release below R3.0.
TC0711 20 Ed. 01 / 14 October 2005

OmniPCX Enterprise
− Replacing the 4630 voice mail by a 4635J voice mail.
The 4635J voice mail can be prepared in the laboratory, once the hardware is received, but
since it is not possible to migrate announcements and messages between the two products, an
agreement needs to be reached with the client for freezing the voice service on the site before the
migration to R6.2, in order to no longer authorize message drops. This is a replacement and not
a migration.
− Migration of the 4635H and 4635H-1 voice mail to the 4635H-2 voice mail.
This migration does not need new locks. It can be carried out on the site before migration to
R6.2. This depends on the compatibility of the VPM35 with the site version.
• If there is compatibility, carrying out these operations before the migration will avoid the
cumulation of operations on the day of the switchover to R6.2.
• If there is no compatibility between the VPM35 and the site version, a part of the migration
can be carried out in the laboratory once the VPM35 board is received. The transferring of
announcements and messages is possible in the laboratory, if the client accepts the freezing
of the voice service for a defined period. If interruption of the service is not possible, the
announcements and messages must be transferred during the migration on the site.
Refer to the technical communications:
TC0666 Installation procedure for version 5.2.6.
3.3.2.3. OmniVista
− Migration of 4715, 4730, 4740 and 4755 applications to the OmniVista 4760 Release 3.1
application.
This migration can be carried out on the site, once the hardware is received, as long as it is
carried out in the 21 days preceding the switchover to R6.2.
This is advised in order to avoid cumulating operations on the day of the switchover to R6.2.
3.3.2.4. OmniTouch
The ACD-V1 groups migrate to CCD.
The supervisors migrate to CCS.
3.3.2.5. 2600, 4600, 5400 set equipment

The 2600, 4600 and 5400 analog equipment migrates to eZ32.
The 2600, 4600 and 5400 digital equipment migrates to eUA32.
− Create the 4400 ACTs and the eZ32 and eUA32 circuits.
− Assign the analog and digital users.
Ed. 01 / 14 October 2005 21 TC0711

OmniPCX Enterprise
− Once the hardware is received, it is possible to start installing it on site.

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

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

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

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

OmniPCX Enterprise
3.3.2.10. Modifications linked to the installation of the Appliance Servers

It is advisable to test the Appliances Servers and INTIPB sets in the laboratory.
Operating mode
− Create the INTIP2 couplers in INTIPB or IOIP mode in position 6, 20 (or 10) of the old ACT0
which has become ACTx, (check the mode to configure in the Actis file).
Note
The CPUs and IO2s have been deleted during the translation. The INTIPBs and IOIPs both
configure themselves on an INTIP2 coupler.
− Configure the MAC addresses of the INTIP2s through the management.
− Configure the ACTx (old ACT0) as reference Media Gateway.
− Configure the switches giving the position of the ACTx on the INTIP2 couplers.
− Configure the IP data of the INTIP2 couplers (static addressing mode), using a VT100 terminal.
CAUTION
The cable for connecting the terminal to the INTIP2 couplers is different to the cable of the INTIPs. It
is identical to the one for the GD boards, 3EH 75003 AAAA.
Note
In IOIP mode, the INTIP2 couplers can not support a compressor board.
4. CASE OF MIGRATION OF A PABX NETWORK

See sections 4, 5 and 6 of the technical communication TC0711 Installation procedure for version
F3.301.10 – Release 6.2.
5. SWITCHOVER TO R6.2 ON THE SITE
5.1. Voice mail in network

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

CAUTION
An Omni_PCX 4400 which migrates to Omni_PCX Enterprise with Appliance Server is from
now on subject to the domain synchronization rules.
Modify the synchronization priorities of the digital accesses.
See appendix 4 Synchronizing the OmniPCX Enterprise after migrating to R6.2 with Appliance
Server.
The synchronization rules are explained in the "PABX synchronization" section of the technical
documentation.
Ed. 01 / 14 October 2005 23 TC0711

OmniPCX Enterprise
TC0711 24 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2 SYNCHRONIZATION
SYNCHRONIZATION
Synchronizing the system after migration to Release 6.2 with an Appliance Server.
1. PREAMBLE
When an OmniPCX 4400 or an OmniPCX Enterprise with CPU5, CPU6 or CPU7 migrates to an
OmniPCX Enterprise with Appliance Server, this Appliance Server takes the place of the ACT-0
during the migration of the database. The old ACT0 is then moved to the first free ACT position. We
will call it ACT-X.
The Appliance Server (ACT-0) sees ACT-X (and if applicable the ACTs attached to it) as an ACT-IP.
The ACT-X which has become ACT-IP is therefore subject to domain synchronization rules. The
accesses which synchronize this ACT should have a synchronization priority between 200 and 254 in
order to create a new synchronization domain.
The management operations need to be carried out manually after the migration, in order to modify
the priorities and to return to correct operation.
The examples in this document allow new synchronization rules to be applied in most cases.
The synchronization rules are explained in the "PABX synchronization" section of the technical
documentation.
2. EXAMPLES
2.1. Example 1
See Figures 1 and 2.
− The following system, before migration to Release 6.2:
• One CPU5 in the ACT-0.
• Two peripheral ACTs (ACT-1 and ACT-2) connected to the ACT-0 through INTOF links.
• In the ACT-1 and ACT-2, there is a T2/T1 access connected to the public network.
• The synchronization priority is managed at "0" on the three accesses.
• One of the three accesses synchronizes the three ACTs. The other two are potential
synchronizers.
• If the synchronizing access breaks down, one of the other two accesses will become the
synchronizer for the three ACTs. If the access is restored, it will become a potential
synchronizer.
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
SYNCHRONIZATION F3.301.10 – RELEASE 6.2
− After migration to Release 6.2 with Appliance Server:

• The CPU5 is replaced by an Appliance Server. An INTIP2 is put in place of the CPU5.
• The ACT-0 is moved to ACT-3 (first free ACT).
• The ACT-3 is now an ACT-IP. It should belong to a synchronization domain.
• The ACT-3 access should be managed with priority 200. But note that the other two accesses
should be managed with priority 201 and 202 so that they stay in the same synchronization
domain (see Figure 1), and not 200 and 200, since in this case two other synchronization
domains would be created (see Figure 2).
• Unlike the configuration before migration, if the access with priority 200 breaks down, the
access with priority 201 will become the synchronizer, but when the access with priority 200 is
restored, it will become the synchronizer again.
• Declaring the ACT-3 access with priority 200 leads to the creation of synchronization
domain 3, to which the three ACTs belong.
• The Appliance Server remains in a global synchronization domain, in other words domain 0.
• After modification, use the command infocs to check the synchronization plan.
2.2. Example 2
See Figure 3.
− The following system, before migration to Release 6.2:
• One CPU5 in the ACT-0.
• Two peripheral ACTs (ACT-1 and ACT-2) connected to the ACT-0 through INTOF links.
• In the ACT-1 and ACT-2, there is a T2/T1 access connected either to the public network or to
private links. The aim is to synchronize the system first on the public access, then on the
private accesses.
• Priority is managed at "0" on the ACT-0 access (public), priority "1" (private 1) on the ACT-1
access and priority "2" (private 2) on the ACT-2 access (see Figure 3).
− After migration to Release 6.2 with Appliance Server:
• The CPU5 is replaced by an Appliance Server. An INTIP2 is put in place of the CPU5.
• The ACT-0 is moved to ACT-3 (first free ACT).
• The ACT-3 is now an ACT-IP. It should belong to a synchronization domain.
• In order to renew the synchronization plan, the public access takes priority 200, private
accesses 1 and 2 go to priority 201 and 202, or 201 and 201 if they come from the same
synchronization source.
• Declaring the ACT-3 access with priority 200 leads to the creation of synchronization
domain 3, to which the three ACTs belong.
• The Appliance Server remains in a global synchronization domain, in other words domain 0.
• After modification, use the command infocs to check the synchronization plan.
TC0711 2 Ed. 01 / 14 October 2005

OmniPCX Enterprise
2.3. Example 3
See Figure 4.
Specific case where the highest level ACT has no synchronizing access (see Figure 4).
If there is no synchronizing access in the highest level ACT, an access will need to be created on a
fictitious coupler with priority 200. This access can be created on a coupler which is not physically
present. The position left available by the IO2 coupler can be used.
After modification, use the command infocs to check the synchronization plan.
Synchronization Appliance server

domain 0
CPU INTIP-B
ACT0 T2 Priority=0 T2 Priority=200

ACT3
Synchronization
Synchronization
domain 3
domain 0 ACT2 T2 Priority=0
ACT2 T2 Priority=202
ACT1 T2 Priority=0
R6.2 migration
Figure 1: Configuration after migration to return part of the initial configuration

In this example, the ACT-3 access is the synchronizer and the two others are potential synchronizers.
If the ACT-3 access breaks down, the ACT-1 access becomes the synchronizer, but if the ACT-3
access is restored, the synchronization will return to this access, unlike with the configuration before
migration.
Ed. 01 / 14 October 2005 3 TC0711

OmniPCX Enterprise
Synchronization
Appliance server
domain 0
CPU
ACT0 T2 Priority=0
Synchronization INTIP-B
Synchronization domain 3
domain 0 ACT2 T2 Priority=0 ACT3 T2 Priority=200
ACT1 T2 Priority=0
Synchronization ACT2
domain 2 T2 Priority=200
Synchronization T2 Priority=200
ACT1
domain 1
R6.2 migration
Figure 2: Configuration after migration does not allow a return to the initial configuration
Management of the three accesses with priority 200 in effect creates three separate synchronization
domains. If one access breaks down, the ACT that it was synchronizing will not be backed up by the
other accesses. The ACT will be in "free running".
TC0711 4 Ed. 01 / 14 October 2005

OmniPCX Enterprise
Synchronization
Appliance Server
domain 0
CPU INTIP-B
ACT0 T2 Priority=0 ACT3 T2 Priority=200

Synchronization
domain 3
Synchronization
T2 Priority=1 ACT1 T2 Priority=201

ACT1
R6.2 migration
Figure 3: Configuration of the synchronization after migration respecting the configuration

before migration
Ed. 01 / 14 October 2005 5 TC0711

OmniPCX Enterprise
Synchronization
Appliance Server
domain 0
CPU INTIP-B
Fictitious T2
ACT0 ACT3
Priority=200
Synchronization
domain 3
Synchronization
T2 Priority=0 ACT1 T2 Priority=201

ACT1
R6.2 migration
Figure 4
In this example, after migration to R6.2, since the ACT-3 does not have a synchronizing access, an
access needs to be created on a fictitious synchronizing coupler with priority 200. This will allow a
return to the same topology as before. Without this configuration, the ACT-3 would belong to the
synchronization domain 0 and would be in "free running".
TC0711 6 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2 NEW FEATURES IN PREVIOUS RELEASES
NEW FEATURES IN PREVIOUS RELEASES
CONTENTS
1. NEW HARDWARE IN RELEASES 5.1, 5.1.1, 5.1.2, 6.0.1, 6.1, 6.1.13
2. NEW FEATURES IN RELEASES 5.1, 5.1.1, 5.1.2, 6.0.1, 6.1, 6.1.1 ..6
3. NEW SERVICES ON INTIP COMPARED TO RELEASE 5.0.1 UX .....14

3.1 Reminder of Release 5.1 ......................................................................... 14
3.2 Reminder of Release 4.2 ......................................................................... 14
3.2.1 ABC-F2 on IP with INTIP .................................................................................14
3.2.2 H323 gateway ................................................................................................14
3.2.3 Compatibility with external gatekeeper ..........................................................14
3.2.4 H323 inter-node calls .....................................................................................15
3.2.5 Fast start .........................................................................................................15
3.2.6 Marking of signaling on VoIP..........................................................................15
3.2.7 T38 .................................................................................................................15
3.2.8 IP redundancy.................................................................................................16
3.2.9 100 MB Full Duplex.........................................................................................16
3.2.10 New IP Booleans .........................................................................................16
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
NEW FEATURES IN PREVIOUS RELEASES F3.301.10 – RELEASE 6.2
TC0711 2 Ed. 01 / 14 October 2005

OmniPCX Enterprise
1. NEW HARDWARE IN RELEASES 5.1, 5.1.1, 5.1.2, 6.0.1, 6.1, 6.1.1

The main hardware appeared from Release 5.1 is detailed below. For more information, please
refer to the System documentation.
Release Boards Reference Remarks Compatibility

CPU6 3BA 23197 BAEBRequires 128 MB SDRAM (Reference 3EH
75011 AA).
GPA2 3BA 23241 AA Allows to deal with the obsolescence of the
flash card for the vocal guides. It replaces
the GPA board both for the voice guides
and for the conference as of Release 5.0
Ux. Cohabitation with GPA board remains
authorized.
NPRAE 3BA 23254 AAAB 04 Allows to deal with the obsolescence of the The board is not
PRA2 board. The PCM function as well as compatible with Releases
DPNSS and DASS2 protocols are not below 5.1.
supported by NPRAE board. In these
cases, Actis continues to manage PRA2
boards.
INTIP2 3BA 23193 ACAF 03 Allows to deal with the obsolescence of the The board is not
INTIP coupler. It offers the same features compatible with Releases
5.1
as the INTIP coupler. The V24 cable to be below 5.1.
used is the same as that of the CS, GD or
GA boards (Reference 3EH 75003 AAAA).
The cable of INTIP (Reference 3BA 28112)
can no longer be used.
eUA32 3BA 23266 AAAA This board was designed to separate the The board is not
hardware and associated software compatible with Releases
licenses. There is no difference of features below 5.1.
between eUA32 and UA32 boards.
eZ32 3BA 23265 AAAA This board was designed to separate the The board is not
hardware and associated software compatible with Releases
licenses. There is no difference of features below 5.1.
between eZ32and Z32 boards.
SLI 4-1 3EH 73052 ADAB Replace the SLI 4/8/16 boards. The board is not
SLI 8-1 3EH 73052 ACAB compatible with Releases
SLI 16-1 3EH 73052 ABAB below 5.1.
PCM-R2 3EH 73007 ADAB This board takes the PCM-R2 signaling
5.1.1
into account in common hardware.
CLIDSP 3EH 73034 ABAB This board is used to manage the CLIP on
APA. Feature available only for USA and
China.
5.1.2 New 1U and 3EH 76020 AE 1U and 3U racks with
3U racks for external batteries are not
external 3EH 76027 AE or BE compatible with Releases
batteries below 5.1.2.
Ed. 01 / 14 October 2005 3 TC0711

OmniPCX Enterprise

Alcatel series 8 IP Touch 40x8 2 types of sets: 4038 and 4068 Sets not compatible with
sets previous releases
Appliance 3BA 27582 AB AS X306 must only be ordered by Compatible with Releases
Server IBM Alcatel to update the Bios. An AS X306 5.1.2 and 6.0
X306 can be duplicated of an X305
CPU7 256 MB CPU7:3BA 23259 AA Replace the CPU5 Step3 board. Not compatible with
256 MB RAM: Hard keys are not supported by CPU7 previous Releases.
3BA 23259 AA
GIP4x GIP4-1 board (1 DSP) GIP4-4 and GIP4-1 daughter boards will You cannot mix old and
3BA 23264 AAAB respectively replace GIP6 and GIP6a new daughter boards on
GIP4-4 board (4 DSP) boards on INTIP/INTIP2 boards a same INTIP/INTIP2
3BA 23263 AAAB Ö 8 compressors per DSP whatever the board.
echo delay and the algorithm used In a same installation, you
Ö Allows to deal with an echo delay up to can mix old and new
64 ms daughter boards.
GIP4 boards are not
compatible with Releases
below 6.0.
MADAx MADA 1 board (1 MADA-1 and MADA-4 daughter boards In a same installation, you
DSP): 3EU 23013 AA will respectively replace MCV-1 and MCV- can mix old and new
MADA 3 board (3 4 daughter boards on GD and GA boards daughter boards.
6.0.1 DSP): 3EU 23012 AA Ö 8 compressors per DSP whatever the MADA boards are not
echo delay and the algorithm used compatible with Releases
Ö Allows to deal with an echo delay up to below 6.0
64 ms
-48V 1U and 1U rack: Requires to be powered by -51V minimum
3U racks for 3EH 76172 AA
external 3U rack:
battery 3EH 76170 AA
DDI DDI2 board: DDI2 et DDI4 boards are used to connect DDI boards are not
3EH 73036 AC 2 or 4 DDI analog lines (Direct Dialing compatible with Releases
DDI4 board: Inward) below 6.0.
3EH 73036 AB
MIX Osiris 3EH 73015 ABAE 02 MIX Legerity 4T0/8UA/4Z Compatible from Release
Legerity 3EH 73015 ACAE 02 MIX Legerity 4T0/4UA/8Z 5.1.2.
3EH 73015 ADAE 02 MIX Legerity 2T0/4UA/4Z
3EH 73015 AEAE 02 MIX Legerity 0T0/8UA/4Z
3EH 73015 AFAE 02 MIX Legerity 0T0/4UA/8Z
3EH 73015 AGAE 02 MIX Legerity 0T0/4UA/4Z
LANX-2 LANX8-2: Replace LANX-1 boards Compatible from Release
3EH 73054 AC Ö LANX8-2: 7 ports 10/100BaseT + 1 5.1.2.
LANX16-2: port 10/100/1000BaseT
3EH 73054 AB Ö LANX16-2: 14 ports 10/100BaseT + 2
ports 10/100/1000BaseT
Alcatel series 9 IP Touch 40x9 2 types of sets: 4029 and 4039 Sets not compatible with
6.1
sets previous releases.
TC0711 4 Ed. 01 / 14 October 2005

OmniPCX Enterprise

INTOF2 3BA 23260 AAAB The INTOF2 board replaces the INTOF The INTOF boards are
board due to the obsolescence of always compatible in
components. R6.1.x.
The mixing of various generation boards is
allowed in a same rack but:
− the couplers in relation to the link must
be of the same type
− the type of INTOF must be of the same
type if the link is doubled or tripled
− In Campus mode:
• Actis continues to configure
INTOFS boards,
• INTOFS2 boards are not allowed.
Moreover, INTOF2 allows to connect the
main ACT and ACT-CH8 via HSL link. In
that case, the INTOF2 will be managed as
INTGD board.
Add-on As of Release 6.1, a new type of Add-on Not compatible with
Module module is available. It is composed of a previous releases.
LCD display type, on which on the level of
each of the 14 keys, an icon or a
mnemonics (14 characters maximum) can
be displayed.
It is available ONLY on 4028-4038-
4068-4029-4039 sets.
You can connect up to 3 Electronic Add-
On modules. These modules cannot be
mixed with the other types of Add-on
modules.
Alcatel series 9 IP Touch 4019 1 type of set: 4019 Sets not compatible with
Alcatel series 8 IP Touch 4018 1 type of set: 4018 Sets not compatible with
6.1.1
UPS on USB Not compatible with
previous releases.
Ed. 01 / 14 October 2005 5 TC0711

OmniPCX Enterprise
2. NEW FEATURES IN RELEASES 5.1, 5.1.1, 5.1.2, 6.0.1, 6.1, 6.1.1

The features appeared from Release 5.1 are detailed below. For more information, please refer to
the System documentation.
Release Features Description

CLIP Z32/eZ32 CLIP allows the calling line identification to be displayed,
whatever the origin of the call (internal, ABC-F network,
external)
The CLIP feature on Z32/eZ32:
− is only available with a Crystal IP Media Gateway,
− supports ETSI and Bellcore protocols (complies with
ETSI 300569 -1/2 and with Bellcore TRNWT000030),
− is only valid in on-hook mode
The functionality is only released in five countries (USA,
China, Pakistan, Hong-Kong and Taiwan)
Remote Extension (cellular client) This feature allows external users to have the same level of
service as internal GAP users
These external sets (fixed set, H323 terminal mobile set
(GSM)) must be capable of generating voice frequencies
(DTMF)
NTP (Network Time Protocol) This feature allows the time setting of the PABXs through
synchronization on an NTP type server. There is therefore
permanent synchronization of all IP equipment which
could be an NTP client
5.1
The NTP server can be external or an OmniPCX Enterprise
CPU
Security As of Release 5.1, several modifications have been made
to simplify and restrict the use of user accounts, such as a
tool (aging password) which limits the validity of the
passwords. It is enabled once it is decided to modify the
passwords
Move licenses This functionality allows a client to move licenses between
two of their machines. In R5.1, only certain licenses can be
moved
IMAP4 (Internet Message Access Protocol In the context of the Alcatel 4645 and 4635 voice mail
version 4) (minimum version 5.1.5), the IMAP service (Internet
Message Access Protocol) allows a user to consult their
voice mail remotely from any PC connected to the Internet.
The IMAP4 service with 4635 and 4645 is possible
through the following e-mail clients:
− Microsoft Outlook 2000/2002 (XP)
− Microsoft Outlook Express 5.5/6.0
− Netscape Mail R7
PCM-R2 This board takes the PCM-R2 signaling into account in
5.1.1
common hardware
Z/PCM
TC0711 6 Ed. 01 / 14 October 2005

OmniPCX Enterprise

IOIP For large systems with Appliance Server and peripheral
ACTs on INTOF, the capacity of the signaling link between
the main and peripheral ACTs may be increased to 4x64
kbps. This signaling mode is called "mode 2", "4x64
mode", or "IO2 mode" (it corresponds to the mode
formerly offered by the IO2 board on OmniPCX 4400).
4x64 mode is obtained via a board referred to as an
"IOIP" board, that controls the main ACT. This board
allows signaling transfer between the Call Server (via the
IP network) and the INTOF A board (via the C1 link) at a
speed of 4x64 kbps. Signaling passes the INTOF A board
transparently to the INTOF B board of the peripheral ACT.
Physically, the IOIP board is an INT-IP (or INT-IP2) board
with no compressor
VPIM 4645 (Voice Processing Internet Allows to connect the voice mail system to other voice mail
Messaging) systems (Alcatel or other manufacturer) through the IP
network
Creation of eZ, eUA or IP Phone sets even if As of Release 5.1.1, you can create a eZ, eUA or IP Phone
their corresponding software lock is to 0 set even if their corresponding software lock is to 0. Refer
to the technical communication TC0528 Create an eZ,
eUA or IP Phone set without buying the corresponding
licenses
Connection of the GD to CS instead of There is a system parameter which makes it possible to
INTIPA connect GD to the CPU (via the IP-Link) and either to the
INTIPA to avoid to have more than 3 levels of crystal (the
limit is 3 levels)
CLIP APA/ NDDI2 (Calling Line Identification The CLIP feature (Calling Line Identification Protocol)
Protocol) operates on:
− APA board: for USA and China
− NDDI2 board: add of China from Release 6.0
It does not operates with T1-CAS boards
CLIDSP daughter board : 3EH 73034 ABAB
Starter Pack 4645 The starter Pack 4645 makes it possible to integrate in the
6.0.1
system, a free 4645 package with a basic configuration:
− 30 users
− One language
− 2 hours of storage
MG configuration without reboot This exploitation makes it possible to modify the T2
accesses of an IP trunk group without rebooting the GD
board
Ed. 01 / 14 October 2005 7 TC0711

OmniPCX Enterprise

G72940 ms Management of a 40 ms framing if the algorithm used is
G729
This feature is useful in the case of network of narrow
band-width. On the other hand, its installation must be
carried out with prudence. Indeed, the lengthening of the
6.0.1 sending framing over IP involves two consequences on the
voice:
− an increase of the time from beginning to end
− any loss of package means that larger quantity of
information is lost, involving a faster degradation of
the voice
N x N party conference on MCV or MADA N party conference can be managed on MCV and MADA
boards of GD and GA boards.
The N party conference feature cannot be managed on:
− S0 sets
− Attendant sets
MEA (Multiline Extension Agent) This feature is used to multiline sets to be CCD agents
Call completion on busy trunk group The Call completion on busy trunk group feature makes it
possible to the user, when all the trunk groups are busy, to
require an automatic callback as soon as a trunk is
released
The call completion on busy trunk group feature is
proposed on the types of following trunk groups:
− Analog trunk groups
− ISDN and GF trunk groups
− ABC-F trunk groups (Private)
Restrictions
− Feature not available on S0 and attendant sets
− Operates only in overlap mode
− Operates with ARS if the trunk group is local
6.0.1 − Does not operate on shared trunk group
Call Completion on busy trunk group can be enabled or
disabled with the parameter Auto. call back
satell.trk.grp (Categories / Phone Facilities
Categories)
Value 1 => Call Completion on busy trunk group is
enabled on the set
Value 0 => Call Completion on busy trunk group is
disabled on the set
Blind Transfer from Voice Mail In a configuration with automated attendant, an incoming
call can be transferred locally or network without
supervision. The interest is to release the resources of the
mailbox as of the realization of the transfer. Moreover, this
feature makes it possible the call to follow the status of the
called set
This feature is available on Alcatel 4635 or 4645 voice
mail systems
UDP port management With netadmin, it is possible to decrease the range of
dynamic ports opened on the level of Call Server,
therefore also on the level of Firewalls
TC0711 8 Ed. 01 / 14 October 2005

OmniPCX Enterprise

Security SSH/SSL PABX The dialog between network machines can be done in
quantified way. To do that, the system uses OpenSSL and
OpenSSH.
6.0.1 Echo Cancellation 64 ms The echo delay is not any more a configurable parameter
but depends on the hardware type of compression board:
− 64 ms with GIP4–1/4 and MADA1/MADA3 boards
− 32 ms with GIP6 and MCVx boards
Private to public overflow In Release 6.0, the calls were impossible if the IP domain
were saturated. Moreover, on loss of IP link and within
"Signaling Link Backup" feature, the calls from backup
Media Gateway were limited to IP domain of this Media
Gateway.
As of Release 6.1, the overflow of a call between domains,
towards switching network is obtained on:
6.1
− saturation of IP domains,
− saturation of compression resources,
− loss of IP link between CS and GD.
This feature uses the principle of private-public overflow in
network i.e. an inaccessible local call makes an outgoing
call on the switching network for DDI number of the set
called in the beginning.
Ed. 01 / 14 October 2005 9 TC0711

OmniPCX Enterprise

Both CPU in two different subnets The "Both CPU in two different subnets" feature makes it
possible two CPU to be in two different subnetworks.
This feature is available on AS and CS.
This feature is supported by following IP equipment:
− SIP sets,
− Alcatel series 8 sets (4028-4038-4068),
− GD,
− GA,
− INTIP,
− IOIP.
The applications able to take into account 2 addresses of
CPU are:
• Alcatel 4635 (R5.2.6)
• Alcatel 4645
• OmniVista 4760i / 4760 (R3.1)
• OmniTouch Contact Center : CCD/CCS (R6.1.90)
• XML Web services
• Application "XML IP Touch"
• TSAPI
• ACAPI V2.1
• VoWLAN R1.1
Restrictions
− No V1 (4080 RE) - V1S (4080 FRE) - V2 (e-Reflexe IP
Phone V2) sets. Only the IP sets of series 8 and SIP sets
are able to take into account 2 addresses of CPU.
− No Genesys applications (CCemail, CCoutbound,
CCivr, CCa, CCweb).
− No RSI Synchro Server.
− No TAPI.
− No OmniTouch Unified Communication.
− If a R6.1.1 node is added in a network with nodes less
than R6.0, it is essential to continue to use the
addressing by role in case of logical links over IP (the
nodes below R6.0 cannot establish logical links
towards two different addresses).
− If an external DHCP server is used, a tftp server must
also be used.
− Audit and broadcast must be performed via IP/X25
and not directly via IP.
500 512
1000 512
2500 1280
5000 2560
TC0711 10 Ed. 01 / 14 October 2005

OmniPCX Enterprise

Management of MOXA box MOXA box is used to increase the number of serial ports
of OmnipCX Enterprise. The aim of this Release 6.1
feature is to make easier the configuration of serial ports
of the box: single management of information in mgr
instead of two distinct programs (mgr and npadm).
The firmware version of Moxa box must be 3.0 or
higher.
Management
• System / Go down hierarchy / Remote
V24 box
• System / Go down hierarchy / V24
Port
Naming of H323 Gateway This feature is used to identify by a name each Gateway
Media. This identifier is used during the recording of the
Gateway Media at Gatekeeper (RAS message). On each
modification of this field, a manual reset of the Gateway
Media is necessary.
By default in R6.1, the identification is GW_CR_CPL_IP@.
The management must be carried in the Ethernet
parameters of INTIP/GD/GA board.
Licenses installation without reboot This feature is used to inform the Business Partner if a
reboot is required or not after installing licenses.
HTTPS The security of HTTP flows completes the offer already
carried out by the introduction of the SSH in R6.0. Until
now, the interface with the Web applications was done
without any encoding on the exchanges of HTTP packets.
From Release 6.1, SSL protocol ensures encoding between
the customer sessions and the Web server of CS. The
topology of the network must authorize the transit of this
type of specific exchanges.
In order to ensure a compatibility with external
applications not supporting yet SSL protocol and wishing
to access resources of the Web server of CS, the whole of
the data is accessible both through a secured connection
(via port HTTPS) and also by a not encoded traditional
connection (port HTTP by default). This feature is
supported by the most of the browsers. In this case, one
uses the https:// prefix at the beginning of the URL
(Uniform Resource Locator) in the browser bar.
This activation/desactivation is obtained via netadmin
with the new heading Security/SSL configuration.
Ed. 01 / 14 October 2005 11 TC0711

OmniPCX Enterprise

Ergonomic improvements for Alcatel series 8 Management of the message LED (series 8 & 9)
& 9 sets Cyclic Home Bar (series 8 & 9)
Remove of unanswered calls with an icon
New management of the forwarding icon
Phone book : Complete display of Name/First Name
New functioning of the Global LED
No erasing of unanswered calls after answered call-back
Multiple Redial List
CBN (Call By Name): Display of the name without number
(series 8 & 9)
Multiple Redial List Each user can store the 8 last numbers called (local or
external). Long press the Redial key to view this list and to
call-back.
This feature is available for every Alcatel series 8 & 9 sets
as well as Reflexes sets .
This feature already exists for mobiles 100&200 Reflexes,
Alcatel 4048/4049 /4059 attendants.
Restrictions
• No multiple Redial list with 4035 attendants.
• No save of the name of a local or networked call
(homogeneous) in the following cases:
♦ Prefix of entity call.
♦ Attendant call.
♦ Call of an abbreviated number.
• Only available on sets:
♦ MR2 3G (4035, 4036, 4037).
♦ 3G (4020, 4021, 4022).
♦ IP Touch B, C, D.
• No update of the list of calls sent by the Stand-By.
• On each RUNTEL or reset of set, the list of sent
calls is initialized.
• No save on the disk.
Management : Specific Telephone Services
• Redial list on UA set: Yes/No
• Internal call:
♦ No : only external calls are stored
♦ Yes : internal and external calls are stored
Serial numbers on Alcatel series 8 sets This feature is available only on the series 8 sets. Using
the tool getnoeversion , it is used to provide
information about series 8 sets such as:
− the serial number
− the hardware version
− the software version
Programmable keys From Release 6.1, 74 programmable keys are available
(72 via the Perso tab of the set and 2 via F1 and F2
keys). For reminder, in Release 6.0, 40 programmable
keys were available (via the Perso tab of the set).
TC0711 12 Ed. 01 / 14 October 2005

OmniPCX Enterprise

CLIP on NDDI2 and APA − CLIP Bellcore on APA.
• CLIP on APA line (CLIDSP daughter board - 3EH
73034 AB) is available for all markets from
Release 6.1.
− CLIP Bellcore on NDDI2.
CLIP on NDDI2 is available for all markets from
Release 6.1.
Cyrillic From Release 6.1.1, the Cyrillic is implemented on Alcatel
6.1.1
series 8 & 9 sets.
DPNSS/DASS2 over NPRAE From Release 6.1.1, the NPRAE board (1) is able to
provide one DPNSS access or one DASS2 access. Only the
access 0 is available.
Then, the NPRAE board can provide either:
− 2 E1–CCS (T2) accesses
− 1 DASS2 access (as of R6.1.1)
− 1 DPNSS access (as of R6.1.1)
(1) As of binary dpnssnv 1.5.
New icons of supervisions From Release 6.1.1, new icons are available for
supervised status.
Private to public overflow From Release 6.1.1, private to public overflow is subject to
the same checks (through Phone Facilities category) as
private to public overflow in network.
• If the domain is saturated or if there is a lack of
compressors, the overflow is performed only if the
user has Busy priv. to public overfl.
= Yes in his Phone Facilities category.
• If the IP network is out of service (therefore MG in
backup), the overflow is performed only if the user
has O/S private to_public overflow =
Yes in his Phone Facilities category.
Remarks
• The sets of an inaccessible domain must be
accessible in DDI.
• It is required to have at least one public access for
each domain.
• All the phone services are lost when
changing from a local call towards a public
call.
Access path
• Categories/Phone Facilities
Categories/private to public
overflow on link out of service
• Translator/External Numbering Plan/Node access
Prefix: Management to be carried out on the local
node.
All local features are lost when passing from local
call to public call.
Ed. 01 / 14 October 2005 13 TC0711

OmniPCX Enterprise
3. NEW SERVICES ON INTIP COMPARED TO RELEASE 5.0.1 Ux

The term INTIPB concerns INTIP boards as well as INTIP2.
3.1 Reminder of Release 5.1
− From Release 5.1, the INTIP board supports Direct RTP in network.
− The Voipstat command is no more used.
3.2 Reminder of Release 4.2
3.2.1 ABC-F2 on IP with INTIP

Through the GIP6 and GIP4-4 boards, a maximum of 60 compressors can be used for a VoIP link.
3.2.2 H323 gateway

Faced with call back problems on OmniPCX 4400 sets which are not on the same node, set the
parameters of the Send Alert message on Cisco.
With Cisco, the Round Trip Delay Request Boolean must be set to No if it is not taken into
account by Cisco.
Cisco and MP104 type gateways do not accept numbering by overlap on reception.
The main case is the use of incomplete abbreviated numbering + prefix for professional bundle
selection with overlap.
Solution
• ARS + overlap.
• Set the parameter of the Direct Numbering By Overlap system Boolean to No.
• Manage Number of digits according to the IP bundle discrimination rules.
3.2.3 Compatibility with external gatekeeper

− Compatibility with Cisco 3620 (IOS 12.2(2)T).
Any modification of a gatekeeper parameter, a gatekeeper number or operation with a
gatekeeper requires the gateway concerned to be reset.
It is possible to make a VoIP call by directly dialing the prefix of the IP bundle or the ARS prefix
with QMCDU.
Without using the abbreviated number.
The translation of E164 numbers in the gatekeeper IP address must be managed dynamically to
avoid numbering by overlap which is not taken into account on reception.
− Compatibility with Alcatel CID: 2.2.43.
TC0711 14 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3.2.4 H323 inter-node calls

Using the H323v2 protocol for operation with gatekeeper and on OmniPCX VoIP gateway.
This parameter must be managed in the same way on each node.
Attention, in this case, the Internodes com GK unreachable system Boolean should be set to
Yes, especially if the gatekeeper controls the passband.
Otherwise, after loss of the IP link between the gatekeeper and INTIP, the release of the calls set up
is not seen immediately by the gatekeeper.
The busy state of the passband can prevent new calls.
Refer to the technical communication TC0545 Problems of VPN over IP.
3.2.5 Fast start

Interworking with Office 4200 is not taken into account by Office 4200.
Capacity to return to the remote operation mode.
3.2.6 Marking of signaling on VoIP

− Local VLAN ID management (used for voice).
Its value is sent to the INTIP board.
− ToS (Type of Service) for inter-node link (signaling used between CPUs):
IP TOS SIG Hybrid value set to True.
3.2.7 T38
T38 fax compatibility is taken into account thanks to the Audiocode module MP102.
In G711, the Enhanced Voice Quality Boolean, called Frame VoIP as from R5.1, must be
set to Yes to avoid audio quality problems. In general, Audiocode requests an inter-frame delay.
If the displaying of CNIP/CNAM is managed, the following displays are obtained:
− MP102 call to 4400: Audiocod Gateway Application
− 4400 call to MP102: GW Test Application.
If the displaying of CNIP/CNAM is not managed, the name for outgoing calls is still displayed,
although it should not be.
T38 is available with Fast start or with the normal procedure.
The fax transmission speed is limited to 9600 b/s.
It is essential to have an integral INTIP network in Release 4.2 to make it easier to use these new
functionalities.
Refer to the technical communication TC0336 Setting the T38 fax over IP application (with MP-102
version 4.0).
Ed. 01 / 14 October 2005 15 TC0711

OmniPCX Enterprise
3.2.8 IP redundancy
The CPUs should be duplicated and be connected to the different data switches belonging to a
single IP network.
New timers linked to this operation:
− Ping frequency: 20 s (default value).
This corresponds to the value between two pings.
− Ethernet state control frequency: 3.
This value is a multiple of Tping corresponding to two Ethernet frame counter checks.
3.2.9 100 MB Full Duplex

Through the Full Duplex parameter, a specific mode can be managed by INTIPA board
depending on the configuration of the switch autonegotiation.
Access path: Shelf/Boards/Ethernet Parameters/Full duplex
Full Duplex: No (by default) (forcing of half duplex mode).
Full Duplex: Yes (authorization for the INTIP board to work in full duplex).
The connection speed is chosen automatically (negotiation between the two elements).
Any modification of this value requires the INTIP board to be reset.
INTIPA and INTIPB can be configured in full duplex and half duplex. The INTIPB board is managed
in static mode via the cable on the front face and not via management.
If the switch and the INTIP are configured in Autonegotiation mode, both ends are in full duplex.
Autonegotiation is an automatic selection mechanism to obtain the best operation supported by both
the switch and the INTIP board.
Management control:
Cmdcpl <cr> <cpl> MNGT (displays management information)
The following are displayed:
• The configured Boolean.
• The mode and speed of transmission.
3.2.10 New IP Booleans

− Round trip delay request (as of Release 4.2):
Access path: System/IP Parameters
This prevents the sending of messages to a remote H323 termination which can not answer. If
the parameter is enabled while the remote termination can not answer, the call is cut off after
approximately 40 seconds.
− Framing VoIP (previously "Enhanced Voice Quality" (as of Release 4.2)):
Access path: IP/IP Parameters
This parameter depends on the algorithm used:
• G711 : 20 or 30 ms
TC0711 16 Ed. 01 / 14 October 2005

OmniPCX Enterprise
• G729 : 20-30 or 40 ms
• G723 : 30 ms
CAUTION
This value must be identical on all nodes.
Ed. 01 / 14 October 2005 17 TC0711

OmniPCX Enterprise
TC0711 18 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 – RELEASE 6.2 NEW FEATURES
NEW FEATURES
CONTENTS
1. ARCHITECTURE AND CAPACITIES................................................5
2. NEW HARDWARE IN RELEASE 6.2................................................7

2.1 IP Touch Security Modules : SSM, MSM ..................................................... 7
2.1.1 IP Touch Security Module description................................................................7
2.2 Implementation of ACT shelf in 19" cabinet .............................................. 8
2.3 Phase out boards ...................................................................................... 9
3. NEW FEATURES IN RELEASE 6.2 ................................................10

3.1 Chinese characters on IP Touch Series 8 & 9........................................... 10
3.2 Compatibility of IP Touch Series 8 & 9 in Hotel/Hospital configuration ... 10
3.3 IP configuration of IP Touch series 8 sets ................................................ 10
3.4 New developments for SIP interworking ................................................. 10
3.4.1 Compatibility of RFC 3842 ..............................................................................10
3.4.2 Compatibility of Thomson ST2020 SIP set .......................................................11
3.5 IP Touch Security Service......................................................................... 11
3.5.1 Overview ........................................................................................................11
3.5.2 Security Policy for the binaries of the Secured IP Touch sets............................13
3.6 IP Touch survivability .............................................................................. 15
3.6.1 Reminder on GD backup signaling link in R6.1...............................................15
3.6.2 IP Touch survivability description ....................................................................15
3.7 New icons of supervisions ...................................................................... 17
3.7.1 Conventions....................................................................................................17
3.7.2 Redial memory ...............................................................................................18
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
NEW FEATURES F3.301.10 – RELEASE 6.2
3.7.3 Boss/Assistant .................................................................................................18

3.7.4 Supervision .....................................................................................................20
3.7.5 Multiline .........................................................................................................22
3.8 Different ringing for secondary MLA set.................................................. 23
3.9 Dial by name with overflow on LDAP server ........................................... 23
3.10 Product Limits and network interworking................................................ 23
3.10.1 IP Domains ..................................................................................................23
3.10.2 Entities.........................................................................................................23
3.10.3 Nodes of an IP homogeneous network........................................................24
3.10.4 Interworking in network ..............................................................................24
3.11 Security enhancements of the system...................................................... 24
3.11.1 Security by default of the system after installation .......................................24
3.11.2 Sending of SYSLOG messages towards an external server ..........................25
3.11.3 Complete command history.........................................................................25
3.11.4 Community name for SNMP ........................................................................25
3.11.5 Enhancement of User’s account menu .........................................................26
3.11.6 Alarm on logging failure .............................................................................26
3.12 New features for the public network....................................................... 26
3.12.1 R1.5 protocol ...............................................................................................26
3.12.2 CLIP on APA ................................................................................................26
3.12.3 NDDI2 board for the Australian market ......................................................26
3.13 Dynamic initialization of SLI board ......................................................... 26
3.14 Ethernet Duplication on CPU7 ................................................................ 27
3.15 Specific developments offered in Release 6.2 ......................................... 27
3.15.1 IP Attendant Softphone and IP CCAgent Softphone .....................................28
3.15.2 Free Desktop application .............................................................................29
3.16 Statistic tickets over IP ............................................................................. 29
3.17 Both CPU in two different subnets........................................................... 29
3.18 Modem, Fax, Data transparency over IP.................................................. 31
3.19 XML IP Touch .......................................................................................... 31
4. FEATURES UNDER PCS (PREMIUM CUSTOMER SUPPORT)...........32
TC0711 2 Ed. 01 / 14 October 2005

OmniPCX Enterprise
4.1 Common Hardware IRAD board ............................................................. 32
Ed. 01 / 14 October 2005 3 TC0711

OmniPCX Enterprise
TC0711 4 Ed. 01 / 14 October 2005

OmniPCX Enterprise
1. ARCHITECTURE AND CAPACITIES

Consult the Marketing documentation available on the BPWS (Our Offer > Products > Alcatel
OmniPCX Enterprise > select In Depth Product Insight > English Language > OK > Release 6.2).
REMINDER
The main features included in previous releases are detailed in Appendix 5.
New hardware and features from Release 6.2:
New hardware New features Features under PCS (1)

IP Touch Security Modules Chinese characters on IP Touch IRAD board (2)
(SSM, MSM) series 8 & 9 sets (500 characters)
Installation of ACT shelves in Alcatel series 8 & 9 sets in Hotel
computer cabinets function
Support of Thomson ST2020 SIP
phone
IP Touch Security Solution – Voice
encryption
IP Touch Survivability
New icon of supervision of a
forwarded set
MLA / Private line ringer
differentiation
LDAP Call by name display on
2x30 characters
1000 Domains IP / 1000 Entities
Security improvement (system)
Transit R1.5- Russian market
CLIP DTMF on APA (India, Taiwan)
NDDI2 for Australian market
Dynamic coupler initialization for
SLI
Duplication over Ethernet for CPU7
IP Attendant Softphone
Free Desktop
Statistic tickets over IP
Both CPU in two different subnets
Modem, Fax, Data transparency
over IP
XML IP Touch
Ed. 01 / 14 October 2005 5 TC0711

OmniPCX Enterprise
Hardware not released Feature not released

ACT-CH8
RGD
ECAN 64ms for USA
(1) Premium Customer Support.

The Premium Customer Support process allows the Partner Businesses to profit an assistance on
features or products whose marketing was announced (DR3) but which are not launched yet on
the market. The PCS process replaces the SDP (Specific Deal Process) previous process; refer to
the eFlash EF_Marketing_003_260704.
(2) Available with OmniVista 4760 R3.2.
TC0711 6 Ed. 01 / 14 October 2005

OmniPCX Enterprise
2. NEW HARDWARE IN RELEASE 6.2
2.1 IP Touch Security Modules : SSM, MSM

SSM : Server Security Module
MSM : Media Security Module
2.1.1 IP Touch Security Module description

The IP Touch Security Modules (SSM or MSM) are encryption units for IP networks. They are
positioned at the front-end of:
− Com Server for the SSM
− the Media Gateways (Common Hardware and Crystal Hardware) application servers for the
MSM
The IP Touch Security Modules are fitted:
− With a console port (RS232) which is used to set up a V24 serial link with a management console
− With two Ethernet ports (RJ45 10/100 base TX) with:
• an uncoded (plain) port (symbolized by an open padlock) on which the IP equipment to be
secured (Com Server or Media Gateway) is connected
• an encoded (cipher) port (symbolized by a closed padlock) on which the IP network is
connected (via a Hub or Switch)
− A button to return the security module to the initial state (factory output values)
− An external power supply connector (220V)
− An IP Touch Security Module status indicator (LED "STATUS")
− A power on indicator (LED "ON")
− An Ethernet link status indicator
− A power supply switch
Ed. 01 / 14 October 2005 7 TC0711

OmniPCX Enterprise
IP Touch Security Module –

Secured Unit Status Indicator
The IP Touch Security Modules can be identified by a label on the rear panel. This label indicates the
type: SSM or MSM.
For more information, refer to the System documentation.
2.2 Implementation of ACT shelf in 19" cabinet

In addition to the use of the M2 and M3 cabinets, the ACT shelf 14 and 28 positions can be installed
in standard 19" data cabinet with the format 38U or 4Ù.
The ACT shelf 14 and 28 positions can thus cohabit with the other data systems (switch, router, etc.)
in the same environment.
For each type of ACT shelf (14 or 28 positions), a assembly kit is provided to allow their installation
in 19" data cabinet.
Alcatel does not provide 19" data cabinet. They must be ordered separately by the Partner Business
by taking into account of the following points:
− the OmniPCX Enterprise ACT shelves must be installed in 19" data cabinet closed and equipped
with fans
− the 19" data cabinets will have to meet same standards CEM and of safety than OmniPCX
Enterprise ACT:
• EMC: EN55022 :1998-EN55024: 1998/FCC part15
• Safety EN60950 :2000/IEC 60950 ed03/CSA/UL certification
− The configurations authorized in cabinets with the format 38U and 4Ù are:
2 ACT shelves 28 positions or 4 ACT shelves 14 positions
TC0711 8 Ed. 01 / 14 October 2005

OmniPCX Enterprise
The various elements necessary to the installation of the ACT in 19" data cabinet are:
• PSAL & 48V Data Cabinet Connecting Kit 3BA27121AAAA
• Variable Speed Fans Data Cabinet Kit 3BA27132AAAA
• ACT 28 Data Cabinet Mounting Kit 3BA27118AAAA
• ACT 14 DATA Cabinet Mounting Kit 3BA27119AAAA
For more information regarding the recommendations of installation and the constraints of thermal
dissipation, refer to System documentation.
2.3 Phase out boards

In Release 6.2, several boards are in phase out.
For more information refer to phase out documention on BPWS.
Ed. 01 / 14 October 2005 9 TC0711

OmniPCX Enterprise
3. NEW FEATURES IN RELEASE 6.2
3.1 Chinese characters on IP Touch Series 8 & 9

IP Touch Series 8 & 9 sets make it possible to use the Chinese language on 500 characters
maximum.
This first stage will be supplemented by following in next the releases bringing the number of
characters to 20 000.
3.2 Compatibility of IP Touch Series 8 & 9 in Hotel/Hospital configuration

IP Touch Series 8 & 9 sets are entirely compatible with any Hotel or Hospital configuration.
IP Touch Series 8 & 9 sets can be used for the following functions:
• Room based management
• Guest based management (GPIN)
• Room service set
• Booth set
• Administrative set
For more information on the different set displays as well as the function keys of various IP Touch
Series 8 & 9 sets used in a Hotel/Hospital configuration, refer to System documentation.
3.3 IP configuration of IP Touch series 8 sets

The IP configuration on IP Touch series 8 sets can be locked by a password (common for the
installation).
Management
Alcatel 8&9 Series / IP Touch sets generic Parameters : Noe password
3.4 New developments for SIP interworking
3.4.1 Compatibility of RFC 3842
"SIP Message Waiting Indication" (MWI) feature of preceding releases was based on a provisional
standard of the IETF which became now a standard RFC: RFC 3842.
Release 6.2 supports standard RFC 3842 in order to allow a better interworking with SIP sets having
a voice mail (A4635, A4645) in OmniPCX Enterprise.
Reminder
Standard RFC 2833 is entirely supported since Release 6.1: A SIP set can reach a T2 trunk group of
OmniPCX Enterprise and send DTMF (by using RFC 2833 on SIP).
TC0711 10 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3.4.2 Compatibility of Thomson ST2020 SIP set

In order to complete the range of SIP sets compatible with OmniPCX Enterprise, a new SIP set is
proposed in Release 6.2: Thomson Speed Touch 2020 (ST2020) set.
The Thomson ST2020 set is a monoline SIP set of entry of range with a 16 characters screen,
loudspeaker, etc.
ST2020 set is available at Thomson Telecom via Alcatel Application Partner Program.
For more information regarding the detail of the functionalities and the level of interworking of the
Thomson ST2020 set with OmniPCX Enterprise in Release 6.2, refer to System documentation.
3.5 IP Touch Security Service
3.5.1 Overview
The "IP Touch Security" service is mainly used:
− to secure signaling flows exchanged between IP equipment on the same node
− to secure voice flows exchanged between IP equipment on the same node
− to define a security policy on flows which cross the IP Touch Security Modules
− to authenticate the binaries of the IP Touch series 8 and IP Touch Security Module.
Within the node, the "IP Touch Security" service can only operate between "secured" IP equipment.
This means:
− the integration of security mechanisms in IP Touch sets,
− the installation of security modules (or IP Touch Security Modules) in front of the other IP
equipment of the node to be secured.
A node is said to be secured once the Com Server is protected by IP Touch Security Modules.
The main area of a secured node can be as shown below:
___change-begin___
Ed. 01 / 14 October 2005 11 TC0711

OmniPCX Enterprise
The IP Touch Security service calls upon various security mechanisms based upon the use of:
− IP equipment able to encrypt the voice and signaling flows. These items of equipment are:
• IP Touch sets with a binary allowing them to operate in secured mode
• IP Touch Security Modules which can be broken down into two versions, with:
♦ The SSM (Server Security Module) which is placed in front of the Com Server to be secured
♦ The MSM (Media Security Module) which is placed in front of each Media Gateway to be
secured or an application server
− Keys which will be used, depending on their function, for:
• Setting up secure signaling links between IP equipment within a node (encryption of the
signaling flows)
• Setting up secure voice calls between IP equipment within a single node (encryption of the
voice flows)
TC0711 12 Ed. 01 / 14 October 2005

OmniPCX Enterprise
• Authenticating the configuration files of the secured IP equipment as well as updating their
binaries
− Configuration files adapted to the requirements of the IP Touch Security service. These will be
used to define the security policy of the node and the IP equipment to be secured.
− Com Server adapted to meet the operating requirements of the IP Touch Security service. This
includes:
• A process (BTLink) which allows it to dialog with the IP Touch Security Modules
• A configuration menu specific to the IP Touch Security service,
− A customization center allowing a client to introduce customized keys in secured IP equipment.
For further information about installation and configuration of the IP Touch Security service refer to
the System documentation.
3.5.2 Security Policy for the binaries of the Secured IP Touch sets
To control the exportation of encryption technology (countries under embargo, countries with limited
export, etc.), both French (Thales technology) and American (WindRiver technology), impose that the
secured binaries of the IP Touch sets and the IP Touch Security Modules are not integrated into the
standard software package of the Com Server.
This constraint involves the supply of a patch called secured patch in complement of the generic
version.
This secured patch included only the secured binaries of the IP Touch sets and the IP Touch Security
Modules.
To get this secured patch, a request must be made on Alcatel Business Partner Website. First a
declaration form must be filled in by the Business Partner, in which they acknowledge that they are
aware of the export limits and agree to respect these limits. Once this first step is completed, the
binaries can be downloaded from the Alcatel website (Support>Technical Support>Software> select
Alcatel OmniPCX Enterprise (including 4400)>Release 6.2>OK).
Naming the IP Touch Binaries
For the IP Touch sets, secured and unsecured binaries have the same name, bin4018 for 4018 sets
and bin40x8 for 4028, 4038 and 4068 sets. However, the version of these binaries changes: from
"a.b.c" type naming to "a.b.(c+50)" type naming.
Example
An unsecured binary 3.13.02 will lead to a secured binary 3.13.52.
The two files have the same correction level, the only difference is whether or not the security stub is
present.
Each time an IP Touch binary is produced, two files are actually produced: a secured file and an
unsecured file.
The command readhead can be used to check the version.
Ed. 01 / 14 October 2005 13 TC0711

OmniPCX Enterprise
Method of delivery for secured patches

For any generic delivery of complete version, static patch or exceptionally dynamic patch, a secured
complement type is generated. This complement contains only secured binaries necessary ones to
the generic delivery to which it is referred (secured binaries of the IP Touch sets and the IP Touch
Security Modules).
This complement, called secured patch, will have the same name as the generic delivery to which it
is referred preceded by the letter S (for Security).
Note
The secured patch CONTAINS ONLY the secured binaries: there are no additional call handling
corrections.
Example
A complete version F3.301 has as secured patch the SF3.301 (contains same binaries of the IP
Touch sets as those of the F3.301 version but secured + the binaries of the "IP Touch Security
Module" in phase with F3.301).
A static patch F3.301.10 has as secured patch SF3.301.10 (contains same binaries of the IP Touch
sets as those of the F3.301.10 Patch but secured + the binaries of the "IP Touch Security Module" in
phase with F3.301.10).
Method of installation
A system in F3.301.10 which requires the installation of security must be installed in two stages:
1 Installation of the system in a standard way with the generic version i.e.:
Installation of the generic version F3.301 then installation of the standard static patch F3.301.10
using the existing tools (standard Installation, Installation on inactive partition or Remote
Download).
2 Installation of the most recent secured patch in complement of the preceding installation i.e.:
Installation of the secured patch SF3.301.10 containing the most recent secured binaries using
the existing tools of installation of patches (Deliveries installation or Remote Download).
Note
If installing a complete version + generic patch, for example F3.301 + F3.301.10, the installation of
the secured patch of complete version SF3.301 is not necessary since the secured patch SF3.301.10
of the standard static patch has same binaries but more recent.
TC0711 14 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3.6 IP Touch survivability
3.6.1 Reminder on GD backup signaling link in R6.1

In a Remote GD context, when IP link between the Gateway Media in domain 1 and Call Server in
domain 0 falls (WAN), Call Server establishes a backup signaling link via an ISDN access to join the
Gateway Media.
WAN NOK
CS DHCP
server 4038
OK
ISDN 4039
Domain
Domain 00 Domain 11
Domain
This configuration have several constraints:

1 If the IP Touch sets of domain 1 have a dynamic configuration, when IP link between the Media
Gateway and Call Server falls (WAN), as the sets are not able to reach DHCP and TFTP servers,
remain out of service whereas the Media Gateway a backup signaling link via an ISDN access to
join Call Server.
2 If the IP Touch sets have a static configuration with as TFTP server address, the IP address of the
Media Gateway of their domain 1 in order to profit of its backup signaling link, the loss of the
Gateway Media also involves the loss of IP Touch sets of domain 1, even if IP network always
works and if Call Server is accessible for IP Touch sets.
3.6.2 IP Touch survivability description

In Release 6.2, the IP Touch survivability makes it possible to raise the constraints related to the
Media Gateway backup signaling link in R6.1.
WAN OK
CS DHCP
server 4038
OK
4039
ISDN
Domain 00
Domain Domain 11
Domain
Ed. 01 / 14 October 2005 15 TC0711

OmniPCX Enterprise
The IP Touch survivability consists in sending an IP address of backup TFTP server to the IP Touch
during its initialization whereas this one is configured dynamically.
This address of backup TFTP server corresponds in fact to IP address of the Media Gateway of the
domain 1 to which also the IP Touch belongs.
In addition to its IP configuration obtained from DHCP server, the IP Touch memorizes in its flash this
IP address of backup with all IP parameters (Netmask, gateway, etc).
Under normal operation, the IP Touch sets a signaling link with Call Server via the WAN:
1 If the Media Gateway falls, as the IP Touch is configured dynamically, retains its signaling link
with Call Server via the WAN.
2 If DHCP server falls, the IP Touch cannot retrieve its lease any more and starts again as if it was
configured in static mode. It retains its previous IP address and is connected on backup IP
address stored in its flash, i.e. on the Media Gateway of its domain 1 whose signaling link is
always set with Call Server (WAN OK).
3 If WAN falls, the IP Touch cannot join Call Server any more and starts again as if it was
configured in static mode. It retains its previous IP address and is connected on backup IP
address stored in its flash, i.e. on the Media Gateway of its domain 1. The Media Gateway has
set a backup signaling link via an access ISDN to join Call Server and can thus also provide a
signaling link for the IP Touch.
Note
Survivability isn't compatible with IP Phone eReflexes.
IP Touch sets can always be configured statically.
TC0711 16 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3.7 New icons of supervisions

From Release 6.1.1, new icons are available for supervised status.
In Release 6.2, an additional icon is used to view on a supervisor set, a forwarding state enabled on
the supervised set.
3.7.1 Conventions
Convention for UA3G icons
Off
On
Blinking
Convention for LEDs
Off
On
Slow blinking
Fast Blinking
Functions keys
• Forward (immediate, on busy, no reply, busy or no reply, on principal or secondary lines)
• Hunting group in/out
• Do not disturb (also for suite)
• Lock the set
• Identity masking
• Caller identity masking
• Camp on control
• No ringing
State IP Touch icon UA3G icon Led

Function deactivated
Function activated
Ed. 01 / 14 October 2005 17 TC0711

OmniPCX Enterprise
3.7.2 Redial memory

No number stored
Number stored
After memory use, the user must press again

on key if he doesn’t want to loose the number
3.7.3 Boss/Assistant
Assistant call (on Boss set)
Idle
Boss calls Assistant
Assistant is calling
Assistant busy
Assistant absent, Routing Assistant present
Assistant(s) absent(s)
TC0711 18 Ed. 01 / 14 October 2005

OmniPCX Enterprise
Boss call (on Assistant set or Routing Assistant set)
Idle
Overflow activated (only on Routing Assistant

set)
Assistant calls Boss
Boss is calling
Boss busy
Filtering activated
Assistant absent (on Assistant set or Routing Assistant set)
Function activated
Screening (on Boss set)

Function activated, Assistant present
Function deactivated, but Assistant(s) absent
Ed. 01 / 14 October 2005 19 TC0711

OmniPCX Enterprise
Screening supervision (on Assistant set or Routing Assistant set)

Function activated on Assistant set
Function deactivated on another Assistant set
3.7.4 Supervision
Trunk group Supervision
At least one trunk available
All trunks are busy or out of service
Trunk Supervision
Idle
Busy, ringing on attendant, out of service or

on another set
Hold on another set
Ringing on another set
TC0711 20 Ed. 01 / 14 October 2005

OmniPCX Enterprise
Set Supervision
Idle
Busy
Fully busy or out of service
Incoming call
In immediate forward, do not disturb or

forward to text mode (1)
(1) The display of forwarding state of a supervised set is available from Release 6.2.
Voice Mail Supervision
No message
No new message, at least one old message
At least one new message
Ed. 01 / 14 October 2005 21 TC0711

OmniPCX Enterprise
3.7.5 Multiline
Line
Idle
Incoming call
In conversation
On hold
Mutual hold possible
Multi Line Appearance
Idle
Incoming call
In conversation
In conversation on another set
On hold for all sets (supervised hold)
On hold on the set
Fully busy
TC0711 22 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3.8 Different ringing for secondary MLA set

In a "Multi Line Appearance" configuration, it is possible to distinguish by a ringing, an external call
of an internal call on secondary MLA set. This exploitation depends on the MLA with ringing
distinction system option:
• MLA with ringing distinction = 0
The set rings like a supervisor, it does not have there a possibility of distinguishing the types
of calls, it is normal operation in R6.1.
• MLA with ringing distinction = 1
The ringing characteristics of secondary MLA set are those of a multiple-line set. They follow
the configuration of the existing system options (Distinction of ringing according to the type of
call).
Management
MLA parameters / MLA with ringing distinction
Remark
To take into account the option MLA with ringing distinction, the mode of ringing can be
short ring, long ring, differed or not.
3.9 Dial by name with overflow on LDAP server

Dial by name with overflow on LDAP server allows display of a name of 30 characters + a first
name of 30 characters + a telephone number of 50 characters maximum.
3.10 Product Limits and network interworking
3.10.1 IP Domains
The number of IP domains changes from 128 to 1000.
3.10.2 Entities
The number of entities for a node or in a network changes from 255 to 1000.
If a network is composed of several nodes with a number of entities higher than 255, each node of
the network must be in Release 6.2.
Ed. 01 / 14 October 2005 23 TC0711

OmniPCX Enterprise
3.10.3 Nodes of an IP homogeneous network

The number of nodes of a backbone IP network changes from 32 to 100.
In a homogeneous IP network, each node of the network can have several adjacent nodes (for a
maximum of 31 adjacent nodes).
VPN Jump
OXE 1
OXE 1 OXE
OXE 2
2
IPIPnetwork
Network
OXE
OXE 3
3 OXE
OXE 4
4
ABC Signaling Link
ABC Signaling Link

It is not necessary to completely mesh the network.
VPN Jump
It is advised to completely mesh the network.
3.10.4 Interworking in network

In a homogeneous network, Release 6.2 allows interworking with nodes in Release 5.0 Ux, 5.1, 6.0
and 6.1.1.
3.11 Security enhancements of the system

In Release 6.2, new rules of configuration regarding system security appear.
3.11.1 Security by default of the system after installation

During the first standard installation, a list of security levels are displayed before any other
configuration is possible.
This list proposed in a menu on the first login on Call Server, makes it possible to sensitize the
Partner Business on the policy of security which he will have chosen for the system.
The absence of security on the system, which remains always possible, will be under the whole
responsibility for the customer.
TC0711 24 Ed. 01 / 14 October 2005

OmniPCX Enterprise
Description
On the first login after the standard installation of a Call Server, the question Do you want to
activate server security high level (Y/N) ? is displayed.
An answer (Y or N) is mandatory to quit the menu.
Answer N
The following menu appears:
Select server security level :
R) Configuration to be restored
0) Level_0 = no security feature activated
1) Level_1 = password/aging
2) Level_2 = password/aging + trusted hosts/TCP wrapper
3) Level_3 = password/aging + trusted hosts/TCP wrapper + SSH
Choice R is used to restore Linux data of the system (and thus to retain its levels of security) if this is a
migration from R5.1, R6.0 or R6.1.
Choice 0 is used to initialize the system with no default level of security as in R6.1.
Choices 1, 2, 3 are used to set the various levels of security already existing in R6.1 by mixing
between them if necessary:
• Choice 1 : Modification of passwords of root, swinst, mtcl and adfexc accounts
and enabling of the aging password function
• Choice 2 : Choice 1 + enabling of the trusted hosts and TCP wrapper
• Choice 3 : Choice 2 + enabling of the SSH service
Answer Y
The level of security 3 is automatically set.
3.11.2 Sending of SYSLOG messages towards an external server

The SYSLOG messages stored in the files /var/log/syslog and /var/log/auth.log can be
sent to an external server (configurable by netadmin).
3.11.3 Complete command history

All shell command history is stored for every user in a file shell.log under /var/log.
3.11.4 Community name for SNMP

It is now possible to modify default community name to avoid easy access to MIB information
(configurable by netadmin).
Ed. 01 / 14 October 2005 25 TC0711

OmniPCX Enterprise
3.11.5 Enhancement of User’s account menu

New features were added in Swinst/User’s account management menu.
1 Change account password

2 Change account aging password
3 Configure maximum authentication attempts
These 3 menus make it possible to modify the passwords of all the accounts, to validate the function
aging password for each account and to limit the number of password failure of the account by
emitting an incident and a SNMP trap on these failures.
3.11.6 Alarm on logging failure

When the configuration of the number of failure on the password of the accounts was carried out as
indicated § 3.11.5 , an incident and a SNMP trap are sent.
3.12 New features for the public network
3.12.1 R1.5 protocol

Release 6.2 supports the R1.5 protocol in transit for the Russian market.
3.12.2 CLIP on APA

− From Release 6.1, CLIP on APA line (CLIDSP daughter board - 3EH 73034 AB) is available for all
markets.
− In addition, Release 6.2 supports CLIP DTMF in APA line (CLIDSP daughter board - 3EH 73034
AB) for India and Taiwan.
Management
• APA board parameters under: Shelf / Go down hierarchy / board / CLIP
Signalization
• Q23X parameters under: System / Go down hierarchy / Tone Detector
Parameters / Go down hierarchy / DSP Parameters / Coupler Type +
MG-APA
3.12.3 NDDI2 board for the Australian market

Release 6.2 supports NDDI2 board for the Australian market.
3.13 Dynamic initialization of SLI board

SLI boards can be initialized dynamically by Call Server. Dynamic initialization can be schematized
by the sending of a batch of 150 parameters from Call Server to the Media Gateway allowing the
dynamic modification of the audio parameters of a SLI board.
TC0711 26 Ed. 01 / 14 October 2005

OmniPCX Enterprise
Management
Shelf / Go down hierarchy / Board / Send Init Dynamic Msg: Yes
3.14 Ethernet Duplication on CPU7

In configuration with CPU7 only, and in order to solve certain problems of load with the C1 link in
the case of high traffic (for example in configurations with CCD), it is possible to send on IP, the
messages of telephone duplication via the process iplink as for the Common Hardware CPU or
Appliance Server.
Role management, decision of switch and detection of loss of Main CPU remain carried out by IO1
board and not by the iplink.
Management
Shelf 0 / Mode Signalisation + ETHERNET
Note
Any change of signaling mode requires a reboot of Stand-By CPU then a restarting with mastercopy.
When Ethernet duplication and IP redundancy are activated, it is necessary to manage timers of IP
redundancy in such a way that switch of CPU is done by IP redundancy before the detection of loss of
IP by iplink.
3.15 Specific developments offered in Release 6.2

Features "IP Attendant Softphone", "IP CCAgent Softphone" and "Free Desktop" developed by the
"Professional Services" are offered in Release 6.2.
These features are entirely supported by "Professional Services" via dedicated e-Service Request.
Ed. 01 / 14 October 2005 27 TC0711

OmniPCX Enterprise
3.15.1 IP Attendant Softphone and IP CCAgent Softphone

This features is used to obtain on a multi-media PC the same telephonic functions that has an CCD
agent or an attendant with 4037 set.
This feature is obtained thanks to the installation of a software on the Multi-media PC of the agent or
the attendant.
Agent or
Attendant
Signaling (UA Protocol)
Voice RTP flow
The level of service offered to the agent or to the attendant is exactly the same one as that of an
4037 set but with an interface type of 4068:
The communications can be restored on loud speaker or on USB headset connected to the PC.
− VoIP characteristics.
Protocols supported: RTP/RTCP (voice), UA (signalization), G711, G723.1, G729 (algorithms)
Tickets over IP
− Ringings (15 melodies) always sent on loud speakers
− DTMF sending
− Encryption of voice and signaling are not supported.
− Compatible with the "Both CPU in two different subnets" feature.
TC0711 28 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3.15.2 Free Desktop application

The Free Desktop feature allows a user of a network to "log on" and "log off" on any equipment while
retaining its set profile (categories).
The "Log on" can be carried out starting from a set or from an application Web (API XML in R2.2)
using the user directory number and its password.
After "log off", the user directory number can be fowarded on voice mail or other.
3.16 Statistic tickets over IP

Voice over IP statistic tickets contain various data items (IP addresses, call duration, compression
used, jitter, packet loss, delay, ...) designed to identify the causes of potential problems on IP devices
connected to an OmniPCX Enterprise.
A ticket (record) is generated at the end of each communication; it involves one of the following
devices:
• INTIPA and B boards
• IP Phones
• IP Touch sets
• GD
• GA
• PCMM
• 4645
• IP Attendant Softphone
• IP CC Softphone
3.17 Both CPU in two different subnets

The "Both CPU in two different subnets" feature, under PCS in R6.1.1, is released in R6.2.
REMINDER
The "Both CPU in two different subnets" feature makes it possible two CPU to be in two different
subnetworks.
Ed. 01 / 14 October 2005 29 TC0711

OmniPCX Enterprise
This feature is available on AS and CS.

This feature is supported by following IP equipment:
• SIP sets
• Alcatel series 8 sets (4028-4038-4068)
• GD
• GA
• INTIP
• IOIP
• "IP Touch Security Module" : SSM, MSM
• Attendant IP Softphone
• IP CCAgent Softphone
The applications able to take into account 2 addresses of CPU are:
• Alcatel 4635 (R5.2.6)
• Alcatel 4645
• OmniVista 4760i / 4760 (R3.2)
• OmniTouch Contact Center : CCD/CCS/CCA/CCIVR
• XML Web services
• Application "XML IP Touch"
• TSAPI
• ACAPI
• VoWLAN R1.x
Restrictions
− No V1 (4080 RE) - V1S (4080 FRE) - V2 (e-Reflexe IP Phone V2) sets. Only the IP sets of series 8
and SIP sets are able to take into account 2 addresses of CPU.
− No Genesys applications (CCemail, CCoutbound, CCweb).
− No RSI Synchro Server.
− No TAPI.
− No OmniTouch Unified Communication.
− If a R6.2 node is added in a network with nodes less than R6.0, it is essential to continue to use
the addressing by role in case of logical links over IP (the nodes below R6.0 cannot establish
logical links towards two different addresses).
− If an external DHCP server is used, a tftp server must also be used.

500 512
1000 512
2500 1280
5000 2560
− Audit and broadcast must be performed via IP/X25 and not directly via IP.
TC0711 30 Ed. 01 / 14 October 2005

OmniPCX Enterprise
3.18 Modem, Fax, Data transparency over IP

"Modem, Fax, Data transparency over IP" feature is available from Release 6.2.
Refer to the technical communication TC0712 Modem, Fax, Data transparency over IP.
3.19 XML IP Touch

REMINDER
Alcatel series 8 sets are able to interact with external applications. This access to the external
applications is provided via the Presentation Server (PRS).
There is no direct access between the series 8 sets and the PRS: all is carried out via Call Server.
Applications XML are provided by the Presentation Server. This one integrates a HTTP client who
behaves like a browser.
The external applications are viewable on IP Touch set from the menu page. When a user selects an
external application, the Presentation Server is notified via Call Server. The server analyzes the action
carried out by the user and returns it towards the concerned application. The application answers
him by a document in XML language describing the new screen to be displayed on the set of the
user.
The series 8 set is able to switch in a phone context if it is already in a application context and
conversely.
In Release 6.2, there is a direct access (no more transit via Call Server) between IP Touch series 8
and the PRS 1.2 (XML Web Services 2.2) for the visualization of images on the sets.
CS XML IP Touch
Web Services
Video
PRS 1.2 Application
For more information, refer to the System documentation and technical communication TC0714 XML
Web Services R2.2.000.171a Technical Release.
Notes
− If switching the CPU, the application context is not retained.
− The software lock 318 (XML IP Touch- IP Engine) is used to define the number of
simultaneous connections.
Ed. 01 / 14 October 2005 31 TC0711

OmniPCX Enterprise
4. FEATURES UNDER PCS (PREMIUM CUSTOMER SUPPORT)
4.1 Common Hardware IRAD board

Common Hardware IRAD board, allows a remote connection via ISDN (T0 or T2), on OmniPCX
Enterprise from a OmniVista 4760 R3.2 server equipped with a T2-E1 board.
The access IRAD board via OmniVista 4760 R3.2 makes it possible to configure, backup the data of
OmniPCX Enterprise and to download a version or a patch by using in complement the PC Installer
with a maximum capacity of 320 Kbit/s by using a "aggregation" of 5 channels B (protocol PPP).
Connection on IRAD board is protected (control of the caller number, account user and IP address,
password, local IP addresses hidden by NAT).
IRAD board is managed in a free position of MG PRA-T2 board.
The internal configuration of IRAD board is done by a WEB navigator.
IRAD Remote Service Typical Configuration

OmniPCX Enterprise Node
OmniPCX Enterprise Node

eRMA/RMA for the alarms
OR Win2003
T0/T2 T0/T2
OR T2
E1 Board
IRAD CH
ISDN
ISDN OR
4760 Server
Ethernet cable to LANx4 on CPU T0/T2 IP Router
IRAD -CH
Client 4760 +
PC Installer
Remote Service Center
TC0711 32 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 - RELEASE 6.2 CONTENT OF THE SOFTWARE PACKAGE
CONTENT OF THE SOFTWARE PACKAGE
The software package contains the OmniPCX Enterprise F3.301.10 application.

The different versions of the OmniPCX Enterprise application modules are:
− Linux : 38.0
− Linux Package : 38.4
− swinst : 2.28.0
− PC Installer : 2.20
− OmniPCX Enterprise R6.2 : F3.301.10:
F3.301 complete version
+ F3.301.10 static patch
+ SF3.301.10 secured patch (Note)
Note
The access to secured patch is only given on request after filing the appropriate document posted on
BPWS Support>Technical Support>Software> select Alcatel OmniPCX Enterprise (including
4400)>Release 6.2>OK> International Multipurpose Letter of Assurance / End-User Certificate Form
File.
From Release 6.1.1, dynamic patches will be no longer delivered. They are replaced
by static patches ; refer to the technical communication TC0682 Stop of dynamic
patch delivery from Release 6.1.1.
Reference of compatible CD-ROMs and DVD

As of Release 6.1, the software is only delivered on DVD.
CD-ROM/DVD Reference
Version F3.301.10 (DVD) 3BA 27681 AAAA
Version F3.301.10 Secured (DVD) 3BA 27682 AAAA
System voice guides v5.2 3BA 57423 AAAF
OmniVista 4760 - Release 3.2 Software 3BH 11632 ADAA
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
CONTENT OF THE SOFTWARE PACKAGE F3.301.10 - RELEASE 6.2
List of binaries in F3.301.10 version

The new binaries of the version are in bold characters.
Released Versions
Binaries R5.1.2 R6.0 R6.0.1 R6.1 R6.1.1 R6.2
E2.504.1.n F1.602.3.i F1.603.1.c F2.500.6.i F2.502.5 F3.301.10
Binaries relative to system
bios CPU5 Step3 3BA 20032
ADAB_4.0
bios CPU6 Step2 3BA 24095 3BA 24095
AAAB02_4.2 AAAB03_4.6
bios CPU7 Incompatible 3BA 24115 3BA 24115
AAAA_2.13 AAAA_2.16
bios CS 8.33 8.27 8.32 8.33
bios GD 8.33 8.27 8.33
io1n 13 15 15
io2 4.6 4.6 4.6
io2n 5.15 5.15 5.15
linux_patch 18.9 23.6 23.8 33.4 33.9 38.4
obca 1.5
pc_install 2.17 2.17 2.19 2.20
swinst 2.22.0 2.22.0 2.25.0 2.27 2.28
Binaries relative to DECT
dect4 7.9
dect8 1.25 1.24 1.25
ibs_appli_ng 37.00 37.00
ibs_boot_ng 7.1
ibsng 18.06
rbsng 43.0
startibsng 0.61 0.71
Binaries relative to compression boards
bindsintip 4.35.1 4.34.1 4.35.2 4.35.3
bindsintip2 1.03 2.2.1 2.2.3 2.3.0 2.3.1
binintip_appli 6.35 7.14.1 8.2.1 9.08.1 9.09.1 10.05.02
binmcv 3.6.1 3.6 3.6.1 3.7.1
binmcv2 2.2.1 2.2.3 2.3.0 2.3.1
bootintip 5.1.2 5.11 5.12 6.0.2 6.03 6.04
ioip 2.0 3.03 3.07.01
lio 3.25 3.25
lio_comp2 3.36 3.36 3.39 3.40
lioe 3.22 3.22
mg_appli 16.30 20.16.11 22.3.2 30.10.1 30.12.1 40.5.1
rGD Incompatible Incompatible Incompatible 1.03
rlio_comp2 3.24 3.26 3.27
tsclioe 2.10
Binaries relative to sets
TC0711 2 Ed. 01 / 14 October 2005

OmniPCX Enterprise
F3.301.10 - RELEASE 6.2 CONTENT OF THE SOFTWARE PACKAGE
Released Versions
Binaries R5.1.2 R6.0 R6.0.1 R6.1 R6.1.1 R6.2
E2.504.1.n F1.602.3.i F1.603.1.c F2.500.6.i F2.502.5 F3.301.10
bin40x8 Incompatible 1.29.2 1.55.01 2.13.03 2.54.04 3.13.04
bindatanoe Incompatible Incompatible Incompatible 2.13 2.54.04 3.13.00
Binnoeux9 Incompatible Incompatible Incompatible 2.14.02 2.54.03 3.10.00
Binnoeu19 2.54.03 3.10.00
ipphone 2.21.00 2.20.00 2.23.00 2.24 2.26 2.27
tscip 5.2
tscipv1S 2.8 3.0
wifi set Incompatible Incompatible 1.04 1.06 1.08
Secured binaries
bin40x8 Incompatible Incompatible Incompatible Incompatible Incompatible 3.13.54
bindatanoe Incompatible Incompatible Incompatible Incompatible Incompatible 3.13.00
SM modules Incompatible Incompatible Incompatible Incompatible Incompatible 1.3.01
(Thales)
Binaries relative to boards
bbc2 3.05 3.05 3.06
bin4615 3.0.24
brapra 2.06
c1nvgpa2 2.13 2.11 2.13 3.0
c1nvua 3.6 3.6 4.2 4.5 4.6
c1nvz32 1.15 2.0 2.2 2.4
cpl2dpnss 1.10 1.11
dpnss 2.3
dpnssnv 1.3 1.5
dpnss2 1.11
dpt1 1.16 1.16
dsp_emtl24021 3.01
dsp_gpa 2.01
dsp_vgu 1.5
dsp0Z32 1.02
dsp1_gpa2 1.05 1.05 1.06
dsp1nddi2 2.01
dsp2_gpa2 1.07 1.07 1.10
gpa2tns 1.10
gpa 2.24 2.24
intof 1.20 1.21 1.22
intofssync 1.02 1.03 1.05
intof2 Incompatible Incompatible Incompatible 1.6 1.7
ivrZ24 1.3 1.03
lia 4.17
lioebbc2 3.04 3.05
liop 1.05 1.06 3.01
mapacs2 1.11 1.12
mic2 2.28
Ed. 01 / 14 October 2005 3 TC0711

OmniPCX Enterprise
CONTENT OF THE SOFTWARE PACKAGE F3.301.10 - RELEASE 6.2
Released Versions
Binaries R5.1.2 R6.0 R6.0.1 R6.1 R6.1.1 R6.2
E2.504.1.n F1.602.3.i F1.603.1.c F2.500.6.i F2.502.5 F3.301.10
nddi 2.11
nddi_in 2.7 2.12
nddi2 2.10 2.11 2.12
nprae 1.24 1.26
pcm2_ru 1.6
pra 2.05 2.06
pra2 2.21
rma 3.04.03 3.04.04
tonesnv 2.15 2.16 3.0
ua 3.13.6 3.13.7 3.13.8
uscvg 2.9
Binaries relative to attendants
fbc 2.13
ta/mac 4.7
ta/pac 1.12 1.12 2.0
Binaries relative to 4760i
4760i 1.0.01.07 2.0.01.06 2.1.01 2.1.01.07
Binaries relative to SIP
lib_sip 2.1.8 4.0.6
TC0711 4 Ed. 01 / 14 October 2005

OmniPCX Enterprise
INSTALLATION PROCEDURE APPENDIX 8
FOR VERSION F3.301.10 - RELEASE 6.2 KNOWN DEFAULTS
KNOWN DEFAULTS
Main known defaults which will be fixed in a static patch.
Anomaly
Title Remarks
Report
XTSce60954 Hotel- Problem in the call forwarding on no reply
XTSce59156 No DTMF send between NOE TDM sets an NOE IP sets
Campus with encryption : communication is scrambled after
XTSce39311
a Handover
XTSce61441 IP Touch 8&9 Sets / DTMF / No * and # / 1-59966888
Field : code access a message SUU does not operate with IP
XTSce57774
Touch set
DTMF CLIP call on a busy set with no camp-on - Display on
XTSce55676
attendant not coherent
XTSce62412 Obstraf: Erroneous ticket during double call.
IP Softphone : cannot take a call when call is presented
XTSce61143
during the initialization
XTSce60641 Very frequently incident 1279 type 19 / 1-59609137
XTSce62518 Communication without audio after 9" of conversation
VM 4645 WEB : No start recording beep on IP phone if
XTSce59797
remote 4645
High number of incident 1608 after INTIP is back to service
XTSce60606
/ 1-59645616
XTSce62096 Memory size : values given by "actorsdata" are wrong
Network call with Netmeeting => alarm 4412=H323 :
XTSce61907
arret de la com
Attribute a network VM to a SIP user : wrong 1st NOTIFY
XTSce63043
message after SUSCRIBE
XTSce61428 Loss of DTMF from NOE if compression is G723 on OXE
Message light on analogue phone not working (when
XTSce61024
configured as analog with 4980
When dialing into UM and pressing 0 to go to operator no
XTSce59290
speech
Device blocked if call back from My Messaging to extension
XTSce59423
fwd to My Assistant
XTSce60325 My Assistant rule : no answer and busy does not work
CSTA: when monitor start during a withdraw pending the
XTSce55477
agent status is wrong / 1-57500991
RSI overflow does not work for Ag2 ext incoming call to RSI
XTSce52928
find Ag1
Since software upgrade to 6.1.1 calls to S0 users abort / 1-
XTSce63500
60721591
Ed. 01 / 14 October 2005 1 TC0711

OmniPCX Enterprise
APPENDIX 8 INSTALLATION PROCEDURE
KNOWN DEFAULTS FOR VERSION F3.301.10 - RELEASE 6.2
TC0711 2 Ed. 01 / 14 October 2005

Technical Communication Omnipcx Enterprise: NB of Pages: 174 Date: 14 October 2005

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Technical Communication Omnipcx Enterprise: NB of Pages: 174 Date: 14 October 2005

Uploaded by

Copyright:

Available Formats

TECHNICAL COMMUNICATION No. TC0711 Ed.

OmniPCX Enterprise Nb of pages : 174 Date : 14 October 2005

NOT URGENT TEMPORARY PERMANENT

SUBJECT : INSTALLATION PROCEDURE FOR VERSION F3.301.10 – RELEASE 6.2

Ed. 01 / 14 October 2005

1. APPLICATION DOMAIN ...............................................................8

2. INTRODUCTION TO RELEASE 6.2 ................................................8

3. CONTENT OF THE SOFTWARE PACKAGE...................................11

5. CONDITIONS FOR INSTALLATION IN NETWORK.......................15

Ed. 01 / 14 October 2005 1 TC0711

TC0711 2 Ed. 01 / 14 October 2005

9. OPERATING MODE ....................................................................37

10. LOADING THE SOFTWARE.........................................................38

11. TRANSLATIONS .........................................................................41

Ed. 01 / 14 October 2005 3 TC0711

11.2 Remarks ................................................................................................. 42

12. UPDATING THE BETA TEST SYSTEMS..........................................42

13. SYSTEM MANAGEMENT .............................................................43

14. CHECKING START-UP OF CPU/IO1/IO2/IO2N...........................43

15. COMPULSORY MINIMUM ADDITIONAL DATABASE

16. STARTING UP THE CPU IN ITS ENVIRONMENT ON SITE.............46

17. CHECKING CORRECT OPERATION.............................................47

18. REFERENCE DOCUMENTS..........................................................48

TC0711 4 Ed. 01 / 14 October 2005

Ed. 01 / 14 October 2005 5 TC0711

TC0711 6 Ed. 01 / 14 October 2005

Ed. 01 / 14 October 2005 7 TC0711

2. INTRODUCTION TO RELEASE 6.2

TC0711 8 Ed. 01 / 14 October 2005

New hardware and features from Release 6.2:

New hardware New features Features under PCS (1)

(1) Premium Customer Support.

Ed. 01 / 14 October 2005 9 TC0711

Hardware not released Feature not released

TC0711 10 Ed. 01 / 14 October 2005

3. CONTENT OF THE SOFTWARE PACKAGE

Reference of compatible CD-ROMs and DVD

Ed. 01 / 14 October 2005 11 TC0711

TC0711 12 Ed. 01 / 14 October 2005

CPU5 Step3 Controlling Appliance Server

(1) Can no more be configured in a new business account.

Ed. 01 / 14 October 2005 13 TC0711

(3) Manual modifications are required.

4.3 VoIP network conformity check

4.4 Recommendations and security

TC0711 14 Ed. 01 / 14 October 2005

5. CONDITIONS FOR INSTALLATION IN NETWORK

During progressive migration and depending on certain topologies and hardware

If using a CCS multi-site, each node must be in Release 6.2.

5.1 Installation in network in Release < 3.0

Ed. 01 / 14 October 2005 15 TC0711

− Prohibit the use of entity numbers greater than or equal to 127.

During this progressive migration and depending on certain topologies and

During a progressive migration in an IP network, the INTIP board can be connected to an

5.3 Installation in network in Release 4.2 and 4.2.1

During this progressive migration and depending on certain topologies and

5.4 Installation in network in Release 5.0 Ux, 5.0.1 Ux, 5.0 Lx

TC0711 16 Ed. 01 / 14 October 2005

5.4.1 OmniPCX Enterprise compatibility

In Release 6.2, INT1and INT2 boards must be replaced by INTOF/INTOF2 boards.

The following tables are not broadcast:

Ed. 01 / 14 October 2005 17 TC0711

5.4.3 Compatibility of external applications