Evolution To R12 - Issue 03 ENTPWTE126 - Nodrm

OMNIPCX ENTERPRISE - RELEASE 12
EVOLUTION TO R12 - ISSUE 03

PARTICIPANT'S GUIDE
OpenTouch Suite for MLE
OmniPCX Enterprise
Release 12
General information
Main new features
Rainbow integration
Cloud Connect: Dongleless
New Call Server kernel
New 80x8s telephone sets
8088 telehone sets in NOE mode
Embedded Web based management
Multi device user
SIP serviceability improvements
Oxe Release 12 Overview
New major release

 M1.403.12
Compatible with OpenTouch 2.1.1, OpenTouch 2.2 and OpenTouch 2.3
OmniVista 8770 software version 3.2
New OPS license files

 Lock #165: value 45
New Call Server Kernel
Goal of the feature:

 Upgrade the OXE Call Server kernel version from 2.4.17 to version 2.6.32.
Benefits
 Future proof
 Have up to date drivers and software modules like cryptographic modules including OpenSSL 1.0.1 to answer to security
vulnerabilities
 Facilitate future appliance servers and virtualization environments compatibility
Hardware Supported by OXE Release 12
OXE Call Server Crystal hardware Common hardware Appliance Server Virtual environments
technology
Compatibility CPU7-2 CS-2 IBM / Lenovo ▪ VMware ESXi

list ▪ 512 MB RAM ▪ X.3250-M6 - 5.5
(upgrade kit will be ▪ X.3250-M5 - 6.0
(refer to the cross sold) - 6.5
compatibility for official ▪ BIOS update required
detailed information) HP
▪ DL 20 G9 ▪ KVM 6.4
▪ DL 320e G8v2
▪ DL 320e G8
BIOS upgrade required
40GB hard disks must be used

Compatible Appliance Servers and CS-2 board must be equipped with a minimum of 1 GB RAM
Reminder: Additional RPM packages or pure binary software different than the contents present in ALE
software deliveries CANNOT be installed on the Communication Server.
Hardware NOT supported
ALE CS-1
ALE CPU7s1
ALE CPU6s2
ALE CPU5
Any Appliance Servers not listed in the Hardware Supported list on previous page
Blade Servers
Note: Blade Servers and old Appliance Servers that meet pre-requisites can still be used install an OXE-V in a
virtualized mode
Upgrade
New hard disk partition configuration
 This requires a complete re-installation from scratch, without multi-partitioning with both Linux 2.4 & 2.6
HP-DL320e G8v1: BIOS upgrade is mandatory.

 The link below indentifies a binary to be downloaded and the complete procedure
 http://h20564.www2.hpe.com/hpsc/swd/public/detail?swItemId=MTX_aada3917771d4d0ca7919842f7#tab5
It is NOT possible to use “Restore MAO data for rebuild” if the database is older that releases L2, L1,etc.
 This is due to binary incompatibility
Upgrade – CPU7s2
CPU7s2 BIOS has been modified to take the new kernel into account.
OXE releases with old BIOS firmware, cannot be upgraded to a new Linux release.
Only systems with CPU7s2 BIOS version 004.001 can be upgraded to new Linux 2.6.
Compatible BIOS banner description:
*** CPU7-2 Board version 3BA23259ABJE05?? ***

*** CPU7-2 Layout 1 ***
*** BIOS Version 3BA24115AAFC bscpu7300/004.003 ***
*** Generated on Mar 23 2015 at 19:11:52 ***
Available in patch
 L1.301.36a
 L2.300.20e
Note:
 “Alize boot method” for CPU7s2 is not available anymore. Only “A4400 network boot” method is supported
Virtualization
For more information about virtual parameters and size to use, consult the release notes document
available on Business Portal website
Multi-Devices
Multi-device support CAUTION: Support for OXE multi-device feature
Overview with OpenTouch is planned for the Q4 2017
Maintenance Delivery
 Currently, there is only one main and one secondary set available in Tandem configuration
 Multi-device is an enhancement of tandem configuration where three more additional devices can be attached to the
main tandem. This will bring the total up to five devices
 Combination Example: User

main
IPDSP
Secondary Devices
DECT Smartphone
(via REX)
All current two set Tandem configuration functions and restrictions remain the same for multi-device users
Multi-device support
Telephone Set types
Restrictions
 Only one DECT per multi-device user
 Only one Remote Extension per multi-devices user
Supported number of
One Main and up to four Secondary
devices
Main set types NOE IP, NOE TDM, IPDSP, SIP (SEPLOS), desk sharing (DSU)
NOE IP, NOE TDM, DECT, MIPT, IPDSP, SIP (SEPLOS), REX,
Secondary set types
desk sharing (DSU)
Call presentation
A call to the main set will ring the Secondary and Multi devices at the same time
Each Secondary set can be called by its own number, in this case, the call is not considered as a multi device
call.
Multi-device telephone sets continue to work as normal, when the Main or Secondary set is out of service the
 See workflow example on next slide
Call presentation possibilities:

 De-activate a remote extension by using a prefix. Result: incoming calls are routed to the REX, and NOT transmitted to
the smartphone
 Put a NOE deskphone in “no ring mode”. Result: incoming calls are still presented, but the set DOES NOT ring
 This feature is supported by IP/TDM NOE sets, but not by DECT sets, SIP extensions or remote extensions
Workflow
Workflow for a call when Main set is Out Of Service
When Main set is OOS
Option “Forward if set is oos” = true ?
No Yes
Option “Overflow to sec tandem if main oos” = true ?
No Yes
Are all secondary sets « oos » ?
Yes No
Associated set
in service ?
Option “Ring secondaries if Main OoS” = true ?
Yes
No
Yes No
Multi device is seen as oos. The main set is forwarded to the All secondary in service are The first secondary is called
Call overflows depending on the call type associated set called
(internal/external) and system management
When “forward if set is oos” or “Overflow to sec tandem if main oos” parameters are modified when the
Main is OOS. This is NOT taken into account until the Main set returns to service, and, then a modified “Out
Of Service” scenario will take place if the Main goes Out Of Service again
Miscellaneous
Exit from Out of Service state
 The multi-devices user returns back to service as soon as one of the sets returns to service
 This is only valid for IP/TDM NOE deskphones
 The “return to service” is not detected by OXE for DECT or SIP SEPLOS extensions
A multi-device user that is supervised by a different user will be seen as “in service” by the supervisor, only
if “Ring secondaries if main OoS” option is activated
Configuration
Two steps are needed to create a multi-device user
1- Create a Tandem
2- Add up to 3 devices to
create a multi device user
OmniVista 8770 « Users » application, all devices are displayed below the user:
Maintenance
Tools:
 zdpost
 multidevice
multidevice 31000 multidevice 31010

--------------------------------------------- ---------------------------------------------
Memory Info of Tandem/Multidevice Memory Info of Tandem/Multidevice
Set numan : 31000 Set numan : 31000
Set nulog : 2 Set nulog : 2
tandem_principal = 1 multi_device_main = 1 tandem_principal = 1 multi_device_main = 0
Multi device Normal Tandem
Number of Multidevice 2 tandem_mcdu : 31011
1 tandem_nulog 3 tandem_mcdu : 31001 ----------------------------------------------
2 tandem_nulog 14 tandem_mcdu : 31009
---------------------------------------------
Call duration control
Overview
Reminder: this feature was partially implemented in R11.2.2 and is modified in R12

 Configure “Timed Call Release” for both outgoing and incoming calls through Public circuits or Private ABC-F/QSIG
circuits.
 Only outgoing, Incoming, or, none
 ISDN, QSIG or ABC-IP trunk groups (public/private)
 Public/Private SIP trunk groups
 Public Analog trunk groups
 Manage timer per COS with a different timer for outgoing and incoming calls.
 User is notified with a “beep” tone and the display will change to ‘impending call cut’ 10 seconds before the call cut.
Implementation:
 Two new phone feature COS timers are introduced and one parameter can be modified
 Timed Call Release
 Release Timer for Outgoing call
 Release Timer for Incoming call
Configuration
/ Trunk Group /
 Special Services: Timed Call Release (to activate the feature for the trunk group)
/ Classes of Service / Phone Features COS
 Timed Call Release: (to manage the feature “COS by COS”)
 None: external calls are never released
 Outgoing: only outgoing calls are released
 Incoming/Outgoing: both incoming and outgoing calls are released
 Release Timer For Incoming Call
 This timer, if not 0, is used in place of timer 260 or 312 automatic release of external Incoming calls
 Release Timer For Outgoing Call
 This timer, if not 0, is used in place of timer 260 or 312 for release of external Outgoing calls
/ System / Timers
 Number 260
 Number 312 is used for QSIG trunk calls
/ System / Other System Param. / System Parameters
 Call Release Timer Restart: (to bypass the 54 min limitation)
 Specify the number of timer 260 restarts (0 by default)
Enter the desired duration: For all timers in steps of 100 ms.
 The range can be from 600 x 100 ms (1 minute) to 32767 x 100 ms (~54 minutes)
Description in a table format
Phone Features COS / Timer used for Incoming Calls Timer used for Outgoing Calls
Timed Call Release
None NA NA
Outgoing NA “Release Timer for Outgoing
Call”, otherwise Timer #260 / 312
Incoming / Outgoing “Release Timer for Incoming “Release Timer for Outgoing
Call”, otherwise Timer #260 / Call”, otherwise Timer #260 / 312
312
Reminder in R11.2.2
From R11.2.2, It was possible to:
 limit duration for private ABC-F link calls
 activate/deactivate timed call release for attendants
Existing parameters:
 / System / Other System Param. / System Parameters
 ABC Timed Call Release
 False/True: Specify if user to user ABC-F calls are limited or not
 Attendant Timed Call Release COS
 -1: to disable the feature for attendants
 0-255: this is the phone feature COS used to get the “Timed Call Release” parameter value for the attendants (an attendant set has
no phone feature COS).
Miscellaneous
This feature works with all established calls in Conversation, On hold, Transfer and Conference Contact
Center Distribution
When an incoming or outgoing external call to either local or network node is transferred, the feature works
in accordance with the TRANSFERRED party’s COS configuration. If the feature is enabled in the transferred
node then:
 The call release timer restarts, if the transferred node is network node.
 The call release timer does not restart, if the transferred node is local node.
The feature does NOT impact Voice mail and calls connected to voice mail will NOT be released
Conferences
Conferences
To extend the Casual Conference capacity
 This feature permits the number of Casual Conferences circuits to be extended from 15 to 30.
Behavior until R11.2:

 A hard coded circuit size 7 is requested from a board when a user initiates a Casual Conference.
 A conference circuit size 15 is requested if a circuit of size 7 is not available.
 A conference circuit size 30 is requested if circuit sized 15 is not available.
 However, a Casual Conference only allows six participants consisting of Initiator + five other participants + Beep
 Whatever the number of circuits reserved on the board: 7 or 15 or 30
Conferences
To extend the Casual Conference capacity
Enhancement:
 This enhancement offers the possibility to increase the size of a conference circuit to 15 (14 participants) or 30 (29
participants).
 A dedicated new parameter “Max participants in casual conf”, has been created.
Caution: This is the MAXIMUM number of participants and all still depends on the resources available on the
boards.
Conferences
IP domain criteria
 This feature introduces the domain's criteria to select conference circuits
Behavior until R11.2:

 The search for free conference circuits starts with circuits belonging to the domain of the initiator and ends with
circuits belonging to other domains.
Enhancement:
 This enhancement allows to control the conference circuit search per IP domain.
 Two new options are available in IP domain
Conferences
IP domain criteria
Option “Accept conf. circ. of other dom.”
 NO: we search for conference circuits only in domain of the user who initiates the conference
 YES (default): we search for conference circuits in domain of the user who initiates the conference AND in the others
domains with the following option to true.
Option “Provide conf. circ. to other dom”

 NO: this domain forbids others domains to use its conference circuits
 YES (default): this domain allows others domains to use its conference circuits.
Behavior is the same as before this evolution when both these options are “yes” for all domains
 This is the default configuration (search conference circuit in all domains)
