Installation Procedure OmniPCX Enterprise R12.0 Version M1.403.12.G

Release Note OmniPCX Enterprise
TC2306 ed.03 Release 12.0
Release Note & Installation procedure for

OmniPCX Enterprise R12.0 Released version
M1.403.12.G
This is the technical release of OmniPCX Enterprise with the version M1.403.12.G It corresponds to the release 12.0
It is available on Alcatel-Lucent Business Portal (https://businessportal.alcatel-lucent.com) and on DVD with the references
3BA 27860 ABAB (non secured version) and 3BA 27861 ABAB (secured version).
Technical modes for migration, new features, registered restrictions and controlled features are described in that document
: “Release note & installation procedure for version M1.403.12.G”
Revision History
Edition 01: February 3, 2017 Creation of the document

Edition 01: April 24, 2017 Release of the document in the B. Portal
Edition 02: April 25, 2017 Misc modifications (4760i ref., R11.2 instead of 12.0 + warning on disk reformatting
needed (“ch.10 Operating Mode”)
Edition 03 : : April 26, 2017 Updated to patch “G” put in GA. Chap. 15.3 : new format .doc. Rewriting of IO2 specific
management + P18 : insert new page. Chap. 21.2.5.4 (App.Serv. G9). Chap. 21.1 restrictions/ known issues : issue related
to Android 7. Chap. 11.1.1.1 : Added URL for ref. of data sheet for all NOE3G S series. CPU7s2 memory bank upgrade :
reference (Chap. 5). Chap 2 : added ref. of R12.0 general presentation. Chap 5 : Content of sw. package : ipv4-ipv6
translator new version/ref.
Legal notice:
The information presented is subject to change without notice.
ALE International assumes no responsibility for inaccuracies contained herein.
Copyright © ALE International 2017
Table of Contents
1 APPLICATION DOMAIN ........................................................................................................ 7
2 REFERENCE DOCUMENTS ..................................................................................................... 7
3 SYSTEM DOCUMENTATION.................................................................................................... 8
4 INTRODUCTION TO RELEASE 12.0........................................................................................... 9
4.1 New hardware ............................................................................................................ 9
4.2 New features/ interoperability ....................................................................................... 10
4.2.1 Interworking/ Interoperability tested ......................................................................... 10
4.2.2 Virtualization ....................................................................................................... 10
4.2.3 Terminals ........................................................................................................... 10
4.2.4 Increasing provisioning level/ product limits ................................................................. 10
4.2.5 Security .............................................................................................................. 10
4.2.6 Mobility .............................................................................................................. 10
4.2.7 IP Enhancement .................................................................................................... 10
4.2.8 Call Handling features ............................................................................................ 11
4.2.9 SIP Enhancement .................................................................................................. 11
4.2.10 Infra ................................................................................................................ 11
4.2.11 Maintenance....................................................................................................... 11
4.3 Features under PCS ..................................................................................................... 11
4.4 Features availability in progress (for MDx patches) .............................................................. 11
5 CONTENT OF THE SOFTWARE PACKAGE .................................................................................. 12
6 BEFORE STARTING ............................................................................................................ 17
6.1 Compatibilities/ Product Limits ...................................................................................... 17
6.2 Hardware : phased-out boards ....................................................................................... 17
6.3 Conditions for installation in ABC network ......................................................................... 17
6.4 Reminder on applications & functionnalities ...................................................................... 18
6.5 Applications and functionalities dependent on CPUs and hardware platform used......................... 19
6.6 VoIP network conformity check ...................................................................................... 21
6.7 Firmware upgrade ...................................................................................................... 21
6.8 Recommendations about security .................................................................................... 21
6.9 DECT....................................................................................................................... 21
7 COMPATIBILITIES/ PRODUCT LIMITS ....................................................................................... 22
7.1 Generalities .............................................................................................................. 22
7.2 Interoperability tests status .......................................................................................... 23
7.3 OXE compatibilities in ABC network ................................................................................. 23
7.4 OT compatibility ........................................................................................................ 24
7.5 Common hardware & Crystal hardware mixity .................................................................... 24
7.6 IP sets compatibility .................................................................................................... 24
OmniPCX Enterprise - Release 12.0

Release Note & Installation procedure for OmniPCX Enterprise R12.0 Released version M1.403.12.G
TC2306 ed.03
Copyright © ALE International 2017 page 2/118
7.7 Subdevices on older sets............................................................................................... 24
7.8 OEM/External equipment compatibility ............................................................................ 25
7.8.1 UPS ................................................................................................................... 25
7.9 SIP sets, Dect sets, other sets … Latest firmware tested. ....................................................... 25
7.10 Genesys Compact Edition : special case .......................................................................... 26
8 CLIENT INFORMATION ........................................................................................................ 26
8.1 New ergonomics and operations ..................................................................................... 26
8.2 Reminder of changes appeared in Release R12.0 ................................................................. 27
8.3 Reminder of changes appeared in Release R11.2.x ............................................................... 27
8.5 Reminder of changes appeared in Release R11.0.1 ............................................................... 27
8.7 Reminder of changes appeared in Release 10.1.1 ................................................................ 27
8.8 Reminder of changes appeared in Release 10.1 ................................................................... 28
8.12 Reminder of changes appeared in Release 8.0 and 8.0.1 ...................................................... 28
8.15 Reminder of changes appeared in Release 6.1.1 ................................................................ 29
8.16 Reminder of changes appeared with R4.2 ........................................................................ 29
9 PREPARATION/ OPERATIONS ............................................................................................... 29
9.1 Checking compatibility ................................................................................................ 29
9.2 Call Server compatibilities ............................................................................................ 30
9.3 Voice guides ............................................................................................................. 30
9.3.1 System voice guides ............................................................................................... 30
9.3.2 Alcatel 4645 voice guides ........................................................................................ 31
9.4 ACTIS, eLP & software locks .......................................................................................... 32
9.5 Before saving the database ........................................................................................... 33
9.5.1 Rebuilding the database before saving ........................................................................ 33
9.5.2 Tickets ............................................................................................................... 33
9.5.3 From crystal to common hardware ............................................................................. 33
9.6 4645 ....................................................................................................................... 33
9.7 Special cases : migrating old versions ............................................................................... 34
9.8 Getting the software ................................................................................................... 34
10 OPERATING MODE ........................................................................................................... 34
10.1 New installation ....................................................................................................... 35
10.2 Updating from R5.1.x, R6.x, R7.x, R8. x, R9.x, R10.x, R11.0/11.0.1/R11.1/R11.2 up to R12.0 ........ 35
10.3 OmniPCX 4400 migration to R12.0 .................................................................................. 35
10.3.1 Use of the hardware or software key ......................................................................... 36

TC2306 ed.03
10.3.2 Crystal hardware compatibility with an Appliance Server ................................................ 36
11 LOADING THE SOFTWARE .................................................................................................. 36
11.1 Installation.............................................................................................................. 36
11.2 Use of ALEDS ........................................................................................................... 36
11.3 Secured systems ....................................................................................................... 36
11.3.1 Security activated by default during an installation ....................................................... 36
11.3.2 Installation of a secured system for VoIP encryption ("IP Touch Security" service) .................. 37
11.4 Using the Remote Download ......................................................................................... 38
11.4.1 Reading the hardware key, CPU-id, CCS-ID ................................................................. 38
11.4.2 Creating a blank database ...................................................................................... 38
11.4.3 Restoring the database and site tickets ...................................................................... 39
11.4.4 Restoring Chorus/Linux data ................................................................................... 39
12 TRANSLATIONS .............................................................................................................. 39
13 Installing/checking OPS/Actis files ...................................................................................... 40
13.1 Procedure : ............................................................................................................. 40
13.2 Checks on physical CPUs ............................................................................................. 41
13.3 Checks on virtualization .............................................................................................. 41
13.4 Checks on Cloud Connected system ................................................................................ 41
14 SYSTEM MANAGEMENT ..................................................................................................... 42
14.1 General : ................................................................................................................ 42
14.2 Special case of IO2N boards (CPU7s2) ............................................................................. 42
15 COMPULSORY MINIMUM ADDITIONAL DATABASE MANAGEMENT ..................................................... 42
15.1 Reminders............................................................................................................... 42
15.2 Reminder for ABC networked sites migrating from Release < 7.x ............................................ 43
15.3 Important management if IO2N is present ........................................................................ 43
15.4 Synchronization ........................................................................................................ 44
15.5 Some system parameters to check ................................................................................. 44
15.5.1 Direct RTP ......................................................................................................... 44
15.5.2 Frame VoIP (Enhanced quality voice)......................................................................... 44
15.5.3 Direct RTP for H323 terminals ................................................................................. 45
15.5.4 Inter-node protocol H323 ....................................................................................... 45
15.5.5 Pre-login (V120 on IO2n boards) ............................................................................... 45
16 STARTING UP THE CPU IN ITS ENVIRONMENT ON SITE ................................................................ 45
16.1 Downloading the couplers and sets ................................................................................ 45
16.2 Sites with the "IP Touch Security" feature: Migration from R6.2 or R7.x to R12.0 with SSM & MSM
boxes in version 3.5.01.a ................................................................................................... 46
17 CHECKING CORRECT OPERATION ......................................................................................... 46
18 CHECKS IN A VIRTUALIZED VMWARE INFRASTRUCTURE .............................................................. 47
19 NEW HARDWARE AND FEATURES IN RELEASE 12.0 .................................................................... 47

TC2306 ed.03
19.1 New hardware .......................................................................................................... 48
19.2 New features : description/explanation & management ....................................................... 50
19.2.1 New OXE incidents (sipmotor/ Cloud Connect) ............................................................. 50
19.2.2 CPU7(S2) installation procedure modification (bios update) ............................................. 50
19.2.3 4645 (users, messages duration …) ............................................................................ 53
19.2.4 New noe sets ...................................................................................................... 55
19.2.5 Virtualization ..................................................................................................... 55
19.2.6 Terminals .......................................................................................................... 58
19.2.7 Increasing provisioning level ................................................................................... 59
19.2.8 Security ............................................................................................................ 59
19.2.9 Mobility ............................................................................................................ 63
19.2.10 IP Enhancement ................................................................................................. 64
19.2.11 Call Handling features ......................................................................................... 64
19.2.12 SIP Trunking features .......................................................................................... 72
19.2.13 INFRA CLOUD .................................................................................................... 75
19.2.14 WBM (Web Based Management) .............................................................................. 76
19.3 Features under PCS ................................................................................................... 79
20 COUNTRIES IN WHICH RELEASE 12.0 IS TECHNICALLY RELEASED ................................................... 79
21 REMARKS & RESTRICTIONS ................................................................................................ 85
21.1 RESTRICTIONS, KNOWN ISSUES ...................................................................................... 85
KVM .......................................................................................................................... 86
Other virtualized systems : ............................................................................................. 87
21.2 COMMUNICATION SERVERS ........................................................................................... 87
21.2.1 Call Server CPU ................................................................................................... 87
Hard drive .................................................................................................................. 87
21.2.2 UPS.................................................................................................................. 87
21.2.3 Blade Center (& others) ......................................................................................... 87
21.2.4 Passive Communication Server ................................................................................ 88
21.2.5 Appliance Servers : Bill Of Material (BOM) .................................................................. 89
21.3 IP CRYSTAL MEDIA GATEWAY ........................................................................................ 93
21.4 MEDIA GATEWAY ....................................................................................................... 94
21.4.1 GD/GA boards ..................................................................................................... 94
21.4.2 INTIPB board ...................................................................................................... 94
21.4.3 Remote connection towards GD/GA/INTIP boards ......................................................... 94
21.4.4 NGP boards (GD3/GA3/INTIP3) ................................................................................ 95
21.4.5 OMS (remote access & ESXi configuration rules) ........................................................... 96
21.5 VoIP ...................................................................................................................... 97
21.6 ABC-F IP TRUNK GROUP .............................................................................................. 99
21.7 SIP SETS ............................................................................................................... 100
21.8 OTHER SETS........................................................................................................... 101
21.8.1 IP Phone V1 – V1S .............................................................................................. 101
21.8.2 IP Phone V2 (e-Reflexe) ....................................................................................... 101
21.8.3 Alcatel series 8 & 9 sets ...................................................................................... 101
21.8.4 Alcatel-Lucent 8082 My IC Phone ........................................................................... 104

TC2306 ed.03
21.8.5 MIPT 300 & 600 handsets ..................................................................................... 104
21.8.6 DECT .............................................................................................................. 105
21.8.7 IP DECT system ................................................................................................. 105
21.8.8 UA Extender 4051/4052 ....................................................................................... 106
21.8.9 NOE3G (premium ip phones) ................................................................................. 106
21.8.10 NOE3G EE....................................................................................................... 106
21.8.11 OTC Android Smartphone ................................................................................... 107
21.9 IP TOUCH SECURITY FEATURE ..................................................................................... 107
21.10 SIP TLS FOR EXTERNAL GATEWAY ............................................................................... 108
21.11 APPLICATIONS ...................................................................................................... 108
21.11.1 OmniVista 4760 & 4760i ..................................................................................... 108
21.11.2 SIP Device Management Server ............................................................................. 108
21.11.3 AAS (Audio Station) ........................................................................................... 109
21.11.4 External Voice Mail ........................................................................................... 109
21.12 Security .............................................................................................................. 109
21.12.1 Voice mail 4645: access blocking after bad password attempts ..................................... 109
21.12.2 Voice mail 4645 : minimum user password length option ............................................. 110
21.13 CLIP ................................................................................................................... 110
21.14 DIRECTORY .......................................................................................................... 111
21.15 BOARDS .............................................................................................................. 112
21.16 MISCELLANEOUS .................................................................................................... 112
22 TECHNICAL SUPPORT ..................................................................................................... 116
23 Interoperability with Third-Party applications ...................................................................... 116

TC2306 ed.03
1 APPLICATION DOMAIN
This document and its appendices describe:

 The installation method with compatibilities & eventual warnings
 Some restrictions and remarks
 The new features brought by that release
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.
The “crqmsxxxxxx” ou “CR-OXExxxx” notations in this document are internal references to ALE RnD
anomaly reports database.
This version M1.403.12.G differs from the previous “.D” by several dynamic patches. This version is now
loaded at factory. Previous versions should upgrade
Warning It is important to read carefully the following chapters :

Remarks & restrictions
Call Server compatibilities
2 REFERENCE DOCUMENTS
General prelease presentation:
OmniPCX Enterprise Release 12 Presentation
Technical communications:
Most of the old technical communications are not mentioned anymore. Refer to precedent document same
section (Release 12.0 – Ch.2 REFERENCE DOCUMENTS) if needed.
TC0778 Migration OmniPCX 4400 to OmniPCX Enterprise

TC0779 Synchronization of the system after migration to OmniPCX Enterprise with Appliance Server
TC1255 4008 / 4018 SIP set deployment with OmniPCX Enterprise
TC1271 Checks for integrity and authenticity of downloaded software

TC2306 ed.03
TC 1862 8002/8012 OXE R11.0 Manual Installation
TC 1868 Multicodec evolutions in OXE Release 11.0: Database translation
TC 1865 OT Connection 8082 : firmware update for noe mode purpose (for non noe compatible firmwares)
TC 1897 installation AS HP DL320E G8v2
New :
TC2312 : “OXE mgr Configurations Management Evolution”. This document describes the new parameters and
the modified parameters introduced in all the releases starting from k1.520 (TC to be released soon)
Offer documents (See chap. 8 for direct links) :

MLE CrossCompatibility ref: ENT_MLE_016252
OTsuite-Hosting-Virtualization Ref: ENT_MLE_015903 including a chapter “USB/IP dongle solution”
OXE system documentation (Ref. in next Chap.)
Product limits : “oxe_r9tor11.2_product_limits_ent_mle_016224_6c_en_0.xlsx” ref: ENT_MLE_016403
Phase in
 eFlash: EF-Phase-In-C088-EN-VAD-SP-DR - OpenTouch Suite for Mid-sized and Large Enterprises:
 eFlash: EF-Phase-In-C085-EN - IP Premiun Deskphones s series
 eFlash: EF-Phase-In-C084-EN - Alcatel-Lucent 8232s DECT Handset
Phase-out
 eFlash: EF-PhaseOut-C086-EN - DeskPhones End-of-Sales notification for 8028, 8068 no BT, 8068 BT
Premium DeskPhones
3 SYSTEM DOCUMENTATION
System documentation is no more provided as a CDROM. R12.0 documentation download is available at the
Business Portal :
https://businessportal2.alcatel-lucent.com/technical-documentation-library
(Customer Support > Technical Support > Technical Documentation Library)
Previous R11.2 documentation still available at the same place.

TC2306 ed.03
4 INTRODUCTION TO RELEASE 12.0
For that release 12.0 (this version M1.403.12.G) Actis is requested (software lock R12.0 and no new lock)
- Oxe version lock : lock 165 : value 45
- Oxe Beta lock 87 : value 25
Below is the corresponding levels of compatibilities for database & software corrections
DB Compatible with following static

OXE Patch Corrections level of sync
patches and their dynamics
M1.403.12.G M1.403.5 M1.403.11.a

M1.401.7 M1.401.7.d
M1.300.16 M1.300.16
L2.300.33 L2.300.33
L1.301.38 L1.301.36
K1.520.46 K1.520.45
K1.400.37 K1.400.37
J2.603.38 J2.603.38
The program of certification is available on the Business Portal
In this document you will find the steps necessary for installing version M1.403.12.G for:
 a new installation,
 an evolution from R5.0 Lx, R5.x, R6.x, R7.x, R8.x, R9.x, R10.0, R10.1, R11.0, R11.0.1, R11.1 & R11.2.x
 a migration from OmniPCX 4400 to OmniPCX Enterprise R12.0 controlled by OmniPCX 4400 CPU type or
board CS or Appliance Server (AS) or virtualized Server.
Plus the description of the new 12.0 features restrictions, features to come & misc. information.
4.1 New hardware

 New NOE3G sets :
o 8028s
o 8058s
o 8068s
o 8078s (touch screen)
 New Appliance servers :

o HP DL20 G9
o Lenovo X3250 M6 (readiness : not available today)
o They are not retrocompatible

TC2306 ed.03
See in “chap. 19.1 NEW HARDWARE AND FEATURES IN RELEASE 12.0” for a complete description.
4.2 New features/ interoperability

4.2.1 Interworking/ Interoperability tested
 OXE - OTMS interworking
 IP Touch Security Encryption with OT applications
 ABC interworking R10.1.x, R11.0.x, R11.1, R11.2.x
 8770 3.2.07
4.2.2 Virtualization
 Vmware / Esx supported versions : 5.5, 6.0 & 6.5
 KVM
4.2.3 Terminals
 New Noe sets
o 8028s
o 8058s (new design)
o 8068s
o 8078s (new design – touch screen)
 USB boost charging mode management on 8018 and new noe “S” sets
 8018 in sip mode for hospitality
 8088 NOE mode with Android OS (for MD2)
4.2.4 Increasing provisioning level/ product limits

 Increase ABCA call queue length for 4059EE
 Extend the capacity of casual conference
 Increase the size of the external telephony application table (internal)
4.2.5 Security
 Thales boxes & IPV6
o IPV6 compatible : release V4.0.14 given by Thales for SSM & MSM is embedded in release
OXE R12.0
4.2.6 Mobility
 No new feature
4.2.7 IP Enhancement
 Dynamic voice guide recording on OMS

TC2306 ed.03
4.2.8 Call Handling features
 Call duration control enhancement (Step2, first step in L2)
 Multi-device
 Rainbow. Rainbow Business offer will be available in June. Look for ALE news to discover this new offer.
o Management of the solution is done in 3 parts :
 The Cloud management plateform
 “netadmin” tool
 “mgr” tool
 Voice Mail 4645 : Security improvement
 Attendant : 4059EE version 1.7
 Loudspeaker Level Management per Terminal (PER 3088)
4.2.9 SIP Enhancement

 SIP serviceability & SIP incidents management
4.2.10 Infra
 New Linux Kernel 2.6.32
 Cloud Connect (CC) connection & registration including FTR pin code
 New appliance servers
o HP DL20 G9
o Lenovo M3250 M6 (readiness)
4.2.11 Maintenance
 Infocollect version 5.2 (includes dedicated module for new features Rainbow, Cloud Connect, WBM).
 Dedicated tools for Rainbow & Cloud Connect
4.3 Features under PCS

The following features are under PCS control. Please Fill the correcponding form to help the deployment.
 IPV6 (common hardware or crystal architecture). Feature controlled by a software lock in Actis
 Sip trunking with TLS
PCS = Premium Customer Support. The Premium Customer Support process allows the Partner Businesses to
profit of 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.
4.4 Features availability in progress (for MD1/2/3 patches)

Rainbow : availability of Business paid offer (communication to be pushed end of June)
OMS R4 VoIP G729A Framing 40ms (PEROXE-111) (MD1)
Cloud Connect (MD1)
8088 NOE mode under Android OS (MD2)

TC2306 ed.03
Forbid 4645 AA transfers to certain destinations (MD2)
Remote Agent on CMP board obsolescence : OXE requirement for replacement solution (MD2)
Leftovers from WBM (MD3)
5 CONTENT OF THE SOFTWARE PACKAGE

The software package contains the OmniPCX Enterprise R12.0
The different versions of the OmniPCX Enterprise application modules are:
 Linux : linux26_patch_109.014 + kernel 2.6.32
 swinst : 3.13.0
 PC Installer : 4.1 (check compatibilities for Windows OS)
 Aleds : 3.4.0.10
 OmniPCX Enterprise R12.0 software M1.403.12.G containing :

M1.403 complete version
M1.403.12 static patch
M1.403.12.G dynamic patch
M1.403.12.G secured patch (Note)
Note The access to secured patch is only given on request after filing the appropriate document posted on
Business Portal Customer Support > Technical Support > Software download > OmniPCX Enterprise >
OmniPCX Enterprise > All Release > Request for Security Patch Access.
DVD R12.0 REFERENCES :

3BA 27860 ABAB OMNIPCX ENTERPRISE R12.0 DVD-R
3BA 27861 ABAB OMNIPCX ENTERPRISE R12.0 SECURED DVD-R
Items :
3BA50280ABAA OMNIPCX ENTERPRISE RELEASE R12.0
3BA27860ABAB OMNIPCX ENTERPRISE R12.0 DVD-R
3BA27861ABAB OMNIPCX ENTERPRISE R12.0 SECURED DVD-R
Other :
Memory bank for CPU7s2 (upgrade to R12.0 ONLY)
Orderable item : 3BA27056AC (SDRAM 512MB for CPU7-2)
Reference of DVDs or CDs releated to R12.0 :
Reference Reference Misc

OMNIPCX ENTERPRISE R12.0 DVD-R 3BA 27860 ABAB Image_OXER12.0_m140312g.iso
Version M1.403.12.G (DVD)
OMNIPCX ENTERPRISE R12.0 3BA 27861 ABAB Image_OXER12.0_sm140312g.iso

TC2306 ed.03
SECURED DVD-R
Secured Version SM1.403.12.G (DVD)
vmFlex-2.1.100.006 for CentOS 7 if vmFlex-2.1.100.006
ESXi’s release is 5.5 or above esxi >= 5.5 Business Portal Link
or
vmFlex-CentOs5-2.1.000.093 for Esxi < 5.5 Business Portal Link
CentOS5 if ESXi release is lower than
5.5
vmFlex-CentOs5-2.1.000.093 for KVM KVM Business Portal Link
OXE IPV6-IPV4 translator DVD-R 3BA27853 ABAB-01 OST64.iso 3.03 (iso)
OXE MS APPLICATION DVD-R 3BA27802ABAB-01 OXE binary 6.02 (updated along with the OXE
Software Version 6.02 patches)
OXE MS bin (3.0.6) link (Red Hat version)
OXE MS bin (4.0) link (Suse 12 version)
OPENTOUCH 2.2.1 Boot Suse ES 12 3BH12007AGAD bootdvd.12.1.010.000.x86_64.iso

SP1 64 bits DVD-R (used for OXE MS Business Portal Link
Application installation)
OXE Software Server To be released for MD1 patch

OmniVista 8770 R3.2 Software – 3BH11670 AGAC OmniVista 8770 R3.2.07 patch A-M
Version R3.2.07
The documentation is no more provided on a
OmniVista 8770 R3.2 Documentation CD.
+ Technical doc TC2305_en-Ed01 It is available on the Alcatel-Lucent Business
(installation procedure) Portal, in the section Technical Support\
Technical Documentation Library
Before installing any 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.
(*) That Sip DM is not usable for 8002/8012 sets in hotel environment
Note PSP software (Phone Set Programming) is not delivered with the R12.0 DVDs.
PSP software is available on Business Portal (https://businessportal2.alcatel-lucent.com) in section
Customer Support > Technical Support > Software Download > OmniPCX Enterprise > OmniPCX Enterprise
> All Releases. This version is compatible with OmniPCX Enterprise RELEASE 12.0

TC2306 ed.03
List of binaries in version M1.403.12.G (including previous released .12.d)
The new binaries of the version are in bold characters.
Version 12.0
released TR Version 12.0
Binaries M1.403.12.d M1.403.12.g
System binaries
bios CPU6 Step2 3BA24095AAAB08_4.8 3BA24095AAAB08_4.8
bios CPU7 3.02 replaced by bios CPU7 Step2 3.02 replaced by bios CPU7 Step2
bios CPU7 Step2 3BA24115AAFC19_4.3 3BA24115AAFC19_4.3
bios CS 10.14 10.14
bios GD 10.14 10.14
bios CS-2 (ami) 3EU24009AAAC01_11.0 3EU24009AAAC01_11.0
io1n 16 16
io2 4.6 4.6
io2n 5.17 5.17
linux 109.014 109.016
ramdisk_patch 109.000.001 109.000.001
rainbowagent 1.11.0 1.13.0
obca 1.5 1.5
pc_install 4.1 4.1
swinst 3.13.0 3.14.0
DECT binaries
dect8 1.26 1.26
rbsng 53.00 53.00
ibs_appli_ng 49.04 49.04
ibs_boot_ng 71 71
Compression Boards
binaries
bootintip 6.13 6.13
binintip_appli 16.23 16.23
bindspintip 4.37.2 4.37.2
bindspintip2 3.45 3.45
mg_appli 46.25 46.25
binmcv 3.9.0 3.9.0
binmcv2 3.45 3.45
ioip 4.19 4.19
lio_comp2 3.40 3.40
rlio_comp2 3.27 3.27

TC2306 ed.03
dsp_lio_comp2 3.09 3.09
r_mg3 4.01, replaced by ngp 4.01, replaced by ngp
r_intip3 4.01, replaced by ngp 4.01, replaced by ngp
r_ngp3 8.10 8.10
binamcvb642x n.a. n.a.
oms 6.02 6.02
ost64 3.03 3.03
Sets binaries
noeip 4.33.81 4.33.81
noeip Gigabit 4.34.21 4.34.21
noe3gip 4.52.60 4.52.60
noe80x8S 5.00.12 5.00.13
noe8018 4.91.15 4.91.15
noe8082 4.51.03 4.51.03
noe8088 5.00.83 5.00.83
noe3guax9 4.01.31 4.01.31
noeuax9 3.81.80 3.81.80
noeua19 3.81.00 3.81.00
noesip 2.12.40 2.12.40
noe3gsip 3.00.50 3.00.50
sip80x8S 1.01.40 1.01.40
jpn_4068 1.00.01 1.00.01
jpn_40x8 1.00.00 1.00.00
jpn_40x9 1.00.01 1.00.01
kor_4068 2.01.00 2.01.00
kor_40x8 2.01.00 2.01.00
kor_40x9 2.01.00 2.01.00
chi_4068 2.01.00 2.01.00
chi_40x8 2.01.01 2.01.01
chi_40x9 2.01.01 2.01.01
ipphone 2.31 2.31
tscip 5.2 5.2
tscipvS 3.0 3.0
VoWLAN sets binaries
noemipt_r2 109.025 109.025
noemipt_r3 120.028 120.028
noemipt8_r100 5.6.1 5.6.1
Secured binaries
noeip 4.38.81 4.38.81

TC2306 ed.03
noeip Gigabit 4.39.21 4.39.21
noe3gip 4.57.60 4.57.60
noe80x8S (same) 5.00.12 5.00.13
noe8018 4.96.15 4.96.15
SM modules (Thales) 4.0.14.a : 4.0.14.a :

- V4 (bin_SM) 3.3.05 3.3.05
- V5 (bin_SM2) 3.6.03 3.6.03
- V5M (bin_SM3) 4.0.15 4.0.15
mg_appli 46.75 46.75
Thales library (mg_appli) 1.1.02 1.1.02
r_mg3 4.51, replaced by ngp 4.51, replaced by ngp
r_intip3 4.51, replaced by ngp 4.51, replaced by ngp
r_ngp3 8.60 8.60
Thales SRTP client
(intip3/mg3) 1.0.06 1.0.06
Thales VPN client
(intip3/mg3) 1.1.03 1.1.03
Boards binaries
brapra 2.06 2.06
c1nvgpa2 3.4 3.4
c1nvua 5 5
c1nvz32 3.12 3.12
cpl2dpnss 1.11 1.11
dpnss_v2 2.3 2.3
dpnss_nv 2.3 2.3
dpt1-2 2.05 2.05
dsp_emtl_24021 3.01 3.01
dsp_gpa 2.01 2.01
dsp_vgu 1.5 1.5
dsp0Z32 1.05 1.05
dsp1nddi2 2.01 2.01
gpa2tns 1.11 1.11
gpa 2.24 2.24
int2_rt2 2.20 2.20
intof 1.25 1.25
intofsync 1.05 1.05
intof2 3.3 3.3
ivrZ24 2 2
lia 4.18 4.18

TC2306 ed.03
lioebbc2 3.05 3.05
lio 3.25 3.25
mic2 2.31 2.31
nddi 2.5 2.5
nddi_in 2.7 2.7
nddi2 2.24 2.24
nprae 2.06 2.06
pcm2_ru 1.6 1.6
pra 2.06 2.06
pra2 2.26 2.26
rma 3.04.04 3.04.04
tonesnv 2.19 2.19
ua 13.9 13.9
uasim 8.14 8.14
Attendants binaries
fbc 2.13 2.13
mapac2 2.01 2.01
Binaries related to 4760i
wbmappli 1200.1708 1200.1708
4760i n.a. n.a.
Note :
You should re-connect to swinst to complete the installation.
6 BEFORE STARTING
6.1 Compatibilities/ Product Limits

To be checked : see Chap. 7 COMPATIBILITIES/ PRODUCT LIMITS
6.2 Hardware : phased-out boards

Check for phase-out boards in the Alcatel-Lucent business portal documents (Eflash Phase out) or in the
Technical Knowledge Center database : https://businessportal2.alcatel-lucent.com/ENT_MLE_032287
(Applications/ Hardware/ Terminals Cross compatibility – document ENT_MLE_032287)
6.3 Conditions for installation in ABC network

Conditions for Installation of RELEASE 12.0 in network is detailed in the last “MLE CrossCompatibility” ref:
ENT_MLE_016252 document available on Business Portal

TC2306 ed.03
6.4 Reminder on applications & functionalities
The table below shows all the applications and functionalities which are no more longer provided by OmniPCX
Enterprise R12.0, whatever hardware used.
Migration batches exist including a specific rate, which have been defined and taken into account
automatically by Actis R19.4
Compulsory
deletion/
Family Type of application Migration to modification Documentation
before migrating
to R12.0
47xx OmniVista 4760i mgr or OmniVista 8770 Yes System Documentation
or WBM (R12.0)
4715, 4730, 4740 or OmniVista 8770 No TC1479
4740 PTP
4730i mgr or OmniVista 8770 Not applicable System Documentation
4755 OmniVista 8770 No TCV010
4000 Directory Server 8770 LDAP Server TCV017
Directory PC Client for 8770 Directory Client TC1479
4755/4000
Voice mail 4630, 4620 or VPS35 4645 or OT MediaCenter
systems 4635 VPCPU, 4635 or
VPCPU-1
ACT migration 4300, 2600, 4600 or Manage the equipment in Yes No

5400 a new crystal ACT or
common hw rack
ACD-V1 ACD-V1 CCD or OTCCSE Yes TC0487 (CCD)

4735 & 4736 CCS
4961 first party TAPI No migration – Not Not applicable No
middleware supported
4973 Telephony Not supported (Replaced Not applicable
Assistant by OmniTouch UC My
Phone)
Others Alcatel Unified OTMC Not applicable
Messaging
Daughter board SPB Moxa box IP/V24 module No System Documentation
Overflow on QoS (VoIP) Not supported No No
CPU2, CPU3, Replaced by No No
CPU5 Step1/Step2/ CPU7-2 – with 512 MB
Step3, CPU6, CPU7s1, memory change
All Appl. Servers except or CS-2 or Appliance
Lenovo M6 & HP Server or vmWare
G8v1/v2 virtualisation (depends on
the Actis configuration)
LIOE & TSC-LIOE INTIP3 Yes No
INT1/INT2 INTOF-2 Yes No

TC2306 ed.03
Compulsory
deletion/
Family Type of application Migration to modification Documentation
before migrating
to R12.0
VoWLAN VoWLAN R1.x VoWLAN R5.x No TC1596
6.5 Applications and functionalities dependent on CPUs and hardware platform

used
Depending on the type of CPU (CPU7, Appliance Server, Call Server in rack, virtualisation) and the hardware
platform used (Crystal, common hardware), some applications or functionalities are not authorized.

TC2306 ed.03
Appliance Server or virtualization
Call Server
CPU7-S2 Common
(CS-2) Crystal hardware
hardware
Voice mail 4645 No Yes Yes No
4615 / VMU-OBCA Yes No No No
4615/VMU-OBCA2 (1) (only 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
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
(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.
Warning REMINDER
DECT2/DECT4 and DECT4 HB boards are phase-out. They are supported by RELEASE 12.0 but can no more
be configured for addition or for new installation.
(3) Manual modifications are required.

(4) No alternative possible.
(5) Boards of IO2/OBCA type do not exist in common hardware. A certain number of applications and
functionalities are therefore no more supported, such as:
 Extension of V24 physical ports via SPB board => use the Moxa box
 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

TC2306 ed.03
 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).
6.6 VoIP network conformity check

The OmniPCX Enterprise R12.0 is a native IP product when using a CPU-CS, CS-2 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 Business Portal for the methodology, recommendations and tools to
secure the VoIP installation. In particular, the VoIP Assessment tool for VoIP Audit and
diagnostic help guide are 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.
6.7 Firmware upgrade

Going from any version up to M1.403.12.G : iptouch sets will upgrade their firmware. Take this time into
account before upgrading. Chapter 5 shows all the components & firmware versions (in bold : new).
6.8 Recommendations about 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.
It is strongly advised to have full network security managed & change regularly the account passwords. Consul
also the security news alerts.
6.9 DECT
Each system equipped with DECT needs a unique PARI configured in the system. To obtain the PARI, refer to
articles in TKC : 000007973, 000011120 on Business Portal.
Information about DECT licenses in case of migration.
If you have an OmniPCX 4400 with DECT, you will find the number of DECT sets in the lock 82 (no lock 175
and no lock 200).

TC2306 ed.03
If you make a migration to OmniPCX Enterprise, you will be able to see locks 82, 175 and 200. During this
migration, if you update the number of DECT sets, only locks 82 and 175 will change, the lock 200 will keep
the value of the number of DECT sets present in OmniPCX Enterprise configuration.
Example:
OmniPCX 4400 with 50 DECT sets:
Lock 82 = 50.
Migration to OmniPCX Enterprise:
Lock 82 = Lock 175 = 50
Lock 200 = 50.
If you change the number of DECT sets from 50 to 60:
=> Lock 82 = Lock 175 = 60
=> Lock 200 = 50.
In that case the maximum declarable of DECT sets is the value of the lock 82 (or 175) but not the
sum of locks 82 and 200 or the sum of locks 175 and 200.
Warning Before upgrade, make sure that the value of the licenses matches the number of DECT users. So, if you
have more DECT users than the value of the license you have to make an add-on with Actis to increase the
license.
7 COMPATIBILITIES/ PRODUCT LIMITS/ FEATURE LIST
7.1 Generalities
New 8770 3.2.07 version is released & is the only compatible version with OXE R12.0 – Check also : 8770
Feature List and Provisioning Level
Other previous versions need to be upgraded. New license update for that release unless it is a migration from
R3.1
Check all compatibilities (applications, hardware etc.) in the following document:

MLE CrossCompatibility ref: ENT_MLE_032287 (download latest edition : https://businessportal2.alcatel-
lucent.com/ENT_MLE_032287)
Limits for features, software, hardware etc. are located at :

Product limits : see OXE (from R9 to R12.0) Global Feature List (Limits are included in tab “provisioning
level”)
Feature list abstract is located at :

ENT_MLE_016151 : xls file (download : https://businessportal2.alcatel-lucent.com/ENT_MLE_016151)
Feature list is located at :

TC2306 ed.03
ENT_MLE_016348 OXE (from R9 to R12.0) Global Feature List : (download : OXE (from R9 to R12.0) Global
Feature List)
Release policy is located at :

Software Release and Hardware Policy for OpenTouch Suite MLE
(download : https://businessportal2.alcatel-lucent.com/opentouch-suite-mid-and-large-enterprises-release-
policy)
All available on the Business Portal : https://businessportal2.alcatel-lucent.com
7.2 Interoperability tests status

Interoperability Tests with Versions used
SIP Audio codes
(MP-114)
Firmware version
6.60A.326.005
Audiocode
OFS
(stand-alone mode on an external server) R 7.6.0.56_suse
8770 8770 R 2.6.07
OTMC R10 10.0.000.020

OTMC 11.0.014.010
Mobility OTC 2.20.05.5
OT - R11.0.014.010
OTCV Soft Phone(Version -
OTMS 2.2.016.003)
OT Version : 11.0.017.006
OTC PC OTC PC Version : 2.2.016.003
7.3 OXE compatibilities in ABC network

The table below shows the compatibility in ABC network : compatibilities were tested with the indicated
versions/patches.

TC2306 ed.03
7.4 OT compatibility
OXE R12.0 is compatible with OT R2.1 MD1, R2.1.1, R2.2 & R2.3
7.5 Common hardware & Crystal hardware mixed

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
In case of Multi-Countries systems, only Common Hardware can be used for secondary countries. Besides, in
such configurations, Call Server and Passive Call Server functions can only be done with Appliance Server or
CS-2 board.
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.
7.6 IP sets compatibility

Refer to “MLE_Cross_compatibility_Nov_2015” document for ip sets compatibility. Inside that document, check
for more details in chapter 9 : “Endpoint compatibility”.
7.7 Subdevices on older sets

This part has been removed from this document. If necessary check precedent document “11.1 release note”.

TC2306 ed.03
7.8 OEM/External equipment compatibility
7.8.1 UPS
In the case of a local 110 Volt power supply, the following MGE (now Eaton) 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.
7.9 SIP sets, Dect sets, other sets … Latest firmware tested.
The set mentioned below do not have their firmware embedded & uploaded by the OXE.
Some of those sets are dual mode (containing the noe mode)
The versions listed below are the latest versions compatible with R12.0
Even lower firmware versions may work but it is recommended to upgrade in case of malfunctioning before
raising a Service Request.
Firmware version Business case Phased out Install/update by …

SIP SETS
8002 / 8012 3.057.0 Business Only 8002 8770
8001 / 8001G 4.1.0.3 Business N 8770
8018 1.05.10 Hotel/ hospital N 8770
8082 1.015.11 Hotel/ hospital N 8770
8088 Conversation 4.008.6.668 N 8770
8088 2.014.2 Hotel/ hospital N 8770
8088 video mode 2.014.1 huddle room N 8770
Vtech S2210 SIP_58.3.80.10 Hotel/ hospital N External Vtech tool
Vtech S2411 SD SIP_58.3.80.10 Hotel/ hospital N External Vtech tool
ATTENDANTS
4059EE 1.7 N Dedicated PC Installer
utility
4059 IP 5.5_0 Windows 8/8.1 N Dedicated PC Installer
(64 bit), utility
Windows 7 (64
bit & 32 bit) and
Windows XP (32

TC2306 ed.03
bit)
NON SIP SETS
8115 / 8125 9.0.12 Conference N Boot on a USB stick on
module the terminal
DECT
Dect 500 v10.88 N FLASHLOADER application
Dect 500 EX v20.05 N FLASHLOADER application
8212 v0007 b0003 N FLASHLOADER application
8232 v48.81 b0008 N FLASHLOADER application
8242 v67.81.b0012 N FLASHLOADER application
8262 v56.80.b0005 N FLASHLOADER application
8262 EX Not released yet N FLASHLOADER application
IPDECT R170 DAP firmware for Dect on IP N
4080 Access Point
: 4910b630.dwl
DAP firmware for
8340 Access Point
: 4920b630.dwl
DAP loader package
: 4992030a.dwl
DAP controller
versions
: 6.21.0299
7.10 Genesys Compact Edition : special case

Premium phones & 8082 are not compatible in R11.2 & above. This is due to a development in R11.2 (new
type of sets). Make sure to upgrade the GCE software to version 4.1.114 & apply the patch from the file
“OXE_L2_for_GCE_4.1.114.zip” (available at the business partner site).
Warning If the patch is not applied the sets will reboot in loop !
8 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.
8.1 New ergonomics and operations

8078S set : touch screen

TC2306 ed.03
8.2 Reminder of changes appeared in Release R12.0
New 4059EE (directory research)
Increase ABCA queue length on 4059 EE
New range of sets (8058S/ 8078S)
Call duration enhancement
Deleting alarms on DECT
Multi-device
New Rainbow application
Security enhancement of A4645
8.3 Reminder of changes appeared in Release R11.2.x

Shortcut to missed calls on DECT
New 4059EE look & feel
Acces to the outgoing calls list via the green touch
Phone user password management
Extended Rapid Call Shift (no more tandem needed, network ABC)

Call log on all IP/TDM & Dect sets
Rapid call shift & NFC feature on Android cell phones
8.5 Reminder of changes appeared in Release R11.0.1

Attendant on 8082 sets (same ergonomics as 4068 sets)
Introduce new dect set 8242 (Note the 8242 MD1 is expected end December 2015)
Introduce new TDM & IP Phones : NOE3G (Premium sets)

 Don't display OXE call log counters when ICS/OT call log is deployed for the IP Touch 8 series EE
 Increase the number of personal directory entries on Dect Hansets
 A4645 security enhancements :
 Access to the voice mail can be blocked after a number of specified failed attempts
 Callback sender via public network
 Notification via public network
 Users connecting from outside the system cannot access their voice mail with the default password
 users connecting from outside the system cannot access the voice mail system
 Desk Sharing Users will be prompted to change their Secret code at first login if they have the Default one
8.7 Reminder of changes appeared in Release 10.1.1

A new ergonomics appears for the IP Touch 8 series EE.

TC2306 ed.03
 Visual SIP Voice Mail Access from IP Touch Mail key
8.8 Reminder of changes appeared in Release 10.1

 Transparent reboot on IP Touch 8 series sets Extended Edition
 Call restriction management for 4068 attendant
 Desk Sharing for IP Touch 8 series sets Extended Edition

A new ergonomics appears for the 4059 application.
 Localization: Japanese on 4059 (Windows 7)
 Localization: Hebrew for 4029/4039 TDM sets from J1.410.38

A new ergonomics appears for some features of 40x8 sets and MIPT.
 Localization: Hebrew (only for 4028/4038/4068 sets).
 Localization: Arabic (only for 4028/4038/4068 sets), from patch I1.605.14.e.
 PERSO page displaying after a time-out.
 MIPT alarm display.
 Translation improvement (Korean language) in IP Touch, from I1.605.24
 Search in internal phone book with several results for internal numbers and abbreviated numbers, from
I1.605.31

 External called number display after call answer (managed by a system boolean).
 Localization: Valenciano language.
 Local time display on sets located in a time zone different of CS as well as in mini-messages, the list of
non-answered calls, Wake-up/Appointment requests.
 It concerns voice messages time/date stamp only for OT8440 (not 4635 and 4645).
8.12 Reminder of changes appeared in Release 8.0 and 8.0.1

 Dial by name with IME (Input Method Editor) on 40x8 and 40x9 sets.
 Localization of softkeys on 40x8 and 40x9 sets.
 Display of Perso page on hang-up on IP Touch sets in Hotel configuration.

 Japanese on IP Touch 40x8 and 40x9 sets.
 Display of the names in UTF-8 format on Alcatel 4059 application.
 Applicative softkey integration on IP Touch 40x8 sets.

TC2306 ed.03
 VoWLAN Release 2.0: New ergonomics of VoWLAN sets using the NOE set protocol.
 Local name UTF-8 (Unicode Transformation Format 8) for users (25 characters).
 Support of traditional Chinese (Hong Kong, Taiwan), Korean, Japanese languages.
 Caller name extracted from personal directory.
 Back to the top of Perso page by default.
8.15 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.
8.16 Reminder of changes appeared with R4.2

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

 Twin set (Tandem)
 Management of "Partial Busy of the set".
 Enhancement of supervision function.

 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.
 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.
9 PREPARATION/ OPERATIONS
The purpose of this paragraph is to mention everything that the technician needs to prepare before starting
the change of version.
9.1 Checking compatibility

Before starting, it is essential to review all the applications, hardware and functionalities which should evolve.

TC2306 ed.03
See Chap. 7
9.2 Call Server compatibilities
Warning FOLLOW CAREFULY THE RULES OF THIS SUB-CHAPTER
Only the following CPUs are compatible :

- CPU7s2 with a change of memory bank to 512Mb. To obtain this memory bank :
 Automatically added during a R12.0 upgrade by Actis
 Can be ordered separately in Actis
- CS-2
- Appliance server Lenovo M5
- New Appliance server Lenovo M6
- Appliance server HP DL xxx G8v1 with a bios update : xxxxx see chapter relating the upgrade
- Appliance server HP DL xxx G8v2
- New Appliance server HP DL20 G9
- VM with following characteristics :
- Memory size from 1Gb
- OS : other Linux or CentOS
- Hard drive size : 40Gb minimum
- Network card :
- E1000
- VMNETX3 IF CentOS is selected
-
!! The cpus not mentioned above ARE NOT compatible and most of them will not be able to be installed
For installing a CPU7s2 the bios must be at a minimum version. Follow the chapter 19.2.2
Thus the menu “boot Alizee” is no more available to load this cpu => use the “A4400” boot method.
Coming from any version up to M1.401.x (included) the disk must be refomated meaning that remote
download feature cannot be used to go to M1.
From M1.403.x to any other M1 remote download is operational.
A system running in L2 for instance can remote load & install a cpu already installed in M1.403.x & vice versa.
9.3 Voice guides

Ensure that you have the voice guides required in RELEASE 12.0 (no change since previous release)
9.3.1 System voice guides

The version of system voice guides compatible with the OmniPCX Enterprise R12.0 is v5.3 CD-ROM reference:
3BA 57423 AAAG (same since R11.0)

TC2306 ed.03
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 Business Portal section Customer Support > Technical Support > Software
Download > OmniPCX Enterprise > All releases.
9.3.2 Alcatel 4645 voice guides

The version of the Alcatel 4645 voice guides is v1.7. CD-ROM reference: 3BA 27588 AAAE.
The following files are provided on the CD-ROM:

 Voice guide transfer tool.
 Voice guides in 40 languages in law A.
 Voice guides in 20 languages in law .
 Voice guide documentation.
They can be downloaded from the Business Portal section Customer Support > Technical Support > Software
Download > OmniPCX Enterprise > 4645.
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

TC2306 ed.03
Country Code Law A Law µ
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
9.4 ACTIS, eLP & software locks

Release 12.0 needs a change in software locks : R12.0 is defined by locks 87 (value 25) & 165 (value 45)
The Actis version for this OmniPCX Enterprise is 22.0, eBuy/eLP/eCOM : R23.3 & the catalog is referenced OXE
E28-Ed37.
To prepare any system to the Cloud connection a new CC-suite id is inserted by eLP or Actis. This data stands
before the CPUids in the swk file constitution.
CAUTION
An add-on via Actis is only possible if the current Actis offer includes the .swk file (generated by eLP then
imported into Actis).
When you make a configuration request four or five OPS files will be generated:
 <offer_id>.zip
 <offer_id>.swk (this file results from the eLP)
 <offer_id>.hw
 hardware.mao
 <offer_id>.sw8770 (if 8770 is present)
In the case of the migration of an OmniPCX 4400, the lock files of the site (photoconfig) should be put in
Actis. Actis will then allow you migrating these locks (in "Migration to OXE" Offer) by proposing migration
packages for the functionalities and hardware that are not supported by R12.0

TC2306 ed.03
9.5 Before saving the database
The following operation may be necessary coming from an old release :
In the current version, carry out the following commands.
9.5.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.
Carry out the back-up in swinst and transfer it to disk or PC.
CAUTION
 Do not choose the save option "Save for rebuilt" (index files will not be saved).
 Do not use a database saved in "Automatic save" (same reason).
9.5.2 Tickets
REMARKS: On the saving of charging tickets.
Sites going from A9.5xx to R12.0 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 R12.0 which already have compressed files should save them as they will be
compatible.
9.5.3 From crystal to common hardware

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 R12.0 with change of
CPU 4400 by CS or 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 is retained.
9.6 4645
Issue is detected in case of backing up/restoring big files bigger than 2Gb (crqms00177881) : the file does not
have the right size (issue related in both os & client tool).
the size of /tmpd (usr4) increased to 25 GB. This change will reflect only for HD size >=80 GB. For other disk
sizes there is no change.
Refer to chap. 19.2.3 for more details on 4645.

TC2306 ed.03
9.7 Special cases : migrating old versions
- There is no automatic translation from releases below 1.5.3 to release 12.0 For all these versions, it is
essential to go via an intermediate translation in a release compatible with translation to R12.0 (from
R1.5.3 to R5.1.2).
- There is no automatic translation from the Custom Release 3.0C (C1.580.1) to RELEASE 12.0 It is
essential to carry out an intermediate translation with Custom Release 3.2-C2 (C1.762.18 minimum).
- 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 release lower than 3.0 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".
- 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.
- The translation of the tunnel creates static LCNs. For a network where all nodes are in R7.1, the static
LCNs must be deleted.
- It is essential to save the site OPS files (photoconfig). They will be required to be able to carry out
a migration to R12.0
- If the lanpbx.cfg file was used in Release 3.2, it is essential to save it before passing to RELEASE 12.0
(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).
9.8 Getting the software

Make sure to have all he DVDs to load the OXE software.
Virtualisation requires extra DVDs or tools like Operating Systems, firmwares …

Virtualized OXE :
- ESXi boot DVD or RH enterprise boot DVD (for the KVM solution)
Flex server :
- OVF file (image of CentOS OpSyst + Flex server binary : vmware solution) or separate CentOS ISO
image + flex server binary (for the KVM solution)
OMS :
- OXE MS APPLICATION DVD-R
ALEDS tool
- Last ALEDS tool in Gen. Availab. plus vmware player (free download & use) or workstation on a PC :
download ALEDS on the BPWS
10 OPERATING MODE
Coming from ANY version <12.0 the cpu MUST be reformatted : no possible use
of unactive partition (partitions are resized + multipartition process NOK)

TC2306 ed.03
10.1 New installation
New installations 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 given to the case of networking.
See MLE CrossCompatibility ref: ENT_MLE_016252
and Product limits Ref: 8AL020033238TCASA available on Business Portal.
10.2 Updating from R5.1.x, R6.x, R7.x, R8. x, R9.x, R10.x,

R11.0/11.0.1/R11.1/R11.2 up to R12.0
After updating to R12.0, you will find the same level of functionalities as initial release.
However, certain applications require a minimum version, see MLE CrossCompatibility ref:
ENT_MLE_016252 available on Business Portal.
CCS must be upgraded to version 10.2.92.0
Note All OMS in Red Hat should migrate to Suse.

There is no specific procedure for doing that : configuration done by “mgconfig” must be managed again at
the identical.
All the elements required for passage to R12.0 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.
10.3 OmniPCX 4400 migration to R12.0

Two possibilities are provided for migration to R12.0 :
 Migration to R12.0, keeping the 4400 type CPU. Change to CPU7s2 with new memory bank
 Migration to R12.0, changing the 4400 type CPU for Appliance Servers (called Migration with Appliance
Server).
????
The migration to R12.0 offers the same level of functionalities as the R5.0 Ux, except for three restrictions:
 As of Release 5.1, certain applications, hardware or functionalities are no more supported; see paragraph
6.1.
 The replacing of 4400 CPUs with Appliance Servers leads to restrictions on the use of certain
functionalities; see paragraph 6.5 .
 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
R11.0 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 is retained.

TC2306 ed.03
Actis is used to migrate locks (resulting from site by photoconfig) of an OmniPCX 4400, proposing migration
packages for functionalities and hardware not supported by R12.0
10.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).
10.3.2 Crystal hardware compatibility with an Appliance Server

See the table in paragraph 6.5 .
Technical communication TC0778 Migration OmniPCX 4400 to OmniPCX Enterprise describes the steps
necessary for transition to Release 9.1
11 LOADING THE SOFTWARE
11.1 Installation
Loading is carried out using the PC Installer tool common to all compatible CPUs (CS-2, AS, CPU7s2 &
virtualized CPU). Refer to the technical communication TC1708 Installing and using the OmniPCX Enterprise PC
Installer v3 and v4 software .
To load the software use the new PC Installer 4.1 delivered in that release and available on Business Portal.
11.2 Use of ALEDS

ALEDS is requested to install OMS & OST64 with Suse operating system. Latest version put in GA is 3.x.x.x
Reminder :
In pure OXE configuration “pc installer” is still used to install OXE (vmware or kvm solution)
Flex server installation does not need any 3rd party tool (vmware or kvm solution)
Use of ALEDS for OXE installation (out of OT context) is not validated yet. Some features will not work.
11.3 Secured systems

11.3.1 Security activated by default during an installation
As of Release 6.2, 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.

TC2306 ed.03
The absence of security on the system, which remains always possible, will be under the whole responsibility
of the customer.
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.x.
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 and in R7.0 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. It is higly recommended to use this level.
11.3.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 M1.403.12.G must be carried in two steps:
1. Installation of system with generic version i.e.:
Installation generic version M1.403, installation of static patch M1.403.12 and then installation of dynamic
patch M1.403.12.G 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.:

TC2306 ed.03
Installation of the security patch M1.403.12.G containing the latest secured binaries with usual tools
(Deliveries installation or Remote Download).
General In general : if installing a generic complete version and patches, for instance M1.403 + M1.403.12 +
M1.403.12.G, the installation of the security patch of the complete version M1.403 and static patch
M1.403.12 are not needed since the security patch SM1.403.12.G has the same binaries but the latest one.
11.4 Using the Remote Download

??? Refer to the technical communication TC0669 Compatibility of versions for remote download feature.
Remote download is NOT operational when coming from ANY version to M1.403.x
But it is operational FROM M1.403.x to M1.403.x & above
Tip ! Remote download allows to perform programmed & scheduled operations (load, installation).
Switch back in older release is always possible through a specific question & guaranties a more secured
upgrade.
Remote download operations can be programmed, sequenced & executed at a specific time.
Switch to the new version (from active to unactive partition) can be programmed at a specific time : in that
case the copies of database & linux data will be performed automatically from Active to unactive partition
11.4.1 Reading the hardware key, CPU-id, CCS-ID

On a label on the CPU :
For all types of CPU (CS-2, AS, CPU7s2), a label is visible indicating the CPU-Id number.
For virtualized systems, the equivalent of the cpuid is the dongle (reference written on it).
Through a command to read the CPU-Id or CCS-id

For all types of CPU (including virtualized but not valid : no cpu-id in that env.), telephone started or not,
execute the command “spadmin”, option 5 : “Read the system CPUID”
CCS-id used in Cloud Connect belongs to the swk file :

“spadmin” choice “Display active file”. CCS-id is displayed as CPU0
Ex: “Cpu Id 0 = CCSID:3834-5945-xxxx-xxxx-xxxx”
11.4.2 Creating a blank database
Warning A blank database should only be created for CPU installation on a new site

TC2306 ed.03
Login swinst
Password xxxx
option 7 Database tools
option 2 Create an empty database
Enter country name example "is" for “Iceland”
11.4.3 Restoring the database and site tickets
Login swinst
Password xxxx
option 4 Backup & restore operations
option 3 Restore operations menus
option 1 Restore from cpu disk
11.4.4 Restoring Chorus/Linux data

CAUTION
It is possible that the Chorus data of certain Releases cannot be reused automatically : manage “netadmin” by
hand in that case.
12 TRANSLATIONS
DO NOT USE THE “mao for rebuild” type of database backup to translate to a release <R12 to R12.0 : the
rebuild tool always included in that backup is NOT compatible with the new Linux OS.
Things to know …
 As of Release 5.1, the translation is automatically run after loading the OPS files.
 Sites in A9.532 should first pass to A9.537 (latest patch)
 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 12.0. It is
essential to carry out an intermediate translation with Custom Release 3.2-C2 (C1.762.18 minimum).
 As of Release 8.0.1, to take into account the provisioning limit evolutions, the translation creates
automatically a fictive shelf in which the virtual UA boards of ACT 19 (intended for the assignment of IP
sets) will be migrated.
This fictive shelf is created automatically with the first free shelf number in the translated database.
In XL configuration, the number of fictive shelves dedicated to IP sets allocation can go up to 3.
 When migrating (use of photoconfig), Actis takes into account the creation of fictive shelves dedicated to
IP sets allocation.
 As of Release 9.0, all standard SIP sets must be declared with the SIP Extension type. Standard SIP sets
are no longer supported with the former "SIP Device" mode (formerly called "External set"). Only items
other than standard sets (Nokia sets in Dual mode, 4135 IP Conference Phones, fax, video, etc.) should
remain with the former "SIP Device" mode.

TC2306 ed.03
When migrating a system with "SIP Device" / "External set" to R9.0, the system moves these sets into the
new mode (SIP extension) automatically.
Warning It is mandatory to declare Nokia sets, used in Dual mode with OXE, and OT4135 IP Conference Phones with
type "SIP device".
Procedure to follow:
 Export the SIP entities which are not standard SIP sets (Nokia sets in Dual mode, OT4135 IP
Conference Phones, fax, video, etc.) by OmniVista 4760(i) by using .prg as export format.
 Remove these entities then migrate to R9.0.
 Import again the items which have been previously exported: standard SIP sets are in "SIP Extension"
and the other SIP entities in "SIP Device".
Note Fictive shelves dedicated to IP sets allocation created automatically by the system must in no way be
changed by the management.
 As of RELEASE 11.0, the Direct RTP mode (in network) is automatically enabled and the relative
parameter removed. The same is done for H323 Internode Protocol system parameter.
 When creating a new Media Gateway or an A4645 voicemail after the upgrade to RELEASE 12.0, a GD3
board will be automatically created and no more a GD one. The already created Media Gateways and
A4645 are of course not modified and will remain with a GD board. For the A4645 voicemail, absolutely no
functional difference exists depending a fictive GD or GD3 is used.
Check if translation performed correctly : operation & error messages are located in a file that can be
displayed by swinst :
7 Database tools
then
5 About last database operation
Translation log file is located under “/usr3/mao/TRANSLATE.dat” and is also included in the infocollect result
file.
13 Installing/checking OPS/Actis files

The procedure for installing OPS files puts together the following steps: RUNMAO, translation of the
database and installation of the OPS files.
13.1 Procedure :
Copy the OPS files using "ftp" in the directory /usr4/BACKUP/OPS.
Use the menu swinst/OPS configuration.

TC2306 ed.03
The progress of the different 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.
13.2 Checks on physical CPUs

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.
13.3 Checks on virtualization

In case the cpu is installed in an esx or KVM environement the check of the cpu-id gives back “Your System
CPU-Id: -no-hard-key-“
The “swk” file contains a “K….” value instead that is the name of the file installed on the flex server. That file
on the flex server will contain the identification of the dongle. So it is not possible to do this kind of check.
In spadmin, menu “Display current counters” verify that the first info are :
(SP) Software Protection counters :
PANIC Flag :0
-------------------------------------
Panic Flex :0
Panic SWK Check :0
Panic RTR Check :0
-------------------------------------
Meaning that everything is ok :

Flex server is reached & dongle is controlled
“Panic RTR Check” relates to the Cloud Connect feature appeared in R12.0)
Checks when a remote dongle is configured :

It is not possible to see if the system is equipped with a remote dongle. Checks must be done on the flex
server itself. Flex has a very specific way of handling dongle deconections & extractions : look at the pre-sales
documentation for more details.
13.4 Checks on Cloud Connected system

See above in “spadmin” tool : Panic RTR Check should be 0 as well as “PANIC Flag”

TC2306 ed.03
14 SYSTEM MANAGEMENT
14.1 General :
Declare the automatic start-up of the telephone in swinst
Manage date/time in swinst (use “ntp” feature if possible)
In case of virtualization manage the ESX in order to be sure that all VM will restart automatically if the server
reboots (vSphere client management)
Make sure that a periodic backup of the database is programmed (“swinst”)
X25 networks :
IP routing is handled by the "gated" or “routed” processes and can only operate if the same 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
14.2 Special case of IO2N boards (CPU7s2)

CAUTION
 IO2 boards are phase-out
 CPU6 & CPU7s1 are not supported
 On a duplicated installation, if an 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 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 IO2N using the command “RUNTEL -DNOIO2” as mtcl user. This
should only be a temporary mode.
 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 IO2N to be checked.
15 COMPULSORY MINIMUM ADDITIONAL DATABASE MANAGEMENT
15.1 Reminders
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 routing in network

TC2306 ed.03
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.2 Reminder for ABC networked sites migrating from Release < 7.x
As of Release 7.0, a new feature is used to display the names with UTF-8 format (long names and for non
Latin languages: Chinese, Korean, Japanese).
In ABC-F2 network functioning, from RELEASE 11.0 the name in UTF-8 format is used in the network
according to the setting of the Enable UTF8 in ABCF network system parameter (default value True).
This information is accepted only from the following versions:

 R6.2 : F3.301.16.e (patch for compatibility UTF-8)
 R6.1.1 : F2.502.12.d (patch for compatibility UTF-8)
 R6.0.1 : F1.603.1.aa (patch for compatibility UTF-8)
If RELEASE 12.0 is functioning in ABC-F2 network with nodes the versions of which are lower than those
mentioned previously (case of temporary phase of migration with R5.0 Ux, R5.x, R6.x), you must set the
Enable UTF8 in ABCF network system parameter to False on nodes where RELEASE is => 11.0
otherwise the calls through the network don't work.
Warning In a network, if a node is declared XL ("Large Capacity"), each node of the network must be in Release 8.x.
minimum
The system parameter Direct RTP must be enabled in all nodes of the sub-network as soon as one node is
migrated in RELEASE 11.0
15.3 Important management if IO2N is present

To solve traffic issues on CPU7s2 (issues related to CPUs crash or peripherial racks rebooting) the signaling to
IO2 must be changed. Notice that this management can be done for any configuration even with very low
traffic with no impact on the system.
On ACT0 :
2 ways of changing the signaling :
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

TC2306 ed.03
Shelf 0/Signaling mode: IO2
Shelf 0/Signaling Channel N64 Size: 8
Or
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.
For the remote shelves :

apply the same management : Signaling mode = IO2 with only 4 channels. Don’t exceed the 60 channels of
the board. Include the 8 channels used for duplication in crystal 0.
Note The IO2N board must be at the minimal edition 07. Refer to the technical communication TC0567 Reboot of
the CPU board after an inopportune shutdown of IO2N board.
15.4 Synchronization
Warning 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.
Warning For migration of a Crystal CPU to an Appliance Server, it is compulsory to change synchronization
management to IP domain type. The synchro priority value must be between 200 and 254; see technical
communication TC0779 Synchronization of the system after migration to OmniPCX Enterprise with
Appliance Server.
15.5 Some system parameters to check

Use the command compvisu to display the parameters.
15.5.1 Direct RTP
Note In this document, "Direct RTP" corresponds to "Direct RTP in network".

In all nodes of the sub-network the Direct RTP parameter must be set to Yes.
From OmniPCX Enterprise R11.0, this parameter is removed (validated by default).
15.5.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.

TC2306 ed.03
It is better to use the Framing 20 ms for G711 or G729.
G723 can only do 30 ms.
15.5.3 Direct RTP for H323 terminals

This parameter must be set to No if a only one H323 terminal of the installation does not support the direct
RTP
15.5.4 Inter-node protocol H323

The “H323 Inter-node protocol” parameter must be set to Yes in all nodes of the sub-network. In an OmniPCX
Enterprise R11.0 system, this parameter is removed (validated by default).
15.5.5 Pre-login (V120 on IO2n boards)

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

CAUTION IN DUPLICATION STATE:
Do not proceed by switchover for 2 different releases : a complete stop of the telephony is required . It is not
recommended also to proceed by “bascul” when installing a static patch though there is no clear rule
established. During that time (patch n & patch n+1 on main & stand-by), the command “twin” may return the
status “KO” for the “memloader” check.
Complete system start-up : this will allow to download automatically the new firmware of the couplers and to
avoid having memory issues (as mentioned above).
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.
Use the “downstat d” command to obtain boards that have to be downloaded
Use the “downstat v cr cpl” command to display 'binaries' version for a coupler
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 controlled by an Appliance Server).
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.

TC2306 ed.03
8082 sets in NOE mode & also new noe3G sets can do upgrades in background mode : once the download
is finished the set will reboot. If a communication is already established, the process will wait for the
communication to end.
Note communication to be over to perform the reboot.
Note IPV6 feature : sets in pure ipv6 network will get their binaries from the OST64 virtual machine : the OST64
must be rebooted in order to perform the correct download mechanism.
16.2 Sites with the "IP Touch Security" feature: Migration from R6.2 or R7.x to
R12.0 with SSM & MSM boxes in version 3.5.01.a
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 R12.0
After upgrading in SL2.300.20.e and with the RUNTEL done, you must update the IP Touch Security boxes
(MSM, SSM) as follows:
1. Check that the versions 3.3.05 for bin_SM or 3.5.01 for bin_SM2 is managed in mgr.
2. Reboot (with Off/On button) each SSM, MSM box, SSM-RM or MSM-RM to allow the downloading of
the new binary 3.3.05 or 3.5.01 (the config_BT.cfg file has been modified; this enhancement is
available only from the version 1.6.02).
3. Check with info -v command that each SSM, MSM box, SSM-RM or MSM-RM has been downloaded with
the version 3.3.05 or 3.5.01 then re-generate the Config_BT.cfg file.
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 & VPN : use “lookars” & “lookvpn” embedded OXE tools.
 Check that all sets & couplers are correctly in service & downloaded & sets are in service : use the
different commands “downstat”, “config”, “listerm” with the correct args (help available)
 Check the coherence of the files (Suspicion of errors during file transfert : ftp must be set to “binary”
mode).
login Swinst

TC2306 ed.03
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 duplication status : use command “twin” : each line should be in “OK” state
 Check of version : use “siteid” to know which version/patch is loaded & also to check if it is an encrypted
patch
 Check start-up of the IBSs behind INTOF.
 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. 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
18 CHECKS IN A VIRTUALIZED VMWARE INFRASTRUCTURE

 Consult document “OpenTouch Suite for Medium and Large Enterprises - Virtualized offers” for more about
vm rules configurations in esxi vmware environment (odc available in the Business Portal).
 Make sure the correct management is done in order to autostart all the vm after a server reboot or power
fail
 Flexserver : be sure that connection is ok between OXE & that server(s). Log files in the flex server (
check in /opt/Alcatel-Lucent/logs/flexlm/ files : system documentation “Call Server in Virtual
Machine” section). Look also for OXE incidents from 640 to 644 (FLEX issues).
 Remote dongle : check the connection to the Raspberry (make a ping from the Flex to the R PI2)
19 NEW HARDWARE AND FEATURES IN RELEASE 12.0

You can also refer to the System documentation.

TC2306 ed.03
19.1 New hardware
19.1.1.1 New noe3G sets :
The 8078s (picture : top right) is a new phone with touch panel
Retro-compatibility mode :
8028s : Yes download only (no update on tools on management)
8058s : No
8068s : Yes download only (no update on tools on management)
8078s : No
Hardware :
*New* phones: 8028s, 8058s, 8068s, 8078s
*New* magnetic wired mini keyboard
Existing wired comfort handset
Existing common Bluetooth handset (C-BTHS) *Update planned with new RTX BT HS*
Existing Add-on module range: AOM10, AOM40, AOMEL
Existing Premium Add-on clip
Existing Power Supply for AC / Existing Power Supply for PoE
Existing Wall Mounting Kit
Software features :
Same feature level as Noe-3G R2xx

TC2306 ed.03
Dynamical changeable skins (4 skins in R100, Rainbow is default skin)
Customization (Startup screens, Skins)
Auto-brightness (via ambient light sensor) on 8058s/8068s/8078s
Busy light logo on 8058s/8068s/8078s
New Noto font
Improved power consumption: 8028s is Class 1 (w/o AOM), others are Class 2
Bluetooth Smart Ready (BT v4.1)
Multiple accessories (headset, handsfree, speaker) via Jack 3.5 mm 4 pole / USB / BT
Super Wideband Ready
Remote Worker (VPN Ipsec)
Improved ringing melodies (16 KHz audio quality)
High / Low brightness level settings
CCD agent Mode:

8058s : N
8078s : Y
8068s : Y
Attendant :
8058s : N
8078s : Y
8068s : Y
Retrocompatibility :
8058s, 8078s : R12.0 & above
8028s, 8068s : R11.0 & above (exact patch to be given later). Warning : before R12.0 ONLY download is
available nor management nor tools that could identify the set type.
Data sheet is available at : http://enterprise.alcatel-lucent.com/assets/documents/8078s-8068s-8058s-8028s-

premium-deskphone-s-series-datasheet-en.pdf
19.1.1.2 New Appliance Servers

2 new appliance servers are introduced in R12.0 :
- Lenovo X3250 M6 readiness (server not available yet)
- HP DL20 G9
They are NOT retrocompatible

HP DL20 G9 is compatible in duplication with the previous servers G8/G8v2
Find the related BoM in chapter 22.2.5.4 (G9)
The G9 is only sold in the ALE catalog in a single Power Supply version. To get the dual power version order
directly to HP.

TC2306 ed.03
19.2 New features : description/explanation & management
19.2.1 New OXE incidents (sipmotor/ Cloud Connect)
new incidents were created in that release. They are related to :
- sipmotor process activity.
See chapter 19.2.12.1 New Sipmotor incidents for more explanations
- Cloud Connect
647 : CCI_FAILURE
648 : RTR_PANIC_SET
649 : RTR_PANIC_CLEAR
650 : MAO_RTR_PANIC_SET
651 : MAO_RTR_PANIC_CLEAR
19.2.2 CPU7(S2) installation procedure modification (bios update)
Important A change in installation
Technical constraints had changed the way CPU7s2 can be installed (at bios level).
The Alize installation method is not supported anymore for a4400 type CPU7, so the support is disabled in
BIOS : if we select the “Alize method” through BIOS monitor a “not supported” message is shown and the
menu is presented again.
Bios versions greater than or equal to “3BA24115AAFC (bscpu7300/004.003)” are concerned
Latest patches in J2, K1.5 & L1 will also inherit that bios
Version check:
With tool “uhwconf”

TC2306 ed.03
At boot time :
Below the display of the menu including the modification :
YOU CAN strike Ctrl B to enter in BIOS monitor during several seconds from NOW !
hit [Ctrl I] for BIOS monitor!

TC2306 ed.03
CPU7 Password or CR ?:
BIOS Loader Menu
1 - Load From Hdisk #0

2 - * Disabled menu entry *
3 - Load From Ethernet (4400 method)
4 - Load From Hdisk #0 and Bootp
5 - MAC Address
6 - PCMS id
7 - System informations
8 - Set interface KENDIN to default(auto-nego)
9 - Interface KENDIN state
10 - Set Interface KENDIN
11 - Ethernet embedded interface state
12 - Full Option Menu
13 - Reset System
CPU7 >
Below is an example as reminder of how to perform the CPU7s2 boot & installation :

TC2306 ed.03
New loaded file correspond to the dir found in :
“\dhs3mgr\<version>\pcmao\boot_res\bootp\linux”
For M1.403 the linux version is “109.000” (“\dhs3mgr\M1403\pcmao\boot_res\bootp\linux\109.000”)
19.2.3 4645 (users, messages duration …)

Number of users is now increased to 7000 for business & hotel/hospitality.
The number of ports is manageable by “mgr” (already in L1.301.25) : a copy (rcp) of a configuration file is
made (oxe to 4645). Make sure the hosts names & addresses are correctly configured on both cpus in case of
dedicated vm.
Max number of ports according to the OXE release (extract from prod limits document) :

TC2306 ed.03
R8.0 R9.0 R9.1 R10 R10.1 R11.x R11.2.x R12.0
Dedicated 8 8 8 8 8 8 8 Not
CS-1 supported
Dedicated 16 16 16 16 16 30 30 30 30 from OXE R11.0.1
or non
dedicated
AS
Dedicated NA NA 16 16 16 30 30 30 30 from OXE R11.0.1
or non
dedicated
CS-2
Total size remains 600 hours

Potential issue with backup using tmpd :
the size of /tmpd (usr4) increased to 25 GB. This change will reflect only for HD size >=80 GB. For other disk
sizes there is no change.
Below is an indication about the size of the partition supporting the messages.
There is no possibility to resize partitions so the only way is to re-install the cpu (reformat) to get the correct
dimensionning.

TC2306 ed.03
19.2.4 New noe sets
New identification in management :
IPTouch 8028s
IPTouch 8058s
IPTouch 8068s
IPTouch 8078s
Notice that the jack is using 4 points now.
NOTE :
8088 set in Noe mode is not released at this current OXE offer. It will be delivered during a patch. Technical
release note “TC2308” will be given then.
19.2.5 Virtualization
19.2.5.1 Virtualization systems

- Flex server vm :
2 lines ore now available :

TC2306 ed.03
 The first one is kept for esx env. In 5.0 & does not support the new remote dongle feature. It is
kept just for compatibility & to provide fixes like security issues … This line will not be maintained
for a long time.
 The other one was made to support local dongle & remote dongle & is intended to work on esx
5.5
- Hyper-V is not available for that release.

- ESXi 6.5 is compatible.
- Not compatible with Amazon Cloud (Xen)
19.2.5.2 Virtualization : configuration

This is a reminder of main configuration
- Memory :
1 Gb recommended. 4 Gb maximum.
- Disk :
Minimum of 40Gb disk with small voice mail storage capacity. Minimum of 100Gb disk in case of more
than 600h voice mail storage.
IDE (0:0) – SCSI not validated
- OS:
Linux / Other linux 32 bits or Centos 4/5/6 32 bits (new in R12.0).
- Network card :
E1000 or VMXnet3
If CentOS 4/5/6 was used, then VMXnet3 becomes visible and a possible choice for Ethernet driver (new
in R12.0).
Consult document “https://businessportal2.alcatel-lucent.com/node/430986” for more about vm rules

configurations in ESXi vmware environment (doc available in the Business Portal).
19.2.5.3 Virtualisation. Change in remote dongle use : go to a Cloud solution

For the systems that do not have or accept a local USB port it is possible now to use the new feature “Cloud
Connect”.
The system key will be hosted in the ALE Cloud thus providing in the future further services.
See the chapter 19.2.13 for further details. Cloud Connect solution can be used on any system virtualized or
not.

TC2306 ed.03
19.2.5.4 SUMMARY ON VIRTUALISATION : COMPONENTS NEEDED FOR INSTALLATION
tool to install on tool to install on
VMWARE KVM How to install misc
OXE PC Installer v4.1 PC Installer v4.1
*OS is now on Suse 12
*bootdvd.12.0.000.01
3.x86_64.iso or upper
64bit image
on vmware : web client *OXE-MS core image
needs to have a vCenter file : oms-
for Suse 12 selection 4.00-IP0001.iso or
OMS ALEDS 3.4.0.2 mini ALEDS 3.4.0.2 mini vmware 6.0 won't need that upper
on vmware <5.5 : web
client needs to have a
vCenter for Suse 12
selection
vmware 6.0 does not need
OST64 ALEDS 3.4.0.2 mini ALEDS 3.4.0.2 mini that OS is now on Suse 12
*file "vmFlex-
2.1.000.093" for
CentOS 7 if ESXi 5.5
or more - same
version number for
kvm
"vmFlex-Centos5-
2.1.000.093" if ESXi
vmware installation kvm installation <5.5
FLEX Server method method ovf deployement
*tool not present in
ALE Portal.
Win32 Disk Imager *OS "ipdongle-firm-
(on "Sourceforge") to write 1.0.000.000.img" is
Raspberry NA NA on SD card present on the Portal

TC2306 ed.03
19.2.6 Terminals
19.2.6.1 8018 Deskphone support in Business mode (3 enhancements)

New features are : SIP Survivability, Encryption and SSH Password management from CS.
SSH Password management is delivered only in OXE M1 and Terminal Version R200 4.80.84
USB Boost Charging is supported from OXE M1 (R12.0) and Terminal Version R100 4.81.00
8018 does not support IPv6 in that release
SSHv2 Password Management for 8018

8018 does not support telnet instead it supports SSH. The SSH password for 8018 sets
(Alcatel 8&9 series) is the existing password for MMI. In order to reset the default SSH
password, the terminal needs a specific hash of the password which is different than the one
used for MMI. The hash for SSH is computed using dhs3password and saved in database
while managing the NOE password.
During the set initialization, OXE sends SET_PARAM_REQ message with two hashes (and
associated signature respectively), one for MMI (existing one) and one for SSH (new one).
For setting SSH password, a new parameter is defined.
Hash encrypted SSH password concatenated with a signature allows the terminal to validate
the received hashed value, for SSH server protection.
8018 USB boost charging mode management

The purpose of this feature is to provide quick/boost charging to the smartphones or tablets
connected to the 8018 terminal.
But boost charging requires more power consumption than the normal USB charging in case of PoE.
In order to control this PoE there is a need for centralized management of USB boost charging.
Parameter “USB Boost Charging” managed in MAO: mgr->Alcatel-Lucent 8&9 Series->8&9 series COS-
> Phone COS-> Review/Modify.
If the parameter value is :
Disable => normal USB charging (default value)
Enable => boosted USB charging (may need a dedicated external power on the set)
Auto => reserved for future use (= disable if set)
As reminder the 8018 supports TLS 1.0/TLS 1.2 in 802.1x EAP-TLS for port authentication of LAN
access based on the settings done at initialization. TLS will be used for SIP signaling, HTTPS and it
has no impact on encryption.
8018 supports SHA-224, SHA-256, SHA-384 and SHA-512 algorithms in SHA-2 family for the
authentication for the signature of customer certificate.
19.2.6.2 8018 in hospitality environement

To be released later. Documentation to follow.

TC2306 ed.03
19.2.7 Increasing provisioning level
19.2.7.1 Extend the capacity of casual conference (see chapter. 19.2.11.4 for further
details)
19.2.7.2 Increase max number of simultaneous CSTA monitoring from 20000 to 32000
19.2.7.3 Increase the size of the external telephony application table

Goal is to be able to handle 254 network voice mails in the networks. Instead of being limited to 127 voice
mails in a network, we can reach 254 voice mails.
19.2.7.4 Increase ABCA call queue length for 4059EE

Business case related to hospitals …
The attendant can hold lot of calls, but displays only 3 in the Parked Calls list. The problem is that when the
doctor calls back, the attendant is not able to retrieve the concerned call to the requester because this call is
currently on hold queue but it is not displayed in the Parked calls list. This makes sometimes it is impossible to
transfer. After the development of this feature, the number of held calls displayed on the Parked calls list is
increased to 8.
In this new feature, the number of held calls that are to be displayed on the Parked calls list is updated to 8
and it is applicable for all types of attendant (4059EE, 4059IP, 4059 MAC, 4068, 8068, and 8082). Therefore,
the below example shows that on receiving 8 calls (can be internal or external call) are put on hold, they are
displayed in the Parked calls list which answers customer’s use case.
If the 9th call is received on the attendant, then it can be put on hold but it is not displayed in the Parked calls
list.
19.2.8 Security
19.2.8.1 Security enhancement of A4645

The objective of this feature is to enhance the existing system behavior on certain scenarios :
 Default value of Password validity period
 User interface on expired password
 User interface on locked account
Incident thrown on locked account due to incorrect password attempts.
A new option in “Eva_tool” to view mailboxes based on password expiration date
Default value of Password validity period :

“Password validity (days)” parameter is used to set the number of days for password expiration. The
mailbox password expires based on when the password is last modified and the “Password validity
(days)” value in 4645 VM ClassofServices.
mgr ->Applications ->Voice Mail ->Descend Hierarchy ->4645 VM ClassofServices ->Review/Modify
->Password validity (days)
Enhancement :

TC2306 ed.03
The “Password validity (days)” parameter’s default value has to be modified to 180 days for empty
database. So the user does not need to change the password frequently.
User interface on expired password :

The mailbox password expires based on when mail box password is last modified and the “Password
validity (days)” value in 4645 VM ClassofServices. If the password is expired, a voice guide plays as
“The password has expired”, the set displays the same string “Password” to enter new password and
to confirm the new password. Only after changing the password, user can access the mailbox.
Enhancement :
The current display for expired password is not user friendly. New strings “Password expired, Enter
new password” and “Enter new password” are created to indicate that the password is expired and it
is prompting for the new password to be entered. New strings “Listen pwd, confirm” and “Listen
password and confirm” are created to get the user confirmation for new password. The string “Enter
new password” and “Listen pwd, confirm” are used for sets having 20 characters display like 4008,
4018, 4019 sets.
The existing voice guide is appropriate, so no change for it.
The string “Enter new password” is created for both 20 and 40 character displays to get the new
password while changing the password via the “password” option in voicemail “perso options” menu.
Incident thrown on locked account :

The mailbox gets locked, if the user enters incorrect password to access the mailbox more than the
configured value of “Allow wrong password attempts” in 4645 VM ClassofServices.
A new incident is created to intimate the administrator when the mailbox is locked due to incorrect
password attempts.
The incident number 5412 is created with severity of “Warning” and cause as “Unknown”.
GEA - “Mailbox of <xxxx> is locked due to too many incorrect password attempts ” and <xxxx>
denotes the directory number of locked mailbox.
User interface on locked account :

When the user enters incorrect password, the account gets locked if it exceeds the value of “Allow
wrong password attempts” configured in 4645 VM ClassofServices. User is disconnected from the
mailbox. If the user tries to access the mailbox again, it gets displayed as “service temporarily
inaccessible” and “Good bye” voice guide has been played.
Enhancement :
A new voice guide “your account is locked” is created to intimate the user that the account has been
locked. The display has to be modified as “Account locked, please contact admin” to inform the user
that the account has been locked and further actions to unlock the mailbox. A new string “VM
Locked,call admin” is created for sets having 20 characters display like 4008, 4018, 4019 sets.
New options in Eva_tool :

Two new options “Locked mailboxes” and “Password validity of mailbox” are introduced in Eva_tool.
The following picture shows the screen shot of two new options “Locked mailboxes” and “Password
validity of mailbox”.

TC2306 ed.03
screen shot of three sub options of Locked mailboxes :

TC2306 ed.03
screen shot of three sub options of Password validity of mailbox :

TC2306 ed.03
19.2.9 Mobility
IP dect R170 support has been tested with minimum versions :
DAP firmware for 4080 Access Point :
4910b62a.dwl
IPDECT R170 DAP firmware for 8340 Access Point :
4920b62a.dwl
DAP loader package : 4992030a.dwl
DAP controller versions : 6.21.0163
This version is available on Business Portal

TC2306 ed.03
19.2.10 IP Enhancement
19.2.10.1 OmniPCX Enterprise Media Services : dynamic voice guide recording on OMS
Before this evolution, dynamic voice guide recording was not possible with OMS. (listening dynamic voice
guide was already possible ).
With this evolution, recording a dynamic voice guide on OMS is now possible (same operations as with GD
couplers ).
19.2.11 Call Handling features
19.2.11.1 Diffusion of an "announcement message" to agent (Aviva) ( CROXE -527)
 Goal of the feature:
The aim of this feature is to play to an ACD Agent, when he off-hooks a call distributed by a RSI, a
Routing Pilot or a Statistic Pilot with a new guide named Identification guide. This Identification guide
allows the ACD Agent to know the identity of the RSI, the Routing Pilot or the Statistic Pilot for which
it processes the call without seeing any written information. During the period when the Identification
guide is played to the ACD Agent, the caller is connected to the Ring Back tone. When the diffusion of
the Identification guide is terminated, the caller and the ACD Agent go in communication.
 Implementation and use of the feature:
Case 1 : Only Identification guide is operational
When the ACD Agent takes the call, the caller is connected to the Ring Back tone and the ACD Agent
to the Identification guide. At the end of the Identification guide, caller and ACD Agent are in
communication.
Case 2 : Identification guide and Agent Presentation guide are operational
When the ACD Agent takes the call, the caller is connected to the Agent Presentation guide and the
ACD Agent to the Identification guide. Three possibilities :
- If Agent Presentation guide ends first, the caller is connected to the Ring Back tone and the ACD
Agent is still connected to the Identification guide. At the end of the Identification guide, caller and
ACD Agent are in communication. (identical to Use Case 1)
- If Identification guide ends first, the caller is still connected to the Agent Presentation guide
and the ACD Agent is connected to the Silence. At the end of the Agent Presentation guide, caller and
ACD Agent are in communication.

TC2306 ed.03
- If the ACD Agent selects the specific EndGuide softkey on the set, both Agent Presentation guide
and Identification guide are ended and caller and ACD Agent are in communication
19.2.11.2 Multi-Country: Provide right calling number in case of external forwarding

Multi-Country: Provide right calling number in case of external forwarding in M1 release.
Implementation and use of the feature:
The feature provide correct calling no ;
When user A, internal set or external caller, calls user B and B is forwarded to external number C (e.g. to
mobile phone), OXE has to provide a public calling number in the outgoing call toward C.
This feature will work when user A and user B are in different /same country-code.
19.2.11.3 Deleting alarms on dect takes far too many clicks

The purpose of this feature is to provide an option in the sub menu of a message to delete all alarm messages
at one shot regardless of whether it is read or not.
This feature is applicable only for AGAP handsets.
The purpose of this feature is to provide an option in the sub menu of a message to delete all alarm messages
at one shot regardless of whether it is read or not.
The alarm messages received by the DECT set from the Alarm server will be accessed by selecting the alarm
icon in the top right corner of the idle screen.
After selecting the alarm icon it will display the number of alarm messages with date and time.
User can read the alarm message by pressing the OK key. Pressing OK key with alarm message content, will
open the sub menu with a new option “Delete all” in the sub menu of a particular message
Next Option to go to the next message.
Delete Option to delete the current message. Already available Cancel option is renamed as “Delete”.
Delete all Option to delete all messages in one shot.
Back Option to go back to the previous page which is displaying the message content.
If the user selected the “Delete all” option, the user will be prompted for confirmation to delete all.
If the user pressed the OK key, then all alarm messages of that user will be deleted in the list.
19.2.11.4 Loudspeaker Level Management per Terminal (PER 3088)

Allows an external alarm application to set the loudspeaker level when making alarm calls via loudspeaker
announcement.
This feature is applicable only for Alcatel-Lucent 8&9 series sets.
Alarm calls using loudspeaker announcement feature can be missed sometimes because the loudspeaker level
has been set too low. So this feature is to allow the alarm application to specify an audio level to be applied
during the alarm calls.
Alarm applications are connected to OXE by trunks like ABC-F, QSIG and SIP.
This feature is applicable when OXE is connected to alarm process via ABC-F only (Including ABC-F links, TDM
or IP Trunk Group)

TC2306 ed.03
In ABC-F network topology (Including ABC-F links, TDM or IP Trunk Group), this feature will be available for
the called user only when it is updated in M1. The transit nodes may or may not be in M1.
The following and already existing parameter must be configured as below to enable the Call Announcement
feature :
Classes of Service -> Phone Features COS -> Review/Modify -> Rights-> Prot.against call announc. : 0
In addition to this Phone Feature COS, the below mentioned parameter is enabled to set Call Announcement
feature when called set is busy :
System -> Descend hierarchy -> Other System Param. -> Descend hierarchy -> Spec. Customer Features
Parameters -> Review/Modify : No Call Announcement on busy set + False
19.2.11.5 Multi-device
Tandem is a feature which allows a user to own two sets under a unique telephone number.
One set is called main, and another one is called secondary. The tandem function is defined so that the
telephone services are provided homogeneously on the two sets.
The aim of this new feature is to increase the number of sets for same user. Such a configuration is
called “multi devices”. Such a user is called “Multi devices user”, or MDU. The limit of the sets for a MDU is 5
multi-lines sets, (1 main set and 4 secondary sets).
The main set can be NOE, UA, IpDesktopSoftphone, SEPLOS, DSS, DSU.
The main set can be controlled by an OTC PC in mode remote call control.
The secondary sets can be NOE, UA, DECT, MIPT, MLA, SEPLOS, Remote Extension, IpDesktopSoftphone,
nomadic.
All functionalities and restrictions of the tandem (2 sets) are also available for the multi-device user.
Any secondary set can be called by its own number, in this case, the call is not considered as a MDU call. (so
others secondary sets are not called)
When any set (main or secondary) is out of service, the multi-device user continues to work with other sets.
New data in Phone Features CoS : “Ring secondaries if Main OoS” : this parameter is used to select what
is ringing, in relation with the 2 others already existing data: “forward if set is oos” in Phone Features CoS and
“Overflow to sec tandem if main oos“ in System Option, when a tandem or MDU is called with a main Oos.
When main set is Oos :

3 datas manage this part:
 “forward if set is oos” in Phone Features CoS
 “Overflow to sec tandem if main oos” in System Option
 “Ring secondaries if Main OoS” in Phone Features CoS
A “forward” is initiated (or not) according to “forward if set is oos” and “Overflow to sec tandem if main oos”,
when the main becomes Oos ( this is an already existing feature on tandem).
The MDU works according the same “philosophy” of the tandem. The only difference is that the test on the
secondary in service is repeated on all secondary.
Restrictions already existing on the tandem feature, before “multi-device”

TC2306 ed.03
- Feature Callback on busy :
When any set of the MDU makes a callback on busy on a set, when the last one is free, it notifies “Callback is
proceeding” to the set that has requested the callback on busy. (other sets of the MDU are not notified).
- Feature Boss/Secretary
When we manage Executive/Secretary for the MDU (so, the Executive or the Secretary is a MDU), the
“Executive Call button” or the “Secretary Call button” is only present on the main set of the MDU.
- Features not provided when roaming:
Reading the metering counter
Call parking
Call transfer within the tandem
Notification and consultation of the text mail
Call back on no answer is only available on the DECT in roaming, not on all sets of the MDU. If no DECT
roaming is present in the MDU, in this case, the callback on no answer is present on all sets of the MDU.
Access to the MDU’s ISDN unanswered call directory.
Wake up
- When a set calls directly the secondary set by its own directory number, the features “callback” and
“leave text message” are not available.
Call logs
Call logs are the same on all sets of the multi-device user.
Keep the current behavior of tandem.
Rapid Call Shift

If Rapid Call Shift is executed from any set of MDU, the first call in conversation state found in the list of MDU
is switched to this set.
Extended Call Shift

If the number given with Extended Call Shift is a physical one of the secondary, so the call in conversation
state of this secondary set is used to switch. But if the number given is the MDU main number, in this case the
first call in conversation state found in the list of the MDU is used.
OTC PC
In mode RCC, (remote call control), the OTC PC is compatible with the MDU. It means that the
following actions are possible on the OTC PC which controls the main set of the MDU:
- call supervision,
- calls starting and ending,
- the Audio is always on the main set. (nevers on the PC)
Notes:
The OTC PC which controls the main set of a tandem also sees the secondary set. This OTC PC can release a
communication established between the secondary set and someone... This kind of things is certainly not
available with the others secondary of a MDU (modifications needed in OTC PC...)
The OTC PC in others mode is not fully compatible (modifications needed in OTC PC and in OXE...)
Feature “No ringing”

TC2306 ed.03
The feature “No ringing” can be used on each device of the MDU (except DECT, REM). In this case, MDU calls
are still presented on this device, but without ringing (except SEPLOS). These calls can be taken on this
device.
Feature “remote extension activation, remote extension deactivation”

If a secondary set is a remote extension, “Remote_Extension_Activation” and
“Remote_Extension_Deactivation” prefixes can be used to route (or not) MDU calls to this remote extension.
If “Remote_Extension_Deactivation” prefix is managed in a programmable button, a flip/flop allows
Activation/deactivation.
Tools:
“zdpost”
Tool “zdpost” will display all secondary sets, using the command zdpost with the Main set MCDU. If zdpost is
used with a secondary MCDU set, there is no evolution, (only information about main set and about this
secondary set are displayed).
“mtracer / actdbg”
A new debug option “mdu” is added to use with actdbg, it allows adding the traces for this new feature.
“Multidevice”
A new tool has been added for this feature named “multidevice” which displays the list of multidevices added
to the main device.
19.2.11.6 Extend the capacity of casual conference

The size of a conference circuit requested for a casual conference is actually 7, thanks to this
evolution; it will be also possible to request a casual conference with a size of 15 or 30. A dedicated new
system parameter is created to define the size of casual conference circuits. The conference circuits need to
be able to insert a “bip”; so the max number of participants will be respectively 6, 14 and 29
Two new attributes are added (path : IP / IP Domain) :
- One attribute indicates if I want to use the conference circuits of the other domains. “Accept conf.
circ. of other dom.”
With no :
we search for conference circuits only in do main of the user who starts the conference
With yes :
we search for conference circuits in domain of the user who starts the conference and in the
others domains with the following option to true
- One attribute indicates if my own conference circuits can be used by another domain. “Provide conf.
circ. to other dom”
With no :
this domain forbids others domains to use its conference circuits
With yes :
this domain allows others domains to use its conference circuits.

TC2306 ed.03
With these 2 options to “yes” for all domains, the behavior is the same as before this evolution.
This is the default configuration (search conference circuitin all domains)
These new attributes concern all types of conferences :

Casual conference , Meet me conference, Add-on conference, Interphony, Announcement
Path : System / Other system Param / Spec. Customer Features Parameters /”Max participants in
casual conf”
This new system parameter can take the following values 7 or 15 or 30.
With ”Max participants in casual conf” = X,
If a conference circuit of size X is free, this circuit is taken. In this conference, we can have :
[1 master + (X-2) others + 1 Bip ]
If there is no conference circuit sized X is available, a conference circuit sized lower than X is searched, if it is
free, this circuit is taken.
If there is no conference circuit sized lower than X, a conference circuit sized higher than X is searched, if it is
free, this circuit is taken, else, the conference cannot takes place.
With this evolution, the number of participants depends on the size of the conference circuit used (new
behavior).
If the size (S) of the used conference circuit is different than the value of ”Max participants in casual conf”, the
conference can contain the conference master + up to (S-2) participants + eventually a Bip.
Checklist of existing parameters :

 System/Other System Param/Spec Customer Features Parameters /casual conference ->True
 Maximum simultaneous casual conferences (through cfgUpdate command) -> Non zero
 Categories/Phone Facilities Categories/Casual Conference ->1
 Available conference circuits with type “ADD ON”
Maintenance tools :
“cnx dom”, “cnx cc”, “cfnstat”

TC2306 ed.03
19.2.11.7 Call duration control enhancements
The new development is to enable the existing behavior for both outgoing and incoming calls for public and
private (ABC-F and QSIG) trunks after respective timer expires, if Timed Call Release is enabled.
To achieve this in M1, two new timers are introduced for outgoing and incoming call respectively.
If the value of these new timers is 0, then Timer 260 is used for the respective call in that direction. If the
value is not 0, then that configured value is used as timer for call release.
In L2, Timer 260 is used to release both incoming and outgoing calls.
In L2
There is no change in the existing Phone Features CoS Right “Timed Call Release” but a new system option
“Timed Incoming Call Release”, which is of Boolean type, is added to enable this feature for both incoming
and outgoing calls.
Below table can be referred for the better understanding

TC2306 ed.03
In M1
The new development is to disable the existing Phone Features CoS Right (Boolean) “Timed Call Release”
and adding a new parameter Phone Features CoS (Enum) “Timed Call Release” which contains three values:
- None
- Outgoing only
- and Both (incoming and outgoing)
Two new timers are added in Phone Features CoS, Release Timer for Outgoing Call and Release Timer for
Incoming Call. If the value of Release Timer is 0, then Timer 260 is used for the respective call in that direction
If the value is not 0, then that configured value is used as timer for call release.
Please refer below table for better understanding,
Management :
Path:
mgr : Classes of Services > Phone Features CoS > All Instances
In L2:
As of R11.2.2, the existing phone features CoS Rights “Timed Call Release” is used
In M1:
1)
Timed Call Release (Old) From this version, this parameter is hidden from the existing place and is used below
Phone Cos Rights in the Phone Features CoS menu
19.2.11.8 Rainbow
Check ALE communication on the different channels for availability on Rainbow offers.

TC2306 ed.03
Rainbow – a cloud-based freemium services operated by ALE is the opportunity to bring flexible Unified
Communication (UC) services combined with legacy PBX telephony without major changes in the existing IT
infrastructure while benefiting from scalable services and multi-site federation. This service provides customers
technology investment protection irrespective of existing communication systems. Features of Rainbow include
IM, rich presence, voice and video conversation including screen and file sharing.
ALE PBX cloud enablement architecture is made of two software components:

- The PBX CC.Control Agent (CCCA), a CPE-hosted piece of code, acting as a query/event gateway
between the cloud and native PBX services. The CCCA can be either directly embedded in the PBX
for compatible OXE releases, or located on an external component deployed in front of the PBX (not
available today).
- The PBX Cloud Gateway (PCG), located in the Rainbow cloud infrastructure, converting the PBX
native interfaces (CSTA, Web Services…) into the generic CC.Control interface (Rainbow XMPP)
used in Rainbow core infrastructure. PCG is a massively multi-tenant and multi instances capable
component. The PCG acts as unique access point to the PBX from the Rainbow infrastructure core,
allowing multiple rainbow-based applications reaching PBX services.
Connection between PCG agents and CCCA is maintained through a unique TLS-secured Web Socket. This
connection is initiated by CCCA towards Rainbow Cloud instance. Once established, this TCP connection is
used as a tunnel through which PCG agent can perform queries and CCCA can send event notifications. The
CCCA ensures that this WSS connection is always up and running (or initiate a new one in case of network
failure).
Management/maintenance : to be updated in a further edition of the document.
19.2.12 SIP Trunking features
19.2.12.1 Sipmotor new incidents - Incident Management in SIP
New incidents related to sipmotor :

SIP_STACK_DEGRADE_MODE_ENTRY 5826
SIP_STACK_DEGRADE_MODE_EXIT 5827
SIP_STACK_DEGRADE_MODE_EXT_RESTART 5828
SIP_QUARANTINE_STATE_ON_OR_OFF 5829
SIP_MOTOR_STARTUP_FAILED 5830
SIP_MOTOR_RESTART 5831
SIP_TLS_LINK_NOK 5832
ACTIVE_LICENSE_THRESHOLD 5833
 Stack Degraded Mode:

The SIP Motor cannot handle more than 8000 active dialogs at the same time. For INVITE transactions, a
dialog becomes active at its creation, and the associated context is released at the end of the call, or while
receiving any other response than 200.OK
For SUBSCRIBE transactions, a dialog becomes active at its creation, and the associated context is released
at subscription timer expiry

TC2306 ed.03
For REGISTER and OPTIONS transactions, a dialog becomes active at its creation, and the associated
context is released at the receipt of any response – 200.OK, 4xx, 5xx or 5xx
SIPMotor moves to “degraded” mode as soon as this maximum of 8000 simultaneous active dialogs is
reached. In that situation, incoming requests are rejected with a 503.Service Unavailable response, and
outgoing requests are internally rejected.
It moves back to “normal” mode as soon as the number of active dialogs decreases below 8000. The incoming
requests are rejected with a 503.Service Unavailable response, which includes a Retry-After header
indicating the “Degraded mode Time To Live”, and outgoing requests are internally rejected.
Incidents 5826, 5827 and 5828 are used for “SIP Degraded Mode”
Example : 5826 “SIP Degraded mode: Entry”
5827 “SIP Degraded mode: Exit”
5828 “SIP Degraded mode: Exit and Restart”
 Quarantine State:
As soon as an IP address is put in or leaves the quarantine state, the new incident 5829 “Quarantine
state” is generated.
Example: 5829: “Quarantine state / IP@ : P1 ”
P1 represents IP Address and State
5829: IP@: 172.19.112.110 is add to Quarantined //IP address Added to Quarantined list
5829: IP@: 172.19.112.110 is removed from Quarantined //IP address Removed from Quarantined list
 Start SIP Motor Failed:

If SIP Motor is not capable to start then sipmotor failed will happen. Incident 5830 “Start SIP Motor failed” is
used to capture SIP Motor startup failure
As an additional information, it provides a “reason: xxxx” argument.
Example: 5830:“Start SIP Motor failed / reason : P1”
P1 represents reason for failed. P1 could be any of the following :
00 Remanent error
01 Chorus Port error
02 Register to Monitel error
03 Register to Call Handling error
5830:“Start SIP Motor failed reason : 00”
 SIP Motor Restart:

SIP Motor will restart for various reasons.
Reasons to restart:
Manual restart:
Manually the SIPMOTOR process restarted for various reason.
Freezing:
The goal is to periodically (A dedicated timer value to be defined) check the current state of the SIP Motor, in
order to be able to automatically exit from the “freezing” state.
Crash
Due to Exceptions in sip motor.
Example: 5831:“Start SIP Motor restart / reason : P1”
P1 represents reason for restart, P1 could be any of the following
00 Manual restart

TC2306 ed.03
01 Freeze
02 Crash
5831:“Start SIP Motor reason : 00 ”
 Start SIP Motor Failed:

If SIP Motor is not capable to start then sip motor failed will happen. Incident 5830 “Start SIP Motor failed” is
used to capture SIP Motor startup failure
As an additional information, it provides a “reason: xxxx” argument.
Example: 5830:“Start SIP Motor failed / reason : P1”
P1 represents reason for failed. P1 could be any of the following
00 Remanent error
01 Chrous Port error
02 Register to Monitel error
03 Register to Call Handling error
5830:“Start SIP Motor failed reason : 00”
 SIP Motor Restart:

SIP Motor will restart for various reasons.
Reasons to restart:
Manual restart:
Manually the SIPMOTOR process restarted for various reason.
Freezing:
The goal is to periodically (A dedicated timer value to be defined) check the current state
of the SIP Motor, in order to be able to automatically exit from the “freezing” state. For more
information refer 1.4 [section 5].
Crash
Due to Exceptions in sip motor.
Example: 5831:“Start SIP Motor restart / reason : P1”
P1 represents reason for restart, P1 could be any of the following
00 Manual restart
01 Freeze
02 Crash
5831:“Start SIP Motor reason : 00 ”
 SIP TLS link:

Set up TLS links may succeed or fail for any reason. If it occurs, the incident 5832 “SIP TLS link” is
generated.
As an additional information, it provides both the “gateway # : xxxx” it refers to, and a “Up/Down”
state arguments.
Example : 5832: “SIP TLS link / gateway : P1 / P2”
P1 represents gateway number
P2 represents link up (1) or down (0)
5832: “SIP TLS link / gateway : 100 / 0”
Active Licences Above / Below Threshold:

TC2306 ed.03
A new system option Overflow licenses threshold is introduced, it indicates the threshold value in
percentage, incidents 5833 is generated whenever the usage of licenses reach the threshold (above or below).
If this parameter is set to 0, these incidents are never generated.
Overflow licenses threshold : 0 .. 100 (Default : 80)
If set to any other value, one of these incidents is generated when the number of current licenses overflows or
decreases regarding this percentage.
Example : 5833 “SIP licenses are (P1) than the threshold which has been set to (P2) %”
P1 represents Above (>) or Below (<)
P2 represents Percentage
5833 “SIP licenses are > than the threshold which has been set to 80 %”
19.2.12.2 Public SIP Trunking SIP user_agent information to differenciate between OXE
system and OXE embedded into OpenTouch BE system
3BA_29000_1483_QZZZA CROXE-2248 PER (crqms00185337)
Some SIP carriers may like to differentiate a pure OXE topology from an OT one, through the content of the
User-Agent header.
They may also wish to customize its content with supplementary information, or to make it completely
manageable
mgr path : SIP/SIP Proxy / (Review-Modify) /All Instance : “User Agent Identifier : %”
19.2.13 INFRA CLOUD

FEATURE AVAILABLE FOR MD1
CloudConnect (CC)
 Cloud Connect feature will ve able to connect any OXE R12 to the ALE Cloud & take advantage of
features like :
o FTR/RTR
o Fleet Dash Board
 FTF/RTR is here mainly to avoid having the Flex/dongle equipement on virtualized systems.
 FTR with PIN code :
Under certain circumstances (fraud detection, administrator change, retrieval from Panic mode...) it
may be necessary to reinitialize system‟s credentials for permanent connection to CCI out of the
context of the Activation Account.
This is done by requesting to the helpdesk a temporary activation account. This activation account is
similar to the one opened when creating the system entry in eLP except that it is associated with a
PIN code composed of 6 decimal digits : the jabber ID is not only built from CC-suite-ID and domain,
but from CC-suite-ID, PIN and domain.
When the system performs successful FTR operation with this account, a new set of credentials is
provided to system, but some initialization is also done on CCI side. For instance, system RTR
previous account is deleted (to retrieve from Panic mode).

TC2306 ed.03
On OXE side this FTR operation is quite identical to the one described previously except one
important difference at the end of the operation.
Like in standard FTR, after successful operation, the new credentials are saved in the file and two
XML messages are sent to CC-Agent: one to request a reset of the permanent link and a second
one to notify the services running in CC-Process.
In the case of FTR with PIN code, this second message is of paramount importance and must be
received by services: it‟s why it is forbidden to perform FTR with Pin code operation if CC-Agent and
CC-Process are not running on system.
A check is done by the tool before performing the operation.
 Management done in 2 parts : “netadmin” & “mgr”

o “mgr” : 3 possibilities now : work on physical cpuid, work on flex server & work on Cloud
Connect. Changing a mode needs to be followed by a reboot
o “netadmin” menu “19. 'Cloud Connect'”
 Maintenance :
o Use “CCtool”
o Use “ftrtool”
o System incidents :
 647 to 651 (RTR feature)
o Logs :
 “/tmpd/CCAlarm.log”
 “/var/log/syslog” : grep on “CC” string
 /var/log/ftrtool.log (.log.0, .log.1 …etc)
 /var/log/ccagent.log (.log.0, .log.1 …etc)
 GOING FROM VIRTUALIZED TO CLOUD
o 2 steps :
 De-activate the flex
 Reboot
 Manage the CC connection
 Reboot
Summary of licenses management :

RTR enabled
Flex-LM enabled and Licensing Mechanism Used
CC-SUITE-ID is Present in SWK file
YES YES Not Allowed
YES NO Flex-LM Licensing used
NO YES CC-RTR is used
NO NO CPU ID Check used
19.2.14 WBM (Web Based Management)

Activation is “ON” by default

TC2306 ed.03
Web server is controlled by a Boolean under “system/ Other System Param./ System Parameters” : “Activate
the Web server”
“netadmin” menu has no effect now (not operational)
Maintenance :
- Check the 2 services/processes :
Nginx:
(601)xb006001> ps -edf | grep nginx
root 4246 3337 4246 0 1 Mar09 ? 00:00:00 nginx: master process
/usr/local/openresty/nginx/sbin/nginx -g daemon off; -c /usr/local/openresty/nginx/conf/wbm.conf
root 4263 4246 4263 0 1 Mar09 ? 00:00:00 nginx: worker process
CMISE/JSON Gateway:
(601)xb006001> ps -edf | grep wbm
root 4246 3337 4246 0 1 Mar09 ? 00:00:00 nginx: master process
/usr/local/openresty/nginx/sbin/nginx -g daemon off; -c /usr/local/openresty/nginx/conf/wbm.conf
mtcl 4259 3337 4259 0 1 Mar09 ? 00:00:00 /DHS3bin/servers/WBM -P :2577 -log
/tmpd/wbm.log -a wbm --nodico
- Get the following logs/files :

- /tmpd/wbm.log
- /var/log/openresty/access.log
- /var/log/openresty/error.log
- /usr/local/openresty/nginx/conf/wbm.conf
- Get also the trace application file from the broswer (« About » then click on « Events log »
beside the version number) :

TC2306 ed.03
The file is named : “OXE-WBM-<date-time>.log”
Security :
- Unlike the system policy : “when we try to connect 3 times the system blocks any attempt for 15 sec.”
- When a client connects via HTTPS (WBM), we rely on the authentication module of our Web server
(Nginx). It is configured so that each attempt must be spaced by at least ½ second.

TC2306 ed.03
- Considering that password should follow system policy: 8 characters (maj & min) with at least 2
alphanumerical and 1 special character… etc (see OXE policy - swinst), the brute force attack must be
discarded.
- ½ second is managed at server side and is shared between sessions
- It avoids dos attack too – it is always possible to connect to OXE with the right password
19.3 Features under PCS

IPV6 (check for IPV6 PCS document).
As a reminder SIP TLS is still under PCS control.
20 COUNTRIES IN WHICH RELEASE 12.0 IS TECHNICALLY RELEASED

OmniPCX Enterprise Release 12.0 concerns the countries mentioned in the table below.
The availability of IP Touch Security Solution for these countries is mentioned in the Logistic and Customs
product information document, which is available on Business Portal, in the right column "Related documents".
In this document, specify the market and the product line, then click on "Update item list" button: the columns
specific to IP Touch Security solution have a red header (columns from "Main origin" to "CCATS").
Country Installation OmniPCX Enterprise R12.0

Market System Software to be used
Installation
Market ISO Country code
Market Country name initial to be Bdd
Code Reminder
used
1 Afganistan AF
2 ÅLAND ISLANDS AX
3 BU Albania pl PL AL
4 GM Algeria dz DZ DZ
5 American Samoa AS
6 Andora AD
7 GY Angola pt PT AO
8 Anguilla AI
9 Antartica AQ
10 Antigua and Barbuda AG
11 KF Argentina ar AR AR
12 Armenia ro RO AM
13 Aruba AW
14 KN Australia as AS AU
15 CF Austria au AU AT
16 Azerbaijan ru SU AZ
17 Bahamas BS
18 FL Bahrain bh BH BH

TC2306 ed.03
19 EH Bangladesh bd BD BD
20 Barbados BB
21 AS Belgium be BE BE
22 AT BELGACOM BELGIUM be BE BE
23 Belize BZ
24 GB Benin ci X1 BJ
25 Bermuda BM
26 Bhutan BT
27 DG Bielorussia ru SU SU
28 JZ Bolivia ln LN BO
29 DX Bosnia and Herzegovia yu YU BA
30 Bostwana BW
31 Bouvet Island BV
32 KG Brazil br BR BR
33 Brithish Indian Ocean Territory IO
34 Brunei Darussalam BN
35 BV Bulgaria bg BG BG
36 GA Burkina Faso ci X1 BF
37 GZ Burundi ke X1 BI
38 EN Cambodia kh KH KH
39 GW Cameroon x1 X2 CM
40 JD Canada us US CA
41 Cape Verde CV
42 Cayman Islands KY
43 HA Central African Republic x1 X1 CF
44 GR Chad x1 X1 TD
45 KH Chile cl CL CL
46 DZ China (PRC) cn CN CN
47 Christmas Island CX
48 Cocos Island CC
49 KJ Colombia co CO CO
50 GT Comoros fr FR KM
51 GU Comores Rep Isl. fr FR
52 HB Congo x1 X1 CG
53 HB CONGO, THE Dem REP OF THE x1 X1 CD
54 Cook Islands CK
55 JJ Costa Rica cr CR CR
56 GX Cote D'ivoire ci CI CI
57 DH Croatia hr HR HR
58 JK Cuba ln LN CU
59 CW Cyprus cy CY CY
60 BZ Czech Republic cz CZ CZ
61 AR Deutsch Telecom ge GE DE
62 AV Denmark de DE DK
63 GV Djibouti x1 X1 DJ
64 Dominica DM

TC2306 ed.03
65 JV Dominican Republic ln LN DO
66 East Timor or TIMOR-LESTE TP
67 KK Ecuador ec EC EC
68 FD Egypt eg EG EG
69 JL El Salvador se SE SV
70 Equatorial Guinea GQ
71 Eritrea ER
72 DJ Estonia ee EE EE
73 HC Ethiopia et ET ET
74 Falkland Islands FK
75 Faroe Islands FO
76 Fiji FJ
77 CJ Finland fi FI FI
78 AA France fr FR FR
79 AK France fr FR FR
80 ze France Telecom fr FR FR
81 French Guiana fr GF
82 LA French Polynesia pf PF PF
83 French Southern Territories fr FR TF
84 HD Gabon x1 X2 GA
85 GC Gambia sn X1 GM
86 Georgia ru SU GE
87 AP Germany ge GE DE
88 GD Ghana ci X1 GH
89 Gibraltar GI
90 BB Greece gr GR GR
91 Greenland GL
92 Grenada GD
93 KV Guadeloupe fr FR GP
94 Guam GU
95 JM Guatemala ln LN GT
96 GE Guinea x1 X1 GN
97 Guinea Bissau GW
98 KW Guyana fr FR GY
99 JN Haiti ln LN HT
100 Heard Islands and Mcdonald HM
101 JP Honduras ln LN HN
102 ED Hong Kong hk HK HK
103 BW Hungary hu HU HU
104 CX Iceland de DE IS
105 EY India in IN IN
106 EM Indonesia ii ID ID
107 FS Iran ir IR IR
108 Iraq IQ
109 BD Ireland ie IE IE
110 FT Israel il IL IL

TC2306 ed.03
111 BF Italy it IT IT
112 BG Italia Telecom it IT IT
113 JR Jamaica ln LN JM
114 EE Japan jp JP JP
115 FU Jordan x1 X1 JO
116 DL Kazakhstan ru SU KZ
117 HF Kenya ke KE KE
118 Kiribati KI
119 Korea DPR KP
120 FH Kuwait kw KW KW
121 Kyrgystan ru SU KG
122 EP Laos la LA LA
123 XE Latin America ln LN
124 DN Latvia lv LV LV
125 FJ Lebanon lb LB LB
126 Lesotho LS
127 Liberia LR
128 FE Libyan Arab Jamahiriya x1 X1 LY
129 Liechtenstein LI
130 DP Lithuania lt LT LT
131 BK Luxembourg lx LX LU
132 Macau MO
133 HG Madagascar fr FR MG
134 DW MACEDONIA, THE FORMER pl PL

YUGOSLAV REPUBLIC OF MK
135 HH Malawi za X1 MW
136 ET Malaysia my MY MY
137 FA Maldives mv MV MV
138 GH Mali sn X1 ML
139 CZ Malta mt MT MT
140 Marshall Islands MH
141 KX Martinique fr FR MQ
142 GJ Mauritania sn X1 MR
143 HK Mauritius fr FR MU
144 KY Mayotte fr FR YT
145 JQ Mexico mx MX MX
146 Micronesia FM
147 DQ Moldavia pl PL MD
148 Monaco fr FR MC
149 Mongolia MN
150 Montserrat MS
151 GP Morocco ma MA MA
152 HL Mozambique pt PT MZ
153 EJ Myanmar mm MM MM
154 Nambia NA
155 Nauru NR

TC2306 ed.03
156 EV Nepal np NP NP
157 BL Netherlands nl NL NL
158 BN Netherlands KPN nl NL NL
159 Netherland Antilles AN
160 KZ New Caledonia fr FR NC
161 KS New Zealand nz NZ NZ
162 JS Nicaragua ln LN NI
163 GK Niger x1 NG NE
164 HW Nigeria ng NG NG
165 Niue NU
166 Norfolk Island NF
167 Northern Mariana MP
168 CM Norway no NO NO
169 FV Oman om OM OM
170 FB Pakistan pk PK PK
171 Palau PW
172 PALESTINIAN TER, OCC PS
173 JT Panama ln LN PA
174 Papua New Guinea PG
175 KA Paraguay ar AR PY
176 KL Peru pe PE PE
177 EG Philippines ph PH PH
178 Pitcairn PN
179 BX Poland pl PL PL
180 BQ Portugal pt PT PT
181 Puerto Rico PR
182 FW Qatar ae AE QA
183 LB Reunion fr FR RE
184 BY Romania ro RO RO
185 CC Russia ru SU RU
186 HP Rwanda ke X1 RW
187 Saint Helena SH
188 Saint Kitts and Nevis KN
189 Saint Lucia LC
190 LH Saint Martin (Guadeloupe) fr FR
191 LC Saint Pierre and Miquelon fr FR PM
192 Saint Vincent and the Grenadines VC
193 Samoa WS
194 San Marino SM
195 Sao Tome and Principe ST
196 FK Saudi Arabia sa SA SA
197 HJ Senegal sn SN SN
198 CB SERBIA AND MONTENEGRO yu YU CS
199 HY Seychelles fr FR SC
200 Sierra Leone SL
201 EQ Singapore sg SG SG

TC2306 ed.03
202 DS Slovakia sl SL SK
203 DY Slovenia si SI SI
204 Solomon Islands SB
205 Somalia SO
206 HZ South Africa za ZA ZA
207 EB South Korea kr KR KR
208 South Georgia GS
209 AX Spain es SP ES
210 EW Sri Lanka lk LK LK
211 FF Sudan x1 X1 SD
212 Suriname SR
213 Svalbard and Jan Mayen SJ
214 Swaziland SZ
215 CQ Sweden sv SV SE
216 CS Switzerland ch CH CH
217 FX Syrian Arab Republic sy SY SY
218 EC Taiwan tw TW TW
219 Tajikistan ru SU TJ
220 HR Tanzania ke X1 TZ
221 ER Thailand th TH TH
222 Timore TL
223 GS Togo ci CI TG
224 Tokelau TK
225 Tonga TO
226 Trinidad and Tobago TT
227 GQ Tunisia tn TN TN
228 DC Turkey tr TR TR
229 Turkmennistan ru SU TM
230 Turks and Caicos Islands TC
231 TUVALU TV
232 HN Uganda ke X1 UG
233 DV Ukraine ru SU UA
234 FM United Arab Emirates ae AE AE
235 BS United Kingdom uk UK GB
236 JD United States of America us US US
237 United States Minor UM
238 KC Uruguay uy UY UY
239 DR Uzbekistan ru SU UZ
240 Vanuatu VU
241 Vatican VA
242 KM Venezuela ve VE VE
243 ES Viet Nam vn VN VN
244 VIRGIN ISLANDS, BRITISH VG
245 VIRGIN ISLANDS, U.S. VI
246 LE Wallis and Futuna Islands fr FR WF
247 Western Sahara EH

TC2306 ed.03
248 FY Yemen x1 X1 YE
249 Zaire CD
250 Zambia za ZA ZM
251 HT Zimbabwe zb ZB ZW
252
253 export x1
254 export franco x2
255 x3
256 x4
257 x5
258 CG Telecom Austria au AU AT
21 REMARKS & RESTRICTIONS
21.1 RESTRICTIONS, KNOWN ISSUES

Some old information were removed. Consult previous document (release 11.2) if needed.
 Virtualisation & 4645 voice mail :
Warning Voice mail 4645 embedded in an oxe VM is under restriction due to a drastic increase in cpu
load !! The fix will be available through a kernel correction brought in OXE R12.0 MD1
 WBM : over a 1000 users performance decrease : fixed in MD1 patch

 WBM : Radius authentication is not working
 “mao for rebuild” backup file cannot be used from a file coming from a previous release (CROXE-
2141). Issue will be seen from xxx to M1. But not from M1 to later releases. This is a definitive
restriction. Error is “segmentation fault” while restoring mao-dat
 Cloud Connect operation to be released for end of June for MD1.
 Rainbow will be released during end of April for its “Essentials” offer. Paid offer (Business Enterprise)
release planned for end of June.
 Since Android OS Nougat update, some ports historically used by the system are now in conflict with
OS Nougat reserved ones. Default port for signaling is 32512, this port is in the range of reserved
ports in Android 7 (32100 to 32599).
To allow android 7 devices, you must change the configuration of default port (IP-> TSC/IP
Parameters -> UDP port).
You must also take this change in the firewall configuration.
 NOE 3G EE sets :

TC2306 ed.03
o not released yet. Communication will be given later.
o Customization binary is not downloaded to Terminal. Feature planned to be released for MD1
patch (CROXE-3859)
o Upgrade binary for 8078S may need a reboot for those sets. See also chapter. 21.8.10 Will be
fixed in a further patch to be delivered around OXE R12.0 MD1
o Some rare case whith blank communication (fixed in the next firmware 5.00.13)
 Hard disk : recommendations on CPU7s2 : only the hard disks provided by Alcatel-Lucent 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 (limited : from 12.0 to 12.0 & above).
 "Ensure database consistency" (introduced in R9.1)

This feature is intended for cases where MAO modifications are done (mgr “like” management or user set
modification) while the Stand-By is temporarily not present.
The Double main Call Servers case is specific : MAO messages may be stored in the buffer of both Call
Servers. When the duplication link is back operational, if there are stored messages in the Call Server
which reboots as Stand-By (independently of the fact messages may have been stored or not in the Call
Server which stays Main), then they are lost (on both Call Servers) and an incident 439 is displayed to
recommend a manual synchronization (mastercopy). If messages have been stored only in the Call Server
which stays Main, then they will be sent to the Stand-By after its reboot.
Currently the MAO storage has two limitations: the buffer can store only 255 messages and the storing
process cannot last more than two hours. From the patch I1.605.14.e, MAO messages are stored directly
in RAM, removing the buffer limitation.
 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.
 CROXE-3794 : 8018 ssh password change (R12.0 feature) does not work.
 Text message option while calling network user throws a service unobtainable error (CROXE-4029)
 8018 in sip mode : not released yet
 Important: It is prohibited to install any other NAOS (RPM packages or pure binary) than
those provided by ALE OXE.
KVM
OXE installation with PC Installer requires a user input to give a directory during linux installation (see in the
document annexe : 1rst screenshot at page 23)
OXE installation with ALEDS does not work.

TC2306 ed.03
Other virtualized systems :
 Known as unsupported virtualization systems : XEN (implies also Amazon)
 Microsoft HyperV : not supported
21.2 COMMUNICATION SERVERS

21.2.1 Call Server CPU
 Direct connectivity of the Ethernet port of the CS-2 to a port of a switch is mandatory.
 Only auto-negotiation mode is supported on the CS-2 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-2 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.
 As of Release 9.0, CS-2 boards offer Ethernet redundancy with load balancing.
Hard drive
In a standard installation, the following message is displayed. It states that any hard disk larger than 80 GB
will not be used to its real capacity.
Alcatel-Lucent e-Mediate Linux installation

+-------------------+ Disk size +--------------------+
| |
| |
| Disk too big : use optimized up to 80000MB only. |
| +-----+ +----+ |
| | Yes | | No | |
| +-----+ +----+ |
| |
+----------------------------------------------------+
The installation continues automatically after a timeout.
21.2.2 UPS
An UPS is strongly recommended to secure the system against abnormal stops because of power failure.
The UPS is used to make up for the short cuts of the power supply. If the UPS arrives at the end of the
battery, it tries to notify the Call Server / CPU to which its USB cable is connected. In the event of a long time
of power supply cut, it is necessary to stop the Call Server with the shutdown command.
21.2.3 Blade Center (& others)

 Blade Servers are no more compatible as well as other CPUs mentioned in this document
 ACTIS behavior

TC2306 ed.03
o Blade : Actis will let people decide what kind of server will be used to migrate to R12.0 :
Appliance Server or Virtualization.
o CPU5/6/7s1 : Actis will propose a CPU7s2
o CS-1 : Actis will propose CS-2 or Appliance Server depending of the traffic
21.2.4 Passive Communication Server

Passive Call Server as well as main or stand-by CPU must follow the rules of compatibility meaning that CS-1
cpus are not compatible
If updating the software (patch or complete version) of a system equipped with PCS, it is necessary to update
the PCS before updating the version of the Central Com Server (constraint related to database compatibility).
If updating the software of PCS, it is necessary to check that this update does not start in the period of
automatic re-synchronization of the database on the PCS (especially if the method used is the scheduled
Remote Download) because this re-synchronization involves an automatic reboot of the PCS.
When SIP set switches on PCS :
 It has to register again as the Call Server registar database is not replicated on the PCS.
 If it is in dynamic mode, a local DHCP server is required.
 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.
This feature is supported by the following IP equipment:
SIP sets
Alcatel series 8 sets
Alcatel-Lucent 8082 My IC Phone
GD
GA
INTIP
OXE-MS
IOIP
"IP Touch Security Module" : SSM, MSM
Attendant IP Softphone
IP CCAgent Softphone
MIPT sets
IP Dect
The applications able to take into account 2 addresses of CPU are:
Alcatel 4635 (R5.6.x)
Alcatel 4645
OmniTouch Contact Center : CCD/CCS/CCA/CCIVR
OmniTouch Unified Communication R4.0
XML Web services
Application "XML IP Touch"
TSAPI
ACAPI
VoWLAN R2.0

TC2306 ed.03
Features not available on AS and CS:
V1 (4080 RE) - 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
21.2.5 Appliance Servers : Bill Of Material (BOM)

Find below the description of the BOM of the 4 latest appliance servers supported
21.2.5.1 HP DL320e G8v2

TC2306 ed.03
21.2.5.2 IBM/ Lenovo X3250 M5
21.2.5.3 Lenovo X3250 M6

Not released yet. BoM will come later.
21.2.5.4 HP DL20 G9
That server is orderable at the ALE catalog.
It is single power & CANNOT be upgraded to a dual power server.
ALE does not sell that dual power model. It needs to be ordered to HP & add another power module.
UPS system validated is an Eaton 1200.
Check the system documentation for bios modification if A.S. was ordered through a reseller or manufacturer.
Summary of bios modifications to do are :

TC2306 ed.03
Next is the BoM used for this server :

TC2306 ed.03
The power module : reference :

TC2306 ed.03
HP
Description
Qty Part Number Option
900W Gold (92% efficiency)

1 775595-B21
100-240V AC autro-ranging hotplug power supply - field installable - SFF models
21.3 IP CRYSTAL MEDIA GATEWAY

In the
document the name "INTIPA or B" concerns the INTIP board as well as the INTIP2 board.
 The GPA2 is supported in the IP Crystal Media Gateway.
 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 (not compatible R12.0 & above) and
CPU7 (S1/2).
Warning As mentioned previously a CPU7 S1/2 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

TC2306 ed.03
maximum.
21.4 MEDIA GATEWAY

21.4.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 does not 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:
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.
 Due to the possibility of the GD to encrypt directly its signaling link, two versions of GD binaries are
available from Release 9.0: one containing the encryption mechanisms and one without. As for the IP
Touch sets since Release 6.2, the generic OmniPCX Enterprise versions provide the binaries without
the encryption mechanisms, whereas the binaries with these mechanisms will be available in the
corresponding secured patch.
 GD/GA binaries (secured or not) are systematically signed. This information is verified only on PBX in
protect mode.
21.4.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:
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.
21.4.3 Remote connection towards GD/GA/INTIP boards
21.4.3.1 Release 9.0 before patch H1.301.38

For safety reasons, telnet access towards GD/GA/INTIP boards has been disabled. The remote access towards
INTIP boards remains available using the cpl_online command.
Regarding the GD and GA boards, a mechanism similar to that of IP Touch sets has been implemented.
Activation of telnet service for a specific GD using the ippstat command.

TC2306 ed.03
Remote access towards GD/GA using the telnet_al <GD/GA_board_address> command.
Note This command corresponds to telnet <GD/GA_address> -b <CS_real_address>, the b option

allows to force the sender address of the request and in this case not use the main address.
The telnet client of the board GD/GA, which has been suppressed in Release 9.0, was necessary in particular
to access the maintenance commands relative to the H323 process (telnet from the GD on its H323 port
(4560)). These commands are now available through the ccmonitor command of the GD.
21.4.3.2 Releases 8.0.1 (from G1.503.35), 9.0 (from H1.301.38) and 9.1
The telnet activation, used for the GD in Release 9.0 before patch H1.301.38, has a major drawback: in case
the signaling link between the Call Server and the GD wasn’t active, there was no way to activate the telnet,
even locally, for remote debugging.
To overcome this limitation the telnet activation is possible in the same fashion, using a new entry in
"mgconfig" tool (on GD/GA), "14 – Telnet server", which allows to activate & de-activate the telnet for a
limited period. The ippstat method remains possible.
The same process applies to authorize a remote connection via telnet on NGP boards (the ippstat solution
doesn’t apply though).
21.4.4 NGP boards (GD3/GA3/INTIP3)

Find below the different hardware compatibility information related to the use of NGP boards.
NGP boards don’t support the following topics:
Non "Direct RTP mode in network"
Proprietary H323 inter-nodes protocol (only H323 mode is supported)
Proprietary fax mode between Media Gateway (only H323 mode is supported)
Contrary to INTIP, the INTIP3 board doesn’t support transit function. So with NGP, whatever the board used,
the direct RTP mode is the only mode to take into account.
NGP binaries (secured or not) are systematically signed. This signature is verified in all cases by Call Server
(mode protect or bypass).
Resources provisioning on Common Hardware NGP boards:
Armada Compressors N-way conferences Voice Guide 3-way conf DTMF

daughter access receivers
board
GD-3 mix 1x7, 2x7, 3x7, 4x7 or
No 15 16 24 30
1x15, 2x15 or 1x30
No 30 0 16 24 30
1x7, 2x7, 3x7, 4x7 or
Yes 45 16 24 30
1x15, 2x15 or 1x30
Yes 60 0 16 24 30
GA-3 N-conf No 0 4x7 or 2x15 or 1x30 16 3 0
GA-3 mix No 15 1x7, 2x7, 3x7 or 1x15 16 3 0
No 30 0 16 3 0

TC2306 ed.03
Yes 30 3x7, 4x7, 2x15 or 1x30 0 0 0
Yes 45 1x7, 2x7 or 2x15 0 0 0
GA-3 VoIP Yes 60 0 0 0 0
GA-3 3-conf No 0 0 0 21 0
PowerMex N/A N/A N/A 0 24 30
The account root has to be used to enter the console of a NGP board. The account admin exists but doesn’t
allow doing anything.
To reload from scratch a binary in a GD3/GA3/INTIP3 board, just use PC Installer and perform a network boot
of the board: it will automatically reformat its flash and then download the various binary files. The LOLA
mode, used for GD/GD2 boards is no more necessary as the flash reformat is performed automatically. A
reboot of the NGP board is mandatory after the flashing process.
To enter the BIOS of a GD3, GA3 or INTIP3, as for a GD board, the sequence Ctrl-B Ctrl-I has to be done
(rather quickly for NGP).
U-Boot 1.3.0-rc3 (Apr 15 2009 - 16:37:27) 3EH30350AAAI bootl100/000.008

Reset Status: Software Hard, External/Internal Soft, External/Internal Hard
CPU: e300c4, MPC8377, Rev: 21 at 399.999 MHz, CSB: 266 MHz
I2C: ready
DRAM:
DDR DIMM: data bus width is 64 bit without ECC
DDRC ECC mode: OFF
DDR RAM: 256 MB
FLASH: 2 MB <---------------- Press quickly Ctrl-B Ctrl-I immediately after this info
PCI: Bus Dev VenId DevId Class Int
00 17 1064 2102 0000 00
In: serial
Out: serial
Err: serial
Net: TSEC0, TSEC1
21.4.5 OMS (remote access & ESXi configuration rules)

Several modifications were done in relation to secure the access of the OMS. Refer to the precedent document
for more details on older versions. Remember that it is now the « admin » user that should be used to connect
on OMS (ssh -2 command).
Virtualization rules (extract from doc “OT suite –hosting – virtualization”)

… this solution is built with one or several OXE Media Services Base and optional access ports (up to 120 per
Base).
Hardware pre-requisites for OXE MS depends on the number of ports and coding/compression algorithm:
• One dedicated core processing (via “affinity rules”, from vShpere client management) per OXE MS
requiring 100 MHz for the Base.
• Hyperthreading has to be disabled on the OXE MS Virtual Machine
• Processing per port:
• With G711 coding only: 5 MHz with a maximum of 120 ports per OXE MS Base

TC2306 ed.03
• When G729 compression is used: 25 MHz with a maximum of 90 ports per OXE MS Base
• Virtual Hard disk per OXE MS Base: 4 GB
Dedicated and reserved memory PER OXE MS Base: 512 MB of RAM … END of extract
21.5 VoIP
 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/Armada board: the echo delay is limited to 128 ms.
 Direct RTP H323.
The management of H323 direct RTP on OmniPCX Enterprise must be carefully enabled since all H323
terminals of the installation must be able to reroute the H245 RTP flow called "Empty Terminal Capability Set"
or "Voice Path Replacement".
No direct RTP between SIP set and a H323 terminal.
No direct RTP between H323 terminals with different compression algorithms (for instance case of H323
terminal in G723 or G729 calling a 4645 in G711)
 Direct RTP in network.
It is used with IP devices (IP Phones, Alcatel 4980 IP Telephony, GDx, GAx, 4645 voice mail, INTIPx, H323
equipment and H323 Gateways); 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 in network is available with H323 terminals or H323 Gateway if all nodes are in Release 7.0 or
higher.
NGP boards support only the "Direct RTP in network" mode.
In Release 9.1, the Direct RTP mode parameter in "IP / IP Parameters" has been suppressed and the
Direct RTP mode in network activated in all cases : the non Direct RTP mode in network is no more
possible. This rule applies for both new systems and systems upgraded from older releases to release
9.1. The other nodes of the ABC-F network must be managed accordingly. All the Alcatel-Lucent
devices used must support this mode.
 Multi-node transit without compression/decompression like in OmniPCX 4400: this optimization is not
implemented in OmniPCX Enterprise; in place, direct RTP in network is provided.
 It is not possible to create several IP trunk groups for a GDx/GAx/INTIPx board => use the VPN Call
Limitation feature to limit the number of calls per direction.
 For a GDx/GAx/INTIPx, 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.

TC2306 ed.03
 As of Release 9.1, the boolean H323 signaling for inter-node links has been removed:
only the H323 mode is possible. The other nodes of the ABC-F network must be managed accordingly.
NGP boards only support this mode.
 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.
QoS tickets are provided by GD/GA/INTIP boards, IP Phone V2, IP Touch (in NOE mode), My Phone and 4645
voice mail.
 Fax over IP.
The rate is limited to 9600 bit/s in Fax Relay mode with common hardware and Crystal Hardware.
The rate remains at 9600 bit/s for the inter Media-Gateway T38 fax mode, introduced in R9.0.
Fax T38 interworking with OmniAccess 512 (VSA Interface) is not available.
Fax V34 is supported.
From Release 7.0, the Analog type parameter used to create an analog equipment of "Fax" or "Modem"
type in order to initialize the connection in transparent mode from the start of the communication , concern
only the modem:
Users / Analog type + No specific management or Fax
If the equipment is a fax: Switch-over to transparency after detection of 2100 Hz by DSP.
If the equipment is a modem: Switch-over to transparency after detection of 2100 Hz par le DSP,
If there is no carrier, no switch-over to transparency.
If the equipment is a set: No switch-over to transparency except if the DSP detects the 2100 Hz.
If Fax behind GD or INTIP are used, verify and manage if necessary value 7 in "V21 Jitter Buffer Length"
under "IP/Fax parameters": all GDs and INTIP must be rebooted to validate this value
When the Inter-Media Gateway T38 fax, introduced in Release 9.0, is used it must be activated on the various
nodes connected by VoIP logical link. A manual reset of GD/INTIP boards is imperative to take into account
the new mode. This mode has also been ported in Release 8.0.1 since patch G1.503.35. NGP boards only
support T38 fax mode between Media Gateways.
On a secured system with Thales devices (IP Touch Security) and using the inter Media-Gateway T38 fax
mode, the Local T38 port number parameter must be set to RTP port Number + 0.
 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.
 Audiocodes MP-112.
T38-SIP: From R7.1, the default value of the Minimal authentication method parameter is set to the
DIGEST (with a password).
T38 Fax over SIP operation is supported with the MP-112 equipment. The transfer in TCP mode is not allowed,
the UDP one must be used.

TC2306 ed.03
 Audiocodes MP-118
An analog set (respectively a fax) plugged on a MP-118 must correspond to a SIP set with type "SIP
extension" (respectively "SIP Device" / "External set") on CS side.
 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).
 Internal DHCP Server
