OXO Connect 5.1 SD MaintenanceServices 8AL91211USAK 2 en

Hybrid-Cloud platform
for SMBs
OXO Connect
Expert Documentation: Maintenance Services

Release 5.1 - April 2022
8AL91211USAK Ed. 2
Legal notices
http://www.al-enterprise.com The Alcatel-Lucent name and logo are trademarks of Nokia used under
license by ALE. To view other trademarks used by affiliated companies of ALE Holding, visit: www.al-
enterprise.com/en/legal/trademarks-copyright. All other trademarks are the property of their respective
owners. The information presented is subject to change without notice. Neither ALE Holding nor any of
its affiliates assumes any responsibility for inaccuracies contained herein. © Copyright 2022 ALE
International, ALE USA Inc. All rights reserved in all countries.
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: https://myportal.al-enterprise.com.
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
Problem-solving methodology
2.1 Maintenance....................................................................................................................................10
2.2 Troubleshooting procedure ........................................................................................... 10
2.3 Extent of failure ..........................................................................................................................10
2.4 Deliberate reproduction of defaults ....................................................................... 11
2.5 Locating errors ........................................................................................................................... 11
2.6 Element substitution .............................................................................................................11
2.6.1 Rules to respect ..................................................................................................................................11
2.6.2 Powering up/down the system .................................................................................................... 11
Chapter 3
Board Management
3.1 Generalities..................................................................................................................................... 12
3.1.1 Single CPU replacement................................................................................................................. 12
3.1.2 Chassis replacement.........................................................................................................................12
3.2 Plugging/unplugging a board........................................................................................12
3.2.1 Plugging a board ................................................................................................................................13
3.2.2 Unplugging a board .......................................................................................................................... 13
3.3 Assigning directory numbers ...................................................................................... 13
3.3.1 Configuration checks ....................................................................................................................... 14
3.4 Initializing sets ............................................................................................................................15
8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 3/91

Table of
Chapter 4
Replacing/relocating sets
4.1 Replacing a set............................................................................................................................ 16

4.1.1 Temporary substitution..................................................................................................................... 16
4.1.2 Permanent replacement.................................................................................................................. 16
4.1.3 Characteristics preserved during temporary or permanent set substitution ......... 16
4.1.4 Data preserved during permanent set replacement ......................................................... 17
4.2 Relocating a set ......................................................................................................................... 17
4.2.1 Relocating a set to an unused socket.......................................................................................17
4.3 Adding sets .................................................................................................................................... 17
4.4 IP phones...........................................................................................................................................17
4.4.1 Automatic Set Relocation Retrieve............................................................................................ 18
4.4.2 Automatic Set Relocation Replace.............................................................................................18
Chapter 5
Backup/restore
5.1 Backup/restore of all data................................................................................................. 20

5.1.1 Overview..................................................................................................................................................20
5.1.2 Configuration......................................................................................................................................... 20
5.2 Restoring data after hardware change................................................................. 21
5.2.1 The MSDB 8 GB equipped with eMMC is not faulty and does not have to be
exchanged.............................................................................................................................................. 21
5.2.2 The MSDB 8 GB equipped with eMMC is faulty and has to be exchanged...........21

Table of
Chapter 6
System messages
6.1 Interface markers ..................................................................................................................... 22

6.2 Hardware messages............................................................................................................... 22
6.3 History messages .................................................................................................................... 28
6.4 Information displayed ..........................................................................................................69
6.4.1 Types of board (INFO 0 of messages 100, 101, and 244) ............................................ 69
6.4.2 Types of terminal (INFO 0 of messages 110, 111 and 112) ..........................................70
6.4.3 Reasons for board refusal (INFO 1 of message 106) ......................................................72
6.4.4 Reasons for device restart (INFO 1 of message 110)...................................................... 72
6.4.5 Reasons for terminal refusal (INFO 1 of message 111) ................................................. 74
6.4.6 Types of interface (INFO 0 of message 113) ....................................................................... 75
6.4.7 Additional information contained in message 113 (INFO 1: cause of refusal)......75
6.4.8 Software key states (INFO 1 of message 34) ......................................................................77
6.5 Management of two-color led on attendant station ............................... 78
6.6 Urgent alarms .............................................................................................................................. 78
Chapter 7
Start and stop of a system
7.1 Maintenance....................................................................................................................................80
7.1.1 Start monitoring .................................................................................................................................. 80

Table of
Chapter 8
System reset
8.1 Warm reset....................................................................................................................................... 81

8.2 Cold reset.......................................................................................................................................... 81
8.2.1 User data.................................................................................................................................................81
8.2.2 System data...........................................................................................................................................82
8.2.3 Cloud Connect data........................................................................................................................... 82
8.2.4 Network, installer passwords and management data....................................................... 82
8.3 Factory reset.................................................................................................................................. 83
8.4 Data reset summary................................................................................................................ 83
Chapter 9
SNMP
9.1 Overview.............................................................................................................................................85
9.2 Protocol...............................................................................................................................................85
9.2.1 Topology.................................................................................................................................................. 85
9.2.2 Security.................................................................................................................................................... 85
9.2.3 SNMP trap.............................................................................................................................................. 86
9.2.4 MIB............................................................................................................................................................. 88
9.3 Configuration.................................................................................................................................90
9.3.1 Configuring the SNMP service..................................................................................................... 90
9.3.2 Notification filtering............................................................................................................................. 90
9.4 Supervision..................................................................................................................................... 90