Conferences
IP domain criteria
Examples
Initiator domain Domains Domains Search cc will be

D1 with D3, D5 with D1, D2, D4 with done in
« Accept cc .. » = Yes “Provide cc…”= Yes “Provide cc …”= No D1,D3,D5
Initiator domain Domains Domains Search cc will be

D1 with D3, D2 ,D5 with D1,D4 with done in
« Accept cc.. » = No “Provide cc …”= Yes “Provide cc…”= No D1

Miscellaneous
Hardware obsolescence
Two new hardware platforms for OmniPCX Enterprise

 Lenovo X.3250 M6
 HP DL20 G9
Compatible as of OXE R12.0
Current HP DL320e G8 (v1 & v2) and Lenovo X.3250 M5 platform are still compatible with R12.0
PER 2856: Increase ABCA call queue length for 4059 EE

 Increase the maximum number of calls that are displayed in the parked calls list from 3 to 8 (PER 2856)
Available for all attendant console types: 4059EE, 4059IP, 4059 MAC, 4068, 8068, 8082
A 9th call can be put on hold but is not displayed in the parked calls list
OMS (OXE Media Services)
It is now possible to record dynamic voice guides on OMS
Reminder: SUSE OS must be installed

Increase the size of the External Voice Mail table

 The goal is to increase the size of the External Voice Mail table from 127 to 254.
 It allows to better address customer configurations with a high number of OpenTouch automated attendant trees.
A4645 security behavior improvement

 Be more user and administrator friendly and thus increase user acceptance and ultimately 4645 Voicemail security
Enhancements:
 Default value of password validity period is changed from 60 days to 180 days
 The GUI message for an expired password is changed from “Password” to “Password expired, Enter new password” to
help the user to understand
 The user interface on locked account is improved. A new voice guide “your account is locked” has been introduced. The
GUI shows “Account locked, please contact admin” to inform the user that the account has been locked and what to do.
 A new incident is created to indicate the mailbox is locked due to incorrect password attempts:
 “Mailbox of <xxxx> is locked due to too many incorrect password attempts”
 Two new options are available in A4645 maintenance command for the administrator
 View / List locked mailboxes
 View / List mailboxes with expired password, List mailboxes depending on password expiry date
Alarm calls with loudspeaker announcement

 Allow an external alarm application to set the loudspeaker level when alarm calls activated via loudspeaker
announcement.
This feature is applicable only for Alcatel-Lucent 8&9 series telephone sets.
Applicable when OXE is connected to the application via ABC-F only (IP/TDM trunk group or ABC-F links)
The feature is available if the user is located on an OXE node in R12.0 (transit nodes may not be in R12.0)
To delete alarm messages from DECT sets

 Add a new option in the sub menu of a message to delete all alarm messages at one shot irrespective of whether it is
read or not
 Only for AGAP handsets
Current menu: New menu:
« Cancel » is replaced by « Delete »

« Delete all » is now possible
« Back » is still present in the menu
OmniPCX Enterprise
Device evolution for H1 2017 MLE offer
IP Premium DeskPhones
Premium DeskPhone Evolution
New model introduction
Black and White Color
8018 8028s 8058s – 8068s – 8068s BT 8078s – 8078s BT 8088 – 8088 BT
2.3 inches 2.8 inches 3.5 inches 5 inches 7 inches

8058s & 8078s to complete the Premium Deskphone range
 8078s Premium Deskphone  8058s Premium Deskphone
 New telephone set with touch panel: 8078s  Same level of service as 8028
 Same level of service as 8068
 Regarding 8058s deskphone:

 Three lines of menu for dynamic softkeys with text.
 The last two lines are managed locally by the phone as an electronic AOM (similar to the four physical AOM buttons of the 8028).
8028s and 8068s to emphasize Premium DeskPhone innovative design with improved performances
 8028s Premium Deskphone  8068s Premium Deskphone
 Evolution of 8028  Evolution of 8068
8058s, 8068s and 8078s
Light Back logo
 Color depends on call state
Skin choice
 4 skins are provided : Rainbow, Crystal, Classical, Luxury
Ambient Light Sensor

 To reduce power consumption. It modulates:
 The LCD Backlight
 All LEDs and Incoming call
 The LOGO LEDs
USB port with boost charging

 To connect headsets, headphones, etc.
8028s, 8058s, 8068s and 8078s
Hardware
 New chip ready for Super Wide Band
 New magnetic wired mini keyboard
 Compatible existing accessories:
 Wired comfort handset
 Common Bluetooth handset (C-BTHS) (for devices supporting Bluetooth)
 Add-on module range: AOM10, AOM40, AOM14
 Premium Add-on clip
 Power Supply for AC / Power Supply for PoE
 Wall Mounting Kit
 PoE class 2
Compatible from:
 OXE R12 for 8058s and 8078s
 OXE R11.1 for 8028s and 8068s
See datasheet for more information:

 https://businessportal2.alcatel-lucent.com/node/438011
Feature description table
Skin USB USB Boost Back Logo Ambient Light

Set type Bluetooth
Customization Connectivity Charging Light Sensor
8018 Not Available Available Available Not Available Not Available Not Available
8028s Not Available Available Available Not Available Not Available Not Available
8058s Available Available Available Not Available Available Available
8068s Available Available Available Available Available Available
8078s Available Available Available Available Available Available
8088
Available Available Not available Available Not Available Available
NOE
8028s, 8058s, 8068s, 8078s Premium Deskphones new features
Configuration
New parameters are available to configure:
 USB connectivity
 USB boost charging
 Ambient Light Sensor
 Back logo LED
Configuration
USB Connection
 YES (default)/NO: A USB device device connection can be allowed or not
USB Boost Charging

 DISABLE: normal USB charging (default value)
 ENABLE: boosted USB charging
 AUTO: reserved for future use (= disabled if set)
 Warning: boost charging requires more power consumption than the normal USB charging provided by PoE.
Ambient Light Sensor Forced Active

 Active ambient light sensor to adapt brightness of LED according to the external brightness
 Modifiable by ULM: user can activate/deactivate Ambient Light Sensor (default value)
 Enable: ambient light sensor is activated (non-modifiable by user)
 Disable: ambient light sensor is deactivated (non-modifiable by user)
Note: Modification of these parameters requires a telephone set reboot

Configuration
Back logo LED
 LED glows for ALE Enterprise Logo at the back of these sets.
 Modifiable by ULM: user can activate/deactivate Back logo LED (default value)
 Enable: Back logo LED is activated (non-modifiable by user)
 Disable: Back logo LED is deactivated (non-modifiable by user)
NOE-3G EE Skin Number

 Skin selection is possible only in set types like 8058s, 8068s and 8078s.
 0: No information is sent to the terminal. Skin is modifiable by user.
 1 to 4: this skin number is sent to terminal and is not modifiable by user.
Note: Modification of these parameters requires a telephone set reboot

8018 IP DeskPhone
8018 DeskPhone enhancements
Introduced as NOE set with R11.2.1

 retro-compatibility with R11.1 and R11.2
As of 8018 R200 and R11.2 MD7 patch

 Encryption IPv4
New Features with 8018 R210 and OXE R12.0

 SIP mode for hospitality (requires OV8770 R3.2)
 SIP survivability
 SSHv2 password management
8088 Smart DeskPhone – NOE mode
Available H2-2017
8088 Smart DeskPhone
NOE mode
History
 OXE R11.1: 8088 available as SIP hospitality set
 OXE R11.2: 8088 available as SIP based video huddle room
In R12:
 8088 Smart Deskphone in NOE business mode
Features:
 Provide full OXE advanced business telephony on a high end desktop terminal controlled by NOE protocol
 Android platform based
 Not possible to install other apps for the moment
 Dual partitions:
 Current SIP stack (based on Linux), R300 version minimum
 NOE stack (based on Android)
8088 Smart Deskphone
NOE mode
Switch between SIP and NOE:
 Local MMI
 DHCP
 embedded command (via SSH session on the deskphone)
Initialization / upgrade in NOE mode

 HTTP is used to retrieve the Android OS package
 Use of an external HTTP server
 « lanpbx.cfg » file provides URL of binaries
Silent binary upgrade mechanism (like Premium Deskphones / 8018 / 8082 NOE)
 Firmware downloaded in background and applied later on when the set is in idle state
Protection against network / power cut

 Upgrade and download processes resume after a cut
8088 Smart Deskphone
NOE mode
Not available in current release:
 Physical Add-On Modules not supported
 IP Premium Security (encryption)
 IPv6 support
 SIP survivability
 VoIP QoS tickets
DECT handsets
Evolutions: 8232s / 8242s DECT
Re-created Face lift: 8232 becomes 8232s and 8242 becomes 8242s
 Intrinsic robustness improvement creating higher level of user-perceived quality
 Upward and backward compatibility for software and accessories
 The new desktop charger is fully compatible with 8232/8242 and with 8232s/8242s
Facelift
8232 8232s
Retro-compatible New desktop charger Compatible
8242s
8242 Facelift
OmniPCX Enterprise
Web Based Management
Overview
OXE WBM is a Web Application to configure OXE

 based on HTML5, CSS and JavaScript
Supported browser OS
 Microsoft Windows 7 and higher Web Server
Supported browsers Authentication CMISE gateway OmniPCX

 Chrome, Firefox, (In MD1: Internet Explorer, Edge, Safari) Enterprise
Radius Server
(optional)
MAO CMISD
Localization
 English, French, German, Spanish, Italian, Portuguese
Access with URL

 https://<<OXE IP@>> EMBEDDED GRAPHICAL FAST
APPLICATION INTERFACE NAVIGATION
Graphical User Interface Help online Console Log
Disconnect
Differentiate the tabs in case

WBM is opened on various OXEs
Dynamic layout adapted to the window size

Graphical User Interface
Object path to ease the navigation
within OXE object model
Contextual menu:
actions available on the
current object
Graphical User Interface
Search functionality
Sorting mode
Disable filtering
Filter activated
Activation
The Web Based Management can be activated by following the path to activate a new system parameter
Log files
Log files are available on both:

The client side:
The server side:

 /var/log/openresty/access.log
 /var/log/openresty/error.log
 /tmpd/wbm.log
 /tmpd/wbm.log.sav
Miscellaneous
4760i is not available on OXE anymore. The 4760i Menu is also disabled from MAO.
APACHE is not available on OXE anymore. WEB menu is also disabled from netadmin.
OmniPCX Enterprise
Release 12 - SIP enhancements
motortrace enhancements
SIP serviceability - motortrace: level of information
Goal of the feature

 New trace options are available in “motortrace” to enhance level 1 and 2 options
Use
 “motortrace 2” should be used for observation captures during a lot of SIP traffic
 “motortrace 3” should be used when more information about specific issue is needed, without traffic
Degraded mode
SIP serviceability - Degraded mode
Goal of this feature

 The SIP Motor cannot handle more than 8000 active communications at the same time
 SIP Motor will change to “degraded” mode when this limit is reached
Behavior when in degraded mode

 Outgoing requests are rejected internally
 Incoming requests are rejected with a 503: Service Unavailable response
 This response includes a Retry-After header, whose timer indication depends on the “Degraded mode Time To Live” value
 If the Time To Live value is GREATER than 300s. The real value will be 600s, independently of the management configuration
 Otherwise, its value is taken from management configuration, incremented by 10s
Conditions needed to exit degraded mode

 Number of active communications below 7600
 Or restart of « sipmotor » process
 Immediatly after entry in degraded mode
 After a timer (new parameter “Degraded mode Time To Live”)
SIP serviceability - Degraded mode
The sipmotor process will re-start immediately when OXE changes to degraded mode, if the “Degraded mode
Time To Live timer” is set to Zero
Otherwise, the sipmotor process re-start when OXE moves to degraded mode, will depend on the value of
the “Degraded mode Time To Live timer”. This timer is set to a default value of 1800 and has a maximum
value equal to 7200 seconds.
New Oxe Incidents
SIP serviceability - Incidents
There are some new incidents to provide more information for the following use cases
 Stack Degraded Mode
 Quarantine state
 Start SIP Motor failure
 SIP Motor restart
 Active Licenses Above / Below threshold

