Release Note OXE_SW

TC3085 ed.02

Release Note for OXE_SW application

This Release Note provides technical information about the OXE_SW application allowing to update the components
binaries in the OXE (like the phones for example).

Revision History
Edition 2: January 20, 2024 Sebastien Ehrhard Update (version 20240120_103000)
Edition 1: November 14, 2023 Sebastien Ehrhard Creation of the document (version 20231120_162300)

Legal notice:
www.al-enterprise.com The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other
trademarks used by affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other
trademarks are the property of their respective owners. The information presented is subject to change without notice. Neithe r
ALE Holding nor any of its affiliates assumes any responsibility for inaccuracies contained herein.
© Copyright 2024 ALE International, ALE USA Inc. All rights reserved in all countries.
Table of contents
1 Introduction ............................................................................................................................................ 3
2 What is OXE_SW ..................................................................................................................................... 4
3 Supported components binaries ............................................................................................................... 5

4 Features ................................................................................................................................................. 6
4.1 Add OXEs ......................................................................................................................................... 6
4.2 Remove an OXE ................................................................................................................................ 7
4.3 Get the OXE and components versions ............................................................................................... 7
4.4 Declare a new component binary ....................................................................................................... 9
4.5 Remove a component binary or complete component ....................................................................... 10
4.6 Upload component binaries to an OXE .............................................................................................. 10
4.7 Backup the current component binary .............................................................................................. 13
4.8 Restore a component binary from a backup ...................................................................................... 13
4.9 Remove a single backup or all backups of a component .................................................................... 14
5 Get the application ................................................................................................................................ 16
6 Installation and configuration ................................................................................................................. 16

7 Upgrade ............................................................................................................................................... 16
8 Limitations, restrictions and good practices ............................................................................................. 16

8.1 Limitations and restrictions .............................................................................................................. 16

9 Help ..................................................................................................................................................... 16
10 Troubleshooting .................................................................................................................................. 17
11 Bugs or new features requests ............................................................................................................. 17

12 Development history (fix and new features) .......................................................................................... 18

12.1 New features and fix since last delivered version (20231120_162300) .............................................. 18
12.2 Previous versions history ............................................................................................................... 18

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 2/19
1 Introduction

OXE_SW is an application which allows to upload the binaries of OXE components (like phones for example)
from a PC.
It does not trigger the update of the components but “only” puts the binaries to the OXE appropriate folders.

The application works on Microsoft Windows operating system. It is delivered “as is” without any guarantee.
It is not an officially supported product, but we will do our best to fix any issue and implement enhancement
request.

Glossary

▪ OXE: OmniPCX Enterprise

Disclaimer
This documentation is provided for reference purposes only. While efforts were made to verify the
completeness and accuracy of the information contained in this documentation, this documentation is
provided “as is” without any warranty whatsoever and to the maximum extent permitted.
In the interest of continued product development, Alcatel-Lucent reserves the right to make
improvements to this manual and the products it describes at any time without notice or obligation.

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 3/19
2 What is OXE_SW
The application connects to the OXE through telnet or ssh and FTP or SFTP and transfers components (mainly
phones) binaries files to it.

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 4/19
3 Supported components binaries

• 80x8S, 8008, 8018 NOE and SIP

• 86x8 (ALE-300, 400, 500) NOE and SIP
• ALE-120 addon module (APK and APP)
• 84xx (ALE-20, 20h, 30h) NOE (IP and TDM)
• EM200 addon module
• 80x8 (8028, 8038, 8068) NOE IP
• H3_6X (ALE-2, 3)
• 8378 xBS
• 8088 NOE (warning: an access to the cloud or internal web server is still needed to upgrade the phones)

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 5/19
4 Features

4.1 Add OXEs

Right click in the OXE window to add a new OXE. Then configure the details to connect to it:

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 6/19
 Name: the name of your OXE (can be whatever you want).
Press <Enter> to update the tab title.
Address: your OXE IP address (role address in case of
duplication)
mtcl password: the password to connect to the mtcl
account
swinst password: the password to connect to the swinst
account
timeout: the maximum time in seconds to try to establish a
connection

To add another OXE, just right click on an existing OXE tab or on the empty space right to the OXE tabs:

4.2 Remove an OXE

To remove an OXE, right click the OXE tab and select the delete entry in the menu:

4.3 Get the OXE and components versions