Verify that the range of the IP addresses assigned is sufficient for the number of clients. If the number is
lower than the numbers of clients, it would duplicate IP addresses with Windows or MAC clients for example,
the server is not protected against the reactivation of IP address by these clients.
 Internal DHCP server is restricted to 5 000 IP Touch.
 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.
 Jitter buffer.
Up to Release 9.0, the jitter buffer was managed by default in static mode with a buffer depth of 100 ms.
From Release 9.1, the default mode is changed with the use of the dynamic mode together with a buffer
depth of 300 ms. These new settings will help to avoid any packets accumulation on one side after a jitter
burst. They will also allow storing more packets and then accept a more important jitter.
21.6 ABC-F IP TRUNK GROUP

When creating the ABC-F IP trunk group, the Homogeneous network for direct RTP parameter must
be set to Yes if each node of sub-network located behind the ABC-F IP trunk group is in R9.0 or higher. If one
of the nodes of remote sub-network is in version less than R9.0, the parameter must be set to No.
If the sub-network, located behind the ABC-F IP trunk group, has a QSIG trunk group, the Homogeneous
network for direct RTP parameter must be set to No.
It is not possible to have both on a same node a ABC-F (IP or not) trunk group and a DPNSS trunk group.
The ongoing communications on an ABC-F IP trunk group are not maintained in case of Call Server switch-
over. This limitation is removed as of Release 9.1.
There is no encryption of the voice and signaling flows between two sub-networks linked by an ABC-F IP trunk
group.
This trunk group doesn't support the transparent fax/modem and cannot be distributed.
Only one ABC-F IP trunk group between two OmniPCX Enterprises. No mixity ABC-F TDM / ABC-F IP between
two sub-networks.