Stack Degraded State

 5826 “SIP Degraded mode: Entry”
 5827 “SIP Degraded mode: Exit”
 5828 “SIP Degraded mode: Exit and Restart”
Quarantine State
 5829 SIP Quarantine State : P1 for IP P2
Start SIP Motor Failed

 5830 “Start SIP Motor failed / reason : P1”
SIP Motor Restart

 5831 “Start SIP Motor restart / reason : P1
SIP TLS link

 5832 “SIP TLS link / gateway : P1 / P2
Active Licenses Above / Below Threshold

 5833 SIP licenses are P1 than the threshold which has been set to P2
Activation of Incidents from 5826 to 5833
A new system option “Overflow licenses threshold” is available.

This indicates the license threshold value as a percentage.
Incident 5833 will be generated whenever the license threshold reaches above or below this value.
User-Agent header
SIP - User-Agent Header
Goal of the feature

 Customize the User-Agent header of the SIP messages
 This was asked by SIP carriers to provide information about the system via SIP User-Agent
Current behavior
 The existing content of the User-Agent header provided by the OXE is:
 User-Agent: OmniPCX Enterprise R12.0 m1.403.12
 … where R12.0 m1.403.12 is the “version” number running on the system.
New behaviour
 Use the current User-Agent. This is the default setting
 Add characters before and/or after the User-Agent
 Create your own User-Agent
SIP – User-Agent Header
Configuration
 Example # 1 / User Agent Identifier : “Empty” or Space(s) (Actual functioning)

 User-Agent : OmniPCX Enterprise R12.0 m1.403.12
 Example # 2 / User Agent Identifier : %/ Open Touch

 User-Agent : OmniPCX Enterprise R12.0 m1.403.12 / Open Touch
 The string following the % character is added at the end of the “version” number.
 Example # 3 / User Agent Identifier : Node 1 -%

 User-Agent : Node 1 - OmniPCX Enterprise R12.0 m1.403.12
 The string preceding the % character is added in front of the “version” number.
OmniPCX Enterprise
4059 Attendant EE 1.7 (Extended Edition)
Overview
New 4059EE release: 1.7
Available from April 2017
New features include:

 New User Interface for Directory lookup
 Extended Contact Card
 Management Settings are reorganized
New Directory lookup User Interface
Multi-criteria search
Number of criteria defined by user and easy to modify
Can be changed temporarily for a specific search
Several attributes displayed in result list, fully configurable
New Directory lookup User Interface
Fields for research are selectable

Type of search can be modified (equals, begins with, ends with, contains)
Extended Contact Card
Free mapping from LDAP fields

All numbers are clickable
Field names can be changed
Combo fields possible
Contact card can be customized

 Up to 50 attributes displayed
 Re-designed settings window

 It is possible to change font, color, etc…
OmniPCX Enterprise
Release 12 - IP Premium Security and IP Version 6
IP Premium Security and IPv6
Overview
Goal of this feature
 The purpose of this development is to encrypt local and network IPv6 communications with the new Server Secure
Module (SSM) and Media Secure Module (MSM) that are compatible with both IPv6 and a mixture of IPv4 and IPv6
addresses
IP Premium Security solution is compatible with IPv6

 IP Premium SSM & MSM are the new Thales encryption boxes
 8028, 8038 & 8068 Premium Deskphones with binary encryption and SoftMSM
The call server still remains in IPv4

 Oxe Signalling Transfer 64 (OST64) converts signaling from the Communication Server with IPv4 to IPv6 devices and vice
versa.
Architecture example with data flow
Media Gateway OST64 Call Server

(IPv6) (IPv4)
PCS
OST64 NOE (IPv6)
(IPv4)
NOE (IPv4)
Premium IPSec (IPv6)
IP Premium Deskphone RTP (IPv6)
IP Premium IP Premium SSM (IPv6) SRTP (IPv6)
MSM MSM
IP Premium SSM has to secure both the OXE Communication Server and the associated dedicated OST64
If a PCS and the associated OST64 are secured they both have to be protected by the same IP Premium MSM
operating in mixed mode.
 Caution: Encryption on Premium Deskphones will NOT be available when a secured PCS changes to active mode
Architecture example with data flow
Media Gateway Media Gateway OST64 Call Server

(IPv4) (IPv6) (IPv4) NOE (IPv6)
NOE (IPv4)
IPSec (IPv6)
RTP Proxy
IPSec (IPv6)
Premium
RTP (IPv4)
IP Premium Deskphone
SSM (IPv6) SRTP (IPv6)
MSM-RM SRTP (IPv4)
IP Premium MSM can protect

 Pure IPv4 or pure IPv6 devices
 Or both IPv4 and IPv6 communications, with the encryption box in mixed mode
RTP Proxy should NOT be configured behind IP Premium xSM module

Old encryption boxes will still operate in IPv4 mode, when used with the new IP Premium SSM module
Architecture example with flows
OTMC (IPv4) Media Gateway OST64 Call Server
(IPv6) (IPv4) NOE (IPv6)
NOE (IPv4)
IPSec (IPv6)
IPSec (IPv6)
Media Gateway
RTP (IPv4)
IP Premium with SoftMSM
IP Premium SSM (IPv6) SRTP (IPv6)
MSM SRTP (IPv4)
Protected applications such as OpenTouch, IP recorder, AVST SIP voicemail, etc will continue to work in IPv4
mode only
Encrypted FAX calls: Are possible between IPv4 devices or between IPv6 devices
 FAX traffic will be in clear mode between IPv4 and IPv6 devices
Encrypted SIP communication through SIP trunks only support IPv4

Configuration
Configuration - Box
Box creation and Address to protect menus, located under the Encryption menu, are enhanced to accept an
IPv6 address in addition to the IPv4 address configuration that is currently available
 The current IP Address field is enhanced to accept both IPv4 and IPv6 addresses.
 This field should to be configured with IPv4 address for mixed mode, and for pure IPv4 devices.
 It should be configured with IPv6 address for the pure IPv6 boxes.
A new field, IP Address2 has been added to accept the IPv6 address in case of mixed mode devices
BOX type IP address IP address 2

SSM IPv4 (Mandatory) IPv6 (Optional)
MSM IPv4 or IPv6 (Mandatory) IPv6 (Optional)
Configuration - Box
Example for SSM box running in front of CS and OST64
Configuration - Box
Example for a pure IPv6 MSM in front of a pure IPv6 Media Gateway
Configuration - Box
Example for a Mixed MSM in front of a Mixed Media Gateway
Configuration - Address to protect
Call Server protected by SSM
IPv6 Media Gateway protected by pure IPv6 MSM
Mixed Media Gateway protected by mixed MSM
Cloud Connect Operation
Overview
Lesson Summary
ALE Cloud Connect

 Introduction
Cloud Connect Operation

 Cloud Connect Operation overview
 Connection to the Cloud Connect Infrastructure
 Cloud Connect product identity
First Time Registration (FTR)

Right To Run mechanism (RTR)
License control on OXE
OXE Release12 configuration Management
RTR problem Troubleshooting
The Pillars Of Cloud Connect
Cloud
Future
Connect
services
OPERATION
Cloud
Connect
CONTROL
Rainbow
What is Cloud Connect Operation?
To create a secure connection between the OXE systems and the company IP infrastructure in order to:
 Benefit from hosted services in the cloud
 Control the use of the systems through a license check control
Cloud Connect will continue to enhance and enable more added value services to be developed on top of it
as time moves forware!
Cloud Connect Operation overview
Global View and perspectives

 Please note: this table is not a roadmap!!
System configuration & System backup
System supervision
System alarming
License management
R12 (Dongless) Right to Run
Right to Use
Advanced data analytics services
Software upgrade
Remote Connectivity over Internet

 Agent is integrated in the OXE system
 They set up a connection from the LAN to the Cloud through the existing Enterprise Data Network
 They use standard and broadly supported connection methods that work without having to touch the IT configuration
ALE’s Cloud Platform
Permanent
connection
Enterprise
CC Agent Firewall
OmniPCX Enterprise
Assumptions: The customer’s network is connected to the Internet / WAN

Cloud Connect Infrastructure (CCI)
Registration
ALE Back- RTR Services
FTR
Office CC Agent CC Agent CC Agent
ERP
License
tools
Cloud Connect Infrastructure
eBuy
ALE’s Cloud
Internet Permanent The OXE establishes a permanent connection
connection with the Cloud Connect Infrastructure operated by the ALE
Enterprise X
Firewall
XMPP over web sockets
CC Agent
OmniPCX Enterprise
Connection with the Cloud Connect Infrastructure
XMPP Connectivity
 XMPP: eXtensible Messaging and Presence Protocol
 Based on XMPP protocol:

 XMPP consists of a TCP / IP protocol based on a client-server architecture to allow decentralized exchanges of instantaneous or non-
instant messages between clients in the Extensible Markup Language (XML) format
 XMPP is in constant and open development within the IETF
 basic RFC are 6120 and 6121 + some standard XMPP extensions (named XEP) are used
 Proprietary Cloud Connect extension has been defined over XMPP
 XMPP server makes the link between the OXE and the hosted services
 First Time Registration, Service Activation, Right To Run
Security
 Information exchanged through web sockets over the Internet

 OXE initiates a bi-directional connection
 No modification of the final customer network security policy
 No (or minimal) reconfiguration of the firewall, WEB proxy or DNS servers
 Secured connection with TLS v1.2:

 Cloud Connect Infrastructure servers use a certificate issued by a Certificate Authority kept under ALE responsibility.
 OXE has this authority certificate in a trust store dedicated to the Cloud Connect agent
 XMPP authentication
 Unique identifier and password for each product
Customer network requirement
 OXE must have an outgoing connection to the Internet to reach the public Cloud Connect Infrastructure
 Customer network gateways & firewalls must allow outbound connections to Cloud Connect Infrastructure
 Outgoing connections must be allowed

 for XMPP over HTTPS  port 443/tcp
 for SOCKS5 connection over HTTP  port 80/tcp
 for DNS resolution  port 53/udp
For more and up-to-date information, refer to lastest documents available on Business Portal website
Cloud Connect product identity
CC-SUITE-ID
 This ID is computed during the order process
 The syntax of the CC-SUITE-ID is:
ADCBE-FGHIJ-KLMNO-PQRST
 A 23 character string where A..T represent an hexadecimal digits (from “0” to “9” and “A” to “F”) written in upper
case characters. The 20 hexadecimal digits are packed 5 by 5 and separated by “-“
 This ID Remains the same during the product life time
 Even after an feature additions or CPU change
CC-PRODUCT-ID
 This ID is computed at both server and product sides and has the following syntax:
CC-SUITE-ID + “-“ + product-type

 Example (for OXE): af76e-05961-da1c1-de028-3
First Time Registration (FTR)
To log into the CCI, a OXE needs its final credentials
 The CC-Product-ID and a password
 A unique and immutable ID computed by the ordering chain
 The CC-Product-ID is unique for each product, whatever the product type and remains unchanged through upgrades
 Only the password may change over time
The main goal of the FTR (First Time Registration) is to allow the OXE to automatically retrieve these
credentials
The OXE must perform an FTR to be fully Cloud Connected and operational
 This is the first connection of the OXE to the Cloud Connect Infrastructure
 It is done by using a temporary product activation account
 Each OXE has its owns activation account based on CC-Suite-ID
Principle Software delivery to Business Partner 4
Order
1 Place order 1 Order Management 1 Order
tool
Business Partner
1
5 2
Order
Software Delivery
• Activation account based on CC-SUITE-

CC-SUITE-ID in
3
license file
ID creation
2 • Credentials creation (based on CC-
CC-SUITE-ID Licenses tools PRODUCT-ID)
creation 2 and database
3
CC login: activation account
8 based on CC-SUITE-ID
6 SW installation
Credentials 9
CC-SUITE-ID in
7 license file
10 Connection to CCI
Installer OXE Cloud Connect
Infrastructure
Performing First Time Registration

 Details on steps 8, 9 and 10 on OXE side
FTRtool CCI
Request for permanent

