OXO - Connect - Evolution - 3.1 - SD - MaintenanceServices - 8AL91229USAB - 1 - en - (Glossario de Erros Dos Alarmes Do OXO)

Alcatel-Lucent OXO Connect Evolution
Expert Documentation: Maintenance Services

Release 3.1 - April 2019
8AL91229USAB Ed. 01
Legal notice
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: http://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.
© 2019 ALE International. All rights reserved. http://www.al-enterprise.com
Disclaimer
While efforts were made to verify the completeness and accuracy of the information contained in this
documentation, this document is provided “as is”. To get more accurate content concerning Cross
Compatibilities, Product Limits, Software Policy and Feature Lists, please refer to the accurate
documents published on the Business Partner Web Site.
In the interest of continued product development, ALE International reserves the right to make
improvements to this documentation and the products it describes at any time, without notice or
obligation.
The CE mark indicates that this product conforms to the following Council Directives:
• 2014/53/EU for radio equipment
• 2014/35/EU and 2014/30/EU for non radio equipment (including wired Telecom Terminal
Equipment)
• 2014/34/EU for ATEX equipment
• 2011/65/EU (RoHS)
• 2012/19/EU (WEEE)
Table of
contents Expert Documentation:
Maintenance Services
Chapter 1
Expert Documentation structure
Chapter 2
PBX diagnostic tool
2.1 Overview.............................................................................................................................................10
2.2 Connecting a management computer to the PBX and powering
the PBX................................................................................................................................................ 10
2.3 Accessing the diagnostic mode..................................................................................10
2.3.1 Accessing the diagnostic mode from the web-based tool...............................................10
2.3.2 Accessing the diagnostic mode from the PBX management console.......................11
2.4 Launching the diagnostic test...................................................................................... 12
2.5 Downloading the diagnostic test results........................................................... 12
2.6 Exiting the diagnostic mode...........................................................................................13
Chapter 3
Replacing/Relocating Sets
3.1 Replacing a Set............................................................................................................................14

3.1.1 Temporary Substitution.................................................................................................................... 14
3.1.2 Permanent Replacement................................................................................................................ 14
3.1.3 Characteristics Preserved During Temporary or Permanent set Substitution ..... 14
3.1.4 Data Preserved During Permanent Set Replacement .................................................... 15
3.2 Relocating a Set ........................................................................................................................ 15
3.2.1 Relocating a Set to an Unused Socket.................................................................................... 15
3.3 Adding Sets ................................................................................................................................... 15
8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 3/83

Table of
3.4 IP Phones.......................................................................................................................................... 15
3.4.1 Automatic Set Relocation Retrieve............................................................................................ 16
3.4.2 Automatic Set Relocation Replace.............................................................................................16
Chapter 4
Backup/restore
4.1 Backup/restore of all data................................................................................................. 18

4.1.1 Overview..................................................................................................................................................18
4.1.2 Configuration......................................................................................................................................... 18
4.2 Backup/restore on SD card..............................................................................................19
4.2.1 Overview..................................................................................................................................................19
4.2.2 Concerned data................................................................................................................................... 19
4.2.3 Backup/restore operations..............................................................................................................19
4.2.4 Logs and anomalies...........................................................................................................................21
4.2.5 Backup status....................................................................................................................................... 21
4.2.6 Restore status.......................................................................................................................................22
Chapter 5
System Messages
5.1 Interface markers ..................................................................................................................... 23

5.2 Hardware messages............................................................................................................... 23
5.3 History messages .................................................................................................................... 27
5.4 Information displayed ..........................................................................................................64
5.4.1 Types of terminal (INFO 0 of messages 110, 111 and 112) ..........................................64
5.4.2 Reasons for device restart (INFO 1 of message 110)...................................................... 65
5.4.3 Reasons for terminal refusal (INFO 1 of message 111) ................................................. 67
5.4.4 Types of interface (INFO 0 of message 113) ....................................................................... 67

Table of
5.4.5 Additional information contained in message 113 (INFO 1: cause of refusal)......68

5.4.6 Software key states (INFO 1 of message 34) ......................................................................69
5.5 Management of two-color led on attendant station ............................... 70
5.6 Urgent alarms .............................................................................................................................. 71
Chapter 6
PBX start and stop
6.1 Overview.............................................................................................................................................72
6.2 PBX start process..................................................................................................................... 72
6.2.1 Starting a PBX in On state............................................................................................................... 72
6.2.2 Starting a PBX in LoLa boot state.............................................................................................. 72
6.3 PBX stop process......................................................................................................................72
6.4 PBX restart process................................................................................................................ 73
Chapter 7
System Reset
7.1 Warm reset....................................................................................................................................... 74

7.2 Cold reset.......................................................................................................................................... 74
7.2.1 User data.................................................................................................................................................74
7.2.2 System data...........................................................................................................................................75
7.2.3 Cloud Connect data........................................................................................................................... 75
7.2.4 Network, installer passwords and Management Data...................................................... 75
7.3 Factory reset.................................................................................................................................. 76
7.4 Data reset summary................................................................................................................ 76

Table of
Chapter 8
SNMP
8.1 Overview.............................................................................................................................................78
8.2 Protocol...............................................................................................................................................78
8.2.1 Topology.................................................................................................................................................. 78
8.2.2 Security.................................................................................................................................................... 78
8.2.3 SNMP Trap.............................................................................................................................................79
8.2.4 MIB............................................................................................................................................................. 81
8.3 Configuration.................................................................................................................................82
8.3.1 Configuring the SNMP Service.................................................................................................... 82
8.3.2 Notification Filtering........................................................................................................................... 83
8.4 Supervision..................................................................................................................................... 83

Chapter
1 Expert Documentation structure
The OXO Connect Evolution Expert Documentation is split into fifteen separated documents. In
addition, the Cross Compatibility document is the reference for detailed status about supported and
unsupported devices and applications.
These documents are:
table 1.1: Expert Documentation structure
Documentation title Part number
[1] OXO Connect Evolution Expert Documentation: General Presentation 8AL91218xxxx

Summary: this document contains general information on OXO Con-
nect Evolution, such as a brief description of services provided, plat-
form hardware, handsets and user applications available, limits, com-
patibility with standards, environmental constraints.
[2] OXO Connect Evolution Expert Documentation: Hardware: Platform, in- 8AL91219xxxx
terfaces and devices
Summary: this document covers all hardware aspects related to OXO
Connect Evolution. This document also contains commissioning proce-
dures for sets.
[3] OXO Connect Evolution Expert Documentation: User services 8AL91220xxxx

Summary: this document gives the presentation and configuration pro-
cedure of features available for end-users. The final chapter of the
document synthesizes features availability according to the type of de-
vice or application.
[4] OXO Connect Evolution Expert Documentation: Voice mail 8AL91221xxxx

Summary: this document details the integrated voice mail system and
automated attendant (general description, management, services avail-
able for end-users), as well as the configuration procedure to connect
an external voice mail unit.
[5] OXO Connect Evolution Expert Documentation: Mobility 8AL91222xxxx

Summary: this document contains a detailed description of mobility
services available on OXO Connect Evolution. This includes useful in-
formation to deploy an xBS infrastructure, the description of associated
base stations and handsets.
Note:
This document does not cover VoWLAN.
[6] OXO Connect Evolution Expert Documentation: VoIP services 8AL91223xxxx

Summary: this document describes VoIP protocols supported by OXO
Connect Evolution (such as SIP), configuration procedure of private or
public access through IP links, as well as dimensioning and mainte-
nance basic information.

Chapter 1 Expert Documentation structure
[7] OXO Connect Evolution Expert Documentation: Private networks 8AL91224xxxx
[8] OXO Connect Evolution Expert Documentation: General applications 8AL91225xxxx

This document gives a description of various applications available on
OXO Connect Evolution, such as Hotel, Call metering, CTI, Network
management center, multiple automated attendant, multiple entities.
[9] OXO Connect Evolution Expert Documentation: Web-based tool 8AL91226xxxx

Summary: this document describes the web-based tool, which is the in-
tegrated monitoring tool of OXO Connect Evolution.
[10] OXO Connect Evolution Expert Documentation: OmniTouch Call Center 8AL91227xxxx
Office
Summary: this document provides the description and installation pro-
cedure of OmniTouch Call Center Office. The document also includes
presentation and operation of Announcement, Traceability, and a short
description of Agent, Statistics and Supervisor applications.
[11] OXO Connect Evolution Expert Documentation: Management tools 8AL91228xxxx

Summary: this document describes the management tool available for
OXO Connect Evolution(OMC). The document describes the OMC in-
stallation procedure, the different types of access between OMC and
OXO Connect Evolution (local, remote, with or without proxy), the soft-
ware installation procedure of OXO Connect Evolution via OMC and the
list of services that can be managed by OMC.
[12] OXO Connect Evolution Expert Documentation: Maintenance services 8AL91229xxxx

Summary: this document contains basic information concerning the
maintenance of your OXO Connect Evolution. This includes a diagnosis
methodology in case of system of terminal(s) failure, the list of system
messages, procedure to save/restore data, procedure to stop/restart
your system, to replace sets.
[13] OXO Connect Evolution Expert Documentation: Security 8AL91230xxxx

Summary: this document gives essential information to secure your
OXO Connect Evolution. This includes deployment guide for certificate,
management of passwords, management of accesses to services from
LAN/WAN and network configuration for remote accesses.
[14] OXO Connect Evolution Expert Documentation: System services 8AL91231xxxx

Summary: this document gives information about software keys, includ-
ing their complete list. The document also describes operation of OXO
Connect Evolution with NTP (as client or server) and the configuration
of the embedded DHCP server.

Chapter 1 Expert Documentation structure
[15] OXO Connect Evolution Glossary 8AL91232xxxx

Summary: this document contains a glossary of general telecommuni-
cations terms as well as specific terms related to OXO Connect Evolu-
tion.
[16] Server deployment guide for remote workers using deskphones 8AL90345xxxx
In the present document, cross-references are identified by the number in the first column of the above
table.
Part numbers are given in the last column, where xx corresponds to the language code of the
document.
Outlook is either a registered trademark, or a trademark of Microsoft Corporation in the United States
and/or other countries.