Chapter
1 Expert Documentation structure
The Expert Documentation is split into fifteen separated documents, listed in the table below.
Expert Documentation describes the features supported by OXO Connect RC2.0* or higher.
* RCz.n, with z greater than or equal to 2, stands for any release starting from 2016 introducing
Connect capabilities.
It appears:
• On product stickers with release format: RC0zn/xx.yy
• In any documentation (including this one) as: Rz.n
Please refer to the OXO Connect Documentation Note, for historical information. In addition, the Cross
Compatibility document is the reference for detailed status about supported and unsupported devices
and applications.
table 1.1: Expert documentation structure
Documentation title Part number
[1] Expert Documentation: General Presentation 8AL91200USAK

This document contains general information on OXO Connect, such as
a brief description of services provided, platform hardware, handsets
and user applications available, limits, compatibility with standards, en-
vironmental constraints.
[2] Expert Documentation: Hardware: Platform, interfaces and devices 8AL91201USAK

This document covers all hardware aspects related to OXO Connect:
this includes description of platforms (racks), boards, sets and comple-
mentary equipment such as additional modules or interface modules.
This document also contains commissioning procedures for sets.
[3] Expert Documentation: User Services 8AL91202USAK

This document gives the presentation and configuration procedure of
features available for end-users. The final chapter of the document syn-
thesizes features availability according to the type of device or applica-
tion.
[4] Expert Documentation: Voice Mail 8AL91203USAK

This document details the integrated voice mail system and automated
attendant (general description, management, services available for
end-users), as well as the configuration procedure to connect an exter-
nal voice mail unit.

Chapter 1 Expert Documentation structure
[5] Expert Documentation: Mobility 8AL91204USAK

This document contains a detailed description of mobility services avail-
able on OXO Connect. This includes useful information to deploy an
IBS DECT, PWT, IP-DECT or xBS infrastructure, the description of as-
sociated base stations and handsets, and necessary information to im-
plement OpenTouch Conversation clients.
Note:
This document does not cover VoWLAN.
[6] Expert Documentation: VoIP Services 8AL91205USAK

This document describes VoIP protocols supported by OXO Connect
(such as SIP), configuration procedure of private or public access
through IP links, as well as dimensioning and maintenance basic infor-
mation.
[7] Expert Documentation: Private Networks 8AL91206USAK

This documentation gives a description of architectures and protocols
(such as SVPN, QSIG) supported for a private network, a description of
ARS, metering, clock synchronization, and the configuration procedure
of accesses.
[8] Expert Documentation: General Applications 8AL91207USAK

This document gives a description of various applications available on
OXO Connect, such as Hotel, Call metering, CTI, doorphones, Network
management center, point-to-point/point to multipoint T0, permanent
logical link, multiple automated attendant, multiple entities, PIMphony
Touch.
[9] Expert Documentation: Web-Based Tool 8AL91208USAK

This document describes the Web-Based Tool, which is the integrated
monitoring tool of OXO Connect.
[10] Expert Documentation: OmniTouch Call Center Office 8AL91209USAK

This document provides the description and installation procedure of
OmniTouch Call Center Office. The document also includes presenta-
tion and operation of Announcement, Traceability, and a short descrip-
tion of Agent, Statistics and Supervisor applications.
[11] Expert Documentation: Management Tools 8AL91210USAK

This document describes the management tool available for OXO Con-
nect(OMC). The document describes the OMC installation procedure,
the different types of access between OMC and OXO Connect (local,
remote, with or without proxy), the software installation procedure of
OXO Connect via OMC and the list of services that can be managed by
OMC.

Chapter 1 Expert Documentation structure
[12] Expert Documentation: Maintenance Services 8AL91211USAK

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

This document gives essential information to secure your OXO Con-
nect. This includes deployment guide for certificate, management of
passwords, management of accesses to services from LAN/WAN and
network configuration for remote accesses.
[14] Expert Documentation: System Services 8AL91213USAK

This document gives information about software keys, including their
complete list. The document also describes operation of OXO Connect
with NTP (as client or server) and the configuration of the embedded
DHCP server.
[15] Glossary 8AL91214USAK

This document contains a glossary of general telecommunications
terms as well as specific terms related to OXO Connect.
[16] Server Deployment Guide for Remote Workers using DeskPhones 8AL90345ENAA
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.
Outlook is either a registered trademark, or a trademark of Microsoft Corporation in the United States
and/or other countries.