To backup credentials,
Save the « Linux Data » under swinst
connection credentials
Credentials
Save to disk
CC-Agent
Reset connection with CCI
Establish permanent connection

Cloud Connect Infrasructure Registration
Oxe Redundancy and Passive Call Server
Never perform a First Time Registration (FTR) on a stand-by Call Server
The final credentials received from CCI are not automatically synchronized with the TWIN Stand-by CS
 A Manual synchronization MUST be done to enable the system to function properly when the role changes.
 A reminder to the administrator will be displayed once FTR is completed successfully.
Cloud Services DO NOT run on Passive Communication Server (PCS)

First Time Registration with PIN code
It may be necessary to reinitialize system credentials to enable a permanent connection to Cloud Connect
Infrastructure. This might be caused by change of System Administrator or fraud detection or something.
Steps:
 System administrator has to request a temporary activation account from the helpdesk
 A new temporary activation account will be created with a PIN code composed of 6 digits (0-9), will be provided by
helpdesk
 The administrator has to re-launch the FTR operation on the OXE with the temporary PIN code
 The system has to re-connect using these new credentials
Help desk 1 Held desk verification:
contact
Principle system owner/fraud detection
1
Business Partner
2 Pwd renewal request
PIN code 4
Help Desk : status view and PWD renewal
5
Request FTR with

• FTR with pin code initialization
pin code 3 (activation account with pin code
creation)
• Other activation accounts deletion
• Disconnect all products
License tools
and database
Validity period Installer OXE CC login: activation account

7 based on CC-SUITE-ID + pin code CC Infra
5 days
Credentials with new

password 8
6 Pin code for FTR
Connection to CCI, with
9 new password
Performing FTR Operation with PIN code

 Details on steps 8,9 and 10 on OXE side
RTR-Process CC-Agent FTRtool CCI
Request for permanent
To backup credentials, connection credentials

Save the « Linux Data » under swinst
Credentials
Save to disk
Reset RTR parameters Reset RTR parameters
Reset connection with CCI
Establish permanent connection

Right to Run (RTR)
Right to Run (RTR)
The Right to Run service removes the need for hardware identifiers or dongle USB keys used to validate the
license. This is also called dongle-less operation
 Available for virtual and physical hardware server
If fraudulent usage is detected, or if for any reason a product has to be decommissioned, the RTR service in
Cloud Connect Infrastructure will restrict the product usage
Right To Run doesn’t replace license possibilities performed at product level

 License items are still controlled by the current license mechanisms at product level (swk files)
 It acts like an on/off switch giving the product the right to run according its license file limits
Right to Run (RTR)
Status
 Normal:
 Following a successful First Time Registration
 During the normal product life when it communicates with the RTR service:
 it is the only one to use a given CC-PRODUCT-ID
 its qualifying period is equal to 30 days.
 Qualifying:
 The qualifying period is less than 30 days but greater than 0 day
 It happens when:
 a piracy attempt is or has been detected, either by the centralized RTR service
 OXE cannot reach the RTR service
 This mode remains for up to 30 days
 There is no use restriction but the product generates alarms to warn the administrator about a piracy attempt
 A switch back to qualifying state can be caused by either the OXE or the Cloud Connect/RTR service
 Exiting from the qualifying mode is ONLY be done by the Cloud Connect /RTR service
 Panic:
 The product goes into Panic mode and runs in degraded mode if a problem still exists after the qualifying period
 The only way to exit from panic state is to perform a new First Time Registration with PIN code
Right to Run (RTR)
Status diagram Qualifying period = 30d from CC/RTR service

successful FTR Qualifying period = 30 days
Normal
Successful FTR with PIN code

Qualifying period = 30d from
CC/RTR service
- Received qualifying period

<30d from CC/RTR service or
- no CC/RTR answer or
Qualifying period is decremented by - no CC infra login
one day each day by:
- the CC/FTR service answer
- the product (no CC/RTR answer or
no CC infra login)
Qualifying period = 0d
Qualifying Panic
Right to Run (RTR)
Fleet dashboard Non definitive screenshot
 Business Partner of Administrator can access the Fleet dashboard: With a product list and RTR status
Right to Run (RTR)
Miscellaneous
 In case of no reply for Right To Run request or no connection to Cloud Connect Infrastructure
 OXE will retry the Right To Run check up for four hours with interval of ten minutes
 If the connection is restored or response received from cloud connect before four hours
 OXE will continue to function normally
 If the connection is not restored at end of the fourth hour
 OXE will decrement the qualifying period by one. The same procedure will be repeated on next day at the exact the same time
 During Save/Restore operation, the previous value of remaining qualifying period is maintained across reboots
 The remaining qualifying period value is updated on the Twin Call Server (if present)
 During the old database restore, the latest remaining qualifying period is maintained
 The RTR service parameters are copied to standby without any user intervention.
 Cloud Services do NOT run on (PCS) Passive Communication Server

License control on OXE
Possibilities
RTR enabled
Flex-LM enabled and Licensing Mechanism Used
CC-SUITE-ID is present in SWK file
YES YES Not Allowed
YES NO Flex-LM License used
NO YES CC-RTR is used
NO NO CPU ID Check used
OXE Management configuration
OXE Configuration
netadmin settings
Three new items added to "netadmin" menu:
 Choice 14 to input DNS server addresses

 Choice 15 to configure the Proxy server parameters
 Choice 19 for Cloud Connect operations
OXE Configuration
netadmin settings
DNS settings
 The DNS server addresses are used

only for Cloud Connect and Rainbow features
OXE Configuration
netadmin settings
 Proxy server settings
 The Proxy server parameters are used only for Cloud

Connect and Rainbow features
 Definition of a Proxy server is optional
OXE Configuration
Cloud Connect Menu
 Cloud Connect Operations menu
 Input and check of product’s CC-Suite-ID

 Execution of the First Time Registration
 Consultation of registration status
 Execution of FTR with PIN code
OXE Configuration
Cloud Connect Menu
 Choice 1: « CC-Suite-ID »
 To view the CC-Suite-ID present in the swk license Files
 CC suite ID can also be retrieved from the 8770

OXE Configuration
Cloud Connect Menu
 Choice 2: « Perform FTR”
 FTR operation can be executed during installation

procedure
 The Oxe telephone application is NOT required to be started
OXE Configuration
Cloud Connect Menu
 Choice 3: “View FTR Status”
 Two status are displayed

 The registration status, indicating if credentials are available to
establish a permanent connection with CCI
 The status of the last FTR operation executed in OXE. In case of failure,
the cause is also indicated
OXE Configuration
Cloud Connect Menu
 Choice 4: « Pin Code »
 FTR with PIN code operation needs CC-Agent and RTR-

Process to be running on system
 Check is done before launching the operation
OXE Configuration
Cloud Connect Menu
How to Enable the Right to Run
RTR Troubleshooting
RTR Troubleshooting
CCTool command
 To display RTR status

 To force RTR execution
 To change RTR execution parameters (time-out …)
RTR Troubleshooting
Incidents
 Incident alarms are generated through out the RTR-Process system lifetime
Number Severity Description

647 Minor Generated after a request to CCI. It details the answer received
(OK, NOK) with additional information (cause of error if any,
remaining qualifying period …)
648 Critical Raised if system goes to panic mode after 30 days.
649 Clear Generated when FTR with PIN code has been performed. It indicates
that system is going out of panic mode.
650 Critical Raised if fraudulent activity is detected inside OXE. System goes
immediately to panic mode.
651 Clear Clearance of incident 650.
OmniPCX Enterprise Communication Server
DNS and proxy configuration
How to
✓ Configure DNS and proxy on the Call Server
Contents
1 DNS configuration ............................................................................. 2
1.1. Setup ..................................................................................................... 2
1.2. Review ................................................................................................... 2
1.3. Delete .................................................................................................... 3
2 HTTP proxy configuration .................................................................... 4
2.1. Setup ..................................................................................................... 4
2.2. Review ................................................................................................... 4
2.3. Delete .................................................................................................... 5
2
Implementation
Notes
The DNS and HTTP proxy configuration will only be used by Rainbow and Cloud Connect agents
1 DNS configuration
Configure the following DNS settings: 151.1.1.253
1.1. Setup
netadmin menu
Alcatel-Lucent e-Mediate IP Network Administration
=======================================
1. 'Installation'
2. 'Show current configuration'
3. 'Local Ethernet interface'
4. 'CPU redundancy'
5. 'Role addressing'
6. 'Serial links (PPP)'
7. 'Tunnel'
8. 'Routing'
9. 'Host names and addresses'
10. 'Copy setup'
11. 'Security'
12. 'DHCP configuration'
13. 'SNMP configuration'
14. 'DNS configuration'
15. 'Proxy configuration'
16. 'VLan configuration'
17. 'Node configuration'
18. 'Ethernet redundancy'
19. 'Cloud Menu'
20. 'History of last actions'
21. 'Apply modifications'
0. 'Quit'
Enter DNS menu 14. 'DNS configuration'
14.DNS Setup
=========================
1. 'View DNS configuration'
2. 'Create/Update DNS setup'
3. 'Delete DNS Details'
0. 'Previous menu'
Choose “2. 'Create/Update What is your choice ? 2
DNS setup'” and enter DNS IP Primary DNS address (default is 127.0.0.1)? 151.1.1.253
address(es) Secondary DNS address (default is 127.0.0.1)?
1.2. Review
netadmin menu
DNS menu 14.DNS Setup
=========================
3

0. 'Previous menu'
Choose “1. 'View DNS What is your choice ? 1
configuration'” DNS Configuration
==================
Primary DNS Address: 151.1.1.253
Secondary DNS Address: 127.0.0.1
1.3. Delete
netadmin menu
DNS menu 14.DNS Setup
=========================
0. 'Previous menu'
Choose “3. 'Delete DNS What is your choice ? 3
Details'” Are you sure you want to delete the DNS settings: 151.1.1.253 (Y/n default
is n)? y
4
2 HTTP proxy configuration

Configure the following proxy settings: 151.1.1.253
There is no authentication
2.1. Setup
netadmin menu
=======================================
1. 'Installation'
4. 'CPU redundancy'
7. 'Tunnel'
8. 'Routing'
10. 'Copy setup'
11. 'Security'
19. 'Cloud Menu'
0. 'Quit'
Enter proxy configuration 15. 'Proxy configuration'
menu
15. HTTP Proxy Menu
====================
1. 'View HTTP Proxy Configuration'
2. 'Create/Update Configuration'
3. 'Delete HTTP Configuration'
0. 'Previous menu'
Choose “2. 'Create/Update What is your choice ? 2
Configuration'” and enter Host address (default is 135.250.161.173) ? 151.1.1.253
proxy IP address, port and Proxy Login?
credentials Proxy password?
Proxy port (default is 443)? 3128
2.2. Review
netadmin menu
HTTP Proxy Menu 15. HTTP Proxy Menu
====================
0. 'Previous menu'
5
Choose “1. 'View HTTP Proxy What is your choice ? 1

Configuration'” HTTP Proxy configuration
=========================
Host address : 151.1.1.253
Proxy user :
Proxy Port : 3128
2.3. Delete
netadmin menu
HTTP Proxy Menu 15. HTTP Proxy Menu
====================
0. 'Previous menu'
Choose “3. 'Delete HTTP What is your choice ? 3
Configuration'” Are you sure you want to delete the Http proxy settings:
151.1.1.253 (y/n, default is n) ? y
OmniPCX Enterprise
How to
✓ Execute First Time Registration on OXE
Contents
1 Prerequisites ................................................................................... 2
2 CC-suite-Id ..................................................................................... 2
2.1. Display in spadmin and OmniVista 8770 ........................................................... 2
2.2. Management in “Cloud menu” ....................................................................... 3
3 Starting FTR .................................................................................... 4
3.1. Registration ............................................................................................. 4
3.2. In case of duplication ................................................................................. 4
4 FTR with PIN ................................................................................... 5
4.1. Registration ............................................................................................. 5
4.2. In case of duplication ................................................................................. 5
5 Maintenance ................................................................................... 6
5.1. FTR status ............................................................................................... 6
2
Implementation
1 Prerequisites
To be able to proceed to the FTR, the product needs to follow some prerequisites:
- Internet access has to be possible for the product via a proxy or not
- Local DNS server should be able to resolve the CCI domain names and product should have network access
to the DNS server.
- The product knows its activation account credentials (CC-SUITE-ID) to connect to the ALE CCI.
2 CC-suite-Id
The 'CC-suite-ID' is present in the license file.
2.1. Display in spadmin and OmniVista 8770

