TC2473 Release Note & Installation procedure for OmniPCX ...

Legal notice:

www.al-enterprise.com The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other trademarks

used by affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other trademarks are the

property of their respective owners. The information presented is subject to change without notice. Neither ALE Holding nor any of its

affiliates assumes any responsibility for inaccuracies contained herein. © Copyright 2020 ALE International, ALE USA Inc. All rights reserved

in all countries.

Release Note OmniPCX Enterprise

TC2473 ed.20 Release 12.2

Release Note & Installation procedure for

OmniPCX Enterprise R12.2 Released version

M3.402.34 (MD12 patch)

This is the MD12 patch technical release of OmniPCX Enterprise release 12.2 with the version M3.402.34. Technical modes

for migration, new features, registered restrictions and controlled features are described in that document: “Release note &

installation procedure for version M3.402.34”.

Revision History

Edition 1: July 12, 2018 creation of the document

Edition 2: July 23, 2018 GAS information chap 18.2.5 adding misc info + upgrade case Edition 3: October 4, 2018 update document to released patch “.13.M” including release of feature “dect ip xBS”.

Update of chapter 15.2.6.1 about OMS & OV64. Update of dedicated chapters concerning dect/mobility + restrictions. Update on chap. 15.2.1.22: Rainbow Web RTC Gateway

Edition 4: October 9, 2018 update of chapter 16 (OXE Components). Updates on 18.2 (G.A.S.: precision on upgrading a server) & 18.3 virtualization

Edition 5: October 10, 2018 update to MD1 patch. Addition of new features released and their description, misc modifications …

Edition 6: October 23, 2018 Chapt. 15.2.16.1 + chapt. 18.1.1 (feature dtmf inband support): adding management, info,

restrictions. Chapt.16 update of oxe components. Edition 7: November 23, 2018 Chapt. 5.7.1 System voice guides: version 5.4 does not exist

Edition 8: January 24, 2019 update to MD2 patch. All corresponding information (dect features, 4059 update…) Edition 9: January 31, 2019 update on dect ip xBS status (See sections 3.2.8, 3.3 and 15.2.3) + restrictions chap.

Edition 10: February 22,2019 update to MD3 Edition 11: March 04,2019 chapter 3.2.6 refer to chapter 14.3.1

Edition 12: April 19,2019 update to MD4 Edition 13: June 13,2019 update to MD5

Edition 14: August 20,2019 update to MD6

Edition 15: September 27,2019 update to MD7 Edition 16: December 06,2019 update to MD8

Edition 17: January 2020 update to MD9 Edition 18: March 2020 update to MD10

Edition 19: June 2020 Update to MD11

Edition 20: July 2020 Update to MD12

https://www.al-enterprise.com/?utm_source=digital-asset&utm_medium=pdf&utm_campaign=doc-link

https://www.al-enterprise.com/en/legal/trademarks-copyright?utm_source=digital-asset&utm_medium=pdf&utm_campaign=doc-link

OmniPCX Enterprise - Release 12.2

Release Note & Installation procedure for OmniPCX Enterprise R12.2 Released version

M3.402.34 (MD12 patch) TC2473 ed.20 Copyright © ALE International 2020 page 2/197

Table of Contents

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

2 DOCUMENTS .......................................................................................................................................... 9

3 INTRODUCTION TO RELEASE 12.2 ........................................................................................................ 11

3.1 New hardware ................................................................................................................................ 12

3.2 List of new features since MD2/ interoperability ................................................................................ 12

3.2.1 Call Handling features ............................................................................................................... 12

3.2.2 CCD ......................................................................................................................................... 12

3.2.3 Encryption ................................................................................................................................ 13

3.2.4 Increasing provisioning level/ product limits ............................................................................... 13

3.2.5 Infra ........................................................................................................................................ 13

3.2.6 Interworking/ Interoperability tested .......................................................................................... 13

3.2.7 Maintenance ............................................................................................................................. 13 3.2.8 Mobility .................................................................................................................................... 13

3.2.9 O2G ......................................................................................................................................... 14

3.2.10 Rainbow ................................................................................................................................. 14

3.2.11 Security .................................................................................................................................. 14

3.2.12 Terminals ............................................................................................................................... 14

3.2.13 Virtualization........................................................................................................................... 14 3.3 Features under PCS ......................................................................................................................... 15

3.4 Features availability in progress (MDx patches) ................................................................................. 15

4 SOFTWARE PACKAGE & OTHER COMPONENTS ....................................................................................... 15

5 BEFORE STARTING ............................................................................................................................... 17

5.1 Checks to perform........................................................................................................................... 17

5.2 Getting the software ....................................................................................................................... 20

5.3 ACTIS, eLP & software locks ............................................................................................................ 20

5.4 Before saving the database ............................................................................................................. 21

5.4.1 Rebuilding the database before saving ....................................................................................... 21

5.4.2 Tickets ..................................................................................................................................... 21

5.4.3 From crystal to GAS or vm or common hardware ........................................................................ 21

5.5 Call Server compatibilities ................................................................................................................ 22

5.6 Firmware upgrade ........................................................................................................................... 23 5.7 Voice guides ................................................................................................................................... 23

5.7.1 System voice guides ................................................................................................................. 23

5.7.2 Alcatel 4645 voice guides .......................................................................................................... 23 5.8 4645 .............................................................................................................................................. 25

5.9 Recommendations about security ..................................................................................................... 25

5.10 Translations .................................................................................................................................. 25 5.11 Migrating old versions ................................................................................................................... 27

5.12 Dect ............................................................................................................................................. 27




5.13 New installation ............................................................................................................................ 28

5.14 Updating the PCSs ........................................................................................................................ 29

5.15 OmniPCX 4400 migration to R12.1 ................................................................................................. 29

5.15.1 Use of the hardware key ......................................................................................................... 29

5.15.2 Crystal hardware compatibility with an Appliance Server............................................................ 29

6 INSTALLING THE SOFTWARE ................................................................................................................ 30

6.1 Using dual partitioning .................................................................................................................... 30

6.2 S.O.T. ............................................................................................................................................ 30

6.3 PC Installer ..................................................................................................................................... 30 6.4 Installation on PCS (OXE not secured by ssh) ................................................................................... 30

6.5 Installation on PCS (OXE secured by ssh) ......................................................................................... 30

6.6 Secured systems ............................................................................................................................. 31

6.6.1 Security activated by default during an installation ...................................................................... 31

6.6.2 Installation of a secured system for VoIP encryption ("IP Touch Security" service – Thales solution)

........................................................................................................................................................ 31 6.6.3 Using the Remote Download ..................................................................................................... 32

6.6.4 Reading the hardware key, CPU-id, CCS-ID ................................................................................ 32

6.6.5 Creating a blank database ......................................................................................................... 33

6.6.6 Restoring the database and site tickets ...................................................................................... 33

6.6.7 Restoring Chorus/Linux data ...................................................................................................... 33

7 INSTALLING & CHECKING Actis files ...................................................................................................... 33

7.1 Procedure ....................................................................................................................................... 33

7.2 Checks on physical CPUs ................................................................................................................. 33

7.3 Checks on virtualization ................................................................................................................... 34 7.4 Checks on Cloud Connected system ................................................................................................. 34

8 CLIENT INFORMATION .......................................................................................................................... 34

8.1 New ergonomics and operations ...................................................................................................... 35

8.2 Reminder of changes appeared in Release R12.2 .............................................................................. 35


8.4 Reminder of changes appeared in Release R12.0 .............................................................................. 35 8.5 Reminder of changes appeared in Release R11.2.x ........................................................................... 35


8.7 Reminder of changes appeared in Release R11.0.1 ........................................................................... 36 8.8 Reminder of changes appeared in Release R11.0 .............................................................................. 36

8.9 Reminder of changes appeared in Release 10.1.1 ............................................................................. 36

8.10 Reminder of changes appeared in Release 10.1 .............................................................................. 36

8.11 Reminder of changes appeared in Release 10.0 .............................................................................. 36

8.12 Reminder of changes appeared in Release 9.1 ................................................................................ 36


8.14 Reminder of changes appeared in Release 8.0 and 8.0.1 ................................................................. 37






8.17 Reminder of changes appeared in Release 6.1.1 ............................................................................. 37

8.18 Reminder of changes appeared with R4.2 ....................................................................................... 37



9 SYSTEM MANAGEMENT ......................................................................................................................... 38

9.1 General .......................................................................................................................................... 38

9.2 Special case of IO2N boards (CPU7s2/ CPU8) ................................................................................... 38

9.3 Integrated WebBasedManagement................................................................................................... 38

10 COMPULSORY MINIMUM ADDITIONAL DATABASE MANAGEMENT .......................................................... 39

10.1 Reminders .................................................................................................................................... 39

10.2 Reminder for ABC networked sites migrating from Release < 7.x ..................................................... 39 10.3 Important management if IO2N is present ...................................................................................... 40

10.4 Important management with sets (noe3Gs, 8018) ........................................................................... 41

10.5 Synchronization............................................................................................................................. 41 10.6 Some system parameters to check ................................................................................................. 41

10.6.1 Direct RTP .............................................................................................................................. 41

10.6.2 Frame VoIP (Enhanced quality voice) ....................................................................................... 41

10.6.3 Direct RTP for H323 terminals .................................................................................................. 41

10.6.4 Inter-node protocol H323 ........................................................................................................ 42

11 STARTING UP THE CPU IN ITS ENVIRONMENT ON SITE ....................................................................... 42

11.1 Download of couplers and sets ....................................................................................................... 42

11.2 8088 ANDROID upgrade ................................................................................................................ 43

11.3 SIP sets upgrade ........................................................................................................................... 43 11.4 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 ...................................................................................................................... 43

11.5 Moving from CPU7s1/2 to a CPU8 .................................................................................................. 43

12 CHECKING CORRECT OPERATION ........................................................................................................ 43

13 CHECKS IN A VIRTUALIZED VMWARE INFRASTRUCTURE ...................................................................... 44

14 COMPATIBILITIES/ PRODUCT LIMITS/ FEATURE LIST ........................................................................... 45

14.1 Documents ................................................................................................................................... 45

14.2 Status of the Version (database, Product Reports) .......................................................................... 45

14.3 Interoperability tests status ........................................................................................................... 45

14.3.1 OXE compatibilities in ABC network .......................................................................................... 45

14.3.2 Open Touch ............................................................................................................................ 46

14.3.3 OXO interop. .......................................................................................................................... 46

14.3.4 IP sets compatibility ................................................................................................................ 46

14.3.5 8770 ...................................................................................................................................... 46

14.3.6 Sub-device on older sets ......................................................................................................... 46




14.3.7 Common hardware & Crystal hardware mixed........................................................................... 46

14.4 OEM/External equipment compatibility ........................................................................................... 47

14.4.1 UPS ........................................................................................................................................ 47

14.5 SIP sets, Dect sets, other sets … Latest firmware tested. ................................................................. 47

14.6 Genesys Compact Edition .............................................................................................................. 49

15 NEW FEATURES AND NEW HARDWARE IN RELEASE 12.2 ...................................................................... 49

15.1 New hardware .............................................................................................................................. 49

15.1.1 IBS DECT refresh (8379 IBS renewal) ...................................................................................... 49

15.1.2 New 8088S set ....................................................................................................................... 49 15.1.3 SSD Disks ............................................................................................................................... 49

15.1.4 New dect base station xBS 8378 .............................................................................................. 50

15.2 New features in MD2: description/explanation & management ......................................................... 50

15.2.1 Call Handling features ............................................................................................................. 50

15.2.2 CCD ....................................................................................................................................... 75

15.2.3 Dect ....................................................................................................................................... 77 15.2.4 Hospitality .............................................................................................................................. 87

15.2.5 Increasing provisioning level .................................................................................................... 88

15.2.6 Infra ...................................................................................................................................... 89

15.2.7 Management .......................................................................................................................... 92

15.2.8 Noe sets ................................................................................................................................. 95

15.2.9 O2G ....................................................................................................................................... 95 15.2.10 OT ....................................................................................................................................... 96

15.2.11 Rainbow ............................................................................................................................... 96

15.2.12 Security ................................................................................................................................ 96

15.2.13 Serviceability/maintenance .................................................................................................. 100

15.2.14 Sip terminals ....................................................................................................................... 100

15.2.15 SIP Trunking features .......................................................................................................... 100

15.2.16 Voice mails ......................................................................................................................... 101

15.3 List of features brought in MD1 patch ........................................................................................... 101

15.4 Features under PCS ..................................................................................................................... 102

16 OXE COMPONENTS ........................................................................................................................... 102

17 COUNTRIES IN WHICH RELEASE 12.2 IS TECHNICALLY RELEASED ...................................................... 106

18 REMARKS & RESTRICTIONS .............................................................................................................. 114

18.1 RESTRICTIONS, KNOWN ISSUES ................................................................................................. 114

18.1.1 Restrictions........................................................................................................................... 114

18.1.2 Misc information, Other issues ............................................................................................... 116

18.1.3 KVM ..................................................................................................................................... 118

18.1.4 Other virtualized systems ...................................................................................................... 119

18.2 COMMUNICATION SERVERS ........................................................................................................ 119

18.2.1 Call Server CPU ..................................................................................................................... 119

18.2.2 UPS ...................................................................................................................................... 119




18.2.3 Blade Center & older CPUs .................................................................................................... 119

18.2.4 Passive Communication Server............................................................................................... 120

18.2.5 Appliance Servers/ G.A.S. & Bill Of Material (BOM) .................................................................. 121

18.3 VIRTUALIZATION ........................................................................................................................ 121

18.3.1 CONFIGURATION .................................................................................................................. 121

18.3.2 SUMMARY ON COMPONENTS NEEDED FOR INSTALLATION .................................................... 122 18.4 IP CRYSTAL MEDIA GATEWAY ..................................................................................................... 123

18.5 MEDIA GATEWAY ........................................................................................................................ 124

18.5.1 GD/GA boards ....................................................................................................................... 124 18.5.2 INTIPB board ........................................................................................................................ 124

18.5.3 Remote connection towards GD/GA/INTIP boards ................................................................... 124

18.5.4 NGP boards (GD3/GA3/INTIP3) ............................................................................................. 125 18.5.5 OMS (remote access & ESXi configuration rules) ..................................................................... 126

18.6 VoIP ........................................................................................................................................... 127

18.7 ABC-F IP TRUNK GROUP ............................................................................................................. 129 18.8 SIP SETS .................................................................................................................................... 130

18.9 OTHER SETS ............................................................................................................................... 131

18.9.1 IP Phone V1 – V1S ................................................................................................................ 131

18.9.2 IP Phone V2 (e-Reflexe) ........................................................................................................ 131

18.9.3 Alcatel series 8 & 9 sets ........................................................................................................ 131

18.9.4 Alcatel-Lucent 8082 My IC Phone ........................................................................................... 134 18.9.5 MIPT 300 & 600 handsets ..................................................................................................... 134

18.9.6 DECT ................................................................................................................................... 135

18.9.7 IP DECT system (NEC) .......................................................................................................... 135

18.9.8 UA Extender 4051/4052 ........................................................................................................ 136

18.9.9 NOE3G (premium ip phones) ................................................................................................. 136

18.9.10 NOE3G EE .......................................................................................................................... 136

18.9.11 OTC Android Smartphone .................................................................................................... 137

18.10 IP TOUCH SECURITY FEATURE .................................................................................................. 137

18.11 SIP TLS FOR EXTERNAL GATEWAY ............................................................................................. 138 18.12 APPLICATIONS .......................................................................................................................... 138

18.12.1 OmniVista 4760 & 4760i ...................................................................................................... 138

18.12.2 SIP Device Management Server ........................................................................................... 138 18.12.3 AAS (Audio Station) ............................................................................................................. 138

18.12.4 External Voice Mail .............................................................................................................. 139

18.13 Security .................................................................................................................................... 139 18.13.1 Voice mail 4645: access blocking after bad password attempts .............................................. 139

18.13.2 Voice mail 4645 : minimum user password length option ....................................................... 140

18.14 CLIP ......................................................................................................................................... 140

18.15 DIRECTORY .............................................................................................................................. 140

18.16 BOARDS ................................................................................................................................... 142

18.17 MISCELLANEOUS....................................................................................................................... 142

19 CORRECTED DEFAULTS ..................................................................................................................... 147




19.1 M3.402.34 R12.2 MD12 ............................................................................................................... 147

19.2 M3.402.33 R12.2 MD11 ............................................................................................................... 149

19.3 M3.402.32 R12.2 MD10 ............................................................................................................... 151

19.4 M3.402.31 R12.2 MD9 ................................................................................................................. 153

19.5 M3.402.30 R12.2 MD8 ................................................................................................................. 156

19.6 M3.402.29 R12.2 MD7 ................................................................................................................. 161 19.7 M3.402.28.A R12.2 MD6 .............................................................................................................. 164

19.8 M3.402.28 R12.2 ......................................................................................................................... 165

19.9 M3.402.27.A R12.2 MD5 .............................................................................................................. 169 19.10 M3.402.27 ................................................................................................................................ 170

19.11 M3.402.26.B ............................................................................................................................. 175

19.12 M3.402.26.A R12.2 MD4 ............................................................................................................ 176 19.13 M3.402.26 ................................................................................................................................ 177

19.14 M3.402.25.A R12.2 MD3 ............................................................................................................ 182

19.15 M3.402.25 ................................................................................................................................ 183 19.16 M3.402.24.a OXR R12.2 MD2 ..................................................................................................... 188

19.17 M3.402.24 ................................................................................................................................ 191

19.18 M3.402.22.c OXE R12.2 MD1 ..................................................................................................... 194

20 TECHNICAL SUPPORT........................................................................................................................ 195

21 Interoperability with Third-Party applications ...................................................................................... 195




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.

Version M3.402 is a version with new software locks (for Full Software Native Encryption). M3.402.30 patch

corresponds to MD8 patch of R12.2 OXE release.




2 DOCUMENTS

General release documents

OmniPCX Enterprise R12.2 - what's new to sell

This presentation describes the OmniPCX Enterprise R12.2 key highlights and sales opportunities.

Audience: Sales reps and sales specialists. General availability: July 9th 2018.

OmniPCX Enterprise R12.2 & OmniVista 8770 R4.0 pre-sales overview

TBE064 - Pre-Sales presentation describing the evolutions brought, as of July 9th 2018, by OmniPCX

Enterprise R12.2 and OmniVista 8770 R4.0 - Edition 01 - June 2018

OmniPCX Enterprise R12.2 & Generic Appliance Server

TBE063 - Pre-sales presentation introducing the Generic Appliance Server package, available as of

OmniPCX Enterprise R12.2 (edition 01) - June 2018

OpenTouch Suite for MLE in virtualized environment, overview

TBE031 - Pre-Sales presentation describing the MLE products virtualization capabilities and the main

principles regarding license control deployment - Edition 03b, update for H1 2018 offers - June 2018

Cross Compatibility - MLE - July 2018 ENT_MLE_032809

This document covers compatibility between OpenTouch Suite software releases and applications. MLE

July 2018

Hardware / Applications Compatibilities

TC0418 Ed. 19

OmniPCX Enterprise Features List and Provisioning Level Releases R10.0 - R12.2

Reference: ENT_MLE_016348

OpenTouch Suite for MLE virtualization design guide

Pre-Sales design guide related to the deployment in virtualized environment of products part of

OpenTouch Suite for MLE offer

Related Technical Communications:

Note: Most of the old technical communications are not mentioned anymore. Refer to previous release notes

same section if needed.

TC2515en-Ed01_Warning_OMS_Suse_SP3

TC2481-RN for Base Station 8378 DECT IP-xBS Release R100

TC2462 OXE Configuration Guide for Rainbow PBX Integration

TC2181en-Ed14_Release_Note_for_8088_Smart_DeskPhone_Release_302_in_Business_mode

TC2347en-Ed04_Technical Release Notes For 8088 R301 Smart Deskphone




TC2431en-Ed01_Virtualization Configuration of OXE following releases and ESXi infra version

TC2312 Ed03: “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)

TC1854en-Ed25_OmniPCX_Enterprise_patch_aligment_procedure.xlsm

TC1897 installation AS HP DL320E G8v2

TC1868 Multicodec evolutions in OXE Release 11.0: Database translation

TC1708 Installing and using the OmniPCX Enterprise PC Installer Software (with compatibility information)

TC1854 OXE patch alignment (patches alignment + database translation table)

TC1271 Checks for integrity and authenticity of downloaded software

TC1255 4008 / 4018 SIP set deployment with OmniPCX Enterprise

TC0779 Synchronization of the system after migration to OmniPCX Enterprise with Appliance Server

TC0778 Migration OmniPCX 4400 to OmniPCX Enterprise

TC2400 PCS upgrade to R12.x improvement

TC2338 R12 Remote installation of PCS

TC1676 messages CONNECT, management Burst size & Burst delay

Remote worker/ noe on vpn: IPsec VPN Deployment Guide for Remote Workers for DeskPhones and Premium

DeskPhones s Serie

TC2431 Virtualization: Configuration of OXE following releases and ESXi infra version

Phase-in products

E-Flash phase-in EF-Phase-in-C114 – announce of a new MLE offer: the Alcatel-Lucent OmniPCX® Enterprise

Communication Server release 12.2

Phase-out products

Always check for latest phase-out products on the Business Portal (EF-Phase-out)

Latest products phased-out:

- The CPU8 board is replacing the CPU7-2 board.

o CPU7-2 board and related components, which were in stock permitting since October 2017,

are no longer available from October 2018 Offer. Please refer to the eFlash Phase-out C093

for more details.

- APFU card, analog trunk diversion card (3BA53107AA)

- GS card (3BA23196AA)

System documentation

System documentation is no more provided as a CDROM. R12.2 documentation download is available at the

Business Portal: https://businessportal2.alcatel-lucent.com/technical-documentation-library

(Customer Support > Technical Support > Technical Documentation Library)

https://businessportal2.alcatel-lucent.com/8AL90345ENAA

https://businessportal2.alcatel-lucent.com/8AL90345ENAA

https://businessportal2.alcatel-lucent.com/ef-phase-c114-en-opentouch-suite-mid-sized-and-large-enterprises-h1-2018-preview

https://businessportal2.alcatel-lucent.com/technical-documentation-library




3 INTRODUCTION TO RELEASE 12.2

Note Release R12.2 need the same supported CPUs/vm recommendations than Release R12.0 or 12.1

For that release 12.2 Actis is requested

- Oxe version lock: lock 165: value 47

- Oxe Beta lock 87: value 27

- Native Encryption: 424

Below are the corresponding levels of compatibilities for database & software corrections.

Patch M340234 - MAO DB software version: M340226

Patch Patches Aligned DB version Compatible till

j2.5 j2.501.23 j2.501.21

j2 j2.603.38 j2.603.38

k1 k1.400.37 k1.400.35

k1.5 k1.520.47 k1.520.43

l1 l1.301.42 l1.301.41

l2 l2.300.43 l2.300.43

m1 m1.403.27 m1.403.26

m2 m2.300.29 m2.300.25

The program of certification is available on the Business Portal

In this document, you will find the steps necessary for installing version M3.402.34 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,

R12.0 & R12.1

− 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.2 features restrictions, features to come & misc. information.




3.1 New hardware

− SSD disks

o Those disks are only available for new CPUs CPU8 & CS-3

− New sets

o 8088S: 16Gb of memory for apps storage

− 8378 new DECT ip Base station

− IBS DECT refresh (8379 IBS renewal)

3.2 List of new features since MD2/ interoperability

see details in chap. 15 NEW FEATURES AND NEW HARDWARE IN RELEASE 12.2

3.2.1 Call Handling features

See also chapter 15.2 for a more detailed explanation

− OXE Hunting Group: login logoff through CSTA

− 4645: simple answering mode only

− Filtering activation when Boss' PC with softphone is in standby mode, power off (MD1)

− Multi-device: possibility to disable from OTCPC the main deskphone to ring/ ring only selected devices

− Long press on "green call button" to get in to "call log menu" (in 8242, 8262, 8232 DECT sets)

− PER - Increase the Limits for OXE max number for incoming greeting guides

− Management of additional fields for users

− Phone book access in Centrex Mode

− Minimize required OXE reboots on software locks installation

− TDM public carrier network phase out anticipation: DTMF In Band Support on OXE / OTBE Public SIP

Trunking connection

− ARQ (crqms00202657) Number of attendant 4059IP in a group with common services is limited to 20

− SNMP Counters for trunking

− Disable loudspeaker on IP phones

− Call log for IPDSP when OOS: PEROXE-195 MD1

− DECT set should be seen as available during "busy" states (directory lookup, com loc consultation, settings

modification, …)

− PER (crqms00186375) Randomly the Automatic network callback facility is not working over ABC-F

− IPDS and REX in Tandem, but secondary set shall not ring if main set is in service

− ARQ (crqms00202636) Need possibility to create profile for Desk Sharing User

− Possibility to disable dhcp survi on NOE/NOE-3G sets via MGR

3.2.2 CCD

− DECT set as ProACD

− Pro-ACD phones support:

− 8018




− 8028/29

− 8008

− OTCC: Increase the number of Statistics Pilots per OXE CS

− Total number of declared & connected Call Center agents per OXE CS to increase

− CCD: Allow queuing when call is transferred to a pilot

− WBM - Enhancement of CCx helps and default display values

3.2.3 Encryption

− Full Native Software encryption 1rst step

− PCS with native encryption

− Native encryption: customized certificates

− Partial native encryption

− SHA-2 (only on V5m)

3.2.4 Increasing provisioning level/ product limits

− Total number of declared & connected Call center agents per OXE CS to increase

− Increase the limits for OXE max number for incoming greeting guides

3.2.5 Infra

− SSD disks are validated & will now be delivered on new CPUs

− Most of CPUs can now be installed by new tool S.O.T. (Software Orchestration Tool)

− Support of SUSE SP3 for Boot DVD + OMS (MD1 feature)

− ABCACom evolution for application centric virtual environments like Citrix XenApp

− Support of G.A.S. (Generic Appliance Server). From this release, the classic Appliance Server is no more

delivered on new offers. As replacement, the G.A.S. is now proposed. Check system documentation &

dedicated chapter in this document.

− Save Restore of OXE data on network

3.2.6 Interworking/ Interoperability tested

− OXE - OTMS interworking

− IP Touch Security Encryption with OT applications

− ABC interworking refer to chapter 14.3.1 OXE compatibilities in ABC network for details

− 8770 R4.0 (includes new developments for OXE R12.2)

− New 4059EE version 2.0.0.15

3.2.7 Maintenance

− New tnet tool

− New infocollect 5.4 (MD1)

− New Rainbow OXE incidents

3.2.8 Mobility

− New IP DECT solution with new xBS stations




− Refer to TC2481 (“TC2481 Release Note for Base Station 8378 DECT IP-BS Release R100”) & system

documentation

− Features released in MD2 patch:

o Multi PARI: xBS deployment under PCS when more than > 254 xBS.

o Multi PARI management modification:

See document Getting started with the 8378 DECT IP-xBS solution on OXE (8AL90356ENAA ed.02,

especially sections 5.1, 5.12) and Technical Communication TC 2555 “DECT PARIs Configuration in

R12.2”

o External synchronization: mixed architecture with xBS-ibs & xBS-rbs and xBS-xBS. Deployment of

external synchronization needs to comply with some technical constraints. See document DECT

Engineering Rules (8AL90874USAA ed.05, especially section 7 about xBS)

− features to release in a further step

o auto registration

o SUOTA

o Campus (IBS, RBS with new xBS)

3.2.9 O2G

− The OmniPCX Open Gateway (O2G) is a standalone application providing Open Web Services on top of

OXE communication platforms

3.2.10 Rainbow

− Web RTC Gateway support for Rainbow + openness of OXE Config protocol exposed by CCCA

3.2.11 Security

− Virtual Management Outbound for virtualized host

− Audit tool to assess OXE/OT security

3.2.12 Terminals

− New Noe sets

o 8088S (8088 with extended memory)

o New Noe TDM sets 80x9

− New 4059EE version 2.0.0.15

Version 5.30.13 with new features (see dedicated chapter for that: 18.2.7)

− 8008 SIP business mode support

− 8008, 8018, 8028s, 8058s, 8068s, 8078s deskphones IPv6 support

− Filtering activation when Boss' PC with softphone is in standby mode, power off

3.2.13 Virtualization

− Compatibility: vmware/Esx support of SCSI disks

− Virtualized OXE license/key manual check possibility in SpAdmin

− Hyper-V : will be released later

https://businessportal2.alcatel-lucent.com/TC2481en




3.3 Features under PCS

− Dect ip xBS when there is more than 255 xBS on the same location.

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.

3.4 Features availability in progress (MDx patches)

4 SOFTWARE PACKAGE & OTHER COMPONENTS

The software package contains the OmniPCX Enterprise R12.2

PC Installer 5.2 minimum version is mandatory for installation (check compatibilities for Windows OS. Latest

version released is 5.6)

!! Notice that PC Installer is no more supported & you must use S.O.T. as replacement.

OmniPCX Enterprise R12.2 software M3.402.34

M3.402 complete version

M3.402.34 static patch

SM3.402.34 secured patch for Thales solution ONLY!! (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.

For systems using Full Software Native Encryption this patch MUST NOT be installed

Other:

Memory bank for CPU7s2 (ONLY for releases from R12.0): orderable item is 3BA27056AC (SDRAM 512MB for

CPU7-2)

Reference Reference or type Misc

OMNIPCX ENTERPRISE R12.2 DVD-R

Version M3.402.34 (DVD)

OXE Only available if factory integration

OMNIPCX ENTERPRISE R12.2 Thales

SECURED DVD-R

Secured Version SM3.402.34 (DVD)

OXE Only available if factory integration

https://businessportal2.alcatel-lucent.com/documents-swdl?f%5b1%5d=field_document_doctype%3A830&f%5b2%5d=field_xproducts%3A7471

https://businessportal2.alcatel-lucent.com/documents-swdl?f%5b1%5d=field_document_doctype%3A830&f%5b2%5d=field_xproducts%3A7471




vmFlex-2.1.100.013 for CentOS 7 if

ESXi release is 5.5 or above

or

vmFlex-CentOs5-2.1.000.093 for

CentOS5 if ESXi release is lower than

5.5

vmFlex-CentOs5-2.1.000.093 for KVM

vmflex centOS vmFlex-2.1.100.013

esxi >= 5.5

Esxi < 5.5

KVM

OXE IPV6-IPV4 translator DVD-R ipv4/v6 translator OST64.iso 4.02 (iso), to be used with bootDVD

Suse SP3 bootdvd-12.3.008.001

OXE MS APPLICATION DVD-R

Software Version 6.02

OMS

OXE binary 8.03 (updated along with the OXE

patches)

bootDVD Suse SP3 bootdvd-12.3.008.001

GAS/ OXE Software Server GAS/ Oxe Software

Server

OXE SW Server 5.16 (oxe version M3.402.34)

OmniVista 8770 R4.0 Software

(version R4.0.09.00)

OmniVista 8770

OmniVista 8770 R4.0.09.00 + patches

System documentation is no more provided on

a CD.

It is available on the Alcatel-Lucent Business

Portal, in the section Technical Support\

Technical Documentation Library

O2G O2G R1.0 DVD-R

SW MEDIA KIT

O2G

Technical Release version 14.0.000.017

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

List of binaries in all different patches of version M3.402

Version of all components is in chapter 16.

https://businessportal2.alcatel-lucent.com/ENT_MLE_015903




5 BEFORE STARTING

5.1 Checks to perform

▪ Compatibilities/ Product Limits

Consult document about CROSS-COMPATIBILITY/ PRODUCT LIMITS (see chap. 2 DOCUMENTS)

▪ 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 (Applications/ Hardware/ Terminals Cross compatibility)

▪ Conditions for installation in ABC network

Conditions for Installation of RELEASE 12.2 in network is detailed in the last “MLE CrossCompatibility”

document available on Business Portal.

▪ Reminder on applications & functionalities

The table below shows all the applications and functionalities which are no more longer provided by OmniPCX

Enterprise R12.1, whatever hardware used.

Family Type of application Migration to

Compulsory

deletion/ modification before

migrating to R12.2

Documentation

47xx OmniVista 4760i “mgr” or OmniVista 8770

or WBM (from R12.0)

Yes System Documentation

4715, 4730, 4740 or 4740 PTP

OmniVista 8770 No TC1479

4730i mgr or OmniVista 8770 Not applicable System Documentation

4755 OmniVista 8770 No TCV010

TCV017

TC1479 4000 Directory Server 8770 LDAP Server

Directory PC Client for

4755/4000

8770 Directory Client

Voice mail

systems

4630, 4620 or VPS35

4635 VPCPU, 4635 or VPCPU-1

4645 or OT MediaCenter

ACT migration 4300, 2600, 4600 or

5400

Manage the equipment in

a new crystal ACT or

common hw rack

Yes No

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

4735 & 4736 CCS

4961 first party TAPI

middleware

No migration – Not

supported

Not applicable No

4973 Telephony Assistant

Not supported (Replaced by OmniTouch UC My

Phone)

Not applicable




Family Type of application Migration to

Compulsory

deletion/ modification before

migrating to R12.2

Documentation

Others Alcatel Unified

Messaging

OTMC Not applicable

Daughter board SPB Moxa box IP/V24 module No System Documentation

Overflow on QoS (VoIP)

Not supported No No

CPU2, CPU3, CPU5 Step1/Step2/

Step3, CPU6, CPU7s1,

All Appl. Servers except Lenovo M6 & HP

G8v1/v2

Replaced by CPU7-2 – with 512 MB

memory change or CS-2

or Appliance Server or vmWare virtualisation

(depends on the Actis configuration)

or new cpus CS-3/CPU8

No No

LIOE & TSC-LIOE INTIP3 Yes No

INT1/INT2 INTOF-2 Yes No

VoWLAN VoWLAN R1.x VoWLAN R5.x No TC1596

▪ Applications and functionalities dependent on CPUs and hardware platform used

Depending on the type of CPU (crystal CPU, Appliance Server, Call Server in rack, virtualization) and the

hardware platform used (Crystal, common hardware), some applications or functionalities are not authorized.

Crystal CPU (7s2 or 8)

Call Server (CS-2/3)

Appliance Server or virtualization

Common

hardware Crystal hardware

Voice mail 4645 No Yes Yes No

4615 / VMU-OBCA

4615/VMU-OBCA2 (1)

Yes

(only CPU6)

No No No

Various Campus DECT Yes No No No (4)

DTM for DECT on CPU6

Yes No

DECT8

No

DECT8

No DECT8 (2)

VG on CPU6 Yes No No No GPA2 (2)

DTMF Yes (on CPU6 &

CPU7)

No No No GPA2 (2)

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

(only with CPU6)

No No No (5)

IO2N Yes No No No (5)

SPB No IO2 No No No V24-IP module (3)




Crystal CPU

(7s2 or 8)

Call Server

(CS-2/3)

Appliance Server or virtualization

Common hardware

Crystal hardware

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 still supported by RELEASE 12.2 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

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

▪ Installation on second partition

Coming from ANY version <12.0 the cpu MUST be reformatted: no possible use of unactive

partition (partitions are resized + multipartition process NOK). Coming from R12.0 second

partition installation can be used

▪ VoIP network conformity check

The OmniPCX Enterprise R12.2 is a native IP product when using a CS-2/3 or Appliance Server/vm 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.

5.2 Getting the 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:

- Boot DVD, OXE MS APPLICATION DVD-R

S.O.T.:

- S.O.T. vmware player (free download & use) or workstation on a PC: download S.O.T. on the BPWS

Note: ALEDS tool is no more supported & is replaced by S.O.T.

5.3 ACTIS, eLP & software locks

Release 12.2 needs a change in software locks: R12.2 is defined by lock 165 (value 47)

FSNE needs software lock 424 (set to the value of the number of ip phones)

The Actis version for this OmniPCX Enterprise is 22.2 & the catalog is referenced OXE E30-Ed39.

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

NEW LOCKS

FNSE feature

❖ New values for Software lock #424: equivalent to the number of ip phones

5.4 Before saving the database

The following operation may be necessary coming from an old release:

In the current version, carry out the following commands.

5.4.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 (over 30mn depending on the database & cpu type) 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).