Chapter
2 Problem-solving methodology
2.1 Maintenance
WARNING
A USER IS NOT AUTHORIZED TO WORK ON THE CABINET.
ONLY A REPRESENTATIVE OF THE INSTALLER IS AUTHORIZED TO WORK ON THE
CABINET.
This section does not deal with failures caused by configuration errors nor with those caused by errors
in the telephone features.
In all cases, a thorough knowledge of the system (architecture, distribution of function processing, etc.)
and of its telephone features is essential, and in particular the limits of these features.
Errors concerning distribution must be eliminated first.
To avoid taking a wrong track when determining faults, it is vital to define the source of the fault from
the outset:
• operating error by the user
• programming error by the user or operator
• programming error in implementation
• genuine system failure
2.2 Troubleshooting procedure

For any system failure, it is essential to make visual checks (LEDs for the various boards, data testing,
automatic set testing), to check the power supply voltage (electrical and battery) and to read the
system messages.
The procedure is as follows:
• locate the terminal(s) affected by the fault. If several terminals are affected by the same fault,
determine the common link which might be the cause (logical numbers of the same board,
geographical distribution, same type of programming, etc.)
• determine at what level the error is occurring (internal or external call, etc.).
2.3 Extent of failure

A failure may be characterized by various aspects:
• Total system failure:
• In this case, the fault can only be located in the module
• The failure is most likely to come from the power supply or from the CPU (control unit); the next
most likely cause is a set or network interface board interfering with the CPU.
• Total failure of a group of sets:
• if all the sets are on the same board, then the fault probably lies in the board
• if all the sets go out on the same cable, then the fault probably lies with the cable.

Chapter 2 Problem-solving methodology
• Total failure of a single terminal: the fault is probably in the set itself. If not, check the equipment in
question.
• Partial failure of a single terminal: the fault is probably due to the configuration or mode of operation.
2.4 Deliberate reproduction of defaults

To make sure that your analysis of the fault is correct, it is essential to try to repeat the failure
intentionally, unless it is unequivocal and permanent.
Once the fault is observed or repeated, and depending on the presumed source of the failure, replace
the faulty item with a working one and try to repeat the original fault again.
If the fault remains, perform a complete analysis of the failure again.
2.5 Locating errors

Power supply problem
If the electrical and battery operation LEDs are both out, check all the fuses.
If the fuses are OK, this means that the duration of the electrical power outage has been longer than
the battery autonomy.
PowerCPU EE board problem
If the LEDs of the PowerCPU EE board are off, or are on steady, the system control unit is not working.
Miscellaneous
For any fault signaled on a terminal (set, add-on module or optional terminal such as a printer, etc), the
following operations will be necessary:
• Test of the maintenance terminal in place of the failed terminal
• Test of the terminal at the module level
2.6 Element substitution

2.6.1 Rules to respect
Any substitution (power supply, PowerCPU EE board equipped with the ARMADA daughter
board) must be performed with the system powered down.
With OMC, you can save and subsequently restore the configuration (see "Data Saving").
If replacing a PRA board, make sure that the configuration of the new board is consistent with the old
one.
2.6.2 Powering up/down the system

On a system with PowerCPU EE:
• Press the ON/OFF button.
• Wait for the LED to go to steady red (about 30 seconds): system powered down
• Press ON/OFF to power up again after intervening (with the boards plugged back in). Wait 3 to 4
minutes for the system to initialize completely.

Chapter
3 Board Management
3.1 Generalities
The following conditions require maintenance to handle boards after these are accepted:
• First appearance in the system:
• System configuration aspect when a new board is detected
• Initialization and start-up of the corresponding hardware
• Dynamic appearance or disappearance due to physical causes:
• Warm system reset
• Board plugged/unplugged while the system is running
• Problems detected requiring actions on the corresponding board
• Dynamic appearance or disappearance due to logical causes
The following rules apply:
• Any detected board is considered by the maintenance as PRESENT.
• A PRESENT board can be considered as ACCEPTED or REFUSED depending on the system
dimensioning or power budget criteria.
• On cold reset, all the PRESENT boards are acknowledged (accepted or refused).
• Hardware decrease aspects are only applied at cold reset. A board seen as PRESENT on cold
reset might not be detected on warm reset (board detection failure or board unplugged). In such a
situation, such a board is considered by maintenance as ABSENT (the board configuration data is
still available) after warm reset.
3.1.1 Single CPU replacement

When a CPU is faulty, a spare CPU with same traffic capacity has to be identified and the faulty CPU
isolated from the network (OmniSwitch configuration).
The DHCP configuration has to be updated to give the IP parameters of the faulty CPU to the new
CPU and the configuration save (done with the AST) restored to this new CPU. Once the configuration
is restored, the CPU will run and the telephony services will be available. The license for the old CPU
will only be operational for 30 days so a new license must be requested for the new CPU ID.
3.1.2 Chassis replacement

If a failure on the master CPU or a hardware failure of the chassis leads to a dysfunction of all the
CPUs of the chassis , the CPU will be individually seen as faulty. In that case, the procedure for single
CPU replacement must be applied to all the faulty CPUs.
3.2 Plugging/unplugging a board