TC2306 ed.03
21.7 SIP SETS
all standard SIP sets must be declared with the SIP Extension type. Standard SIP sets are no longer
supported with the former "SIP Device" mode (formerly called "External set"). Only items other than standard
sets (Nokia sets in Dual mode, Alcatel 4135 conference module, fax, video, etc.) should remain with the
former "SIP Device" mode.
Set 8088 used for huddle room does NOT follow this rule and MUST be managed as "SIP Device".
The “sip extension” mode (Native SIP Call Controller, also named SEPLOS - SIP End Point Level Of Service in
some technical documents) allows to increase strongly the level of service on a SIP set, compared with the SIP
standard (use of many OmniPCX Enterprise prefixes, etc.). Only the sets mentioned in the SEPLOS "white list"
(refer to the technical documentation TC1108 Native SIP Call Controller: White List) will be supported in
complete SEPLOS mode. This "white list" is likely to be regularly expanded further interoperability tests
performed in the AAPP framework. The sets not listed in the "white list" continue to be supported with the
basic level of service offered by the SIP standard (functioning equivalent to R8.0).
When migrating a system with "SIP Device" / "External set" from an older release, the system moves these
sets into the new mode (SIP extension) automatically.
Warning It is mandatory to declare Nokia sets, used in Dual mode with OXE, as well as 4135 IP Conference Phones,
with type "SIP device".
Procedure to follow:
Export the SIP entities which are not standard SIP sets (Nokia sets in Dual mode, 4135 IP Conference Phones,
fax, video, ...) by OmniVista 4760(i) by using .prg as export format.
Remove these entities then migrate to R9.0.
Import again the items which have been previously exported: standard SIP sets are in "SIP Extension" and the
other SIP entities in "SIP Device".
Information to manage SIP sets in SEPLOS mode with SIP Device Management is available in OmniVista 4760
R5.0 documentation. See also the technical communications TC1106 Thomson ST20xx SIP sets deployment
and TC1255 4008 / 4018 SIP set deployment with OmniPCX Enterprise.
 Direct RTP Switching in network is mandatory when SIP phones are configured.
 SIP-Phones are supported in:
stand-alone,
network configurations.
 From R9.0, Business SIP sets in "SIP Extension" are mandatory multiline and room sets monoline.
These modes are those available by default and must not be modified for any reason.
 Refer to the R11.1 Feature List for the list of telephonic features available on SIP sets.
The framing on these sets must be set to 20 ms in G711 and G729 and to 30 ms in G723.
Refer to technical communication TC1106 Thomson ST20xx SIP sets deployment for more information
regarding the deployment of these sets in an enterprise network (VLAN, spatial redundancy, ...).
 Support of 4008/4018 sets in SIP mode.

TC2306 ed.03
Refer to technical communication TC1255 4008 / 4018 SIP set deployment with OmniPCX Enterprise for
detailed information regarding the deployment of these sets in an enterprise network.
 SIP Session Timer.
This feature can be made of two alternative ways: via the Re-Invite method (available in previous releases)
and via the Update method (available from R9.0). Depending of the SIP set possibilities, this mode may also
be set up within the set. If the CS is managed in "Update" mode, it is able to switch back to "Re-Invite" mode
if the set imposes this mode.
For OmniTouch Unified Communication, this new method requires R5.1. The OmniTouch Unified
Communication will use the mode set up on the CS.
 SIP Keep Alive mechanism is available in Release 9.1 only for SIP sets declared in SEPLOS mode and