5.4.2 Tickets

REMARKS: On the saving of charging tickets.

Sites going from A9.5xx to R12.2 which wish to retain client tickets (hotel or hospital type) in the ‘TABJUSTIF’

files should "empty" the administrative tickets before saving as these are no more processed as of R3.0. As of

R3.0, administrative tickets are stored in compressed files.

Sites going from R1.5.2 to R12.2 which already have compressed files should save them as they will be

compatible.

5.4.3 From crystal to GAS or vm or 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. When migrating to OXE R12.2 with change of CPU 4400 by a VM or a CS or GAS, 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.

5.5 Call Server compatibilities

Warning FOLLOW CAREFULY THE RULES OF THIS SUB-CHAPTER (same rules as those from R12.0)

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 or upper upgrade by Actis

• Can be ordered separately in Actis

- CPU8

- CS-2

- CS-3

- Appliance server Lenovo M5

- New Appliance server Lenovo M6

- Appliance server HP DL 320e G8v1 with a bios update: see this link for upgrade information

- Appliance server HP DL 320e 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 reformatted 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.

http://h20564.www2.hpe.com/hpsc/swd/public/detail?sp4ts.oid=5249568&swItemId=MTX_55d75794edb141ed946952e9be&swEnvOid=4064#tab4




5.6 Firmware upgrade

Going from any version up to this release: iptouch sets will upgrade their firmware. Take this time into account

before upgrading. Chapter 5 shows all the components & firmware versions (in bold: new).