All boards, except the CPU board, can be plugged/unplugged when the system is in operation.
Before unplugging a PowerCPU EE board, perform a clean shutdown and switch the board to Off.
Interface boards can be replaced when the system is in operation, provided their OBC's version
allows it (version legible by OMC -> Hardware and Limits).
• from the 2.006 version for old boards.
• from the 3.003 version for the APA, UAI16-1 boards.

Chapter 3 Board Management
3.2.1 Plugging a board

• Plugging a board in an unused environment:The board is considered as "present, accepted or
refused"; it depends on the various configuration settings: authorized or unauthorized slot,
equipment limits, software keys, etc. A "present and accepted" board is taken into account by the
system.
• Plugging a board into a slot which was previously used by a similar board with the same
number of interfaces or accesses: The data related to the old board are not deleted; the new
board is considered as "present, accepted or refused" with the same number of accesses or
interfaces as the previous board.
• Plugging a board into a slot which was previously used by a different board or by a similar
board with a different number of interfaces or accesses: All the data related to the old board are
deleted; the new board is then considered as if it had been plugged in a new slot.
3.2.2 Unplugging a board

If the board is unplugged when it is in "present and accepted" status, it is deactivated and declared
"absent"; the other data related to the board configuration remain unchanged. The processing is the
same for a board in a "present but refused" state, but that board will not be deactivated.
Note:
In case of a "gentle" plugging-in, it is possible that the plugged board may not be detected by the CPU board or
detected with the wrong slot number.
In online Mode, if OMC does not automatically detect a plugged/unplugged board on a powered-up system, the
session should be closed, then restarted for the board to be included.
3.3 Assigning directory numbers

At start up, a default telephone number is associated to each internal and virtual extension, according
to the default numbering plan and following the order of appearance of the interfaces and their
extensions:
The interfaces appear in the same order as the boards, so the order in which the system gives a
number to each interface is the following:
• The master cabinet extension board interfaces.
• The first satellite cabinet extension board interfaces if present.
• The second satellite cabinet extension board interfaces if present.
• The Mini-MIX daughter board interfaces if present.
• The virtual board interfaces (XRA, DECT, badge, IVPS, IP).
At the end of the start up, the next numbers are assigned to the sub-device extensions according to
their order of appearance.
The order of appearance is the same for every sub-device and the device to which it is attached.
Example:
We have a system with 2 cabinets:
• a master cabinet with a 16UA extension board.
The UA set connected to the first interface has a V24 sub-device.
The UA set connected to the last interface also has a V24 sub-device.
2 IVPS ports.
• a satellite cabinet with a 16UA extension board.

The UA set connected to the first interface has a V24 sub-device.

After the system is started, 10 DECT handsets are added.
In the above configuration, and with a 3-digit numbering plan, the phone numbers are assigned as
follows:
• From 101 to 116 to the UA interfaces on the master cabinet.
• From 117 to 132 to the UA interfaces on the satellite cabinet.
• Numbers 133 and 134 to the IVPS ports.
• Numbers 135 and 136 to the V24 sub-devices on the master cabinet.
• Number 137 to the V24 sub-devices on the satellite cabinet.
• From 138 to 147 to the DECT handsets.
Example:
We have an XS-N with an AMIX board, a PowerCPU EE with a Mini-MIX daughter board.
For sets, the numbering order is:
• UA of AMIX.
• Z of AMIX.
• Z of Mini-MIX.
• VMU ports, RA.
For trunks, the numbering order is:
• Trunks of AMIX.
• T0 of Mini-MIX.
Advantages
• This numbering order associates the phones numbers with the devices following their physical
positions in the 3 cabinets.
• No undetected interface (because of an underequipped board) gets a telephone number. Therefore,
no telephone number is wasted.
• DECT handsets can be created, after the system is started. The corresponding phone numbers
follow the number given to the sub-device last detected.
• In case of a Mini-MIX, the Z interfaces are not always in the operator group.
Drawback
An interface connected to no device is given a number.
3.3.1 Configuration checks

If there are hardware or configuration changes, the following limits are checked (for detailed
quantifications, please see "Capacities and limits" in the "Product Presentation" section):
• Maximum number of corded interfaces: Any additional interface will be refused.
• Maximum number of directory numbers: Any attempt to add another number will be rejected.
The directory numbers assigned to the auxiliaries (VMU, XRA, etc) are not covered by these
checks, and are always accepted.
• Maximum number of D-channels (T0/T1/T2 interfaces): Any additional interface (T0) or board
(PRA) will be refused.
• Maximum number of B-channels (TLs, ISDN access, VoIP access): any attempt to add another
interface will be rejected (and the interface containing the B-channel in question declared out of
service).

3.4 Initializing sets

On powering up, dedicated sets execute a self-test:
• display test
• test of the LEDs or icons of the set and add-on module, if any
• audio test

Chapter
4 Replacing/relocating sets
4.1 Replacing a set