Chapter
2 PBX diagnostic tool
The diagnostic tool is used to verify that OXO Connect Evolution components run correctly. The
diagnostic tool can be launched before installing a software version on the (OXO Connect Evolution.
For readability purposes, OXO Connect Evolution is called PBX in the rest of the section.
2.1 Overview
The PBX supports the following boot modes:
• Application mode: this is the default boot mode
In this mode, all the PBX functionalities are supported and all external applications (OMC, web-
based tool) can connect to the PBX.
• Diagnostic mode: the diagnostic tool is launched to perform the diagnostic test of the PBX hardware
components
In this mode, the PBX does not support its functional operations and external applications (OMC,
web-based tool) cannot be accessed.
2.2 Connecting a management computer to the PBX and powering the

PBX
1. If you want to start the diagnostic mode from the web-based tool, connect the management
computer to the PoE hub/switch used to power and connect the PBX to the customer LAN
2. Connect the management computer to the micro-USB port of the PBX to start the PBX
management console.
The micro-USB port (console port) settings are:
• 115200 bauds
• 8 data bits
• 1 stop bit
• No parity
3. Power and connect the PBX to the customer LAN:
• Plug an Ethernet cable into the RJ45 Ethernet port located on the device front panel (identified
as Eth0)
• Connect the cable to the LAN itself via a PoE hub/switch (IEEE802.3af compliant)
2.3 Accessing the diagnostic mode

Before launching the diagnostic test, the diagnostic mode must be configured. It is possible from the
web-based tool or from the console.
2.3.1 Accessing the diagnostic mode from the web-based tool

The diagnostic tool can be launched from the web-based tool in both installer and debug sessions.
1. From the computer, open a web browser and access the web-based tool:
https://<OXO Connect IP address or host name>/services/webapp/
2. Log in to your account

Chapter 2 PBX diagnostic tool
The web-based tool home page opens.

3. Select System > Diagnostic Test
The IPBox Diagnostic Test page opens.
Figure 2.1: Web-based tool IPBox Diagnostic Test page example

4. Click the Start Diagnostic Test Software button
A warning message is displayed.
5. Click OK
The system reboots and starts the diagnostic tool.
6. Go to the PBX management console to continue the operation.
2.3.2 Accessing the diagnostic mode from the PBX management console
On the PBX management console:
1. During startup, press ctrl^b + ^I to enter the PBX main menu
The main menu is displayed:

1- Boot from network

2- Start OXO Connect Evolution
3- Start OXO Connect Evolution & bootp
4- Start diagnostic test software
5- Set system date & time
6- Display Manufacturing data
7- UIT Menu
8- Reset
2. Select the menu option 4- Start diagnostic test software
The PBX reboots and starts the diagnostic tool.
2.4 Launching the diagnostic test

After the system reboot, the diagnostic tool main menu is displayed:
1. Factory Menu
2. Customer Menu
1. Select 2 to enter the diagnostic tool for customer.

The following menu is displayed:
1. ipbox test
2. usb test
3. sdcard test
4. Ethernet test
Q to quit
2. Enter the number corresponding to the diagnostic test to run
• 1: to verify the PBX internal components
• 2: to verify the access to USB key and data written/read in the USB key
Note:
A USB key must be plugged in the PBX front connector.
• 3: to verify the access to SD card and data written/read in the SD card
Note:
An SD card must be plugged in the PBX rear connector
• 4: to perform the Ethernet test and check for packet loss
Note:
eth1 (LAN2) must be connected to the PoE switch.
It is mandatory that no other packet from the network cross the switch. Only packets from eth0 (LAN1) and
eth1 (LAN2) must be present on their subnetwork.
The diagnostic test is launched.
At the end of the test, the diagnostic test results are displayed with the following message:
Example with USB test:
usb test PASSED or usb test FAILED
On next reboot, the system starts up in application mode.
2.5 Downloading the diagnostic test results

To download the diagnostic test results from the web-based tool:
1. Select System > Diagnostic Test
The IPBox Diagnostic Test page opens.
2. Click the Download Diagnostic Test Result button

2.6 Exiting the diagnostic mode

To exit from the diagnostic mode, enter the command quit or q in the diagnostic tool.
The PBX reboots and starts up in application mode.

Chapter
3 Replacing/Relocating Sets
3.1 Replacing a Set

Replacing or moving an IP phone can be achieved by connecting the hardware into the network.
Default parameters are configured on the phone set on connection. To retain individual user
parameters, configuration is required either on the set, or on the OMC and the set.
3.1.1 Temporary Substitution

The replacement set keeps its own default functions (customized settings are not transferred). The
data not transferred are stored in the OXO Connect Evolution system until a set of the same type as
the initial one is connected.
Your terminal is unserviceable Your terminal is repaired
Unplug Plug in Unplug Plug in
Defective Replacement Replacement Repaired

terminal terminal terminal terminal
3.1.2 Permanent Replacement

The maximum quantity of data from the initial set is transferred to the replacement. Data not transferred
are deleted.
Unplug Plug in
"Terminal replacement"
code + password
Defective Replacement
terminal terminal
3.1.3 Characteristics Preserved During Temporary or Permanent set Substitution

• Rights (restricted features)
• Barring level
• Metering profile
• Messages and last caller repertories
• Destination set for metering reminder, forwarding and/or monitoring
• Set belonging to a hunting group and/or a Manager-Secretary relation
• Appointment reminder
• Locked or unlocked set
• Callbacks
• Active forwarding
• Last number redial

Chapter 3 Replacing/Relocating Sets
3.1.4 Data Preserved During Permanent Set Replacement

3.1.4.1 Replacement of Digital Sets
Regardless of the type of the initial digital set and that of the replacement, the function and resource
keys are not preserved. The directory numbers are preserved in accordance with the size of the
directories of the stations concerned.
Note:
The add-on modules are always transferred provided the substitution set supports these modules.
3.2 Relocating a Set

If you move office, you can move your set from one socket to another and still preserve all or part of its
settings.
Before relocating the set:
• You need to change the personal code, which must be different from the default code.
• It is advisable to lock the set.
3.2.1 Relocating a Set to an Unused Socket
Unplug Plug in
"Terminal movement" code

+ Dir. P1
Movement
+ password
(not default password)
3.3 Adding Sets

When adding sets, attention must be paid to the limits on the number of sets and the features offered
by the system software key.
Plug in
The set is recognized as soon as it has been plugged into the socket.
3.4 IP Phones
When an IP phone is connected to the network, default parameters are configured on the phone set on
connection.
To keep individual user parameters, configuration is required on the phone.
OMC configuration is recommended for large networks to activate the Automatic Set Relocation
Replace service.

3.4.1 Automatic Set Relocation Retrieve

The Automatic Set Relocation Retrieve service exchanges the data of the source and target phones.
Example:
Retrieve
If Phone 50 has been configured and now a new IP Phone is connected to the LAN.
This Phone is automatically taken into account by the system with a default configuration and is
operational.
The phone number 150 is automatically allocated to this phone. The Automatic Set Relocation
‘Retrieve’ service is invoked from the newly connected IP Phone 150 (target) to retrieve the
configuration of phone 50 (source):
<ASR-Retrieve-code><Source-EDN>< source phone password>
Phone 150 is reset and has the same configuration as set 50.
This means that for each IP Phone in the network there is another Phone defined in the system with
the IP Phone’s previous default configuration.
For each IP Phone connected there are two Phones defined in the system. A license is required to
create an IP Phone whether it is connected or not. In this situation, for a system with N users, 2xN
subscribers are defined in the system and 2xN IP Phone licenses are required. If N > 100, the number
of subscribers and licenses would exceed the limits of the system (200).
3.4.2 Automatic Set Relocation Replace

The Automatic Set Relocation Replace feature allows the retrieval of user parameters in networks
containing more than 100 sets.
On dialing the ASR-Replace code in the new IP Phone, it requests the EDN and then password of the
existing IP Phone. On successful replacement:
• The New IP Phone is assigned with the existing sets EDN and other properties
• The previous IP Phone with default configuration is deleted
The OMC must be configured to enable the Noteworthy addressASRRep_IP.
To activate this feature:
From the OMC -> System Miscellaneous -> Memory Read/Write -> Other Labels
Enable Noteworthy addressASRRep_IP
Set to TRUE (01)
Note:
By default the Noteworthy address ASRRep_IP is set to FALSE (00)
After a Cold reset default parameters (00) are restored.
When the OMC is configured in this way, more than 100 sets can be configured
Example:
Replace
Phone 50 has been configured earlier. And now a new IP Phone is connected to the LAN. This Phone
is automatically taken into account by the system with a default configuration and is operational.

The phone number 150 is automatically allocated to this phone. The Automatic Set Relocation
Replace service is invoked from the newly connected IP Phone 150 (target) to retrieve the
configuration of phone 50 (source):
<ASR-Replace-code><Source-EDN>< source phone password>
Phone 150 is reset and has the same configuration as set 50 and the previous set is deleted.
Note:
Under normal conditions default passwords are not allowed for set relocation services. If the Noteworthy
addressASRRep_IP service is enabled, a default password can be used.

Chapter
4 Backup/restore
4.1 Backup/restore of all data

4.1.1 Overview
Backed up data
This backup operation concerns all the parameters not reinitialized during a warm reset:
• Global data (software version, backup time and date, etc.)
• Configuration data (types of boards and terminals, characteristics of terminals and groups, keys and
directory settings, numbering plans, directory, Class of Service restrictions tables)
• Data recorded by users (mail, appointment reminders, forwarding)
• Call details counters
Backup operations are performed in any of the following ways:
• Manually by the installer (OMC backup command)
• Automatically and periodically, at a time programmed by the installer, using the OMC
The backup session is exclusive of any OMC operation or customization session; any modification is
ignored during backup; avoid any activation or inhibition of services (appointment reminders are not
protected, forwarding and filtering are refused) which would modify settings.
Any system data modification and any hardware modification on the OMC must be followed by a
backup.
A backup session lasts for more than a minute for a multi-module installation.
At the end of the session, a message appears in the hardware message table (to signal failure) or in
the system history table (to signal success).
Restoration
The restore session is activated manually by the installer (OMC restore command). All the saved data
is restored.
A restoration session lasts for more than a minute for a multi-module installation.
At the end of the session, a message appears in the hardware message table (failure indication) or in
the system history table (success indication).
Note:
After restoration, Management Passwords (see the section Management password in [13]) are not restored.
After an OMC software download with data saving or EPROM backup and restore, Management Passwords are
restored.
4.1.2 Configuration
• Manual backup:
• In the OMC (Expert View): select Data Saving & Swapping -> Commands -> validate the
backup option
• Automatic backup:

Chapter 4 Backup/restore
• In the OMC (Expert View): select Data Saving & Swapping -> Data Saving -> enter date, time
and periodicity for backups
• Restore:
• In the OMC (Expert View): select Data Saving & Swapping -> Commands -> validate the
Immediate Restore option
4.2 Backup/restore on SD card

4.2.1 Overview
This feature backs up customer configuration data and user data on the PBX SD card, with several
possible recovery points, created periodically or on demand.
Note:
As of R3.1, backup is encrypted. Encryption standard used is AES 256.
Configuration and user data are typically restored in case the PBX device is changed, or damaged, and
when device configuration has changed.
The minimum capacity for an SD card is 2GB.
The backup LED on the device front panel indicates backup status:
• If steady green: a scheduled backup is configured
• If OFF: no scheduled backup is configured
• If blinking: a scheduled or immediate backup is in progress
4.2.2 Concerned data

Data that can be saved on the device SD card is classified as system or user.
System data consists of:
• ACD (statistics and configuration)
• NMC
• Metering
• Third party devices (including Stellar AP and Omniswitch configuration)
• System configuration (including tones and data related to terminals)
• Trust store additional
• Third party device binary
User data consists of:
• Voice messaging
• Instant messaging
System binaries/software cannot be backed up on an SD card.
4.2.3 Backup/restore operations

The number of recovery points is restricted by the size of SD Card and the size of the recovery points.
When a new backup is saved, log rotation deletes the oldest recovery point when there is not enough
available space on the SD Card.
All backup files are saved in the format of <type of data>_<release version>_<time
stamp>.tar.gz, for example systemdata_R30_040_001_DDMMYY_HHMMSS.tar.gz.

Configuration and user data is restored from the selected recovery point(s).
The recovery point configured from a specific software version can be restored in the system running
on the same major software version (this is the limitation from the internal data saving process). The
restore operation is not supported from the system running on a major software version, which is
different from the software version where the backed up recovery point was configured.
4.2.3.1 SD card information

To view and (if necessary) format the SD card of the OXO Connect Evolution:
1. On the OMC, go to Data Saving & Swapping > Data Backup & Restore
2. Select the SD Card tab
This displays information that cannot be modified:
1. The status of the SD card of the device (operational or not operational)
2. Its total capacity
3. The free space available on the card
Click Format SD Card if the card needs formatting. A confirmation request is displayed warning that
formatting the card erases the current contents of the SD card.
4.2.3.2 Backup configuration

2. Select the Backup tab
The Backup configuration area allows to control and modify programmed backups:
1. The type of data to back up (system and/or user data)
2. The backup time
3. The number of days separating each backup
By default, the System Data and User Data options are unchecked. Backup time and frequency for
backups can be configured irrespective of the selection of data type. The configured backup time and
frequency is taken into account only when the corresponding data type is selected for backup.
To back up user data, both options (System Data and User Data) must be selected.
If the system and user data backups are configured at the same time, backup is performed
sequentially: the system data is backed up first, then the user data is backed up. If the system data
backup fails, then the user data backup will not be performed.
Once a backup has taken place at the specified time, the next backup dates are automatically changed
according to the specified frequency, but the time for backup remains the same. When clicking the OK
button, all the parameters are saved in the database, even if no SD card is present on the device.
Any change in backup configuration displays a confirmation request, reminding that the SD card must
be valid, not protected against writing and offering enough memory space.
Select the Immediate Backup option to perform an immediate backup.
When immediate backup is selected, both types of data (System Data and User Data) are selected for
backup with Backup time (date and time) and Frequency controls grayed out. By default, Immediate
Backup is not selected.
At least one type of data must be selected. Clicking the OK button opens a confirmation request.
Clicking Yes starts the immediate backup and disconnects the OMC.
4.2.3.3 Recovery points and restoration configuration


2. Select the Delete/Restore tab

The Type of Data area allows to select the type of data (System Data and User Data) to delete or
restore.
Before restoring system data, perform a cold reset of the PBX with the System Data option selected in
OMC (access path: System Miscellaneous > System Reset).
Before restoring user data, perform a cold reset of the PBX with the System Data and User Data
options selected in OMC (access path: System Miscellaneous > System Reset). This steps must be
performed in order to synchronize user data with their associated devices.
The Recovery points area allows to select multiple recovery points from each of the list boxes, before
deleting the selected items. The Restore button is greyed out when the user selects more than one
recovery point in any of the two data types. When only one recovery point is selected in each list box,
you can restore the selected recovery points by clicking the Restore button. A confirmation request is
displayed.
Once your choices are made, use the Delete or Restore button under the two lists.
If you click Delete, the OMC displays a confirmation request. Click Yes to proceed.
If you click Restore, the OMC displays a confirmation request. Clicking Yes starts restoration
immediately and disconnects the OMC.
A backup performed on a PBX can only be restored from the same PBX, or another PBX provided that
the installer password is identical to that of the PBX where the backup was performed.
When the installer password is modified, old backups in the SD card can no more be restored. When
restoration fails due to a wrong installer password, you must first change the installer password with the
password used during the backup. After modification, you can restore the backup.
4.2.4 Logs and anomalies

Event 13 (R_SD_CARD_STATUS_AND_EXISTENCE) is generated for the SD Card with complementary
information (comp_info[0]) indicating one of the following causes:
• The SD card is protected against writing
• The SD card is corrupted
• The file system of the SD card is not supported
• The SD card is operational
• The SD card storage space is very low
• The SD card has been successfully formatted
• The SD card formatting has failed
4.2.5 Backup status

The following events provide information on backup status:
• Event 3 (R_ANO_SAVE _STARTED) is generated when the backup is started
• Event 4 (R_ANO_BACKUP_OK) is generated when the backup is successful
• Event 5 (R_ANO_BACKUP_KO) is generated when the backup fails with the following complementary
information (comp_info[x]) for SD card:
• comp_info[0]) indicates one of the following causes:
• The system configuration backup on SD Card has failed
• The user configuration backup on SD Card has failed

• The SD card is protected against writing

• The SD card is corrupted
• The SD card is not available
• The file system of the SD card is not supported
• The SD card storage space is very low
4.2.6 Restore status

The following events provide information on restore status:
• Event 7 (R_ANO_RESTORE _STARTED) is generated when the restoration is started
• Event 8 (R_ANO_RESTORE_OK) is generated when the restoration is successful
• Event 9 (R_ANO_RESTORE_KO) is generated when the restoration fails with the following
complementary information (comp_info[x]) for SD card:
• The system configuration restoration from SD Card has failed
• The user configuration restoration from SD Card has failed
• The installer password is wrong
• The software version is not the expected one