spadmin
Display current counters ........................... 1
Display active file ................................ 2
Check active file coherency ........................ 3
Install a new file ................................. 4
Read the system CPUID .............................. 5
CPU-Ids management ................................. 6
Display active and new file ........................ 7
Display OPS limits ................................. 8
Display ACK code ................................... 9
Exit ............................................... 0
Choose “Display active file” Cpu Id 1 = F123456D
Cpu Id 2 = CCSID: aaaaa-bbbbb-ccccc-ddddd
Suite Id = aaaaa-bbbbb-ccccc-ddddd
Your System CPU-Id:F123456D
Notes
CC-Suite-ID will never be the first one in the file (in order not to impact Flex configurations for
which first one is used)
In order for OXE to differentiate CCSID from CPU-Id, CC-Suite-ID is prefixed with “CCSID:”
There is only one CC_SUITE_ID for both main and standby CPU.
3
OmniVista 8770 - Configuration application

Suite Id is displayed on the
main page of the OXE
Notes
When the parameter “Cloud Connect Licensing Enabled” is “No” then the string “-no-suite-id-” is displayed in
the place of Suite id.
2.2. Management in “Cloud menu”

netadmin menu
=========================================
1. 'Installation'
4. 'CPU redundancy'
7. 'Tunnel'
8. 'Routing'
10. 'Copy setup'
11. 'Security'
19. 'Cloud Menu'
0. 'Quit'
Enter cloud menu 19.Cloud Connect Menu
19.Cloud Connect Menu
=====================
1. 'CC-suite-ID'
2. 'Perform FTR'
3. 'View FTR Status'
4. 'PIN Code'
0. 'Previous menu'
If CCSID is present in swk file, What is your choice ? 1
it will be displayed The SUITE ID present in SWK file is 1111-2222-3333-4444-5555
4
3 Starting FTR
3.1. Registration
netadmin > Cloud menu
=====================
1. 'CC-suite-ID'
2. 'Perform FTR'
4. 'PIN Code'
0. 'Previous menu'
Choose 'Perform FTR' and What is your choice ? 2
accept terms and conditions ================== TERMS AND CONDITIONS ==================
I do accept ALE Cloud Connect Terms & Conditions
"(www.enterprise.alcatel-lucent.com/Terms&Conditions) and
commit to inform my customer (y/n).y
Launching FTR ...
ftrtool is still running waiting for tool to exit
FTR Done Successfully

WARNING: Credentials to connect to CCI are not synchronized automatically
with TWIN CPU.Maunal Synchronization is mandatory for proper functioning of
system when CPU Role is changed.
ftrtool has been exited
FTR Details
===========
FTR Status:Success
FTR Host :ftrserver.cloudconnect.ale
FTR Port:443
3.2. In case of duplication
Warning
THERE IS NO NEED TO DO FTR ON STANDBY CPU.
The final credentials obtained can be copied to standby in one of the ways:
- netadmin –m
Option 10: Copy setup
1. 'Copy from twin CPU (all)' (OR)
2. 'Copy to twin CPU (all)'
Warning
BEFORE MAKING A COPY, VERIFY THAT:
DUPLICATION AND ROLE ADDRESSING ARE MANAGED IN THE SAME WAY ON THE TWO COMMUNICATION SERVERS.
NETADMIN IS NOT RUNNING ON THE DUPLICATED COMMUNICATION SERVER AT THE TIME OF THECOPY.
- Swinst/mastercopy
5
4 FTR with PIN

FTR with PIN code option will perform FTR with a 6 digit PIN code. Performing this will completely reset
Cloud Connect configuration and parameters while the system is still in operation.
FTR with PIN can be performed only with the presence of RTR and ccagent process, if these processes are not
running, FTR operation will not be performed.
4.1. Registration
=====================
1. 'CC-suite-ID'
2. 'Perform FTR'
4. 'PIN Code'
0. 'Previous menu'
Choose ‘4. 'PIN Code'’ and What is your choice ? 4
enter the PIN code provided
by ALE Please enter the 6-digit pincode to perform FTR or press 'q' to exit 123456
Launching FTR ...
ftrtool is still running waiting for tool to exit
FTR Done Successfully

WARNING: Credentials to connect to CCI are not synchronized automatically
with TWIN CPU.Maunal Synchronization is mandatory for proper functioning of
system when CPU Role is changed.
ftrtool has been exited
FTR Details
===========
FTR Status:Success
FTR Host :ftrserver.cloudconnect.ale
FTR Port:443
4.2. In case of duplication

Warning
THERE IS NO NEED TO DO FTR ON STANDBY CPU.
The final credentials obtained can be copied to standby in one of the ways:
- netadmin –m
Option 10: Copy setup
1. 'Copy from twin CPU (all)' (OR)
2. 'Copy to twin CPU (all)'
Warning
BEFORE MAKING A COPY, VERIFY THAT:
DUPLICATION AND ROLE ADDRESSING ARE MANAGED IN THE SAME WAY ON THE TWO COMMUNICATION SERVERS.
NETADMIN IS NOT RUNNING ON THE DUPLICATED COMMUNICATION SERVER AT THE TIME OF THECOPY.
- Swinst/mastercopy
6
5 Maintenance
5.1. FTR status

=====================
1. 'CC-suite-ID'
2. 'Perform FTR'
4. 'PIN Code'
0. 'Previous menu'
Choose ‘3. 'View FTR Status'’ What is your choice ? 3
to check status FTR Details
===========
FTR Status:Success
FTR Host : ftrserver.cloudconnect.ale
FTR Port:443
Notes
Example of common errors for FTR status:
- ConnConnectionRefused: Connecting to Proxy failed
- ConnProxyAuthFailed: Proxy authentication failed
- ConnDnsError: DNS Service failed. Could not resolve FQDN
- ConnTlsFailed: Server certificate could not be verified
- ConnStreamClosed: Connection closed by server
- SaslNotAuthorized: Invalid cc-suite-id entered in netadmin
OmniPCX Enterprise
Right to Run (RTR)
How to
✓ Use Right to Run service to check licenses on OXE
Contents
1 RTR .............................................................................................. 2
1.1. Prerequisites ............................................................................................ 2
1.2. Configuration ........................................................................................... 2
2 Maintenance ................................................................................... 2
2.1. Cloud trace.............................................................................................. 2
2.2. Incidents ................................................................................................. 3
2.3. Alarms.................................................................................................... 3
2
Right to Run (RTR)
Implementation
1 RTR
1.1. Prerequisites
The FTR must be completed (see previous steps) and a permanent connection established with the CCI.
The Product knows its CC-Product-ID.
1.2. Configuration
System > Licenses
Review/Modify
FlexLM Licensing Enabled No
Cloud Connect RTR Enabled Yes
Notes
No: the RTR service on Communication Server is disabled. Licensing via the CCI/RTR service is not available.
Yes: the RTR service on Communication Server is activated. If a CC-SUITE-ID is present on the Communication
Server, licensing via the CCI/RTR is started.
Tips
A reboot is required
Warning
FOR COMMUNICATION SERVERS RUNNING ON VIRTUAL MACHINES, VERIFY THAT LICENSING VIA FLEXLM SERVER IS
NOT ACTIVATED. THE TWO LICENSING MODES (FLEXLM SERVER AND CCI/RTR) CANNOT RUN AT THE SAME TIME
2 Maintenance
2.1. Cloud trace

When the system starts up the cloud connect debugging traces are disabled by default. “cloudtrace” tool is
used to enable or disable debugging traces, the output is redirected to “traced”.
On the OXE
Command cloudtrace <verbosity>
Notes
The verbosity value can be ranges from 0 to 7:
0 Disable trace
1 To enable Basic traces
3 To enable XML & RTR traces
4 To enable Dispatcher and Services (Keepalive / CCTool / Standby ) traces
5 To enable RTR service traces
6 To enable all traces
7 To enable Basic and Dispatcher
3
Right to Run (RTR)
2.2. Incidents
Incidents on the OXE
647 Minor This incident indicates “remaining qualifying period” and “Cause Message” of the latest RTR
Response. This incident is raised
(i) After getting response from CCI for the RTRRequest
(ii) In case of failure of RTR Request
648 Critical This incident is raised when OXE goes to PANIC mode because of RTR failure as per CCI
request.
649 Clear This is clear incident for the above (648) incident. It is generated when Re-FTR is performed
and OXE moves out of PANIC mode.
650 Critical This incident is triggered when it finds CC (cloud connect) process is not running properly.
OXE moves to PANIC mode.
651 Clear This is clear incident for the above (650) incident. It is generated when CC process running or
responding again.
Notes
Example of incidents:
647: “CC RTR Response: Rem Period 30.0 Cause “RTR OK” “
647” “CC RTR failure, remaining 20.0 days for Panic”
648: “Panic mode raised further to Right to Run continuous failure”
649: “RTR : Checkout failure, remaining 30.0 days for Panic”
650: “MAO_RTR_PANIC_SET: Link breakdown with the CC process”
651: “MAO_RTR_PANIC_CLEAR: CC process started working”
2.3. Alarms
Alarms related to cloud connect Services are captured in CCAlarm.log file, it is present in /tmpd/ directory.
In general the alarm file has information classified with the below severities:
- Critical Failure
- Major Failure
- Minor Failure
Rainbow - Global overview
Summary
The Pillars Of
Cloud Connect
What is Rainbow?
Rainbow solutions
• Rainbow as Public-cloud
• Rainbow as hybrid-cloud
Architecture
Commercial offer
& links
The Pillars Of Cloud Connect
Cloud
Connect
OPERATION
Cloud
Connect
CONTROL
Rainbow
What is Rainbow?
Alcatel-Lucent Rainbow solutions
Rainbow as hybrid-cloud
Connect Corporate Telephony to the cloud
integration with existing PBX
(Rainbow Agent on PBX)
Rainbow as Public-cloud
Provides overlay services
along side existing solutions
Rainbow
Rainbow
PBX
Rainbow agent
Third-party call control
Alcatel-Lucent Rainbow – Global overview
Clients
Rainbow administration to
provision companies, users API(*)
& PBX
API
Rainbow
Rainbow Web & desktop app.
OXO
Connect R2
Rainbow agent
OXE R12
CSP
Smartphones
Rainbow agent
(*)https://api.openrainbow.com/
For Customers Clients

that need:
A new
flexibility of Independent
collaboration of telephony Rainbow Web & desktop app.
tools
Cloud Service
Provider
Rainbow as Public-cloud CSP
Infrastructure Operated by ALE
Smartphones
Product Rainbow
License model Free – needs a subscription
Services UC a-la-carte services

Traffic
Extended federation
End-user features include:
Chat, Contacts, Presence, File sharing…
Organize your contacts
by names, by enterprise Presence status
Create lists of contacts
Create your “bubbles”
Audio & video

communications
In the office, at home, or on

the road, always access
coworkers and stay connected
with them; No VPN needed, no
IT hassle
Chat discussions with one File shared or

person or in Your smart-phone contacts
received instantly
groups – with presence become available from any
device; you can invite them
instantly to join your community
on Rainbow
End-user features include:
Audio, Video, Screen sharing
Screensharing
Video call
Rainbow as a hybrid-cloud
Rainbow administration:
For Customers Association between a Rainbow
that need both user and his PBX device
Web & desktop app.
Reliability
Flexibility https
of on
of cloud
premise
UC Rainbow
telephony
3rd-party
call control
WebSocket/CSTA
Infrastructure Co-operated by ALE & Customer
or Partner PBX
Product PBX + Rainbow
License model (*) Subscription +

Rainbow agent
Pay per use
Services Rich Telephony – PBX services
Extended federation
UC services
(*) PBX licenses are still required

