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.

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

Chapter 6 System messages

Type Message Location Additional Information Action

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%
of its life time due to increased
block erase count
• 03: device has reached >=80%
of its life time due to increased
bad block
• 04: device has reached >=90%
of its life time due to increased
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.

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

Chapter 6 System messages

Type Message Location Additional Information Action

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.

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

208 4070 IO/EO BASE: TRANS- Board lo-

MISSION BUFFER FULL cation.
Interface
marker

209 4070 IO/EO BASE: TRANS- Board lo-

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
PROMPT FILE voice prompt

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

Chapter 6 System messages

Type Message Location Additional Information Action

244 ERROR ON READING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt

245 ERROR ON WRITING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt

246 ERROR ON OPENING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt

247 ERROR ON OPENING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt

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.

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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)

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

Chapter 6 System messages

Type Message Location Additional Information Action

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)

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

Chapter 6 System messages

Type Message Location Additional Information Action

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.

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

Chapter 6 System messages

Type Message Location Additional Information Action

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.

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
INFO 2 = 5th byte of set’s MAC ad-
dress
INFO 3 = 6th byte of set’s MAC ad-
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)

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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)

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

Chapter 6 System messages

Type Message Location Additional Information Action

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)

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
of the remote registry
INFO 2 = octet 3 of the IP address
of the remote registry
INFO 3 = octet 4 of the IP address
of the remote registry

141 REGISTER OK CPU (80) INFO 0 = octet 1 of the IP address

of the remote registry
SIP registration success
INFO 1 = octet 2 of the IP address
of the remote registry
INFO 2 = octet 3 of the IP address
of the remote registry
INFO 3 = octet 4 of the IP address
of the remote registry

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

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

143 REGISTER 423 CPU (80) INFO 0 = octet 1 of the IP address

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

144 REGISTER 400 CPU (80) INFO 0 = octet 1 of the IP address

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

145 REGISTER 403 CPU (80) INFO 0 = octet 1 of the IP address

of the remote registry
SIP registration failure (403:
Forbidden) INFO 1 = octet 2 of the IP address
of the remote registry
INFO 2 = octet 3 of the IP address
of the remote registry
INFO 3 = octet 4 of the IP address
of the remote registry

146 REGISTER 404 CPU (80) INFO 0 = octet 1 of the IP address

of the remote registry
SIP registration failure (404:
Not found) INFO 1 = octet 2 of the IP address
of the remote registry
INFO 2 = octet 3 of the IP address
of the remote registry
INFO 3 = octet 4 of the IP address
of the remote registry

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

of the remote registry
SIP registration failure (Time-
out) INFO 1 = octet 2 of the IP address
of the remote registry
INFO 2 = octet 3 of the IP address
of the remote registry
INFO 3 = octet 4 of the IP address
of the remote registry

148 REGISTER FAILED CPU (80) INFO 0 = octet 1 of the IP address

of the remote registry
SIP registration failure
INFO 1 = octet 2 of the IP address
of the remote registry
INFO 2 = octet 3 of the IP address
of the remote registry
INFO 3 = octet 4 of the IP address
of the remote registry

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
The critical threshold (80 % by
default) of the history fault table
has been reached

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

Chapter 6 System messages

Type Message Location Additional Information Action

162 THRESHOLD METERING TA- CPU (80)

BLE
The critical threshold (80 % by
default) of the data metering
buffer has been reached

163 THRESHOLD URGENT TABLE CPU (80)