Chapter
5 System Messages
The system messages are divided into 2 tables:

• the hardware message table
• the history message table
5.1 Interface markers

XX # 1 for the first half-board of slot XX, XX # 2 for the second half-board, XX - YY for the YY access of
slot XX, ***** concerning the system messages.
A board can be cut into 2 half boards, this means that the same board uses 2 LCP codes (one per half-
board). The 2 half boards may or may not be identical.
5.2 Hardware messages

When the table is full, a new fault is stored in place of the oldest message (the table may be emptied
by an OMC command or by cold starting the system).
Type Message Location Additional Information Action
5 CONFIGURATION BACKUP Check the

FAILURE configuration
9 CONFIGURATION RESTORA- Check the

TION FAILURE configuration.
33 KEY REDUCED CPU (80) INFO 0 = reduced feature set index

The features normally associ- • 01 : VMU storage capacity
ated with the active key have diminished
been reduced due to a hard- • 02 : number of VMU and
ware problem (CPU type, insuf- Automated Attendant ports
ficient memory, etc). diminished
• 03 : Automated Attendant
unavailable
• 04 : Audiotex unavailable
• 05 : welcome messages
unavailable
• 06 : distribution list names
unavailable
• 07 : recording of conversations
unavailable
• 08 : duration of please-wait
message diminished
• 10 : number of NMC metering
statements diminished
• 12 : number of languages
diminished

Chapter 5 System Messages
37 eMMC in MSDB is approaching MAIN_CP INFO 0 = Indication of MSDB Replace the

its end of life due to increase in U_SLOT health status: MSDB
block erase count / bad blocks
• 01: device has reached >= 80%
of its life time due to increased
block erase count
• 02: device has reached > =90%
block erase count
• 03: device has reached >=80%
bad block
• 04: device has reached >=90%
bad block
38 Power CPU EE does not sup- MAIN_CP INFO 0 = High byte of detected Replace the
port RAM less than 512 MB U_SLOT RAM size RAM
INFO 1= Low byte of detected
RAM size
Example:
comp_info: 01 00 FF FF
The detected RAM size is 256 MB.
50 ISDN ACCESS REBOOT Board lo- INFO 0 = D-channel

PROBLEM cation.
Interface
marker
51 CLOCK PROBLEM Board lo- INFO 0 = type of interface: T0, T2, Check there
cation. DASS2, etc. is no syn-
Clock synchronization problem
chronizing
detected on an add-on module Access
access in the
interface marker
add-on mod-
ules
52 SPECIFIC ACCESS PROB- Board lo- INFO 0 =1: FCS (Frame Check Se- If the fault re-
LEM DETECTED BY AN ISDN cation. quence) 2: CRC (Cyclic Redundan- curs fre-
BOARD LEVEL 2 cy Check) quently,
Access
check the
marker
connection to
the public
network.

53 ALARM DETECTED ON A Board lo- INFO 0 = XX : type of alarm Ensure that