provided that they support OPTION messages.
 Reason header is also specific to SIP sets declared in SEPLOS mode. This information is intended for
network administrators and Business Partners (information provided in English only in the SIP trace).
In the current version, 4008/4018EE sets in SIP mode display this information, so end-users will see
some English messages despite the set language may be managed in another language.
21.8 OTHER SETS

21.8.1 IP Phone V1 – V1S
The IP Phone V1 (4098 RE) sets are no more supported
The IP Phone V1 set does not work in Direct RTP.
Those sets will not work in ipv6 configurations (constant reboot).
21.8.2 IP Phone V2 (e-Reflexe)

 The VoIP Technical Characteristics of the IP-Phones are available on Business Portal.
 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.
Those sets will not work in ipv6 configurations (constant reboot).
21.8.3 Alcatel series 8 & 9 sets

 The Alcatel series 8 & 9 sets cannot be used as attendant sets.

TC2306 ed.03
As of Release 9.1, only 4068 set (Fast Ethernet or Extended Edition) can be used as attendant.
 Alcatel series 8 & 9 sets can be used as CCD sets from Release 7.0.
 Alcatel series 9 sets used as CCD sets require eUA32 boards (3BA 23266).
 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.
 Only the 4028-4038-4068 sets can access to XML applications.
 The 4018-4028 set cannot access to OmniTouch UC R4.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.
 Add-on modules AP (3GV 27014) and S0 (3GV 27016) are compatible with UA Reflexe and 9 series