Press the Refresh button to read the OXE and components versions:

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 7/19
Deploying one line will show the binaries which have been backed up on the OXE.

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 8/19
4.4 Declare a new component binary
To declare a new component binary, just drag it from you the Windows file explorer and drop it to the SW
window:

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 9/19
The component type and binary version is automatically detected.
If not, the file may be corrupted or does not have the appropriate format or is not supported by the
application.
Important note: the files are not copied from the source folder to another folder. The application only takes
the source folder path and name to create the entry in the SW window. So do not delete the binary files in the
source folder.

4.5 Remove a component binary or complete component

Select the component binary and press the <Delete> button of the keyboard to remove it from the
application.
Select a component name to delete all its binaries.

Note: it does not delete the source files.

4.6 Upload component binaries to an OXE

To upload a component binary to an OXE, select it in the SW window and drag and drop it to the selected OXE
window:

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 10/19
Once dropped, a console is displayed to follow the process and a popup asks for confirmation:

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 11/19
If Yes is selected, the binary files are put in the appropriate format to the appropriate OXE folder. In case of
duplication, the binary if uploaded on both call servers.

Note: to also upload the binaries to the inactiv partition check the dedicated checkbox:

It is also possible to upload several components binary at the same time. Select them in the SW window
thanks to <Ctrl><Left-click> and drag and drop them to the selected OXE window.
In that case, the Remember my answer checkbox in the confirmation popup allows to either confirm the
upload for all the selected components binaries or get the popup for each one.

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 12/19
4.7 Backup the current component binary
Before each new upload, the current component binary is backed up on the OXE. The backed up binaries are
listed in the OXE window:

Note: only the last three binaries are backed up. Then, the oldest one is replaced.

Caution: if some backups are no more needed, remove them (see section xx). This will help to not saturate
the OXE partition.

4.8 Restore a component binary from a backup

It is possible to restore a backup by selecting it in the OXE window and drag and dropping it to the OXE
window:

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 13/19
4.9 Remove a single backup or all backups of a component
Select the component backup and press the <Delete> button of the keyboard to remove it from the OXE.
Select a component name to delete all its backups.
Multiple selection are possible thanks to <SHIFT> button.

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 14/19
This will remove the backups on the OXE and help to not saturate its partition.

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 15/19
5 Get the application

The application is delivered in a .7z file.

It is available here: https://myportal.al-enterprise.com/a6f5I0000008SNbQAM in the “Software / Tool :
OXE_SW upload the binaries of OXE components” section.

6 Installation and configuration

Just extract the “oxe_sw” folder contained in the delivered file.

The “oxe_sw” folder contains:

• oxe_sw.exe: run this file to start the application

• oxe_sw.ini: the application configuration file

See also section 4 for the detailed features and how to set them up.

7 Upgrade

Just back up the oxe_sw.ini file.

Then install the new version and put back your backed up oxe_sw.ini file.

8 Limitations, restrictions and good practices

8.1 Limitations and restrictions

• See in the other sections

9 Help

There is a help menu with a video showing the application is use, details on the version and contact for support
and a short release note with the fix and evolutions:

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 16/19
10 Troubleshooting
When reporting an issue (see section 11), if possible, collect the logs (oxe_sw.log file).

11 Bugs or new features requests

As written in the introduction, the application is delivered “as is” without any guarantee.
It is not an officially supported product, but we will do our best to fix any issue and implement enhancement
requests.
So do not hesitate to send any bugs, feature requests or just supporting messages to sebastien.ehrhard@al-
enterprise.com.

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 17/19
12 Development history (fix and new features)

12.1 New features and fix since last delivered version (20231120_162300)
version 20240120_103000

• add feature to delete one (or all) backup line(s)

• add support of 8088 NOE (add to release note with warning about the cloud or external http server)
• fix issue with OXE using telnet (no issue with OXE using ssh)
• fix issue when refreshing the components tree, if some backups were manually deleted, the backups
lines still appeared
• fix issue with redundant OXE (standby CPU was not always correctly updated with the good binaries)
• add warning in console when OXE partition is almost full
• in console, error message are now in red
• fix issue when refreshing the components tree with OXE running R10.1 N3 versions (OXE version was
not displayed)

12.2 Previous versions history

version 20240120_103000

• add feature to delete one (or all) backups on OXE

• add support of 8088 NOE
warning: an access to the cloud or internal web server is still needed to upgrade the phones
• fix issue with OXE using telnet (no issue with OXE using ssh)
• fix issue when refreshing the components tree, if some backups were manually deleted, the backups
lines still appeared

version 20231120_162300
first officially released version

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 18/19
Submitting a Service Request
Please connect to our eService Request application.

Before submitting a Service Request, please be sure:

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

- END OF DOCUMENT -

OXE_SW -
Release Note for OXE_SW application TC3085 ed.02
© Copyright 2024 ALE International, ALE USA page 19/19