PRIMARY ACCESS cation. the alarm dis-
• 00 : Level 1 synchronized; all
appears.
Access systems go.
marker • 01 : Synchronization loss in If the fault re-
"multiple frame" mode curs fre-
(synchronization in "double- quently,
frame" mode is correct). check the
• 02 : No multiple frames; T2 connection to
automatically starts "double- the public
frame" mode. network.
• 03 : RDS (...)
• 04 : Remote Frame Alarm.
• 05 : Synchronization loss in
"double-frame" mode.
• 06 : Alarm Indication Signal;
sequence of "1's received,
interface not synchronized.
• 07 : Loss of Frame Alignment
(occurs when the cable is
disconnected).
• 08 : Temporary clock lag;
synchronization established.
• 09 : Error rate; number of error
frames > 5 in 1 second.
• 10 : Erroneous frames received
in the checksum (CRC).
• 11 : The network emits this
alarm when the FALC sends
erroneous frames in the CRC.
54 EXTERNAL FAULT ON S0 Board lo-

cation.
External problem detected on
an S0 access following release Access
message giving cause as "de- marker
activation of level 1"
55 INTERNAL FAULT ON S0 Board lo- If the fault

cation. keeps recur-
Internal problem detected on
ring, check
an S0 access following release Access
the bus wir-
message giving cause as "de- marker
ing.
activation of level 1"
58 ISDN BOARD FAULT Board lo- INFO 0 = type of error (not signifi- If the fault
cation. cant) keeps recur-
A level 1 error was detected by
ring, check
the board's OBC Access
the bus wir-
marker
ing.

72 UNSUCCESSFUL ATTEMPT Check the

TO PRINT printer and its
connection
Message sent by the output de-
cable.
vice (printer) after every 5 failed
print attempts.
103 OBC FAULT Board lo- INFO 0 and 1 = type of fault

cation.
220 DSP OUT OF SERVICE ON Board lo- INFO 0 = DSP number

ONE OF THE BOARDS cation.
INFO 1 = cause (resource problem,
DSP overload, etc)
239 STORAGE MEMORY CPU (80) INFO 0 = type of error

CHANGED OR LOST
• 0 : medium KO
• 1 : medium full
• 2 : checksum error
• 3 : system file control error
INFO 1 = type of medium
• 0 : NAND FLASH CPU
• 2 : HARD DISK
INFO 2 = type of initial medium
INFO 3 = affected memory area
(metering, alarms, voice prompts,
etc)
242 ERROR ON OPENING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt
243 ERROR ON CLOSING VOICE CPU (80) INFO 0 to 3 = type and value of
244 ERROR ON READING VOICE CPU (80) INFO 0 to 3 = type and value of
245 ERROR ON WRITING VOICE CPU (80) INFO 0 to 3 = type and value of

248 DISCHARGED BATTERY OR CPU (80)

BATTERY REPLACEMENT
This results in an incorrect
date/time
5.3 History messages

The events identified by the codes in the system history messages table concern modifications to the
system hardware configuration (appearance/disappearance of boards or terminals, refusal of a board
on exceeding equipment limits) or other events (reset execution, buffer fill rate attained, etc).
When the table is full, a new event is stored in place of the oldest message.
This table is only emptied in the event of a cold system reset.

0 SYSTEM RESTART INFO 0 = reason to restart

1 - RST_MMC: MMC reset com-
mand
2 - RST_MAINTENANCE: reset
due to hardware fault
3 - RST_EXCEPTION: mail notify
queue is full
4 - RST_OS to 5 - RST_LOOP: re-
set following software problem
6 - RST_BOOT: reset due to an ex-
ternal application to take into ac-
count new configuration
For example: push of new software
licenses by Web access, cold re-
set...
7 - RST_SWL: reset following soft-
ware license problem (the values of
the default key are used)
11 - RST_SOFTWARE_SWAP: re-
set following software swap or after
restoration after swap
12 - RST_DB: too many one-way
communications
13 - RST_AUTO_MAINT: automatic
restart programmed by MMC
14 - RST_TIME_OUT: timeout ex-
piration
15 - RST_NOTIFQUEUE_FULL:
no more inodes in notifqueue
0x55 - RST_NIL: normal reset
INFO 1 = restart type
0 - WARM: warm reset is triggered
1 - COLD: cold reset is triggered
2 - FACTORY: factory reset is trig-
gered
0xFF - RST_TYP_NIL: no restart
type information available
INFO 2: restart trigger source
0 - MMC: restart triggered from
MMC

1 - OMC: restart triggered from

OMC
2 - WDTINST: restart triggered
from Webdiag installer session
3 - WDTDBG: restart triggered
from Webdiag debug session
0xFF: RST_SRC_NIL: no reset
trigger information available
INFO 3: sub-options for cold reset
type
1 - USR: User configuration data is
removed
2 - SYS: System configuration data
is removed
3 - USR_SYS: User and System
configuration data are removed
4 - CC: Cloud connect configura-
tion data is removed
5 - USR_CC: User and Cloud con-
nect data are removed
6 - SYS_CC: System and Cloud
connect data are removed
7 - USR_SYS_CC: User, System
and Cloud connect data are re-
moved
8 - MGNW: Management and Net-
work configuration data are re-
moved
9 - USR_MGNW: User, Manage-
ment and Network configuration
data are removed
10 - SYS_MGNW: System, Man-
agement and Network configura-
tion data are removed
11 - USR_SYS_MGNW: User, Sys-
tem, Management and Network
configuration are removed
12 - CC_MGNW: Cloud connect,
Management and Network configu-
ration data are removed
13 - USR_CC_MGNW: User, Cloud
connect, Management and Net-

work configuration data are re-

moved
14 - SYS_CC_MGNW: System,
Cloud connect, Management and
Network configuration data are re-
moved
15 - USR_SYS_CC_MGNW: User,
System, Cloud connect, Manage-
ment and Network configuration
data are removed
0xFF - RST_SUB_OPT_NIL: No
Sub options. (Applicable for reset
type other than cold reset)
1 DOWNLOAD INFORMATION CPU (80) INFO 0 = information

1 : download started
2 : download finished
3 : download failure
INFO 1 = cause of failure
0 : download complete
9 : invalid date
11 : file transfer error
14 : download incomplete
2 SWAP INFORMATION CPU (80) INFO 0 =1: swap complete; 2: data

saving error; 3: fault during swap
Program change-over
INFO 1 = type of swap: 0 : normal
with data saving; 1: normal without
data saving; 2: forced with data
saving
INFO 2 = acknowledgement: 0 : no
problem; 1: save KO; 2: restore
KO; 3: save/restore KO
3 LAUNCH OF DATA SAVING CPU (80) INFO 0
Data Saving 00 Data Saving backup on Flash

EPROM is started
01 System configuration backup on
external SD Card is started
02 User data backup on external
SD Card is stated

4 DATA SAVING BACKUP OK CPU (80) INFO 0

00 Data Saving backup on Flash
EPROM status is OK
01 System configuration backup on
external SD Card status is OK
02 User data backup on external
SD Card status is OK
6 AUTOMATIC DATA SAVING CPU (80) End the MMC

BACKUP REFUSED session.
Save man-
MMC session was active
ually or wait
for the next
automatic
save.
7 LAUNCH OF DATA RESTORE CPU (80) INFO 0
Data Saving 00 Data restore from Flash

EPROM is started
01 System configuration restore
from external SD Card is started
02 User data restore from external
SD Card is stated
8 DATA RESTORE OK CPU (80) NFO 0 Check if the

hardware
00 Data Saving restore from Flash
configuration
EPROM status is OK
has been
01 System configuration restore changed
from external SD Card status is OK since the last
backup
02 User data restore from external
SD Card status is OK
10 DATA SAVING REFUSED CPU (80)

No data saving option
11 END OF START-UP
The system is operational
20 NOT ENOUGH MEMORY CPU (80)

Available space < 15 %
21 FULL BUFFER MESSAGE CPU (80) INFO 0 = type of pool (see the
FLOW CONTROL ON MEMORY
POOLS event)

22 FLOW CONTROL ON MEMO- Board lo- INFO 0 = type of pool:

RY POOLS cation
1: POOL_REMANENT (LP_CM)
Alert level size of memory allo-
2: POOL_VOLATIL (LP_CM)
cated to flow control on a mem-
ory reached 3: POOL_CSLANG (LP_CM)
4: POOL_DEBUG (LP_CM)
5: POOL_CPAU_PLAY (LP_CM)
6: POOL_CPAU_RECORD
(LP_CM)
7: POOL_RT_SIG (RT_SIG)
INFO 1 = level:
0x5F (95) (alert level is reached)
0x4B (75) (normal level retrieved)
30 DBMS CRASH CPU (80) INFO 0 = High byte of function

causing the suicide
INFO 1 = Low byte of function
causing the suicide
INFO 2 = High byte of cause of the
suicide
INFO 3 = Low byte of cause of the
suicide
31 CURRENCY CONVERSION CPU (80) INFO 0 =1: conversion complete
32 PRIORITY CALL CPU (80) INFO 0 = Directory Number High

Byte INFO 1 =Directory Number
Low Byte
34 SOFTWARE KEY CHANGE CPU (80) INFO 0 = type of key (0= main key;
1 = CTI key)
INFO 1 = type of event (see: Soft-
ware key states (INFO 1 of mes-
sage 34) on page 69)
INFO 2 and 3 = Bytes correspond-
ing to the acknowledgement code
(respectively High and Low)
35 PS-BOOST BOARD FAULT CPU (80) INFO 0 = type of error (1 = more

than one boost present or boost in
A PS-BOOST board problem
a small rack; 2 = no boost nor ex-
has been detected
ternal feeding; 3 = external power
loss; 4 = external power recovery)

36 The status of the server certifi- INFO 0 = Subevent

cate has changed
• 1: Certificate OK
• 2: Incomplete names list
• 3: Expired certificate
• 4: Expired authority
INFO1 = Type of certificate
• 0: Self-signed
• 1: CA-signed
INFO2 = Trigger
• 0: Reset
• 1: Webdiag
• 2: Config
• 3: Daily check
40 R_ANO_EMERGENCY_CON-
FIG
No device has been configured
to receive emergency call notifi-
cation
44 R_ARP_SPOOF_INFO Board lo- INFO 0 to 3 = IP address of the tar-

cation get, eg : C0 A8 5C 16 for
ARP spoofing detected. Multi-
192.168.92.22
ple ARP reply received within
lock-time period.
45 R_MGTSRV_LOCK Board lo-

cation
Access to system management
is locked due to 6 consecutive
authentication failures with in 5
minutes.
46 R_TERM_REBOOT_OR_RE- Board lo- INFO 0 = Reset (01) or Reboot (02)

SET_OF_USER_DATA cation
INFO 1 = --
Reboot of IP terminal or reset
INFO 2 = First byte of EDN
of user data.
INFO 3 = Second byte of EDN
47 R_PUBLIC_DDI_REGISTRA- Board lo-

TION_LIMIT_EXCEED cation
Public DDI Registration limit ex-
ceeded.

48 R_DEFAULT_PASS- Board lo-

WORD_FOUND cation
Default passwords found in
Management/ SIP Phone Ad-
ministrator passwords.
49 R_EASY_PASS- Board lo- INFO 0 indicates for which catego-

WORD_FOUND cation ries some easy or trivial passwords
have been detected by the system.
Easy passwords found in Man-
agement/ User passwords. The INFO 0 value is a bit field val-
ue with one bit for the following cat-
egories:
The installer session (bit 6 [highest
bit])
The operator session (bit 5)
The administrator session (bit 4)
The download session (bit 3)
The NMC session (bit 2)
The subscribers (bit 1 [lowest bit])
56 ISDN BOARD ACCESS Board lo- INFO 0 = access status (0 = ac-

cation. cess KO, 1 = access OK)
The ISDN protocol manage-
ment module detected a layer 1 Access INFO 1 = type of access (03h = T0,
problem on a BRA or PRA ac- marker 16h/17h = DLT0, 23h = T1, 04h =
cess T2, 18h = DLT2, 2Ah = PCM, 2Dh
= T1CAS)
57 TEI DELETION CPU (80) INFO 0 = D-channel Analyze the

reason why
INFO 1 = TEI
the TEI was
modified by
the network
carrier.

59 R_ANO_VOWLAN_ACCESS. INFO 0 = Code of error:

Voice over WLAN access prob- 1 = Rate of calls cut/total calls on
lems. system reached 5%
2 = Saturation time on one AP
reached 1 minute
3 = Saturation number on one AP
reached 3 times
4 = Rate of refused calls/total calls
on system reached 5%
5 = Rate of calls cut/total calls on
one handset reached 5%
6 = Rate of refused calls cut/total
calls on one handset reached 5%
70 PRINTER THRESHOLD K.O. Check the

printer and its
Message emitted by the spool-
cable con-
er when the array where the
nection
tickets are stored is 70% full
71 PRINTER THRESHOLD O.K.

Message emitted by the spool-
er when the array where the
tickets are stored is less than
70% full again
80 R_DHCP_SERVER_EXITED Board lo- INFO 0:

cation
DHCP server exited due to bad 00 = Bad configuration
configuration or option defini-
01 = Option definition error
tion error or IP address not in
subnet or restart failed 02 = IP address not in subnet
03 = Restart failed
81 R_DHCP_SERVER_STATUS Board lo- INFO 0:

cation
DHCP server status changed 00 = DHCP server normal exit
01 = DHCP server started success-
fully

82 R_PASSWORD_AUTHENTI- INFO 0 = Reason for Lock: this val-

CATION_LOCKED ue gives the information from
where the last failed authentication
attempt was made:
• 01 = Local access to VMU
• 02 = Remote access to VMU
• 03 = Local access to WSAPI
• 04 = Remote access to WSAPI
• 05 = Hot Desking Session
Access
INFO 1 = Count of Lock
INFO 2 = first byte of EDN
INFO 3 = second byte of EDN
83 R_PASSWORD_AUTHENTI- INFO 0 = not used

CATION_UNLOCKED
INFO 1 = not used
INFO 2 = first byte of EDN
INFO 3 = second byte of EDN
84 R_SYSTEM_AUTO_PROVI- INFO 0 = Auto provisioning status:

SION
• 0x00: Deactivated (OFF)
• 0x01: Activated (ON)
INFO 1 = Source of Auto provision-
ing configuration trigger:
• 0x01: OMC
• 0x02: MMC
85 R_SD_CARD_STATUS_AND_ INFO 0 = External SD card status:

EXISTENCE
00: SD Card is operational
Availability and Status of the
01: SD Card is not available
External SD Card used for the
configuration Backup/Restore 02: SD Card is write protected
management
03: SD Card is corrupted
04: SD Card storage space is very
low
05: SD Card format successful
06: SD Card format failed
07: SD Card unsupported files sys-
tem

86 R_DTLS_CONNECTION_FAIL INFO 0 = DTLS connection failure

URE reason:
00: Connection failure due to En-
forced DTLS mode
01: Endpoints Authentication failed
due to CA authentication failure
02: Endpoints Authentication failed
due to startnoe-DTLS MAC ad-
dress verification failure
INFO 1 = 4th byte of set’s MAC ad-
dress
dress
dress
90 ENTERING AN MMC SES- CPU (80) INFO 0 =1: ADMINISTRATOR

SION password; 2: INSTALLER pass-
word; 3: OPERATOR password; 5:
GUARDED password
91 END OF MMC SESSION CPU (80)
92 R_LOCAL_MGT_PWD_RE- INFO 0 = update type:

SET 01: The management passwords
have been reset to a random value
02: The management passwords
have been restored to their previ-
ous unknown values after expira-
tion of the limited delay
03: The management passwords
have been updated within the limi-
ted time frame
INFO 1 = time frame duration in mi-
nute (in reset case)
100 BOARD BACK IN SERVICE Board lo- INFO 0 = type of board (see:
cation #unique_9/
(Following a system stoppage
unique_9_Connect_42_s8)
or after being unplugged)
101 BOARD UNPLUGGED Board lo- INFO 0 = type of board (if known)
cation (see: #unique_9/
unique_9_Connect_42_s8)
INFO 1 = cause of rejection

104 TEMPORARY BOARD RESET Board lo- INFO 0 =1: hardware fault; 2: no
cation response from board (board main-
tenance); 3: fan fault; 4: running on
battery; 5: license problem; 6:
maintenance problem; 7: reason
unknown
If INFO 0 = 1: hardware fault
• INFO 1 = root problem high
order byte
• INFO 2 = root problem low
order byte
If INFO 0 = 3: fan fault, 4: running
on battery, 5: license problem, 6:
maintenance problem, or 7: reason
• INFO 1 = cause of reset
• INFO 2 = Shutdown Status
105 PERMANENT BOARD RESET Board lo- INFO 0 =1: hardware fault; 2: no Disconnect
cation. response from board; 3: fan failure; and recon-
4: running on battery; 5: license nect the
problem; 6: maintenance problem; board. If the
7: reason unknown; 8: power sup- fault persists,
ply problem replace the
board
If INFO 0 = 1: hardware fault
• INFO 1 = root problem high
order byte
• INFO 2 = root problem low
order byte
If INFO 0 = 3: fan fault, 4: running
on battery, 5: license problem, 6:
maintenance problem, 7: reason,
or 8: power supply problem
• INFO 1 = cause of reset
• INFO 2 = Shutdown Status

106 BOARD REFUSED Board lo- INFO 0 = type of board Check the
cation hardware
The board has been refused INFO 1 = cause of refusal: (See
configuration
and, in the case of an intelligent #s10)
(the system
board, a permanent reset is
1: REJ_MAX_BRD_POW: Too limits may
performed on it
much power consumed have been
exceeded).
4: REJ_UNKOWN_BOARD_TYPE:
Board unknown by system
5: REJ_BOARD_FORBIDDEN:
Board known, but not allowed at
that location
6: REJ_PRA_IN_MASTER_NEE-
DED: No PRA access in Master
cabinet
7: REJ_NO_LICENSE: Not Accep-
ted according rights given by the
License
8: REJ_TOO_MANY_CPUS: Max
of Applicative boards is reached
9: REJ_BOARD_INIT_FAILED:
Board could not be initialized
13: REJ_TOO_MANY_RAS: Max
of coCPU RAS boards is reached
15:
REJ_NO_MORE_MIXED_BOARD
_LICENSE: Number of trunks on
Mixed board reaches maximum
given by the license
107 MMC BOARD RESET Board lo-

cation
The reset of an interface board
processor has been requested
by MMC
108 POWER OFF: LAUNCH OF Board lo-

BACKUP PROCEDURE FOR cation
A BOARD
109 BOARD INFO CLEARED BY Board lo-

OMC cation

110 APPEARANCE OF A DEVICE Board lo- INFO 0 = type of device (see:

cation. Types of terminal (INFO 0 of mes-
A device has been recognized
sages 110, 111 and 112) on page
by the system. This device is Interface
64)
now operational marker
INFO 1 = reason for restarting
NB: this message will only be
(see: Reasons for device restart
sent if the NMC is present and
(INFO 1 of message 110) on page
active
65)
111 DEVICE REFUSED Board lo- INFO 0 = type of device (see: Check the
cation. Types of terminal (INFO 0 of mes- hardware
Configuration limit attained
sages 110, 111 and 112) on page configuration
Interface
64) (the system
marker
limits may
INFO 1 = cause of refusal (see:
have been
Reasons for terminal refusal (INFO
exceeded).
1 of message 111) on page 67)
INFO 2 = 1: software license prob-
lem (in this case, INFO 1 = 255
(terminal is not totally refused, be-
cause recognized by MMC))
112 FAULT ON A DEVICE Board lo- INFO 0 = type of device (see: If the fault re-
cation. Types of terminal (INFO 0 of mes- curs fre-
sages 110, 111 and 112) on page quently,
Interface
64) check the ter-
marker
minal and its
INFO 1 = type of error (only rele-
connections.
vant for UA sets)
113 INTERFACE REFUSED Board lo- INFO 0 = type of interface (see: Check the
cation. Types of interface (INFO 0 of mes- hardware
An interface was refused be-
sage 113) on page 67) configuration
cause the system limits were Interface
(the system
exceeded marker INFO 1 = cause of refusal (see: Ad-
limits may
ditional information contained in
have been
message 113 (INFO 1: cause of re-
exceeded).
fusal) on page 68)
120 CABINET OPERATIONAL Controller INFO 0 = type of backpanel board

board (81 (3 = wall mounted; 4 = RACK1U; 5
or 82) = RACK2U; 6 = RACK 3U; 7 =
RACK 1U G2; 8 = RACK 2U G2; 9
= RACK 3U G2; 10 = RACK XS; 11
= RACK XS-N)
INFO 1 = module operating mode
(0 = restricted mode, running on
battery; 1 = normal mode, running
on the electrical power supply)

121 CABINET REFUSED Controller INFO 0 = reason for rejection:

board (81
1: REJ_CABINET_FORBIDDEN
or 82)
(Rack XS forbidden as satellite)
2: REJ_MEX_FORBIDDEN
122 CABINET UNPLUGGED Controller

board (81
or 82)
123 MAIN FAILURE CPU (80) INFO 0 = Main power supply state
(0 = Electrical power supply KO -
battery activated; 1 = Electrical
power supply OK; 2 = System on
battery, only with 2G power supply)
124 FAN STATUS CPU (80) INFO 0 = fan identity (0 = fan 1; 1 =

or Control- fan 2)
ler Board
INFO 1 = fan status (True = OK;
(81) or (82)
False = KO)
125 POWER SAVING INFO 0 = module (0 = basic mod- Check rota-

ule; 1 = extension 1; 2 = extension tion of the
System in power-saving mode;
2) module fans.
only the 2 first Reflexes tele-
phones as well as all T0 ac- INFO 1 = reason (0 = Fan problem)
cesses will be taken into ac-
count
126 DSP RESOURCE KO Controller INFO 0 = DSP type 0 or 1 (DSP0

board (81 or DSP1)
Message not processed by the
or 82)
DSP of one of the controller INFO 1 = Resource type
boards
INFO 2 = Opcode of the message
INFO 3 = State of the resource
127 DSP RESULT CODES Controller INFO 0 = DSP type 0 or 1 (DSP0

board (81 or DSP1)
These codes are used in confir-
or 82)
mation messages and by the INFO 1 = Result code
reception buffer
INFO 2 = Result sub-code
INFO 3 = Type of resource
128 DSP KO CPU (80) INFO 0 = 0 or 1 (DSP0 or DSP1)

or control-
The DSP of one of the control-
ler board
ler boards is out of service.
(81 or 82)

129 CPU KO INFO 0 = type of CPU (0 = Internet

access; 1 = VoIP)
PowerCPU EE/PowerCPU EE
C25 board not detected by the INFO 1 = number of CPU resets
backpanel board 10 minutes af- during the-10 minute period
ter initialization
INFO 2 = CPU state
INFO 3 = last byte of MAC (Ether-
net) Internet address of CPU
140 UNREGISTRATION CPU (80) INFO 0 = octet 1 of the IP address

of the remote registry
SIP un-registration
INFO 1 = octet 2 of the IP address
141 REGISTER OK CPU (80) INFO 0 = octet 1 of the IP address

SIP registration success
142 REGISTER 500 CPU (80) INFO 0 = octet 1 of the IP address

SIP registration failure (500:
Server error) INFO 1 = octet 2 of the IP address

SIP registration failure (423: In-
terval too brief) INFO 1 = octet 2 of the IP address


SIP registration failure (400: In-
valid request) INFO 1 = octet 2 of the IP address

Forbidden) INFO 1 = octet 2 of the IP address

Not found) INFO 1 = octet 2 of the IP address
147 REGISTER TIMEOUT CPU (80) INFO 0 = octet 1 of the IP address

SIP registration failure (Time-
out) INFO 1 = octet 2 of the IP address
148 REGISTER FAILED CPU (80) INFO 0 = octet 1 of the IP address

SIP registration failure