sets.
 Add-on module External ringing interface (3GV28050AA) is compatible with UA Reflexe and 8 & 9
series sets.
 Add-on module V24 / CTI (3GV 27015) is compatible with UA Reflexe sets and cannot be declared
behind 9 series sets.
 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.
 "SIP Survivability" feature, released for 4008/4018/4028/4038/4068 Extended Edition sets.
Once switched in SIP mode, the sets continue to use the NOE data file.
The concerned binaries are noesip4018 (resp. noesip40x8) and dat4018 (resp. dat40x8) for 4008/4018
Extended Edition (resp. 4028/4038/4068 Extended Edition) sets.
 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 FOR OLD VERSIONS
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, 6.2 or R7.0.
When migrating from R6.0 to R7.0, 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.
Login swinst

TC2306 ed.03
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 “
 Several 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 the 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-Lucent 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.
In Release 9.0, during the IP Touch initialization, the CS checks the MAC address of the set, returned at the
START_NOE TFTP request, and the MAC address of the set, returned during the signaling link initialization of
the set. A new field was added in IP-link protocol in the message that returns the IP address of the set. If this
new field is not present in the signaling message the initialization of the set is still performed, but the incident
441 is generated. This mechanism is not implemented on the MIPTs and IP SoftPhones.

TC2306 ed.03
 As of RELEASE 10.1.1, two new parameters control the reboot of Alcatel-Lucent IPTouch 8 series