You can replace your digital set by connecting a set of the same family, but of a different type, into your
phone socket. This substitution can be temporary or permanent.
Replacing an analog set by another analog set, or replacing a digital set by a set of the same type,
requires no special procedure (simple hardware exchange).
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.
4.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 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
4.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
4.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

Chapter 4 Replacing/relocating sets
• Locked or unlocked set

• Callbacks
• Active forwarding
• Last number redial
4.1.4 Data preserved during permanent set replacement

4.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.
4.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.
4.2.1 Relocating a set to an unused socket
Unplug Plug in
"Terminal movement" code

Movement + Dir. P1
+ password
(not default password)
4.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.
4.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.
4.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).
4.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
5 Backup/restore
5.1 Backup/restore of all data

5.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.
5.1.2 Configuration
• Manual backup:
• In the OMC (Expert View): select Data Saving & Swapping -> Commands -> validate the
backup option
• Automatic backup:

Chapter 5 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
5.2 Restoring data after hardware change

When maintaining and exchanging a PowerCPU EE board, the data stored in the MSDB (Mass
Storage Daughter Board) 8 GB equipped with eMMC (embedded Multi-Media Card) will be restored by
applying the following procedures.
5.2.1 The MSDB 8 GB equipped with eMMC is not faulty and does not have to be
exchanged
• Install the old MSDB 8 GB equipped with eMMC in the new PowerCPU EE board
• After a cold reset of the system, launch the "Data restore" process via the OMC:
• Select Comm ->Write to PBX, select the box Voice Prompts (screen "Write to PBX"). All
information saved on the MSDB 8 GB equipped with eMMC is normally available (including voice
messages and recorded conversations).
5.2.2 The MSDB 8 GB equipped with eMMC is faulty and has to be exchanged
• All messages, recorded conversations and NMC call detail records are lost.
• The cache memory is also lost.
• Launch the "Data restore" process via the OMC to restore voice files (voice prompts):
• Select Comm ->Write to PBX, select the box Voice Prompts (screen "Write to PBX")

Chapter
6 System messages
The system messages are divided into 2 tables:

• the hardware message table
• the history message table
6.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.
6.2 Hardware messages

All of the hardware faults detected locally by a board or by the PowerCPU EE board are listed in this
table.
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.

Chapter 6 System messages
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
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.
200 4070 IO/EO BASE: SLAVE Board lo- INFO 0 = interface number invalid Check the
LINK CONNECTED TO INVA- cation. cables on the
INFO 1 = base station operating
LID INTERFACE 2nd link in
Interface status
the base sta-
marker
tion
201 4070 IO/EO BASE: FRE- Board lo- INFO 0 to 3 = bitmap of frequen-
QUENCY REJECTION cation. cies authorized and in use
Discrepancy between the num- Interface For more information, refer to the
ber of frequencies configured marker "Installing 4070 IO/EO base sta-
by the installer and the number tions", file in the "Mobility" section.
of DECT frequencies pro-
cessed
202 4070 IO/EO BASE: LOSS OF Board lo- INFO 0 = link status (0 = link KO; 1 Check ca-
SYNCHRONIZATION ON UA cation. = link OK) bling
LINK 0
Interface Replace the
marker 4070 base
station

203 4070 IO/EO BASE: LOSS OF Board lo- INFO 0 = link status (0 = link KO; 1 Check ca-
SYNCHRONIZATION ON UA cation. = link OK) bling
LINK 1
Interface Replace the
marker 4070 base
station
204 4070 IO/EO BASE: NO REPLY Board lo-

ON DSP PRESENT (RESET) cation.
Interface
marker
205 4070 IO/EO BASE: TRANS- Board lo-

MISSION ERRORS DETEC- cation.
TED ON SERIAL LINK TO DSP
Interface
(RESET)
marker
206 4070 IO/EO BASE: ERRORS Board lo-

DETECTED DURING INITIALI- cation.
ZATION PHASE OF BOOT
Interface
PROGRAM (RESET)
marker
207 4070 IO/EO BASE: ERRORS Board lo-

DETECTED DURING SOFT- cation.
WARE DOWNLOAD PHASE
Interface
marker

MISSION BUFFER FULL cation.
Interface
marker

MISSION BUFFER FULL cation.
Interface
marker
210 4070 IO/EO BASE: A MES- Board lo-

SAGE IS SENT TO THE BASE cation.
WITH A FALSE LINK IDENTI-
Interface
TY
marker
212 4070 IO/EO BASE: WRONG Board lo-

LINE LENGTH cation.
Interface
marker

213 4070 IO/EO: RECEPTION OF Interface

AN ERRONEOUS MESAGE marker
214 4070 IO/EO: RECEPTION OF Board lo-

AN ERRONEOUS FREQUEN- cation.
CY PLAN
Interface
marker
215 4070 IO/EO BASE: WRONG Board lo-

LINE LENGTH cation.
Interface
marker
216 4070 IO/EO BASE: RECEP- Board lo-