149 SIP Registration rejected CPU (80) INFO 0 = reason for the rejection
• 0: Undefined error
• 1: Unknown user
• 2: No request or Registrar call
• 3: Bad login or username
• 4: Bad password
• 5: Bad domain name
• 6: Error processing of register
request
• 7: Only one contact allowed.
• 8: Database full
• 9: Too many contacts for one
single address
10: Wrong terminal type for IP-
DECT handset
INFO 1 = First byte of edn
INFO 2 = Second byte of edn.
INFO 3 = Count of occurrence of
the event with same reason of re-
ject
150 R_ ANO_QUARAN- CPU (80) An IP address has been placed in

TINE_ALERT quarantine.
The IP address placed in quaran-
tine can be one of a SIP Phone or
of a Gateway SIP Trunk.
The four bytes of the IP address
are given in comp_info[0],
comp_info[1], comp_info[2] and
comp_info[3].
160 THRESHOLD HARDWARE TA- CPU (80)

BLE
The critical threshold (80 % by
default) of the hardware fault
table has been reached
161 THRESHOLD HISTORY TA- CPU (80)

BLE
default) of the history fault table
has been reached

162 THRESHOLD METERING TA- CPU (80)

BLE
default) of the data metering
buffer has been reached
163 THRESHOLD URGENT TABLE CPU (80)

default) of the urgent alarms ta-
ble has been reached
164 HARDWARE TABLE FULL CPU (80)

The hardware anomaly table is
full
165 HISTORY TABLE FULL CPU (80)

The history event table is full
166 METERING TABLE FULL CPU (80) INFO 0 = Origin (1 byte); 0 = Ac-
count ticket table; 1 = VoIP RTP
The metering table is full
ticket table
167 URGENT TABLE FULL CPU (80)

The urgent alarms table is full
168 NMC CONNECTION START CPU (80)

The NMC application has es-
tablished a connection with the
PCX
169 NMC CONNECTION END CPU (80)

The NMC application has
ended the connection with the
PCX
171 NMC ERRONEOUS CALL CPU (80)

The PCX tried to establish a
call to an NMC but it was erro-
neous
172 NMC NON ANSWERED CALL CPU (80)

The PCX tried to establish a
call to an NMC, but the call was
not answered

173 NMC INFO TIMEOUT CPU (80)

The PCX connected to an NMC
and sent an INFO message
saying that an urgent alarm
should be read. The PCX did
not respond to this message.
174 NMC PUT DATA TIMEOUT CPU (80)

The PCX received no acknowl-
edgement for the data sent in
the message. The communica-
tion failed.
175 NMC WAIT ACK TIMEOUT CPU (80)

The PCX received no acknowl-
edgement for the establishment
request sent to the NMC
176 NMC PHONE NB MISSING CPU (80)

The PCX attempted to call the
NMC to send urgent alarms,
but the NMC number was not
specified
177 ADDRESS NOT REGISTERED CPU (80)

The PCX attempted to call the
NMC, but the NMC refused the
call because it didn't recognize
the PCX
178 UNEXPECTED ALARM CPU (80) INFO 0 = cmvision reference
Unsuccessful anomaly transla- INFO 1 = cmvision reference

tion for the NMC

180 R_ANO_CC_STATUS MAIN_CP INFO 0 = Cloud Connect event

U_SLOT type:
The status of the Cloud Con-
nect has changed with suc- 0x00: No type
cess.
0x01: Cloud Connect connection
It could be a Cloud Connect success
connection, a Cloud Connect
0x02: Cloud Connection discon-
disconnection, or a FTR
nection success
change.
0x03: FTR done
INFO 1 = Cause:
0x00: No cause
0x01: First OXO startup
0x02: OXO startup
0x03: Cloud Connect agent startup
0x04: FTR done
0x05: Cloud Connect disabled
0x06: Cloud Connect enabled
0x07: Network troubles: Cloud
Connect reconnection after a dis-
connection due to network troubles
0x08: CC ping timeout: Cloud Con-
nect reconnection after a discon-
nection due to a ping timeout
INFO 2 = Cloud Connect account
type:
0x00: No type
0x01: activation account
0x02: final account
INFO 3 = Counter of occurrence by
type defined by the triplet of 3 first
bytes contained in comp_info

181 CLOUD CONNECT FAILURE MAIN CPU INFO 0 = Cloud Connect event
type:
Event generated after a con-
nection failure with the Rain- • 0x00: No type
bow Cloud infrastructure, or a • 0x0A: Cloud Connect
problem with the Cloud Con- connection failed
nect Control Agent (CCCtrlA) • 0x0B: Internal Cloud Connect
embedded on OXO Connect agent error
Evolution, or a Rainbow service • 0x0C: Cloud Connect
which is no more reachable connection lost
• 0x0D: Bad credential (THIS
CASE IS URGENT BY
DEFAULT)
• 0x0E: Service unreachable
• 0x0F: Final account getting
• 0x10: Final account
acknowledgement
• 0x11: Inconsistent received data
• 0x12: Event node error
• 0x13: Get File error
• 0x14: License error
• 0x15: Software download error
INFO 1 = Cause:
• 0x00: No cause
• 0x09: Stream version error
• 0x0A: Stream Close
• 0x0B: Proxy authentication
required
• 0x0C: Proxy authentication
failed
• 0x0D: Proxy no supported
authentication
• 0x0E: Connection refused
• 0x0F: DNS error
• 0x10: No supported
authentication
• 0x11: TLS failed
• 0x12: TLS not available
• 0x13: Connection compression
failed
• 0x14: Input/Output error
• 0x15: Parse error
• 0x16: Out of memory
• 0x17: Authentication failed
• 0x18: Service unreachable
• 0x19: Service non responding
• 0x1A: Invalid input

• 0x1B: Inconsistent product state

• 0x1C: Service internal failure
• 0x1D: Bad version
• 0x1E: Bad format
• 0x1F: OXO Connect Evolution
not subscribed to the Pubsub
node
• 0X20: No persistent item on the
Pubsub node
• 0x21: Item retrieval not
supported on the Pubsub node
• 0X22: OXO Connect Evolution
is not in the Pubsub node white
list
• 0X23: OXO Connect Evolution
has a bad affiliation for the
Pubsub node
• 0x24: Pubsub node does not
exist
• 0x25: Bad Credential
• 0x26: File not found
• 0x27: File not changed
• 0x28: Error during Transfer
• 0x29: ftr waiting for eBuy
• 0x2A: ftr no longer authorized
• 0x2B: fleet and install ref
already used
• 0x2C: ftr security check error
• 0x2D: generic error elp
• 0x2E: Bad checksum
• 0x2F: Software version
mismatch
• 0x30: Fleet and install ref must
be provided
• 0x31: A session is required
• 0x32: A session is already
existing
• 0x33: Session timeout
INFO 2 = Cloud Connect account
type or Cloud Connect service:
• 0x00: No type
• 0x01: activation account
• 0x02: final account
• 0x03: FTR Service
• 0x04: SA Service
• 0x05: Inventory file

• 0x06: Actis file

• 0x07: Events file
• 0x08: Counters file
• 0x09: Usage file
• 0x0A: License service
• 0x0B: Download service
INFO 3 = Counter of occurrence
by type defined by the triplet of 3
first bytes contained in comp_in-
fo
182 R_CC_VPN_STATUS MAIN_CP INFO 0 = Cloud Connect VPN

U_SLOT event type:
0x01: VPN start
0x02: VPN stop
0x03: VPN stop all
INFO 1 = Cause:
0x00: Undefined
0x01: User request
0x02: Cloud Connect disabled
0x03: Cloud Connect agent stop
0x04: Cloud Connect agent start
0x05: Connection supervision
INFO 2 = VPN connection identifier
INFO 3 = VPN tunnel identifier

183 R_CC_VPN_FAILURE MAIN_CP INFO 0 = Cloud Connect VPN

U_SLOT event type:
0x01: VPN start
0x02: VPN stop
0x03: VPN stop all
INFO 1 = Cause:
0x00: Undefined
0x08: Wrong parameter
0x09: Maximum number of VPN
connection reached
0x0A: Maximum number of VPN
tunnel reached
0x0B: Internal error
0x0C: Error during phase 1 of VPN
establishment
0x0D: Error during phase 2 of VPN
establishment
INFO 2 = Additional parameter
0x00: Undefined
0x01: Query header
0x02: Query version
0x03: Requester
0x04: Organization
0x05 User
0x06: Gateway
0x07 Login
0x08: Password
0x09: PSK
0x0A: Connection Identifier
0x0B: IKE authentication method
0x0C: IKE port
0x0D: NAT port
0x0E: Certificate of the certificate
authority
0X0F: Certificate subject
0x10: Peer identifier
0x11: Phase 1 encryption

0x12: Phase 1 hash

0x13: Phase 1 Diffie Hellman
Group (DH group)
0x14: Phase 2 encryption
0x15: Phase 2 authentication
0x16: Phase 2 Perfect Forward Se-
crecy Group (PFS group)
0x17: Phase 2 inactivity timer
INFO 3 = VPN tunnel identifier
184 R_ANO_RB_STATUS MAIN_CP INFO 0 = Event type:

U_SLOT
The status of the Rainbow 0x00 No type
agent has changed with suc-
0x01 Connection success
cess.
0x02 Disconnection success
It could be a connection or a
disconnection. INFO 1 = Cause:
0x00 No cause
0x01 First OXO startup
0x02 OXO startup
0x03 Agent startup
0x04 Agent disabled
0x05 Agent enabled
0x06 Network troubles: reconnec-
tion after a disconnection due to
network troubles
0x07 Ping timeout: reconnection af-
ter a disconnection due to a ping
timeout
0x08 Agent stop
INFO 2 = Account type:
0x00 No type
0x01 Activation account
0x02 Final account
INFO 3 = Counter of occurrence by

185 R_ANO_RB_FAILURE MAIN_CP INFO = Event type:

U_SLOT
A failure occurs in the Rainbow 0x00 No type
features.
0x01 Connection failed
It could be a failure during the
Rainbow agent connection, a 0x02 Internal agent error
failure in the Rainbow agent on 0x03 Connection lost
OXO, or a failure in a Rainbow
service. 0x04 Bad credential (THIS CASE
IS URGENT BY DEFAULT)
0x05 Service unreachable
0x06 Final account getting
0x07 Final account acknowledge-
ment
0x08 Inconsistent received data
0x09 Event node error
INFO = Cause:
0x00 No cause
0x01 Stream version error
0x02 Stream Close
0x03 Proxy authentication required
0x04 Proxy authentication failed
0x05 Proxy no supported authenti-
cation
0x06 Connection refused
0x07 DNS error
0x08 No supported authentication
0x09 TLS failed
0x0A TLS not available
0x0B Connection compression
failed
0x0C Input/Output error
0x0D Parse error
0x0E Out of memory
0x0F Authentication failed
0x10 Service unreachable
0x11 Service non responding
0x12 Invalid input
0x13 Inconsistent product state

0x14 Service internal failure

0x15 Bad version
0x16 Bad format
INFO = Account type:
0x00 No type
0x01 Activation account
0x02 Final account
INFO = Counter of occurrence by
190 UNKNOWN IPUI CPU (80) INFO 0, INFO 1, INFO 2, INFO 3 =

corresponding byte of port identifier
A GAP handset tried to access
the PBK without being regis-
tered
191 R_DECT_SYNC_STATUS DECT site INFO 0 = Event type:

identifier
8378 DECT IP-xBS synchroni- 0x00: No type
zation status in a DECT site
0x01: Impossible to build the syn-
chronization tree in manual mode
(THIS CASE IS URGENT BY DE-
FAULT)
0x02: Master of the synchroniza-
tion tree in manual mode is back.
The synchronization tree is back to
normal
0x03: Synchronization mode is au-
tomatic
0x04: Synchronization mode is
manual
0x05: Change in the number of is-
lands in the synchronization tree
1 = Number of islands (relevant
when event type is 0x05)
221 ETHERNET DOWN Board lo- Check the

cation. LAN connec-
Ethernet interface of the IP-
tion and, if
LAN board is down. Ethernet
necessary,
interface
the LAN ele-
marker.
ments (hub,
switch).

222 ETHERNET UP Board lo-

cation.
Ethernet interface of the IP-
LAN board is working. Ethernet
interface
marker.
223 REMOTE GATEWAY DOWN INFO 0 to INFO 3: bytes corre- Check the IP
sponding to the IP address Net- connectivity
Remote gateway is out of serv-
work format to the remote
ice.
gateway
(LAN, inter-
mediate IP
router) and
the remote
gateway sta-
tus.
224 REMOTE GATEWAY UP INFO 0 to INFO 3: bytes corre-

sponding to the IP address Net-
Remote gateway is working
work format
225 GATEWAY TRAFFIC CPU (80) INFO 0 to INFO 3: bytes corre- If this alarm
sponding to the IP address Net- keeps recur-
Too much traffic to the remote
work format ring, increase
gateway xxxxx
the band-
width associ-
ated with the
gateway in
the ARS ta-
ble, and the
number of
DSPs as-
signed to
VoIP access.
226 EXTERNAL GATEKEEPER IN- Check the IP

ACCESSIBLE connectivity
to the remote
gatekeeper
(LAN, inter-
mediate IP
router) and
check that
the remote
gatekeeper is
online.

227 NOT ENOUGH IP TRUNK CPU (80) If this alarm

keeps recur-
VoIP call refused: no DSP
ring, increase
channel available
the number
of DSPs as-
signed to
VoIP access,
or increase
the band-
width in the
ARS, or add
hardware re-
sources.
228 NOT ENOUGH DSP CPU (80) INFO 0 = Type of DSP allocation If this alarm
failure keeps recur-
VoIP telephony failure: no DSP
ring, increase
channel available.
the number
of DSPs as-
signed to the
IP user pool
(decrease the
number of
VoIP-access
DSPs or add
hardware re-
sources).
229 NO MORE TSC IP DYN AD- Increase the