3rd Party Call Control
Make Call Incoming Call
3rd-party 3rd-party
call control call control
Active Calls
3rd-party
call control
Terminals taken into account by Rainbow
Alcatel-Lucent 80x8 DeskPhones IP Softphone
• Alcatel-Lucent 8018 DeskPhone • IP Desktop softphone
• Alcatel-Lucent 8028/38/68 Premium DeskPhones DECT

• Alcatel-Lucent 8082 (on OXE) • Alcatel-Lucent 300/400/500/500EX DECT Handsets
• Alcatel-Lucent 8088 Smart DeskPhone (NOE business) • Alcatel-Lucent 8212/32/42/62/62EX DECT Handsets
• Alcatel-Lucent 8028s/58s/78s Premium DeskPhones WLAN
Alcatel-Lucent 80x9 DeskPhones • Alcatel-Lucent OmniTouch 8118/28 WLAN Handsets
• Alcatel-Lucent 8029/39 Premium DeskPhones SIP
Alcatel-Lucent 8 Series IPTouch Phones • Alcatel-Lucent 8001/8001G DeskPhones
• Alcatel-Lucent 4008/18/28/38/68 IPTouch Phones Analog
Alcatel-Lucent 9 Series Digital Phones • Analog telephones
• Alcatel-Lucent 4019/29/39 Digital Phones
Architecture
Inter/Intra Company Federation with OmniPCX Enterprise and OXO Connect systems
Intra/Inter company federation

▪ Rich Telephony / IM Presence
Other rainbow users ▪ Dial by Name
Intra-company Intra-company
federation Inter-company federation federation
(admin based)
Company 1 Company 2
Company 1 users Company 2 users
Rainbow
Phonebook
OXE OXE OXO OXO OXO

HA Connect Connect OXE Connect
OXE
OXE
Subnet1 PBXs / sites / supranetwork Company 2
PBXs / sites / supranetwork Company 1
Architecture
Connection overview
Rainbow Cloud Solution

Web & desktop app.
Customer LAN
web.openrainbow.com
Proxy • Https
• WebSocket
• Audio/video
Firewall/NAT
PBX WebSockets
Rainbow agent •The WebSockets protocol allows a two-way

communication with a remote host over internet
•Uses HTTPS port
•One of the key benefits that WebSockets provide is their

ability to traverse existing firewalls and proxies
Architecture
Bots
Alcatel-Lucent Cloud Infrastructure
Emily
PBX Gateway XMPP Core Portal: APIs Media Core

Web
User identity
server
XMPP TURN
PCG
server Admin User Tech. server
HTTP REST API
• PBX driver • Notification • Administration • Authentication • Monitoring Media bridge

- CSTA • Relation • Billing • Search • Statistics NAT / Proxy
- Provisioning • IM / Presence • Contacts
CSTA / HTTP or other over WSS WSS XMPP HTTPS REST ICE: DTLS / STUN / TURN / SRTP
Agent
Mobile Desktop Web
PBX User
Admin
Rainbow applications
Network requirements
Proxy
Depends on the presence of an HTTP Web Proxy
 Following connections take place between Rainbow client/Agent and Rainbow Cloud Services
all XMPP messages and notifications
NAT traversal methods
audio/video media streams

Connection
Secure, Simple, Non IT intrusive
Two ALE CA
Rainbow Cloud
levels of TLS (Transport Layer

Security)
security • Cloud side deployed digital
certificates signed by ALE private
PKI ensure that a PBX Rainbow
agent connects only to a Rainbow
authorized server
• Then the connection is encrypted

Rainbow server Rainbow agent
Certificate credentials
Rainbow credentials
Rainbow
• Once securely connected to a Agent
Rainbow authorized server, agent
itself is authenticated by Rainbow PBX
cloud platform using dedicated
credentials PKI : Public Key Infrastructure
CA: Certificate Authority
Commercial offer and links
Commercial offer and links
 Commercial offer  Find more information and documents on:
UC Services
Enterprise
PBX Services (*)
4€ / user / month
Management
UC Services Business portal web site

Business •https://businessportal2.alcatel-lucent.com/
2€ / user / month PBX Services (*)
Management
UC Services
Essential PBX Services (*)
Free of charge
Management
(*) PBX services are provided by an ALE certified Business Partner
Rainbow web site

•https://www.openrainbow.com/
OmniPCX Enterprise
OXE connection to Rainbow
How to
✓ Connect the OXE to Rainbow
Manage the Rainbow agent in the OXE
Contents
1 Manage companies and PBX in Rainbow ................................................... 2
2 Manage the Rainbow agent in the OXE ..................................................... 3
2.1. Rainbow ID and the activation code ................................................................ 3
3 Link between PBX user and Rainbow user account ....................................... 4
4 Status of the connection with the Rainbow platform .................................... 5
4.1. Check the state of the connection.................................................................. 5
5 Maintenance ................................................................................... 6
5.1. Restart Rainbow agent on OXE ...................................................................... 6
5.2. Log file ................................................................................................... 6
5.3. CSTA connection ....................................................................................... 7
2
Implementation
Warning
NETWORK PREREQUISITES MUST BE COMPLETED BEFORE!
1 Manage companies and PBX in Rainbow

Consult this document:
https://support.openrainbow.com/hc/en-us/articles/115000439510-How-to-manage-an-End-Customer-
company-
Management on Rainbow side is already done. Ask the trainer to show you the companies
and the PBX that are created
Note that you must create dialing rules for your PBX if you want users be able to make some calls from
Rainbow with RCC on deskphone. See:
https://support.openrainbow.com/hc/en-us/articles/115001293464-How-do-I-configure-the-PBX-numbering-
rules-
3
2 Manage the Rainbow agent in the OXE
Connect your OXE to Rainbow with the credentials provided by the trainer
2.1. Rainbow ID and the activation code

/Rainbow/
Select “YES” to enable the
rainbow agent
Enter the Rainbow ID and the

activation code
And click on “Save”
Rainbow domain Leave the default value

Rainbow ID The Rainbow ID is generated by Rainbow. It will be provided by the rainbow administrator.
Activation code The activation code are generated by Rainbow. It will be provided by the rainbow
administrator.
Notes
These credentials must be used for PBX agent configuration
4
3 Link between PBX user and Rainbow user account

Manage the link between PBX user 31001 and the Rainbow account the trainer will give
you.
Test the Rainbow RCC (Remote Call Control) features
Rainbow PC app or https://web.openrainbow.com

Connect on Rainbow with
company administrator
account. Go to “members”
configuration and manage the
chosen member.
In “Phone” tab, select the PBX

from the list (“Device” field)
and the Extension number.
Fill the public number of the
user
5
4 Status of the connection with the Rainbow platform
4.1. Check the state of the connection

/Rainbow/
Check the state of the
connection
6
5 Maintenance
5.1. Restart Rainbow agent on OXE

On the OXE with mtcl account
Command dhs3_init –R RAINBOWAGENT
5.2. Log file

Command more /var/log/rainbowagent.log
Result 017-04-03 18:21:04:145 [I] rainbowagent ---------------------------
-------------------------------------------
2017-04-03 18:21:04:145 [I] rainbowagent rainbowagent Version
1.10.0 - Revision 818f54794727
2017-04-03 18:21:04:145 [I] rainbowagent Built Mar 14
2017, 14:55:06
2017-04-03 18:21:04:145 [I] rainbowagent for OXE
platform
2017-04-03 18:21:04:145 [I] rainbowagent --------------------------
--------------------------------------------
2017-04-03 18:21:04:145 [I] rainbowagent Command line:
/usr/sbin/rainbowagent --log /etc/oxe/rainbowagent.properties
2017-04-03 18:21:04:145 [I] rainbowagent Current time: Mon, 3
Apr 2017 18:21:04 +0200
2017-04-03 18:21:04:145 [I] rainbowagent Start time : Mon, 3
Apr 2017 18:21:04 +0200
2017-04-03 18:21:04:145 [I] rainbowagent Running time: 0d
00:00:00.002
2017-04-03 18:21:04:145 [I] rainbowagent --------------------------
--------------------------------------------
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig Network File loaded :
/usr/netadm/data/netdata
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig CPUIPADDR: 151.1.1.1
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig SUITEID:
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig DNSPRIMADDR: 127.0.0.7
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig DNSSECADDR: 127.0.0.7
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig PROXYADDR:
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig PROXYPORT: 0
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig PROXYUSER:
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig PROXYPASSWD(encrypted):
2017-04-03 18:21:04:146 [I] rainbowagent.RainbowAgentConfig Configuration File loaded
: /DHS3data/mao/ccca.cfg
2017-04-03 18:21:04:146 [N] rainbowagent.RainbowAgentConfig RAINBOW_HOST:
2017-04-03 18:21:04:146 [N] rainbowagent.RainbowAgentConfig RAINBOW_PORT: 443
2017-04-03 18:21:04:146 [N] rainbowagent.RainbowAgentConfig RAINBOW_AGENT_ENABLE: 1
2017-04-03 18:21:04:146 [N] rainbowagent.RainbowAgentConfig RAINBOW_DOMAIN:
openrainbow.com
2017-04-03 18:21:04:146 [N] rainbowagent.RainbowAgentConfig PBX_ID:
zerzerzerzerzerzerzerz
2017-04-03 18:21:04:146 [N] rainbowagent.RainbowAgentConfig PASSWORD(encrypted): ...
2017-04-03 18:21:04:146 [N] rainbowagent.RainbowAgentConfig OLDPASSWORD(encrypted):
...
2017-04-03 18:21:04:146 [N] rainbowagent.RainbowAgentConfig TEMPASSWORD(decrypted):
123...
2017-04-03 18:21:04:147 [D] rainbowagent.RainbowAgentConfig decodePassword(): Issue on
decodePassword() encoded string len = 4
2017-04-03 18:21:04:148 [D] rainbowagent.RainbowAgentConfig decodePassword(): encoded
string = 1234...
2017-04-03 18:21:04:148 [N] rainbowagent.RainbowAgentConfig STATE: 0
2017-04-03 18:21:04:148 [N] rainbowagent.RainbowAgentConfig PBX_IP: localhost
2017-04-03 18:21:04:148 [N] rainbowagent.RainbowAgentConfig CSTA_PORT: 2555
2017-04-03 18:21:04:148 [N] rainbowagent.RainbowAgentConfig PBX_TYPE: OXE
2017-04-03 18:21:04:148 [N] rainbowagent.RainbowAgentConfig USE_PHONEBOOK: 0
2017-04-03 18:21:04:148 [N] rainbowagent.RainbowAgentConfig CONFIG_KA: 3
7
5.3. CSTA connection

Command telnet localhost 2555
Enter “D” and press enter to
enter in debug mode.
Enter “ls” to show the client
number
Enter “ls –m 1” to see the sets
monitored by Rainbow
OXE Software Release 12.1 MD1 new features
OXE R12.1 MD1 new features - Tools “tnet” and “getlogs.sh”
Tools developed by TS to connect and find information from ALE IP telephone sets connected to OXE
Log on with the mtcl account and use “tnet d <directory number>” to connect to an IP telephone set
 A password may be asked for depending on the telephone set type.
 See the example below:
(101)csa> tnet d 31000

tnet version 1.0.2017.05.19
'31000' with IP address '151.1.1.168' ... enabling remote access
Password is *tx8000#
admin@151.1.1.168's password:
BusyBox v1.19.4 (2017-08-28 21:49:37 CEST) built-in shell (ash)

Enter 'help' for a list of built-in commands.
$
Tools “tnet” and “getlogs.sh”
Enter “getlogs.sh” when connected to 8008, 8018 or 80x8s telephones to generate a compressed file. The
file will contain all the telephone information, including telephone version, configuration files, IP
configuration, and logs.
Warning defense messages to take into account before a reset and more!
$ getlogs.sh
############### Start of getlogs.sh version_1.20_build_20170403_122300 ###############
…………………
############### Phone type and appl_mode ###############
type 8078S
Curr boot mode is NOE Next boot mode is NOE appl OK
…………………
############### ... building archive file ... ###############
############### WARNING !!! Since the /tmp folder is not flashed, the file will not survive to a reset ###############
############### /tmp/00809FF7F205-logs.tar.gz can now be downloaded ###############