TION OF AN ERRONEOUS cation.
MESSAGE
Interface
marker
217 4070 IO/EO BASE: RECEP- Board lo-

TION OF AN ERRONEOUS cation.
FREQUENCY PLAN
Interface
marker
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
6.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 77)
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
88 R_BINARY_SIGNATURE_FAIL Main CPU INFO 0 = Binary signature

URE verification failure stage:
(binary signature verification 00: Binary signature verification
failure during download, start- failed during binary download via
up, and periodic check) OMC
01: Binary signature verification
failed during software update via
CCO
02: Binary signature verification
failed during periodic check by the
PBX
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: Types
cation of board (INFO 0 of messages 100,
(Following a system stoppage
101, and 244) on page 69)
or after being unplugged)
101 BOARD UNPLUGGED Board lo- INFO 0 = type of board (if known)
cation (see: Types of board (INFO 0 of
messages 100, 101, and 244) on
page 69)
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 Reasons for board refusal (INFO 1
(the system
board, a permanent reset is of message 106) on page 72)
limits may
performed on it
1: REJ_MAX_BRD_POW: Too have been
much power consumed 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
70)
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
72)
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
70) (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 74)
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
70) 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 75) 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 75)
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 digital 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 board not de-
tected by the backpanel board INFO 1 = number of CPU resets
10 minutes after initialization during the-10 minute period
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
170 NMC NOT ALLOWED CALL CPU (80) INFO 0 = Type of connection:
NMC call by analog XRA (not 01: Analog

allowed) 02: ISDN
03: IP
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, or agent error
a Rainbow service which is no • 0x0C: Cloud Connect
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 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 is not in

the Pubsub node white list
• 0X23: OXO Connect 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.
6.4 Information displayed

The information given below concerns the hardware messages as well as those contained in the
system history.
6.4.1 Types of board (INFO 0 of messages 100, 101, and 244)

82H : integrated voice server

A0H : UAI board

A1H : PRA board = E1
A2H : PRA board = DLE1
A3H : PRA board = T1
A7H : virtual XRA board
B0h : main PowerCPU EE board
B4h : APA board (Analog lines)
B7h : UAI-1 board
B9h : DDI board
A5h : PRA board = PCM
BBh : Media virtual board
BCh : LanX-2 board
BFh : AMIX-1 board (Legerity)
C0h : AMIX-1 board (St)
C1h : SLI-2 board
C2h : MIX-2 board
C3h : BRA-2 board
6.4.2 Types of terminal (INFO 0 of messages 110, 111 and 112)

Types of terminal Value of INFO 0 in
message 111 and 112
4070 IO base station 1F
NOE devices
8029 Premium DeskPhone 2C
8028 Premium DeskPhone 2C
8039 Premium DeskPhone 2D
8038 Premium DeskPhone 2D
8068 Premium DeskPhone 2E
8028s Premium DeskPhone 31
8008 DeskPhone 35
8088 Smart DeskPhone 36
xBS 37
8019s DeskPhone 38


message 111 and 112
8039s Premium DeskPhone 3A
8008G DeskPhone 3B
WLAN devices
Alcatel-Lucent 8118/8128 WLAN Handsets 2B
Alcatel-Lucent 8158s WLAN Handset 3C
Alcatel-Lucent 8168s WLAN Handset 3D
ALE-20h Essential DeskPhone IP 3E
ALE-20h Essential DeskPhone TDM 3F
ALE-30h Essential DeskPhone IP 40
ALE-30h Essential DeskPhone TDM 41
ALE-20 Essential DeskPhone 42
ALE-300 Enterprise DeskPhone 43
Subdevices
10-key add-on module for IP Premium DeskPhones/Digital Premium 4A
DeskPhones
40-key add-on module for IP Premium DeskPhones/Digital Premium 4B
DeskPhones
Smart Display Module 4C
EM-200 Smart Expansion Module 4D
ALE-120 Key Expansion Module 4E
GAP devices
GAP DECT handset without display 58
GAP DECT handset with 16 character-display 59
Third-party DECT GAP handset without display 5A
Third-party DECT GAP handset with 16 character-display 5B
GAP DECT handset with 2x16 character-display 62
GAP: 8232 DECT 63
8242 DECT 64
8262 DECT 65
8212 DECT 66
8254 DECT 67
8234 DECT 68


message 111 and 112
8244 DECT 69
CSTA virtual set 6B
SIP devices
Basic SIP phone -6C
4135 IP Conference Phone 6D
Open SIP phone 72
IP-DECT: 8232 DECT 75
IP-DECT GAP 76
SIP Companion 78
8242 DECT 79
8135s IP Conference Phone 7D
8008 CE 7E
8008G CE 7F
ALE-2 DeskPhone 80
6.4.3 Reasons for board refusal (INFO 1 of message 106)

01H : consumption limits exceeded
04H : unknown board type
05H : board refused
06H : no primary access in basic module
07H : feature denied (rights linked to license)
09H : board cannot be initialized
0FH : max number of trunks on mixed boards exceeded
6.4.4 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 telnet x


