TECHNICAL COMMUNICATION

No. TC1349

Ed. 01

OmniPCX Enterprise

Nb of pages : 34

Date : 28 May 2010

URGENT
NOT URGENT

TEMPORARY

PERMANENT

SUBJECT : INSTALLATION PROCEDURE FOR VERSION I1.605.16.c RELEASE 9.1

This is the technical release of OmniPCX Enterprise with the version I1.605.16.c. It corresponds to
Release 9.1.
It is available on Alcatel Business Partner Web Site (http://www.businesspartner.alcatel-lucent.com/)
and on DVD only with the references 3BA 27730 ABAC (non secured version) and 3BA 27731 ABAC
(secured version).
Technical modes to change the release, new features, registered restrictions and controlled features
are described in the installation procedure for version I1.605.16.c.

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

CONTENTS
1.

APPLICATION DOMAIN ...............................................................

...............................................................6
...............................6

2.

REFERENCE DOCUMENTS................................
DOCUMENTS ............................................................
............................................................6
............................6

3.

FEATURES AND SPECIFIC

SPECIFIC PROCESS .............................................
.............................................8
.............8

3.1

Features under PCS in version I1.605.16.c................................

I1.605.16.c ................................................
................................................ 8

3.2

Features in test ................................................................

.........................................................................................
......................................................... 8

4.

CONTENT OF THE SOFTWARE

SOFTWARE PACKAGE................................
PACKAGE .....................................
.....................................9
.....9

5.

LOADING THE SOFTWARE................................

SOFTWARE .........................................................
.........................................................13
.........................13

5.1

Complete loading
loading of the I1.605 version and the I1.605.16 and I1.605.16.c
patches ................................................................
................................................................................................
...................................................................
................................... 13

5.2

Sites with the "IP Touch Security" feature: Loading procedure of SSM and
MSM boxes after upgrading in SI1.605.16.c ...........................................
........................................... 13

5.2.1

Migration with SSM & MSM boxes in version 1.3.xx ........................................13

5.2.2

Migration with SSM & MSM boxes in version 1.4.xx, 1.6.01, 2.x.0x .................14

5.3

6.

Swinst 2.58.0 ................................................................

..........................................................................................
.......................................................... 14

RESTRICTIONS AND REMARKS

REMARKS ...................................................
...................................................14
...................14

6.1

Loading the version with 40 GB or 60 GB hard disks .............................. 14

6.2

4760i availability and support ................................................................

................................................................ 15

7.

NEW FEATURES AVAILABLE

AVAILABLE ON RELEASE 9.1.............................
9.1 .............................17
.............................17

7.1

From I1.605.16.c version ................................................................

........................................................................
........................................ 17

7.1.1

SLI-2 boards ...................................................................................................17

7.1.2

New Appliance Server HP DL320 G6 ..............................................................17

7.1.3

New Appliance Server IBM X3250 M3 (Maokong) ..........................................18

7.1.4

PCS download in parallel mode......................................................................18

7.1.5

Wake up call customization ............................................................................ 18

Ed. 01 / 28 May 2010

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

7.1.6

Logs sent in real time......................................................................................19

7.1.7

Dial By Name overflow to LDAP......................................................................19

7.1.8

Unset the Redial Feature.................................................................................19

7.1.9

DECT encryption on IBS/Crystal Hardware .....................................................19

7.1.10

Voice mail password length.........................................................................20

7.1.11

Cellular Voice Mail detection timer..............................................................20

7.1.12

Supervision with Free Desktop ....................................................................20

7.1.13

Call Transfer (USA Conference Mode) .........................................................21

7.1.14

3 party conference (USA Conference Mode) ................................................21

7.1.15

Management Event on Forward cancellation/activation ..............................21

7.1.16

FlexOffice: forwarding cancelled .................................................................21

7.1.17

UDP to TCP switching for long messages .....................................................22

7.1.18

Multiple SIP gateways support using via header..........................................22

7.1.19

SIP QoS tagging support..............................................................................22

7.1.20

Force On Net...............................................................................................22

7.1.21

Interoperability with SBC 5.2.8 ....................................................................23

TC1349

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

Ed. 01 / 28 May 2010

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

1.

APPLICATION DOMAIN

WARNING
This document applies to the OmniPCX Enterprise Release 9.1 in standardized version I1.605.16.c.
Version I1.605.16.c makes a set of corrections available for sites already installed, new binaries
from version I1.605.14.e and provides some new features.
This document is based around a central document, the Release 9.1 installation procedure, and
appendices which describe:
The restrictions and remarks.
The new features.
Note
The appendices below of previous installation procedures were removed from this document and
replaced by technical communications to make easier their search and their update:
The comparison of licenses from R5.0 Ux.
The migration from an OmniPCX 4400 to an OmniPCX Enterprise.
The synchronization of the system after migration to an OmniPCX Enterprise with an Appliance
Server.
The reminder of features released in previous releases.

2.

REFERENCE DOCUMENTS

Technical communications:
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 Alcatel 4635 - Migration procedures
TC0274 DECT Compatibilities
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
TC0594 Coupling a Bluetooth device on Alcatel IP Touch set 4068

TC1349

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

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
TC0712 Modem, Fax, Data transparency over IP
TC0777 Comparison of licenses from Release 5.0 Ux
TC0778 Migration OmniPCX 4400 to OmniPCX Enterprise
TC0779 Synchronization of the system after migration to OmniPCX Enterprise with Appliance Server
TC0780 New hardware and features from Release 5.1
TC0781 Migration of Mobile IP Touch from Release 1.x to Release 2.x
TC0940 Technical release note for VoWLAN Release 3.0 offer
TC0941 VoWLAN compatibility
TC0944 Configuration, incidents & log files recovery
TC1105 Alcatel 4059 MAC / IP - Installation procedure for version 5.1.1
TC1106 Thomson ST20xx SIP sets deployment
TC1108 Native SIP Call Controller: White list
TC1195 Technical Release Note of VoWLAN 4.1 for OmniPCX Enterprise
TC1212 CS-2 board introduction
TC1235 Detailed list of all the ports and protocols used by OmniPCX Enterprise
TC1243 Technical Release Note for OmniPCX Enterprise Release 9.1 - Version I1.605.12
TC1244 Installation Procedure for version I1.605.12 - Release 9.1
TC1246 Alcatel 4059 MAC / IP - Installation procedure for version 5.1.5
TC1253 Alcatel 4635 - Installation procedure for version 5.4.6 - Release 5
TC1254 Technical Release Note for Device Management Server 1.2.000.020
TC1255 4008 / 4018 SIP set deployment with OmniPCX Enterprise
TC1256 Installation procedure for version 5.1.06.03.c - Release 5.1.1
TC1271 Checks for integrity and authenticity of downloaded software
TC1290 LLDP-MED on IP Touch sets
TC1291 Technical Release Note for OmniPCX Enterprise Release 9.1 - Version I1.605.14.e
TC1292 Installation Procedure for version I1.605.14.e - Release 9.1
TC1308 Technical Release Note of VoWLAN 4.2.1 for OmniPCX Enterprise
TC1319 Installing and using the OmniPCX Enterprise PC Installer v2.26 software
TC1321 Patch2 for version 5.1.06.03.c Release 5.1.1
TC1330 Booting issue of GD/GD2 or IP Terminals in OmniPCX Enterprise R9.1

Ed. 01 / 28 May 2010

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

3.

FEATURES AND SPECIFIC PROCESS

3.1

Features under PCS in version I1.605.16.c

Authentication 802.1x TLS for IP Touch 40x8 sets

DSLAM / Triple Play
IBM Blade Center Quotation & Ordering process for BPs
IP DR-Link on Passive Call Server - OmniPCX Enterprise Rel. 8.x and 9.0
SIP Trunking
VoWLAN on non-Alcatel-Lucent WLAN infra R9.1
PCS = 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.

3.2

Features in test

SIP Trunking.
New carriers have begun a validation.

TC1349

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

4.

CONTENT OF THE SOFTWARE PACKAGE

The software package contains the OmniPCX Enterprise I1.605.16.c application.

The different versions of the OmniPCX Enterprise application modules are:
Linux
: 67.0
Linux Package
: 67.10
swinst
: 2.58.0
PC Installer
: 2.26
OmniPCX Enterprise R9.1 : I1.605.16.c : I1.605 complete version
I1.605.16 static patch
I1.605.16.c dynamic patch
SI1.605.16.c 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 IP Telephony > Software download > Alcatel-Lucent OmniPCX
Enterprise (including 4400)> Release 9.1 > Request for Security Patch Access.
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
Version I1.605.16.c(DVD)

Reference
27730 ABAC

Secured Version SI1.605.16.c

(DVD)
System voice guides v5.3
OmniVista 4760
R5.1.06.03.c_Patch2 - Release
5.1.1
SIP Device Management Server
1.2.000.020 - Release 1.2

27731 ABAC
3BA 57423 AAAG
3BH 11632 AJAC

3BH 11761 AAAD

MD5 checksums (1)

2ffa7916f828ada3fd9238bb919511a6
*Image_R91_I160516c.iso
3f99ed1f09af0ef80d40c34e0fe91e2a
*Image_R91_Si160516c.iso
a0c115fd1481754ecb32d084b4aef895
*Image_4760_R510603c_Patch2.iso (2)
392937c3530b40f1101d040631483065
*image_dm_12000020.iso

(1) Before installing the software, we strongly advise you to check the integrity and authenticity of the
software. For detailed information about checksums, please refer to the technical communication
TC1271 Checks for integrity and authenticity of downloaded software.
(2) This checksum concerns only the DVD containing the OmniVista 4760 software Release
R5.1.06.03.c_Patch2.

Ed. 01 / 28 May 2010

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

Note
PSP software (Phone Set Programming) is not delivered with I1.605.16.c and SI1.605.16.c DVD
versions.
To get it, download the 5.0.000.540 version available on BPWS
(https://www.businesspartner.alcatel-lucent.com), in section Technical Support Telephony /
Download Software / Alcatel-Lucent OmniPCX Enterprise (including 4400) / Published / Phone Set
Programming.
This version is compatible with OmniPCX Enterprise Release 9.1.
List of binaries in version I1.605.16.c
The new binaries of the version are in bold characters.
Released R9.1 Versions
I1.605.14.e
I1.605.16.c
Binaries relative to system
bios CPU5 Step3 (3)
bios CPU6 Step2 (1)
3BA24095AAAB07_4.7
bios CPU7
3BA 24115 AAAA16_3.02
bios CS
10.14
bios GD
10.14
bios CS-2 (AMI)
3EU24009 AAAA01_9.0
io1n
16
io2
4.6
io2n
5.17
linux_patch
67.5
67.10
obca
1.5
pc_install
2.26
swinst (2)
2.57.0
2.58.0
Binaries relative to DECT
dect4
7.9
dect8
1.26
ibs_appli_ng
48.07
49.03
ibs_boot_ng
71
ibsng
18.06
rbsng
53.0
startibsng
0.71
Binaries relative to compression boards
binintip_appli
14.20
14.23
bindsintip
4.37.2
bindsintip2
3.4
3.42
intip_linux
1.16
bootintip
6.10
mg_appli
44.34.1
45.4
binmcv
3.9.0
binmcv2
3.4
mg_version_country
1.11.11
1.11.12
mg_linux
8.1
Binaries

TC1349

10

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

Released R9.1 Versions

I1.605.14.e
I1.605.16.c
mg_platform
8.4
flashdriver
2.2
dsp_firmware
81.00
ioip
4.07
lio_comp2
3.40
rlio_comp2
3.27
mg3
2.18
3.02
intip3
2.18
Binaries relative to sets
bin40x8
4.20.60
4.20.70
bindatanoe
4.20.60
4.20.70
bin40x8G
4.50.60
4.20.71
bindatanoeG
4.20.60
4.20.71
noesip
2.00.81
2.01.10
binnoeuax9
3.81.00
binnoeua19
3.81.00
jpn_4068
1.00.01
jpn_40x8
1.00.00
jpn_40x9
1.00.01
kor_4068
2.00.00
kor_40x8
2.00.00
kor_40x9
2.01.00
chi_4068
2.01.00
chi_40x8
2.01.01
chi_40x9
2.01.01
ipphone
2.31
tscip
5.2
tscipv1S
3.0
Secured binaries
bin40x8
4.25.60
4.25.70
bindatanoe
4.25.60
4.25.70
bin40x8G
4.25.60
4.25.71
bindatanoeG
4.25.60
4.25.71
SM modules (Thales)
2.2.03
(4)
mg_appli
44.84.1
45.4
security Thales
1.0
sign.verif.
security Thales
1.1.01
1.1.02
library
mg3
2.68
3.02
intip3
2.68
3.02
Binaries relative to boards
brapra
2.06
c1nvgpa2
3.3
c1nvua
4.9
Binaries

Ed. 01 / 28 May 2010

11

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

Released R9.1 Versions

I1.605.14.e
I1.605.16.c
c1nvz32
3.0
cpl2dpnss
1.11
dpnss
2.3
dpnssnv
2.2
dpt1
2.05
dsp_emtl24021
3.01
dsp_gpa
2.01
dsp_vgu
1.5
dsp0Z32
1.02
dsp1_gpa2
1.09
dsp1nddi2
2.01
dsp2_gpa2
1.10
gpa2tns
1.10
1.11
gpa
2.24
intof
1.24
1.25
intofssync
1.05
intof2
2.2
2.3
ivrZ24
2.0
lia
4.17
lioebbc2
3.05
lio b/p/x
3.25
mic2
2.31
nddi
2.7
nddi_in
2.7
nddi2
2.21
2.22
nprae
2.06
pcm2_ru
1.6
pra
2.06
pra2
2.24
rma
3.04.04
tonesnv
3.0
ua
3.13.9
uscvg
2.9
Binaries relative to attendants
fbc
2.13
mapacs2
2.01
ta/mac
4.7
ta/pac
2.01
Binaries relative to 4760i
4760i
2.3.01.00
Binaries relative to VoWLAN
noemipt_r2
109.025
noemipt_r3
120.021
Binaries

1 The delivery of a new CPU6 Bios requires to reboot the PABX after installing the dynamic patch.

TC1349

12

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

2 You should connect to swinst to complete its installation.

3 CPU5 Step3 is no longer supported from Release 8.0.
4 SM Modules Thales: this is the reference seen in mgr.

5.

LOADING THE SOFTWARE

5.1

Complete loading of the I1.605 version and the I1.605.16 and I1.605.16.c
patches

To install the I1.605 complete version and the I1.605.16 and I1.605.16.c patches, refer to the
technical communication TC1319 Installing and using the OmniPCX Enterprise PC Installer v2.26
software.
It is necessary to use the software OmniPCX Enterprise PC Installer v2.26 or higher during
the complete installation with CS-2 (this software is available on BPWS) and GD-3.
REMINDER
Each Bios flashing operation requires to switch off the CPU6 with the M/A button to
take it into account and a reboot of the PABX.

5.2

Sites with the "IP Touch Security" feature: Loading procedure of SSM and MSM
boxes after upgrading in SI1.605.16.c

5.2.1 Migration with SSM & MSM boxes in version 1.3.xx

CAUTION
Sites using "IP Touch Security Solution" feature (Encryption) must follow a specific procedure to
update the IP Touch security boxes.
SSM & MSM downloading procedure after an upgrade in R9.1
After upgrading in SI1.605.16.c and with the RUNTEL done, you must update the IP Touch Security
boxes (MSM, SSM) as follows:
1 Check that the version 2.2.03 is managed in mgr.
2 Enter the config.BT command.
3 Reboot (with Off/On button) each SSM and MSM box to allow the downloading of the new
binary 2.2.03 (the config.BT file has been modified to take in account the IP Touch Security in
network feature. This enhancement is available only from the version 1.6.02).
Notes
If the system is duplicated, it should be better to stop the Stand-By CPU before installing the Main
CPU.
Encryption in network: For the link encryption (Inter node link) of SI1.605.16.c installations,
generate the file config_BT.cfg at each activation or un-activation of the link encryption.

Ed. 01 / 28 May 2010

13

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

5.2.2 Migration with SSM & MSM boxes in version 1.4.xx, 1.6.01, 2.x.0x
After upgrading in SI1.605.16.c and with the RUNTEL done, you must update the IP Touch Security
boxes (MSM, SSM) as follows:
1 Check that the version 2.2.03 is managed in mgr.
2 Update the SSM & MSM boxes. Two ways are available:

either reboot (with Off/On button) each SSM and MSM box,

or re-generate the Config_BT.cfg file.

3 Check that each SSM and MSM box has been downloaded with the new version:
enter the info v command (to be entered for each box).
Note
To connect from the CS to the active MSM, you must mandatory use the b option to indicate the CS
physical address.
Example: telnet b @_IP_Physical_CS @_IP_MSM

5.3

Swinst 2.58.0

You should connect to swinst to complete the installation.

6.

RESTRICTIONS AND REMARKS

6.1

Loading the version with 40 GB or 60 GB hard disks

The initial loading of 40 GB or 60 GB hard disks must be performed with the installation of the
complete version, of static patch and dynamic patch (i.e. with the PC installer application, at version
telephone level, you should select I160516c).
You must follow this procedure to be able to partition the disk otherwise after a
switch of a partition, the disk no longer restarts.
The various references of the 40 GB disk are:

Catalog reference
Code
Alcatel reference
Manufacturer reference

For CPU6/CPU7
3BA 27013
3BA 27013 ABAL
1AF 11417 AAAA
MK4032GAX TOSHIBA

For CS
3EH 76031
3EH 76031 ADAE
1AF 11417 AAAA
MK4032GAX TOSHIBA

For more details, refer to the technical communication TC0771 Installation of Toshiba 40 GB hard
disks.
The various references of the 60 GB disk are:

Catalog reference

TC1349

For CPU6/CPU7
3BA 27013

14

For CS
3EH 76031

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

Code
Alcatel reference
Manufacturer reference

3BA 27013 ABAN

1AF 14826 AAAA
HTE 541660J9AT0 HITACHI

3EH 76031 ADAF

1AF 14826 AAAA
HTE 541660J9AT0 HITACHI

Installation is identical to 40 GB disks.

6.2

4760i availability and support

By default 4760i is not activated. To activate 4760i, you need to update the Use 4760i flag in
System Parameter and reboot the CPU. Such activation option was no more available in following
PCX versions:
R9.0: H1.301.38 up to H1.301.40
R9.1: I1.605.12 up to I1.605.15
With some support conditions, we have now fit back the 4760i option as of:
R9.0: H1.301.41
R9.1: I1.605.16
The reintroduction of 4760i is done with following support conditions:
Usage is reserved for pre-installation of PCX under Business Partner control and should not be
used by End customer.
No improvement is done or planned.
No security update will be done (as stated in point 1, the 4760i tool is not designed for
production environment and end customer usage).
No update to support latest Windows OS or Java version is planned.
Any minor and major issue which could be considered as rendered by other tool will be
rejected.
This concerns for instance: graphical view of Device key management, backup
4760i is mainly used to inject mass data through a grid management.
End customer who needs to use a graphical interface to manage its PCX must be equipped of 4760
software.
Note
To make easier the launching of one or several 4760i client version use this method:
Install the related java version used by 4760i.
Install 4760i software on your PC (4760iClient.exe), you will get the c:\4760i folder.
Rename it as c:\4760i_R9.1 for instance.
Copy c:\Program Files\Java\jre1.5.0_12 folder to
c:\4760i_R9.1\lib\ext\jre15
Edit c:\4760i_R9.1\lib\ext\runconfig.bat
Change the startup line :
%START% ..javaw.exe
by
%START% jre15\bin\javaw.exe

Ed. 01 / 28 May 2010

15

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

This way:
You can host several java versions on your PC and have a dedicated java for 4760i usage.
You can install several 4760i versions and use one at a time.
You have a better performance of the 4760i application.

TC1349

16

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

7.

NEW FEATURES AVAILABLE ON RELEASE 9.1

For more information, refer to the System documentation.

7.1

From I1.605.16.c version

7.1.1 SLI-2 boards

The new SLI-2 boards: SLI4-2, SLI8-2 and SLI16-2 are only supported from version I1.605.16.c.
SLIx-2 board of Common Hardware rack:
Allows the user to connect up to 16 Z devices (Analog sets or modems or fax machines).
Offers CLASS facility to the users.
Provides a new service - Calling Part Control [CPC].
CPC (Calling Party Control) is a signal sent by a terminal to indicate that the "Calling Party" has hung
up. It's usually called "Open Loop Disconnect".
The CPC signal tells the SLI-2 board equipment that the outside party has hung-up, it is a very
important feature especially when communicating with voicemail or similar systems that need to stop
recording when the calling party hangs up.
For more information, refer to the updated System documentation.
7.1.2 New Appliance Server HP DL320 G6
The Hewlett Packard DL320 G6 Appliance Server is only supported from versions I1.605.16.c and
H1.301.42.a.

Characteristics of Hewlett Packard DL320 G6 Appliance Server reference 3BA27704CA:

Form factor/height: Rack/1U
1 Processor: Xeon E5504 Quad Core 2.0 GHz / 4MB L3 - 2 * 4.8 GT/s QPIs - no HT - no
Turbo - 800MHz DDR3 - 80W
Memory: 2GB PC3-10600 (1* 2GB dual-rank Unbuffered DIMM)
Expansion slots: 1 * PCI-Express x4 low-profile + 1 * PCI-Express x16 - full length / full height
Disk bays: 1 HDD S-ATA (Serial Advanced Technology Attachment) 160 GB 3"5 in Simple
Swap (SS) thus not Hot-swappable
Maximum internal storage: 160 GB
Network interface: 2 embedded GbE NICs
Power supply: 1 x 400W non-redundant AC power
Hot-swap components: HDD : NO
Redundant array of independent disks (RAID) support: NO, not on Simple Swap model.

Ed. 01 / 28 May 2010

17

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

7.1.3 New Appliance Server IBM X3250 M3 (Maokong)

The IBM X3250 M3 Appliance Server is only supported from version I1.605.16.c and H1.301.42.a
minimum

Characteristics of IBM X3250 M3 Appliance Server reference 3BA27582CA:

Form factor/height: Rack/1U
1 Processor: Celeron G1101 2.26GHz/1066MHz DualCore
Memory: 1GB (1x1GB, Single Rankx8) PC3-10600 CL9 ECC DDR3 1333MHz LP UDIMM
Disk bays: 250 GB 7200 RPM 3.5"" Simple-Swap SATA II
Network interface: 2 embedded GbE NICs
Power supply: 1 x 351W non-redundant AC power
Hot-swap components: HDD
7.1.4 PCS download in parallel mode
As of version I1.605.16.c, OmniPCX Enterprise allows to perform the software update (immediate or
scheduled) of many Passive Communication Servers in parallel mode instead of sequentially.This
software download in parallel mode is provided by OmniVista 4760 R5.2 (not released yet).
For more information on software update using OmniVista 4760, see section 9 Maintenance of the
OmniVista 4760 Administrator Manual.
7.1.5 Wake up call customization
As of I1.605.16.c, the new Wake Up Guide Option system option is created for wake up call
guide configuration. With the new option, users can manage and personalize the wakeup call guide
in system independently on the 46x5 voicemail.
This new system option is under System -> Other System Param. -> Local Features
Parameters -> Wake Up Guide Option would provide 3 options to control the guide which
would be used:

If system option = 0 (default)

We use voice mail both in wake up reminder execution and programming time.

If system option = 1
We never use voice mail in both cases

If system option = 2
We use voice mail during programming time and use voice guide at execution time.

For more information, refer to the updated System documentation.

TC1349

18

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

7.1.6 Logs sent in real time

As of I1.605.16.c, a new feature provides ability to send Management logs to an external server
using an application developed by Professional Services. This external server IP address and Port
configuration can be configured under Applications -> Extern Management Logs.
Management logs are being stored in history files as of current implementation. If External Server is
connected to OmniPCX Enterprise, OmniPCX Enterprise will send these logs in form of UDP packets.
There will not be any acknowledgement for this data.
7.1.7 Dial By Name overflow to LDAP
As of I1.605.16.c, the new LDAP direct access system option allows to perform the dial-byname search directly in LDAP server instead of searching in local directory.
This new system option is under System
parameters

->

Other

System

Param.

->

System

For more information, refer to the updated system documentation.

7.1.8 Unset the Redial Feature
As of I1.605.16.c, the new Deactivate Redial Key system option for Redial Key allows to
make the Redial key a manageable one. The Redial Key is made ineffective only if both the System
option for Redial Key is forbidden and the parameter for Redial Prefix is also forbidden
(RedialLast Number) in Phone feature COS.
This new system option is under Specific Telephone Services -> Deactivate Redial
Key.
For more information, refer to the updated System documentation.
7.1.9 DECT encryption on IBS/Crystal Hardware
As of I1.605.16.c (including the ibs_ng v49.03 encryption binary), Alcatel OmniPCX Enterprise
provides three levels of security for establishing and maintaining DECT calls. These levels correspond
to the following three modes:
1 "Identity" mode
2 "Authentication" mode
3 "Encryption" mode
Before Release 9.1, the system's security level is limited to "Authentication" mode for
a DECT system in IBS configuration.
Pre-requisites:
Modification in the IBS software to open the DECT standard encryption as available on RBS.
All RF bands, World Wide.
Only with Crystal hardware (synchronisation by DTM needed).

Ed. 01 / 28 May 2010

19

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

OmniPCX Enterprise management to allow the user to set the DECT security level to
encryption, the software encryption of the IBS is activated by a message from OmniPCX
Enterprise.
The encryption binary ( v49.03) is for IBS NG (not possible with "old" IBS 1G).
MR100/200/300/400 mobiles must normally operate.
Mobiles must be reinstalled to take into account the encryption.
Actis software lock for DECT encryption.
For more information, refer to the Technical Communication TC0274 DECT compatibilities.
7.1.10 Voice mail password length
As of I1.605.16.c the maximum length of the administrative voice mail password is increased from
four to eight characters while managing from mgr.
7.1.11 Cellular Voice Mail detection timer
While calling a tandem (fixed set with a Mobile Remote extension twin set association), A problem if
the External Cellular Client is unreachable (set switched off or out of coverage) the call is
automatically forwarded to the voice mail provided by the public operator (if activated) and the main
set stops ringing.
As of I1.605.16.c, the new timer no. 373 can be configured in the PCX to bypass public operator
voice mail forwarding and allow user to take the call from the main set.
When the call presented to the External Cellular Client is answered before timer expiration, it is
identified as an automatic answer from the voice mail and the call is cancelled. The main set
continues to ring. The user can take the call from the main set of the tandem.
This feature is available for External Cellular Clients accessible through ISDN, H.323 and SIP
trunking.
The call presentation to the twin set association depends on the timer no. 373.
By default, timer no. 373 is set to 0.
Timer value different to 0: the timer is activated and it allows to bypass the Cellular Client forwarded
to voice mail.
In case of MyIC mobile on Blackberry and Windows mobile, the feature Cellular
Voice Mail detection timer cannot be used. The timer no. 373 must be set to 0.
This restriction will be resolved in a future patch.
For more information, refer to the updated System documentation.
7.1.12 Supervision with Free Desktop
As of I1.605.16.c, it is possible to move the supervised set to another node of the same network
when supervisor set is busy.

TC1349

20

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

7.1.13 Call Transfer (USA Conference Mode)

As of I1.605.16.c, enabling USA Conference Mode allows to display the Transfer key on a set
already in conversation with a party.
This parameter is under System
Parameters.

->

Other

System

Param.

->

Local

Features

True: The call transfer can be initiated in conversation (one active call and no call on hold).
The user must press the Transfer key to dial a directory number (consultation call) and press
the Transfer key a second time to complete the call transfer.
False (default option): The call transfer can only be initiated during a consultation call or
three-party conference. The Transfer key only appears during a consultation call.
For more information, refer to the updated system documentation.
7.1.14 3 party conference (USA Conference Mode)
As of I1.605.16.c, enabling USA Conference Mode allows to display the Conference key on a set
already in conversation with a party.
This parameter is under System
Parameters.

->

Other

System

Param.

->

Local

Features

True: The three-party conference can be initiated in conversation (one active call and no call
on hold). The user must press the Conference key to dial a directory number (consultation call)
and press the Conference key a second time to complete the three-party conference
False (default option): The three-party conference can only be initiated during a consultation
call. The Conference key only appears during a consultation call
For more information, refer to the updated System documentation.
7.1.15 Management Event on Forward cancellation/activation
As of I1.605.16.c, CMISE events are generated when a subscribers forward, DND, lock or overflow
states changed. No matter the state change comes from phone set or from management tools like
mgr/4760, ACAPI will get the event and communicate with external applications. The external
applications will receive these events and decide what to do.
For more information, refer to the updated System documentation.
7.1.16 FlexOffice: forwarding cancelled
As of I1.605.16.c, the new NOEIP INSERV Forwarding Cancelled system option allows to
cancel the forward of a NOE IP set automatically, when the user comes back from out of service to in
service.
This implementation is specific to making NOE IP sets out of service by using the prefix or deleting
MAC address.
So whenever the user makes the set out of service by using inserv/outserv prefix or deleting the MAC
address of the set and made back into service, then whatever forwarding is been enabled in the set
will be cancelled automatically.

Ed. 01 / 28 May 2010

21

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

The new NOEIP INSERV Forwarding Cancelled system option set to TRUE to validate the
feature is under System option -> System parameters -> Other System Parameters
-> Local Features Parameters.
For more information, refer to the updated System documentation.
7.1.17 UDP to TCP switching for long messages
As of I1.605.16.c, the new Move to TCP parameter is introduced in SIP proxy layer (SIP ->
Proxy)
True: Allows OmniPCX Enterprise switches to TCP automatically for SIP messages longer than
1300 bytes (in compliance with RFC3261). It was OmniPCX Enterprise behavior in previous
versions.
False: Inhibits this behavior and force use of UDP only. It applies globally, for External
Gateway, and as well for SIP Extension, SIP Device and SIP External Voice Mail.
7.1.18 Multiple SIP gateways support using via header
As of version I1.605.16.c, on inbound calls, a new feature enables "Via" header checking in order to
select the proper external gateway to handle the call. It comes in addition to existing matching rules.
Next, when an inbound request is received it is routed to the right external gateway using the
following rules:
If the "P-Asserted-ID" header is present, and its domain part matches with the "Remote
Domain" of a given External Gateway, the call is processed using this gateway.
If there isnt any "P-Asserted-ID" header, and the domain part of the "From" header matches
with the "Remote Domain" of a given External Gateway, the call is processed using this
gateway.
If one or several "Via" header are available, and the domain part of one of the URLs matches
with the "Remote Domain" of a given External Gateway, the call is processed using this
gateway.
Multiple gateways routing on "Via" header has to be activated with Via Header_ Inbound
Calls Routing parameter under System -> Other System Param. -> SIP
Parameters.
7.1.19 SIP QoS tagging support
As of I1.605.16.c, a new feature will provide ability to store the IP QoS parameters ("802.1 priority"
and "TOS/Diffserv") in the SIP stack at the time of stack initialization, so that the stack can open
sockets with the right QoS parameters.
These parameters will be used for all SIP messages from OmniPCX Enterprise. The IP QoS
parameters are fetched from the CPU IPs respective IP domain. If no IP domain is managed, the
default domains IP QoS parameters are stored in the SIP stack.
7.1.20 Force On Net
As of I1.605.16.c, Routing Application parameter is created in external gateway to enable the
Force On Net feature. In this case OmniPCX Enterprise sends Invite message without SDP to an
external SIP server provided by Professional Services. OmniPCX Enterprise may receive 302

TC1349

22

Ed. 01 / 28 May 2010

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

responses from external SIP server for initial INVITE. In this case OmniPCX Enterprise will not
consider 302 as forwarded call. The forward notification (arrow [=>]) symbol) for internal forwards
will be removed from the display of the calling user, during the ringing state and also calling
number alone be shown in display of called user. For external forwards also, arrow symbol will not
be displayed as it exists up to now in the calling user. And also for this feature 302 responses is
mandatory from external SIP server.
Restriction
When SIP device calls the external SIP server it receives the 302 response with forwarded number's
information. And also the user display will have the forward notification (arrow [=>]) symbol)
because SIP device is treated as an external entity of OmniPCX Enterprise.
7.1.21 Interoperability with SBC 5.2.8
As of version I1.605.16.c, OmniPCX Enterprise allows to interoperate with the SBC 5.2.8.

Ed. 01 / 28 May 2010

23

TC1349

OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
I1.605.16.c RELEASE 9.1

TC1349

24

Ed. 01 / 28 May 2010