Tools “tnet” and “getlogs.sh”
To retrieve the file:

 Close any SSH connection to the telephone set
 Enter “ippstat telnet d <directory nb> t 120” on Call Server
 From your PC, open a SFTP or SCP connection to the set
 Log file is in “/var/tmp/” directory
Miscellaneous OXE Release 12.1 information includes:
The Number of “SIP extension” users is increased to 7000 for hospitality services
The OMS can support VoIP G729A with 40ms framing

OXE software Release 12.1 MD2 new features
The ability to forbid 4645 Auto Attendant to transfer calls to pre-defined destinations - Overview
This feature enables the administrator to restrict the 4645 Automated Attendant menu to transfer calls to
some destinations.
Based on:
 The Connection COS of the 4645 Automated Attendant menu, and, the COS of the called user
 A new system option “Forbid 4645 AA transfer” located in the System Voice Mail Parameters
Connection COS
“Forbid Authorized Not authorized
4645 AA transfer”
Call transferred to
False Call transferred to called user
called user
Voice guide “You are not allowed to call this

Call transferred to
True number” will be played to the caller, then the
called user
AA menu will be played again
Forbid 4645 AA transfers to pre-defined destinations - Configuration
New system option

Forbid 4645 Auto Attendant transfer to pre-defined destinations - Configuration
Existing parameters:
 Connection Class of Service located in the user parameters
 For automated attendant menu
 For called user
 Connection Class of Service matrix
Automated attendant COS
Called user COS 0 = forbid

Forbid 4645 AA transfers to certain destinations - Miscellaneous
This feature is only applicable when the called user is local to the node
Not applicable to the numbers that do NOT have a connection COS, such as: Entities/Call Routing Group
Calls, Individual Attendant Calls and Attendant Group Calls
OXE Software Release12.1 overview
Overview
New software Release 12.1

 M2.300.13b
New ACTIS software lock needed is:

 softkey #165 (Release): 46
Ecosystem
 OTMS compatibility
 OTMS R2.2, R2.2.1, R2.3, R2.3.1
 OXE compatibility in network

 Compatible with R11.2.x in the same subnetwork
 OmniVista 8770 compatibility

 R3.2.8
Also available
8088 telephone in NOE mode from OXE R12.0
MD1
NOE mode for 8088 announced earlier this year is available
For more information, see:

 The chapter "New phones and updated range" of this course
 The technical communication available on the Business portal
 8088 NOE Android: Admin Guide for deployment
 oxe12.1_sd_DedicatedSets in system documentation
Update "sipextgw -g x" and "sipgateway" tools
"sipextgw -g x" and "sipgateway" tools are updated in order to give all information available in the mgr
parameters
 Some new SIP parameters were missing from previous releases
Increased maximum number of CSTA clients on OXE increased from 20 to 30
The maximum number of CSTA clients is increased to 30.

In addition to CSTA clients, specific debug sessions with HTML browser can be created.
 In this case, the total amount of CSTA clients session specifics cannot exceed 32.
Hotel/Hospitality: Complete checkout of all guests in one shot via hotdebug menu
This feature is to provide a new option “Check-out of all guests” in hotdebug tool to check-out all guests in
one shot from hotel.
This will reduce the manual effort of the administrator to check-out all guests from the hotel. This is
applicable for both Room management and Guest management with Dynamic and Static multi-occupancy.
(101)csa> hotdebug
*** HOT_DEBUG: MENU ***
[1] - At which room a guest is allocated ?
[2] - Guests chaining from a room number
[3] - List of allocated guests of which equipment number is not a room
[4] - List of not allocated guests of which equip.nbr = -1 and chbr_occ = 1
[5] - List of not allocated guests of which equip.nbr = -1
*** Update data ***
[6] - Update guests equipements numbers within a room
*** Hotel Menu ***
[7] - Starting Hotel Menu
*** Warning : escape Hotel Menu with CTRL Z ***
[8] - Release of hotel semaphores
[9] - busy password not allocated to a guest
[10] - hotel semaphores state
[11] - Voice mailbox management status
[12] - Guests Name and Secret Code
[13] - Room and Guest data
[14] - Menu hotline
[15] - Check-out of all guests
[0] - exit
PER 3005 - Increase the DID translation table size
This feature increases the number of possible DID Number Translator Rules from 2000 to 20000 entries per
DID number translator
Available for:
 DID numbering translator
 incoming or outgoing trunk calls based on trunk group NPD
 Node DID translator

 Local and same Sub-network node Private to Public Overflow
 Network DID translator

 Private to Public Overflow on different ABC-F Sub-network
Support of Hebrew on OXE for IP sets
Hebrew is supported on NOE 3G (8028/38/68), 8018 and NOE 3G EE (8028s/58s/68s/78s) telephone sets
 This possibility was as already available for IP Touch (4028,4038,4068)
To enable Hebrew keyboard for:

 NOE 3G and NOE 3G EE sets: press alt ( ) and space together
 8018 sets: enable the text mode and then press # and *
Support of Hebrew IP telephone sets - Configuration
Hebrew needs to be configured for “Authorized IME”:

 Alcatel-Lucent 8&9 Series → 8&9 Series COS → Phone COS → Authorized IME
Change the display language to Hebrew:

 System
Remote worker possiblility for DeskPhones
Also available
Remote worker for DeskPhones - Overview from OXE R12.0
MD1
8008, 8018, 8028s, 8058s, 8068s, 8078s DeskPhones in NOE mode is now embed a VPN client
DeskPhones can operate outside company network through a third party VPN server without any other
equipment (such as remote access point)
Remote worker network Enterprise network

(home for example) Internet
NOE
OXE
Router VPN Router Firewall