9: UA3G_RESET_MESSAGE UA3G reset received x
10: UA3G_TSC_RESET_MESSAGE TSC reset received x
11: NOEP_RESET_MESSAGE NOE reset message received without bin x x
download
12: NOEP_DOWNLOAD_REQUEST NOE reset message received with bin x x
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: DHCPC_NO_OFFER_RECEIVED DHCP offer received x x
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: DHCPC_DIFF_ADDR_RECEIVED Received a different IP address from the x x
DHCP server
24: INIT_PSK_CUSTOM_MODE Exit from the PSK customization mode x
25: BAD_SEC_MODE_RESET_MSG The terminal was running in a bad security x x
mode, typically, was not secured while it
should have been
26: DOT1X_FAILURE Dot1x Authentication failed x x
27: END_BOOT_WITHOUT_DOWNLOAD End of bootloader without any download x
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_NOE_APPLICATION SIP_MODE INTO NOE_APPLICATION x
39: NEW_VLAN_UPDATE_LLDP New VLAN update in LLDP x x
50: DSP_STALLED The DSP is stalled x
51: WBM_ENGINEER_FACTORY_RESET An administrator logged to WBM (engineer) x
has pushed the Factory reset button


53: RESET_BUTTON_MEDIUM An administrator has push the reset button for x
a medium duration
53: RESET_BUTTON_LONG An administrator has push the reset button for x
a long duration
6.4.5 Reasons for terminal refusal (INFO 1 of message 111)

Rejection reason 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 sub-devices 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_PR 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

18: REJ_MAX_DLT0 Maximum of DLT0 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: 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
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 system

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

Rejection reason Meaning

34: REJ_MAX_AT_PER_CAB Maximum of analog trunk reached for a cabinet
35: REJ_MAX_AT_PER_SYS Maximum of analog trunk reached for the system
36: REJ_MAX_RESSOURCE_REACHED Maximum of resource reached (when limitation)
37: REJ_PROTOCOL_NOT_SUPPORTED Protocol mismatch
6.4.6 Types of interface (INFO 0 of message 113)

01H : analog set interface
03H : T0 access interface
04H : T2 access interface
05h : S0 set interface
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
2Bh : PCM analog 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
3Eh : integrated analog modem interface
3Fh : integrated ECMA modem interface
45h to 50h : MSG9 to MSG20 interfaces
6.4.7 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
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 system
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
34: REJ_MAX_AT_PER_CAB Maximum of analog trunk reached for a cabinet
35: REJ_MAX_AT_PER_SYS Maximum of analog trunk reached for the system

36: REJ_MAX_RESSOURCE_REACHED Maximum of ressource reached (when limitation)
37: REJ_PROTOCOL_NOT_SUPPORTED Protocol mismatch
6.4.8 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.
6.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)
• electrical power supply fault (message 123)
• 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)
6.6 Urgent alarms

OXO Connect 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 board is back in service after a system stoppage or after being unplugged (message 100)
• the board is disconnected (message 101)
• the board is permanently reset (message 105)
• the board is refused (message 106)
• the board info has been erased by MMC (message 109)
• the module is back in service (message 120)
• the module is disconnected (message 122)
• there is a power supply problem (message 123)
• 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)
• IBS synchronization lost on UA link 0 (message 202)
• IBS synchronization lost on UA link 1 (message 203)
• 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
7 Start and stop of a system
7.1 Maintenance
7.1.1 Start monitoring
It is possible to follow the progress of the start in 2 ways:
• On the display of the dedicated stations
• Using the Web-Based Tool
7.1.1.1 On station
The display on the dedicated set indicates the different steps for starting the system with following
elements: Start x.y (x is the step and y the sequence)
7.1.1.1.1 Detail:
• Start 2-6: detection of the cards of the main cabinet
• Start 2-5: search of extension 2 and loading of the VoIP channel if the extension exists
• Start 2-4 : detection of the expansion card 2 (optionnal)
• Start 2-3: search of extension 2 and loading of the VoIP channel if the extension exists
• Start 2-2: detection of the expansion card 2 (optionnal)
• Start 2-1: end of detection of telephony (appearance of virtual cards XRA IVPS)
• UNBLOCKING of the telephony (stations are operational)
• Normal display
7.1.1.2 Web-Based Tool

See: document [9].
7.1.1.3 Console port

To follow progress of start-up on the console port, use the following characteristics:
• Login: swap_serial
• Password: alcatel

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