phone Extended Edition sets when the connection with CS or PCS is lost. Those features named Keep
Voice Flow and Transparent Reboot are available on IP Touch 8 series Extended Edition only.
 As of R10.0, Alcatel-Lucent IP Touch 4028/4038/4068 phone Extended Edition sets can operate with
NOE-SIP encapsulation. When this is the case, they are called NOE-SIP sets.
In this configuration, NOE messages are encapsulated in SIP Options messages. A NOE-SIP set offers the
same services and interface as a standard Alcatel-Lucent IP Touch 4028/4038/4068 phone Extended Edition
set. A keep alive dialogue is established to check the presence of the remote party.
On client network gateways and firewalls, messages from NOE-SIP sets are processed as SIP messages, using
the same ports as standard SIP messages. The dynamic opening of firewall ports is available.
All Alcatel-Lucent IP Touch 4028/4038/4068 Extended Edition sets of a node must operate in the same
configuration (standard NOE or NOE-SIP encapsulation).
21.8.4 Alcatel-Lucent 8082 My IC Phone

 As of R11.0, Alcatel-Lucent 8082 My IC Phone is a physical phone set that operates with the OmniPCX
Enterprise for usage named OpenTouch™ Connection for 8082 My IC Phone. That is to say Alcatel-
Lucent 8082 My IC Phone sets relying on the NOE protocol and presenting all the typical features of
OmniPCX Enterprise business as an Alcatel-Lucent IP Touch 4068 set.
 OT Connection for 8082 My IC Phone is also compatible with R10.1.1, provided the OmniPCX