The critical threshold (80 % by
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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

• 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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
type defined by the triplet of 3 first
bytes contained in comp_info

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

type defined by the triplet of 3 first
bytes contained in comp_info

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

Chapter 6 System messages

Type Message Location Additional Information Action

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.

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

Chapter 6 System messages

Type Message Location Additional Information Action

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.

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
on the value attached to the
03: The firewall has dropped a
noteworthy address, named
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
INFO 1 = Log unique identifier High
Byte
INFO 2 = Log unique identifier Low
Byte

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
on the value attached to the
03: DHCP offer failed: dynamic ad-
noteworthy address, named
dress range contains static ad-
«StoreAlertIA». This anomaly
dresses
is not stored in the historic
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
INFO 1 = Log unique identifier High
Byte
INFO 2 = Log unique identifier Low
Byte

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
Report of anomaly depends
03: No response to PAP authenti-
on the value attached to the
cation requests
noteworthy address, named
«StoreAlertIA». This anomaly 04: CHAP authentication failed
is not stored in the historic
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
INFO 1 = Log unique identifier High
Byte
INFO 2 = Log unique identifier Low
Byte

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
Report of anomaly depends
failed
on the value attached to the
noteworthy address, named 04 RAS: No IP address affected
«StoreAlertIA». This anomaly
05 VPN: PPP terminated
is not stored in the historic
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
INFO 1 = Log unique identifier High
Byte
INFO 2 = Log unique identifier Low
Byte

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

Chapter 6 System messages

Type Message Location Additional Information Action

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.
on the value attached to the
03: Original configuration file is cor-
noteworthy address, named
rupted!
«StoreAlertIA». This anomaly
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.
INFO 1 = Log unique identifier High
Byte
INFO 2 = Log unique identifier Low
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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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

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

Chapter 6 System messages

Type Message Location Additional Information Action

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
17: Cause: download request re-
fused: Internal downloader missed
18: Cause: download request re-
fused: Internal software locked
19: Cause: download request re-
fused: wrong parameter into down-
load request (available since IP
Touch R2.0)
20: Cause: download request re-
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
34: Cause: during downloading:
Decompress error
35: Cause: during downloading: Bi-
nary header error
36: Cause: during downloading:
Test error
37: Cause: during downloading:
Cannot accept more data

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

Chapter 6 System messages

Type Message Location Additional Information Action

38: Cause: during downloading: No

download running
39: Cause: during downloading:
Too many bytes received
255: Cause: during downloading:
unknown error
40: Cause: Error during checksum
check: error detected 1
48: Cause: Error during checksum
check: error detected 2
49: Cause: Error during checksum
check: bytes missing
64: Cause: Error because of sys-
tem timer expired: Acknowledge
timer failed
65: Cause: Error because of sys-
tem timer expired: Checksum timer
failed
66: Cause: Error because of sys-
tem timer expired: Downloading
end timer failed
67: Cause: Error because of sys-
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

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

Chapter 6 System messages

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
8058s Premium DeskPhone 32
8068s Premium DeskPhone 33
8078s Premium DeskPhone 34
8008 DeskPhone 35
8088 Smart DeskPhone 36
xBS 37
8019s DeskPhone 38
8029s Premium DeskPhone 39

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

Chapter 6 System messages

Types of terminal Value of INFO 0 in

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
ALE-400 Enterprise DeskPhone 44
ALE-500 Enterprise DeskPhone 45
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

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

Chapter 6 System messages

Types of terminal Value of INFO 0 in

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

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

Chapter 6 System messages

Restart reason Meaning NOE xBS

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

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

Chapter 6 System messages

Restart reason Meaning NOE xBS

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
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: 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

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

Chapter 6 System messages

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

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

Chapter 6 System messages

Reject reasons for interfaces Meaning

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

18: REJ_MAX_DLT0 Maximum of DLT0 reached

19: REJ_MAX_DLT2 maximum of DLT2 reached

22: REJ_MAX_S_ISDN_SUBS

23: REJ_MAX_S_ISDN_T2

25: REJ_MAX_IBS Maximum of IBS reached for a reached

26: REJ_MAX_WIRED_MAIN_DEV_PER_S Maximum of wired main devices reached

27: REJ_NIL_DYN_PROT Default allocated protocol is not NIL_PROT

28: REJ_MAX_POWER_BUDGET Maximum of power budget reached for a cabinet

29: REJ_MAX_HSL_LINK_TS Maximum of hsl resources reached for a cabinet

30: REJ_MAX_HDLC_RESOURCE Maximum of hdlc resource reached for the 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

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

Chapter 6 System messages

Reject reasons for interfaces Meaning

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
services are open for a limited time.
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.

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

Chapter 6 System messages

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
services are open for a limited time.
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):

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

Chapter 6 System messages

• 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)

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