In warm reset, all the system configurations are retained.
8.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
8.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 8 System reset
8.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.
8.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.
8.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.
8.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.
8.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 8.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
9 SNMP
9.1 Overview
The OXO Connect includes an SNMP service enabling network supervision (remotely or locally) of the
system from an SNMP supervisor. The number of OXO Connect 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 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 Hardware
• The telephony service: historic, hardware anomalies and urgent alarms tables
All these data (information and status), read from the OXO Connect, cannot be modified.
For more information, see: TC2093en ed.02, available from the Business Portal.
9.2 Protocol
9.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. Security is based on a community identifier,
which is sent transparently over the network for trap sent from the OXO Connect and status got from
the supervisor
VPN is recommended for the exchanges between the OXO Connect SNMP agent and the remote
supervisor. It can be offered with an network operator.
The OXO Connect 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
9.2.2 Security
When the supervisor is the network operator, it can supervise several OXO Connect located in different
enterprises. If all the OXO Connect supervised belong to one enterprise through an Intranet, the
supervisor can be either the operator or the enterprise itself.
When the supervisor is not the operator network, the security must be provided with a VPN which
ensures integrity, confidentiality and authentication if necessary.

Chapter 9 SNMP
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, 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, open only when the SNMP is activated in the
OXO Connect
• Port 162 (TRAP mode): used by the supervisor to receive the traps
The OXO Connect 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.
9.2.3 SNMP trap

The OXO Connect 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 9 SNMP
table 9.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 9 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.
9.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 system is made of
• A specific MIB dedicated to the call handling
9.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 9 SNMP
9.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 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, 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 9.2: Call handling MIB
Alarm
Alarm description
Start End
System reset ochmSystemRestart ochmSystemRestarted
Cabinet alarm ochmCabinetUnplugged ochmCabinetOperational
Board alarm ochmBoardUnplugged ochmBoardOperational

ochmBoardPermanentReset
Main power supply ochmPowerSupplyFailure ochmPowerSupplyOperational

failure
Fan alarm ochmFanFailure ochmFanOperational
ISDN T2 access prob- ochmIsdnFailure ochmIsdnOperational

lem
VoIP board Ethernet ochmVoipLinkDown ochmVoipLinkUp

interface problem
IBS alarm ochmIbsSynchroDown ochmIbsSynchroUp
Access Mbx ochmRemoteAccessMbxLocked ochmRemoteAccessMbxUnlocked
Access Wsapi ochmRemoteAccessWsapiLocked ochmRemoteAccessWsapiUnlocked

Chapter 9 SNMP
9.3 Configuration
9.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
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
9.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.
9.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.

Chapter 9 SNMP
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 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 5.1 SD MaintenanceServices 8AL91211USAK 2 en

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 5.1 SD MaintenanceServices 8AL91211USAK 2 en

Uploaded by

Copyright:

Available Formats

Hybrid-Cloud platform

Expert Documentation: Maintenance Services

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 3/91

4.1 Replacing a set............................................................................................................................ 16

5.1 Backup/restore of all data................................................................................................. 20

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 4/91

6.1 Interface markers ..................................................................................................................... 22

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 5/91

8.1 Warm reset....................................................................................................................................... 81

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 6/91

1 Expert Documentation structure

Documentation title Part number

[1] Expert Documentation: General Presentation 8AL91200USAK

[2] Expert Documentation: Hardware: Platform, interfaces and devices 8AL91201USAK

[3] Expert Documentation: User Services 8AL91202USAK

[4] Expert Documentation: Voice Mail 8AL91203USAK

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 7/91

Documentation title Part number

[5] Expert Documentation: Mobility 8AL91204USAK

[6] Expert Documentation: VoIP Services 8AL91205USAK

[7] Expert Documentation: Private Networks 8AL91206USAK

[8] Expert Documentation: General Applications 8AL91207USAK

[9] Expert Documentation: Web-Based Tool 8AL91208USAK

[10] Expert Documentation: OmniTouch Call Center Office 8AL91209USAK

[11] Expert Documentation: Management Tools 8AL91210USAK

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 8/91

Documentation title Part number

[12] Expert Documentation: Maintenance Services 8AL91211USAK

[13] Expert Documentation: Security 8AL91212USAK

[14] Expert Documentation: System Services 8AL91213USAK

[15] Glossary 8AL91214USAK

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 9/91

2.2 Troubleshooting procedure

2.3 Extent of failure

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 10/91

2.4 Deliberate reproduction of defaults

2.5 Locating errors

2.6 Element substitution

2.6.2 Powering up/down the system

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 11/91

3.1.1 Single CPU replacement

3.1.2 Chassis replacement

3.2 Plugging/unplugging a board

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 12/91

3.2.1 Plugging a board

3.2.2 Unplugging a board

3.3 Assigning directory numbers

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 13/91

The UA set connected to the first interface has a V24 sub-device.

3.3.1 Configuration checks

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 14/91

3.4 Initializing sets

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 15/91

4.1 Replacing a set

4.1.1 Temporary substitution

Defective Replacement Replacement Repaired

4.1.2 Permanent replacement

4.1.3 Characteristics preserved during temporary or permanent set substitution

8AL91211USAK - Ed. 2 - April 2022 - Expert Documentation: Maintenance Services 16/91

• Locked or unlocked set

4.1.4 Data preserved during permanent set replacement

4.2 Relocating a set

4.2.1 Relocating a set to an unused socket