Enterprise version is at least J2.603.26
OT Connection for 8082 emulates IP Touch 4068 and has same level of service except:
• Encryption
• NOE encapsulation in SIP
• Survivability in SIP
• Add on modules
• IME
• Guest position for hospitality market
21.8.5 MIPT 300 & 600 handsets
Warning VoWLAN R1.x offer is no more supported from Release 7.0 and must be replaced by VoWLAN Release 3.0
offer from OmniPCX Enterprise Release 8.0.
For more information, refer to the technical communications TC0940 Technical Release Note for VoWLAN
Release 3.0 offer and TC1195 Technical Release Note of VoWLAN 4.1 for OmniPCX Enterprise.
 MIPT handsets have same level of feature than an IP Touch set (call by name, tandem, Boss /
secretary, notification messages, Hotel and Hospital sets, etc.).
 MIPT handsets are not supported in Contact Center, attendant, etc.
 MIPT handsets support codecs G711 and G729A.
 MIPT handsets supports the WEP, WPA and WPA2-PSK
 As of Release 8.0, VoWLAN offer operates around Alcatel-Lucent IP Touch 310&610TM (MIPT
310&610) handsets, integrating the NOE protocol (New Office Environment) and compatible with or
without Mobile IP Touch SVP Server (SVP Server). The mode without SVP server is only available on

TC2306 ed.03
the OmniAccess WirelessLAN infrastructure. If there is a mixing of MIPT 300&600 and MIPT 310&610
handsets, a SVP Server must be used.
21.8.6 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.
 DECT Campus.
The DECT Campus feature is not supported with Call Server or Appliance Server driving common hardware or
Crystal Media Gateway.
Due to a bad synchronization of INTOFS board, the DECT Campus is not operational. DECT(s) remain attached
to their preferential node. Thus in limit of coverage, there is no handover towards the node of better
coverage. In this case, reset INTOFS boards of the PCX after restarting the PCX
 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).
 As of Release 8.0, XL configuration is only supported on Appliance Server and does not allow an
operation of Campus DECT.
 As of Release 8.0, DECT is available for USA. PWT and DECT cannot operate on the same installation.
 INTIP3B board carries out a full DTM function for its own ACT. This means all DECT synchronizations
are broadcasted over the whole remote crystal including sub-level. In such case, there is no more
need to use an additional DECT synchro board in the shelf. It is forbidden in a remote ACT to perform
this DTM function on both INTIP3B and DECT board. INTIP3B switchover preserves the DECT
synchros.
21.8.7 IP DECT system

Generalities:
 In case of incoherency mobiles management between OXE and DAP controller the DAP reboot :
workaround is to use authentication between DAP and OXE (Will be fixed in a maintenance version)
 Audio clack in com in G729 : workaround is to disable VAD (analysis on going for a fix with VAD)
 Call cut after 50s when DAP managing the handset is disconnected: when during a call the communication
between the visiting DAP (handles DECT communication with handset) and the registration DAP (handles
the communication with the SIP server) is lost for more than 50 seconds, both DAPs will clear the call.
4080 DECT IP Access Point:

 No Static IP address management (only in DHCP mode)
 No LLDP Poe negociation
 No AVA and no LLDP-MED VLAN ID acquisition
 No multi-PARI support
 No TFTP server redundancy

TC2306 ed.03
 No G723
 No telnet
 No ARP spoofing nor DoS protection
 NAT is not supported
 No RJ45 Cat 7 support
DAP Controller/Manager installer:

 No redundancy of the DAP Manager
 DAP manager and OmniVista 4760/8770 cannot be hosted on the same physical server
 DAP manager cannot be virtualized
ALU DECT IP offer:

 TDM-DECT (IBS or RBS) and IP-DECT APs cannot be mixed on the same OXE system
 MR100/200 handsets are not supported
 No end to end encryption (No encryption over the lan)
 ALU feature called “DECT over campus” is not supported
 Notification server integration enhancement on 400 DECT handsets is not supported (AAPP with newVoice
notification server).
21.8.8 UA Extender 4051/4052

The use of UA Extender 4051/4052 is not available through IP.
21.8.9 NOE3G (premium ip phones)

In L2 TR version (patch .20.e) the firmware is R100 which is NOT compatible with ipv6.
Patches after TR (.21 and beyond) will contain the R200 firmware which include the ipv4/v6 dual stack. For
encryption firmware will still be R100 but named R200. Encryption will come later.
21.8.10 NOE3G EE
It is possible that some sets will not reboot after upgrading the firmware (for that patch all new NOE 3G EE
sets are in 5.00.12).
Use the command “downstat i” to check who is not updated & rebooted.
Use the command “downstat i r HH:MM” to program a reboot of those sets.
Use the command “tftp_check -s -t [time]” to start the download (incident thrown : 391 : “Update the binaries
of IP set by tftp server”.
Technical communication to come (“TC2308 : technical release note for 8028s, ... Premium Deskphones”)
Known restrictions :
 Bluetooth accessories: only Sennheiser MB Pro 2 UC works smoothly with our phones (Plantronics
Voyager Legend loses audio after a few minutes and should *not* be used)
 Bluetooth handset is currently limited to narrow band
 IME is disabled for Stroke (Hong Kong) and Jamo (Korea)
 USB accessories not available

TC2306 ed.03
 Group listening deactivated
 External IP recording ( internal recording is OK )
 VPN remote worker
21.8.11 OTC Android Smartphone

CROXE-3530 - OTC Android Smartphone // OS Android 7 Update issue
Since Android OS Nougat Update some ports historycally used by the System are now in Conflict with OS
Nougat reserved ones.
Default port for signaling is 32512, this port is in the range of reserved port in Android 7 (32100 to 32599).
To allow android 7 devices, you must change the configuration of default port (IP-> TSC/IP Parameters ->
UDP port). Must also take this change is the firewall configuration
21.9 IP TOUCH SECURITY FEATURE

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-Lucent 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
Secured GD binaries likely to encrypt the signaling directly
Secured GD3 / GA3 / INTIP3 binaries likely to encrypt both voice and signaling directly
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.
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.

TC2306 ed.03
To customize GD3 / INTIP3B board with Soft-MSM feature (PSKmg), the version 1.2.01 of Security Center has
to be used. GA3 and INTIP3A boards don’t have to be customized and must be configured with Voice MSM
type instead of SoftMSM type (to be used only for GD3 and INTIP3B).
Only boards with SoftMSM type (ie GD3, INTIP3B) are taken into account by software lock 348.
Before activating Soft-MSM feature on a NGP board, it is mandatory for the board to perform an initial boot
without encryption (MG type selected in "Addresses to protect" MAO object).
21.10 SIP TLS FOR EXTERNAL GATEWAY

Before OmniPCX Enterprise Release 10.0, only IPsec/SRTP protocols were supported to protect UA/NOE
communications. The IPsec protocol protects UA/NOE signaling and the SRTP protocol protects the sent and
received voice flows.
As of OmniPCX Enterprise Release 10.0, SIP TLS/SRTP protocols are supported to secure SIP Trunks
configured on the OXE to a Carrier or Service Provider network (Public SIP Trunking in ISDN mode). The TLS
protocol protects SIP signaling and the SRTP protocol protects voice flows.
Depending on Carrier/Service Provider capabilities, voice media can also be encrypted using SRTP. Each Public
SIP Trunk can be configured at OXE level with SIP TLS&RTP or SIP TLS&SRTP. The voice media can be end-
to-end encrypted (using SRTP) from the IP Touch set in the customer’s network up to the Carrier’s gateway.
Restrictions whatever the system configuration:
 The minimum OXE Release is 10.0 (J1.410.34.c).
 SSM boxes model and MSM boxes model are not compatible with the SIP TLS feature. These boxes
must be replaced by new Server Security Modules SSM-RM and Media Security Modules MSM-RM in
front of PCS.
 SIP TLS with SIP devices or SIP extensions is not supported.
 As of R10.0, for duplicated Com Server configuration, spatial redundancy is mandatory (2 different
Main IP addresses for each CPU).
 As of R10.1.1, the feature SIP TLS can operate with OmniPCX Enterprise local redundancy
(using role addressing)
As of Release 10.0, IPsec/SRTP and SIP TLS/SRTP protocols can be used simultaneously in the different
configurations detailed in PCS Form.
21.11 APPLICATIONS
21.11.1 OmniVista 4760 & 4760i
Omnivista 4760 is phase-out. Last version available is 5.2.03.00.c where most of the remaining existing issues
are fixed.
4760i : This application is removed from the system and replaced by the Web Based Management tool
described further in the document.
21.11.2 SIP Device Management Server

Application is embedded in 8770.
Always check in the Business Portal for new sip sets binaries (8002/8012/8082 hotel/8001, 8088 Huddle room
mode)

TC2306 ed.03
21.11.3 AAS (Audio Station)
Warning On secured sites (by ssh) the copy of the guides is not working anymore in R12.0 Use a manual copy by
using an ssh client program.
21.11.4 External Voice Mail

As of Release 10.0, the new parameter Subscription on registration in mgr-> Application ->External Voice Mail
object is added.
It must be set to False (Default value) when using external application such as UC R6, ACS, AVST, …
In case of OXE set using Local Storage Mail box (on OpenTouch Solution), this parameter must be set to True
to allow notification on the OXE set when he receives a new voice message. When OXE receives the "Register"
from Local Storage Voice Mail, a "Subscribe" is sent for the user to receive notifications.
21.12 Security
As of R11.0, new options in A4645 allow security enhancement.
Nothing new in R12.0
Make sure that those security improvements are done to avoid hacking issues.
The features described below come from the previous release : R11.2, put as reminder …
21.12.1 Voice mail 4645: access blocking after bad password attempts
As of R11.0, Access to the A4645 voice mail can be blocked after a number of specified failed attempts (wrong
password entries)
If access to the voice mail has been blocked, the duration of this access lock can be managed in:
Applications > Voice Mail > Descend hierarchy > 4645 VM Classes of Services > Mailbox lock duration
• 0: voice mail access remains possible (lock deactivated)
• Any value between 1 and 32000: voice mail access is blocked for the same number of minutes
• -1: voice mail access is blocked and can only be unlocked via new options in the Eva_tool command
As of R11.0, external calls to the voice mailbox can be forbidden if using the default password.
External access with default password can be managed in:
Applications > Voice Mail > Descend hierarchy > 4645 VM Global Parameters > Ext access with default
password
• Yes: users connecting from outside the system can access their voice mail with the default password
• No: users connecting from outside the system cannot access their voice mail with the default
password. They must first change their password.
As of R11.0, the access to any mailbox by pressing the # key (using the voice mail system) for users
connecting from outside the system can be managed in:
Applications > Voice Mail > Descend hierarchy > 4645 VM Global Parameters > Mailbox number input from
external

TC2306 ed.03
 Yes: users connecting from outside the system can access their voice mailbox. They can also
access someone else's mailbox, by pressing the # key
 No: users connecting from outside the system cannot access the voice mail system
21.12.2 Voice mail 4645 : minimum user password length option

As of R11.0, the user mail box password minimum length can be increased in system administration.
The password minimum length can be managed in :
Applications > Voice Mail > Descend hierarchy > 4645 VM Classes of Services > User Password minimum
Length
• Enter the minimum length for users password: This value must be above between 4 and 8
21.13 CLIP
 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.
The feature is released only for 6 countries (France, 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-Lucent 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-Lucent Business Partner
Program to carry out such validation of their product.
 CLIP on SLI and MIX.
As of Release 8.0, SLI and MIX boards on common hardware supports the CLIP FSK ETSI or Bellcore.
 Some telephones only displayed the calling number and not the calling name.
 Alcatel-Lucent 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-Lucent Business Partner Program to carry out such validation of their product.
 CLIP Bellcore on NDDI2.
CLIP on NDDI2 is available for all markets from Release 6.1.
 CLIP Bellcore on APA.
CLIP on APA line (CLIDSP daughter board - 3EH 73034 AB) 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.

TC2306 ed.03
21.14 DIRECTORY
External LDAP Server :
LDAP overflow is available on all sets.
Alcatel-Lucent Premium Deskphones, myIC phone Standart & 40x8/40x9 sets as well as Reflexe/eReflexe have
an "Overflow" softkey.
During a phone book search with LDAP overflow setup, the PCX searches its local phone book the
corresponding entries to the search.
- If the search in the phone book succeeds, only the sets having a "Overflow" softkey can use the
softkey to complete their search in the external LDAP server.
- If the search in the phone book fails, the search overflows towards external LDAP server whatever
the type of set.
The search in the external phone book is a "Begin with" search (the similar entries are not displayed).
The result displays the directory number or if it misses the mobile number (both information are not
displayed). If no number is available, the entry is ignored even it corresponds to the search.
client_ldap was no more available in R8.0.
- In Release 8.0.1, a new client_ldap tool is available. It performs an LDAP search on telnet access.
You don't need anymore to give LDAP parameters, such tool use actual OmniPCX Enterprise
configuration and requires only to specify the Entity Id.
(611)xa006011> client_ldap
Entity of set
54
Entity = 54
0 => Exit
1 => Search by name
2 => Search by initial
3 => Search by name and first name
1
Request Name ...
paris
Request 5 paris
Result reply_count 3
Result 0 PARIS STEPHANE 61234
Result 1 PARIS DELPHINE 72123
Result 2 PARIS LAURENT 72345
(611)xa006011>
Troubleshooting
You can trace the overflow to external ldap server by phone book process
For the UTF-8 phone book
On OmniPCX Enterprise console launch:
utf8_pbm_tuner output-tty=`tty`
utf8_tuner trace-level=all
For non UTF-8 phone book

TC2306 ed.03
On OmniPCX Enterprise console launch:
pbm_tuner output-tty=`tty`
tuner trace-level=all
Search in UTF-8 phone book.

This feature is only available for Premium Deskphones, myIC phone Standart & 40x8/40x9.
Note If the UTF-8 field is completed in user data with the same information as Latin name, the search of name in
the directory, using "Call by name", will give a double result ( Latin name + UTF-8 name).
 From R9.1 (I1.605.31), search in internal Phone Book (Call By Name search ) with several results for
internal numbers and abbreviated numbers display first internal number before Abbreviated number in
case of dual entries for a same Name.
21.15 BOARDS
 MIX board.
This board is not supported in a Rack 3U in central area.
 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
- 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.
 DPT1-2 board.
NPRAE and DPT1-2 boards cannot be used together on the same PCX.
21.16 MISCELLANEOUS
 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.
 MIPT.
No music played during a music on hold.
 Customized ringing melody.
The customized ringing file is limited to 16 melodies.
 T0 interface on Media Gateway.

TC2306 ed.03
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:
32 000 on Appliance Server
10 000 on CPU7
1000 on other CPUs
 Number of automatic call back requests per node
As of Release 8.0, the number of automatic call back requests passes to 2000 by node instead of 200.
 Number of T0.
Maximum number of T0 is limited to 1000.
 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.
The 4645 supports only DTMF sent in the signaling.
 Voice Guides.
GD/GA board supports maximum 4 languages for voice guides (including music on hold).
As of Release 8.0, GD/GA allows the playing of 40 min 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,

TC2306 ed.03
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. An evolution of the box for Common Hardware is being
developed.
EAU (United Arabian Emirates) is available.
 A-Law/-Law.
The A-Law / –Law configuration is valid for the whole system.
DPT1-2 board does not allow any more the A-Law / µ-Law conversion.
 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.
 eRMA.
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 GDx (does not in case of
access work through an ABC-F link).
eRMA feature is not available if the concerned Media Gateway encrypts directly the signaling (MGsec).
 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, 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:

TC2306 ed.03
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.
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.
 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.
 ppp.
ppp connection w/o RMA does not operate with each current Linux versions. The connection is active but
telnet, config, synchro fail.
 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.
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.
From Release 8.0.1, private to public overflow of a routed call by RSI is monitored by RSI.
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.
 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).
Warning 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).

TC2306 ed.03
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.
22 TECHNICAL SUPPORT
Technical support will be provided to certified ACSE or ACFE engineers. The engineer must provide the valid
SMS/SES or SPS contract id (Support processes available on the Business Portal under the heading Customer
Support > Technical Support > Support processes).
Before contacting Alcatel's Business Partner Support Center (ABPSC), make sure that you have consulted:
 The Troubleshooting Guides (Diagnostics support guides) where they exist and perform the
actions suggested for your system problem (available on the Business Portal under the heading
Customer Support > Technical Support > Technical Documentation Library.
 The Technical Knowledge Center tool to perform a search, get a result, print the article or send it
by email. This is the Alcatel-Lucent Enterprise Customer Care knowledge tool for Alcatel-Lucent
Communications and Network solutions (available on the Business Portal under the heading
Customer Support > Technical Support > Technical Knowledge Center ): Technical Knowledge
Center
23 Interoperability with Third-Party applications

In case of interoperability with Third-Party applications, it is highly recommended to verify the interoperability
either by contacting the Third-Party supplier or by checking the existence of a valid “InterWorking Report” on
the Business Portal.
Technical support will be provided only in case of a valid InterWorking Report and in the scope of the features
which have been certified. That scope is defined by the InterWorking report via the tests cases which have
been performed, the conditions and the perimeter of the testing as well as the observed limitations. All this
being documented in the IWR. The certification does not verify the functional achievement of the AAPP
member’s application as well as it does not cover load capacity checks, race conditions and generally speaking
any real customer's site conditions.
Any possible issue will require first to be addressed and analyzed by the AAPP member before being escalated
to Alcatel-Lucent.

TC2306 ed.03
For any request outside the scope of this IWR, Alcatel-Lucent offers the “On Demand Diagnostic” service
where assistance will be provided against payment.

TC2306 ed.03
Follow us on Facebook and Twitter
Connect with us on Facebook and Twitter for the latest:
 Software releases
 Technical communications
 AAPP InterWorking reports
 Newsletters
…and much more!
twitter.com/ALUE_Care
facebook.com/ALECustomerCare
Submitting a Service Request

Please connect to our eService Request application.
Before submitting a Service Request, please be sure:

 The application has been certified via the AAPP if a third party application is involved.
 You have read the release notes that list new features, system requirements, restrictions, and more,
and are available in the Technical Documentation Library.
 You have read through the related troubleshooting guides and technical bulletins available in the
Technical Documentation Library.
 You have read through the self-service information on commonly asked support questions and known
issues and workarounds available in the Technical Knowledge Center.
- END OF DOCUMENT -

TC2306 ed.03

Installation Procedure OmniPCX Enterprise R12.0 Version M1.403.12.G

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Installation Procedure OmniPCX Enterprise R12.0 Version M1.403.12.G

Încărcat de

Drepturi de autor:

Formate disponibile

Release Note OmniPCX Enterprise

TC2306 ed.03 Release 12.0

Release Note & Installation procedure for

Edition 01: February 3, 2017 Creation of the document

OmniPCX Enterprise - Release 12.0

OmniPCX Enterprise - Release 12.0

OmniPCX Enterprise - Release 12.0

OmniPCX Enterprise - Release 12.0

OmniPCX Enterprise - Release 12.0

This document and its appendices describe:

Warning It is important to read carefully the following chapters :

TC0778 Migration OmniPCX 4400 to OmniPCX Enterprise

OmniPCX Enterprise - Release 12.0

Offer documents (See chap. 8 for direct links) :

OmniPCX Enterprise - Release 12.0

DB Compatible with following static

M1.403.12.G M1.403.5 M1.403.11.a

The program of certification is available on the Business Portal

4.1 New hardware

 New Appliance servers :

OmniPCX Enterprise - Release 12.0

4.2 New features/ interoperability

4.2.4 Increasing provisioning level/ product limits

OmniPCX Enterprise - Release 12.0

4.2.9 SIP Enhancement

4.3 Features under PCS

4.4 Features availability in progress (for MD1/2/3 patches)

OmniPCX Enterprise - Release 12.0

5 CONTENT OF THE SOFTWARE PACKAGE

 OmniPCX Enterprise R12.0 software M1.403.12.G containing :

DVD R12.0 REFERENCES :

Reference of DVDs or CDs releated to R12.0 :

Reference Reference Misc

OmniPCX Enterprise - Release 12.0

OPENTOUCH 2.2.1 Boot Suse ES 12 3BH12007AGAD bootdvd.12.1.010.000.x86_64.iso

OXE Software Server To be released for MD1 patch

OmniPCX Enterprise - Release 12.0

OmniPCX Enterprise - Release 12.0

OmniPCX Enterprise - Release 12.0

SM modules (Thales) 4.0.14.a : 4.0.14.a :

OmniPCX Enterprise - Release 12.0

6.1 Compatibilities/ Product Limits

6.2 Hardware : phased-out boards

6.3 Conditions for installation in ABC network

OmniPCX Enterprise - Release 12.0

ACT migration 4300, 2600, 4600 or Manage the equipment in Yes No

ACD-V1 ACD-V1 CCD or OTCCSE Yes TC0487 (CCD)

OmniPCX Enterprise - Release 12.0

6.5 Applications and functionalities dependent on CPUs and hardware platform

OmniPCX Enterprise - Release 12.0

(2) Replacement is carried out by Actis.

(3) Manual modifications are required.

OmniPCX Enterprise - Release 12.0

6.6 VoIP network conformity check

6.7 Firmware upgrade

6.8 Recommendations about security

Information about DECT licenses in case of migration.

OmniPCX Enterprise - Release 12.0

7 COMPATIBILITIES/ PRODUCT LIMITS/ FEATURE LIST

Check all compatibilities (applications, hardware etc.) in the following document:

Limits for features, software, hardware etc. are located at :

Feature list abstract is located at :

Feature list is located at :

OmniPCX Enterprise - Release 12.0