Professional Documents
Culture Documents
TC3009 ed.08
Revision history
Edition 1: November 17, 2022 creation of the document for ALE-120 1.14.27 and 1.15.32
Edition 2: January 13rd, 2022 new version 1.16.34 + information about report in previous release N1, M5 with
restrictions
Edition 3: March 23rd, 2023 new version 1.16.36 + new explanation for private server.
Edition 4: July 11th, 2023 new version 1.17.37 + update after comments received
Edition 5: Sept 15th 2023 new version 1.19.41 (crash issue fixed, taken by OCO/OCE)
Edition 6: Oct 12th 2023 new version 1.19.42 (crash issue fixed, screen saver)
Edition 7: Dec 7th 2023 new version 1.20.48 (synchronization update improvements)
Edition 8: January 29th 2024 Document update following cascading feature availability with
phone version >=1.40.13,
a new reference 3ML37120AB is required at first position when more than one ALE-120
is connected.
Legal notice:
www.al-enterprise.com The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other
trademarks used by affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other
trademarks are the property of their respective owners. The information presented is subject to change without notice. Neither
ALE Holding nor any of its affiliates assumes any responsibility for inaccuracies contained herein.
© Copyright 2024 ALE International, ALE USA Inc. All rights reserved in all countries.
Table of contents
1 Overview ................................................................................................................................................ 3
1.1 Generalities ...................................................................................................................................... 3
1.2 USB-C Connectors ............................................................................................................................. 3
1.3 Smart wheel support multi pages: ...................................................................................................... 4
2 Hardware configuration ........................................................................................................................... 6
2.1 ALE-120 references characteristics ..................................................................................................... 6
2.2 Cascading configuration (phone version >= 1.40.13) .......................................................................... 6
2.3 Single ALE-120 configuration ............................................................................................................. 7
2.4 Supplying rules ................................................................................................................................. 7
2.4.1 OXE configuration ....................................................................................................................... 8
2.4.2 OXO (OCO/OCE) configuration ................................................................................................... 10
3 Software ............................................................................................................................................... 12
1.1 Generalities
It is possible to connect an USB headset behind the free USB-C connector of the last ALE-120.
• Multi-page support
3 pages support on OXE
2 pages support on OXO
➢ Home page
The central point of the wheel acts as “HOME” key,
Short press: goes back to the “home page”, default as the page number one
Long press: define the Selected page as “home page”
• Headset detect when plug in in the USB-C connector of the last ALE-120,
• Single call (make/accept/end through line key),
• Mute/unmute (function / sync with set),
• Volume up/down on phone.
Note:
Minimum version for cascading:
OXE: N2.534.7.b
OXO: 6.0/121.001
- Phone may be powered either by a PA, either by POE with power boost activated
- When using one single ALE-120, this one will be powered by phone
- When using 2 or 3 ALE-120, a PA is mandatory to be plugged in the first ALE-120 at right side of the
phone
Note: If PoE Power Boost (capability to provide more power through a setting in the call server) is not
available, a PoE injector can be used. This will allow to save one USB port, for the keyboard for example.
If the switch in which the the is connected is call compliant an external power supply is not needed but a
specific management of the set has to be done:
Alcatel-Lucent 8&9 Series COS -> Phone COS: Power Boost
If no external power supply is plugged on the phone, it is required to set the power boost in the OCO/OCE or
the OXE configuration for the switch to identify a class 3 equipment phone.
• One ALE-120 (72 keys: one physical page of 24 keys + 2 virtual pages of 24 keys): When turning the
finger on the addon wheel, the pages are changed sequentially when the finger passes over the
associated segment.
• Up to 3 ALE-120,
• 2 pages per ALE-120 (fixed configuration): 48 keys per ALE-120, 24 keys per page,
• Max keys per desk phone: 3 ALE-120 * 48 keys = 144 keys,
It is important to have a phone version >= R200 1.20.16 to have the update functional,
For the cascading, it is required to have a phone version >= R300 1.40.13
During several steps of production, following software version were embedded in ALE-120 at production:
• 1.19.43,
• 1.20.40,
• 1.16.35,
• 1.15.32,
R&D recommendation is to avoid mixing other version of phones and ALE-120 combinations listed in the below
table.
Remark:
All production versions have been qualified by R&D. For example, you do not see the factory version 1.16.35
in the table, but it works for release R200.
Key Summary
CRPLAOM-220 custom skin,resource synchronization improvement.
CRPLAOM-233 Resource update improvement.
Key Summary
CRPLAOM-203 After the completion of resource synchronization on a customized skin, the AOM skin is not correct.
3.4.2 Restriction
No DSS/DSU feature with an ALE-120.
Key Summary
CRPLAOM-127 After a phone reset, ALE-120 prompts an android error.
Key Summary
[ALE-120][services]: The app logs can't be obtained by first running the getlogs command on the phone
CRPLAOM-102
after the ALE-120 connects to the phone.
CRPLAOM-89 [Related] : [Alpha-18][ALE-120] AoM is crashed while answering internal incoming call
CRPLAOM-100 Alpha - Pleiades NOE - ALE-120 : reset occured when supervised call was notified
CRPLAOM-101 [ALE-120] Addon freeze while receiving incoming call, and resume after several minutes.
Key Summary
CRPLAOM-99 Add the screenshot when getting ALE-120’s logs
CRPLAOM-98 ALE-500 + ALE-120 brightness synchronization NOK after NightMode
When phone exit no light mode during ambient light become light, ALE-120 backlight display
CRPLAOM-90
wrong.
CRPLAOM-86 Couldn't receive the HID_MSG_UPG_DONE after the ALE-120 device upgrade
CRPLAOM-85 Screen of the ALE-120 is not turned off when the phone is.
CRPLAOM-82 when the phone enters in no light mode, AOM still is lightness.
CRPLAOM-79 The log level should be saved on ALE-120 side.
After the AOM reset, the brightness isn't synchronized with phone and touching the smartpad
CRPLAOM-19
of ALE-120 can't wake up the screen.
Key Summary
CRPLAOM-64 After the phone verswitch, the first ALE-120 keys' pressing freeze.
CRPLAOM-58 when phone enter no light mode, AOM still is lightness.
CRPLAOM-57 The labels of upper screen and lower screen don't appear at the same time.
CRPLAOM-56 The first key is missed after the ALE-120 is upgraded from 1.14.27 to 1.15.32.
• During the upgrade phase, do not make any communication with a headset connected to the last ALE-
120, the audio could be cut during the upgrade process,
• Do not interrupt any flashing process of the ALE-120 (white bar (one, two or three) on AOM during
the flashing process),
• The upgrade process can take up to 45mn for 3 ALE-120, if it fails, there is a retry every 24 hours,
• You can check the reference of the AOMs via i/About/hardware/USB devices/ALE-120 Key Expansion
Module/PCMS/3ML36120ABAA01,
• Before upgrade, you should determine which part you need to upgrade. The version format is x.yy.zz,
yy is the OTA version, zz is the APK version.
If there is the same OTA version, ALE-120 upgrade should be APK upgrade only.
If there is the same APK version, ALE-120 upgrade should be OTA upgrade only.
If OTA version and APK version both need upgrade, OTA and APK upgrade should be executed, OTA
upgrade at first and then APK upgrade.
Then you can upgrade your ALE-120 by any of the following three ways.
2. If you have a USB-C key, just do as following step. Or you may need prepare a USB-A turn USB-C
adapter.
This chapter applies to upgrade OTA only while there is no APK version upgrade requirement.
Such as upgrade from 1.14.27 to 1.15.27.
1. Download upgrade OTA binary from the MyPortal.
OTA binaries are not delivered with each APK versions, we can use the OTA binaries whose
system version numbers are same. (The version format is x.yy.zz, x.yy is the system version, zz is the
APK version. Ex, if we want to upgrade to 1.02.04 but we don’t find the ALE120_OTA_1.02.04 binaries,
we can use ALE120_OTA_1.02.02 binaries.)
2. All binary files should be saved in the “upgrade” folder of USB key, including
ALE120_OTA_x.yy.zz.gza[a to j],
ALE120_OTA_x.yy.zz.md5sum,
aom_ALE-120_bin,
aom_ALE-120_bin-header.
3. Plug the USB key on the left USB-C port of the last ALE-120 connected to the phone when you look
behind the ALE-120,
4. You will see the prompt “working step***” shown automatically in the screen. If the installation is
successful, the screen will display the following image and reboot.
5. After the upgrade is successful and ALE-120 resets, “SW VER.=***” will appears at the bottom of
the small screen below.
6. The whole upgrade (from copying binaries to new version initializing) spends about 10 minutes.
This chapter applies to upgrade APK only while there is no OTA version upgrade requirement.
Such as upgrade from 1.14.xx to 1.14.yy.
1. Download aom_ALE-120_app and aom_ALE-120-header from MyPortal, and save in the “upgrade”
folder of the USB key.
2. Plug the USB key on the left USB-C port of the ALE-120.
This chapter applies to upgrade OTA and APK at the same time. For example, user want to upgrade
from 1.14.27 to 1.15.28, then OTA and APK should upgrade at the same time. There are two methods
to realize this upgrade.
• OTA upgrade and APK upgrade separately through USB key according to guide from 2.2.2 and 2.2.3.
Note: OTA upgrade at first and then APK upgrade is necessary.
• OTA and APK upgrade together through USB key. Put all the files (OTA files + APK files) into the
upgrade folder of USB key as below, then plugs it to the ALE-120 which is connected to the phone.
• Upgrade by cloud is triggered automatically if ALE-120 is connected with terminal and the
version is not the latest. Terminal takes responsibility of checking AOM header file (name as:
aom_ALE-120_APP-header and aom_ALE-120_bin-header) on OXE or OXO servers, and compare
ALE-120 version number in header files with current version. If current version is lower than
version required in header file, cloud upgrade process will be launched. When ALE-120 SW
update from Cloud, “SW update” is displayed on the ALE-x00 phones’ screen.
• Aom_ALE-120_APP-header is high priority than aom_ALE-120_bin-header, so aom_ALE-120_APP-
header should be updated to the servers even if the APP version has been included in the
OTA files.
• Upgrade by cloud is applicable to ALE-x00 with one ALE-120 or several ALE-120 since the phone
version 1.40.13,
• Upgrade with multi ALE-120s cascade is supported from phone version 1.40.13 (up to 45 mn).
• Downgrade is not possible via the cloud.
• An ALE-x00 phone connected to ALE-120 is mandatory to upgrade by Cloud as below:
If the user wants to use a private cloud server instead of ALE cloud server. He must declare it in the
lanpbx.cfg. Then the private server will be the higher priority than ALE cloud server. It is the
responsibility of the people in charge of the server to update the Android image (OTA directory) each
time a new Android image is present on the cloud 1.15.xx to 1.16.yy for example. For the apk file, it is
done automatically by the call server on OXE only, not on OCO/OCE ( in this case, The APK file should
also be deployed in the cloud server as no APK file is deployed in the OCO/OCE call server). Alcatel does
not provide the way to install a server, you can have some clue in the TC2461 ( windows server ) for the
installation of an http server written originally for the 8088.
Totally 11 OTA files need to be put into the folder of the private server which are
ALE120_OTA_X.XX.XX.gza[a to j] and the md5sum file like below.
On the cloud:
https://devices.al-enterprise.com/ale_tx/ALE-120/SYSTEM/1.16.34/ALE120_OTA_1.16.34.gzaa
https://devices.al-enterprise.com/ale_tx/ALE-120/SYSTEM/1.16.34/ALE120_OTA_1.16.34.gzab
https://devices.al-enterprise.com/ale_tx/ALE-120/SYSTEM/1.16.34/ALE120_OTA_1.16.34.gzac
...
final file:
https://devices.al-enterprise.com/ale_tx/ALE-120/SYSTEM/1.16.34/ALE120_OTA_1.16.34.gzaj
https://devices.al-enterprise.com/ale_tx/ALE-120/SYSTEM/1.16.34/ALE120_OTA_1.16.34.md5sum
It is important to update the 2 files on OXE to point to the new version of APK (applications image only)
and OTA (whole android image: big size):
aom_ALE-120_app (in zip file APK)
aom_ALE-120_bin (in zip file OTA)
- END OF DOCUMENT -