DRESS number of IP
addresses in
TSC/IP phone cannot be initial-
the DHCP
ized due to a DHCP problem
server range
(this address
range must
be greater
than or equal
to the num-
ber of IP En-
ablers to be
installed).
230 EXTERNAL GATEKEEPER

REJECTED

231 R_IA_EMAIL CPU (80) INFO 0 = Type of alert:

Anomaly sent when the call 01: Connection with ISP server
handling receives a log from IA failed
concerning e-mail feature
02: ETRN error
Report of anomaly depends
03: Incorrect password for a POP3
on the value attached to the
account
noteworthy address, named
«StoreAlertIA». This anomaly 04: The ETRN SMTP isn’t suppor-
is not stored in the historic ted by the remote e-mail server
table, just transmitted to
05: A user tried to connect to e-
NMC
mail server with an incorrect pass-
word
INFO 1 = Log unique identifier High
Byte
INFO 2 = Log unique identifier Low
Byte
232 R_IA_SECURITY CPU (80) INFO 0 = Type of alert:

Anomaly sent when the call 01: The firewall has dropped a
handling receives a log from IA packet
concerning security feature.
02: The firewall has dropped a
Report of anomaly depends packet with ports information
03: The firewall has dropped a
packet with protocol type informa-
«StoreAlertIA». This anomaly
tion
is not stored in the historic
table, just transmitted to 04: The firewall has accepted a
NMC packet
05: The firewall has accepted a
packet with ports information
06: The firewall has accepted a
packet with protocol type informa-
tion
Byte
Byte

233 R_IA_NETWORK CPU (80) INFO 0 = Type of alert:

Anomaly sent when the call 01: DHCP found to have failed: no
handling receives a log from IA free address on network
concerning network feature.
02: DHCP rejected: no free ad-
Report of anomaly depends dress
03: DHCP offer failed: dynamic ad-
dress range contains static ad-
dresses
table, just transmitted to 04: DHCP server failed to start
NMC
05: Unable to update routing table
06: DynDns: IP update failed
07: DynDns: successful IP update
Byte
Byte

234 R_IA_ACCESS CPU (80) INFO 0 = Type of alert:

Anomaly sent when the call 01: Incorrect usage of the ISDN
handling receives a log from IA script
concerning access feature.
02: PAP authentication failed
03: No response to PAP authenti-
cation requests
«StoreAlertIA». This anomaly 04: CHAP authentication failed
05: Watchdog detected too many
table, just transmitted to
errors. Access disabled
NMC
06: Access file(s) not correctly cre-
ated
07: No ethernet device for access
08: Unknown IA connection
09: ISP defined without connection
type
10: Configuration change: use of a
new ISP
11: ISP not activated because of
time ranges
12: Unknown option
13: Internet access is not activated
14: Internet access is dialing
15: Connection established with
ISP
16: Connection to the ISP termina-
ted
17: CHAP MD5 authentication suc-
cessful
18: Auto DNS search using MS
DNS protocol
Byte
Byte

235 R_IA_REMOTE_ACCESS CPU (80) INFO 0 = Type of alert:

Anomaly sent when the call 01 VPN: MSCHAP-v2 peer authen-
handling receives a log from IA tication failed for a remote host
concerning remote access fea-
02 RAS: PAP authentication failed
ture.
03 RAS: CHAP authentication
failed
noteworthy address, named 04 RAS: No IP address affected
05 VPN: PPP terminated
table, just transmitted to 06 VPN: PPTP Client control con-
NMC nection started
07 VPN: PPTP Client control con-
nection stopped
08 RAS: callback connection es-
tablished
09 RAS: 64kbps connection estab-
lished
10 RAS: 128kbps connection es-
tablished
11 RAS: Connection terminated
12 RAS: Second line hung up
13 VPN: PPP interface startedSec-
ond line hung up
14 VPN: MSCHAP-v2 peer authen-
tication successful for a user
Byte
Byte

236 R_IA_DATA_CONFIG CPU (80) INFO 0 = Type of alert:

Anomaly sent when the call 01: Configuration file is corrupted.
handling receives a log from IA Back configuration file restored
concerning configuration data
02: Back configuration file is cor-
feature.
rupted. Original configuration file
Report of anomaly depends restored.
03: Original configuration file is cor-
rupted!
is not stored in the historic 04: Too many startips failed ! Origi-
table, just transmitted to nal configuration file restored
NMC
05: One or several user files are
corrupted! These users have been
removed
06: One or several URL filter files
are missing! These files have been
removed in configuration files
07: Error creating user (user al-
ready exists)
08: Error modifying user (user al-
ready exists)
09: The critical threshold of the tel-
ephonic alert table is reached (80%
full)
10 The telephonic alert table is full.
Byte
Byte
240 NO VOICE MESSAGE AVAILA- CPU (80) INFO 0 = number of megabytes of

BLE DRAM detected by the BIOS.
Anomaly sent at the init if the
BIOS does not detect the whole
RAM.
241 VMU MEMORY THRESHOLD CPU (80) INFO 0 = 1 (ON) if there are just a
few minutes of recording time left;
The voice message recording
0 (OFF) end of the anomaly.
memory area is nearly full.
250 STARTUP SCRIPT CPU (80) INFO 0 = Error line / 256

Anomaly sent when an error in INFO 1 = Error line mod. 256
the Linux startup script occurs.
INFO 2 = Critical error
INFO 3 = Status

251 R_NOE_DLD_SUCCESS CPU (80) INFO 0 = Device type

Alcatel-Lucent 9 series down- INFO 1 = Files downloaded: one bit
loading successful. for each kind of file:
Bit 0 = 0x01: Patch file
Bit 1 = 0x02: Code file
Bit 2 = 0x04: Data file
Bit 3 = 0x08: Localization file
Bit 4 = 0x10: Customization file

252 R_ANO_NOE_DLD_FAIL Board lo- INFO 0 = Device type

cation.
Alcatel-Lucent 9 series down- INFO 1 = Phase of failure:
loading unsuccessful. Interface
16: Phase: downloading request
marker
refused
32: Phase: a lot of errors
48: Phase: checksum test
64: Phase: system timer failed
INFO 2 = Reason of failure:
16: Cause: download request re-
fused: Hardware problem
fused: Internal downloader missed
fused: Internal software locked
fused: wrong parameter into down-
load request (available since IP
Touch R2.0)
fused: Incompatible software (avail-
able since IP Touch software R2.0)
32: Cause: during downloading:
Packet number error
33: Cause: during downloading: In-
valid header
Decompress error
35: Cause: during downloading: Bi-
nary header error
Test error
Cannot accept more data
38: Cause: during downloading: No
download running
Too many bytes received
unknown error
40: Cause: Error during checksum
check: error detected 1


check: error detected 2
check: bytes missing
64: Cause: Error because of sys-
tem timer expired: Acknowledge
timer failed
tem timer expired: Checksum timer
failed
tem timer expired: Downloading
end timer failed
tem timer expired: Packet control
timer failed
INFO 3 = Files downloaded failure
253 R_SWL_SOON_EXPIRED CPU(80) contact the

installer to
Indicates that the Software Li-
get a new li-
cence expires in 30 days
cence
255 R_BUSY_TRUNK_CALL_FAIL INFO 0 to INFO 3: displays the

ED trunk group information. Exception:
comp info: FF FF FF FF No trunk
An outgoing call could not be
group no. is available (Error in con-
set up because the trunk group
figuration).
was overloaded.
5.4 Information displayed

The information given below concerns the hardware messages as well as those contained in the
system history.
5.4.1 Types of terminal (INFO 0 of messages 110, 111 and 112)

Types of terminal Value of INFO 0 in
message 111 and 112
Alcatel-Lucent OmniTouch 8118/8128 WLAN Handsets 2BH
8028 Premium DeskPhone 2CH
8038 Premium DeskPhone 2DH
8068 Premium DeskPhone 2EH

Types of terminal Value of INFO 0 in

message 111 and 112
4081/4090 L 40-key add-on module 30H
4081/4090 M 20-key add-on module 32H
10-key add-on module for IP Premium DeskPhones/Digital Premium Desk- 34H

Phones
40-key add-on module for IP Premium DeskPhones/Digital Premium Desk- 35H

Phones
GAP DECT handset without display 40H
GAP DECT handset with 16 character-display 41H
Third-party DECT GAP handset without display 42H
Third-party DECT GAP handset with 16 character-display 43H
GAP DECT handset with 2x16 character-display 4AH
GAP: 8232 DECT 4BH
CSTA virtual set 4DH
Basic SIP phone 4EH
4135 IP Conference Phone 4FH
Open SIP phone 54H
IP-DECT: 8232 DECT 57H
IP-DECT GAP 58H
5.4.2 Reasons for device restart (INFO 1 of message 110)

Restart reason Meaning NOE xBS
0: UNKNOWN_RESET_CAUSE Unknown cause x x
1: HARDWARE_RESET If the user plugs/unplugs the cable x
2: VERSWITCH_RESET Switch version on user request x x
3: INIT_BAD_CONFIGURATION Bad IP configuration x x
4: INIT_LANPBX_FAILED Download lanpbx.cfg file failed x x
5: INIT_DOWNLOAD_SUCCESS Software upgrade success x x
6: INIT_STARTFILE_FAILED Download startfile failed x x
7: WBM_ENGINEER_REBOOT Reset by user logged using telnet x x


8: SHELL_USER_REQUEST Download request by user logged using x
telnet
9: UA3G_RESET_MESSAGE UA3G reset received x
10: TSC reset received x
UA3G_TSC_RESET_MESSAGE
11: NOEP_RESET_MESSAGE NOE reset message received without bin x x
download
12: NOE reset message received with bin x x
NOEP_DOWNLOAD_REQUEST download
13: UAUDP_LOST_CONNECT UA/UDP connection lost x x
14: UAUDP_RELEASE_MESSAGE UA/UDP release received x x
15: DHCP_LEASE_EXPIRATION DHCP lease date expired x x
16: DHCP offer received x x
DHCPC_NO_OFFER_RECEIVED
17: UAUDP_NO_CONNECT_ACK No Connect Ack has been received x x
18: MGR_TOOMUCH_RESTART No connect received after many startnoeip x x
download
22: AFTER_REDIRECT Reset after command redirect has been x x
received
23: Received a different IP address from the x x
DHCPC_DIFF_ADDR_RECEIVED DHCP server
24: INIT_PSK_CUSTOM_MODE Exit from the PSK customization mode x
25: The terminal was running in a bad security x x
BAD_SEC_MODE_RESET_MSG mode, typically, was not secured while it
should have been
26: DOT1X_FAILURE Dot1x Authentication failed x x
27: End of bootloader without any download x
END_BOOT_WITHOUT_DOWNLO
AD
28: EXIT_MMI_SOFT_RESET Exit of local MMI with soft reset x
29: EXIT_MMI_HARD_RESET Exit of local MMI with hard reset x
30: BOOT_CODE_UPDATE Boot code update x
31: RESET_HARD_COMMAND Reset hard command (user request) (xBS: x x
short press on reset button)
32: SOFT_FATAL_ERROR Software fatal error x x
33: ETH_LINK_UNPLUGGED Ethernet link unplugged x
34: NOE_SIP_SURVI NOE to SIP-SURVIVABILITY x
35: NOE_SIP_STANDALONE NOE to SIP-STANDALONE x
36: SIP_SURVI_NOE SIP-SURVIVABILITY to NOE x
37: SIP_STANDALONE_NOE SIP-STANDALONE to NOE x
38: SIP_MODE INTO NOE_APPLICATION x
SIP_MODE_NOE_APPLICATION


39: NEW_VLAN_UPDATE_LLDP New VLAN update in LLDP x x
50: DSP_STALLED The DSP is stalled x
51: An administrator logged to WBM (engineer) x
WBM_ENGINEER_FACTORY_RE has pushed the Factory reset button
SET
53: RESET_BUTTON_MEDIUM An administrator has push the reset button x
for a medium duration
53: RESET_BUTTON_LONG An administrator has push the reset button x
for a long duration
5.4.3 Reasons for terminal refusal (INFO 1 of message 111)

Rejection reason Meaning
4: Maximum of wired interfaces per system reached
REJ_MAX_WIRED_ITF_PER_SYSTEM
5: REJ_MAX_DEV_POW
7: REJ_MAX_DEV
8: REJ_MAX_SUBSCRIBERS Maximum of subscribers reached
9: REJ_MAX_TRK_B_CH Maximum of external b channels reached
13: REJ_COMPATIBLE_DEV Incompatible device for the product
14: REJ_RES_FOR_KEY Maximum of keys reached
15: REJ_MEM_FULL
17: REJ_NON_PERMITTED_DEV Non permitted devices for the product
22: REJ_MAX_S_ISDN_SUBS
23: REJ_MAX_S_ISDN_T2
25: REJ_MAX_IBS Maximum of IBS reached for a reached
26: Maximum of wired main devices reached
REJ_MAX_WIRED_MAIN_DEV_PER_S
27: REJ_NIL_DYN_PROT Default allocated protocol is not NIL_PROT
28: REJ_MAX_POWER_BUDGET Maximum of power budget reached for a cabinet
31: REJ_LICENSE EXCEEDED Maximum of B channels reached
32: REJ_LIN_INIT_FAILED LIN init failed
33: REJ_B_CH_INIT_FAILE B channel init failed
36: Maximum of resource reached (when limitation)
REJ_MAX_RESSOURCE_REACHED
37: Protocol mismatch
REJ_PROTOCOL_NOT_SUPPORTED
5.4.4 Types of interface (INFO 0 of message 113)