8088 Android sets will do the upgrade on the Cloud if correct managemen is performed (see dedicated chapter

on system documentation/ terminals

5.7 Voice guides

Ensure that you have the voice guides required in RELEASE 12.2

5.7.1 System voice guides

The version of system voice guides compatible with the OmniPCX Enterprise R12.1 is v5.3 CD-ROM reference:

3BA 57423 AAAG

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.

5.7.2 Alcatel 4645 voice guides

The version of the Alcatel 4645 voice guides is v1.10. CD-ROM reference: 3BA 27588 AAAH

https://businessportal2.alcatel-lucent.com/node/347441





Version details:

09 07.16.10 e-Va voice guides CD-ROM – v1.8

Corrected fault reports:

crms00197618 – New voice prompts 1071, 1091, 1608,

1626, 1628 & 1646 in Cantonese


New Swedish voice prompts.

Add of Hebrew language.


New voice prompt 1911 “Your account is locked” in all

languages

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




Country Code Law A Law µ

Hungarian HU0 x

Icelandic IS0 x

Italian IT0 x x

Japanese JP0 x x

Korean KR0 x x

Latvian LV0 x

Lithuanian LT0 x

Mandarin China CN0 x x

Mandarin Taiwan CN1 x x

Norwegian NO0 x x

Polish PL0 x x

Portuguese PT0 x x

Portuguese Brazil PT1 x x

Romanian RO0 x

Russian RU0 x x

Slovak SK0 x

Slovenian SI0 x

Spanish ES0 x

Spanish United States ES2 x x

Spanish Latin America ES3 x x

Swedish SV0 x x

Turkish TR0 x

5.8 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

size there is no change.

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

Consult also the security news alerts.

You can use the new oxe embedded tool “securitystatustool” to perform a check of the OXE. Those controls

are detailed in chapter 15.

5.10 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 …

− Consult TC1854 for database translation compatibilities

− 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.2. 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, 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.

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

When migrating a system with "SIP Device" / "External set" to R9.0, the system moves these sets into the

new mode (SIP extension) automatically.

Warnin

g

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.1, 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.

5.11 Migrating old versions

- Sometimes there is no automatic translation between 2 releases. An intermediate translation has to be

done. For that you need to use the document “TC1854en-

Ed25_OmniPCX_Enterprise_patch_aligment_procedure.xlsm“ in the business portal.

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

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

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.

https://businessportal2.alcatel-lucent.com/customer-support/technical-support/tdl?articleID=000007973

https://businessportal2.alcatel-lucent.com/node/221781?articleID=000011120




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.

Concerning the new solution ip dect on xBS there is no change on software locks.

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.

5.13 New installation

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.

Warning Migrating from a CPU7S1/2 to CPU8: if the embedded ethernet was used a new cable has to be

installed on the cpu that lacks this connection to the external switch.

This internal interface is not present anymore. See corresponding chapter 18.1.1 new CPUS

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.




5.14 Updating the PCSs

Coming from versions lower than R12.0 there is no possibility to use the second partition. Disk must be re-

installed from scratch.

See also TC2338 for a specific installation method without going on site. This method is not adapted to sites

that are secured (ssh v1 or v2). Workaround today is to let the ftp protocol pass for the time of the operation.

5.15 OmniPCX 4400 migration to R12.1

Two possibilities are provided for migration to R12.1:

− Migration to R12.1, keeping the 4400 type CPU: only CPU7s2 with new memory bank (512Mb) or new CP8

are compatible

− Migration to R12.1, changing the 4400 type CPU for Appliance Servers (called Migration with Appliance

Server). This operation is done automatically as a translation.

The migration to R12.1 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

5.1.

− The replacing of 4400 CPUs with Appliance Servers leads to restrictions on the use of certain

functionalities; see paragraph .

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

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

5.15.1 Use of the hardware key

Hardware key is no more used on CPU7s2 since it is no more proposed by Actis.

Hardware key is not available on CPU8.

5.15.2 Crystal hardware compatibility with an Appliance Server

See the table in paragraph

See also phase-out & compatibility documents

Technical communication TC0778 Migration OmniPCX 4400 to OmniPCX Enterprise describes the steps

necessary for transition to Release 9.1 but is not updated to R12.0




6 INSTALLING THE SOFTWARE

6.1 Using dual partitioning

▪ Coming from ANY version <12.0 the cpu MUST be reformatted: no possible use of

unactive partition (partitions are resized + multipartition process NOK)

▪ Coming from R12.0 second partition installation can be used.

6.2 S.O.T.

S.O.T. first released version is 1.0

Installation from OXE R11.x is supported & tested

Reminder:

Flex server installation does not need any 3rd party tool (vmware or kvm solution)

6.3 PC Installer

PC Installer is no more supported. Installing old versions will be not available as well as boards firmware reload.

PC Installer is still present in deliveries. For those who still want to use it, install the latest version 5.6

Compat

ibility

Only PC Installer 5.2 minimum version can install new CPUs CS-3 & CPU8. This version is retro-

compatible & can install any previous OXE version.

Notice also that latest Windows versions may not be compatible with PC Installer on some PCs

6.4 Installation on PCS (OXE not secured by ssh)

Update PCS systems then update Main & Stdb CPUs

The issue when using “pcscopy” where PCS become unreachable after reset is fixed on this version.

Coming from a release up to L2 the PCS needs to be reformatted (new Linux M1/R12.0 constraint). Upgrade

of a PCS without being physically at the PCS location is described in TC2338 (https://businessportal2.alcatel-

lucent.com/TC2338en ).

6.5 Installation on PCS (OXE secured by ssh)

Previous method will not work. A solution is under study.

A workaround can be to let the not secured protocols temporarily pass through the firewalls.






6.6 Secured systems

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

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 highly recommended to use this level.

6.6.2 Installation of a secured system for VoIP encryption ("IP Touch Security" service –

Thales solution)

Thales encryption: 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".

There is no need of this kind of patch for FSNE feature.

Installation process

The installation of security on a system in M3.402.2x.y must be carried in two steps:

1. Installation of system with generic version i.e.:

Installation generic version M3.402, installation of static patch M3.402.2x and then installation of dynamic

patch M3.402.2x.y with usual tools (Standard Installation, Installation on inactive partition or Remote

Download).

2. Installation of the latest patch of security in addition of the previous installation i.e.:

Installation of the security patch SM3.402.2x.y (called also SM3.402.2x.y) containing the latest secured

binaries with usual tools (Deliveries installation or Remote Download).

6.6.3 Using the Remote Download

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 to unactive partition is possible through a specific question & guaranties a more secured

upgrade. If answered yes, ANY kind of reboot will switch back to the other partition. This behavior can b

Cancelled if system seems stable.

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.

Consult system documentation for operational details.

6.6.4 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”




6.6.5 Creating a blank database

Warning A blank database should only be created for CPU installation on a new site

Login swinst

Password xxxx option 7 Database tools

option 2 Create an empty database

Enter country name example "is" for “Iceland”

6.6.6 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

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

7 INSTALLING & CHECKING Actis files

The procedure for installing OPS files puts together the following steps: RUNMAO, translation of the database

and installation of the OPS files.

7.1 Procedure

Copy the OPS files using "ftp" in the directory /usr4/BACKUP/OPS.

Use the menu swinst/OPS configuration.

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.

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

7.3 Checks on virtualization

Document: OpenTouch Suite for MLE virtualization design guide

In case the cpu is installed in an esx or KVM environment 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 is:

(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 disconnections & extractions: look at the pre-

sales documentation for more details.

7.4 Checks on Cloud Connected system

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

8 CLIENT INFORMATION

The purpose of this section is to specify the changes in ergonomics or operation that will be visible or available

to users after changing version.





8.1 New ergonomics and operations

8.2 Reminder of changes appeared in Release R12.2

Applications support on 8088 Android. Today only ALE specific applications are compatible due to specific

developments related to the screen size.

Possibility to use an 8058S phone as a 8068S: virtual keys removing. Phone will still not benefit of the Blue

Tooth due to hardware design.

Dect sets can be pro-ACD agents now.

Disable loudspeaker on IP phones.

DECT set should be seen as available during "busy" states (MD1 patch)

DECT : long press on green call button (redial feature) : behavior can be changed


New sets available: 8008 & 8088 Android/noe (no app support)

OXE native call log for calls on busy sets

Support of alarm button on ASCOM MIPT dect sets


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.5 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.7 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.9 Reminder of changes appeared in Release 10.1.1

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

− Visual SIP Voice Mail Access from IP Touch Mail key

8.10 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.14 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.


− 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.17 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.18 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 SYSTEM MANAGEMENT

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

9.2 Special case of IO2N boards (CPU7s2/ CPU8)

CAUTION

− IO2 boards are phase-out and cannot work from R12.0

− CPU6 & CPU7s1 are no more 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.

9.3 Integrated WebBasedManagement

WBM was tested on:




▪ Windows 10 Enterprise 32 bits, Windows 10 Professional 64-bit, Windows 7 Professional 32-bit and

64-bit versions

▪ Windows 8.1 Pro 32-bit and 64-bit versions

▪ Windows XP SP3 and Windows Vista Business Edition

▪ Windows 2012 R2 (64-bit)

▪ Compatibility with Win2016 Server (64-bit)

▪ compatible with VMware ESXi 5.5

Browsers supported are the following (make sure to always have the latest version):

▪ Chrome

▪ FireFox

▪ Edge (on Windows 8/8.1/10 64bits)

10 COMPULSORY MINIMUM ADDITIONAL DATABASE MANAGEMENT

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

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.

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

10.3 Important management if IO2N is present

To solve traffic issues on CPU7s2 (issues related to CPUs crash or peripheral 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

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.




10.4 Important management with sets (noe3Gs, 8018)

By default, an OXE with a default database is configured to use G723

But new generation of IP Phones like 8018, 8058s… do not support the G723.

In consequence, the communication gets no audio.

Changing the system compression defaults immediately fixed the problem.

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

10.6 Some system parameters to check

Use the command “compvisu” to display the parameters.

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

10.6.2 Frame VoIP (Enhanced quality voice)

The Frame VoIP parameter (Enhanced quality voice in previous versions) must be identical on each node

of a network.

It is better to use the Framing 20 ms for G711 or G729.

G723 can only do 30 ms.

10.6.3 Direct RTP for H323 terminals

This parameter must be set to No if only one H323 terminal of the installation does not support the direct RTP




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

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

11.1 Download of 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.

8082 sets in NOE mode & also new noe3G/Premium 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.

communication to be over to perform the reboot. Note

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.




11.2 8088 ANDROID upgrade

Upgrade mechanism through the Cloud is done by management.

Notice that Android 8088 sets cannot be downgraded even if re-installed on a lower OXE version.

11.3 SIP sets upgrade

Operation must be carried by 8770. Check on the Business Portal for latest versions of SIP sets.

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

11.5 Moving from CPU7s1/2 to a CPU8

See chapter 9.2 & 18.1.1: Warning about the embedded ethernet interface that does not exist anymore.

12 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 attendants.

− 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 arguments (help available)

o For noe sets use “downstat i” & “tftp_check -c” tools




− Check the coherence of the files (Suspicion of errors during file transfer: ftp must be set to “binary”

mode).

login Swinst

option 8 Software Identity Display option 6 Application Software Validity Checking

Press 0 for the active version, 1 for the unactive one or q to quit

Please wait .....

Checking mode : 1=size & sum 2=size only (default is 1) 1

Checking size and sum of all files , please wait ...

file modified (authorized) : /DHS3data/manager/mtcl.adm

The application software is correct

Press return

− Check 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

− Dect xBS

Check xBS state with “dectview xbs” & synchronization tree with “xbssynchro”

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

− Remote dongle : Raspberry Pi 2 Model B or Raspberry Pi 3 Model B.




14 COMPATIBILITIES/ PRODUCT LIMITS/ FEATURE LIST

14.1 Documents

Check documents listed in chapter 2 (softw. & hardw. compatibilities, limits …)

Release policy is located at:

Software Release and Hardware Policy for OpenTouch Suite MLE

https://businessportal2.alcatel-lucent.com/opentouch-suite-mid-and-large-enterprises-release-policy

14.2 Status of the Version (database, Product Reports)

Patch Patches Aligned DB version Compatible till

j2.5 j2.501.23 j2.501.21

j2 j2.603.38 j2.603.38

k1 k1.400.37 k1.400.35

k1.5 k1.520.47 k1.520.43

l1 l1.301.42 l1.301.41

l2 l2.300.43 l2.300.43

m1 m1.403.27 m1.403.26

m2 m2.300.29 m2.300.25

14.3 Interoperability tests status

14.3.1 OXE compatibilities in ABC network

The table below shows the compatibility in ABC network and Audit/Broadcast: extract from cross compatibility

document. No patch number is named: always take the latest one.

Grey cell doesn’t mean it is incompatible.

The table must be read: column version compatible with the line version.




‘Y’=’available’, ’OM’=’Only for OXE migration’, ’N’= ‘Not supported’, ‘NA’= ‘Not Applicable’

14.3.2 Open Touch

OXE R12.2 is compatible with OT R2.3.1

Check document “MLE_CrossCompatibility_July_2018” sheet named “OpenTouch”

OT interworking:

▪ OTMS version14.0.009.003

▪ OTMC version14.0.009.003

▪ OFC R7.6 version OFC 7.6.0.87

▪ OTCT PC version 2.3.100.014

▪ OTCT Mobile (OTC iPhone version 2.31.08.7)

14.3.3 OXO interop.

OXO interoperability was tested between OXE release M3 and OXO version ONE022

14.3.4 IP sets compatibility

Refer to “MLE_Cross_compatibility” document for ip sets compatibility. Inside that document, check for more

details in chapter 7: “Endpoint compatibility”.

14.3.5 8770

OXE R12.2 was tested with 8770 4.0.07.00

Some R12.2 OXE features need that R4.0 release of OmniVista

14.3.6 Sub-device on older sets

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

14.3.7 Common hardware & Crystal hardware mixed

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




14.4 OEM/External equipment compatibility

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

14.5 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.2

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.3.0.1 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 2.0 N Dedicated PC Installer

utility

4059 IP 5.5.4 Windows 8/8.1

/10 (64 bit),

Windows 7 (64

N Dedicated PC Installer

utility




bit & 32 bit)

NON SIP SETS

8115 / 8125 9.0.12 Conference

module

N Boot on a USB stick on the

terminal

DECT

Dect 500 v10.88 N (note) FLASHLOADER application

Dect 500 EX v20.05 N (note) FLASHLOADER application

8212 v0007 b0003 N FLASHLOADER application

8232 v48.81 b0008 N FLASHLOADER application+

SUOTA (oxe R12.2 MD1)

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

4080 Access Point

: 4910b630.dwl

DAP firmware for

8340 Access Point

: 4920b630.dwl

DAP loader package

: 4992030a.dwl

DAP controller

versions

: 6.21.0299

Dect on IP N (note)

Note: sets NOT compatible with dect ip xBS solution




Minimum DECT sets versions for Auto-registration feature:

• 8212 – v0012b0002 • 8232 – v4383b0004

• 8242 – v6382b0003

• 8262 – v5681b0006

• 8262Ex – v7682b0006

14.6 Genesys Compact Edition

The “Genesys Compact Edition (GCE)” product is phase out. Previous mentioned patch is not tested anymore

& may not operate correctly.

Check with your local presales for a replacement solution.

15 NEW FEATURES AND NEW HARDWARE IN RELEASE 12.2

You can also refer to the System documentation.

15.1 New hardware

15.1.1 IBS DECT refresh (8379 IBS renewal)

IBS Renewal is an evolution of IBS NG made necessary by the obsolescence of the RF transceiver and of the

power supply controller.

IBS renewal has worldwide coverage. There is no more need for Country/Region specific variants. A software

evolution of OXE will indicate to IBS Renewal which regional setting it shall use. However, a default region will

be configured in IBS Renewal for compatibility with existing systems

15.1.2 New 8088S set

Changes:

- 16Gb of memory will bring more storage possibility for external applications

15.1.3 SSD Disks

SSD device will replace traditional electro-mechanical hard drives as mass storage device of the OXE system

(CS-3 & CPU8).

SSD is based on NAND flash chips in opposite to traditional hard drives, based on electro-magnetic field

polarizing sensitive plates.

Hard-disk kit:

- 3BA27013AD DISK DRIVE for CPU8 / CS-3

Introduction of SSD with 3BA27013ADBA via commercial ECO 500000015506 (date: 06/08/2018)

- 3EH76031AD DISK DRIVE SATA for CS-2




Introduction of SSD with 3EH76031ADBA

15.1.4 New dect base station xBS 8378

This new ip base station is part of the new Dect ip solution. Not compatible with the NEC dect ip solution.

15.2 New features in MD2: description/explanation & management

15.2.1 Call Handling features

15.2.1.1 4059EE XenApp Virtualized Attendant

On 4059EE virtualized in Citrix XenApp application centric environment.

4059EE application is installed on Citrix Desktop Windows 2012 server.

4059EE instances are launched in CitrixReceiver® Apps web page.

Need of the version of 4059 EE R2.0.x

With 4059EE 2.0.x version, at startup a drop-down list allows to choose the attendant directory number

among a set of attendant/phone set pairs.

15.2.1.2 Additional fields for user

To add 4 new parameters in OXE management "Users" (mgr, WBM and 8770). These new parameters can be

used by an external application which can retrieve the data from 8770 LDAP.

These 4 new parameters are called "Comment 1", "Comment 2", "Comment 3", "Comment 4". They are stored in OXE database.

In WBM and 8770, they are in "Miscellaneous" group and can be filled with UTF8 characters (up to 127 characters).

Restriction: There is not possible filter on those fields

15.2.1.3 Attendant 4059ee version 2.0

4059EE R2.0 version 2.0.0.18

Changelogs for 4059EE:

2.0.0.18

General

BUGFIX: 00378230 & 00378234 - Issue when search in OXE phone book

2.0.0.17

General

BUGFIX: 00345909, Abc-a disconnected on frozen Ldap query

Feature: OXE

UPDATE: Abcacom.exe updated to 7.2.3.0




2.0.0.16

General

BUGFIX: Result columns persist regardless of returned searchdata

BUGFIX: Last result column allowed to be unchecked

BUGFIX: Retrieved mappable columns added dynamically to user settings

BUGFIX: Contact card toolbar sometimes incorrectly resized

UD General:

UPDATE: EE preserve all search requests except 'Image' for repeat operations

2.0.0.15

General

BUGFIX: 00357512 Directory name conflict

BUGFIX: Contact card incorrectly displayed detail view

2.0.0.14

General

BUGFIX: 00345909, Abc-a disconnected on frozen Ldap query

2.0.0.13

General

BUGFIX: 00343919, Unable to copy the “contact card settings” from 4059EE

2.0.0.12

General

BUGFIX: Contact card: Multivalued phone numbers incorrectly handled

2.0.0.11

General

BUGFIX: Contact card: Toolbar button not created for item info pagea

BUGFIX: Contact card: Fixed incorrect behavior when clicking colleague/manager.

UDPATE: Contact card: Calendar appointments alpha color updated to accommodate

transparency

UDPATE: Contact card: Search suppressed when dialing from contact card

Feature: OXE

BUGFIX: 00336113, SearchByFirstName always defaulted to false on app startup.

UD LDAP:

BUGFIX: Fixed bad filtering on multi-valued fields

2.0.0.10

General




BUGFIX: Contact card settings: SetDefault button enabled when not supposed to

UPDATE: Improved name/number caching

UPDATE: Language resources updated 2018-10-04

Feature: OXE

BUGFIX: Comma as host delimiter caused abcacom to crash.

BUGFIX: 00326965, waiting calls are invisible

2.0.0.9

General

BUGFIX: Themes not applied on detached blf window

Feature: OXE

BUGFIX: Default device sometimes not stored correctly.

2.0.0.8

General


2.0.0.8

General


2.0.0.7

Feature: OXE

BUGFIX: Some labels in Guide/Service-mode incorrectly resized

OpenTouch:

UPDATE: OTCt users again BLF monitored by OT

UPDATE: FwdState separately handled not to interfere will TelState

2.0.0.6

General


Feature: OXE

BUGFIX: 00295800, loss of call in the call-log

BUGFIX: 00287946, Abbreviated text but enough space is available

2.0.0.5

General

UPDATE: 00287400, Hover effect too light.

UPDATE: Theme adjustments


Feature: OXE

BUGFIX: UD search never invoked on OTCv user pseudo call




BUGFIX: CROXES-16740: External number not displayed in call log

OpenTouch:

BUGFIX: 00300872, BLF otct user: reconnection issue

BUGFIX: 00300885, BLF otct user: status inconsistency

2.0.0.4

General

BUGFIX: Start time for calendar lookups incorrectly set to "now"

BUGFIX: 00279873, Issue 4059ee Crash with exception randomly

Feature: OXE

BUGFIX: 00289793, loss of time in the call log.

UD LDAP:

UPDATE: Ldap templates moved to public docs as part of silent installer adaptions.

Feature: OXE


Installer:

UPDATE: Adaptions made for silent installations.

2.0.0.3

General

BUGFIX: CROXE-6729 M3: 4059EE virtual: BLF item popup menu is not translated

BUGFIX: 1-219194843 - Number formatting incorrectly applied when dialing a OXE CBN

record.

UPDATE: Max instances increased to 120.

UD LDAP:

BUGFIX: CROXE-6673, Ldap overflow doesn't work due to a forcefully closed tcp

connection.

NEW: Support for multi-valued fields.

2.0.0.2

General

BUGFIX: 1-219367470 Modification of detailed view is lost

Feature: OXE

BUGFIX: Fastcall incorrectly triggered

BUGFIX: Called device sometimes not shown in call wnd

BUGFIX: ALE keyboard icon never shown

UD LDAP:

BUGFIX: CROXE-6673, Ldap overflow doesn't work due to multiple hosts management

issues

2.0.0.1

General


Feature: OXE

BUGFIX: CROXE-6530 M3: 4059EE virtual: Three buttons of the status bar do not work




BUGFIX: CROXE 5213 M2-4059EE Virtual: Selection of a bad attendant number is not warned


2.0.0.0

General

NEW: XenApp and multi-instance support

NEW: Ldap lookup in ringing phase

NEW: Themes; Light and Rainbow.

NEW: Support for OT calendar presence state

UD PD:

NEW: E164 support for personal directory search

Feature: OXE

UPDATE: Asynchronous session start


15.2.1.4 Boss/Secretary filtering activation when Boss is OOS (MD1)

The objective of this feature is to allow an assistant to activate manager set filtering and to disable any

manager filtering (to the assistant set or to another assistant set) even if the manager is out of service.

It is delivered in OXE Release R12.2 (M3) with marketing id RQOXE-308.

Existing Behavior: Screening Supervision Feature

The Screening Supervision/ Filtering Supervision key is used to activate or disable forwarding according to call

origin (screening or unscreening) by the assistant.

This facility allows an assistant to activate manager set filtering and to disable any manager filtering (to the

assistant set or to another assistant set).

The assistant must have a filtering supervision key for each screening or unscreening filtering key to be

supervised, activated or disabled.




Signaling by the icon or LED associated with the key (assistant set):

1. Filtering not activated icon off or LED off

2. Filtering activated on this assistant (or on Reflexes sets) icon or LED on steady

3. Filtering activated on another assistant (other assistant or overflow assistant) flashing filtering icon (see

above) or icon on or LED on steady

The problem with the existing behavior is that the filtering activation is not allowed when the manager set is out of service.

Enhancement

The enhancement of the existing feature allows an assistant to activate manager set filtering and to disable

any manager filtering (to the assistant set or to another assistant set) even if the manager is out of service.

NOTE: - The assistant should ensure that a routing assistant is configured to forward the calls to the routing

assistant when the boss is out of service

15.2.1.5 Call log for IPDSP when OOS: PEROXE-195 (MD1)

The objective of this feature is to update the Call Log server with incoming call information for a IPDSP / NOE

set which is in Out Of Service

15.2.1.6 DECT set should be seen as available during "busy" states (directory lookup, misc.

consultations, settings modification …) (MD1)

The objective of this feature is to allow incoming call during menu consultation on DECT set (only for AGAP).

When the DECT user is getting an incoming call during menu consultation, the information related to menu

consultation will be lost and the incoming call is presented to the DECT set.

During menu consultation, the DECT user can receive the incoming call based on the new system parameter

“DECT: Allow call in menu consult.”. The path of this parameter is mgr-> system-> DH-> other system

parameter-> DH-> Local feature parameter




If this parameter is true, the DECT set receives the incoming call.

If this parameter is false, the DECT set does not receives the incoming call.

With this feature, the DECT set can receive the incoming call while accessing the following items only:

• Call log entries.

• Forward services (activating forward, deactivating the forward, etc...)

• Mini messages

• Phone settings

• Personal directory entries

• Missed call list

• Ring tone setting

• Dial by name

• Block dialing

This feature is only for AGAP handsets & does not concern calls with voice mail.

15.2.1.7 Disable loudspeaker on IP phones

In open-space offices like call centers, loudspeaker/hands-free usage would create a very noisy environment

and it is difficult to manage for each and every user.

The objective of this feature is to enable/disable the loudspeaker or handsfree mode based on the parameter

in phone COS. It is delivered in OXE Release R12.2 (M3) with marketing id RQOXE-276 and feature id CROXE-

4425. At present, this feature will be applicable only for NOE terminals.

Existing Behavior

The hands free or loudspeaker mode in terminals allows the user to converse without off hook the handset.

There is no need for the user to off hook the handset to make a call or to attend a call. To make a call in

loudspeaker mode the user can press the “hands free key” or by dialing the digits directly without off hook.

For answering a call-in loudspeaker mode, the user can press the handsfree key or press the take call soft key

on the terminal.

Moreover, during conversation, the user can switch between the loudspeaker mode and handset mode using

the "hands free key".




But, in open-space offices like call centers, loudspeaker/hands-free usage would create a very noisy

environment and it is difficult to manage each and every user.

Enhancement

So, it needs to have a control by the OXE management to restrict the loudspeaker usage on group of

terminals, a new parameter “Hands Free Enable" is created under Alcatel 8 & 9 series phone COS menu.

Loudspeaker is enabled by default and should be disabled if required.

Identified scenarios that will be impacted on disabling the loudspeaker mode are given below

Making a call

When the user dials a digit directly on keypad (without off-hook) to make call, a pop up screen

appears as “Hands free mode not allowed. Please off hook” for 5 seconds. If the user continues

dialing, the digits will be accepted, the call will be established and the audio will be redirected either to

the headset (if the headset is plugged in) or to the handset.

When the user pushes hands free key in idle (to make a call), display "Hands free mode not allowed.

Please off hook”.

In case the user presses any programmed keys or redial key to make a call, the screen appears as

“Hands free mode not allowed. Please off hook” for 5 seconds and the call will be established. But the

audio will be redirected to the headset/handset.

Answering a call

If the user tries to answer a call using hands free key or pressing the take call soft key, a pop up

appears as “Hands free mode not allowed. Please off hook”, until the user off hooks. Call will be

established only when the user off hooks.

Switching between audio modes

During conversation, if the user tries to switch from headset/handset mode to hands free mode by

pressing the hands-free key, the screen “Hands free mode not allowed” appears and it won’t allow the

user to switch to hands free mode.

LS announcement

There will be no restriction on the LS Announcement feature. The user is allowed to make

announcement even though the loudspeaker mode is disabled.

BT handset call recovery mode

During conversation, if the BT handset is in low battery mode (battery down), the user is unable to

continue the conversation through handset. So, the Call Recovery Mode will be activated and the user

will be allowed to answer call in hands free mode. There will be no restriction on this feature.

Interphony mode

The user will be allowed to enable the interphony mode by pressing the interphony key on the

terminal only if the headset is connected to the terminal. Otherwise, if the user presses the interphony

key, the screen appears as “Hands free mode not allowed” for 5 seconds and the interphony mode

cannot be enabled.

In an interphony enabled terminal, if the headset is removed, the interphony mode will be disabled.

Restrictions

- Wake up with music feature will not be allowed if the loudspeaker mode is disabled.

- Auto answer mode with CSTA will not be allowed if the loudspeaker mode is disabled




Details of New Parameter “Hands Free Enable”

A parameter “Hands Free Enable” has been added in the menu “Alcatel Lucent 8&9 series” under phone COS

category with default value “YES”

Parameter Name: Hands Free Enable

Parameter Path: mgr->Alcatel Lucent 8 & 9 series->8 & 9 Series Cos ->Phone Cos- >R/M-> All instances

Values : YES/NO

Default Value : YES

Details of New Parameter “Hands Free Enable”

15.2.1.8 Increase the Limits for OXE max number for incoming greeting guides

The objective of this feature is to increase the max number of incoming greeting guides from 255 to 1000

Existing behavior

Incoming Call Greeting Guide Prefix allows an incoming caller to hear a greeting guide before it is routed to a

pre-configured destination configured using Incoming Greeting Guides. The routing destinations could be a

set, a hunting group (PBX or ACD), or an attendant group.




Each Incoming Greeting Guides can have three sets of voice guides configuration and overflow directory

number. In case a problem occurs on the called set or hunting group, the former routing is replaced by a

second one, or a third one if the problem occurs again.

Enhancement

After R12.2, we can create from 0 up to 999 Incoming Greeting Guides.

This incoming greeting guides will be linked to the Incoming Call Greeting Guide Prefix, which will be dialed

from external. Increasing the creation of Incoming Greeting Guides from 255 to 1000. So we can configure

from 0 up to 999 Incoming Greeting Guides.

15.2.1.9 IPDS and REX in Tandem, but secondary set shall not ring if main set is in service

The objective of this feature is not to ring the secondary set in parallel to the main set when the main set is in

service.

15.2.1.10 Long press on "green call button" to get in to "call log menu" (in 8242, 8262,

8232 DECT sets)

The feature identifier is CROXE-4423 and marketing id of this feature is RQOXE-275.

Until OXE release R12.1, Call log is accessed from DECT AGAP sets (which includes 8232, 8242 and 8262

DECT) through menu page by pressing OK key and navigating to the call log icon, if authorized by phone COS.

From R12.2, direct access to the call log menu is provided on DECT sets by long press of the green call button,

which was used for re-dialing and redial list until R12.1.

Services provided:

This feature provides a direct access to the call log menu on long press of the green call button in DECT AGAP

(which includes 8232, 8242 and 8262 DECT) sets, rather than accessing it via the call log icon in the main

menu page which requires multiple key press.

Existing Behavior

Currently, if a user wants to open his call logs, then the call log icon in main menu page of AGAP sets must be

accessed. This requires multiple key press to access his call log. Hence an enhancement is required to provide

more direct access to user call log by long press on green call button.




Fig 1: Accessing call log via menu page

In AGAP DECT sets, if a long press on green call button is made, either the last dialed user is called or the

redial list is displayed based on the Boolean “DECT: redial list via long press” in Phone features COS.

If the Boolean “DECT: redial list via long press” is set to true in Phone features COS, dialed calls list is

displayed on long press of green call button. If not, then the last dialed number is alerted.

Fig 2: Existing Behavior when “DECT: redial list via long press: True”




Fig 3: Existing Behavior when “DECT: redial list via long press : False”

Enhancement

With the introduction of this feature, more direct access to the user call log is achieved. Instead of accessing

the call log via the icon in the main menu page, the user can access it via long press on the ‘Off hook key’

(green call button) of the set.

As mentioned above, there are already two functionalities defined for long press on green call button under

the phone features COS parameter “DECT: redial list via long press”. Hence for this feature, one more

functionality is introduced under this parameter to open call log via long press.

Fig 4: Behavior on long press after setting the system option to Call log (2)

If the parameter “DECT: redial list via long press” is set to Redial (0), the last dialed number is alerted, if it is

set to Redial list (1), outgone calls list is displayed and if the option is set as Call log (2), then call log of the

user is displayed on long press of Green key

Parameter Name : DECT: redial list via long press

Parameter path: mgr-> Classes of service -> Phone Feature COS -> R/M -> All instances

Values : Redial (0)

Redial list (1)

Call log (2)




Default Value : Redial(0)

Fig 5: Display of modified parameter “DECT:redial list via long press” in English

15.2.1.11 Minimize required OXE reboots on software locks installation - step 1

The objective of this feature is to minimize the OXE system reboot request at the end of OPS installation. It is

delivered in OXE Release R12.2 with marketing id RQOXE-304 and feature id CROXE-4427.

This feature reduces the system reboot required during new OPS installation for capacity change in OXE. This

is achieved by defining the maximum possible remanent reservation for each RAM capacity based on the

parameters like Users, Trunks and Demi-com’s. (Refer Table 1)

During RUNTEL, these Defined Maximum Values from the table were compared with the New OPS values and

then the higher value is taken for remanent reservation.




Parameters

System Memory

RAM_512MB

RAM_1GB

RAM_2GB

Total Remanent Size (MB) 256000 512000 512000

Users 8000 12000 15000

Trunks 4000 8000 10000

Demi Com 6000 8000 10000

Table1: Defined Maximum Values

In the existing system, the “spadmin” with option 8 for “OPS Limits” displays only the “hardware.mao” file

content.

As a part of this feature, Modification done in “spadmin” with option 8 for “OPS Limits” to display both the

“hardware.mao” file content and the Maximum predefined values for the parameters like Total Remanent Size,

Users, Trunks and “Demi Coms”. Refer next Fig.




Fig 4: Display OPS Limits in spadmin

15.2.1.12 Multi-device: possibility to disable from OTCPC the main deskphone to ring/ ring

only selected devices

OpenTouch has implemented the multi-device feature for CT user.

The end-user has a NOE deskphone (either IP or TDM) registered as 'primary device'.

When acting as a remote worker, the end-user doesn't want to disturb the office colleagues: capability to

mute the deskphone ringing through CSTA services.

Feature: capability to remotely mute/unmute the deskphone ringing (i.e. the incoming call is always

presented on the deskphone’s screen but the device shall not/shall ring).

Targeted devices: NOE IP and NOE TDM

15.2.1.13 Need possibility to create profile for Desk Sharing User (crqms00202636)

New parameter 'Profile Type' having options 'Normal, Desk Sharing Set (DSS) & Desk Sharing User (DSU)' is

introduced in user menu. This parameter enables the customer to configure the user profile for desk sharing

user and desk sharing set. When a user is created as a user profile through mgr-> Users by selecting the field

'Set Function' as 'Profile' and validated, in the next screen provision is made to select the type of profile. Error

message while creation of normal DSS or DSU should be followed for user profile created with type of profile

DSS or DSU. A new user created through 'User by profile', is updated based on the type of profile selected.




15.2.1.14 Number of attendant 4059IP in a group with common services is limited to 20 -

ARQ (crqms00202657)

4059 IP / 4059 EE attendant displays the information about incoming calls on each screen of all attendant in

an attendant group at the same time. This display is based on parameter “No display Threshold on 4059 list”.

Currently the configurable range for this parameter is 1 to 20




Enhancement

Customer having more than 20 4059 IP attendant in a group and needs to have same level of display

information on each screen of all attendant at the same time. However currently the maximum threshold is 20

which is manageable via parameter “No display Threshold on 4059 list”.

Now the requirement is to increase maximum configurable threshold value to 50. If the group of attendant

include pc based attendant with type different than 4059IP or 4059EE the limit must be configured with 20.

Restrictions

This threshold must be managed to 20 or less for attendant group including "4058 (W95/WNT)

Migration" or "4059 MAC/BLF and Migration" attendant type

Configuration

Name of the parameter: “No display Threshold on 4059 list”

Parameter path: mgr->Attendant-> Attendants Group-> (Create) / (Review/Modify)

15.2.1.15 OXE Hunting Group: login logoff through CSTA

Without OXE CSTA development

No login state when starting the monitoring, so the login state displayed on OTC PC is “unknown” for the login or logout actions, OT must retrieve the login/logout OXE prefixes, and do a CSTA make call with

these prefixes. Doing a “make call” engages a call and user experience can be strange (typically in nomadic mode without auto answer, and once the call is answered it is immediately cleared)

Two developments on OXE CSTA

1. in private 4980, add the login state inside an escape service (values: logged in / logged out / not

applicable)

2. in private 4980, add two new services, HG login / HG logout, these services will do the login/logoff without call, so user experience will be good. For the result, CSTA events must be generated after




services execution (TBC what is the best these CSTA events, the same than we have when doing a make call with prefixes EVT_PRIVATE with Station State = 18/19/4)

15.2.1.16 Phone book access in Centrex Mode

The objective of this feature is to manage the phone book access with a dedicated parameter in phone feature

COS irrespective of the Centrex mode (private/common company) or existing phone feature COS.

When “Centrex Centralised Serv” is set to False (private company) and the “Inter-Company Calling Right”

(from Phone Facilities Categories) is set to True, user should be able to make calls to users of other companies

but accessing other company phonebook should be prohibited. But irrespective of the Centrex Centralised Serv option when Inter-Company Calling Right is set to True all the users on the phone book can be viewed (across

companies) which is to be restricted.

To control the access of the phonebook irrespective of the values set for Centrex Centralized Serv (company

mode) or Inter-company calling rights a new parameter is created in mgr. When this parameter set to 'True'

then the entire phone book (all entries across companies) is visible to the user. However, to call other

company user, the user requires 'inter-company calling rights' managed in the phone COS. If it is set to False

only local users is visible.

A new parameter “Intercompany phone book access” of type Boolean has been introduced in Phone COS

under the menu “Classes of service” with a default value “True”.

Parameter Details

Parameter: Inter company phone book access

Parameter path: mgr-> Classes of service -> phone features COS -> R/M -> All instances (below the

category “Rights”)

Values: True/False

Default Value: True




Fig1: Display of parameter “Inter company phone book access“

15.2.1.17 Possibility to disable dhcp survi on NOE/NOE-3G sets via MGR

Existing Behaviour

When DHCP Server is down, with DHCP survivability feature, NOE IP device do not release its IP address at

the expiry of its lease time and remain connected to CS if it is alive. But when the DHCP server is up again,

there is a chance of allocating the same IP to other device which results in IP conflict and DHCP server

blacklists the IP address.

Currently DHCP survivability is enabled by default in NOE IP devices. There is no management in OXE to

disable the DHCP Survivability.

Enhancement

To avoid the blacklist of IP address by the DHCP server a new Boolean parameter, “DHCP survivability" is

introduced in 8 & 9 Series NOE phone COS menu. This parameter is updated to NOE IP devices during its

initialization. The parameter identifier in SET PARAM REQUEST is 0x20 (DHCP survivability). Default value is

enabled. Change of this parameter requires reboot of IP sets.

Terminals with DHCP survivability disabled lose their IP when their lease time expires or reboot of terminal and

then terminal will go for continues reboot until the DHCP server is reachable. Once the DHCP server is

reachable, Terminals may get new IP and DHCP server can re-allocate the old IP to some other device.

A new parameter “DHCP survivability” of type boolean has been introduced in Phone COS under the menu

“Alcatel Lucent 8&9 series” with a default value “Yes”.




Note: Change of this parameter requires reboot of IP sets.

Parameter Name : DHCP survivability

Parameter path: mgr->Alcatel Lucent 8&9 series->8&9 COS->phone COS->R/M->All instance

Default Value : Yes

Fig 1: Display of new parameter “DHCP survivability” in English

15.2.1.18 Randomly the Automatic network callback facility is not working over ABC-F -

PER (crqms00186375)

This feature is to register 100 automatic network callbacks in a single CS. As per the existing behavior 50

callbacks can be registered in a single CS.

15.2.1.19 SNMP Counters for trunking

The objective of this feature is to get information about the trunk groups and its associated channels and

cumulative counters of the OXE which is been connected through MIB browser via SNMP.

The OXE MIB offers the following new data for the trunk group:

1. Trunk group ID

2. Trunk Group Name

3. Crystal Number 4. Coupler Number

5. Trunk Type




6. Node PBX 7. Number of available (Free) channels

8. Number of used (Busy) channels

9. Number of OOS Channels 10. Status of the trunk group (INS, OOS)

11. Cumulative Number of OOS Channels 12. Cumulative Number of Overrun (Failed Outgoing Calls when trunk is Busy/HS)

Supported Trunk Groups are,

1. ISDN (T0, T1, T2) 2. SIP

3. NDDI 4. ABCF

Each field of the trunk table holds a specific information of the trunk and a respective OID is mapped for the

same. Its type and description are explained below.

Trunk ID

Name : trunkid

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.1

Type : Integer

Description : Trunk Number as Found in MAO

Trunk Name

Name : trunkname

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.2

Type : String

Description : Name of the Trunk as Found in MAO

Crystal Number

Name : crystalnum

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.3

Type : Integer

Description : Crystal number as found in MAO

For the trunks which don’t have any physical address crystal number is mentioned as -1.

Coupler Number

Name : couplernum

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.4

Type : Integer

Description : Coupler number as found in MAO

For the trunks which don’t have any physical address coupler number is mentioned as -1.

Trunk Type

Name : trunktype

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.5

Type : String

Description : Type of the Trunk Group as Found in MAO

Node PBX




Name : nodepbx

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.6

Type : Integer

Description : Node Number where the Trunk Exists

Free Channels

Name : freechan

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.7

Type : Integer

Description : Current Available (Free) Channels for the given trunk

Busy Channels

Name : busychan

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.8

Type : Integer

Description : Current Busy (Used) Channels for the given trunk

Out Of Service Channels

Name : ooschan

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.9

Type : Integer

Description : Current Out Of Service Channels for the given trunk

Trunk Status

Name : trunkstatus

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.10

Type : Integer {OOS(0), INS(1)}

Description : Status of the Trunk Group

If the state is out of service the other counters about Trunk Group are inconsistent.

Cumulative OOS

Name : cumuloos

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.11

Type : Integer

Description : Cumulated Number of OOS Channels

Cumulative Overrun

Name : cumuloverrun

OID : .1.3.6.1.4.1.637.64.4400.1.9.1.12

Type : Integer

Description : Cumulated Number of failed outgoing calls (oos/hg)

MIB Description

+--alcatel(637) |

+--abs(64) |

+--a4400(4400)




| +-- -R-- INTEGER nodepbx(6) |

| +-- -R-- INTEGER freechan(7)

| +-- -R-- INTEGER busychan(8) | +-- -R-- INTEGER ooschan(9)

| +-- -R-- EnumVal trunkstatus(10) | Values: OOS(0),INS(1)

| +-- -R-- INTEGER cumuloos(11) | +-- -R-- INTEGER cumuloverrun(12)

15.2.1.20 Virtualized OXE license/key manual check possibility in SpAdmin

Existing Behaviour

When a new license is installed in OXE, it takes at least 4 hours to know the validity of installed license with

respect to the FlexLM server configured. If the new license installed in MAIN is invalid, then 0640 incident

occurs after 4 hours only (Ref [4]). There are no other possibilities to know the license validity within 4 hours.

Enhancement

In order to know the installed license validity at OXE’s startup and whenever needed, the following

enhancements are done:

- To allow the user to check the validity of OXE’s license file with FlexLM server(s) using spadmin tool.

- To trigger 0640 incident at OXE’s startup in the case of invalid license installation is detected

License validity check using spadmin tool

A new option “Check connection with FlexLM server” (option10) is introduced in the menu of spadmin. On

selecting this option, the validity of license installed in OXE with the FlexLM server is verified and the result is

shown on the spadmin tool. Please refer section 4.2.1.1 for the steps to check license validity using spadmin

tool.

Fig1: Check connection with FlexLM option in spadmin

The following output is shown in the spadmin tool if license installed in OXE is valid




Fig3: Output of spadmin for valid license

The following output is shown in the spadmin tool if license installed in OXE is invalid.

Fig4: Output of spadmin for invalid license

The following output is shown in the spadmin tool if FlexLM server is not reachable from OXE.

Fig5: Output of spadmin for FlexLM server not reachable

15.2.1.21 Voice Guide for internal call waiting on attendant/attendant group

This feature provides possibility to play a dynamic voice guide (like presentation guide) instead of ring back

tone for internal calls waiting on attendant/attendant group. The feature id is CROXE-4426 and the ARQ

ID/marketing id is RQOXE-277

Until OXE release R12.2, when an internal call (local/ network call) is placed to an attendant, a ring back tone

is played. From M3, a dynamic voice guide is played to the calling user based on the entity configuration of

the called attendant group/attendant/entity distribution. This feature is controlled by a new system option.

Dynamic voice guide configured in Entity is played to the internal users calling general attendant/attendant

group. New system option “Play VG for Internal Calls” is used to provide the dynamic voice guide.

Existing Behavior

Currently when the system option “Entity Call Guide No Answer” is set to true, if an External call is placed to a

busy attendant via entity overflow or entity prefix, then dynamic guide (attendant waiting guide) is played to

the calling user. But if an internal call is placed to a busy attendant, a ring back tone is played.

Enhancement

In this feature, a new system option “Play VG for Internal Calls” is introduced.

If this system option is set to true, when an internal call is placed to an attendant, a dynamic voice guide is

played to the calling user based on the entity configuration of the called attendant group/attendant/entity

distribution.

Same dynamic guide (attendant waiting guide) which was used in the external calls is reused in the internal

calls. Even the first internal caller to the attendant also hears the dynamic voice guide.

Parameter Path: mgr -> system -> D/H -> other system parameters ->DH ->Attendant Parameters ->Entity

Call Guide No Answer

Values : True/False

Default Value : False




Fig 1: Details of new system parameter “Play VG for Internal Caller” in English

15.2.1.22 Web RTC Gateway

Consult the web site https://support.openrainbow.com/hc/ + “TC2462 OXE Configuration Guide for Rainbow

PBX Integration”

15.2.2 CCD

15.2.2.1 New sets as ProACD

Support of Dect as Pro-ACD phone

“Remote Agent on CMP board” application allows ACD agents inside an enterprise using any OmniPCX

Enterprise phone not supported by Contact Centre like DECT, to handle CCD and RSI distributed calls.

Because the CMP board is being phased out and will not be produced anymore, an alternative solution

needs to be made available to provide the same features i.e. allowing use of any phone types as ACD

agent for inside enterprise configurations.

To solve the problem of ACD agents inside an enterprise, the solution is to allow ACD agents to log on

DECT phone.

To allow an ACD agent to log on a DECT, it is mandatory, in MAO, to set the user parameter “ACD

station” to “ACD authorized phone set” for DECT.

https://support.openrainbow.com/hc/




Restrictions:

• DECT ACD agent is always mono-line, even if it is a managed multiline set.

• Only the first 10 programmable keys are available.

• Only the first 42 repertory keys are available

• ACD supervisor is not authorized to log on a remote extension.

mgr / Users

• A GAP Enhanced with parameter “ACD station” set to “ACD authorized phone set”, here called

“DECT Pro-ACD”, allows log-on of ACD agents of type 4037 and IP Touch 4068.

• Mobiles (200/300/400) Reflexes, Mobiles (8212/8232/8242/8262) are supported

Support of 8018 as Pro-ACD phone

Support of 8028/29 as PRO-ACD phone

Support of 8008 as PRO-ACD phone

15.2.2.2 OTCC: Increase the number of Statistics Pilots per OXE CS

Number of Statistics Pilots is increased from 1000 to 3000

15.2.2.3 CCD product limits summary

Before R11.1 From R11.1 From R12.2

Routing Pilots 200 600 -

Pilot Routing Directions 20 30 -

Queues 200 600 -

Queue Distribution Directions 30 50 -




Processing Groups 150 450 -

Calendar Timeslots Managed

by CCS/AFE

6 10 -

Expected Waiting Time 200 600 -

Primary Rules 400 1200 -

Emergency Closure Lists 10 50 -

Statistics Pilots 1000 - 3000

managed agents 5000 - 7000

Logged agents 2000 - 2800

15.2.3 Dect

15.2.3.1 New dect ip solution with new base stations 8378 (xBS)

IP-xBS is a DECT mobility solution with base stations connected via the IP network and clock synchronized

over the air.

This new base station offers extension and migration solutions for installed base. It takes place in DECT

infrastructure strategy for a mid-term solution to replace our current TDM offer.

The ALE A-GAP stimuli protocol is transported transparently to / from the DECT handsets. From the user point

of view there is exactly the same level of service as with the DECT handsets under the legacy TDM RBS/IBS

base station coverage.

The IP-xBS base stations are synchronized together over the air. They are also able to synchronize with IBS

base stations over the air. The synchronization is managed by the IP-xBS sub-system.

The IP-xBS sub-system is responsible for managing connection handovers between Ip-xBS. Support of mixity

(IP-xBS/RBS, IP-xBS/IBS) is addressed by External Handover (EHO). The IP-xBS base stations are

geographically grouped and EHO generating audio glitches are limited as much as possible. Support of mixity

(IP-xBS/IP-DECT) is addressed by roaming only. No handover is supported with IP-DECT. In addition, only A-

GAP handsets can be used on both IP-DECT and IP-xBS/TDM systems.

Recomm

endation

&

warning

It is recommended to have a syslog server for debug purpose: logs from that server must be sent to Tech.

Support/ RnD. Management of the feature is done entirely from the oxe side (syslog server address, level of

debug per station)

Management should NOT be done through the Web Based Management of the xBS stations unless advised

by the ALE support or RnD.

FEATURES AVAILABILITY MD2 patch brings new features. See chap.3.2.8

Following features to be released in a further step: - SUOTA




- Campus - Auto-registration

EXTERNAL SYNCHRONIZATION recommendations - master AND backup master is mandatory - master AND backup master are able to see external source RPN - master AND backup master are able to see another base station from external sync PARI.

These are mandatory conditions not to lose external sync.

FIRMWARE COMPATIBILITES (auto-registration feature)

Minimum versions to use the feature. Those firmware are available at the business portal.

• 8212 – v0012b0002 • 8232 – v4383b0004

• 8242 – v6382b0003

• 8262 – v5681b0006

• 8262Ex – v7682b0006

AUTO-REGISTRATION (future patch) A DECT system is identified by a PARI number. For an OXE node, up to 16 PARI may be defined. Moreover, a

handset installed on an OXE may access to DECT systems (PARI) declared on another node of the OXE network. At installation, a handset is granted with access right to some of this PARIs, using a PARI (common

for all allowed PARIs) and a PLI (mask on this PARI). This could be done using the PARK, but PARI is used, to allow activation of “home preference” in case of campus. These indications are either automatically computed

by the command “dectinston” (base on some configuration rules), either forced by the installer.

A new way to call this tool is designed. In this mode, indication of PARI and PLI is mandatory, as long as a list of handsets to re-register. When called, the PBX suggest the handset to start a registration procedure. During

this procedure, the new identifiers (PARI, PLI) are sent to the handset that updates its internal data. The tool displays the result or registration update on the console. No indication is displayed on the handset during the

procedure: it is seamless for the handset’s user.

“dectinston” is a command-line tool used to update re-registration of dect handset. This mode is activated by

using “-update” or “-forceUpdate” option. In this mode, only following parameters are relevant: * <directory number list> single directory number, or -f <file>, where “file” contains the list of directory

numbers to update. * “-pari”: the new PARI attributed to the handset

* “-pli”: the new PLI attributed to the handset

When “-f <input_file>” option is used, the input file contains one directory number per line. A line beginning with “#” followed by a space delimiter is considered as a comment and is not taken into account.

Two output files are generated as follows: 1. “ReinstallSuccessHandsetsList.txt” - contains list of handsets for which Auto re-registration is successful.

2. “ReinstallNOKHandsetsList.txt” – contains list of handsets for which Auto re-registration has failed.

These output files are saved in the same path as the input file. When dectinston tool is relaunched with new set of handset list, the new successful handsets will be appended to the output file

“ReinstallSuccessHandsetsList.txt”. A handset may appear several times in “ReinstallSuccessHandsetsList.txt” if it has been reinstalled several times. Make a note that “ReinstallNOKHandsetsList.txt” should be renamed

before launching the command next time for “unsuccessful handsets”. This allow to easily retry the operation

for handsets that failed, without building a new list. For every directory number given in parameter, the tool initiates the procedures towards the telephonic

application based on “-update” or “forceUpdate” respectively. The latest activates the DECT Mobility




Management layer to manage the DECT access-rights procedure. At the end of the procedure, the telephonic application notifies the result to the tool.

Important point: this result is the view of the FP DECT MM layer. It does not guaranty that the handset took

the new parameter into account. The tool displays this result on the standard output. In case of failure, a more specific indication is given of the

reason of the failure (handset in conversation/busy, unreachable, in roaming, …) The procedure is not initiated for a handset when it has an established link, to avoid call cut. In this case, a

message is displayed to indicate that update of installation parameters is not done. On the phone side, once the procedure is started, no outgoing call can be placed. Any attempt of CC

establishment is refused by the call server.

In case of failure, the handset keeps its previous installation parameters.

GENERAL TECHNICAL INFORMATION The IP-xBS solution is comprised of IP-DECT xBS base stations connected to OXE Call Server thru the IP LAN.

There is no IP Multicast, only Unicast in the exchanges between IP-xBS and OXE Call Server.

Once connected to the LAN, IP-xBSs start up and are discovered by OXE Call Server in the same manner as NOE IP phones (see document [4]).

➢ Connection to DHCP server for IP configuration when in dynamic mode (default). Static IP configuration, including TFTP address, when in static mode (configuration via IP-xBS web

interface).

➢ Connection to TFTP server (OXE call server). ➢ Connection to OXE Call Server with UA / UDP for configuration and signaling (see document [5]).

The IP-xBS base station is able to manage 12 DECT radio slots, with 11 slots usable for communications. The IP-xBS base stations are clock synchronized together over the air. They are also able to clock synchronize

with TDM IBS base stations over the air. The clock synchronization is managed by the IP-xBS subsystem. ➢ The DECT Network layer is running in the Call Server, it uses an UA / UDP / IP socket (legacy

protocol) as the configuration and signaling link with the Call Server. This DECT network layer is

shared with the TDM IBS DECT base stations solution. ➢ Connection handover is not possible between IP-xBS and TDM RBS/IBS infrastructure.

➢ The media stream (RTP) may be direct between an IP set or trunk and an IP-xBS base station. The subscription of the DECT handsets is managed by the Call Server with mgr in the same manner as with

TDM IBS. In case of mix of both IP-xBS and TDM IBS, the subscription may be done thru either an IP-xBS or a

TDM IBS base station. The subscribed handsets can be used either on IP-xBS or TDM IBS subsystems. The IP-xBS acts as a DECT / UA / UDP / IP bridge.

Data exchanged between the base station and the Call Server are encapsulated in UA messages over UDP.




As for TDM IBS, DECT Network layer (Call Control, Mobility Management) is managed by the Call Server while

Physical layer, MAC layer and DLC layer are managed by the base station. This allows for end to end signaling

with the DECT handset without protocol translation.

IP-xBS base station web interface

Each IP-xBS provides a web interface over HTTPS.

The web interface is enabled by default.

Access is protected by a password that is defined by the Call Server during the initialization of the base

station. The password is common to all IP-xBS base stations.

Password is not sent in clear: Call Server sends a hash of the password + a secret shared with the base

stations. A signature is added to the command to validate the change of the password.

Configuration Procedure:

PWT/DECT System

Parameter Values Purpose

Radio base type RBS/IBS - IP-xBS/Mixed Radio base station type.

Frequency plan European/Latam/China/US

(default European)

IP-xBS is able to handle

several frequency plans.

This setting indicates which

one must be used by default

on the system.

Setting may be different for

specific clusters




Flag External Handover Yes/No (default No) There is already such a flag in

RBS system. But it must be

common for all base stations.

- It must not be created

for ip-xBS

It must be moved from RBS

System to DECT/PWT System

IP-xBS System


Number of Pari 0-7 Number of PARI declared for

using IP-xBS

Registration node 0-n (n being the number of

nodes in the network) or ??

when registration is not

authorized on any node?

Show the node of the network

used for registration

Registration authorized True/false (default false) Authorize/block automatic

registration of new IP-xBS.

Can be set to True only in one

node of a network.

- avoid installation of

unwanted equipments

- allow installer to change

following field before installing

new base stations.

See detailed behavior of this

parameter below

Default PARI for registration 0-7 (depending on the

number of PARI declared), or

255 for auto

PARI to affect to registering

base stations.

If set to auto, the first PARI,

where RPN values are

available is affected, among

those configured on the

system




Default location area for

registration

0-253 (depending on the

number of location areas

defined in PARI), or 255 for

auto.

Affects a RPN to this base

station, so that it is placed in

the configured area location. If

auto is set, first free RPN is

used.

If auto is set for default PARI,

then auto also applies for this

parameter.

Base station busy trigger 0-12 (default 8) Used by performance

management. This attribute

defines the maximum number

of simultaneous

communications on a base

station. Past this number, the

busy counter of this base

station is incremented.

Slots reserved for emergency True/False (default false) When set, slots are reserved

on base station for emergency

calls.

Management

Allow IP-xBS Web Based

Management

True/False (default True) When true, it is possible to

connect to the WBM of IP-xBS

base stations.

IP-xBS WBM engineer

password

String not shown (default

“Engineer00!”)

Change the password of the

the engineer account for the

IP-xBS web based

management. Empty string

suppresses the password.

IP-xBS WBM admin password String not shown (default

“Admin00!”)

Change the password of the

the admin account for the IP-

xBS web based management.

Empty string suppresses the

password.

SYSLOG IP address IP address/None (default

None)

IP address of a syslog server.

May be OXE embedded syslog

server, or an external one.

SYSLOG port 0-65536 (default 514) Port used on the syslog server

IP-xBS parameters

xBS objects must be provisioned for every base station to be installed in the system.





Terminal Ethernet address Mac address of the IP-xBS

IP addr Mode Ipv4/ipv6 (display only) IP version of address returned

by IP-xBS

IP address (read-only) IP address of IP-xBS

Location name String Give a human-understandable

name to the base station to

help the installer recognizing

the IP-xBS.

e.g.:

Building_A_Floor_3_BS_45

Site Number 0-??? Site identifier this BS belongs

to

PARI Number

0-7, depending on number of

PARI declared.

Filled using information in Site

Number, without possibility to

modify it

shortcut to real PARI identifier,

31-bit long

Location area 0-128 depending on the

number of areas declared

RPN 0-255 identifies a base station for a

given PARI.

This value is allocated

automatically in the range

related to location area.

If modified, it must be a free

value, and must be in the

same location area.

Sync Cluster Mask

Internally, it is a bit field : one

bit per cluster.

In mgr, it could be something

like

Sync cluster n : True/False for

all 8 clusters.

A cluster is a group of base

station that cannot

synchronize with other base

stations then the ones

belonging to the same cluster.

This is usefull for some

topologies to avoir unexpected

synchronization links, and to

construct “backbones” of

synchronization.

A base station may belong up

to 8 clusters. By default it

belongs to cluster 0. Cluster

definition is limited to a Site




Alien synchronization master 0: disabled (default)

When enabled, this base

station is candidate to be root

of a synchronization tree for

its site. To be enabled, PARI

and RPN must be filled in

related Site object.

Antenna diversity (default

yes),

Yes/no (default yes) The base allows the set to

transmit and receive on either

of the DECT set's 2 antennae

according to its position. This

avoids smothering the signal

by reflection.

NO: desirable, perhaps even

imperative position with

certain antennae for example,

uni-directional).

IP Address IP address of the IP-xBS

(display only)

IP Domain Number IP Domain of the IP-xBS

(display only)

Base in noisy audio

environment

Yes/no (default no) This function is used when

there are high levels of

ambient noise (such as in an

engineering workshop, etc.) It

prevents the ambient noise

from weakening the voice

reception of the remote

correspondent on DECT sets.

RF power setting 0 -24 (default 24) Nominal transmitted RF power

(0 – 24dBm)

Syslog level One of the following :

- Syslog off (default)

- Normal operation

- System Analyze - Debug

Level of syslog information

that will be logged.




PARI


PARI value Octet string of length 0 up to

11 Within the following range

'0'to'7'

Pari Value (Primary Access

Right Identifier);

This number gives the identity

of PWT/DECT installation

(given by the manufacturer

Note:This number of 11

characters Represents 11

bytes; that is why each

character ranges from 0 to

7.This Number must be filled

obligatorily when PWT/DECT

sets are registered.

All PARI must all be different,

and also different from the

ones configured for IBS or

RBS.

Area type One of the following values:

1 area of 256 xBS (0)

2 areas of 128 xBS (1)








identifies a base station for a

given PARI

Site

A site is a group of base stations able to communicate together using IP connection. This is mainly useful to

configure branch offices and avoid IP traffic between base stations through a low performance network.

A site can only handle one PARI so large headquarters may be composed of several sites without functional

impact.

Each branch office is a dedicated site. By default, only one site is created, and all base stations belong to it.


Site Number 0-?




Site Name String Give a human-understandable

name to the site.

e.g.: Headquarter, Branch

Office Illkirch, …

PARI Number 0-7 Defines the PARI this site

handled. This is usefull to

check consistency of Site and

PARI when configuring base

stations

Alien Sync PARI type RBS/IBS/xBS/none If none is selected, no base

station in this site will use

alien synchronisation

Alien Sync PARI Pari number. 0-7 if Alien Sync

PARI type is RBS or xBS, 0 if it

is IBS

Alien bases(s) station(s) is

(are) a synchronization source

for this cluster. This is the

PARI of alien base(s)

station(s)

Alien Sync RPN 0-255 (1-254 in case PARI

type is xBS)

RPN number of the base

station used for alien

synchronization

Max levels in sync tree 0-24 (default 24) Limits the maximum of level in

a synchronization. A constraint

is that the maximum number

of hops in a synchronization

tree should not exceed 24.

Due to alien synchronization, it

may be usefull to limit the size

of the tree in every site, so

that the global chain of

synchronization does not

exceed 24 hops.

Frequency plan European/Latam/China/US

(default: same value as the

one configured in IP-xBS

system)

IP-xBS is able to handle

several frequency plans.

This setting is used to override

system-wide value for specific

clusters

Provisioning level

Up to 8 different PARI, 254 base stations per PARI

Up to 11 simultaneous radio connections can be managed per IP-xBS base station

New incidents

See with command “incinfo” for further details on each incident




6070, INC_XBS_GENERIC_ANOMALY

6071, INC_XBS_SELF_TEST_ERROR

6072, INC_XBS_INTERNAL_ANO

6073, INC_XBS_KO

6074, INC_XBS_OK -> when a dect station xBS comes in service. Gives also the firmware version

6075, INC_XBS_WRONG_RADIO_TYPE

6076, INC_XBS_ILLEGAL_COMMAND

6077, INC_XBS_PRIMARY_LOSS

6078, INC_XBS_MASTER_LOSS

6079, INC_XBS_EXTERNAL_SYNC_SOURCE_LOSS

6080, INC_XBS_REGISTERED

6081, INC_XBS_EXTERNAL_SYNC_WRONG_CFG

6082, INC_XBS_EXTERNAL_SYNC_STATE

6083, INC_XBS_EXTERNAL_SYNC_RESTART

6084, INC_XBS_TOO_MANY_SUBTREES

6085, INC_XBS_AIR_SYNC_STATUS

6086, INC_XBS_REGISTRATION_ENABLE

15.2.3.2 Long press on "green call button" to get in to "call log menu" (in 8242, 8262, 8232

DECT sets)

With the introduction of this feature, more direct access to the user call log is achieved. Instead of accessing

the call log via the icon in the main menu page, the user can access it via long press on the “Off hook key‟

(green call button) of the set.

As mentioned above, there are already two functionalities defined for long press on green call button under

the phone features COS parameter “DECT: redial list via long press”. Hence for this feature, one more

functionality is introduced under this parameter to open call log via long press.

15.2.4 Hospitality

15.2.4.1 Display name and room for guest calls on administrative sets with small displays

(MD1)

The objective of this feature is to display the name or number in sets with small display (like 8008, 8018,

8028s and 8058s with Virtual AOM) during conversation state through toggle key.

Existing Behavior

When call arrives on administrative Sets with small display (like 8008, 8018, 8028s and 8058s with Virtual

AOM), due to limitation of screen size, the Display information about the caller is truncated in CS. Thus, end

user gets only name and not the number.

Enhancement

With this enhancement, during conversation state, an option of switching (toggle) the display between name

and number is provided with help of “OK” (APPLY) key.




In hotel configuration, toggling can be done between guest name and room number or guest number based

on the Multi Occupancy Type parameter set in management

15.2.4.2 Increase the number of simultaneous wake-up calls (crqms00209045)

See chap. 15.2.5.2

15.2.5 Increasing provisioning level

15.2.5.1 Increase the limits for OXE max number for incoming greeting guides

The objective of this feature is to increase the max number of incoming greeting guides from 255 to 1000

Existing behavior

Incoming Call Greeting Guide Prefix allows an incoming caller to hear a greeting guide before it is routed to a

pre-configured destination configured using Incoming Greeting Guides. The routing destinations could be a

set, a hunting group (PBX or ACD), or an attendant group.

Each Incoming Greeting Guides can have three sets of voice guides configuration and overflow directory

number. In case a problem occurs on the called set or hunting group, the former routing is replaced by a

second one, or a third one if the problem occurs again.

Enhancement

After R12.2, it is possible to create from 0 up to 999 Incoming Greeting Guides.

This incoming greeting guides will be linked to the Incoming Call Greeting Guide Prefix, which will be dialed

from external. Increasing the creation of Incoming Greeting Guides from 255 to 1000. So we can configure

from 0 up to 999 Incoming Greeting Guides.

15.2.5.2 Increase the number of simultaneous wake-up calls

In this feature “Increase the number of simultaneous wake-up calls”, from 80 to 320 per second.

Today, the OXE can only make 80 wake-ups per minutes.

The evolution is: in R12.2, (M3.xxx) OXE can make 320 wake-ups per minutes, in 4 bursts of 80.

This evolution is not available if a voice mail is used in step 2 on the wake-up sequence

In this case, we have configured in “System / local option / wake up guide option” = 0

Compressors needed:

To have proper wake-up on IP set, we need to be able to hear the voice guide message broadcasted when

the set takes the wake-up call, so, a compressor is needed, so the number of free compressors has to be

controlled. Also, all the free compressors cannot be used by wake-up feature… let’s say 90%.

320 wakes-up per minute using 90% of the free compressors,

320/0,9 = 356 compressors are needed => 360 compressors

360 compressors are needed to allow a wake-up rate of 320 wake-up per minute on one CS




15.2.5.3 Number of attendant 4059IP in a group with common services is increased to 50

Currently the maximum threshold is 20 which is manageable via parameter “No display Threshold on 4059

list”. Now version has increased maximum configurable threshold value to 50. If the group of attendant

include pc based attendant with type different than 4059IP or 4059EE the limit must be configured with 20.

15.2.5.4 Total number of declared & connected Call center agents per OXE CS to increase

Number of managed agents is increased from 5000 to 7000

Number of simultaneously logged agent is increased from 2000 to 2800

15.2.6 Infra

15.2.6.1 Oxe MS + OST64 with Suse SP3 (MD1)

From new version of OXE MS 8.01 the OS is upgraded to Suse SP3.

No new functionality.

It is mandatory at MD1 patch to re-install ALL OXE-MS otherwise the OMS will not go into service. No

possibility to make it work other than re-installing with the right bootDVD + OMS.

That OMS can be installed on a release lower than the MD1 patch: no downgrade will be done & the OMS will

be operational as before.

Same update for the OST64 ipv6 translator: minimum version 4.02 with Suse SP3. In that version, the

protection for downgrade is not put yet.

15.2.6.2 Save Restore operations of OXE data on network

This feature allows the users to save their backups of data on a network periodically and lets them restore the

saved data from the network when needed.

To perform the periodic backup operation on network, the user can go into the swinst (swinst --> expert menu --> Backup and restore operations -->Periodic backup operations).

A new choice “Periodic save on network” is added.

Periodic backup on network will be registered only if the server allows host based authentication without

password like immediate save on network. FQDN is not supported. Either host name or IP address of the remote server can be specified. (Hostname to

be added in OXE /etc/host list).

The user is asked to enter the name of the server, name of the account and complete path + base file name where the data should be saved.

At the time of registration, the reachability of the server is checked. If the server is reachable and the user name and the path of the remote file is valid a message is printed that the server is reachable otherwise a

message is displayed telling that the server is not reachable and also the backup operation is not registered. The base file name provided by the user will be prepended to the backup name.

Now an optimum time between 0AM-6AM for taking the periodic backup is suggested by scanning crontabs

files and proposed to the operator.

If the OXE is down during the registered backup time, backup on network will be performed only at the next scheduled time and no incidents will be thrown.




Daily mechanism

Once the backup operation on network is registered, the backup files will be stored in the below format and

order. The files are saved in the format, <name of base file_day of backup>. On network, the backups (cho-dat, mao-dat) will be stored in the specified path under the following

directories: OXE_DAY, OXE_DAY-1, OXE_DAY-2, OXE_DAY-3, OXE_DAY-4, OXE_DAY-5, OXE_DAY-6, OXE_WEEK-1, OXE_WEEK-2, OXE_WEEK-3, OXE_MONTH-1.

A max of 11 backup files is retained.

Assuming that the user programs a periodic backup on network on Sunday afternoon of April 5th then, the first backup will be performed on Monday morning.

The following chart shows how the day of this first backup will be move from DAY to MONTH1.

DAY

DAY

–

1

DAY

–

2

DAY

–3

DAY

–

4

DAY

–

5

DAY

–

6

WEEK

–

1

WEEK

–

2

WEEK

–3

MONTH

–1

Apr,6 mon

tue mon

wed tue mon

thu wed tue mon

fri thu wed tue mon

sat fri thu wed tue mon

sun sat fri thu wed tue mon

Apr,13 mon sun sat fri thu wed tue mon

mon

sun sat fri thu wed tue mon mon

Apr,20 mon sun sat fri thu wed tue mon mon

mon mon




sun sat fri thu wed tue mon mon mon

Apr,27 mon sun sat fri thu wed tue mon mon mon

mon mon mon

sun sat fri thu wed tue mon mon mon mon

May,4 MON sun sat fri thu wed tue mon mon mon mon

The files are saved in the same format as in periodic backup on cpu disk.

If the name of remote file was OXE then the result names will be:

OXE_Day

OXE_Day–1

OXE_Day-2

OXE_Day-3

OXE_Day-4

OXE_Day-5

OXE_Day-6

OXE_Week-1

OXE_Week-2

OXE_Week-3

OXE_Month-1

15.2.6.3 SSD disks are now provided with CPU8 & CS-3.

Nothing specific about installation.

15.2.6.4 Generic Appliance Server (G.A.S.)

Appliance servers are no more proposed as integrated oxe system.

Instead there is now a solution based on a Suse hosting KVM as replacement. No dongle is needed: Flex

server is embedded in the Suse OS. The Cloud solution is also possible.

It will be possible to order an ALE pre-defined server or get a server from a reseller at the correct conditions

(pre-requisites to have compatibility between Suse version & the server).

For the second solution, some BIOS modifications should probably be done especially if the server has RAID.




15.2.6.5 Software Orchestration Tool

This new external tool (S.O.T.) is now replacing either ALEDS & PC Installer.

Some features in PC Installer are still not taken into account by S.O.T. (future versions). “old” cpus & versions

are not tested by S.O.T. & may not be compatible (installation issues). For that, PC Installer is still needed in

some cases (like cpu reload …).

15.2.7 Management

15.2.7.1 WBM mass provisioning

Mass Provisioning Export Template and Import (Part 1)

WBM support two format: .prg and .txt for both Export and Import.

➢ “. prg” files use a tab character as the column delimiter and the headers are in non-translated format.

➢ “.txt” files use a tab character as the column delimiter.

Mass Provisioning part1 contains the following:

Export Template of Users

• Select Users model in treeview, click on the Export Button from top menu bar, then select the

format using the format selection dialog.

• Once the administrator clicks ok, then the exported template file gets downloaded in the downloads folder with the filename OXEWBM_timestamp.

• Exported template will have the headers of the Users model. Once exported template file is

available the administrator must add the appropriate data required for the mass provisioning

operation.

Export format selection dialog is shown in below figure

Import of Users

• Import of Users will support only creation.

• Select Users model in tree view.

• Click on the Import Button from top menu bar, then the file dialog will get opened to select the file.

• WBM supports “.prg” and “.txt” files.

• When importing, If the administrator attempted to select any other file format, error popup

gets displayed with the message “Unsupported file format”.

• In WBM R1801, Importing of User done in two steps: ▪ After successful import, all entries from the imported file created as unsaved entries.




▪ Then the administrator can click on the “Save All” button to save all the unsaved entries in WBM application.

Mass Provisioning Export Data and Import (Part 2)

Mass Provisioning ExportData

• Select Users model in tree, click on the Export Button from top menu bar, then select the format using the format selection dialog.

• Once the format is selected, then the administrator can select the subclasses to export using

the subclasses export dialog. By default, the main class will be checked.

• Once the administrator clicks ok, then the exported data file gets downloaded in the downloads folder with the filename OXEWBM_timestamp.

• Exported data will have the headers and data of all users in the Users model. Once exported

data file is available the administrator can modify the existing users or they can create the new users.

• File content contains the following:

➢ 1st Column will have the Action as the header and its value will be + for Creation, #

for modification and – for deletion. By default, the Action with # is present. ➢ 2nd Column will have the Subscriber as the header and its value will be the Directory

number of the selected user. ➢ The exported data will use the tab character as the column delimiter if the data file

suffix is. prg but the headers are in non-translated format and will use the tab

character as the column delimiter if the data file suffix is .txt. ➢ The exported file will have the sequence attribute header as sequence attribute

parent name / child and its value will be the child value. ➢ For example: Tandem is the sequence attribute and it will have set of attributes as

{Tandem Directory Number 1002, Main set in the Tandem: true, Partial Busy:

false,…}. Here the exported file header will have Tandem/Tandem Directory Number and its value will be 1002.

➢ Selected subclasses data will get exported in the same manner.

Subclasses export dialog shown below:




Mass Provisioning Import

• Import of Users will support creation/modification/deletion.

• Select Users model in tree, click on the Import Button from top menu bar, then the file dialog

will get opened to select the file.

• If the selected file contains the subclasses data, then the administrator can select the subclasses to import using Subclasses Import Dialog.

• WBM supports. prg and .txt files.

• When importing, If the administrator attempted to select any other file format, error popup

gets displayed with the message “Unsupported file format”.

• In WBM R17.09, Importing of User done as single step: o After successful import, all the entries from imported file gets created and saved directly.

o For creation/modification/deletion of any entry, administrator should specify +/#/-

respectively in the Action column. Data for creation needs to be supplied by the administrator to perform the mass provisioning.

Exception Processing

During the processing of imported file, a record found to be in error will be rejected and errors will be logged

and the processing will continue with the next record in the file.




15.2.8 Noe sets

15.2.8.1 Summary of noe 3GEE from version 5.30.13

Native Encryption: DTLS

Partial Native encryption

DTLS serviceability

NOE IPv6 (Dual mode, pure mode)

Possibility to disable dhcp survivability on NOE 3G/NOE-3G EE sets via MGR

8008 in EE family

Configurable Virtual AOM display

8058s replace 8038 on old systems

About in local menu

Change Default Hostname

Serviceability - Log - USB key

Release skin (Arcturus)

Update and Merge DeskPhones User Guide & Installation Guide in a single document.

VPN: Mode IKEV1 Aggressive mode, IKEV2+EAP+MSChapV2 (not released in that .13.x OXE patch)

15.2.8.2 Support of 8058s in "8068s without bluetooth" mode and in "8028 mode"IP

Enhancement

Use new tool “forcenoe » to switch the sets display from 8058s to 8068s. Otherwise the switch can be

done by the IM if the set. Set will reboot 2 times.

15.2.8.3 8008, 8018, 8028s, 8058s, 8068s, 8078s deskphones IPv6 support

IPv6 is supported from M3 (R12.2) for those phones.

New OST64 4.02 with associated OS Suse SP3 is mandatory.

15.2.8.4 Filtering activation when Boss' PC with softphone is in standby mode, power off

The problem with the existing behavior is that the filtering activation by the assistant set using the filtering

supervision key is not allowed when the manager set is OOS.

NOTE: A Manager-Assistant configuration can operate within a network. This means that the manager can be

located on one node while the assistant is located on another node. In this case, the filtering activation by the

assistant using filtering supervision key is allowed.

The objective of this feature is to allow an assistant to activate or deactivate manager set filtering even when

the manager set is out of service.

15.2.9 O2G

The OmniPCX Open Gateway (O2G) is a standalone application providing Open Web Services on top of OXE

communication platforms. This gateway simplifies the vertical integration and development of customer centric

services from third party partners or end-customers.




It provides a unique set of REST full APIs covering Telephony, Management and Analytics domains.

It is also a universal Openness server which can host your /ALE applications (executing business rules / logic)

thanks to a built-in DOCKER engine.

Software based and designed for mission critical environments (HA, Secured by design, CPE deployment, 1

single server for all your OXE network).

Finally, it supports multiple Licensing models from perpetual license, to vendor specific agreement (TOKEN

/revenue sharing) or consumption-based licenses in OpEx (analytics).

15.2.10 OT

Compatibility with new OT R14 (with OXE R12.2 MD1)

15.2.11 Rainbow

Web RTC Gateway readiness.

15.2.12 Security

15.2.12.1 Audit tool to assess OXE/OT security (more features in MD1 patch)

A new OXE integrated tool is now present.

At present, there is no tool to provide all the security information as output. The proposal is to provide a new

tool (securitystatustool) to display all security information as output in a XML format.

The tool must be able to run without telephonic application running, in this case only system and installation

parameters will be returned as output from the tool.

When telephonic application is running, all information is available.

Information to be displayed in XML format:

➢ Software version of OXE ➢ SSH configuration and SSL certificate details

➢ Isolation / trusted hosts information ➢ Radius server configurations

➢ SNMPv3 details

➢ NTP server information ➢ Syslog server details

➢ System account details ➢ DISA details

➢ Manual set lock and secret code information

➢ 4645 Voicemail details

Example of output (extract)

Trusted Hosts and TCP Wrapper

The following fields are provided to identify the trusted hosts in OXE.

<IsolateEthernetInterface > <Enabled>Yes</Enabled>

<TrustedHosts> <Host>

<Name>router</Name>




<Address>172.19.109.88></Address> <GatewayName>localhost</GatewayName >

<HostType>Router</HostType>

</Host> </TrustedHosts>

</IsolateEthernetInterface >

15.2.12.2 FNSE (Full Native Software Encryption)

The current OXE Security solution is based on hardware and software modules. It delivers IPsec and SRTP

encryption for LAN devices using the NOE/IPLINK proprietary protocols. SIP-TLS encryption is supported for Public SIP Trunking. Though it is field proven one with technology & performance, it has some major

limitations too. Some of them described below: * It is not suited for virtualized deployments

* It does not support certificate based authentication

* It has obsolete TLS implementation with no support for latest crypto libraries and protocols such as SHA2/TLS 1.2

* IPsec used for LAN encryption is not compatible with End to End encryption with remote devices.

To overcome the limitations of the current solution, Full Software Native Encryption solution (FSNE) is

proposed. FSNE is a software-based solution for signaling and media encryption within ALE PBX solutions. It

complements the existing IPT Security solution by bringing in easy to deploy and low-cost encryption

capabilities, initially for small to mid-sized OXE deployments.

The major objectives of the solution are:

* Support encryption natively inside OXE (Full Software).

* Work on application level DTLS Technology instead of IPsec.

* State of the art authentication based on certificates, with an option for mutual authentication.

* Provide support for easy deployment mode (plug and play)

* Design Openness, to support interoperability with existing IPT security solution in later steps.

* Provide native support for SRTP based media encryption by using Native SRTP Key generator.

In FSNE, signaling encryption is achieved through exchange of NOE/IPLINK protocol messages over DTLS

while media encryption is achieved through SRTP. Media keys for ALE proprietary devices are conveyed

through signaling, similar to what is done for IP Touch security solution. CS and endpoints software are

delivered with DTLS encryption capability and activation of this feature is managed through a system

configuration parameter and a software license.

15.2.12.3 FNSE: customized certificates

Native encryption is using certificate based authentication.

The standard way is to use a server certificate generated automatically by OXE at installation

Some demanding customers having their own PKI, will not use auto generated but a certificate from their PKI.

In case of MTLS, OXE has to trust customized client certificates in IP phones.

15.2.12.4 FNSE: partial native encryption

OXE has been fully encrypted once enabled the Native Encryption parameter and able to manage up to 1500

FSNE supported IP devices. To overcome the limitations of the current solution, a new user option “Native




Encryption” is introduced in OXE to enable/disable encryption per user. This option allows enabling encryption

only for limited set of users. This enables OXE to protect the conversation between the “Native Encryption”

option enabled users.

This user option is applicable only for sets which supports native encryption, from R12.2 (MD1) release OXE

checks this user option parameter on each IP set connection.

* When IP set connects in clear mode,

* When IP set connects in encrypted mode.

A new parameter “Native Encryption” is added in the path “mgr ->Users”, for the following set types –8008,

8018, 8028s, 8058s, 8068s, 8078s which supports Native Encryption.

In FSNE system,

* For already existing NOE3GEE sets the “Native Encryption” option is set to Enable.

* For others sets the default value remains Disable.

Note: The system will go to panic mode, if there are more number of NOE3GEE sets with “Native Encryption”

enabled in the node, than the number allowed by the lock 424 “Native Encryption”. So administrator needs to

ensure that the lock 424 value must be greater than or equal to the number of sets currently supporting

native encryption.

In FSNE, the default value for “Native Encryption” Option is “Disable”.

Description: this parameter “Native Encryption” is introduced in OXE to facilitate the DTLS supporting users to

enable/disable encryption as per requirement. This allows activating encryption for only a limited number of

VIP users whose conversations between must be protected.

Note: This parameter can be enabled only if the system option “Enable Native Encryption” is set to True.

Otherwise the error message “The system option “Enable Native Encryption” must be set to True would be

thrown.

15.2.12.5 FNSE with PCS

PCS support for FSNE is added for M3 MD1. It enables GD3, INTIP3B, NOE3GEE, 8008, 8018 sets to be

rescued in DTLS encrypted mode when the IP link with the Call Server fails. The protection of these IP

elements only lasts for a limited period (30 days), at the end of this period the PCS services will be blocked on

all the equipment.




15.2.12.6 SHA-2 support for Thales V5M

Thales V5M boxes: only 2048 bits rsa key is supported for customized certificates in SSM

15.2.12.7 Virtual Management outbound for virtualized host (MD1)

The main requirement is to support multi-homed IP configuration; three different and dedicated IP

interfaces instead of the current solution of just one. The resulting network topology logically consists of the service, storage, and management planes, which are isolated from each other, preventing some

technical and security issues via Out-of-Band management.

" Out-of-Band management" is defined as any management done over channels and interfaces that are separate from those used for user/customer data. Examples would include a serial console interface or a network interface connected to a dedicated management network that is not used to carry customer traffic.” OXE shall restrict the reachability of services so that they can only be reached on interfaces where their usage

is required. On interfaces were services are active, the reachability should be limited to legitimate communication peers.

This limitation shall be realized on the oxe product itself (without measures (e.g. firewall) at network side).

Basic Description

In a « Standard deployment », OXE is installed using only one interface ‘eth0’ and existing documentation and

procedures apply.

In a « Multiple IP interface deployment » inside a Data-Center, each vNIC provided to an OXE VM in Multi-IP

development implies that in addition to the Ethernet device “eth0”, OXE might have two or three interfaces:

“eth0”, “eth1” and “eth2”.




In a « Multiple IP interface deployment » on a bare-metal server, each physical NIC are mapped to one, two

or three interfaces: “eth0”, “eth1” and “eth2”.

15.2.13 Serviceability/maintenance

New infocollect 5.4

- Adding dect ip xBS tools & oxe logs

New version of “tnet” tool

15.2.14 Sip terminals

15.2.14.1 8008 SIP business mode support

To support 8008 set in SIP mode as a business phone.

15.2.14.2 8008 SIP business mode support (firmware NOE 3G EE R400)

15.2.15 SIP Trunking features

15.2.15.1 TDM public carrier network phase out anticipation: DTMF In Band Support on OXE

/ carrier Public SIP Trunking connection (MD1)

RTP flow contains the VOICE and DTMF digits:

in “RFC 4733 DTMF mode”

DTMF digits are encapsulated within a dedicated DTMF packets. Voice packets and DTMF packets are

distinct.

in “In-Band DTMF mode”

DTMF digits are encapsulated within a voice packet. No difference between “VOICE” and “DTMF”

packets.

Currently, the RFC 4733 DTMF mode is supported.

This new feature (PEROXE-57 / CROXE-5017) responds to two needs:

In-Band DTMF mode for SIP external gateway.

In-Band DTMF mode for specific analog set.

Needed

This “In-Band DTMF” mode is applied if all the following conditions are met:

Domains configuration should allow G711.

• “IP compression type” attribute of “trunk group” used for VPN hop should be equal to G711 (useful for IP network call)

• “IP compression type” attribute of “VPN Overflow” on each node should be equal to G711 (useful

for IP network call)

• Analog type attribute of analog set is In-Band DTMF. • List of received codecs (from SIP carrier) should contain G711.

• A VOIP resource is available.

In-Band DTMF mode for analog set: this feature should be installed in each node in which In-band analog

set(s) and sip trunks are declared.




Management

A new SIP external gateway parameter “In Band DTMF” is created

Path: mgr-> SIP→ External Gateways: In Band DTMF

A new value “In Band DTMF” is added to “Analog type” attribute for an analog set. (This attribute does not

exist for no analog set)

Restrictions

• Due to non-availability of InBand digit detection inside OMS, the VOIP resources (compressors)

allocation privileges GDx/INTIPx couplers. If the VOIP resources are only available on OMS and if the local user is EVA or 4645 Automated attandant or automatic DISA, the call is refused.

• For an outgoing call if the SDP are present in 18x and 200 OK messages, the DTMF mode is chosen

according of the SDP of 200OK message.

• In conversation state, for any received RE-INVITE (Send and Receive) that indicates a DTMF mode change is refused by answering successful OK with the DTMF mode of the current call.

• In Band is incompatible with SIPTLS-SRTP encryption (In Band should not be configured if SIPTLS-

SRTP encryption is enabled). • analog set used as emergency set inside elevator, the “In-Band DTMF” mode is insured for a direct

call but NOT insured for call evolution like hold, enquiry call, transfer …

For an Incoming SIP carrier call in case of INVITE without SDP, if the DTMF mode of SIP gateway is

RFC 4733, the call is refused if in SDP of ACK message received from carrier, the indicated DTMF mode

is In-Band

15.2.16 Voice mails

15.2.16.1 4645: simple answering mode only

No system option required. The behavior of the way 4645 has changed:

When 4645 is in extended absence greeting

• in case the user has not recorded a greeting, we continue playing the system prompt

• in case the user has recorded a greeting, we do not play the system voice prompt after the greeting

message.

15.3 List of features brought in MD1 patch

Below is the list of features that arrived along the patches from the TR patch until the MD1

8008, 8018, 8028s, 8058s, 8068s, 8078s deskphones IPv6 support M3.402.13.c

RQOXE-308: Filtering activation when Boss' PC with softphone is in standby mode, power

off

M3.402.15.c

RQOXE-309: Display name and room for guest calls on administrative sets with small

displays

M3.402.15.c

Virtual Management Outbound for virtualized host M3.402.17.c

DECT set should be seen as available during "busy" states M3.402.17.c




Call log for IPDSP when OOS M3.402.17.c

Upgrade of Suse sles 12 sp1 to sp3 M3.402.17.c

New BIOS for M6 M3.402.17.c

TDM public carrier network phase out anticipation: DTMF In Band Support on OXE / OTBE

Public SIP Trunking connection - Analog device (and not for SIP external gateway).

M3.402.19.d

Partial native encryption M3.402.19.d

Hyper-V (with restriction) M3.402.19.d

Audit tool to assess OXE/OT security (adding new checks) M3.402.19.d

Backup-restore service M3.402.19.d

SIP business 8088s Video (8088 R302) M3.402.21.a

Native encryption PCS M3.402.21.a

15.4 Features under PCS

No features in PCS mode.

16 OXE COMPONENTS

Following is the list of all components with their corresponding version.

It is also possible to consult the “read.me” file included in every static & dynamic patch to find this king of

information. Do a text search with the binary name requested. One read.me file contains all the precedent

patches.

For instance:

- For the dynamic patch: read.me file of patch .A will contain all data from patch .A No information

related to static patches.

- For the static patch: read.me file of patch .34 will contain all data from patch .1 to .34

Below is the content of deliveries

Binaries

Version 12.2 MD7

Version 12.2 MD8

Version 12.2 MD9

Version 12.2 MD10

Version 12.2 MD11

Version 12.2 MD12

M3.402.29 M3.402.30 M3.402.31 M3.402.32 M3.402.33 M3.402.34

System binaries

bios CPU6 Step2 3BA24095AAAB0

8_4.8 3BA24095AAAB0

8_4.8 3BA24095AAAB0

8_4.8 3BA24095AAAB0

8_4.8 3BA24095AAAB0

8_4.8 3BA24095AAAB0

8_4.8

bios CPU7

3.02 replaced by bios CPU7

Step2


Step2


Step2


Step2


Step2


Step2

bios CPU7 Step2 3BA24115AAFC1

9_4.3 3BA24115AAFC1

9_4.3 3BA24115AAFC1

9_4.3 3BA24115AAFC1

9_4.3 3BA24115AAFC1

9_4.3 3BA24115AAFC1

9_4.3

bios CS 10.14 10.14 10.14 10.14 10.14 10.14




bios GD 10.14 10.14 10.14 10.14 10.14 10.14

bios CS-2 (ami)

3EU24009AAAC0

1_12.0

3EU24009AAAC0

1_12.0

3EU24009AAAC0

1_12.0

3EU24009AAAC0

1_12.0

3EU24009AAAC0

1_12.0

3EU24009AAAC0

1_12.0

firmware_CPU8 1.5 1.5 1.5 1.5 1.5 1.5

io1n 16 16 16 16 16 16

io2 4.6 4.6 4.6 4.6 4.6 4.6

io2n 5.17 5.17 5.17 5.17 5.17 5.17

linux 123.028 123.028 123.030 123.031 123.031 123.033

ramdisk_patch 123.000.003 123.000.005 123.000.005 123.000.006 123.000.006 123.000.006

rainbowagent 3.0.14 3.0.14 3.0.14 3.0.14 3.0.14 3.0.14

obca 1.5 1.5 1.5 1.5 1.5 1.5

pc_install 5.6 5.6 5.6 5.6 5.6 5.6

swinst 3.42.0 3.44.0 3.44.0 3.46.0 3.50.0 3.53.0

DECT binaries

dect8 1.26 1.26 1.26 1.26 1.26 1.26

rbsng 53.00 53.00 53.00 53.00 53.00 53.00

ibs_appli_ng 53.02 53.02 53.02 53.02 53.02 53.02

ibs_boot_ng 71 71 71 71 71 71

IPxBS 64.0016 64.0016 65.0006 65.0006 65.0008 66.0002

Compression Boards binaries

bootintip 6.13 6.13 6.13 6.13 6.13 6.13

binintip_appli 16.25 16.25 16.25 16.25 16.25 16.25

bindspintip 4.37.2 4.37.2 4.37.2 4.37.2 4.37.2 4.37.2

bindspintip2 3.45 3.45 3.45 3.45 3.45 3.45

mg_appli 46.27 46.27 46.27 46.27 46.27 46.27

binmcv 3.9.0 3.9.0 3.9.0 3.9.0 3.9.0 3.9.0

binmcv2 3.45 3.45 3.45 3.45 3.45 3.45

ioip 4.19 4.19 4.19 4.19 4.19 4.19

lio_comp2 3.40 3.40 3.40 3.40 3.40 3.40

rlio_comp2 3.27 3.27 3.27 3.27 3.27 3.27

dsp_lio_comp2 3.09 3.09 3.09 3.09 3.09 3.09

r_mg3 4.01, replaced

by ngp 4.01, replaced





by ngp

r_intip3 4.01, replaced






by ngp

r_ngp3 9.19 9.19 9.20 9.20 9.20 10.08




binamcvb642x n.a. n.a. n.a. n.a. n.a. n.a.

oms 8.05 (Suse SP3) 8.05 (Suse SP3) 8.05 (Suse SP3) 8.05 (Suse SP3) 8.05 (Suse SP3) 8.05 (Suse SP3)

ost64 4.03 (Suse SP3) 4.03 (Suse SP3) 4.03 (Suse SP3) 4.03 (Suse SP3) 4.03 (Suse SP3) 4.03 (Suse SP3)

egw 1.15 1.15 1.15 1.15 1.15 1.15

Sets binaries

noeip 4.33.81 4.33.81 4.33.81 4.33.81 4.33.81 4.33.81

noeip Gigabit 4.34.21 4.34.21 4.34.21 4.34.21 4.34.21 4.34.21

noe3gip 4.53.20 4.53.21 4.53.21 4.53.22 4.53.22 4.53.22

noe80x8S 5.40.20 5.40.30 5.40.40 5.40.40 5.40.40 5.40.40

noe8018 5.40.20 5.40.30 5.40.40 5.40.40 5.40.40 5.40.40

noe8008 5.40.20 5.40.30 5.40.40 5.40.40 5.40.40 5.40.40

noe8082 4.51.03 4.51.03 4.51.03 4.51.03 4.51.03 4.51.03

noe8088 5.05.21 5.05.21 5.05.21 5.05.21 5.05.21 5.05.43

noe3guax9 4.11.32 4.11.32 4.11.32 4.11.32 4.11.32 4.11.32

noeuax9 3.81.80 3.81.80 3.81.80 3.81.80 3.81.80 3.81.80

noeua19 3.81.00 3.81.00 3.81.00 3.81.00 3.81.00 3.81.00

noesip 2.12.40 2.12.40 2.12.40 2.12.40 2.12.40 2.12.40

noe3gsip 3.00.50 3.00.50 3.00.50 3.00.50 3.00.50 3.00.50

sip80x8S 1.51.03 1.51.03 1.51.03 1.51.03 1.51.03 1.51.03

sip8018 1.51.03 1.51.03 1.51.03 1.51.03 1.51.03 1.51.03

sip8008 1.51.03 1.51.03 1.51.03 1.51.03 1.51.03 1.51.03

jpn_4068 1.00.01 1.00.01 1.00.01 1.00.01 1.00.01 1.00.01

jpn_40x8 1.00.00 1.00.00 1.00.00 1.00.00 1.00.00 1.00.00

jpn_40x9 1.00.01 1.00.01 1.00.01 1.00.01 1.00.01 1.00.01

kor_4068 2.01.00 2.01.00 2.01.00 2.01.00 2.01.00 2.01.00

kor_40x8 2.01.00 2.01.00 2.01.00 2.01.00 2.01.00 2.01.00

kor_40x9 2.01.00 2.01.00 2.01.00 2.01.00 2.01.00 2.01.00

chi_4068 2.01.00 2.01.00 2.01.00 2.01.00 2.01.00 2.01.00

chi_40x8 2.01.01 2.01.01 2.01.01 2.01.01 2.01.01 2.01.01

chi_40x9 2.01.01 2.01.01 2.01.01 2.01.01 2.01.01 2.01.01

ipphone 2.31 2.31 2.31 2.31 2.31 2.31

tscip 5.2 5.2 5.2 5.2 5.2 5.2

tscipvS 3.0 3.0 3.0 3.0 3.0 3.0

VoWLAN sets binaries

noemipt_r2 109.025 109.025 109.025 109.025 109.025 109.025




noemipt_r3 120.028 120.028 120.028 120.028 120.028 120.028

noemipt8_r100 6.0.8 6.0.8 6.1.2 6.1.2 6.1.2 6.1.2

Secured binaries

noeip 4.38.81 4.38.81 4.38.81 4.38.81 4.38.81 4.38.81

noeip Gigabit 4.39.21 4.39.21 4.39.21 4.39.21 4.39.21 4.39.21

noe3gip 4.58.20 4.58.21 4.58.21 4.58.22 4.58.22 4.58.22

noe80x8S (same) 5.40.20 5.40.30 5.40.40 5.40.40 5.40.40 5.40.40

noe8018 5.40.20 5.40.30 5.40.40 5.40.40 5.40.40 5.40.40

noe8008 5.40.20 5.40.30 5.40.40 5.40.40 5.40.40 5.40.40

SM modules (Thales) - V4 (bin_SM) - V5 (bin_SM2) - V5M (bin_SM3)

4.1.03: 3.3.05 3.6.03 4.1.03

4.1.03: 3.3.05 3.6.03 4.1.03

4.1.03: 3.3.05 3.6.03 4.1.03

4.1.03: 3.3.05 3.6.03 4.1.03

4.1.03: 3.3.05 3.6.03 4.1.03

4.1.03: 3.3.05 3.6.03 4.1.03

mg_appli 46.77 46.77 46.77 46.77 46.77 46.77

Thales library (mg_appli) 1.1.02 1.1.02 1.1.02 1.1.02 1.1.02 1.1.02

mg3 4.51, replaced






by ngp

intip3 4.51, replaced






by ngp

ngp3 9.69 9.69 9.70 9.70 10.07 10.08

Thales SRTP client (intip3/mg3) 1.0.06 1.0.06 1.0.06 1.0.06 1.0.06 1.0.06

Thales VPN client (intip3/mg3) 1.1.03 1.1.03 1.1.03 1.1.03 1.1.03 1.1.03

Boards binaries

brapra 2.06 2.06 2.06 2.06 2.06 2.06

c1nvgpa2 3.4 3.4 3.4 3.4 3.4 3.4

c1nvua 5 5 5 5 5 5

c1nvz32 3.13 3.13 3.13 3.13 3.13 3.13

cpl2dpnss 1.11 1.11 1.11 1.11 1.11 1.11

dpnss_v2 2.3 2.3 2.3 2.3 2.3 2.3

dpnss_nv 2.3 2.3 2.3 2.3 2.3 2.3

dpt1-2 2.05 2.05 2.05 2.05 2.05 2.05

dsp_emtl_24021 3.01 3.01 3.01 3.01 3.01 3.01

dsp_gpa 2.01 2.01 2.01 2.01 2.01 2.01




dsp_vgu 1.5 1.5 1.5 1.5 1.5 1.5

dsp0Z32 1.05 1.05 1.05 1.05 1.05 1.05

dsp1nddi2 2.01 2.01 2.01 2.01 2.01 2.01

gpa2tns 1.11 1.11 1.11 1.11 1.11 1.11

gpa 2.24 2.24 2.24 2.24 2.24 2.24

int2_rt2 2.20 2.20 2.20 2.20 2.20 2.20

intof 1.25 1.25 1.25 1.25 1.25 1.25

intofsync 1.05 1.05 1.05 1.05 1.05 1.05

intof2 3.4 3.5 3.5 3.5 3.5 3.5

ivrZ24 2 2 2 2 2 2

lia 4.18 4.18 4.18 4.18 4.18 4.18

lioebbc2 3.05 3.05 3.05 3.05 3.05 3.05

lio 3.25 3.25 3.25 3.25 3.25 3.25

mic2 2.31 2.31 2.31 2.31 2.31 2.31

nddi 2.5 2.5 2.5 2.5 2.5 2.5

nddi_in 2.7 2.7 2.7 2.7 2.7 2.7

nddi2 2.25 2.25 2.25 2.25 2.25 2.25

nprae 2.06 2.06 2.06 2.06 2.06 2.06

pcm2_ru 1.6 1.6 1.6 1.6 1.6 1.6

pra 2.06 2.06 2.06 2.06 2.06 2.06

pra2 2.26 2.26 2.26 2.26 2.26 2.26

rma 3.04.04 3.04.04 3.04.04 3.04.04 3.04.04 3.04.04

tonesnv 2.19 2.19 2.19 2.19 2.19 2.19

ua 13.9 13.9 13.9 13.9 13.9 13.9

uasim 8.14 8.14 8.14 8.14 8.14 8.14

Attendants binaries

fbc 2.13 2.13 2.13 2.13 2.13 2.13

mapac2 2.01 2.01 2.01 2.01 2.01 2.01

Binaries related to 4760i

wbmappli 1202.1809 1202.1810 1202.1810 1202.1810 1202.1811 1202.1812

17 COUNTRIES IN WHICH RELEASE 12.2 IS TECHNICALLY RELEASED

OmniPCX Enterprise Release 12.2 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.2

Market System Software to be used

Market

Code Market Country name

Installation initial to be

used

Bdd ISO Country code

Reminder

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 DE Azerbaijan ru SU AZ

17 Bahamas BS

18 FL Bahrain bh BH BH

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

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

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 YUGOSLAV REPUBLIC OF

pl PL 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

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

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

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

18 REMARKS & RESTRICTIONS

18.1 RESTRICTIONS, KNOWN ISSUES

Some old information was removed. Consult document from release 11.2 if needed.

18.1.1 Restrictions

18.1.1.1 Hyper-V

Hyper-V virtualization will be released in a further step

18.1.1.2 8088 Noe/ Android

No desksharing in ABC network.

18.1.1.3 Dect ip xBS

Feature is released with following restrictions:

- VAD (Voice Activity Detection) does not work correctly in case of DECT Encryption




- SUOTA (Software Upgrade On the Air of dect sets)

- Auto-registration (dect sets needs a minimum firmware version. See chap. 15.2.3.1)

▪ Do not validate the SUOTA feature until it is released in a patch: leave the value to “No”

▪ Path : mgr->PWT/DECT System->C/R:Allow auto FW update of sets + NO

- Campus (ibs, rbs)

- If a base station was already installed on an oxe node & is transported to be installed on another node

of the same network a factory reset has to be done (manual long push on a dedicated button). This

reset factory can be done on any case where the update of the xBS takes too long time.

- Dect xBS when more than 255 xBS on the same location (under PCS process)

Those restrictions will come in a further OXE patch

18.1.1.4 FSNE

No support for 4645 Voicemail

No IPv6 Support

No support for SIPTLS implementation

No compatibility with Thales installed server

No support for GD, GD2 and IOIP3 boards

No VPN support (Set movement via network is impossible)

18.1.1.5 G.A.S. (Generic Appliance Server)

Post-installation does NOT set the virtual machine auto start after reboot. This must be done manually

(management to do in KVM manager).

To reboot the whole server, it is mandatory to stop FIRST the OXE (“shutdown -h now”) and then stop or

restart the server through Suse.

If the server is not ordered through ALE, check the compatibilities (cross comp. document, Suse & KVM

compatibilities in Suse web site).

A Raid server can be used if correct management is performed at bios level.

18.1.1.6 Virtualized attendants

CROXE-5216: at CPU switching all com are lost and 4059 is unplugged.

This issue also occurs with physical PC and is not linked to virtualization. If there is no other type of attendant

(meaning all attendants are virtual) in the group public external call cannot be recovered.

18.1.1.7 Sip

In Band DTMF is incompatible with SIPTLS-SRTP encryption. In Band should not be configured if SIPTLS-

SRTP encryption is enabled.




18.1.2 Misc information, Other issues

▪ Configuration with Thales Encryption: move of noe sets internode fails. Fixed in a further firmware

version.

▪ Dect ip xBS: Web Based Management

Account “engineer” should only be used to view information. Parameters are pushed from the OXE

and there is no need to do any management directly on the xBS itself.

Modifying those parameters directly on the WBM is strongly NOT recommended

▪ PC Installer error message:




This error has no impact and is fixed by installing PC Installer version 5.4 present from static patch .13

▪ Encryption/ FNSE:

Command to print CTL on OXE:

“openssl crl2pkcs7 -nocrl -certfile /etc/pki/oxe/truststore/trustchain.pem | openssl pkcs7 -print_certs -

text -noout”

Transform pem/crt -> p12:

“openssl pkcs12 -export -nokeys -in xxx.pem -out xxx.p12”

In case of mutual authentication, certificates of type client for GD3/INTIP3/OMS

In case of mutual authentication, certificates of type client for the sets as well.

▪ “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

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

• Hard disk: recommendations on ALE cpus: 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).

• Esx virtualisation: Memory should be lower than 4Gb. VM will not start if 1 or both managements are

applied.

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

• 8088 noe/ Android sets: use the “bugreport” tool as described in Technical communications

(TC2347en-Ed04 - Technical Release Notes For 8088 R301 Smart Deskphone) in case of bug to report

to technical report. Result will be asked.

• Case of GD/OMS new board or installation: it may take several reboots of the boards to load all the

voice guides into that board. Once they are all & completely loaded that process will not start again.

Check the incidents to know how many guides are loaded & if it the download is finished.

Example of messages thrown during the 1rst startup:

02/10/18 17:42:02 001010M|004/27/-/---|=4:0260=Beginning of downloading

/DHS3ext/vgadpcm/flash/std/vgadpcm.FR1

02/10/18 17:43:18 001010M|004/27/-/---|=5:0261=End of downloading

/DHS3ext/vgadpcm/flash/std/vgadpcm.FR1

02/10/18 17:43:19 001010M|004/27/-/---|=4:0260=Beginning of downloading

/DHS3ext/vgadpcm/flash/std/vgadpcm.IT1

02/10/18 17:44:59 001010M|004/27/-/---|=5:0261=End of downloading

/DHS3ext/vgadpcm/flash/std/vgadpcm.IT1

• Important: It is prohibited to install any other NAOS (RPM packages or pure binary) than

those provided by ALE OXE.

18.1.3 KVM

OXE installation with PC Installer requires a user input to give a directory during Linux installation.

After having installed the OXE vm needs to be set in autostart.

https://businessportal2.alcatel-lucent.com/8AL90617USAA




18.1.4 Other virtualized systems

• Known as unsupported virtualization systems at the moment:

o XEN (implies also Amazon)

o Microsoft Hyper-V (MD1 patch but restriction due to QoS issue). Installation ONLY through

S.O.T. tool (NOK in PC Installer).

18.2 COMMUNICATION SERVERS

18.2.1 Call Server CPU

− Direct connectivity of the Ethernet port of the CS-2/3 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.

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

18.2.3 Blade Center & older CPUs

− Blade Servers are no more compatible as well as other CPUs mentioned in this document

− ACTIS behaviour




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

18.2.4 Passive Communication Server

Updating PCS from version <12.0: disk reformatting is mandatory & needs to be considered before migration.

Installation must be done locally (see also chap. 10.2)

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 must register again as the Call Server registrar 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:

OmniTouch Contact Center : CCD/CCS/CCA/CCIVR

XML Web services

Application "XML IP Touch"

TSAPI

ACAPI

VoWLAN R2.0

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

18.2.5 Appliance Servers/ G.A.S. & Bill Of Material (BOM)

BOM of Appliance Servers is no more provided in this document. If needed, check with previous Release Note

(OXE R12.1)

Appliance Servers are no more sold in that form. Replacement is done through the Generic Appliance Server

(G.A.S.) based on existing platforms 3BA27582CDAC (LENOVO X3250-M6) and 3BA27704CEAB (HP DL20 G9)

Note Notice that in case of migration the ordered server is no more delivered with the software integrated.

If a server is already in an installed OXE version it is possible to migrate to oxe R12.2 (e.g.: a G9 server in

oxe R12.1 wants to migrate to oxe R12.2 This operation will be performed through the inactive partition)

Note Notice: G.A.S. should be upgraded like the appliance servers where before. When a server is received from

factory, administrators should look for the most advanced OXE version to put at the right level of software.

Servers delivered with version “.12.E” should be updated to this patch. This is mandatory.

18.3 VIRTUALIZATION

In OXE up to R12.2:

Hyper-V is available for lab only (QoS restriction – documentation & fix to come later).

Not compatible with Amazon Cloud (Xen)

ESXi 6.5 is compatible.

18.3.1 CONFIGURATION

This is a reminder of main configurations. Check the virtualization guide (Business Portal) & TC2431

(Virtualization: Configuration of OXE following releases and ESXi infra version) for more details & provisioning

level.

- 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 & SCSI disks are validated

- OS:

Linux / Other linux 32 bits or Centos 4/5/6 32 bits.




- Network card:

E1000 or VMXnet3 (preferred & chosen automatically with S.O.T. ovf)

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

18.3.2 SUMMARY ON COMPONENTS NEEDED FOR INSTALLATION

tool to install on

VMWARE

tool to install on

KVM How to install misc

OXE PC Installer v4.1 PC Installer v4.1

OMS ALEDS 3.4.0.2 mini ALEDS 3.4.0.2 mini

on vmware : web client

needs to have a vCenter

for Suse 12 selection

vmware 6.0 won't need that

*OS is now on Suse 12

*bootdvd.12.0.000.01

3.x86_64.iso or upper

64bit image

*OXE-MS core image

file : oms-

4.00-IP0001.iso or

upper

OST64 ALEDS 3.4.0.2 mini ALEDS 3.4.0.2 mini

on vmware <5.5 : web

client needs to have a

vCenter for Suse 12

selection

vmware 6.0 does not need

that OS is now on Suse 12

FLEX Server

vmware installation

method

kvm installation

method ovf deployement

*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

<5.5

Raspberry

(PI3+ not

compatible) NA NA

Win32 Disk Imager

(on "Sourceforge") to write

on SD card

*tool not present in

ALE Portal.

*OS "ipdongle-firm-

1.0.000.000.img" is

present on the Portal





18.4 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

maximum.




18.5 MEDIA GATEWAY

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

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

18.5.3 Remote connection towards GD/GA/INTIP boards

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

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.

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

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

daughter board

Compressors N-way conferences Voice Guide

access

3-way conf DTMF

receivers

GD-3 mix No 15

1x7, 2x7, 3x7, 4x7 or

1x15, 2x15 or 1x30 16 24 30

No 30 0 16 24 30

Yes 45 1x7, 2x7, 3x7, 4x7 or

1x15, 2x15 or 1x30 16 24 30

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

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

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

• 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

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




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




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

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




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




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.

18.9 OTHER SETS

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

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

18.9.3 Alcatel series 8 & 9 sets

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

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 Password xxxx




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.




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

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

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

the OmniAccess WirelessLAN infrastructure. If there is a mixing of MIPT 300&600 and MIPT 310&610

handsets, a SVP Server must be used.

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

18.9.7 IP DECT system (NEC)

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

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

18.9.8 UA Extender 4051/4052

The use of UA Extender 4051/4052 is not available through IP.

18.9.9 NOE3G (premium ip phones)

From L2 TR version (patch .20.e) the firmware is R100 which is NOT compatible with ipv6.

18.9.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: TC2308 Technical Release Notes For 8028S, 8058S, 8068S, 8078S 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

▪ Group listening deactivated






▪ External IP recording (internal recording is OK )

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

18.10 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 considers 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.

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

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

18.12 APPLICATIONS

18.12.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/ save-restore: both applications are removed from the system. 4760i and replaced by the Web Based

Management tool described further in the document. No equivalent for “Save/restore”

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

18.12.3 AAS (Audio Station)

Warning On secured sites (by ssh) the copy of the guides is not working anymore from OXE R12.0 Use a manual




copy by using an ssh client program.

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

18.13 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 …

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

• 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




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

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

18.15 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 any more to give LDAP parameters, such tool uses 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

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.

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

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

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 another 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,

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:

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

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

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.




19 CORRECTED DEFAULTS

19.1 M3.402.34 R12.2 MD12

List of all fixes:

ISSUE KEY MAIN CR PRIORITY HOW FOUND SUMMARY

CROXE-16908 CROXE-16908 Major endUser_customerSite

Randomly users are unable to make outgoing calls and receive incoming calls

CROXES-24661 CROXES-24661 Major validation_funcManual

OXE/M3 :Back trace observed when a multi-line set is forwarded to analog(Virtual) set in pre-production nodes

CROXES-23685 CROXES-23685 Minor endUser_customerSite

SIP SBC incoming greeting guide are not heard when broadcasted by INTIP3 behind MSM or with Soft MSM// 00436376// m3.402.26.a

CROXES-24118 CROXES-24118 Major endUser_customerSite ISDN ARS problem doesn’t take the second route

CROXE-17086 CROXE-17086 Minor endUser_customerSite RSI : Enquiry call to withdrawn agent not possible


Same RE-Invite scenario works fine with UA set but fails in case of analog set

CROXE-16649 CROXE-16649 Minor endUser_customerSite

Waiting Guide is missing for the external caller from the Remote Node Trunk


SIP - UPDATE following PRACK sent in loop by OXE in SIP-TLS/SRTP context


//1893F_LSY_RR//New GCID not created during a MakeCall when agent in Pause

CROXES-23350 CROXES-23350 Major endUser_customerSite

When user are disconnected we don't have the busy tone. We are still in ringing on caller side.

CROXES-24759 CROXES-24759 Major validation_funcManual OXE/M3: In WBM phone book filter is not working


Rainbowagent: Segmentation violation after configuration action on OXE


Trunk Supervision calls using R1.5 trunk is NOK//00414000//

https://jira.ale-international.com/browse/CROXE-16908


https://jira.ale-international.com/browse/CROXES-24661



























List of all reports:


CROXES-24584 CROXES-23446 Major endUser_customerSite [Report] : //1893F_LSY_RR//Backtrace générée

triple exception sur équipement

CROXES-24798 CROXES-24747 Major None [Report] : Removal of CROXES-24214 and CROXES-24523

CROXE-17766 CROXE-15255 Major endUser_customerSite [Report] : Analog sets are not ringing if CLIP is activated

CROXE-17769 CROXE-17630 Major software

[Report] : OXE N1-Enhance dynamic patch installation: Unary operator expected error occurs while loading dynamic patch without TEL binaries in a node with hotfix already installed

CROXE-17770 CROXE-17626 Major software [Report] : OXE N1-Enhance dynamic patch installation:Issue in sorting the highest dynamic patch

CROXE-17863 CROXE-17726 Major validation_nonRegression [Report] : M5:Error observed during remote mode installation of patch m52046b

CROXE-17540 CROXE-17170 Major endUser_customerSite [Report] : Open2Gateway lot of OXE incident 2676

CROXES-24879 CROXES-24707 Major validation_funcManual [Report] : OXE/M4 : Filter not working in progr keys in wbm

CROXES-24789 CROXES-24321 Major endUser_customerSite [Report] : [Related] : Atrium#00455861 // Cannot link user to PBX

CROXE-16498 CROXE-15678 Major endUser_alpha [Report] : Alpha nu11 : loss service Tel rainbow during 15mn after bascul in M5.200.4.a

CROXES-24765 CROXES-23981 Major endUser_customerSite [Report] : SIP trunk license problem

CROXES-24815 CROXES-24610 Major endUser_customerSite [Report] : Random GD3 reboot issue with reboot reason 16 and backtrace.

CROXES-24814 CROXES-24638 Major None [Report] : Report of CROXES-24448 in NGP component

CROXES-24816 CROXES-24152 Major endUser_customerSite [Report] InBand DTMF is not working with analog phones

CROXE-17705 CROXE-16832 Major validation_funcManual [Report] : M5 : HyperV2019 -sysstat log not started in OXE

CROXES-24880 CROXES-24535 Major endUser_customerSite [Report] : OXE // Problem to restore linux data / "A netadmin process is already running .... (pid xxx) . Stop."

CROXES-24868 CROXES-24376 Major endUser_customerSite [Report] : Call Center applications ar eno more compatible with OXE in secure mode SSH-2






































List of all duplicates:


CROXES-24493 CROXE-17157 Major validation_funcManual OXE/M3 : Backtrace is observed when Multi device is configured with it's own number

19.2 M3.402.33 R12.2 MD11

List of all fixes:


CROXES-23253 CROXES-23253 Minor endUser_customerSite //1893_LSY//8088 Phone On Hook Button Red and not working CROXES-23453 CROXES-23453 Major endUser_customerSite License control for G729. CROXES-22623 CROXES-22623 Major endUser_customerSite No way communication when UPDATE with sendonly received

CROXE-17077 CROXE-17077 Minor endUser_customerSite Impossible to perform Immediate Forward on target DSU OOS/Logged-Off with previous customized Immediate Forward.

CROXE-15551 CROXE-15551 Major endUser_customerSite No voice connection when call from SIP ext.GW to CCD Agent.

CROXE-14121 CROXE-14121 Major endUser_customerSite Lost the bluethooth connexion with DECT when Enquiry call is selected

CROXES-23529 CROXES-23529 Major endUser_customerSite OXE dect 8242 set no notification

CROXES-24485 CROXES-24485 Major software_analysisTool Array 'payloads_recu' of size 6 may use index value(s) 6..7 // KW ID 58246.58235 // SIP

CROXES-23869 CROXES-23869 Major endUser_customerSite Following migration to R12.2 and a bascul, DECT are froze -older Case 00409603 -

CROXES-23382 CROXES-23382 Major endUser_customerSite Fax Fallback T38 to G711 not working in OXE

CROXE-16148 CROXE-16148 Minor endUser_customerSite Want to know the limitation of managing the Backup IP address on ip domains//00438733//

CROXES-18258 CROXES-18258 Minor endUser_customerSite Lock SP 328 issue when restore new OPS files on Customer Site with duplication

CROXE-16114 CROXE-16114 Minor endUser_customerSite Issue with GAP+ handset, when using AOCR on outbound calls//00437912//

CROXES-23098 CROXES-23098 Minor endUser_customerSite Issue with remote extension CROXES-24483 CROXES-24483 Major software_analysisTool Null pointer may be dereferenced // KW ID 58243// CCx

CROXES-21432 CROXES-21432 Minor endUser_customerSite When PCS is in INACTIVE* mode, xBS don't remain attached to the PCS

CROXE-15029 CROXE-15029 Major endUser_customerSite Barring does not work if incoming SIP ISDN is transferred out by SIP ABCF VM.

CROXES-24357 CROXES-24357 Minor endUser_customerSite REINVITE including PAI fail (OXE replies 502 after 15s) - Same REINVITE with no PAI succeed (OXE replies 200ok)

CROXES-24528 CROXES-24528 Major validation_funcManual OXE:M3// Double call log entry in dect user for trunk incoming-unanswered calls












































List of all Reports:


CROXE-17033 CROXE-16147 Major endUser_customerSite [Report] : GD3 rebooted with the bactrace : * CPL *Backtrace: 0xD24C7C9C NIP _ZN9EventMngr16EventMngr_assertEPcS0_i+0xa0/0xcc

CROXES-24054 CROXES-23315 Major endUser_customerSite [Report] : Sporadically impossible to use DECT sets

CROXES-24077 CROXES-22727 Major endUser_acceptance [Report] : Rainbow Media Pillar OXE: some audio lost cases after hold-retrieve calls

CROXE-17277 CROXE-16178 Major endUser_customerSite [Report] : Spontaneous restart of SIP motor with the Backtrace

CROXE-17309 CROXE-17097 Major endUser_prebetaSystem [Report] : Easy install of OXE feature : add control of /usr4 disk space + iso remove

CROXE-17038 CROXE-16891 Major software [Report] : Modified inst_common script in rload to install nss packages

CROXE-17034 CROXE-15795 Major endUser_customerSite [Report] : INTIP boards are resetting after upgrade to 12.3 with the backtraces._//00431230//

CROXE-16784 CROXE-14064 Major validation_nonRegression [Report] : M4-NRT: Call disconnected with backtraces when Tandem set is called by VM 4645 AA MENU

CROXES-24482 CROXES-22775 Major endUser_customerSite [Report] : Voice over IP not working

CROXES-24254 CROXES-24064 Major endUser_alpha [Report] RBT is not proper for external calls via transit node

CROXE-17035 CROXE-15409 Major endUser_customerSite [Report] : GD3 Fan LED turns off when rescued by PCS

List of all Duplicates:


CROXES-24474 CROXES-22775 Minor endUser_customerSite IP-DECT white calls when moving from xBS system to DAP System

CROXE-13771 CROXES-18258 Minor endUser_customerSite IPT TSC_IP Parameters are lost after Out Of Service state by Prefix

CROXE-17344 CROXES-24357 Minor endUser_customerSite //1893F_LSY_RR//Plus de communication en provenance d'un XIVO depuis passage de la version m2.300.29.a
































19.3 M3.402.32 R12.2 MD10

List of all fixes:


CROXES-23218 CROXES-23218 Minor validation_funcManual OXE:M3// Improper display of ringing indication tabs for Boss/Secretary call

CROXE-14727 CROXE-14727 Major validation_funcManual mtracer causes segmentation fault

CROXES-22853 CROXES-22853 Major validation_funcManual MAO error occurs when the user remove the directory name

CROXES-23322 CROXES-23322 Major validation_funcManual OXE/M3: Wrong destination type After forwarding(fwd on busy/fwd on no ans) to voicemail

CROXES-23732 CROXES-23732 Major endUser_customerSite [Related] : Since the installation of Hotfix 999 call forwarding via mgr is no longer possible on some devices.

CROXES-22167 CROXES-22167 Major endUser_customerSite CAC blocked for SIP ISDN outgoing call with RE_INVITE for keepalive and enquiry call // 00378381 //m3.402.24.a

CROXE-13609 CROXE-13609 Minor endUser_customerSite %20 in PAI when SIP extension uses Speed dial number created with Directory Name and First name .

CROXES-22465 CROXES-22465 Minor endUser_customerSite Root cause analysis for the CPU reboot.//00401140

CROXES-23068 CROXES-23068 Major endUser_customerSite Call cancelled in case of reception of 183 from SIP to H323 trunk to remote OXE.

CROXES-22665 CROXES-22665 Minor endUser_customerSite Random tranfer in DTMF mode from VAA server

CROXES-23392 CROXES-23392 Minor endUser_customerSite // 1893F_LSY_RR // Question about SSH on OXE

CROXE-11707 CROXE-11707 Critical endUser_customerSite Main_afe crash with ain_afe_exit: signal 11 received by thread 18570

CROXE-14869 CROXE-14869 Minor endUser_customerSite Call is hang up when reach a 4645 in case of OMS uses

CROXE-13397 CROXE-13397 Minor endUser_customerSite RSI : Call was not successfully transferred

CROXE-14774 CROXE-14774 Minor endUser_customerSite Recording of call transferred appears with wrong remote number

CROXE-14244 CROXE-14244 Minor endUser_customerSite Ecart de statistiques

CROXES-23374 CROXES-23374 Minor endUser_customerSite DTMF issue when DECT with XBS used

CROXE-13780 CROXE-13780 Minor endUser_customerSite All phones are unable to make internal or external calls until a double BASCUL//00401014

CROXE-14585 CROXE-14585 Minor endUser_customerSite Bad "to" content when abrev. number before CCD pilot:"to" is abreviated number.

CROXE-15499 CROXE-15499 Minor endUser_customerSite Backtrace on Standby CPU involving REX eqt while VoIP Rainbow Call on Mobile App is engaged.

CROXE-14857 CROXE-14857 Minor endUser_customerSite Agent DECT Call by name doesn't work after OXE reboot if the agent was logon














































CROXE-15582 CROXE-15582 Minor endUser_customerSite //1893F_LSY_RR//Musique non diffusÃ©e sur trunk sip via csta genesys

CROXES-22833 CROXES-22833 Minor endUser_customerSite External caller hears noise and the attendant does not hear any audio in transfer scenario.

CROXES-22773 CROXES-22773 Minor endUser_customerSite Wrong PAI in "180 Ringing" sent to a SIP device

CROXES-23270 CROXES-23270 Minor endUser_customerSite mtracer with -u stop working when IPDSP start with incidents 1603 / 1607 linked to AOM

CROXES-23206 CROXES-23206 Minor endUser_customerSite Forward on no reply to a user on a distant node does not work

CROXES-22048 CROXES-22048 Minor endUser_customerSite Wrong spelling of the "Category 1" parameter (mgr > Categories > Transfer Category) in French

CROXES-23742 CROXES-23742 Minor endUser_customerSite Impossible to answer an alarm call on DECT if digit key is pressed accidentially OXE R12.2 m3.402.25.a

CROXES-23194 CROXES-23194 Minor endUser_customerSite //1893F_LSY_RR// Cloud Connect Procedure RTR Status NOK Code 603 : CNX/DCNX every 2 minutes

CROXES-23791 CROXES-23791 Major endUser_customerSite LDI one way communication when blind transfer to tandem remote worker

CROXES-21962 CROXES-21962 Minor endUser_customerSite Wrong spelling of the "Unattended Transfer for RSI" parameter (SIP external gateway) in French

CROXES-22304 CROXES-22304 Minor endUser_customerSite Rainbow : impossible to have a connection to openrainbow.com because of domain name

CROXES-23143 CROXES-23143 Minor endUser_customerSite Impossible to transfer external call to a statistical pilot.

CROXES-23558 CROXES-23558 Minor endUser_customerSite Unable to access OT Voicemail when calling a CCD pilot set - Voicemail Server does not recognize the VoiceMail Box

CROXE-15378 CROXE-15378 Minor endUser_customerSite DID number not send in case of forward on no answer

List of all Reports


CROXE-16149 CROXE-15681 Major software [Report] : Need to close port 80(unnecessarily opened by Nginx)

CROXES-23656 CROXES-20759 Major endUser_prebetaSystem

[Report] : [Related] : SEPLOS user: Impossible to retrieve the first call on OTC Smartphone if second calling party release the call first .

CROXE-16504 CROXE-11420 Major validation_acceptance [Report] : 9 FWdwl on 9 time slots on 1 IP-XBS with emerg. reserved slots: Calls KO

CROXES-24024 CROXES-21824 Major endUser_customerSite [Report] : Remote FWD to OOS Sip Extension with valid overflow not working

CROXE-16215 CROXE-15425 Major validation_funcManual [Report] : OXE:M4- Multiple entries in call log after camp-on

CROXE-16720 CROXE-14090 Minor endUser_customerSite [Report] : OXE phonebook stuck in R12.3

CROXES-24013 CROXES-23033 Major endUser_customerSite [Report] : crontab modification done by crontab -e are lost after cpu reboot

CROXE-15925 CROXE-15827 Major validation_funcManual [Report] : M5 Direct RTP: NRT- Call released when SEPLOS in hold state
















































CROXES-23763 CROXES-23740 Major validation_funcManual [Report] : Unable to load m4.501.12 #2

CROXES-23745 CROXES-22978 Major endUser_customerSite [Report] : [Related] : //1893_OT_RR// OTC App Error on forwarding busy or no answer

CROXES-24008 CROXES-23943 Minor validation_funcManual [Report] : OT15_MD4/Can't associate OTC Smartphone device to a CT user - PMS error

CROXES-24025 CROXES-22864 Major endUser_customerSite [Report] : CAC is not released for some IP domain, reaching CAC limit

CROXE-16217 CROXE-15049 Major None [Report] : 4645 Voice Guides after 2020: Need to remove an incident

CROXES-24023 CROXES-23375 Major endUser_customerSite [Report] : DECThandset not reachable randomly / R12.3 sm4.302.18.h

CROXES-21490 CROXES-21899 Major validation_funcManual SIPTLS M3/While Attendant involved in intrusion call ,Voice path is not present.

List of all Duplicates


CROXES-23357 CROXES-23322 Major validation_funcManual OXE/M3: Wrong destination type After changing from immediate forward to immediate forward on busy/No reply

CROXES-22890 CROXES-23374 Minor endUser_customerSite Unable to send DTMF from 8232 DECT to SIP device, extension, IPTouch

19.4 M3.402.31 R12.2 MD9

List of all fixes


CROXES-22056 CROXES-22056 Critical validation_funcManual OXE M3: Rainbow: ApiMgt connection failed to /var/run/nginx_socket. Poco exception: I/O error

CROXE-12835 CROXE-12835 Major endUser_customerSite No audio when the internal call in node 2 is tansferred to OTCPC Connection user in node 10_//00383849

CROXE-14735 CROXE-14735 Minor endUser_customerSite DTMF not working with IPDECT

CROXES-22783 CROXES-22783 Minor endUser_customerSite Command "compvisu eqt" aborts with backtrace

CROXES-20063 CROXES-20063 Major validation_funcManual OXE:M3: No RBT for SIPISDN Calls from Restricted Domain(g729) set

CROXES-22757 CROXES-22757 Minor validation_funcManual OXE:M3// Column misalignment of Type, DSU, DS field in "ippstat d" command


































CROXE-14047 CROXE-14047 Major endUser_customerSite Agent on DECT 8242 with Bluetooth Headset are not availible when automatic WrapUp Time on Pilot is configured

CROXE-12982 CROXE-12982 Minor endUser_customerSite //1893_PROSERV_ESC// Dual CSTA event from OXE sip calls creating for Recorder in OXE .

CROXES-22695 CROXES-22695 Minor endUser_customerSite Remote forwarding not working with DECT set in ABC-F Network

CROXE-7867 CROXE-7867 Minor endUser_customerSite CAC counter randomly blocked in one IP domain.


After a DOUBLE MAIN situation, prefered CS (CPU A) reboots since CPU B is connected to Reference Media Gateway while Reference M/G is not configured

CROXES-21893 CROXES-21893 Major endUser_customerSite SIPMOTOR crashes due to backtrace CMotorTimerSynchroniseStdBy::treateTimeO

CROXE-14426 CROXE-14426 Critical endUser_customerSite The EWT is getting higher and higher.because the number of ACR cal is not correct in alb process

CROXES-22800 CROXES-22800 Minor endUser_customerSite OXE Accounting tickets - Called number only 8 digits long in tranzit call

CROXE-13381 CROXE-13381 Major endUser_customerSite //1893F_LSY_RR//CCD/SIP OTCS : SIP INVITE has bad 'to' field' in case of failover

CROXES-22969 CROXES-22969 Minor endUser_customerSite 4645 distributed list mail box number shows as out of service when dialed. Not able to leave message.

CROXES-17343 CROXES-17343 Minor endUser_customerSite Wrong values for compressors retrieved by SNMP linked to cnx dom// 1-219494841 // l2.300.36.a

CROXES-12609 CROXES-12609 Minor endUser_prebetaSystem nomadic ghostz busy with AUXRA

CROXES-22545 CROXES-22545 Minor endUser_customerSite //Supervised transfer from VAA is not working if Q23 transparency is set to TRUE the SIP ABCF trunk group//

CROXE-15401 CROXE-15401 Critical endUser_customerSite OXe : SIP To Header not correct on RSI Transfert of Outgoing calls

CROXES-22057 CROXES-22057 Minor endUser_customerSite Incidents 1603 and 1607 recurrent//00387529//


By abc link, Overflow on 2nd routing number of ENTITY CDT is not working in case of timer 102 expiration before of timer overflow_//00390193//

CROXE-13171 CROXE-13171 Major endUser_customerSite Alarmserver urgent broadcast on devices wirh set supervision team display of 'please hangup'

CROXES-22313 CROXES-22313 Major endUser_prebetaSystem

[Related] : Communication without audio between OXO user called from his Rainbow on mobile a user OTC PC on OXE node.

CROXES-23027 CROXES-23027 Major endUser_customerSite Some incoming public SIP call to a TDM set in a peripheral shelf behind INTOF fails

CROXES-22912 CROXES-22912 Major endUser_customerSite Dect-User"no response from system"

CROXES-22127 CROXES-22127 Major endUser_customerSite //OTHER// Error during Faxtransmission


H323 trunk calls forwarded to external disconnected by INTIP3 (timer) linked to delay to get ALERT from T2 // 00404678// m3.402.25

CROXES-17719 CROXES-17719 Minor review FW Enhancement: Automation of on-hook tone detector parameters for APA trunk


















































CROXES-22430 CROXES-22430 Minor software Netadmin warning message during partition duplication is redundant

CROXES-23268 CROXES-23268 Critical endUser_customerSite

GE: REx: Remote Extension Network doesn't start + Exceptions init_remote_nwk with incidents 5904 and 1721 / OXE / R12.2 m3.402.25.a

CROXES-22531 CROXES-22531 Major endUser_customerSite [Related] : No call forwarding to the tandem device if the SIP Extension (Main set) is Out of Service

CROXE-15738 CROXE-15738 Minor software CS-2 reboots in case of POWER DOWN request

CROXES-22782 CROXES-22782 Minor endUser_customerSite Special character for proxy do not work and full fqdn for proxy name does not work

CROXES-20708 CROXES-20708 Minor endUser_labSystem Cloud Connect netadmin menu needs formatting

List of all Reports



[Report] : Wrong country code in calling number in case of external forward on no reply to a SIP voice mail attached to an OXE in another country

CROXES-23065 CROXES-21645 Major endUser_customerSite [Report] : CLI issue with UTF-8 character in Korean language.


[Report] : GE: Incorrect display on the Z-set, when SIP trunk has Special Service = Urgent Broadcast / OXE / R12.1 sm2.300.24

CROXES-23054 CROXES-21927 Major endUser_customerSite [Report] : Failure to send fax to a few destinations

CROXES-23053 CROXES-21702 Major endUser_customerSite [Report] : No voice after transfer of a public SIP call to the IAA by a SIP application

CROXES-23051 CROXES-21104 Major endUser_customerSite [Report] : Incident 2650=SQL error: appli CMIS_SAVE table NOE_PARAM error 100

CROXE-15092 CROXE-13204 Major endUser_customerSite [Report] : No direct rtp between OXE IPT and OXO behind SIP.

CROXE-15132 CROXE-11864 Major endUser_customerSite [Report] : m2.300.19a-us SIP no audio due to no codec in ACK for RE-INVITE

CROXES-23587 CROXES-23224 Major endUser_customerSite [Report] : SIP REFER impossible with long number with RSI

CROXE-15797 CROXE-11838 Major validation_nonRegression [Report] : M4-NRT:Backtrace occurs and call disconnected during Pilot called from secondary tandem

CROXES-23047 CROXES-22572 Major endUser_customerSite [Report] : LDI Handle correctly session timer with RE-INVITE in SIP-tLS SRTP

CROXE-15101 CROXE-12445 Major endUser_customerSite [Report] : Recording has no audio

CROXES-23061 CROXES-20848 Major endUser_customerSite [Report] : Cannot register new DECT sets, no answer on dectinston tool


[Report] : //1893_LSY_RR// GE: Call log doesn't store missed call for busy user without Multiline with camp-on enabled / OXE / R12.3 m4.302.5.a












































CROXES-23055 CROXES-22585 Major endUser_customerSite [Report] :Bad handling of UPDATE received in conversation state, noisy call

CROXES-23403 CROXES-22920 Major endUser_betaSystem [Report] : CSR Import PKCS#12 / PKCS#7

CROXE-15103 CROXE-14134 Major endUser_customerSite [Report] : Dect-User"no response from system"

CROXES-23062 CROXES-22045 Major endUser_customerSite [Report] : Getting Backtrace while executing "compvisu lio" command.//00388805//

CROXE-15096 CROXE-11973 Major endUser_customerSite [Report] : Urgent broadcast call to Agent - CC Tab in MenÃ¼ on phones disappears

CROXE-15126 CROXE-12665 Major endUser_customerSite [Report] : Inbound SIP no audio when call picked up on other node.



CROXES-22972 CROXES-21454 Major endUser_customerSite SIPMOTOR crash with backtrace related to CMotorTimerSynchroniseStdBy::treateTimeO

CROXE-15000 CROXE-14735 Minor endUser_customerSite DTMF GAP+ with IP-DECT not working.

19.5 M3.402.30 R12.2 MD8

List of all fixes


CROXE-11106 CROXE-11106 Major endUser_acceptance SOSM messages 1.1-1.3 issue : "selection feature" does not change to "statistical" in specific case

CROXE-13788 CROXE-13788 Major endUser_customerSite Sometimes the phones 80x8s do not ring//00395971

CROXE-14428 CROXE-14428 Major endUser_customerSite SS (CS) Point 6.3 step 10 Code value is 04 instead of 05 call

CROXE-14009 CROXE-14009 Major endUser_customerSite No Ring Back Tone on T2, when an incoming call transit via OXE to Third Party SIP PBX

CROXE-14140 CROXE-14140 Major endUser_customerSite SOSM SS (conf) Point 9.4 step 12 no message MCL not released

CROXE-13547 CROXE-13547 Major endUser_customerSite 80x8S sometimes do not ring for an incoming call

CROXE-11102 CROXE-11102 Major endUser_acceptance SOSM MCL voice tract Connect by command issue

CROXE-12420 CROXE-12420 Major endUser_customerSite Keyboard de activated frequently

CROXE-12093 CROXE-12093 Major endUser_customerSite 8078s Crashes when Plantronics Voyager Legend used

CROXE-13554 CROXE-13554 Major endUser_customerSite 8078S reboots just after switching from Bluetooth handset








































to Plantronics Voyager Legend Bluetooth headset

CROXE-11103 CROXE-11103 Major endUser_acceptance

SOSM Data transfer request and MCL/Group correspondence issue ( not defined in the TT channels for the PABX of given capacity )

CROXE-14015 CROXE-14015 Major endUser_customerSite //S3 requested// Incorrect display of diversion info on the terminal device

CROXE-13230 CROXE-13230 Minor endUser_customerSite DTMF is not taken into account.

CROXE-13909 CROXE-13909 Minor endUser_customerSite download of voice guide blocked for OMS

CROXE-11107 CROXE-11107 Major endUser_acceptance

SOSM Remote Control does not receive messages 1.4 about the order/cancellation by the subscriber of the Supplementary Services.

CROXE-11105 CROXE-11105 Major endUser_acceptance SOSM issue when re-stop with the initial password ( No transmission to the CP of message )

CROXE-14427 CROXE-14427 Major endUser_customerSite Sometimes, there are no digits in the messags 1.3 when user make "insignificant" call

CROXE-14138 CROXE-14138 Major endUser_customerSite SOSM SS (chain forward) Point 2.4 step 1 no message 1.1 if all A,B,C, D under control


//1893_CCD_RR// 377412_Wrong Information in CSTA when Call goes through ABCF Hybridlink and Call is transferred by a SIP Application

CROXE-13493 CROXE-13493 Major endUser_customerSite 8068s crashing during calls

CROXE-11894 CROXE-11894 Minor endUser_customerSite Protel Synronisation via AHL doesn't work

CROXE-13596 CROXE-13596 Major endUser_customerSite Audio issue on 8078s with Bluetooth

CROXE-12676 CROXE-12676 Minor endUser_customerSite INTOF2A remains in wait link after inter act link loss or power fail

CROXE-13146 CROXE-13146 Minor endUser_labSystem CSTA – Not possible to active on hold from a DECT set by CSTA

CROXE-13588 CROXE-13588 Minor endUser_customerSite Since upgrade to 12.2, lots of incident 2612

CROXE-11101 CROXE-11101 Major endUser_acceptance SOSM MCL assignment issue

CROXE-12415 CROXE-12415 Minor endUser_customerSite Lot of checkdb errors after upgrading to R12.2

CROXE-12919 CROXE-12919 Minor endUser_customerSite Check-in language is not applied automatically in IP DECT 8242 hotel suit guest extensions.

CROXES-22090 CROXES-22090 Minor endUser_customerSite 80x8s display strings problem

CROXES-14988 CROXES-14988 Minor endUser_customerSite After RSI call to agent, wrap up is cancel

CROXES-22113 CROXES-22113 Major endUser_customerSite IP allocation problem with 8028s phones.//00387855//

CROXES-21887 CROXES-21887 Major endUser_customerSite encryption noise with FSNE

CROXES-22013 CROXES-22013 Major endUser_customerSite vulnerabilities Oxe R12.2

CROXES-22176 CROXES-22176 Critical validation_funcManual [Related] : sequential group: the external incoming call is ended on the first disconnected mobile

CROXES-20661 CROXES-20661 Major endUser_customerSite OXE 12.2 Thales bascul don´t work

CROXES-22904 CROXES-22904 Minor software M3-Delivering libidn package

CROXES-22830 CROXES-22830 Major integration_continuousTest M3-CI: Calling number not displayed on called party during network call


























































CROXES-22517 CROXES-22517 Minor endUser_customerSite GE: Database change on Main-CPU not taken into account on Stand-By CPU / OXE / R12.2 m3.402.25

CROXES-21635 CROXES-21635 Minor endUser_customerSite OXE no longer generates Obstraf pmm tickets under /usr4/pmm

List of all Reports


CROXE-14311 CROXE-11214 Major endUser_customerSite [Report] : SIPMOTOR restarted.

CROXE-14632 CROXE-13969 Major None [Report] : Phone-set not seen as busy when in local application

CROXE-14303 CROXE-12046 Major endUser_customerSite [Report] : One way audio when call gets transfer from one node to another then goes to voicemail.

CROXE-14304 CROXE-12361 Major endUser_customerSite [Report] : m2.300.19a-us Inbound ISDN SIP call via IAA, ABCF TDM, SIP VM to agent can't be transferred by agent.

CROXE-15022 CROXE-14049 Major review [Report] : [Related] : [Feature] Creation of Serbian country variant-Swinst part


[Report] : AT: mailsys process sporadically blocked and no incidents / Omnivista Alarms anymore / OXE / R12.1 m2.300.20

CROXE-14316 CROXE-12164 Major endUser_demoSystem [Report] : Incident 412 not working

CROXE-14841 CROXE-12890 Major endUser_customerSite [Report] : Unable to add hosts under trusted hosts list on OXE

CROXE-14842 CROXE-13756 Major endUser_alpha [Report] : Alpha nu11 : loss of service tel RAINBOW after switch-over to M4.302.25.g

CROXE-14888 CROXE-13446 Major endUser_customerSite [Report] : Mute Problem on 8082, Similar issue: CR8082NOE-313. (Regression)//00394587//

CROXE-14644 CROXE-13887 Major endUser_prebetaSystem [Report] : [Related] : servicability request for IP-xBS synchronization tree splits OXE part

CROXE-14318 CROXE-11936 Major endUser_customerSite [Report] : SIP calls remain as inactive with State = INITIAL_STATE

CROXE-14315 CROXE-12099 Major endUser_customerSite [Report] : While switching from 8058s to 8068s with MLA keys, switching fails and time is not displayed on the screen

CROXE-14309 CROXE-12524 Major endUser_customerSite [Report] : Incorrect filling of the SIP field "TO" following a call transfer from an agent to an RSI point


[Report] : In a Master conference scenario, master is hearing the RBT until all the users in the conference group list picks up the call via SIP TG.

CROXES-22763 CROXE-14442 Minor endUser_customerSite [Report] : Problem with Cloud Connect_//00411614//

CROXES-22515 CROXES-21818 Major endUser_customerSite [Report] : 1st digit is missing in the display of 8018,8058s during Incoming call

CROXES-22822 CROXES-21126 Major endUser_customerSite [Report] : OXE WBM GUI issue when consulting "Help" Menu from "Phone Features COS" with Firefox












































CROXES-22823 CROXES-22109 Major validation_funcManual [Report] : OXE//M3: Copyright year is not updated to 2019 in WBM

CROXES-22895 CROXES-22326 Major endUser_customerSite [Report] : OXE Rainbow CCTool failed - can't create lock ..file was not created.

CROXES-22638 CROXES-17304 Major endUser_customerSite [Report] : since R12 migration crash of CPU very oftern without logs


report: GE-SIP-TLS after restart of CPU or SIPMOTOR ext. SIP-GW becomes unstable. part concerning the SHORT / USHORT issue

CROXES-22633 CROXES-19988 Major endUser_customerSite [Report] : Crash CPU MAIN with Backtrace + Crash Standby

CROXES-22903 CROXES-22713 Major endUser_prebetaSystem [Report] : [prebeta OXE] database periodic backup doesnt work in m4, the line is missing in crontab

CROXES-22819 CROXE-12904 Major validation_funcManual

[Report] : M4: Unable to register "Periodic backup on network" after completing the "Immediate backup on CPU disk"

CROXES-22637 CROXES-15500 Major endUser_customerSite [Report] : Since managed "Paging overflow Dir.No.", lots of 2615 incidents with DECT sets.

CROXES-22901 CROXES-22738 Major software [Report] : Unary operator expected error thrown during delivery installation

CROXES-22634 CROXES-18254 Major endUser_customerSite [Report] : No voice connection when calling of user with active forwarding to 4645 voicemail

CROXES-22795 CROXES-22433 Major endUser_customerSite [Report] : SIP TLS and ABCF2 network : End of call after blind transfer to remoteworker

CROXES-22899 CROXES-20605 Major endUser_customerSite [Report] : remote install PCS fails



CROXE-14311 CROXE-11214 Major endUser_customerSite [Report] : SIPMOTOR restarted.

CROXE-14632 CROXE-13969 Major None [Report] : Phone-set not seen as busy when in local application

CROXE-14303 CROXE-12046 Major endUser_customerSite [Report] : One way audio when call gets transfer from one node to another then goes to voicemail.

CROXE-14304 CROXE-12361 Major endUser_customerSite [Report] : m2.300.19a-us Inbound ISDN SIP call via IAA, ABCF TDM, SIP VM to agent can't be transferred by agent.

CROXE-15022 CROXE-14049 Major review [Report] : [Related] : [Feature] Creation of Serbian country variant-Swinst part


[Report] : AT: mailsys process sporadically blocked and no incidents / Omnivista Alarms anymore / OXE / R12.1 m2.300.20

CROXE-14316 CROXE-12164 Major endUser_demoSystem [Report] : Incident 412 not working

CROXE-14841 CROXE-12890 Major endUser_customerSite [Report] : Unable to add hosts under trusted hosts list on OXE












































CROXE-14842 CROXE-13756 Major endUser_alpha [Report] : Alpha nu11 : loss of service tel RAINBOW after switch-over to M4.302.25.g

CROXE-14888 CROXE-13446 Major endUser_customerSite [Report] : Mute Problem on 8082, Similar issue: CR8082NOE-313. (Regression)//00394587//

CROXE-14644 CROXE-13887 Major endUser_prebetaSystem [Report] : [Related] : servicability request for IP-xBS synchronization tree splits OXE part

CROXE-14318 CROXE-11936 Major endUser_customerSite [Report] : SIP calls remain as inactive with State = INITIAL_STATE

CROXE-14315 CROXE-12099 Major endUser_customerSite [Report] : While switching from 8058s to 8068s with MLA keys, switching fails and time is not displayed on the screen

CROXE-14309 CROXE-12524 Major endUser_customerSite [Report] : Incorrect filling of the SIP field "TO" following a call transfer from an agent to an RSI point


[Report] : In a Master conference scenario, master is hearing the RBT until all the users in the conference group list picks up the call via SIP TG.

CROXES-22763 CROXE-14442 Minor endUser_customerSite [Report] : Problem with Cloud Connect_//00411614//

CROXES-22515 CROXES-21818 Major endUser_customerSite [Report] : 1st digit is missing in the display of 8018,8058s during Incoming call

CROXES-22822 CROXES-21126 Major endUser_customerSite [Report] : OXE WBM GUI issue when consulting "Help" Menu from "Phone Features COS" with Firefox

CROXES-22823 CROXES-22109 Major validation_funcManual [Report] : OXE//M3: Copyright year is not updated to 2019 in WBM

CROXES-22895 CROXES-22326 Major endUser_customerSite [Report] : OXE Rainbow CCTool failed - can't create lock ..file was not created.

CROXES-22638 CROXES-17304 Major endUser_customerSite [Report] : since R12 migration crash of CPU very oftern without logs


report: GE-SIP-TLS after restart of CPU or SIPMOTOR ext. SIP-GW becomes unstable. part concerning the SHORT / USHORT issue

CROXES-22633 CROXES-19988 Major endUser_customerSite [Report] : Crash CPU MAIN with Backtrace + Crash Standby

CROXES-22903 CROXES-22713 Major endUser_prebetaSystem [Report] : [prebeta OXE] database periodic backup doesnt work in m4, the line is missing in crontab


[Report] : M4: Unable to register "Periodic backup on network" after completing the "Immediate backup on CPU disk"

CROXES-22637 CROXES-15500 Major endUser_customerSite [Report] : Since managed "Paging overflow Dir.No.", lots of 2615 incidents with DECT sets.

CROXES-22901 CROXES-22738 Major software [Report] : Unary operator expected error thrown during delivery installation

CROXES-22634 CROXES-18254 Major endUser_customerSite [Report] : No voice connection when calling of user with active forwarding to 4645 voicemail

CROXES-22795 CROXES-22433 Major endUser_customerSite [Report] : SIP TLS and ABCF2 network : End of call after blind transfer to remoteworker

CROXES-22899 CROXES-20605 Major endUser_customerSite [Report] : remote install PCS fails
















































19.6 M3.402.29 R12.2 MD7

List of all fixes


CROXE-11208 CROXE-11208 Major endUser_customerSite //1893F LSY_ESC// Incident 2678 Error IPC SEND: appli CMISE

CROXE-12211 CROXE-12211 Minor endUser_customerSite Set type is "NOE_C_COLO" in listerm all for 8039s set.

CROXE-12584 CROXE-12584 Major endUser_customerSite RSI : Caller does not ear the VG when calling from SIP trunk

CROXE-10058 CROXE-10058 Minor endUser_customerSite Attendant's call to entity call prefix fails if set is CDT is forwarded to voicemail

CROXE-12531 CROXE-12531 Major endUser_customerSite SOSM a lot messages 2.2 for already disconnected calls coming

CROXE-12439 CROXE-12439 Minor endUser_customerSite Frequently incidents 4403=Error 8 on message type 1 on timeslot x is generated

CROXE-12664 CROXE-12664 Major endUser_customerSite audio issue with calls recorded through Packetyzer

CROXE-11415 CROXE-11415 Minor endUser_customerSite Issue of DTMF - not recognized by SIP Server of conference

CROXE-10186 CROXE-10186 Minor endUser_customerSite lost of INTOF shelf during CPU switchover

CROXE-12537 CROXE-12537 Minor endUser_customerSite SOSM not complect list of SS in command 12

CROXE-12530 CROXE-12530 Minor endUser_customerSite SOSM unexpected 0F in reply of command 10

CROXE-13602 CROXE-13602 Minor endUser_customerSite Impossible to keep the supervision key mnemonic has empty content for DECT user

CROXE-13597 CROXE-13597 Minor endUser_customerSite Shows 4 digits against 5 digits when make a call using programmable key (Trunk group prefix)

CROXE-13106 CROXE-13106 Minor endUser_customerSite The incoming call from SIP Trunk transit OXE to DPNSS Trunk fails.

CROXE-13119 CROXE-13119 Minor endUser_customerSite No Ring back tone on 4059IP attendant while make transfer to External//00387764////

CROXE-12534 CROXE-12534 Major endUser_customerSite SOSM test 8.2

CROXE-12535 CROXE-12535 Major endUser_customerSite SOSM Attribute of phone number

CROXE-12533 CROXE-12533 Major endUser_customerSite SOSM no Music on Hold in MCL

CROXE-12978 CROXE-12978 Minor endUser_customerSite Calls from IP Touch set to E1-CAS circuit (point-to-point) are not recorded by OmniPCX Record

CROXE-13672 CROXE-13672 Minor endUser_customerSite Incidents 1367 since upgrade from 11.2 to 12.2

CROXE-13725 CROXE-13725 Minor endUser_customerSite Called/Dialed by Name and busy camp is not working correctly //00398050

CROXE-13862 CROXE-13862 Major endUser_customerSite Not possible to make Call forwarding after time with MGR or 8770

CROXE-13496 CROXE-13496 Minor endUser_customerSite MGR - Create Object Limit(s) works temporarily


















































CROXE-13071 CROXE-13071 Minor endUser_customerSite INT_HS role status for standby INTIP3B link see in config all

CROXE-13182 CROXE-13182 Minor validation_funcManual OT15/Option 'can be called/dialled by name' is set to false if user created using OXE profile in 8770

CROXES-22292 CROXES-22292 Major endUser_customerSite For DECT invalidation of 'Allow auto FW update of sets' parameter in M3

CROXES-21776 CROXES-21776 Minor endUser_customerSite An incoming SIP-ABCF call internally transferred can't be put on hold by the remote SIP party

CROXES-21107 CROXES-21107 Major endUser_customerSite OT | Incoming Fax transmission error

CROXES-21722 CROXES-21722 Major endUser_customerSite RADIUS authentication without Local User. Cannot browse to all folders with FTP

CROXES-22423 CROXES-22423 Major endUser_customerSite Error "Software problem in restricted_map_dcom !!!" when using "dectview com"

CROXES-21937 CROXES-21937 Major endUser_customerSite Problems with incoming SIP Calls after upgrade to Rel 12.2

CROXES-21579 CROXES-21579 Major endUser_customerSite System crashes with 1640=Internal Monitel error no 3, line 11745, file 68 error GAP_HANDSET exception

CROXES-22675 CROXES-22675 Major software_analysisTool Array 'number' of size 18 may use index value(s) 18 // KWID-58184 // CCX

CROXES-21638 CROXES-21638 Major endUser_customerSite OXE users gets connected to voice guides or one way call during external calls after some time//00375884//

CROXES-21660 CROXES-21660 Critical endUser_betaSystem ALE PROD : unsupervised transfer by attendant fails

CROXES-22325 CROXES-22325 Major software_analysisTool Pointer 'pt_demi' checked for NULL may be dereferenced // 58168 // 58172 // Switching

CROXES-22354 CROXES-22354 Major validation_funcManual OXE/M3 : Count of the Call-log disappears when scrolled down to next page in Japanese language

CROXES-22479 CROXES-22479 Major endUser_customerSite Multicodec not launched on RE-INVITE reception leading to noise in encryption

CROXES-22016 CROXES-22016 Major endUser_customerSite strong noise during blind transfer

CROXES-22656 CROXES-22656 Blocker validation_funcManual OXE:M3 :EXternal SIPTLS Hold/Retrieve Call disconnects with Backtrace in THALES

CROXES-22100 CROXES-22100 Major endUser_customerSite After dectrestart xBS, xBS go in IP Domain 0 instead in their configured IP Domain

CROXES-22482 CROXES-22482 Blocker validation_funcManual Unable to build lanpbx in FSNE configured node

CROXES-21615 CROXES-21615 Major endUser_customerSite DTMF Issue with R12.2 on T2/ABCF.

CROXES-21770 CROXES-21770 Major endUser_customerSite IPxbs - abnormal display on IP ticket via XBS

CROXES-21527 CROXES-21527 Minor endUser_customerSite DTMF Tones are being sent automatically to the calling extension on ISDX when Call is answered on OXE.

CROXES-21952 CROXES-21952 Major endUser_customerSite Issue witch dect calls (xbs coverage) coming from skype

List of all Reports



















































CROXE-14067 CROXE-12243 Major endUser_customerSite [Report] : Panic Flag SWK because of software lock 328 IP-Softphone Attendants exceeded.

CROXE-13949 CROXE-13096 Major software [Report] : Generate DH parameters for NGINX SSL

CROXE-13950 CROXE-13326 Major endUser_customerSite [Report] : OXE vulnerability: mtcl can execute root command without root password

CROXE-13952 CROXE-13075 Major validation_nonRegression [Report] : M4 NRT: Error message thrown on Partition duplication of linux from M4.302.18.a to M4.302.25

CROXE-13951 CROXE-13201 Major endUser_alpha [Report] : RAINBOW AGENT: WSS is disconnected because PONG timeout value is too low

CROXE-13831 CROXE-12678 Major None [Report] : 8088 NOE R304: Keyboard QWERTY whereas NOE language is French

CROXE-14102 CROXE-13880 Major integration_funcManual [Report] : N1-220:Partition duplication failed in all CS and also inactive side get corrupted.

CROXE-13888 CROXE-12231 Major endUser_customerSite [Report] : Incoming call transfer to external agent not possible when GVP in the call path

CROXE-14235 CROXE-11905 Major software [Report] : M4 xBS : localization of handsets is not correct

CROXE-13713 CROXE-10703 Major endUser_alpha [Report] : OXE XBS SUOTA : download does not start on several xBS.

CROXE-14197 CROXE-13063 Major validation_funcManual [Report] : OXE M4-Public SIP trunk (tls(v1.2)-No voice path in park/retreive scenario

CROXE-13939 CROXE-12928 Major operations [Report] : GD3-GA3: Format SD card to 1Go

CROXES-22562 CROXES-21903 Major endUser_customerSite [Report] : Site crash with REMAGEN error

CROXES-22594 CROXES-22405 Major validation_funcManual [Report] : Incorrect time is updated in call log when the set is out of service


[Report] : [Related] : //1893_OT_RR// MIGROS : OTC Smartphone VoIP - No Voip when switching to mobile network

CROXES-22443 CROXES-21096 Major software [Report] : GD3/INTIP3: Bug in source code with Thales context

CROXES-22441 CROXES-21499 Major software [Report] : GD3/INTPIP3: Fax SIP overflow on maxSizeCbTb

CROXES-22440 CROXES-21500 Major software [Report] : GD3/INTIP3: ATTR_MCC field is not coherent than enum LIOEM_MCC

CROXES-22447 CROXES-19918 Major endUser_customerSite [Report] : Netadmin: add a message to warn that a copy of data to twin is needed after applying modifications


[Report] : On SIP-ABCF forwarded calls, "transport=TCP" is missing in the Contact header of the 302 when the URI of the Contact contains the OXE

CROXES-22069 CROXE-9227 Major endUser_customerSite [Report] : 8242 blocked : No answer from system


[Report] : [Related] : OXE Phonebook Freefield is cleared when OTC Smartphone or OTC PC is added or user name is changed


[Report] : CCD Agent receives a distributed call. This agent does an enquiry call to the user in the second node


















































CROXES-22590 CROXES-21899 Major validation_funcManual [Report] : SIPTLS M4/LDI : While Attendant involved in intrusion call ,Noise is present



CROXE-13415 CROXES-22292 Minor endUser_customerSite 8242 handset intermittently reboots.

CROXE-8393 CROXE-11208 Minor endUser_customerSite Cannot change or delete SNMP hypervisor

CROXE-13707 CROXES-21338 Minor endUser_customerSite Transport=TCP is missing in the contact header in 302 moved temporariy scenario

CROXE-13533 CROXE-13201 Major endUser_customerSite Lost Rainbow Agent Node LEZ400

CROXE-12532 CROXE-12530 Minor endUser_customerSite SOSM COMMAND 10

CROXES-20546 CROXE-13201 Major endUser_customerSite OXE 12.2 / Rainbow agent lose connection / connection not stable

CROXES-21489 CROXE-13063 Major validation_funcManual OXE:M3:LDI: No Voice path when a parked External call is retrieved by domian user

CROXES-22661 CROXE-13672 Minor endUser_customerSite Incidents 1367 after upgrade to R12.2

CROXES-22283 CROXE-10703 Major endUser_customerSite IP-xBS traffic observation per Base Station

19.7 M3.402.28.A R12.2 MD6

List of all fixes


CROXE-13825 CROXE-13825 Minor endUser_customerSite [Related] : [Report] : OXE vulnerability: mtcl can execute root command without root password

List of all Reports


CROXE-13228 CROXE-13201 Major endUser_alpha [Report] : RAINBOW AGENT: WSS is disconnected because PONG timeout value is too low

CROXE-13858 CROXE-12978 Major endUser_customerSite [Report] : Calls from IP Touch set to E1-CAS circuit (point-to-point) are not recorded by OmniPCX Record






























CROXE-13859 CROXE-13597 Major endUser_customerSite [Report] : Shows 4 digits against 5 digits when make a call using programmable key (Trunk group prefix)

CROXE-13729 CROXE-13096 Minor software [Report] : Generate DH parameters for NGINX SSL

CROXE-13896 CROXE-12928 Major operations [Report] : GD3-GA3: Format SD card to 1Go

CROXE-13224 CROXE-13075 Major validation_nonRegression [Report] : M4 NRT: Error message thrown on Partition duplication of linux from M4.302.18.a to M4.302.25

CROXE-13704 CROXE-13326 Major endUser_customerSite [Report] : OXE vulnerability: mtcl can execute root command without root password

CROXES-22413 CROXES-22354 Major validation_funcManual [Report] : OXE/M3 : Count of the Call-log disappears when scrolled down to next page in Japanese language

CROXES-22356 CROXES-21722 Major endUser_customerSite [Report] : RADIUS authentication without Local User. Cannot browse to all folders with FTP

CROXES-22396 CROXES-22325 Major software_analysisTool [Report] : Pointer 'pt_demi' checked for NULL may be dereferenced // 58168 // 58172 // Switching

CROXES-22421 CROXES-21096 Major software [Report] : GD3/INTIP3: Bug in source code with Thales context

CROXES-22419 CROXES-21499 Major software [Report] : GD3/INTPIP3: Fax SIP overflow on maxSizeCbTb

CROXES-22418 CROXES-21500 Major software [Report] : GD3/INTIP3: ATTR_MCC field is not coherent than enum LIOEM_MCC

CROXES-22407 CROXES-21952 Major endUser_customerSite [Report] : Issue witch dect calls (xbs coverage) coming from skype

CROXES-22420 CROXES-21107 Major endUser_customerSite [Report] : OT | Incoming Fax transmission error


CROXES-22406 CROXES-21770 Major endUser_customerSite [Report] : IPxbs - abnormal display on IP ticket via XBS

CROXES-22455 CROXES-22405 Blocker validation_funcManual [Report] : Incorrect time is updated in call log when the set is out of service

19.8 M3.402.28 R12.2

List of all fixes


CROXE-12830 CROXE-12830 Critical validation_funcManual OXE/M3 : Pro-ACD set gets frozen while doing 'cancel unavailable' operation with Backtrace

CROXE-10627 CROXE-10627 Major None KCME: japanese language looks weird

CROXE-12460 CROXE-12460 Major endUser_customerSite Agent logged in and available, not getting calls

CROXE-11047 CROXE-11047 Minor endUser_customerSite 8018 phone set has no USB menu when Agent

CROXE-11767 CROXE-11767 Major endUser_customerSite Music on Hold is not working after an upgrade//00365815//

CROXE-12854 CROXE-12854 Minor endUser_customerSite OXE incident "2615" when agent DECT logon by CSTA

CROXE-12302 CROXE-12302 Major endUser_customerSite Attendant transfer to busy phone fails


















































CROXE-12215 CROXE-12215 Minor endUser_customerSite Wrong information in Call log when called a Routing Number to a SIP-ABFC Trunk over a ABCF Hybrid-Link overflow

CROXE-13546 CROXE-13546 Major endUser_customerSite When DECT set is switch off, the set ring twice and received message "not authorised"

CROXE-11078 CROXE-11078 Minor endUser_customerSite No ticket generated when call goes to Menu on Set and external caller disconnects

CROXE-12409 CROXE-12409 Minor endUser_customerSite Ecart dans les statistiques ACR

CROXE-12716 CROXE-12716 Major endUser_customerSite Upon overflow on no answer via SIP ABCF, OXE does not send number of called set

CROXE-12022 CROXE-12022 Major endUser_customerSite OXE-CCD: agent not able to park nor able to take next call

CROXES-21659 CROXES-21659 Major validation_funcManual OXE:M3: Call to a Busy Tandem user is disconnected with Backtrace

CROXES-21661 CROXES-21661 Major validation_funcManual OXE:M3: Call to a user which is forwarded to Tandem user is disconnected with Backtrace

CROXES-17628 CROXES-17628 Major endUser_customerSite The 4059EE application is getting frozen randomly

CROXES-21902 CROXES-21902 Major endUser_customerSite //1893_LSY_RR// issue witch dect calls (xbs coverage) coming from skype - Backtrace

CROXES-22086 CROXES-22086 Major software_analysisTool M3-Klocwork Bug// 'WITH_terminaison' and WITH_ralpost might be used uninitialized

CROXES-21408 CROXES-21408 Minor endUser_customerSite OMS / no DTMF when transcoding from G729 (IPTouch) to G711 (SIP Trunk to SBC) // 00359364 // m3.402.13.f


//1893F_LSY_ESC// Demande d'un nouveau FTR pour pallier la décrémentation intempestive et inexpliquée du compteur RTR \\S3 Requested\\

CROXES-22023 CROXES-22023 Minor software crontab files "/var/spool/cron/* missing after empty DB

CROXES-19918 CROXES-19918 Major endUser_customerSite Netadmin: add a message to warn that a copy of data to twin is needed after applying modifications

CROXES-21935 CROXES-21935 Major None OTBE 15 MD2: getVersion, checkALL hang at OMS check, OMS ssh connection from OT refused

CROXES-20473 CROXES-20473 Major endUser_customerSite OMS 8.03 / root partition full / m3.402.13.f

CROXES-21454 CROXES-21454 Minor endUser_customerSite SIP motor crashes since upgrade L2 to M3

CROXES-21861 CROXES-21861 Major validation_funcManual OXE/M3 : 'Events Routing Discriminator' disappears when filtered with incorrect ID

CROXES-22221 CROXES-22221 Major validation_funcManual /OXE-m3.402.28 bad linux version error occurs

CROXES-22042 CROXES-22042 Major software OXE-M3: Restoration of "/var/spool/cron/root" file when it is missing.

CROXES-22200 CROXES-22200 Major endUser_customerSite Network overload display on DECT sets and paging failures problem

List of all Reports


CROXE-13083 CROXE-12148 Major endUser_labSystem [Report] : Rainbow - PCG: Xmpp authentication channel is



























file://///S3
























not reopen

CROXE-13086 CROXE-12700 Major validation_acceptance

[Report] : [Related] : [NOE3GEE][OXE][DTLS] : For mutual authentication we should not have to upload NOE3GEE CTL from phone to OXE, it should be by default - Swinst Part

CROXE-13009 CROXE-12782 Major endUser_prebetaSystem [Report] : Request to RnD to integrate new infocollect 5.7

CROXE-13300 CROXE-9527 Major endUser_labSystem [Report] : Sip External Gateway ,OTCS type , "to" header content evolution


[Report] : OTC-PC nomadic calling external thought SIP ISDN : no RBT after 183 with SDP// 00312196 // l2.300.36.a

CROXE-13214 CROXE-11356 Major endUser_customerSite [Report] : No redirected info if Overflow on busy set to False//00353369


[Report] : External call access via analog trunk by transfer to the network meet me conference from ABC-link not work.

CROXE-13212 CROXE-8809 Major endUser_customerSite [Report] : Attendant group distribution not working when the ABCF T2 link is down is one node.

CROXE-12783 CROXE-11979 Major endUser_customerSite [Report] : Auto dtmf is not working for alarmserver SIP Trunk

CROXE-13084 CROXE-11897 Major endUser_alpha [Report] : Alpha nu12 : loss services tel Rainbow all users - during mastercopy

CROXE-13268 CROXE-8721 Major endUser_labSystem [Report] : //1893_LSY//Problem with DTMF in IAA//00314150//

CROXE-12369 CROXE-8392 Major endUser_customerSite [Report] : //1893_LSY// WBM free number search takes excessively long

CROXE-13082 CROXE-12198 Major endUser_alpha [Report] : Alpha: Core RAINBOWAGENT on start M4.302.5..b for nu11 and nu18

CROXE-13274 CROXE-8232 Major endUser_customerSite [Report] : Random end of call between 2 nodes

CROXE-13181 CROXE-10564 Major endUser_customerSite [Report] : Search name with Return key instead of softkey not working for names with spaces

CROXE-12958 CROXE-12657 Critical None Zendesk#25182 // wrong telephony routing after upgrade BBB in other phone

CROXE-13360 CROXE-10323 Major validation_funcManual [Report] : M4 NRT: "NoeCustomFiles::read_versions - position 3 1543245962" content is populated in traces

CROXE-13085 CROXE-9991 Major validation_funcManual [Report] : OXE:M3: Unwanted # symbol is displayed during patch installation(M3.402.24 #2)

CROXE-13278 CROXE-12069 Major software [Report] : SIP: Junk values in Called Number IE in RO_NUMBER_REQUEST

CROXE-13277 CROXE-10921 Major endUser_customerSite [Report] : No audio when Attendant 4059ee transfer a call, after transit via Genesis server.

CROXE-13275 CROXE-8593 Major endUser_customerSite [Report] : RSI : One way call during external transfert

CROXE-13225 CROXE-11112 Major endUser_customerSite [Report] : External incoming call via internode link does not follow overflow on busy

CROXE-13081 CROXE-12512 Major endUser_betaSystem [Report] : Native encryption SIP TLS : import of CA certificate of SBC not done
















































CROXES-21859 CROXES-20398 Major endUser_prebetaSystem [Report] : [Related] : Conference call impossible if main device Out Of Order.

CROXES-21848 CROXES-18401 Major endUser_acceptance [Report] : [Related] : //1893_OT//Call from OTC PC to public busy destination does not hear busy tone

CROXES-21852 CROXES-17424 Major endUser_customerSite [Report] : [Related] : DTMF no working for OTC smartphone connection user if we call Voice mail.

CROXES-22191 CROXES-17245 Major integration_funcManual [Report] : OTMS HA, AA: call transfer with "Blind Transfer" switched on can't be finished

CROXES-22175 CROXES-20483 Major endUser_customerSite [Report] : Call dropped after the scenario : Node 1 : AA4645 + SIP ABCF => Node 2 : CCD => agent

CROXES-21921 CROXES-20873 Major endUser_customerSite [Report] : [Related] : //1893_OT//OTMS Adding Home pages to IP Phones

CROXES-22068 CROXES-20919 Major endUser_customerSite [Report] : //1893F LSY// Accounting ticket for field (08) Calling number is empty.

CROXES-22009 CROXES-19626 Major endUser_customerSite [Report] : ssh-2 vulnerabilities not resolved in R12.1 OXE

CROXES-22126 CROXES-19381 Major endUser_customerSite [Report] : DTMF is failed for the 4645 AA transferred calls//00300022//

CROXES-22178 CROXES-21060 Major endUser_customerSite [Report] : //1893_LSY// 4059EE, double calling number at incoming call!

CROXES-22153 CROXES-21296 Major validation_funcManual [Report] : OXE/M1 : Junk characters are displayed on Dect when configured as a tandem to an OOS user


[Report] : Speed dail unable to overflow to another speed dail, when analog trunk is used in the speed dial//00334950//

CROXES-22091 CROXES-18562 Major endUser_customerSite [Report] : A lot of Monitel errors 1662 and automatic restarts of SIPMotor

CROXES-22092 CROXES-18837 Major endUser_customerSite [Report] : //1893F_LSY// Issue with 8088 when calling set if immediate forward to 9 "Operator:

CROXES-22180 CROXES-22031 Major validation_funcAuto [Report] : CCX-AT: : Calling set number missing in display for external/loopback incoming call to NOE

CROXES-22183 CROXES-22031 Major validation_funcAuto [Report] : CCX-AT: : Calling set number missing in display for external/loopback incoming call to NOE

CROXES-22070 CROXE-9032 Major endUser_customerSite [Report] : Randomly no response from Dect Set

CROXES-22135 CROXES-15556 Major endUser_customerSite [Report] : Incoherent billing when use remote PINCODE on ABC-F network.//1-212336891//

CROXES-22124 CROXES-20897 Major endUser_customerSite [Report] : Multicompany: Call from the list of missed calls END USER: EWE AG Node 2

CROXES-22084 CROXES-17495 Major endUser_customerSite [Report] : Conversation recording with key F2 after upgrade to R12.0 not possible.

CROXES-21854 CROXES-20428 Major endUser_customerSite [Report] : [Related] : //1893_OT_ESC//Call can not be retrieved from OTPC Client


[Report] : [Related] : //1893_OT_ESC// No RBT for outgoing calls from OT user using PRA-T2 PSTN Trunk with OXE system

CROXES-22082 CROXES-21555 Major endUser_customerSite [Report] : DTMF on IAA not received for SIP trunk call to another node through hybrid IP // 00374759 // m2.300.25


















































CROXES-22181 CROXES-21060 Major endUser_customerSite [Report] : //1893_LSY// 4059EE, double calling number at incoming call!

CROXES-21865 CROXES-20436 Major endUser_customerSite [Report] : [Related] : Call has been lost after 30" when OTCPC call another OTCPC through the RP .

CROXES-22069 CROXE-9227 Major endUser_customerSite [Report] : 8242 blocked : No answer from system

CROXES-22179 CROXES-20270 Major endUser_customerSite [Report] : SIP call failure due to missing called number in INVITE depending on RSI scenario in remote OXE node


[Report] : Incident 1662=Monitel: Lack of resource for ISDN processing, type 1 on SIP Trunk // 00345833 // m2.300.21.a



CROXE-12461 CROXE-12460 Major endUser_customerSite Ghost Calls appear stuck in CCS Waiting Room

CROXE-12462 CROXE-12460 Major endUser_customerSite CCD Agent Sets lock up after log on.

CROXE-13288 CROXES-21454 Major endUser_customerSite SIP motor crashed with the backtrace and Requesting for Hotfix in m3.402.25.a_//00393958//

CROXES-21978 CROXES-21659 Minor endUser_customerSite Backtraces related to the tandem user in the OXE.

CROXES-22003 CROXE-11979 Minor endUser_customerSite Auto DTMF not working for alarm server linked via SIP Trunk - HF request on M3.402.25A

19.9 M3.402.27.A R12.2 MD5

List of all fixes


CROXE-9991 CROXE-9991 Minor validation_funcManual OXE:M3: Unwanted # symbol is displayed during patch installation(M3.402.24 #2)

List of all Reports


CROXE-12299 CROXE-11897 Major endUser_alpha [Report] : Alpha nu12 : loss services tel Rainbow all users - during mastercopy

CROXE-12427 CROXES-19626 Minor endUser_customerSite [Report M3] : //1893_LSY// ssh-2 vulnerabilities not resolved in R12.1 OXE






























CROXE-13018 CROXE-12782 Major endUser_prebetaSystem [Report] : Request to RnD to integrate new infocollect 5.7

CROXE-12298 CROXE-12198 Major None [Report] : Alpha: Core RAINBOWAGENT on start M4.302.5..b for nu11 and nu18

CROXE-13019 CROXE-11047 Minor endUser_customerSite [Report] : 8018 phone set has no USB menu when Agent

CROXE-12860 CROXE-12512 Major endUser_betaSystem [Report] : Native encryption SIP TLS : import of CA certificate of SBC not done

CROXE-12993 CROXE-12830 Major validation_funcManual [Report] : OXE/M3 : Pro-ACD set gets frozen while doing 'cancel unavailable' operation with Backtrace

CROXE-12599 CROXE-12148 Major endUser_labSystem [Report] : Rainbow - PCG: Xmpp authentication channel is not reopen

CROXE-13136 CROXE-12958 Major None [Report] : Zendesk#25182 // wrong telephony routing after upgrade BBB in other phone

CROXES-21972 CROXE-12700 Major validation_acceptance

[Report] : [Related] : [NOE3GEE][OXE][DTLS] : For mutual authentication we should not have to upload NOE3GEE CTL from phone to OXE, it should be by default - Swinst Part


[Report] : //1893F_LSY_ESC// Demande d'un nouveau FTR pour pallier la décrémentation intempestive et inexpliquée du compteur RTR \\S3 Requested\\


CROXES-22050 CROXES-22042 Major software [Report] : OXE-M3: Restoration of "/var/spool/cron/root" file when it is missing.

CROXES-22036 CROXES-22023 Major software [Report] : crontab files "/var/spool/cron/* missing after empty DB



CROXES-21640 CROXE-12148 Major endUser_customerSite authentication channel is not reopen

19.10 M3.402.27

List of all fixes



















file://///S3













CROXE-12469 CROXE-12469 Major software M4-User 'ccfexc' is not created for country Qatar during swinst installation

CROXE-12219 CROXE-12219 Minor software Netadmin conversion after linux data base restoration failing

CROXE-9323 CROXE-9323 Minor validation_funcAuto OXE M3:Pilot2a AT:Some values in events are changed with multiline sets for the double forward case

CROXE-12285 CROXE-12285 Minor software [Related] : M3-FSNE [Feature]: Backporting of CROXE-9409 and CROXE-11346 (Development done in M4) - CH part

CROXE-12284 CROXE-12284 Minor software [Related] : M3-FSNE [Feature]: Backporting of CROXE-9409 and CROXE-11346 (Development done in M4) - Infra Part

CROXE-10548 CROXE-10548 Minor endUser_customerSite 8058S phone switchs back to handsfree after a transfert

CROXE-10230 CROXE-10230 Major endUser_customerSite //1893_LSY// No possibility to set the Bootfilename in Class VHENOE and SIP80x8s

CROXE-11833 CROXE-11833 Minor endUser_customerSite ALE PROD: pcsview does not show a nice tabbed table

CROXE-12117 CROXE-12117 Critical endUser_customerSite Main_afe crash when managing an euthorized phone set

CROXE-12686 CROXE-12686 Minor endUser_customerSite tnet - bad handling of Agents

CROXE-10637 CROXE-10637 Minor endUser_customerSite Call log shows number and not name for speed dial numbers (abbreviated numbers)

CROXE-12121 CROXE-12121 Major endUser_customerSite Unable to create an 8019s Set Profile

CROXE-11826 CROXE-11826 Critical endUser_customerSite SIP PBX - DR-Link (TDM) recording - Call analog line - echo in conversation on reflex phone

CROXE-10152 CROXE-10152 Major endUser_customerSite PR-00343913// Problem in main -Stand By CPU

CROXE-11907 CROXE-11907 Major endUser_customerSite ALE PROD: OXE WBM does not authorize login anymore with R12.2 m3.402.25.a

CROXE-11843 CROXE-11843 Minor endUser_customerSite ALE PROD: downstat i does not show a nice tabbed table.

CROXES-20137 CROXES-20137 Major validation_funcManual OXE/M3 : Display of the secondary is not updated after tandem removal

CROXES-21590 CROXES-21590 Minor endUser_customerSite [Related] : Local database authentication from console port when Radius server OoS does not work on virtual machine

CROXES-21741 CROXES-21741 Minor software Problem in immediate forwarding for analog sets

CROXES-21328 CROXES-21328 Major endUser_customerSite IBS : external call T2 => 4059EE => dect IBS => One way audio call

CROXES-21425 CROXES-21425 Minor review NGP_9.xx: trace suppression

CROXES-21896 CROXES-21896 Minor software problem in fwd for tandem sets

CROXES-20959 CROXES-20959 Major validation_funcManual Audio NOK in conference after EHO

CROXES-21329 CROXES-21329 Major endUser_customerSite One way audio on call pickup on dect

CROXES-21857 CROXES-21857 Blocker validation_funcManual OXE/M3: The option "Free Directory Numbers" and "Free numbers ranges list" are lost after applying filter

CROXES-21345 CROXES-21345 Minor endUser_customerSite //1893_LSY// Issue: 8088 NOE phones does AutoAnswer time to time

CROXES-20863 CROXES-20863 Minor endUser_customerSite IP-xBS one way call during call pickup -

CROXES-20885 CROXES-20885 Minor endUser_customerSite //1893_LSY_RR// GE-R12.2 - Frequently reboots of ACT's




























































behind IOIP3 after IOIP3 crash with backtrace


QSIG-GF incoming calls to SEPLOS failed linked to EI_RTP_INFO in ALERT - Regression // 00368600 // m3.402.24.a

CROXES-20872 CROXES-20872 Minor endUser_customerSite //1893_LSY// Wake up call delay ///00358462//

CROXES-20898 CROXES-20898 Minor endUser_customerSite Local database authentication from console port when Radius server OoS does not work on virtual machine

CROXES-20760 CROXES-20760 Major endUser_customerSite Lot of messages: 4403=Error 5 on message type 3 on timeslot xxx

CROXES-20290 CROXES-20290 Major endUser_customerSite SNMP / Trunk Group SNMP counters are inconsistent for H323 trunk groups // 00345396 / /m3.402.22.c

CROXES-19929 CROXES-19929 Major endUser_customerSite modification done by crontab -e are lost after CPU retsart

CROXES-21351 CROXES-21351 Major endUser_customerSite Incident 6005 contains source code comments / OXE / R12.3 m4.302.1.a

CROXES-20478 CROXES-20478 Major endUser_customerSite //1893_LSY//Wake up call not displaying //00350030//

CROXES-20887 CROXES-20887 Minor endUser_customerSite //1893_LSY// GD-3 Power OFF issue

CROXES-21366 CROXES-21366 Major endUser_customerSite SNMP counters for IP Domain and Trunk Group do not work anymore in patch m3.402.25.a.

CROXES-21420 CROXES-21420 Minor endUser_customerSite Call from a CCA when the phose is an agent DECT in Wrap-up

CROXES-21619 CROXES-21619 Minor endUser_customerSite //1893F_LSY//perte de communication lors de l'activation du HP sur les poste 4010 ou 4020

CROXES-21403 CROXES-21403 Minor endUser_customerSite Issue "No answer from system" with Dect 8378 xBS

List of all Reports


CROXE-11404 CROXE-11379 Minor integration_funcManual [Report] : Cloud Connect: Missing log on software.mao file not compliant

CROXE-11828 CROXE-11701 Major integration_continuousTest [Report] : Cloud Connect: Sometimes ccprocess may freeze without restarting possible

CROXE-12276 CROXE-7632 Major endUser_customerSite [Report] : Secret identity is being displayed instead of the actual calling number for the supervised set


[Report] : No Busy Tone when calling from 8001 set on One node to busy analog set on another Node_//00329053

CROXE-12204 CROXE-11562 Major endUser_labSystem [Report] : M4 FNSE: wrong lanpbx file is generated

CROXE-12370 CROXE-10700 Major validation_funcManual [Report] : M3-IP-xBS: Master & Backup stations are "External Locked" together

CROXES-21578 CROXES-19241 Major endUser_customerSite [Report] : OXE does not reply to Re-Invite in case of 3-party-conference

CROXES-21585 CROXES-17512 Major endUser_customerSite [Report] : crash od CPU with crashdump after monitel watchdog

CROXES-21678 CROXES-19663 Major validation_funcManual [Report] : OXE/M1 : Blank screen when a is immediate
















































forwarded to a set without name.

CROXES-21583 CROXES-18931 Major endUser_customerSite [Report] : DTMF issue when sent from IPT via ABCF IP

CROXES-21586 CROXES-19252 Major endUser_customerSite [Report] : Redundancy services KO after doing a CPU switchover since migration to R11.2

CROXES-21671 CROXES-18532 Major validation_funcManual [Report] : OT-OXE/L2:Network user displays junk characters when called a customized OT user

CROXES-21522 CROXES-19558 Major endUser_customerSite [Report] : Unable to carry out blind transfer form CCD agents to CRG group on same node


[Report] : When a call is not answered, the call logs is displaying the time of the CS instead of IP domain time. //00303437//

CROXES-21680 CROXES-15312 Major endUser_customerSite [Report] : SOSM service doesnt start after bascul

CROXES-21710 CROXE-10364 Major endUser_customerSite [Report] : //1893F_LSY// incident 2650 error CMIS_SAVE POSTE table

CROXES-21698 CROXES-19909 Major endUser_customerSite [Report] : Transfer on ringing by a SIP extension set

CROXES-21589 CROXE-9530 Major endUser_customerSite

[Report] : Since Upgrade from R10.0 to R12.1, on 4059 IP console, called extension name display is lost(entity name is show)

CROXES-21643 CROXES-21161 Major endUser_customerSite [Report] : [Related] : remote install PCS failled with PC installer 5.5 -- PC-installer fix

CROXES-21568 CROXES-20751 Minor endUser_customerSite [Report] : IP phones go on loudspeaker and emit 3 beeps when there is a bascul

CROXES-21575 CROXES-16677 Major endUser_customerSite [Report] : G729 sent in a Re-Invite on a SIP ext. GW having Type of codec negotiation = Single codec G711

CROXES-21447 CROXES-19984 Major endUser_customerSite [Report] : No-ReInvite with SendRecv to retrieve a held call when "SendOnly for hold" is True

CROXES-21670 CROXES-19761 Major endUser_customerSite [Report] : External call to sets with ‘Forward to Text message’ not properly displayed on 4059IP

CROXES-21591 CROXES-19902 Major endUser_customerSite [Report] : OXE CAC counter not decreasing after call via GVP

CROXES-21577 CROXE-8772 Major endUser_customerSite [Report] : Overflow on total busy not working as defined when group sets are busy


[Report] : Incoming anonymous SIP calls from Voice Alarm server to IP Attendant (4059IP) doesn't work => no voice connection

CROXES-21519 CROXES-21185 Major validation_funcManual [Report] : OXE:M2: Backtrace observed when User is set to 'forward on no reply' in centrex configuration

CROXES-21817 CROXES-20974 Major endUser_customerSite [Report] : Display is not shown in the sets if there is call-in,call-out or if dials any digits.

CROXES-21711 CROXE-9932 Major endUser_customerSite [Report] : No ringback tone in case of external incoming call via SIP to VAA is transferred to OXE Attendant












































CROXES-21576 CROXES-19435 Major validation_funcManual [Report] : OT/M1: Wrong Display and call log during supervised transfer to SIPDEVICE by OT.

CROXES-21524 CROXE-9097 Major endUser_customerSite [Report] : Problem with 80x8S device - unreachable after set type changed to 8039 with forward activated

CROXES-21720 CROXE-8596 Major endUser_customerSite [Report] : //1893_PROSERV_RR//OPXR - External Anonymous Calls marked as internal

CROXES-21706 CROXES-21034 Major endUser_customerSite [Report] : Backtrace in dectview com command

CROXES-21584 CROXES-18815 Major endUser_customerSite [Report] : SIP: PRACK transaction not working well in case of early reception of 200ok/INVITE

CROXES-21713 CROXE-9905 Major endUser_customerSite [Report] : //1893_OT_RR// OT Web Guest unable to send DTMF signals

CROXES-21697 CROXE-9475 Major endUser_customerSite [Report] : Call state is reported from OXE to Genesys T-server with delay

CROXES-21592 CROXE-9030 Major validation_funcManual [Report] : Rainbow: Call disconnects and bactrace thrown during transferring attendant call

CROXES-21587 CROXES-17040 Major endUser_customerSite [Report] : Problem with calling number with from empty and external fwd

CROXES-21515 CROXES-21190 Major software [Report] : Wrong entity fetched for Inter-company rights

CROXES-21672 CROXE-8463 Major endUser_customerSite [Report] : 8001 sets freeze randomly.


[Report] : No VG being played when call coming from SIP ISDN one one node being send to another node through ABCF T1

CROXES-21677 CROXE-9247 Major endUser_customerSite [Report] : Known external caller display on agent set


[Report] : Could not ignore the call from OTC PC by selecting the Voicemail option, when Menu On Set is enabled



CROXE-12274 CROXE-12117 Critical endUser_customerSite OXE CCD | AFE crashed

CROXE-11923 CROXES-21366 Minor endUser_customerSite SNMP - No Such Object available on this agent at this OID error




































CROXES-21588 CROXE-12219 Minor endUser_customerSite //1893F_LSY_RR//Problème sur la commande "tcpdump" sur des serveurs GAS en R12.2

CROXES-21375 CROXE-11907 Minor endUser_customerSite Unable to login as mtcl on OXE WBM

CROXES-21601 CROXE-12310 Minor endUser_customerSite Call log shows 'Amt' instead calling number for ISDN Remote Trunk / OXE / R12.2 m3.402.25

19.11 M3.402.26.B

List of all fixes


CROXES-19876 CROXES-19876 Major endUser_customerSite [Related] : No ring back tone when we call from OTC PC to an external BTIP SIP.

CROXES-20398 CROXES-20398 Major endUser_prebetaSystem [Related] : Conference call impossible if main device Out Of Order.

List of all Reports


CROXE-12550 CROXE-12469 Major software [Report] : M4-User 'ccfexc' is not created for country Qatar during swinst installation

CROXES-21739 CROXES-18401 Major endUser_acceptance [Report] : [Related] : //1893_OT//Call from OTC PC to public busy destination does not hear busy tone

CROXES-21740 CROXES-17424 Major endUser_customerSite [Report] : [Related] : DTMF no working for OTC smartphone connection user if we call Voice mail.

CROXES-21700 CROXES-20428 Major endUser_customerSite [Report] : [Related] : //1893_OT_ESC//Call can not be retrieved from OTPC Client

CROXES-21718 CROXES-20436 Major endUser_customerSite [Report] : [Related] : Call has been lost after 30" when OTCPC call another OTCPC through the RP .

CROXES-21719 CROXES-20419 Major endUser_customerSite [Report] : [Related] : //1893_OT_ESC// No RBT for outgoing calls from OT user using PRA-T2 PSTN Trunk with OXE system

CROXES-21773 CROXES-21741 Major None [Report] : Problem in immediate forwarding for analog sets




























19.12 M3.402.26.A R12.2 MD4

List of all fixes


CROXES-7097 CROXES-7097 Major endUser_labSystem ECM mode not taken in account with external gatewy declared + T38 to G711 fall back

List of all Reports

IISUE KEY MAIN CR PRIORITY HOW FOUND SUMMARY

CROXE-12258 CROXE-10230 Major endUser_customerSite [Report] : //1893_LSY// No possibility to set the Bootfilename in Class VHENOE and SIP80x8s

CROXE-12393 CROXE-12219 Major software [Report] : Netadmin conversion after linux data base restoration failing

CROXE-12398 CROXE-6449 Major endUser_customerSite [Report] : shelf with CS3 adn GD3 is not powered off

CROXE-12392 CROXE-12284 Major software [Report] : [Related] : M3-FSNE [Feature]: Backporting of CROXE-9409 and CROXE-11346 (Development done in M4) - Infra Part

CROXE-12259 CROXE-10700 Major validation_funcManual [Report] : M3-IP-xBS: Master & Backup stations are "External Locked" together

CROXE-12261 CROXE-11907 Major endUser_customerSite [Report] : ALE PROD: OXE WBM does not authorize login anymore with R12.2 m3.402.25.a

CROXE-12263 CROXE-9991 Major validation_funcManual [Report] : OXE:M3: Unwanted # symbol is displayed during patch installation(M3.402.24 #2)

CROXE-12262 CROXE-11562 Major endUser_labSystem [Report] : M4 FNSE: wrong lanpbx file is generated

CROXES-20925 CROXES-20225 Major endUser_customerSite [Report] : OFS inbound faxes were received since then as successful but some pages are truncated.

CROXES-20923 CROXES-10884 Major endUser_customerSite [Report] : OXE: G.711 Fax Passthrough ? Interworking Issue between OFC R7.5 and OXE R11.1 (3% Failure).


























CROXES-21571 CROXES-21366 Major endUser_customerSite [Report] : SNMP counters for IP Domain and Trunk Group do not work anymore in patch m3.402.25.a.

CROXES-21573 CROXES-20887 Major endUser_customerSite [Report] : //1893_LSY// GD-3 Power OFF issue

19.13 M3.402.26

List of all fixes


CROXE-7751 CROXE-7751 Minor validation_nonRegression OXE-M3 NRT: Lanpbx requests to "Save modifications" when no modifications have been done

CROXE-11436 CROXE-11436 Major endUser_prebetaSystem [Related] : [Report] : rainbowagent does not initialize... linux

CROXE-11435 CROXE-11435 Major endUser_prebetaSystem [Related] : [Report] : rainbowagent does not initialize... mao part

CROXE-11081 CROXE-11081 Minor endUser_customerSite //1893_LSY//No audio during conference on OXO extensions.

CROXE-9517 CROXE-9517 Blocker validation_funcManual M3-IP-xBS: conference call without audio after an EHO (IBS)

CROXE-9938 CROXE-9938 Major endUser_customerSite mao translation error, shelf 0 not moved/changed after mao translation

CROXE-9742 CROXE-9742 Minor endUser_customerSite Protocol error on Alcatel 8&9 series, type 14

CROXE-11249 CROXE-11249 Minor integration_funcManual Cloud Connect: Missing error cause in message

CROXE-9889 CROXE-9889 Minor endUser_customerSite Bad behavior the Mobile REX agent seem to be in a CCD call but in fact the agent are in idle state.

CROXE-10699 CROXE-10699 Major endUser_customerSite Audio Transmission problem from 8001 SIP Phone Set to CCD Pilot - CCD Agent (recorded on TDM DR-Link)

CROXE-10105 CROXE-10105 Minor endUser_customerSite Duplicated of CROXE-9286 : overflow on entity via SIP ABCF when DECT ahndset out of service

CROXE-10156 CROXE-10156 Major endUser_customerSite //1893_LSY// Isuue with short ring trunk supervision

CROXE-7905 CROXE-7905 Minor endUser_labSystem Wrong agent real-time state : Busy tone

CROXE-10734 CROXE-10734 Critical endUser_customerSite redundancy is not able to initialize since bascul

CROXE-11912 CROXE-11912 Major validation_funcManual SIPTLS:M3:LDI: CAC block is observed during Hold/Retrieve

CROXE-9120 CROXE-9120 Minor endUser_customerSite swinst: 'Set maximum authentication attempts' does not work

CROXE-11069 CROXE-11069 Minor software_analysisTool Code Optimization for FSNE in M3 based on COCO tool

CROXE-9701 CROXE-9701 Major validation_funcManual M3-8088 NOE with Rainbow : MLA (or) Agent NOE Incoming












































Call during Rainbow Communication is NOK

CROXE-10126 CROXE-10126 Minor endUser_customerSite No answer while opening users, shelf, etc.

CROXE-11405 CROXE-11405 Minor integration_funcManual Cloud Connect: Debug Trace level facility to ccprocess

CROXES-20815 CROXES-20815 Major validation_funcManual OT-OXE/M3 : Call disconnects with a backtrace when transfered to local user during 6 party conference

CROXES-20607 CROXES-20607 Minor endUser_prebetaSystem Sendonly for hold value is not in "sipextgw -g" command

CROXES-20621 CROXES-20621 Minor validation_funcManual OXE:M3: Abnormal IBS incidents Observed during RUNTEL

CROXES-20111 CROXES-20111 Major validation_funcManual OXE/M3: 8039 set resets twice when replacing a 4029 set

CROXES-20693 CROXES-20693 Major validation_funcManual OXE/M3: Wake-up failed cases with Voice Guide 0/1

CROXES-19772 CROXES-19772 Minor endUser_customerSite Fault with "Wake-up" since upgrade in R12.2

CROXES-20592 CROXES-20592 Major endUser_customerSite No voice in one direction during external ISDN calls after time

CROXES-20296 CROXES-20296 Major endUser_customerSite 2677=Maoagent : Exception 11, operation GET, objet No 917593 , PC = 0x0813d7f4

CROXES-20770 CROXES-20770 Minor endUser_labSystem xBS not in service since upgrade OXe 12.2.22c to patch 24a

CROXES-20818 CROXES-20818 Major endUser_customerSite Wrong caller information on GAP+ when main set is OOS

CROXES-20945 CROXES-20945 Minor software DB Translation for M3.402.26

CROXES-21095 CROXES-21095 Minor software_analysisTool M3-Klocwork Bug// Pointer 'ptdcom_ipp' and 'ptdcom_sip' returned from call to function 'interro_neqt' may be NULL

CROXES-19547 CROXES-19547 Major endUser_customerSite Compressors on INTIP3A are blocked

CROXES-19643 CROXES-19643 Major endUser_customerSite GD never comes back in service after CPU switchover

CROXES-21238 CROXES-21238 Major validation_funcManual SIPTLS M3/LDI: No Voice path btn Remote worker user & OXE user in loopback scenario

CROXES-21349 CROXES-21349 Blocker validation_funcManual No voice path between Set and DECT after EHO in IP-xBS

CROXES-20220 CROXES-20220 Minor endUser_customerSite [Related] : REST API no events received when remote party releases an incoming call

CROXES-21210 CROXES-21210 Major validation_funcManual OXE:SIPTLS:M3:LDI: CAC block is observed everytime when OXE does Hold-retrieve.

CROXES-19930 CROXES-19930 Major endUser_customerSite remote install PCS failled with PC installer 5.5

CROXES-21409 CROXES-21409 Critical validation_funcManual After the EHO, Call is disconnected automatically from DECT and SEPLOS

CROXES-20226 CROXES-20226 Minor endUser_customerSite Incidents 2040 on Standby CPU

List of all Reports


CROXE-11375 CROXE-11267 Major endUser_prebetaSystem [Report] : dfmf not sent to external SIP trunk from dect XBS

CROXE-11061 CROXE-10219 Major endUser_prebetaSystem

[Report] : Multi-tenant config: during the creation of an OXE user with several devices there is an error message linked to domain ID

CROXE-11230 CROXE-9899 Major validation_funcManual [Report] : OXE-M4:OXE WBM access should be disabled for
























































radius users other than mtcl account

CROXE-11229 CROXE-10880 Major integration_funcManual [Report] : M4: Error incidents observed during RUNTEL

CROXE-11231 CROXE-10435 Major validation_funcManual [Report] : M3-IP-xBS: OXE internal syslog server shall implement log file rotation


[Report] : //1893_LSY// no audio between OT Conversation user from node 1 and OXE user from node 2, after a transference from user OXE in node 2

CROXE-11806 CROXE-11391 Major endUser_labSystem [Report] : OXE M4 Wrong Welcome title for OS

CROXE-11697 CROXE-8251 Major endUser_customerSite [Report] : For external SIP calls, DTMF is not recognized when ABC-F2 is used

CROXE-11233 CROXE-10369 Major validation_nonRegression [Report] : OXE-M4-NRT: M4.301 Patch installation is failed in CPU8

CROXE-11809 CROXE-10717 Major validation_nonRegression [Report] : OXE-M4-NRT: Application software validity checking is NOK in encrypted OXE

CROXE-11202 CROXE-10088 Major validation_funcManual [Report] : M4-NRT: DSU log on over network fails and multi line key which is used to log on freezes

CROXE-11722 CROXE-11253 Major validation_nonRegression [Report] : M4-NRT: Unwanted ? symbol is displayed when Attendant makes an External Call in US DB

CROXE-11975 CROXE-10739 Major validation_funcManual [Report] : SIPTLS NRT: Back trace during chained call with TLS user

CROXE-11981 CROXE-10679 Major validation_funcManual [Report] : SIPTLS NRT: Encryption lock symbol is missing after hold and retrieval

CROXE-10449 CROXE-10820 Major validation_funcManual [Report] : M3-IP-xBS: Campus Half com when DECT calls a SEPLOS 8001 and DECT returns to home node

CROXE-11644 CROXE-11447 Major validation_funcManual [Report] : M4-IP-xBS: external call: loss of audio after cpu switching and eho

CROXE-11968 CROXE-11651 Major endUser_customerSite [Report] : PR-00362419//Oxe stopped sending outgoing accounting registers for Trunk - Trunk transit calls.

CROXE-11403 CROXE-11386 Major endUser_prebetaSystem [Report] : rainbowagent does not initialize correctly on prebeta node99

CROXE-12073 CROXE-11793 Major integration_funcManual [Report] : OXE-M4: Weekly & monthly periodic Database Backup is not being taken automatically.

CROXE-11527 CROXE-10600 Major endUser_labSystem

[Report] : CCO: Failed to send the data into the SOCKS5 connexion for Get offer or Inventory when a proxy is configured on OXE

CROXE-7898 CROXE-7870 Major validation_funcManual [Report] : OXE M3:PCS Remote instalation:Missing of console information while running install script.

CROXES-20868 CROXES-19985 Major endUser_customerSite [Report] : //1893_LSY// Failure to send an "Alert" message

CROXES-20849 CROXE-9488 Major endUser_customerSite [Report] : Attendant call to a Blocked Pilot do not follow block address with Entity number

CROXES-20924 CROXES-18710 Major endUser_customerSite [Report] : freeze GD after switch restart for upgrade

CROXES-21162 CROXES-18632 Major endUser_customerSite [Report] : Unable read voicemail by clicking on the visual voicemail play icon in the OTC PC

CROXES-21124 CROXES-18915 Major endUser_customerSite [Report] : prsdebug maintenance tool doesn't work anymore

CROXES-20869 CROXE-8107 Major endUser_customerSite [Report] : Transmission DTMF in SIP for conference call




















































CROXES-20851 CROXES-19700 Major validation_funcManual [Report] : OXE M1: Analog set doesn't come inservice after patch upgrade from m1.403.24 #2 to m1.403.24 #3

CROXES-21130 CROXES-18844 Minor endUser_customerSite [Report] : Fail license to cloudconnect services

CROXES-20853 CROXES-17338 Major endUser_customerSite [Report] : OXE TFTP phone binary upgrade stategy

CROXES-21167 CROXES-18662 Major endUser_customerSite [Report] : The operators can no longer forward callers to a users mailbox.

CROXES-21189 CROXES-19523 Major endUser_customerSite [Report] : Need to remove the call charging for ABCF Transit call//00318590//


[Report] : M3-FSNE: Unwanted Warning Messages thrown while login into GD3/INTIP3boards using cpl_online command

CROXES-20855 CROXES-17566 Major endUser_customerSite [Report] : Blank info & perso screen observed on physical sets//1-219797003//

CROXES-20875 CROXE-9931 Major endUser_customerSite [Report] : //1893_LSY// The ID's generated at destination needs to be swapped.

CROXES-20556 CROXES-20501 Major endUser_customerSite [Report] : [Related] : Fault with "Wake-up" since upgrade in R12.2

CROXES-21232 CROXES-18924 Major endUser_customerSite [Report] : When IPP is recordable, no acces to its SIP VM possible

CROXES-21175 CROXE-10415 Major software_analysisTool

[Report] : Klockwork CR for M4.101.1 build - Pointer 'p_rall_sip_device' checked for NULL at line 2705 will be dereferenced at line 2714.

CROXES-20852 CROXES-18855 Major validation_funcManual [Report] : OXE:M1:Call between SIPDEVICE is failed with "Forbiden " message when Identity Secrecy is enabled.


[Report] : Need to know the timer is used for Maximum time on hold of trunk transferred before coming back to attendant when a 4059 attendant does the transfer.

CROXES-20874 CROXE-8069 Major endUser_customerSite [Report] : Operator 4059-IP cannot change forward

CROXES-21168 CROXES-4050 Major endUser_customerSite [Report] : SIP ABCF call lost after RE_INVITE (hold)

CROXES-20906 CROXES-16367 Major endUser_customerSite [Report] : Pilot : One Way call in transfert

CROXES-20877 CROXE-6879 Major endUser_customerSite [Report] : 2nd VG not played but silence for VG duration in RSI scenario

CROXES-21225 CROXES-19473 Major endUser_customerSite [Report] : Problem of overflow from one SIP GW to another

CROXES-20850 CROXES-16334 Major endUser_customerSite [Report] : IPDECT EI Sistema no responde (System does not respond)

CROXES-21197 CROXE-11166 Major validation_funcManual [Report] : M4-FSNE: In normal redundancy Standby goes to shutdown after giving RUNTEL

CROXES-21151 CROXES-21089 Major software_analysisTool [Report] : M2-Klocwork Bug// 'ptd' is used uninitialized in this function// 58464

CROXES-21024 CROXES-20291 Major endUser_customerSite [Report] : Lot of incidents 4403 Error 5 & 13 on message type 1 on OMS // 00345888 // m2.300.21.a

CROXES-21377 CROXES-21141 Major endUser_customerSite [Report] : Too long user-to-user info header with CSTA Correlator Data tag 4580 causes SIPmotor crashes

CROXES-21133 CROXES-19701 Minor endUser_customerSite [Report] : Following bascul, zdmict0 command not working correctly / OXE / R12.0 m1.403.19.a





















































[Report] : M4: Enquiry call to the network set gets disconnected when local CAMP ON call is made to the same set.

CROXES-20876 CROXES-16944 Major endUser_customerSite [Report] : Calls is not distributed to pilot after be routed through entity call Prefix.

CROXES-21170 CROXE-9435 Major validation_funcManual [Report] : M4-FSNE: LS announcement is non encrypted for a Set which is already in a encrypted conversation

CROXES-20981 CROXE-10195 Major validation_funcManual [Report] : M4-FSNE/Thales_XBS: No Voice between IP DECT and other sets when Authentication for SRTP is set

CROXES-21031 CROXES-20158 Major endUser_customerSite [Report] : [Related] : Forward on No answer and Busy not working with OTC smartphone if SIP extension OOS

CROXES-21026 CROXES-20200 Major endUser_customerSite [Report] : one way communication during individual hold from attendant

CROXES-21021 CROXES-20187 Major endUser_customerSite [Report] : strong noise while external caller is setting remote extension to hold

CROXES-21022 CROXES-20330 Major endUser_customerSite [Report] : SRTP : call pickup between nodes causes strong noise

CROXES-21381 CROXES-21303 Major endUser_customerSite [Report] : 4059 EE individual hold fall back to attendant not working

CROXES-21012 CROXES-19716 Major endUser_customerSite [Report] : 4059 EE strong noise when connecting

CROXES-21011 CROXES-19983 Major endUser_customerSite [Report] : 4059 strong noice when 4059 transfers a call from node 1 to node 2

CROXES-20867 CROXES-15507 Major endUser_customerSite [Report] : CSTA no call id for a user events

CROXES-21178 CROXE-10633 Major validation_nonRegression [Report] : OXE-M4-NRT: Backtrace occurs when immediate forward configured in hotel set

CROXES-21123 CROXE-9519 Minor endUser_customerSite [Report] : GE: Incidents 2656=Incoherent data: appli CMIS_SAVE table POSTE (xx) / OXE / R12.1 m2.300.22.a

CROXES-21378 CROXES-21155 Major endUser_customerSite [Report] : short strong noise if caller is placed into conference


[Report] : SIP-SRTP : External call (to N2) to attendant on N1 transferring to a hunt group in N2. During circular ringing to the sets in the hunt group, there is noise

CROXES-21177 CROXE-10418 Major validation_nonRegression [Report] : M4 NRT - No RBT when DECT makes callback to Attendant

CROXES-21171 CROXE-9778 Major software [Report] : [OPUS] unable to deactivate OPUS (SWB) to use G722 (WB)

CROXES-21029 CROXES-20218 Major endUser_customerSite [Report] : SIP-SRTP : SIP calls SIP extension. Transfer to IPP, no voice

CROXES-21020 CROXES-20152 Major endUser_customerSite [Report] : strong during transfer from remote worker 8001 set

CROXES-21030 CROXES-20865 Major endUser_customerSite [Report] : 8001 remoteworker one way communication if an enquiry call to node 1 is transfered to external

CROXES-21176 CROXES-20496 Major endUser_customerSite [Report] : SIP Law A & Law MU : OXE doesn't respect the correct low

CROXES-21169 CROXE-9153 Major endUser_customerSite [Report] : Calls drop when dtmf is sent before conferencing 2 calls//00327064// - OXE L2.300.30




















































CROXE-11579 CROXE-10880 Major endUser_customerSite //1893F_LSY_RR// Migration R12.2 M3.402.24.A : NGINX ERROR

CROXE-10672 CROXE-9763 Minor endUser_customerSite //1893_LSY// Audio is interrupted when second call is answered

CROXE-11862 CROXE-10126 Major endUser_customerSite No answer while opening users, shelf, etc. with 2663 incident

CROXE-10773 CROXE-10449 Major validation_funcManual M3-IP-xBS: DECT half communication during a conference with SEPLOS + EHO

CROXE-11766 CROXE-10126 Minor endUser_customerSite Unable to Review/modify any component in mgr.

CROXE-10933 CROXE-10126 Minor endUser_customerSite mgr access locked with the Incident 2630=SQL error: appli CMISE table No. 2650 error -26003

CROXE-11335 CROXE-10126 Major endUser_customerSite mgr locks up after disabling/enabling virtual add-on key in 8058s phones

CROXE-11835 CROXE-10126 Minor endUser_customerSite With 8058s phones, mgr not functioning and getting error 2663ibcchruserrappli MAO agent oper 6 err-1

CROXE-11929 CROXE-11403 Minor endUser_customerSite rainbowagent does not initialize correctly after OXE update

CROXE-10900 CROXE-10126 Major endUser_customerSite Mao blocked. Unable to do any configurations


//1893_LSY//City of Ocala -- when 8058S phone is created and virtual add on is not checked, locks up MGR and call center and double bascul is needed to clear

CROXES-20595 CROXES-20592 Minor endUser_customerSite One way voice connections in during external calls after update to R12.2// 00351416 // m3.402.13.f

CROXES-21172 CROXE-8251 Major endUser_customerSite Request for HF CROXE-8251 TEL.111 in R12.2 m3.402.24a

CROXES-21174 CROXES-19643 Major endUser_customerSite //HT OK L3 HL// URGENT problem with OXE guardia civil

CROXES-20890 CROXE-11447 Major endUser_customerSite Major Issue with handover from XBs to RBS - UZ Brussel

CROXES-21224 CROXE-11447 Major endUser_customerSite Handover IBS-IPxBS in conversation doesn't work.

19.14 M3.402.25.A R12.2 MD3

List of all Reports





































CROXE-11430 CROXE-11230 Major validation_funcManual [Report] : [Report] : OXE-M4:OXE WBM access should be disabled for radius users other than mtcl account

CROXE-11526 CROXE-9517 Major validation_funcManual [Report] : M3-IP-xBS: conference call without audio after an EHO (IBS)

CROXE-11427 CROXE-9120 Major endUser_customerSite [Report] : swinst: 'Set maximum authentication attempts' does not work

CROXE-11425 CROXE-11229 Major integration_funcManual [Report] : [Report] : M4: Error incidents observed during RUNTEL

CROXE-11428 CROXE-10369 Major validation_nonRegression [Report] : OXE-M4-NRT: M4.301 Patch installation is failed in CPU8


[Report] : //1893_LSY// no audio between OT Conversation user from node 1 and OXE user from node 2, after a transference from user OXE in node 2

CROXE-11429 CROXE-11231 Major validation_funcManual [Report] : [Report] : M3-IP-xBS: OXE internal syslog server shall implement log file rotation

CROXE-11426 CROXE-10600 Major endUser_labSystem

[Report] : CCO: Failed to send the data into the SOCKS5 connexion for Get offer or Inventory when a proxy is configured on OXE

CROXES-20999 CROXES-19547 Major endUser_customerSite [Report] : Compressors on INTIP3A are blocked

CROXES-20997 CROXES-18710 Major endUser_customerSite [Report] : freeze GD after switch restart for upgrade

CROXES-20979 CROXE-11023 Major validation_funcManual [Report] : M4-FSNE/Thales_XBS: Signature needed on clear DL link also when node is in Thales or FSNE mode.

CROXES-20931 CROXE-9938 Major endUser_customerSite [Report] : mao translation error, shelf 0 not moved/changed after mao translation

CROXES-20998 CROXES-19643 Major endUser_customerSite [Report] : GD never comes back in service after CPU switchover

CROXES-20971 CROXES-20592 Major endUser_customerSite [Report] : No voice in one direction during external ISDN calls after time


[Report] : M3-FSNE: Unwanted Warning Messages thrown while login into GD3/INTIP3boards using cpl_online command

CROXES-20970 CROXES-20770 Major endUser_labSystem [Report] : xBS not in service since upgrade OXe 12.2.22c to patch 24a

CROXES-20628 CROXES-20296 Major endUser_customerSite [Report] : 2677=Maoagent : Exception 11, operation GET, objet No 917593 , PC = 0x0813d7f4

CROXES-20978 CROXE-10195 Major validation_funcManual [Report] : M4-FSNE/Thales_XBS: No Voice between IP DECT and other sets when Authentication for SRTP is set

19.15 M3.402.25

List of all fixes









































CROXE-10106 CROXE-10106 Major software [Rainbow - Hospitality environment] OXE shall indicate the Hotel users as can be monitored

CROXE-10150 CROXE-10150 Minor software_analysisTool Klocwork corrections for Auto re-registration feature

CROXE-10061 CROXE-10061 Blocker validation_funcManual M3-IP-xBS: Campus IBS: half communication in visited node after EHO from xBS to IBS

CROXE-9776 CROXE-9776 Minor validation_funcManual M3 Regression: Help text Missing for parameter 'From Display Name' in SIP parameters

CROXE-9103 CROXE-9103 Minor validation_nonRegression OXE-M3-NRT:Junk display observed during MDU ringing with Main tandem OOS.

CROXE-9023 CROXE-9023 Minor software [M3 IP-xBS] xBS registration is not closed

CROXE-9449 CROXE-9449 Major endUser_customerSite \\S3 Requested\\ //1893F_LSY_RR//In virtual mode issue with OS

CROXE-10561 CROXE-10561 Major endUser_betaSystem Request to RnD to integrate new infocollect 5.5

CROXE-9639 CROXE-9639 Major validation_funcManual M3-8088 NOE with Rainbow : Incoming NOE call to Rainbow Video User after Switch Over is NOK

CROXE-9535 CROXE-9535 Major endUser_customerSite CPU8 with RMA Alarm: Red led on RMAB not lit and loop state not changed when CPU8 is shutdowning

CROXE-9357 CROXE-9357 Minor endUser_customerSite GE: Backtraces abbreg_appelant 0x083d8196 / OXE / R12.2 m3.402.13.f

CROXE-10240 CROXE-10240 Major endUser_alpha Alpha Autoreg : ReinstallSuccess/NOKHandsetsList.txt must give details command

CROXE-10547 CROXE-10547 Major endUser_customerSite //1893_LSY// No voice call from VMP 4059 to a reflex set without Multiline //CUST: OK-Lahr

CROXE-9745 CROXE-9745 Major endUser_customerSite ACR not working after ALB got frozen

CROXE-9312 CROXE-9312 Minor endUser_betaSystem [R12.2] Change in Multi Pari configuration when adding a new PARI

CROXE-9939 CROXE-9939 Major endUser_prebetaSystem [M3 IP-xBS] Radio Base Type: Help text and behavior

CROXE-9891 CROXE-9891 Major integration_funcManual [M3 IP-xBS] Master and Backup must always be shown in dectview xbs

CROXE-9960 CROXE-9960 Minor endUser_customerSite OXE-M3: Auto Reg_Output Tool statement not displayed in OXE window

CROXE-10083 CROXE-10083 Major integration_funcManual RAINBOWAGENT: Lost of first REST messages after the WSS initialization

CROXE-10394 CROXE-10394 Major validation_nonRegression OXEM4:NRT: Error message observed during inactive part installation of static patch installation

CROXE-8804 CROXE-8804 Major validation_funcManual OXE M3: Hyper-V: Unable to enable QoS in Hyper-V OXE-VM

CROXE-8965 CROXE-8965 Major validation_funcManual OXE M3: OXE Inventory: IPT terminal type are repeated twice with case sensitive

CROXE-7905 CROXE-7905 Minor endUser_labSystem Wrong agent real-time state : Busy tone

CROXE-10664 CROXE-10664 Minor endUser_customerSite GE: multitool command doesn't work anymore as expected / OXE / R12.2 m3.402.23

CROXE-10755 CROXE-10755 Critical endUser_customerSite GAP+ first & last names creation issue on standby















file://///S3








































CROXE-10721 CROXE-10721 Minor endUser_customerSite RSI no charging script “Taxsda3” is not working in case of interruptible voice and collect digits

CROXE-10852 CROXE-10852 Major validation_funcManual M4-QATAR Contry Management: Empty DB created with wrong country UAE instead of QATAR on SOT Installation

CROXE-9965 CROXE-9965 Minor endUser_labSystem Wrong EWT in alb server

CROXES-20288 CROXES-20288 Major validation_funcManual ACR call is not working when the Native Encryption is Enabled and Disabled

CROXES-20297 CROXES-20297 Major validation_funcManual No Voice path between TDM and DECT(XBS) when the TDM calls local RSI with interrupted voice guide

CROXES-20609 CROXES-20609 Critical validation_funcManual OXE/M3: WBM is not working in spatial redundancy nodes

CROXES-20299 CROXES-20299 Minor endUser_customerSite //1893_LSY//Partition duplication through swinst menu is not working in m3.402.22.c.

CROXES-19931 CROXES-19931 Minor endUser_customerSite backtrace occured when "looknpd i" command is run

CROXES-19496 CROXES-19496 Minor validation_funcManual OXE/M3 : No 'Hands-free Disabled' pop-up when supervisor answers the call using softkey


[Related] : ALE PROD Bad TO in INVITE when calling from network or local a remote in tandem (mobile phone ringing)-MAO part

CROXES-20049 CROXES-20049 Major endUser_customerSite REX is still forwarded to associate after a reset when Overflow If Out Of Service is set

CROXES-19614 CROXES-19614 Minor validation_funcManual OXE:M3:Incident 2667/2685`is generated when 8018/8008set is made OOS by prefix

CROXES-20531 CROXES-20531 Minor endUser_acceptance OXE R12.2: MWI does not work on ASCOM MyCo Sets

CROXES-20201 CROXES-20201 Major validation_funcManual OXE M3:Unable to modify user parameters when native encryption is enabled in terminal and FSNE disabled in node

CROXES-19906 CROXES-19906 Minor endUser_customerSite standby CPU is not able to start in spatiale redundancy

CROXES-20171 CROXES-20171 Major validation_funcManual OXE:M3: Unwanted ? symbol is displayed when Attendant makes an External Call

CROXES-20372 CROXES-20372 Major endUser_customerSite [Related] : A lot of Shudown of CS after upgrade in R12.1

CROXES-19511 CROXES-19511 Minor validation_funcManual OXE/M3:"Disable Loudspeaker on IP Phones" feature is not working while picking a call via add-on module

CROXES-20859 CROXES-20859 Major validation_funcManual OXE/M3 : Secondary MLA is not alerted if it is a 8088 User

CROXES-20782 CROXES-20782 Blocker validation_funcManual Backtrace occurs when the agent set type is changed

CROXES-20858 CROXES-20858 Blocker validation_funcManual gdump is not working and remanent error occurred

List of all Reports


CROXE-10254 CROXE-9829 Major endUser_alpha [Report] : Alpha nu11 : loss audio in DECT/DECT call after EHO XBS/RBS

CROXE-10252 CROXE-9657 Major validation_funcManual [Report] : M3-IP-xBS: call without audio after a record+EHO from IBS to IP-xBS


















































CROXE-10253 CROXE-9670 Major validation_funcManual [Report] : 4400 Mixed: After multiple handset EHO RBS to IP-XBS, sometimes audio lost on handsest

CROXE-10255 CROXE-9856 Major validation_funcManual [Report] : M3-IP-xBS: Second incoming call tone is missing after an EHO from xBS to RBS

CROXE-10589 CROXE-10131 Major endUser_customerSite [Report] : [Security] WBM access vulnerability

CROXE-10581 CROXE-10370 Major validation_funcManual [Report] : M3-IP-xBS: Campus IBS: Conference is lost after campus handover

CROXE-10577 CROXE-10342 Major validation_funcManual [Report] : M3-IP-xBS: Campus IBS: no audio after loss of visited IBS station


[Report] : OMS / deleting dynamic voice guide assignment when it’s broadcasting caused OMS to go OUT OF SERVICE and it don’t come back IN SERVICE // 00319283 // l2.300.39

CROXE-11027 CROXE-9763 Major endUser_customerSite [Report] : //1893_LSY// Audio is interrupted when second call is answered.

CROXE-10506 CROXE-8487 Major endUser_customerSite [Report] : //1893F_LSY_RR// Probleme de localisation DECT suite au changement de version en R12.1

CROXE-10750 CROXE-7785 Major endUser_customerSite [Report] : SIP Trunk Disconnect ohne Direction after 32 seconds in Call

CROXE-10610 CROXE-10424 Major software_analysisTool [Report] : Klockwork M4.101.1

CROXE-10689 CROXE-8152 Major endUser_customerSite [Report] : Hot Fix needed for backtrace tandem_main_is_oos - m1.403.21.a

CROXE-10686 CROXE-8652 Major endUser_customerSite [Report] : After bascul: Error with user agent ringing volume ringing melody

CROXE-10376 CROXE-9851 Major validation_funcManual [Report] : M3 : IP-xBS 6078 incident is not observed during master xBS loss the sync data

CROXE-10896 CROXE-9042 Major validation_funcManual [Report] : M4: OMS logs get increased to 100% and goes OOS

CROXE-10870 CROXE-10640 Major validation_funcManual [Report] : Radius users which contain space characters cannot authenticate in SSH


[Report] : //1893_LSY//Belgian Army // Username which contain space characters cannot authentificate through Radius

CROXE-10895 CROXE-10229 Major software [Report] : [Report] OMS SuSE SP3 8.xx : ssh connection is not restricted to OXE CS when enabled

CROXE-10678 CROXE-9898 Major endUser_customerSite [Report] : //1893_LSY_RR// GE: Incident 2687 shows wrong nulog / OXE / R11.2.2 l2.300.41

CROXES-20411 CROXE-10239 Major endUser_alpha [Report] : Alpha Autoreg : ForceUpdate -f file should not work with PARI or PLI only

CROXES-20408 CROXE-10080 Major validation_funcManual [Report] : OXE-M3: After Auto Re-registration HS details not updated in Output file during Bascul and Reboot Scenario

CROXES-20526 CROXES-19458 Major software_analysisTool [Report] : M2-Klocwork Bug// Too many parameters provided for sprintf function// 58416 // CROXES-17408

CROXES-20472 CROXES-19923 Major endUser_customerSite [Report] : crash CPU7s2 and CPU8 after restart mailsys process

CROXES-20551 CROXES-18510 Major endUser_customerSite [Report] : //1893_LSY_RR// 4645 Issue Too much voice mails


















































CROXES-20675 CROXES-19254 Major endUser_customerSite [Report] : OMS did not reconnect automatically after network outage

CROXES-20718 CROXES-19827 Major endUser_customerSite [Report] : Bad behavior of OMS when number of free compressors is 1

CROXES-20533 CROXES-14506 Major endUser_customerSite [Report] : Fron 4074 to GAP+

CROXES-20555 CROXES-18096 Major endUser_customerSite [Report] : //1893_LSY_ESC// After upgrade to 12.1 incvisu log doesn't show

CROXES-20391 CROXE-9770 Major None

[Report] : OXE-M3:DECT auto re-registration - PARK compatibility check must be implemented in Call handling(MM)

CROXES-20745 CROXE-6998 Major endUser_customerSite [Report] : SNMP Trap 1378/1381 has wrong class / missing informationsOXE / R12.1 m2.300.18.d

CROXES-20578 CROXES-20056 Major endUser_customerSite [Report] : [Related] : Regression: No outgoing T38 Fax from MP124 since OXE Upgrade - MAO Correction

CROXES-20581 CROXES-19527 Major endUser_customerSite [Report] : Regression: No outgoing T38 Fax from MP124 since OXE Upgrade

CROXES-20575 CROXES-18521 Major endUser_customerSite [Report] : ALE PROD Bad TO in INVITE when calling from network or local a remote in tandem (mobile phone ringing)

CROXES-20583 CROXES-14422 Major validation_nonRegression [Report] : /CCX/m1.403/call profile name and skills are not showing in CCS

CROXES-20674 CROXES-20582 Major software [Report] : Randmonly OMS rebooting several time before coming to service


[Report] : //1893_LSY_RR// GE: CPU7-2 crash if termstat command is executed too early during system start / OXE / R12.1 m2.300.19

CROXES-20481 CROXES-16302 Major endUser_customerSite [Report] : IUU on SIP not working after double switchover

CROXES-20579 CROXES-18456 Major endUser_customerSite [Report] : [Related] : OTC Smartphone the 2nd ARS route on GSM doesn't work

List of all duplicates


CROXE-10367 CROXES-20299 Major endUser_customerSite \\S3 Requested\\ Partition duplication through swinst menu is not working in m3.402.24

CROXE-10496 CROXE-10664 Major validation_funcManual M3: OXE multitool command does not show number

CROXE-11072 CROXE-10664 Major endUser_customerSite GE: multitool command doesn't work anymore as expected / OXE / R12.2 m3.402.22.c

CROXE-11147 CROXE-10664 Minor endUser_customerSite //1893_LSY// issue with multitool

CROXE-10478 CROXE-10664 Major endUser_customerSite Database Error and Boss/Secretary Problem

CROXES-20725 CROXES-20782 Major validation_funcManual OXE/M3: Backtrace occurs while removing tandem

CROXES-19520 CROXES-19511 Minor validation_funcManual OXE/M3:"Disable Loudspeaker on IP Phones" feature is not working while picking the call on F1 or F2 key

CROXES-19629 CROXES-19906 Major endUser_customerSite Spatial redundancy: Standby does not come into service and restarts in loop when gateway does not respond to ping































file://///S3


















19.16 M3.402.24.a OXR R12.2 MD2

List of all fixes


CROXE-10370 CROXE-10370 Blocker validation_funcManual M3-IP-xBS: Campus IBS: Conference is lost after campus handover

CROXE-10342 CROXE-10342 Blocker validation_funcManual M3-IP-xBS: Campus IBS: no audio after loss of visited IBS station

CROXE-10229 CROXE-10229 Major software [Report] OMS SuSE SP3 8.xx : ssh connection is not restricted to OXE CS when enabled

CROXE-10239 CROXE-10239 Major endUser_alpha Alpha Autoreg : ForceUpdate -f file should not work with PARI or PLI only

CROXE-10080 CROXE-10080 Major validation_funcManual OXE-M3: After Auto Re-registration HS details not updated in Output file during Bascul and Reboot Scenario

CROXES-20582 CROXES-20582 Major software Randmonly OMS rebooting several time before coming to service

List of all Reports


CROXE-10649 CROXE-9535 Major endUser_customerSite [Report] : CPU8 with RMA Alarm: Red led on RMAB not lit and loop state not changed when CPU8 is shutdowning

CROXE-10645 CROXE-10106 Major software [Report] : [Rainbow - Hospitality environment] OXE shall indicate the Hotel users as can be monitored

CROXE-10387 CROXE-9657 Major validation_funcManual [Report] : M3-IP-xBS: call without audio after a record+EHO from IBS to IP-xBS

CROXE-10388 CROXE-9670 Major validation_funcManual [Report] : 4400 Mixed: After multiple handset EHO RBS to IP-XBS, sometimes audio lost on handsest

CROXE-10646 CROXE-9449 Major endUser_customerSite [Report] : \\S3 Requested\\ //1893F_LSY_RR//In virtual mode issue with OS

CROXE-10271 CROXE-9891 Major integration_funcManual [Report] : [M3 IP-xBS] Master and Backup must always be shown in dectview xbs

CROXE-10250 CROXE-9565 Major validation_funcManual [Report] : M3-IP-xBS: incident message is displayed after an EHO from xBS to IBS

CROXE-10251 CROXE-9758 Major validation_funcManual [Report] : M3-IP-xBS: One GD timeslot stays busy after xBS calls

CROXE-10361 CROXE-9517 Major validation_funcManual [Report] : M3-IP-xBS: conference call without audio after an EHO (IBS)

CROXE-10249 CROXE-9601 Major validation_funcManual [Report] : M3-IP-xBS: DECT call is sometimes suddenly























file://///S3














released

CROXE-10384 CROXE-9601 Major validation_funcManual [Report] : M3-IP-xBS: DECT call is sometimes suddenly released

CROXE-10385 CROXE-9565 Major validation_funcManual [Report] : M3-IP-xBS: incident message is displayed after an EHO from xBS to IBS


[Report] : //1893_LSY//Belgian Army // Username which contain space characters cannot authentificate through Radius

CROXE-10256 CROXE-9851 Major validation_funcManual [Report] : M3 : IP-xBS 6078 incident is not observed during master xBS loss the sync data

CROXE-10644 CROXE-10083 Major integration_funcManual [Report] : RAINBOWAGENT: Lost of first REST messages after the WSS initialization


[Report] : OMS / deleting dynamic voice guide assignment when it’s broadcasting caused OMS to go OUT OF SERVICE and it don’t come back IN SERVICE // 00319283 // l2.300.39

CROXE-10604 CROXE-10561 Major endUser_betaSystem [Report] : Request to RnD to integrate new infocollect 5.5

CROXE-10231 CROXE-9042 Major validation_funcManual [Report] : M4: OMS logs get increased to 100% and goes OOS

CROXE-10909 CROXE-10394 Major validation_nonRegression [Report] : OXEM4:NRT: Error message observed during inactive part installation of static patch installation

CROXE-10390 CROXE-9856 Major validation_funcManual [Report] : M3-IP-xBS: Second incoming call tone is missing after an EHO from xBS to RBS

CROXE-10912 CROXE-10762 Major integration_funcManual [Report] : OXE-M4: WBM connection failed with correct identifier and Password

CROXE-10911 CROXE-10640 Major validation_funcManual [Report] : Radius users which contain space characters cannot authenticate in SSH

CROXE-10642 CROXE-8487 Major endUser_customerSite [Report] : //1893F_LSY_RR// Problème de localisation DECT suite au changement de version en R12.1

CROXE-10362 CROXE-10061 Major validation_funcManual [Report] : M3-IP-xBS: Campus IBS: half communication in visited node after EHO from xBS to IBS

CROXE-10386 CROXE-9758 Major validation_funcManual [Report] : M3-IP-xBS: One GD timeslot stays busy after xBS calls

CROXE-10647 CROXE-6355 Major validation_funcManual [Report] : Cmisd : connection problem (?CCCA 99) incident observed during RUNTEL


CROXES-20530 CROXES-20299 Major endUser_customerSite [Report] : //1893_LSY//Partition duplication through swinst menu is not working in m3.402.22.c.

CROXES-20561 CROXES-20171 Major validation_funcManual [Report] : OXE:M3: Unwanted ? symbol is displayed when Attendant makes an External Call

CROXES-20529 CROXES-20372 Major endUser_customerSite [Report] : [Related] : A lot of Shudown of CS after upgrade in R12.1

CROXES-20560 CROXES-19254 Major endUser_customerSite [Report] : OMS did not reconnect automatically after network outage

CROXES-20680 CROXES-20609 Major validation_funcManual [Report] : OXE/M3: WBM is not working in spatial
















































redundancy nodes

CROXES-20553 CROXES-20297 Major validation_funcManual [Report] : No Voice path between TDM and DECT(XBS) when the TDM calls local RSI with interrupted voice guide

CROXES-20570 CROXES-20288 Major validation_funcManual [Report] : ACR call is not working when the Native Encryption is Enabled and Disabled

CROXES-20624 CROXES-20296 Major endUser_customerSite [Report] : 2677=Maoagent : Exception 11, operation GET, objet No 917593 , PC = 0x0813d7f4

CROXES-20528 CROXES-19906 Major endUser_customerSite [Report] : standby CPU is not able to start in spatiale redundancy














CROXE-10073 CROXE-10061 Blocker validation_funcManual M3-IP-xBS: Half communication after IBS-xBS-IBS external handovers

19.17 M3.402.24

List of all fixes


CROXE-8069 CROXE-8069 Minor endUser_customerSite Operator 4059-IP cannot change forward

CROXE-9488 CROXE-9488 Major endUser_customerSite Attendant call to a Blocked Pilot do not follow block address with Entity number

CROXE-7785 CROXE-7785 Minor endUser_customerSite SIP Trunk Disconnect ohne Direction after 32 seconds in Call

CROXE-7691 CROXE-7691 Minor endUser_customerSite After Update to Rel 12.1 set supervision randomly not working Endkunde:Espelkamp//00285521//

CROXE-6879 CROXE-6879 Minor endUser_customerSite 2nd VG not played but silence for VG duration in RSI scenario

CROXE-9898 CROXE-9898 Minor endUser_customerSite //1893_LSY_RR// GE: Incident 2687 shows wrong nulog / OXE / R11.2.2 l2.300.41

CROXE-6998 CROXE-6998 Minor endUser_customerSite SNMP Trap 1378/1381 has wrong class / missing informationsOXE / R12.1 m2.300.18.d

CROXE-8040 CROXE-8040 Minor endUser_customerSite No DTMF sent by OMS when in 3 way conference // m2.300.13.g


OMS / deleting dynamic voice guide assignment when it’s broadcasting caused OMS to go OUT OF SERVICE and it don’t come back IN SERVICE // 00319283 // l2.300.39

CROXE-8483 CROXE-8483 Minor endUser_customerSite //1893_LSY// Mastered Conference Announcement - no auto pickup or audio either way

CROXES-20104 CROXES-20104 Major endUser_customerSite [Related] : [Report] : [Related] : SNMP process using too much swap because of get SNMP on OXE


[Related] : ALE PROD Bad TO in INVITE when calling from network or local a remote in tandem (mobile phone ringing)-MAO part

CROXES-18662 CROXES-18662 Minor endUser_customerSite The operators can no longer forward callers to a users mailbox.

CROXES-20173 CROXES-20173 Major validation_funcManual ? is shown in the menu page of 80x8s

CROXES-20407 CROXES-20407 Minor validation_funcManual unwanted Warning message is observed once after the stratup of RUNTEL

CROXES-19306 CROXES-19306 Major endUser_customerSite (with Hotfix CROXES 18861) Missing "+" in the called number






































leads that the call can’t be established

CROXES-19523 CROXES-19523 Major endUser_customerSite Need to remove the call charging for ABCF Transit call//00318590//

CROXES-19527 CROXES-19527 Major endUser_customerSite Regression: No outgoing T38 Fax from MP124 since OXE Upgrade

CROXES-20056 CROXES-20056 Major endUser_customerSite [Related] : Regression: No outgoing T38 Fax from MP124 since OXE Upgrade - MAO Correction

CROXES-18924 CROXES-18924 Major endUser_customerSite When IPP is recordable, no acces to its SIP VM possible

CROXES-20196 CROXES-20196 Major endUser_customerSite //1893_LSY// No outgoing fax at Audiocodes MP after upgrade 12.1 M2.300.13 -> 21a

CROXES-19808 CROXES-19808 Major endUser_customerSite Directory not sent to Rainbow

CROXES-20292 CROXES-20292 Major software_analysisTool M2-Klocwork Bug// 'twincpu_ip_address' array elements might be used uninitialized in this function. // 58445


//1893_LSY_RR// GE: CPU7-2 crash if termstat command is executed too early during system start / OXE / R12.1 m2.300.19

CROXES-18510 CROXES-18510 Minor endUser_customerSite //1893_LSY_RR// 4645 Issue Too much voice mails

CROXES-20260 CROXES-20260 Major software_analysisTool M2-Klocwork Bug// Void function returns value// 58443

CROXES-19254 CROXES-19254 Major endUser_customerSite OMS did not reconnect automatically after network outage

CROXES-19790 CROXES-19790 Minor endUser_customerSite //1893_LSY// GE: Missing infos in termstat command / OXE / R12.1 m2.300.19

CROXES-18521 CROXES-18521 Major endUser_customerSite ALE PROD Bad TO in INVITE when calling from network or local a remote in tandem (mobile phone ringing)

CROXES-19985 CROXES-19985 Minor endUser_customerSite //1893_LSY// Failure to send an "Alert" message

List of all Reports


CROXE-9421 CROXE-9351 Major endUser_prebetaSystem [Report] : Rainbow agent did not send all the users to Rainbow after a rainbowagent restart

CROXE-9786 CROXE-8136 Major endUser_customerSite [Report] : New callId generated on RSI routeRequest

CROXE-9785 CROXE-8791 Major endUser_customerSite [Report] : Agent DTMF issue


[Report] : CCD - wrong calling number (FROM) in SIP INVITE when calling from internal number towards PILOT that is in forward towards SIP ISDN trunk

CROXE-10142 CROXE-8107 Major endUser_customerSite [Report] : Transmission DTMF in SIP for conference call

CROXE-9618 CROXE-9153 Major endUser_customerSite [Report] : Calls drop when dtmf is sent before conferencing 2 calls//00327064// - OXE L2.300.30

CROXE-10493 CROXE-9535 Major endUser_customerSite [Report] : CPU8 with RMA Alarm: Red led on RMAB not lit and loop state not changed when CPU8 is shutdowning

CROXE-10144 CROXE-9931 Major endUser_customerSite [Report] : //1893_LSY// The ID's generated at destination needs to be swapped.

CROXE-10338 CROXE-9554 Major endUser_customerSite [Report] : //1893_LSY//Belgian Army // Username which


















































contain space characters cannot authentificate through Radius

CROXE-10492 CROXE-9449 Major endUser_customerSite [Report] : \\S3 Requested\\ //1893F_LSY_RR//In virtual

mode issue with OS

CROXE-10339 CROXE-8487 Major endUser_customerSite [Report] : //1893F_LSY_RR// Problème de localisation DECT suite au changement de version en R12.1

CROXE-10085 CROXE-10083 Major integration_funcManual [Report] : RAINBOWAGENT: Lost of first REST messages after the WSS initialization.

CROXES-20103 CROXES-19732 Major endUser_customerSite [Report] : [Related] : SNMP process using too much swap because of get SNMP on OXE


CROXES-19986 CROXES-19571 Major endUser_customerSite [Report] : KOMSA#57025515 — OXE wrong state of call forwarding key


[Report] : GE: Regression: Missing correction for crqms00153049 (Wrong german translation for display info "erreichtbar" instead of "erreichbar" / OXE / R10.1.1) / OXE / R12.x

CROXES-20093 CROXES-16367 Major endUser_customerSite [Report] : Pilot : One Way call in transfert

CROXES-20283 CROXES-15507 Major endUser_customerSite [Report] : CSTA no call id for a user events


CROXES-20352 CROXES-20171 Major validation_funcManual [Report] : OXE:M3: Unwanted ? symbol is displayed when Attendant makes an External Call

CROXES-20168 CROXE-7804 Major endUser_customerSite [Report] : INTIP Board crashes with backtrace on extract_T4_payload

CROXES-20110 CROXES-19906 Major endUser_customerSite [Report] : standby CPU is not able to start in spatiale redundancy

CROXES-20015 CROXES-15893 Major endUser_customerSite [Report] : CSTA Problem with EventDialing message sent from oxe to Genesis via CSTA.

CROXES-20043 CROXES-17479 Major endUser_customerSite [Report] : CCD agent Phone in blocked state

CROXES-20249 CROXES-16944 Minor endUser_customerSite [Report] : Calls is not distributed to pilot after be routed through entity call Prefix.

CROXES-20261 CROXES-16334 Major endUser_customerSite [Report] : IPDECT EI Sistema no responde (System does not respond)

CROXES-20267 CROXES-17566 Major endUser_customerSite [Report] : Blank info & perso screen observed on physical sets//1-219797003//

CROXES-20262 CROXES-19700 Major validation_funcManual [Report] : OXE M1: Analog set doesn't come inservice after patch upgrade from m1.403.24 #2 to m1.403.24 #3


CROXES-20125 CROXES-18862 Major endUser_betaSystem [Report] : Missing "+" in the called number leads to rejection by the SIP provider

CROXES-20462 CROXES-20372 Major endUser_customerSite [Report] : [Related] : A lot of Shudown of CS after upgrade in R12.1



file://///S3














































CROXES-19997 CROXES-4050 Major endUser_customerSite [Report] : SIP ABCF call lost after RE_INVITE (hold)

CROXES-20269 CROXES-17338 Major endUser_customerSite [Report] : OXE TFTP phone binary upgrade stategy

CROXES-19999 CROXES-19229 Major endUser_customerSite [Report] : //1893_LSY// For IP tickets "IPAYXX.DAT file" DISTANT ID and LOCAL ID is mismatching.

CROXES-20313 CROXES-18855 Major validation_funcManual [Report] : OXE:M1:Call between SIPDEVICE is failed with "Forbiden " message when Identity Secrecy is enabled.

CROXES-20055 CROXES-19661 Major endUser_customerSite [Report] : One way audio issue involving one OTCv set (8088) and two Cell Phones in 3 party conference.

CROXES-20465 CROXES-18456 Major endUser_customerSite [Report] : [Related] : OTC Smartphone the 2nd ARS route on GSM doesn't work

CROXES-20169 CROXE-9783 Major review [Report] : [Related] : [Feature] Qatar Country Management -Swinst

CROXES-20167 CROXES-19608 Major review [Report] : INTIP Teamware environment becomes very slow after conencting



CROXE-8013 CROXE-7691 Major endUser_customerSite Supervision is not working for digital sets.//00299713//

CROXE-9087 CROXE-8483 Major endUser_customerSite //1893_LSY// Call announcement not working with OXE OMS//_00323452

CROXES-3849 CROXE-4427 Major endUser_customerSite reboot when installing new Licences

CROXES-18482 CROXES-18510 Major endUser_customerSite //1893_LSY// 4645 KO after upgrade to release 12.1, same issue experienced in SR-1-209903611

CROXES-19193 CROXES-18510 Major endUser_customerSite //1893_LSY// 4645 voicemail not working after bascul

19.18 M3.402.22.c OXE R12.2 MD1

List of all Reports






























IISUE KEY MAIN CR PRIORITY HOW FOUND SUMMARY

CROXES-19833 CROXES-19780 Major endUser_customerSite [Report] : No audio for new created GAP sets in R12.2

CROXES-19848 CROXES-19758 Major endUser_customerSite [Report] : OXE M3 - SIP IN-Band DTMF: call refused by 488

eventhough G711 in SDP offer

To all reports before MD1 please see in the readme file at the root of the version.

The M340221 has the same level of correction than M230022 and the M340213f (TR) has the same version of

correction than M230020.

20 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

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





https://businessportal2.alcatel-lucent.com/technical_documentation_library

http://sourceforge.net/projects/win32diskimager/

https://businessportal2.alcatel-lucent.com/system/files/documents/mle_crosscompatibility_nov_2015_ent_mle_016252_ed29h_en_0.pdf

https://businessportal2.alcatel-lucent.com/system/files/documents/mle_crosscompatibility_nov_2015_ent_mle_016252_ed29h_en_0.pdf




Any possible issue will require first to be addressed and analyzed by the AAPP member before being escalated

to Alcatel-Lucent.

For any request outside the scope of this IWR, Alcatel-Lucent offers the “On Demand Diagnostic” service

where assistance will be provided against payment.




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 -

https://businessportal.al-enterprise.com/customer-service-link

https://businessportal.al-enterprise.com/technical_documentation_library

https://businessportal.al-enterprise.com/technical_documentation_library

http://businessportal.al-enterprise.com/technical-knowledge-center-0

TC2473 Release Note & Installation procedure for OmniPCX ...

Documents

Transcript of TC2473 Release Note & Installation procedure for OmniPCX ...