Embedded VPN RTP
VPN client connection
Server
Remote worker for DeskPhones - Configuration
A new menu is available in the set (accessible with “*” + “#” during step 2 initialization)
Accessible with administrator password (if defined) or a PIN code (code is defined at first access of the VPN
menu)
VPN server menu

 Enable VPN
 IP address
 PSK (pre-shared key)
TFTP server menu

 TFTP1/TFTP2 OXE IP address
 necessary because DHCP server on remote worker network will not provide it
 Authentication menu  Reset VPN settings

 Login and password (provided by VPN server
administrator)
 VPN PIN code menu

 Request PIN code on boot (On/Off)
 Change PIN code
Remote worker for DeskPhones - Miscellaneous
Workstation connected to the PC connector of the phone (on remote worker network) only have access to
remote worker’s LAN
 Workstation IP traffic is never tunneled
RTP flow never transit through the Call Server

 When two users on different remote sites call each other, RTP flows will transit through the VPN gateway/server
Remote worker network #1 Enterprise network

Internet
NOE
Embedded Router
VPN client
NOE OXE
Router
Remote worker network #2 Firewall VPN
Server
RTP
Router
Embedded
VPN client
Remote worker for DeskPhones - Documentation
For more information, see Administrator manual in system documentation:

 IPsec_VPN_server_deployment_guide_for_remote_workers (8AL90345)
OXE Release 12.1 new hardware and new telephone sets
New 8008 Deskphone
8008 Deskphone
8008 is a new IP Touch set similar to 8018 set, intended to replace 4018 NOE 2G IP phone and 8001 SIP
device.
Supports most of the 8018 telephone set features with changes in hardware platform:
 Four program keys which are present in 8018 are removed
Technical details:
64×128 pixels, black and white, 5 lines, no backlit
4-way navigator & OK/Cancel Keys
Hands-free and mute keys
6 program keys,F1/2 message keys
Fast Ethernet PC port X2
RJ 9 Headset
Wall mount kit (optional)
Wideband handset
NOE-SIP Dual-stack phone
G711 (a/µ), G722, G729AB, QoS
IPSec VPN client
Power over Ethernet (IEEE 802.3af), class 1
8008 Deskphone support
Same level of service as 8018 set except IPv6 feature:

 NOE, SIP Survivability modes
 Encryption
 Desk sharing
 No CCD features
 Add On Module not supported
 No interface to connect external mini keyboard
 SIP Hospitality mode not supported
 IPv6 feature not supported
Implementation
 Implementation of 8008 Deskphone is similar to other IP Touch telephones
Backwards compatibility with OXE R12 and R11.2

 With those versions, 8008 will be seen as an 8018 by the system
New Call Server boards
New Call Server boards
New CPU8 replaces CPU7-2

New CS3 replaces CS2
Software installation
 With PC Installer 5.2
 OXE R12.1 minimum
 Note: All R12 compatible boards are compatible with R12.1
Bootp can ONLY be performed on LAN1 port of the board
Moving from CPU7s2 to CPU8 or CS-2 to CS-3:

 SATA disk needs to be re-installed. CPU7 s2 CPU8 CS-2 CS-3
OXE < R12.1 Yes No Yes No
OXE ≥ R12.1 Yes Yes Yes Yes
CS3 board - Overview
Main differences of CS3 over CS2

 Better performance
 New processor Intel Atom C2338 SoC processor instead of Celeron
 DDR3 instead DDR2 memory module (maximum 4GB due to software limitation)
 SLAN4 function is directly available on board

 No more daughter board
 No more USB port

CPU8 board - Overview
Main differences between the CPU8 and CPU7-2

 Better performance
 New processor Intel Atom C2338 SoC processor instead of Celeron
 1GB DDR3 RAM instead of 512MB SDRAM
 Native SATA hard disk interface instead of PATA
 Two 10/100BT Ethernet Interfaces compared to 1 in CPU7-2

 No more embedded Ethernet interface
 No more USB interface
 No more compatible with OmniPCX Enterprise VH & WM1 Cabinets
CPU8 board - Cable arrangement
Without dual ethernet:

 Same cable arrangement as CPU6 or CPU7sX
 Remove current cable to MMSFD board
Cable
V24/ CBRMA
Cable Cable Cable

Backup Ethernet Backup
Cable
Cable Ethernet
CBRMA
CPU8 board - Cable arrangement
With the use of second Ethernet interface:

 New 10/100BT interface (WARNING: NOT the same as INTIP3 interface)
 New cable between the CPU8 slave and connecting box when duplication is used
 Remove current cable to MMSFD board
MASTER SLAVE
Cable LAN2
Backup LAN2
LAN1 Cable
LAN1
Backup
Cable
CBRMA
New Cable
CBRMA
CPU8 board - New cable and Ethernet interface
CPU8 board - Miscellaneous
Do NOT put a CPU7sX and a CPU8 in Main-Stand-by duplication state
See Crystal hardware Installation manual for more information on cable connection:
 https://businessportal2.alcatel-lucent.com/oxe-system-crystal-hardware-installation-manual
8318 SIP-DECT single base station
8318 SIP-DECT single base station
New DECT base station

 Connected to the LAN OmniPCX SIP
Enterprise 8318 DECT 8212
 Supports up to 20 8212 DECT Phones
 One base station per site:
 No handover between base station
Central site Small remote location
Ideal for users in small areas or companies that only require a small number of cordless handsets to extend
their VoIP solution
8318 SIP-DECT single base station - Main features
Six radio Slot with up to five voice channels

 Five simultaneous calls using G.711
 Four simultaneous calls using G.729
Up to 20 handsets registered
Security: DECT security
Mains power adaptor
Centralized phonebook (csv, XML or LDAP)
Multiline, Call groups, Backup server, …
Auto provisioning
8318 SIP-DECT single base station - Configuration
Embedded web server on the base station permits:

 Configuration and programming of the base station
 Handsets registration and de-registration
 Software or firmware download to base station and handsets
 Control of system logs
DECT handsets declared as SIP extension in OXE Call Server

 SIP registration is done by the base station
8088 in NOE mode with Android OS
How to
✓ Deploy the 8088 device in NOE mode with Android OS
Contents
1 Pre-requisites .................................................................................. 2
1.1. Hardware requirement ................................................................................ 2
1.2. Software requirement ................................................................................. 2
1.2.1. SIP Binary .................................................................................................... 2
1.2.2. OXE version .................................................................................................. 2
1.2.3. Cloud connectivity through HTTP proxy ................................................................. 2
2 Detailed process ............................................................................... 3

2.1. Upgrade to R300 SIP binary .......................................................................... 3
2.2. Migration to the Android version .................................................................... 4
2.2.1. Factory reset ................................................................................................ 4
2.2.2. Switch to NOE mode ....................................................................................... 5
2.2.3. Download Android OS & Binary ........................................................................... 9
2.2.4. Initialization in NOE mode .............................................................................. 10
3 Deployment from LAN ...................................................................... 11

3.1. HTTP server ........................................................................................... 11
3.2. OXE server............................................................................................. 12
2
Implementation
1 Pre-requisites
1.1. Hardware requirement

The minimum hardware version required is P4T4.
Check the hardware version of the Smart DeskPhone, in the Settings application enter tabs: Device >
Software version > Hardware version
1.2. Software requirement
1.2.1. SIP Binary

Switch-over from SIP to NOE is supported with last SIP binary, R300 03.005.0
1.2.2. OXE version

Compatible version of OXE to handle NOE upgrade of 8088 phone M1.403.12 or M2.300.4 minimum.
1.2.3. Cloud connectivity through HTTP proxy

Currently Android OS is delivered through the cloud and requires an HTTP Proxy to download the RPM
files.
It works also without proxy in case of internet direct access (no proxy required for internet access)
Tips
See Part 3 if you want to deploy Android OS from LAN
3
2 Detailed process
The migration of 8088 must be managed in 2 steps:
1. Upgrade to R300 Linux version
2. Migration to the Android version
2.1. Upgrade to R300 SIP binary

Topologies for binary upgrade:
-For a phone connected to Open Touch, the update can be done through the 8770 with Device Application
-For a phone connected to OXE, SIP extension profile, the update can be done through the 8770 with
Device Application
-For a phone in huddle room, the web admin of the phone can be used to update it in the correct version
(feature available since R200.02.015.4) https://192.XXX.XXX.XXX (IP address of the phone)
-For phone out of the box, please use ALEDS to update the phone.
After upgrade check that the phone is upgraded with the right software version. In the Settings
application enter tabs: Device > Software version > Software version
The release R300 Linux allow to download and install a new Android image into the phone.
Now, your phone has the capability to migrate to Android platform. A dedicated switching mechanism is
needed to migrate into “NOE” mode.
This “NOE” mode will run in a new Android OS which will be installed into new partitions.
4
2.2. Migration to the Android version
2.2.1. Factory reset

As the phone was connected before to a system i.e. an OT server or an OXE server, you need to perform a
“Reset to factory” to be able to switch from SIP mode to NOE mode.
On the 8088, during initialization, in step 2

Enter in settings, select tab
Device > Reset
Activate Reset to factory,
button becomes purple then
enter factory password
“*tx8000#”, press
to reset the phone
Confirm by pressing “Yes”,

the phone will reset.
5
2.2.2. Switch to NOE mode

By local MMI
VHE in factory state, and setting DHCP mode is set to “Dynamic”.
On the 8088, during initialization, in step 2

Activate admin rights with
default password *tx8000#
Enter Network->TFTP, set
TFTP address (OXE main IP
address)
Enter Device->Running mode,

set NOE protocol as Yes
Save the changes by pressing

Home physical key on the
right of the sensitive bar
Notes
If proxy is required for internet access:
1. Enter Network -> Proxy, set proxy address & port.
2. Enter Network -> Proxy, Enable proxy (if parameter is not present, disable admin right)
If required, you can have the IP configuration in static mode, though Network -> IP
6
By embedded command
VHE in factory state, and setting DHCP mode is set to “Dynamic” and TFTP configuration is OK.
Procedure is the same as Switch to NOE mode by local MMI except “Enter Device->Running mode, set
NOE protocol as Yes”. Through a SSH connection on phone set, launch command “appl_mode NOE” to
switch to NOE mode.
7
By DHCP “bootfile name” option

This is an example of DHCP server configuration on Windows Server 2012
On VHE 8088
VHE in factory state, and
setting DHCP mode is set to
“Dynamic”.
On Windows Server 2012

Create a scope and configure
scope options
Set scope option 66 to TFTP

address (OXE address)
In case of spatial redundancy
OXE address is node name.
Set scope option 67 (boot

filename) to “lanpbx.cfg”
8
Set scope option 252 (local

proxy config) to your proxy if
one required for internet
access
Check also ROUTER and DNS

are correctly configured and
DNS resolution is OK.
The scope options should look
like this:
Notes
If you will use “User Classes”, all these options must be configured in the policy of the user class.
Then on VHE:
Activate admin rights with default password *tx8000#
Enter Network -> Network DHCP user class and activate DHCP user class, button becomes purple
9
2.2.3. Download Android OS & Binary

Phone will download “Migration Deployment File” (bin8088s) from OXE TFTP server:
12:09:43.690197 IP 135.117.65.199.53314 > xm006099.tftp: 50 RRQ "lanpbx.cfg" octet tsize 0 blksize 1428
timeout 1
12:09:44.054277 IP 135.117.65.199.35175 > xm006099.tftp: 47 RRQ "key.xml" octet tsize 0 blksize 1428
timeout 1
12:09:46.796647 IP 135.117.65.199.46961 > xm006099.tftp: 55 RRQ "bin8088sheader" octet tsize 0 blksize
1428 timeout 1
12:09:46.932458 IP 135.117.65.199.42509 > xm006099.tftp: 48 RRQ "bin8088s" octet tsize 0 blksize 1428
timeout 1
The “Migration Deployment File” contains two needed information for the deployment:
• The binary version to install
• The default BASE_HTTP value (http link to cloud server)
Phone will create the Android needed partitions and install Android OS.
10
2.2.4. Initialization in NOE mode

After switch to NOE mode, the DHCP vendor Class switch to default alcatel.noe.0 to retrieve the TFTP
server address from OXE (or other DHCP server if configured) automatically.
Notes
In case of static configuration, you may need to reconfigure IP settings & TFTP server address.
To access the MMI menu:
-Press the Settings key

-On the top right end corner there is an icon with a Key to access administrator menu
-Enter the default password *tx8000# and press OK
Select the Network entry to access the IP parameter and TFTP parameters to set back the corresponding data.
If properly connected to OXE server, the phone should display the registration screen:
11
3 Deployment from LAN

TFTP server (OXE Call Server) is used for download “Migration Deployment Files” of 8088 (bin8088s, dat8088s
and noe8088s files)
HTTP server is used for download Android OS (rpm file)
If no BASE_HTTP is configured in lanpbx.cfg file on OXE, Android OS is downloaded from the cloud.
If you want to use your own http server, you need to define in the lanpbx.cfg file the BASE_HTTP option. This
will override the default link.
3.1. HTTP server

The structure of the HTTP server tree must be correlated with the format of the link to the rpm file:
<BASE_HTTP>/8088/binaries/<version>/8088_bin_<version>.rpm
Ex : http://192.168.3.1/NOE/8088/binaries/<version>/8088_bin_<version>.rpm
Where BASE_HTTP= http://192.168.3.1/NOE/
Copy the folder /8088/binaries/<version>/ under BASE_HTTP on HTTP server.
Example with Windows Server 2012:
12
3.2. OXE server

HTTP server for download is managed in lanpbx.cfg file located on OXE under /DHS3data/mao:
Where:
-IP_DOWNLOAD= is IP address of OXE or internal TFTP server
-IP_CPU1= is IP address of OXE server
-BASE_HTTP= is the URL where binaries are located on HTTP server
On OXE, lanpbx.cfg file can exists or not (exists always in OXE spatial redundancy)
On the Call Server with mtcl account

Command lanpbxbuild
Choose 2 (Add) for new file or

add new parameters in
existing file
Choose 4 (Modify) for existing
file to modify existing
parameters
Example for Add :

For download IP, choose 2 and
enter TFTP IP address (OXE IP
in this case) and return
For CPU1, choose 5 and enter

OXE IP address and return
For HTTP, choose i and enter

BASE_HTTP URL
Choose 0 to go back than 6 to

apply changes than 0 to quit
4059EE 1.8
Virtual desktop environment compatibility
4059EE is now compatible with Citrix XenDesktop

 ALE Keyboard is not supported in this case
Possibility to add multiple devices in the application

Virtual desktop environment compatibility
Device is selected during application startup when more than one device is configured
UI updates
New queue bar
Next queue
Camped & Routing queue
Hold queue
VIP call, regardless of queue
Emergency call, regardless of queue

UI updates
Improved visibility for Out of Service and timeout states

UI updates
New icons for phone lists
Toolbar icons updates

Book your remote demo
through the
eDemo website!
• What’s in for you FREE SERVICE to conduct remote

 Demonstration booking forms
demonstrations on your premises or
 User guides
 Requirement lists the customer’s from our data center
 Videos on selected ALE Communications and
 Access to the help desk (from 9am to 6pm CET – PST) Network solutions
 And much more!
http://edemo.al-mydemo.com/
• Specific demonstrations can be handled upon request

Evolution To R12 - Issue 03 ENTPWTE126 - Nodrm

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Evolution To R12 - Issue 03 ENTPWTE126 - Nodrm

Uploaded by

Copyright:

Available Formats

OMNIPCX ENTERPRISE - RELEASE 12

EVOLUTION TO R12 - ISSUE 03

New major release

Compatible with OpenTouch 2.1.1, OpenTouch 2.2 and OpenTouch 2.3

OmniVista 8770 software version 3.2

New OPS license files

Goal of the feature:

Compatibility CPU7-2 CS-2 IBM / Lenovo ▪ VMware ESXi

40GB hard disks must be used

HP-DL320e G8v1: BIOS upgrade is mandatory.

*** CPU7-2 Board version 3BA23259ABJE05?? ***

 Combination Example: User

Call presentation possibilities:

Option “Forward if set is oos” = true ?

Option “Overflow to sec tandem if main oos” = true ?

Are all secondary sets « oos » ?

multidevice 31000 multidevice 31010

Goal of the feature:

Behavior until R11.2:

 A conference circuit size 15 is requested if a circuit of size 7 is not available.

 A conference circuit size 30 is requested if circuit sized 15 is not available.

Behavior until R11.2:

Option “Provide conf. circ. to other dom”

Initiator domain Domains Domains Search cc will be

« Accept cc .. » = Yes “Provide cc…”= Yes “Provide cc …”= No D1,D3,D5

Initiator domain Domains Domains Search cc will be

« Accept cc.. » = No “Provide cc …”= Yes “Provide cc…”= No D1

Two new hardware platforms for OmniPCX Enterprise

Compatible as of OXE R12.0

Goal of the feature:

It is now possible to record dynamic voice guides on OMS

Reminder: SUSE OS must be installed

Goal of the feature:

Goal of the feature:

Goal of the feature:

Goal of the feature:

Current menu: New menu:

« Cancel » is replaced by « Delete »

Black and White Color

8018 8028s 8058s – 8068s – 8068s BT 8078s – 8078s BT 8088 – 8088 BT

2.3 inches 2.8 inches 3.5 inches 5 inches 7 inches

 Regarding 8058s deskphone:

Ambient Light Sensor

USB port with boost charging

See datasheet for more information:

Skin USB USB Boost Back Logo Ambient Light

8058s Available Available Available Not Available Available Available

8068s Available Available Available Available Available Available

8078s Available Available Available Available Available Available

USB Boost Charging

Ambient Light Sensor Forced Active

Note: Modification of these parameters requires a telephone set reboot

NOE-3G EE Skin Number

Note: Modification of these parameters requires a telephone set reboot

Introduced as NOE set with R11.2.1

As of 8018 R200 and R11.2 MD7 patch

New Features with 8018 R210 and OXE R12.0

Initialization / upgrade in NOE mode

Protection against network / power cut

Retro-compatible New desktop charger Compatible

OXE WBM is a Web Application to configure OXE

Supported browsers Authentication CMISE gateway OmniPCX

* CPU7-2 Board version 3BA23259ABJE05?? *