1Dh : "integrated voice mail" interface

20H : master DECT base interface

21H : slave DECT base interface
22H : DECT Reflexes interface
26H : IP interface
27h : IP network interface
28h : TSC IP set
2Ah : PCM digital network interface
2Fh, 30h, 31h, 32h : MSG1 to MSG4 interfaces
34h : Audio In interface
35h : Audio Out interface
36h : General bell interface
3Ah to 3Dh : MSG5 to MSG8 interfaces
3Fh : integrated ECMA modem interface
45h to 50h : MSG9 to MSG20 interfaces
5.4.5 Additional information contained in message 113 (INFO 1: cause of refusal)

Reject reasons for interfaces Meaning
4: REJ_MAX_WIRED_ITF_PER_SYSTEM Maximum of wired interfaces per system reached
5: REJ_MAX_DEV_POW
6: REJ_MAX_DEV_ON_ITF Only 2 AOM on UA and only 4 subdevices on UA
7: REJ_MAX_DEV
8: REJ_MAX_SUBSCRIBERS Maximum of subscribers reached
9: REJ_MAX_TRK_B_CH Maximum of external b channels reached
10: REJ_MAX_T0 Maximum of T0 interfaces reached
11: REJ_MAX_PRA Maximum of PRA interfaces reached
12: REJ_MAX_MUA Maximum of Multi UA reached
13: REJ_COMPATIBLE_DEV Incompatible device for the product
14: REJ_RES_FOR_KEY Maximum of keys reached
15: REJ_MEM_FULL
16: REJ_MAX_S0
17: REJ_NON_PERMITTED_DEV non permitted devices for the product

Reject reasons for interfaces Meaning
18: REJ_MAX_DLT0 Maximum of DLT0 reached
19: REJ_MAX_DLT2 maximum of DLT2 reached
22: REJ_MAX_S_ISDN_SUBS
23: REJ_MAX_S_ISDN_T2
25: REJ_MAX_IBS Maximum of IBS reached for a reached
26: REJ_MAX_WIRED_MAIN_DEV_PER_S Maximum of wired main devices reached
27: REJ_NIL_DYN_PROT Default allocated protocol is not NIL_PROT
28: REJ_MAX_POWER_BUDGET Maximum of power budget reached for a cabinet
29: REJ_MAX_HSL_LINK_TS Maximum of hsl resources reached for a cabinet
30: REJ_MAX_HDLC_RESOURCE Maximum of hdlc resource reached for the sys-

tem
31: REJ_LICENSE EXCEEDED Maximum of B channels reached
32: REJ_LIN_INIT_FAILED LIN init failed
33: REJ_B_CH_INIT_FAILED B channel init failed
36: REJ_MAX_RESSOURCE_REACHED Maximum of ressource reached (when limitation)
37: REJ_PROTOCOL_NOT_SUPPORTED Protocol mismatch
5.4.6 Software key states (INFO 1 of message 34)

01 : system boot; the current key does not correspond to the system (wrong serial number): the
services are open for a limited time.
02 : system booted with a valid key.
03 : system booted with a key problem. The services are closed.
04 : system boot; the current key version does not correspond to the system software version: the
05 : system boot; the current key version does not correspond to the system software version; the end
of the limited period causes the services to close.
06 : system boot; the current key is too old; the services are open for a limited time.
07 : system boot; the current key is too old; the end of limited time causes the services to close.
12 : valid key entered.
13 : the current key does not correspond to the system (invalid serial number); end of limited time
causes the services to close.

14 : serial number problem with the system key; a new key with a valid serial number but with a version
which does not correspond to system software version has been entered: the services are open for a
limited time.
16 : serial number problem with the system key; a new key with a correct serial number but too old has
been entered: the services are open for a limited time.
21 : the key entered does not correspond to the system: the services are open for a limited time.
24 : the software key entered does not correspond to system software version (invalid serial number):
the services are open for a limited time.
26 : a software key with too old an edition has been entered: the services are open for a limited time.
32 : the services were closed; entering a valid key causes the services to open.
35 : the services were closed; the new key entered has a valid serial number but a version which does
not correspond to the system: the services remain closed.
37 : the services were closed; the new key entered has a valid serial number but too old: the services
remain closed.
41 : the key version does not correspond to the system; the new key entered does not correspond to
the system (invalid serial number): the services are open for a limited time.
42 : the key version does not correspond to the system; a valid key was entered: the services are
open.
45 : the key version does not correspond to the system; the end of the limited time causes the services
to close.
46 : the key version does not correspond to the system; a new key with a valid serial number but too
old an edition has been entered: the services are open for a limited time.
52 : the services were closed; a valid key was entered: the services are open.
53 : the services were closed; the key entered does not correspond to the system: the services remain
closed.
57 : the services were closed; the key entered has a valid version but does not correspond to the
system (invalid serial number): the services remain closed.
61 : the system's edition is too old; the new key entered does not correspond to the system: the
62 : the system's edition is too old; a valid key was entered: the services are open.
64 : the edition of the system's key is too old; a new key with a valid edition, but an old version, was
entered: the services are open for a limited time.
67 : the system’s key is too old; the end of limited time causes the services to close.
72 : the system’s key is too old; the services were closed; the new key entered is valid: the services are
open.
73 : the system's edition is too old; the services were closed; the new key entered has a problem with
the serial number: the services remain closed.
75 : the system's key is too old; the services were closed; the new key entered has a valid serial
number, but a version which does not correspond to the system: the services remain closed.
5.5 Management of two-color led on attendant station

The two-color LED on the attendant station flashes quickly (orange) in the following cases:

• either of the 2 following T2 alarms (message 53):

• MS: Missing Signal
• RFA: Remote Frame Alarm
• the call detail record storage buffer is 70% full (default value) (message 70)
• counting printer fault (message 72); this alarm is only transmitted if the "PrintFault" flag is other than
0
• problem regaining ISDN access (message 50)
• the hardware message table is 80% full (message 160); this alarm is only transmitted if the
"OperAlarm" flag is other than 0
• erroneous NMC call (message 171)
• unanswered NMC call (message 172)
• NMC communication failure (messages 173, 174 or 175)
• NMC: alarm report failure (message 176)
• NMC: PCX not registered (message 177)
• NAND Flash memory (CPU ) or hard disk not detected (message 239)
5.6 Urgent alarms

OXO Connect Evolution will generate a call to the network management center (NMC) if any of the
following alarms is detected:
• the system reboots (message 0)
• the system is operational after start-up (message 11)
• either of the 2 following T2 alarms (message 53):
• MS: Missing Signal
• RFA: Remote Frame Alarm
• the ISDN protocol management module detected a level 1-fault on an ISDN access (message 56)
• the call detail record storage buffer is 70% full (default value) (message 70)
• counting printer fault (message 72); this alarm is only transmitted if the "PrintFault" flag is other than
0
• the module is back in service (message 120)
• the module is disconnected (message 122)
• there is a problem with the fan (message 124)
• the hardware message table is 80% full (message 160); this alarm is only transmitted if the
"OperAlarm" flag is other than 0
• NMC: history event table 80% full (message 161)
• NMC: call detail record table 80% full (message 162)
• NMC: call detail record table full (message 166)
• the Ethernet interface of the IP-LAN board xxxx is out of service (message 221)
• the Ethernet interface of the IP-LAN board xxxx is in service (message 222)
• the duration of the VMU messages is reaching maximal duration (message 241)
• an error occurred at the opening of the voice prompt file (message 242)
• an error occurred at the reading of the voice prompt file (message 244)
• an error occurred at the writing of the voice prompt file (message 245)
• the downloading of Digital Premium DeskPhones has failed (message 252)

Chapter
6 PBX start and stop
6.1 Overview
The PBX power button allows to either start, restart or stop the PBX. A power LED is associated to the
power button giving information on PBX status and activity.
Power button actions differ according to the initial state of the PBX. The PBX can be in any of the
following states:
PBX state Meaning

Off The PBX is not powered by PoE (no cable plugged)
On The PBX is powered by PoE and started (telephony application is running)
LoLa boot The PBX is powered by PoE and boots in LoLA mode (for software installation)
Standby The PBX is powered by PoE and not started (telephony application is stopped)
Note:
When the PBX is stopped without using any standard stop process (for example: the PoE cable is unplugged), and
restarted after approximatively two minutes, the watchdog defense mechanism is launched after some time, and
the PBX restarts a second time.
6.2 PBX start process

The PBX can start from Off or Standby state to On or LoLa boot state.
6.2.1 Starting a PBX in On state

The PBX start process differs according to its initial state:
• If the PBX is in Off state (power LED is off), connect the PBX to a PoE switch, and let the system
start. Do not press the power button.
• If the PBX is in Standby state (power LED is red), press the power button (short press).
In both cases, the PBX starts (Uboot process) and the power LED turns green. After PBX startup, the
LED flashes green. The PBX is in the On state (telephony application is running).
6.2.2 Starting a PBX in LoLa boot state

1. If the PBX is in Off state, connect the PBX to a PoE switch
2. Press the power button until the LED flashes green and release the power button
If the power LED stops flashing when the power button is released, the PBX goes to LoLa boot
state. If the power LED does not stop flashing when the power button is released, the PBX goes to
On state (see: Starting a PBX in On state on page 72).
In LoLa boot state, the power LED is first lit green before it starts flashing alternatively green and
red when the software installation starts.
6.3 PBX stop process

The PBX can be stopped when it is in On or LoLa boot state.

Chapter 6 PBX start and stop
To stop the PBX (Standby state), press the power button and keep your finger on the button for at
least five seconds.
The PBX shuts down with the power LED flashing red. When the PBX is in Standby state, the power
LED switches to steady red.
To set the PBX from Standby state to Off state, unplug the POE cable from the PBX (power LED is
off).
6.4 PBX restart process

The PBX can be restarted when it is in On or LoLa boot state.
To restart the PBX, press the power button and keep your finger on the button for less than five
seconds.
The PBX shuts down with the power LED flashing red.
Note:
PBX restart can also be performed either from the OMC or web-based tool. These tools provide access to different
restart options (warm reset, cold reset, or factory reset).

Chapter
7 System Reset
From OXO Connect Evolution, system reset can be done in the following ways:
• Warm Reset
• Cold Reset
• Factory Reset
7.1 Warm reset

In warm reset, all the system configurations are retained.
7.2 Cold reset

• The system is reset to a default configuration state
• The following parameters are retained:
• Installer passwords: Only passwords necessary for the configuration by the installer and those
that may lead to security concern are retained. Other parameters are restored to default values
• Network settings: Network configurations are retained to their configured values
• Management services access flags: Only “Allow Management services from WAN” flag is
retained to its configured value
The “Allow User application services from WAN” and “Allow User application services from LAN”
flags are reset to default values
• Cloud Connect parameters: Parameters are retained to their configured values
• New options under cold reset enable to remove data retained even after cold reset. Data to be
removed has been categorized and is removed according to the user requirement
Cold reset provides options to select the additional data to be removed.
Configurations retained by default in cold reset can also be removed by selecting the appropriate data.
When cold reset is triggered without selecting any sub options, system changes to default configuration
except the retention of data mentioned above.
When sub options are selected, additional data is removed accordingly.
Data to be removed is categorized as follows:
• User data
• System data
• Cloud Connect data
• Network, installer passwords and Management Data
7.2.1 User data

Following information related to users/subscribers is categorized as user data:
• Voice mail (VMU)
• Instant Messaging (IM)
• Mails
When cold reset is selected with User data sub option, the above data is removed in addition to cold
reset.

Chapter 7 System Reset
7.2.2 System data

Following information is categorized as system data:
• Secondary software
• Data saving files
• NMC
• Historic events
• Hardware anomalies
• Urgent alarms
• Metering
• Traces and core files
• ACD statistics and logs
When cold reset is selected with System data sub option, the above data is removed in addition to cold
reset.
Only reset.log is retained as part of traces and core files to get information about earlier resets.
7.2.3 Cloud Connect data

Cloud Connect data includes CCC data and CCO data.
Following information is categorized as CC data:
• Activation state
• FTR completion status
• Server URL
• One Time Activation account and password
• Final account and password
When cold reset is selected with Cloud Connect data sub option, the above data is removed in addition
to cold reset.
7.2.4 Network, installer passwords and Management Data

Following information is categorized as Network and management data retained in cold reset:
• Network configuration
• Host Name
• IP address
• Net Mask
• Broadcast
• Gateway
• VLAN
• Router
• Domain Name Server
• Web Proxy parameters
• IP/hostname
• Port
• Account
• Password
• Management passwords
• Attendant

• Administrator
• Installer
• Download
• NMC
• Management services access flag
• Allow Management services from WAN
When cold reset is selected with Network and Management data sub option, network configuration,
management passwords and management service access flags change to their default configuration.
7.3 Factory reset

Factory reset removes all the sub categories of data in cold reset and also removes system logs and
license*.
After Factory reset, the system state is close to that of LoLa installation.
If system logs and license are to be retained, installer must launch cold reset with all the sub options
enabled.
* During License removal if the temporary state is active, counter is not reset. When license is
removed, installer has to reinstall the license.
7.4 Data reset summary

The following table shows the data removed/not removed in factory reset and cold reset when
compared to LoLa installation.
table 7.1: Data removed/not removed in factory reset and LoLa installation
S. No Data Factory reset LoLa installation Cold reset category

1 VMU User data
2 IM User data
3 NMC System data
4 License
5 System logs
6 Traces and core files System data
7 Secondary Software System data
8 Mails User data
9 Metering System data
10 Cloud Connect data * Cloud Connect data

ACD statistics and
11 System data
logs

S. No Data Factory reset LoLa installation Cold reset category

Network
configurations, Network, installer
12 management access passwords and
flags, management Management Data
passwords
13 Trust store
14 Server Certificate
15 Certificate Authority
16 Data Saving files System data
: Data removed
: Data not removed

* : Data remove is optional

Chapter
8 SNMP
8.1 Overview
The OXO Connect Evolution includes an SNMP service enabling network supervision (remotely or
locally) of the system from an SNMP supervisor. The number of OXO Connect Evolution nodes
supervised by OmniVista 8770 is limited. SNMP is a protocol commonly used for data network
supervision.
Historic, hardware anomalies and urgent alarms of the OXO Connect Evolution are got via the SNMP
service. Through the SNMP, an alarm report mechanism with traps (SNMP Trap V2C mechanism)
allows to report the urgent alarms of the system on the fly.
Configuration and actions on the system are provided by the OMC tool.
SNMP allows to provide a physical view of system information and equipment status, via:
• MIB-II, which describes all the IP network side and the corresponding generic alarms
• The host resources MIB which describes a “host” system (with all resources)
• Some private MIBs which describe:
• The OXO Connect Evolution Hardware
• The telephony service: historic, hardware anomalies and urgent alarms tables
All these data (information and status), read from the OXO Connect Evolution, cannot be modified.
For more information, see: TC2093en ed.02, available from the Business Portal.
8.2 Protocol
8.2.1 Topology
The SNMP service is a mechanism to supervise remotely the system. Three SNMP protocol versions
are normalized differing from each other mainly on security aspects.
The SNMPv2c protocol is implemented on OXO Connect Evolution. Security is based on a community
identifier, which is sent transparently over the network for trap sent from the OXO Connect Evolution
and status got from the supervisor
VPN is recommended for the exchanges between the OXO Connect Evolution SNMP agent and the
remote supervisor. It can be offered with an network operator.
The OXO Connect Evolution sends its own specific traps, easily integrated with supervisors
The service is available on LAN and WAN with low security level. When enabled, a supervisor can:
• Receive, on the fly, the urgent alarms of the system
• View the system’s life (some supervisors ping their agent), its configuration (hardware description)
and status at any time
8.2.2 Security
When the supervisor is the network operator, it can supervise several OXO Connect Evolution located
in different enterprises. If all the OXO Connect Evolution supervised belong to one enterprise through
an Intranet, the supervisor can be either the operator or the enterprise itself.

Chapter 8 SNMP
When the supervisor is not the operator network, the security must be provided with a VPN which
ensures integrity, confidentiality and authentication if necessary.
On the supervisor side, a gateway VPN must be used, and:
• The supervisor must have a public IP address
• The supervisor must be accessible from the OXO Connect Evolution, and vice versa
Only UDP protocol is used for SNMP.
Ports used by SNMP are the default ones:
• Port 161 (GET mode): used by the OXO Connect Evolution, open only when the SNMP is activated
in the OXO Connect Evolution
• Port 162 (TRAP mode): used by the supervisor to receive the traps
The OXO Connect Evolution uses only SNMP V2c security. The "community identifier" must be known
by all entities and the authentication of clients is performed only by a "community string", as a
password, which is transmitted in clear text. Packets are not encrypted.
8.2.3 SNMP Trap

The OXO Connect Evolution sends specific traps. Different cases are possible about this sending of
SNMP traps:
1. When the trap name is described in MIB, a trap containing MIB information is sent
2. When the trap name is not described in MIB, a default trap is sent.
The trap name chosen depends on the alarm level severity:
• Unknown Incident
• Critical Incident
• Major Incident
• Minor Incident
• Warning Incident
• Indeterminate Incident
The trap contains the following information:
• Alarm time
• Severity alarm
• Alarm event NMC number
• Alarm event name
• Equipment board information
• Complement information
• Event type
• Probable cause

Chapter 8 SNMP
table 8.1: SNMP Trap List
SNMP Trap Type SNMP Trap Name
Trap defined in MIB ochmSystemRestart

ochmSystemRestarted
ochmCabinetUnplugged
ochmCabinetOperational
ochmBoardFailure
ochmBoardCleared
ochmBoardOperational
ochmPowerSupplyFailure
ochmPowerSupplyOperational
ochmFanFailure
ochmFanOperational
ochmIsdnFailure
ochmIsdnOperational
ochmVoipLinkDown
ochmVoipLinkUp
ochmIbsSynchroDown
ochmIbsSynchroUp
ochmAnoRegisterReject
ochmRemoteAccessMbxLocked
ochmRemoteAccessMbxUnlocked
ochmRemoteAccessWsapiLocked
ochmRemoteAccessWsapiUnlocked
ochmArpSpoofInfo
ochmDefaultPasswordFound
ochmEasyPasswordFound
ochmDhcpServerExited
ochmDhcpServerStatus
ochmAnoQuarantineAlert
ochmMgtsrvLock
ochmMgtsrvUnlock
ochmUnsupportedRamSize
ochmMsdbHealthStatus
ochmAnoPrinterFault ochmAnoMemoryAvail

Chapter 8 SNMP
SNMP Trap Type SNMP Trap Name
ochmTermRebootOrResetOfUserData
ochmBoardTempReset
ochmThresholdHardwareTBL
ochmThresholdHistoryTBL
ochmThresholdMeteringTBL
ochmThresholdUrgentTBL
ochmNmcMeteringTblFull
ochmAnoNoeDLDFail
Trap Default ochmNotifUnknownIncident

ochmNotifCriticalIncident
ochmNotifMajorIncident
ochmNotifMinorIncident
ochmNotifWarningIncident
ochmNotifIndeterminateIncident
No trap is sent when the network connection is down, and they are definitely lost. In this case, the
supervisor will retrieve the eventsthe next time it gets the MIBs.
There is no acknowledgment that a trap is correctly received by the SNMP supervisor.
8.2.4 MIB
The MIB files can be collected in two categories:
• Standard MIBs: MIB-II is enabled for the following elements:
• System: global information (Linux version / OID enterprises…)
• Interfaces: network interfaces statistics
• AT: Address Translation (deprecated)
• ICMP: ICMP statistics
• Transmission: SNMP global statistics
• SNMP: SNMP detail statistics
• Proprietary MIBs, containing:
• A hardware MIB available to give a view of what OXO Connect Evolution system is made of
• A specific MIB dedicated to the call handling
8.2.4.1 Hardware MIB

The Hardware description gives information about the board itself.
No information about connection managed by a board is indicated, except for the LAN-Switch board on
which are given:
• The ports Status
• The Ethernet negotiations (10/100 Mb/s ; Half or Full duplex)

Chapter 8 SNMP
8.2.4.2 Call handling MIB

The call handling MIB provides:
• Global status
• Element description for the three tables: history event, hardware anomaly and urgent alarm
• Specific trap for urgent alarms
The global status reflects the urgent alarm of the highest severity currently opened. The supervisor
polls this status to animate the color of the OXO Connect Evolution node on its map, allowing to quickly
locate the problems occurring on a system.
In the three tables: history event (max 500 entries), hardware anomaly (max 250 entries) and urgent
alarm (max 100 entries), the oldest entry is removed and replaced by the new one, when they are full.
These three tables are returned to the GET request done by a supervisor.
The historic event and hardware anomaly tables allow reading the recent problems that have occurred.
Some of these problems correspond to the traps sent by OXO Connect Evolution, but most of them
only describe less important troubles that the system has encountered.
When an alarm reports the occurrence of a problem, and another one reports the end of the same
problem, then they are correlated. The following table is a synthetic view of correlated alarms of the call
handling MIB.
table 8.2: Call handling MIB
Alarm
Alarm description
Start End
System reset ochmSystemRestart ochmSystemRestarted
Fan alarm ochmFanFailure ochmFanOperational
VoIP board Ethernet ochmVoipLinkDown ochmVoipLinkUp

interface problem
IBS alarm ochmIbsSynchroDown ochmIbsSynchroUp
Access Mbx ochmRemoteAccessMbxLocked ochmRemoteAccessMbxUnlocked
Access Wsapi ochmRemoteAccessWsapiLocked ochmRemoteAccessWsapiUnlocked
8.3 Configuration
8.3.1 Configuring the SNMP Service
The SNMP configuration is performed using the OMC tool. The SNMP service can be activated or
deactivated via the OMC tool (deactivated by default).
Note:
In case of default, the access to the SNMP service is not enabled for the supervisor and all parameter fields are
empty.
To declare the SNMP Service to Supervisors:
1. From the OMC tool, navigate to the menu

Chapter 8 SNMP
2. Review/modify the following global parameters:
Enable Flag Select the check box to activate the SNMP service
System Contact Enter contact information of the person responsible for this man-
aged system
System Name Enter the administrative name of the system
System Location Enter the physical location of the system

3. Up to five supervisors can be defined and are usable at the same time to get requests:
Address Indicate the supervisor IP address:

• To open a firewall for supervisor on GET mode
• To add a supervisor on sender TRAP list
Enable Flag Select the check box to activate the supervisor
3 Communities Community identifier allowing to access to the system information

from three communities:
• Read community: allows GET mode
• Read-write community: allows GET and SET mode
• Trap community: send SNMP traps to all users defined
4. Confirm your entries
8.3.2 Notification Filtering

Only critical alarms that are configured urgent by OMC are sent on the fly (with trap mechanism) to the
supervisor.
The trap base on the SNMP supervisors can be filtered upon one or more criteria (source, type...) to
limit the number of alarms displayed.
8.4 Supervision
A zip file containing the MIBs description can be downloaded through Web dialog window, see [9]. It is
a free downloadable access, even when SNMP is not activated.
The alarm supervision is done exclusively either through the SNMP supervisor or the NMC. The two
services are exclusive, but neither the OMC nor the OXO Connect Evolution check it. The installer
must insure that both are not configured.
The NMC can be used for taxation purpose in parallel of the SNMP supervision.

OXO - Connect - Evolution - 3.1 - SD - MaintenanceServices - 8AL91229USAB - 1 - en - (Glossario de Erros Dos Alarmes Do OXO)

Uploaded by

Copyright:

Available Formats

OXO - Connect - Evolution - 3.1 - SD - MaintenanceServices - 8AL91229USAB - 1 - en - (Glossario de Erros Dos Alarmes Do OXO)

Uploaded by

Document Information

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

OXO - Connect - Evolution - 3.1 - SD - MaintenanceServices - 8AL91229USAB - 1 - en - (Glossario de Erros Dos Alarmes Do OXO)

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent OXO Connect Evolution

Expert Documentation: Maintenance Services

3.1 Replacing a Set............................................................................................................................14

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 3/83

4.1 Backup/restore of all data................................................................................................. 18

5.1 Interface markers ..................................................................................................................... 23

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 4/83

5.4.5 Additional information contained in message 113 (INFO 1: cause of refusal)......68

7.1 Warm reset....................................................................................................................................... 74

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 5/83

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 6/83

1 Expert Documentation structure

table 1.1: Expert Documentation structure

Documentation title Part number

[1] OXO Connect Evolution Expert Documentation: General Presentation 8AL91218xxxx

[3] OXO Connect Evolution Expert Documentation: User services 8AL91220xxxx

[4] OXO Connect Evolution Expert Documentation: Voice mail 8AL91221xxxx

[5] OXO Connect Evolution Expert Documentation: Mobility 8AL91222xxxx

[6] OXO Connect Evolution Expert Documentation: VoIP services 8AL91223xxxx

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 7/83

Documentation title Part number

[7] OXO Connect Evolution Expert Documentation: Private networks 8AL91224xxxx

[8] OXO Connect Evolution Expert Documentation: General applications 8AL91225xxxx

[9] OXO Connect Evolution Expert Documentation: Web-based tool 8AL91226xxxx

[11] OXO Connect Evolution Expert Documentation: Management tools 8AL91228xxxx

[12] OXO Connect Evolution Expert Documentation: Maintenance services 8AL91229xxxx

[13] OXO Connect Evolution Expert Documentation: Security 8AL91230xxxx

[14] OXO Connect Evolution Expert Documentation: System services 8AL91231xxxx

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 8/83

Documentation title Part number

[15] OXO Connect Evolution Glossary 8AL91232xxxx

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 9/83

2 PBX diagnostic tool

2.2 Connecting a management computer to the PBX and powering the

2.3 Accessing the diagnostic mode

2.3.1 Accessing the diagnostic mode from the web-based tool

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 10/83

The web-based tool home page opens.

Figure 2.1: Web-based tool IPBox Diagnostic Test page example

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 11/83

1- Boot from network

2.4 Launching the diagnostic test

1. Select 2 to enter the diagnostic tool for customer.

2.5 Downloading the diagnostic test results

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 12/83

2.6 Exiting the diagnostic mode

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 13/83

3.1 Replacing a Set

3.1.1 Temporary Substitution

Defective Replacement Replacement Repaired

3.1.2 Permanent Replacement

3.1.3 Characteristics Preserved During Temporary or Permanent set Substitution

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 14/83

3.1.4 Data Preserved During Permanent Set Replacement

3.2 Relocating a Set

3.2.1 Relocating a Set to an Unused Socket

"Terminal movement" code

3.3 Adding Sets

8AL91229USAB - Ed. 01 - April 2019 - Expert Documentation: Maintenance Services 15/83