0% found this document useful (0 votes)
82 views18 pages

List of Errors and Solutions: System Start-Up and On-Line Operation

This document provides a list of errors that can occur in a PBX system along with their probable causes and suggested solutions. It includes error codes ranging from 000 to 060 with descriptions of the error message, likely reasons for the error, and steps to resolve the issue. The errors cover a range of issues from system start-up failures and process errors to more specific problems involving hardware components like the internal SSD, DSP cards, USB ports, or L2 switch communications. Suggested solutions include rebooting the system, checking cable connections, replacing defective parts, and consulting the system seller for assistance.

Uploaded by

Leonardo Ortiz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
82 views18 pages

List of Errors and Solutions: System Start-Up and On-Line Operation

This document provides a list of errors that can occur in a PBX system along with their probable causes and suggested solutions. It includes error codes ranging from 000 to 060 with descriptions of the error message, likely reasons for the error, and steps to resolve the issue. The errors cover a range of issues from system start-up failures and process errors to more specific problems involving hardware components like the internal SSD, DSP cards, USB ports, or L2 switch communications. Suggested solutions include rebooting the system, checking cable connections, replacing defective parts, and consulting the system seller for assistance.

Uploaded by

Leonardo Ortiz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

List of Errors and Solutions

The tables below list the errors and their solutions.

System Start-up and On-line Operation


Error Code Error Message PROBABLE CAUSE SOLUTION
000 MPR WDT overflow  System reset due to  Please consult the seller where you
software problem purchased this PBX.

002 System Restart  System reset was


performed using
Web Maintenance
Console
 Power failure
 The PBX was
automatically reset
due to a system
fault or system
restoration

003 System start up error  System detected  Reboot PBX.


software problem  Please consult the seller where you
while the system purchased this PBX, if rebooting
booting up PBX is not effective.
004 Common process
error (Minor)
005 Common process
error (Major)
006 Common process
error (Critical)
010 Incorrect AC shut  System was  Shutdown the PBX by Web
down shutdown with Maintenance Console.
inappropriate
procedure

011 DC power down  AC power down  Check the power supply system
 Power supply circuit  See if the AC cord is connected
(PSU, back board) properly
malfunction  Check the AC cord
 Detection of over  Replace the AC cord (be sure to
current (short circuit turn off the PBX when replacing)
on optional service
cards)

014 FAN Alarm  Fan malfunction  Check if the FAN is operating


correctly
 Replace the defective FAN unit

016 CS overload  Defective cable  Check the cable diameter and
 CS malfunction length
 Optional service  Replace the CS
card malfunction  Replace the corresponding optional
service card
017 BRI port overload  Defective cable  Check the cable
 Defective ISDN  Replace the defective terminal
terminal equipment equipment
 Optional service  Check the number of connected
card malfunction terminal equipment
 Replace the corresponding optional
service card

020 Internal storage  Internal SSD  Perform a system reset of the PBX
access error malfunction through Web Maintenance Console
 Bad connection of (If the system reset cannot be
Internal SSD performed, turn off the power
 PBX main board switch, and then turn it on)
malfunction  Confirm that the Internal SSD Card
is properly installed
 Replace the Internal SSD Card

022 Not enough free  Too many log files  Remove old log files
space on internal such as system log
storage and packet capture
files.
 No free space on
Internal SSD due to
aged deterioration
Internal SSD
023 System data file  Defective system  Restore the backup files
version error files on Internal  Re-install the software
SSD
024 System initialisation
file version error

025 Card initialisation file


version error
026 LCD file version error

027 System data file


checksum error

028 System initialisation


file checksum error

029 Card initialisation file


checksum error

030 LCD file checksum


error

031 System data file not  Internal SSD  Perform a system reset of the PBX
found malfunction through Web Maintenance Console
 Bad connection of (If the system reset cannot be
032 System initialisation Internal SSD performed, turn off the power
file not found  PBX main board switch, and then turn it on)
malfunction  Reprogramme the PBX
033 Card initialisation file  Replace the Internal SSD Card
not found (Turn off the power switch of the
PBX before replacing SSD)
034 LCD file not found
035 System data file
access error

036 System initialisation


file access error

037 Card initialisation file


access error

038 LCD file access error

039 File access error

044 Master CS ID  A CS ID number  Please consult the seller where you


duplicated registered as the purchased this PBX.
Master CS ID is
also detected
046 Internal Storage life  The usage lifetime  Please consult the seller where you
is running out limit of the internal purchased this PBX in order to
SSD is approaching replace the internal SSD card.

047 Program update  A Program Update  Confirm that the Program Update
failure failed file is valid

048 Program Recovery  Due to an error in


the operation of the
Program Update,
the previous
programme version
was restored

049 Expansion VOIP  A communication  Perform a system reset of the PBX


DSP link error error is occurring through Web Maintenance Console
between the PBX's (If the system reset cannot be
mother board and a performed, turn off the power
DSP card switch, and then turn it on)
 Confirm that the DSP card is
properly installed (Turn off the
power switch of the PBX before
doing so)
 Replace the DSP card (Turn off the
power switch of the PBX before
doing so)

050 L2SW error  Communication  Please consult the seller where you
between PBX and purchased this PBX.
L2 switch is in
trouble.

058 USB overcurrent  A device that  Remove the device connected to


causes an the USB port
overcurrent to occur
at the USB port has
been connected
059 USB restore  A data restore  This message indicates that a data
succeeded operation from a restore operation was successful
USB memory
device was
successful
060 USB restore failed A data restore  Check that the backup data stored
operation from a USB on the USB memory device is valid
memory device failed

061 Shelf cabinet  Cabinet information  Confirm that connected Legacy GW


mismatch mismatch between is supported.
Legacy GW shelf  Install correct Legacy GW shelf.
installed on Web
Maintenance
Console and
Legacy GW shelf
actually connected.
 Connected Legacy
GW shelf is not
supported.

062 System Data  System Data  This message indicates System


converted converted Data was converted successfully by
successfully successfully by newly installed software.
program update.

063 Failed to convert  System Data  Restore backup of system data and
System Data convert failure restart the system for recovery of
during program the system programming
update

068 MPR Flash ROM  MPR Flash ROM  Perform a system reset of the PBX
access error malfunction through Web Maintenance Console
 Bad connection of (If the system reset cannot be
MPR Flash ROM performed, turn off the power
 PBX main board switch, and then turn it on)
malfunction  Please consult the seller where you
purchased this PBX.

090 Over Card Limitation  Too many optional  Reduce the number of optional
service cards service cards.
installed  The maximum capacity is described
in the installation manual.
119 Duplicate IP segment  WAN, LAN and  Consult your network administrator
MNT segments are
overlapped
120 MPR VoIP-DSP  A malfunction  Ignore if not frequent
failure occurred in the DSP  Perform a system reset of the PBX
on the PBX mother through Web Maintenance Console
121 MPR VoIP-DSP boot board (If the system reset cannot be
failure performed, turn off the power
switch, and then turn it on)
 Replace the DSP card
123 Duplicate IP address  IP address is  Consult your network administrator
identical to another
device’s on the
Network
124 LAN interface start  PBX main board  Perform a system reset of the PBX
up error LAN device through Web Maintenance Console
malfunction (If the system reset cannot be
performed, turn off the power
switch, and then turn it on)
 Please consult the seller where you
purchased this PBX.
125 Login authentication  Login authentication  Login using a correct Login ID and
failure failure three Password after waiting more than
consecutive times 10 minutes

127 Activation Key was  Activation Key has  It is required to purchase activation
expired (SHGW4) expired key. (IP Trunk)
129 Activation Key was  It is required to purchase activation
expired (SPE16) key. (SIP Extension)
132 Collection of date  SNTP server is not  Check SNTP client settings
and time was failed active  Consult your network administrator
(SNTP client)  Network malfunction

133 Acquisition of  DHCP server is not  Consult your network administrator


network information active
was failed (DHCP  Network malfunction
client)
134 Extension of lease  DHCP server is not  Consult your network administrator
was failed (DHCP active
client)  Network malfunction

135 Lease time was  DHCP server is not  Consult your network administrator
expired (DHCP active
client)  Network malfunction
136 IP extension or trunk  IP extension or  It is required to purchase activation
limitation over trunk limitation over key. (SIP Extension or IP Trunk)

138 Two-way Recording  The limit on the  It is required to purchase activation


or Mobile user number of two-way key.
limitation over recording or mobile
extension users was
exceeded
140 ActivationKey was  Activation Key has
expired (Pre-installed expired
licence)
145 ActivationKey was
expired
(Maintenance)
146 ActivationKey was
expired (IP-CS
channel expansion)
147 ActivationKey was
expired (Remote
maintenance)
148 ActivationKey was
expired (Normal
User)
149 ActivationKey was
expired (Mobile
User)
150 FTP server  Authentication failed  Confirm account information (ID,
authentication failure when logging in to Password)
the FTP server  Consult your network administrator
 FTP server is not
active
 Network malfunction

151 SMTP server  Authentication failed  Confirm account information (ID,


authentication failure when logging in to Password)
the SMTP server  Consult your network administrator
 SMTP server is not
active
 Network malfunction

153 FTP client limitation  Too many  This message indicates when the
over simultaneous FTP number of FTP clients logging in to
client connections the PBX exceeds limitations

154 CA private  The CA private key  Reboot PBX.


key/certification error or the CA certificate  Please consult the seller where you
data has been purchased this PBX, if rebooting
damaged PBX is not effective.

155 Server secret  The server private  This message indicates when the
key/certification error key or the server server private key or the server
certificate data has certificate data has been
been damaged automatically restored

156 E-Mail send failure  Network malfunction  Check the SMTP settings in Web
Maintenance.
 Consult your network administrator.

158 LDAP server  Network malfunction  Check communication with LDAP


communication error  Incorrect credential server
for LDAP server  Set correct credential information in
the PBX
177 ActivationKey was  Activation Key has  Renew Activation Key
expired (Advanced expired
User)
178 ActivationKey was
expired (Peripheral
Device)
179 ActivationKey was
expired (UM
Message Backup)
180 ActivationKey was
expired (Automatic
Two-way Recording)
181 ActivationKey was
expired (Call Centre)

182 ActivationKey was


expired (Multiple
CSTA Connection)
183 ActivationKey was
expired (LDAP)

185 ActivationKey was


expired
(Redundancy)
187 ActivationKey was
expired (System
Activation Key)
200 LPR start up error  Optional service  Pull out and re-insert the
(ROM NG) card malfunction corresponding optional service card
 Perform a system reset of the PBX
through Web Maintenance Console
201 LPR start up error (If the system reset cannot be
(RAM NG) performed, turn off the power
switch, and then turn it on)
 Update the software of the
202 LPR start up error  Optional service corresponding optional service card
(No Program) card malfunction  Replace the back board (be sure to
203 LPR start up error turn off the PBX when replacing)
(Version NG)
204 LPR start up error
(Download NG)
205 LPR start up error
(No response)
206 LPR start up error
(Card type NG)
207 LPR start up error
(Check SUM NG)

208 Instantaneous  A combination card  This message indicates when a


Interruption error malfunction due to combination card malfunction that
an instantaneous occurred due to an instantaneous
interruption has interruption has been automatically
been automatically recovered
recovered from

224 Expansion VoIP-DSP  Optional service  Ignore if not frequent


failure card malfunction :  Confirm that the DSP card is
VoIP-DSP properly installed (Turn off the
power switch of the PBX before
225 Expansion VoIP-DSP  Optional service doing so)
boot failure card malfunction :  Replace the DSP card (Turn off the
VoIP-DSP power switch of the PBX before
doing so)

226 MOH failure  The system failed to  Please consult the seller where you
access MOH flash purchased this PBX.
memory.
227 MOH data restore  MOH data that was  This message indicates when MOH
not successfully data that was not installed
installed due to successfully was re-installed
power loss, etc. has
been automatically
restored
230 Card disconnected  Optional service  See if the corresponding optional
card not installed service card is installed properly
properly  Pull out and re-insert the
 Optional service corresponding optional service card
card malfunction  Perform a system reset of the PBX
 Back board through Web Maintenance Console
malfunction (If the system reset cannot be
performed, turn off the power
switch, and then turn it on)
 Replace the corresponding optional
service card
 Replace the back board (be sure to
turn off the PBX when replacing)

231 LPR alive check  Optional service  Check cabling.


error card malfunction  See if the corresponding optional
 Back board service card is installed properly
232 MPR-LPR malfunction  Pull out and re-insert the
communication error  MPR card corresponding optional service card
233 LPR data check error malfunction  Perform a system reset of the PBX
through Web Maintenance Console
(If the system reset cannot be
234 DPLL clock failure performed, turn off the power
switch, and then turn it on)
 Replace the corresponding optional
service card
 Replace the back board (be sure to
turn off the PBX when replacing)
 Please consult the seller where you
purchased this PBX.

235 CS clock failure  Optional service  Replace the corresponding optional


card malfunction service card
(CSIF card only)

237 Illegal CS connection  Incorrect CS  Connect CS correctly


connection (CSIF card only)

250 T1/E1 DSP failure  Optional service  See if the corresponding optional
card malfunction service card is installed properly
 Replace the corresponding optional
service card
252 FPGA failure  Optional service  Replace the corresponding optional
card malfunction: service card
FPGA

260 UM information  Erroneous  Perform a system reset of the PBX


recorded(Minor) processing of PBX through Web Maintenance Console
software (If the system reset cannot be
 Software error due performed, turn off the power
261 UM information to external factors switch, and then turn it on)
recorded(Major)  Reprogramme the PBX
 Please consult the seller where you
purchased this PBX.
262 All UM ports  All UM ports  It is required to purchase more
exceeded the busy exceeded the busy Activation Key for UM channel.
threshold time threshold time
[hh:mm:ss]  [hh:mm:ss] shows
busy continuation
time

263 Mailbox is full  Recording capacity  Remove old messages


was exceeded the  Expand the limit of the mailbox
limit

300 Digital trunk out of  Network (digital  Check the signals from the network
Synchronisation trunk) malfunction  Check the cable
 Optional service  See if the A/B switch is set to A on
card malfunction the corresponding optional service
301 Digital trunk RAI  Wrong A/B switch card
Reception setting  See if the termination switch is set
 Wrong termination properly on the corresponding
switch setting optional service card: 120  when
302 Digital trunk AIS using RJ45 connector; 75  when
Reception using BNC connector
 See if the corresponding optional
service card is installed properly
303 Multiframe out of  Replace the corresponding optional
Synchronisation service card

304 Frame error

305 Data Link failure  Data link between  Check the connection between the
the network and network and PRI/BRI card
PRI/BRI card failed  Check the connection between the
 Data link between network and PBX
the network and
PBX failed

306 E1 Channel Block  Network (digital  Check the signals from the network
failure trunk) malfunction  Check the cable
 Optional service  See if the A/B switch is set to A on
card malfunction: the corresponding optional service
E1 card
 Wrong A/B switch  See if the termination switch is set
setting: E1 properly on the corresponding
 Wrong termination optional service card: 120  when
switch setting: E1 using RJ45 connector; 75  when
using BNC connector
 See if the corresponding optional
service card is installed properly
 Replace the corresponding optional
service card

307 LAN/WAN No Carrier  PBX not connected  Check the connection between the
to the LAN/WAN LAN/WAN and PBX

310 Port Link Failure  Voice Processing  Check the Voice Processing System
System malfunction  See if the corresponding optional
 Ports defective on service card is installed properly
optional service  Replace the corresponding optional
card service card

328 The  This code means  Consult your network provider


LoopBack(PRI23) your network
was established by provider is
Network diagnosing the PRI
line
329 Data Link failure  Data link between  Check the connection between the
the PT/CS and PBX PT/CS and PBX.
failed
330 Loop current  Detection of LCOT  Change the corresponding trunk
detection error loop current error status back to In Service
 Enter the feature number to clear
Busy Out status
 The trunk status is automatically
changed back to In Service by
system diagnosis performed at a
preprogrammed time every day

363 PPPoE connection  Network malfunction  Consult your network administrator


was disconnected
364 PPPoE  Account information  Confirm account information (ID,
authentication failure (ID, Password) that Password)
was entered is  Consult your network administrator
wrong
 Network malfunction

365 SIP Server  SIP server is not  Consult your network administrator
connection was active
disconnected  Network malfunction
366 SIP Server  Account information  Confirm account information (ID,
authentication failure (ID, Password) that Password)
was entered is  Consult your network administrator
wrong
 Network malfunction
367 DDNS Server  DDNS server is not  Consult your network administrator
connection error active
 Network malfunction
368 IP-CS  The IP-CS is not  Set an appropriate air
synchronisation synchronised with synchronisation group
failure other CSs  Refer to the Quick Installation Guide
of the KX-NCP0158
369 IP-CS Handover  Master CS2 is not  Change the status of Master CS2 to
error synchronised with OUS and then back to INS using the
Master CS1 WEB-MC
 Refer to the Quick Installation Guide
of the KX-NCP0158
378 SIP redundancy  Redundancy of SIP -
operated trunk was operated
due to;
- Receiving ICMP
- Time-out of
redundancy timer
for REGISTER
- Time-out of
redundancy timer
for INVITE
- Receiving error
response “503”
379 IP-CS alive check  IP-CS malfunction  Check the network connections
error (Sync Master (Sync Master CS1)  Refer to the manual of the
CS1)  Network malfunction KX-NS0154.

380 IP-CS alive check  IP-CS malfunction  Check the network connections
error (Sync Master (Sync Master CS2,  Refer to the manual of the
CS2, Sync Slave) Sync Slave) KX-NS0154.
 Network malfunction
381 IP-CS LAN  Wrong LAN  Set an appropriate LAN
Synchronisation Synchronisation Synchronisation Group
Group limitation over Group setting  Refer to the manual of the
KX-NS0154
382 IP-CS LAN  Network malfunction  Check the network connections
connection check  Refer to the manual of the
error KX-NS0154.

383 IP-CS IGMP Querier  Network malfunction  Check the network connections
not found  Refer to the manual of the
KX-NS0154

390 Digital signal  Synchronisation of  This information is logged when


synchronisation digital line synchronisation of digital line is
established established or established, and does not indicate
restored an error condition that needs to be
solved

391 Data Link  Connection with PC  This information is logged when


established Phone/PC Console connection with PC Phone/PC
established or Console is established, and does
restored not indicate an error condition that
needs to be solved. However, if this
is logged frequently (with "305 Data
Link failure"), check the connection
as it may not be done properly

392 Clock master card  Clock master card  Check if the proper card is selected
selected has been changed as the new clock master card
to the one indicated
by the sub code

393 LAN/WAN Carrier  PBX connected to  This information is logged when


detected the LAN/WAN synchronisation of LAN/WAN is
established

398 Data Link  Connection with  This information is logged when


established PT/CS established connection with PT/CS is
or restored established, and does not indicate
an error condition that needs to be
solved. However, if this is logged
frequently (with "329 Data Link
failure"), check the connection as it
may not be done properly
500 Acquisition of DNS  Acquisition of DNS  Consult your network administrator
Server Address was Server Address
failed (DNS Server) from DNS Server
failed

501 No response from  DNS server is not  Consult your network administrator
DNS Server active
 Network malfunction

502 No response from  STUN server is not  Consult your network administrator
STUN Server active
 Network malfunction

520 CTI link failure  System detected  Restart the CTI-Application


disconnection of
CSTA session
 CTI-Application
malfunction

525 CT Link no response  CTI-Application  Restart the CTI-Application


malfunction
526 CT Link
disconnected
(No response)

527 CDR retry out

528 Multi site start up  SD card is not  SD card should be KX-NS3134 or


error (SD card not installed when the 3135 or 3136 for KX-NS300 in
installed) Multi site connection multisite network.
is starting up

529 Multi site alive check  Communication  Check all cable connections
retry status between sites between the sites, and check that
is unstable hubs, routers, etc. are operating
correctly
 Confirm that the communication
transmission speed between sites is
sufficient
 Confirm that all other parties'
equipment is powered on
 Consult your network administrator
530 Multi site connection  A communication  Check all cable connections
error error between sites between the sites, and check that
is occurring hubs, routers, etc. are operating
correctly
 Confirm that the communication
transmission speed between sites is
sufficient
 Confirm that all other parties'
equipment is powered on
 Consult your network administrator

531 Multi site connection  A communication  This message indicates when a


recovery error between sites communication error between sites
was recovered from was recovered from
532 Multi site data sync  A communication  Check all cable connections
error error between sites between the sites, and check that
is occurring hubs, routers, etc. are operating
correctly
533 Unit start up error  A communication  Confirm that all other parties'
error between sites equipment is powered on
is occurring when  Consult your network administrator
the PBX is starting
up
534 Unit registration  Due to software  Upgrade the software of either NSX
denied version mismatch or expansion gateway, and make
between NSX and both software version same. (In
expansion gateway case of Slave unit, please login the
to be registered, site Slave unit directly and upgrade the
registration has software)
been failed
537 Change into Isolated  Malfunction  Check error log of NSX
mode occurred in NSX  Check all cable connections
 Malfunction between the sites, and check that
occurred in the hubs, routers, etc. are operating
communication path correctly
of an expansion  Confirm that the communication
gateway. transmission speed between sites is
sufficient
 Confirm that all other parties'
equipment is powered on
 Consult your network administrator
538 Isolated mode was  Isolated mode was  This message shows that the
released released. operation mode recovered from
isolated mode.
540 Network Security  PBX detected  Consult your network administrator.
Alarm attacking from the
network
541 NAS disconnected  NAS is not active  Check all cable connections
 Network malfunction between the PBX and the NAS, and
check that hubs, routers, etc. are
operating correctly
 Confirm that the communication
transmission speed between the
PBX and the NAS is sufficient
 Confirm that all other equipment is
powered on
 Consult your network administrator

542 Not enough free  Not enough memory  Remove unnecessary files from the
space on NAS space available to NAS
save the data  Check the permission of the NAS
 Wrong permission
of the NAS

543 Not enough free  No free space to  Remove old log files
space on internal place log files on an  Replace an Internal SSD card
storage for Log Internal SSD
544 USB storage  USB flash memory  Mount USB memory if you want to
disconnected installed on the PBX use
was removed
545 Not enough free  No free space to  Replace with new USB memory
space on USB place log files on a  Remove old files from the USB
storage USB memory. memory

546 Manually System  System adjusted  Confirm if this time adjustment is


clock adjusted clock using NTP or expected
caller ID information

547 System Operation  System operation


Mode (Suspended) mode was changed
Started from normal mode
to suspended mode
548 System Operation  System operation
Mode (Suspended) mode was changed
Finished from suspended
mode to normal
mode

553 Packet flooding  System detected  IP broadcast storm may have


detected the reception of a occurred in the network. Check the
large number of IP connection or configuration of the
packets network switch.
554 Packet flooding  Recovery from
recovered network abnormal
state caused by
error #553
555 ICMP packet  System received an  Consult your network administrator.
received ICMP (Internet - 003: Destination Unreachable
Control Message - 009: Destination network unknown
Protocol) packet - 014: Network unreachable for TOS
from the network - 015: Host unreachable for TOS
- 030: TTL expired in transit
- 031: Fragment reassembly time
exceeded

567 CDR(SMDR) buffer  Free buffers for  Connect SMDR device to output call
exceeded specific SMDR are recording information stored in the
usage decreasing. system.

569 Hotel billing buffer  Free buffers for  Connect hotel application software
exceeded specific hotel billing are to output billing information stored in
usage decreasing. the system.

570 DSP resource  Free DSP resources  Add a DSP card to the system.
exceeded specific are decreasing.
usage

913 PING Attack  System received a  Setup the firewall as to block ICMP
detected high quantity of echo from external network
PING packets  Take capture of network packet,
then identify the cause
914 PING Attack  PING attack
subsided stopped
915 SIP Flood Attack  System received a  Consult your network administrator
detected high quantity of in order to block the SIP connection
SIP(INVITE) if the packet is unexpected.
packets
916 SIP Flood Attack  SIP attack stopped
subsided

917 Remote MNT  Connection for


Connection remote
Established maintenance was
established
918 Remote MNT  Connection for  Confirm DNS server setting and http
Connection Timeout remote proxy setting of PBX.
maintenance was
timed-out
919 Remote MNT  Connection for  Confirm “Remote Access
Connection remote Acceptance” setting of PBX.
Disconnected maintenance was  It is required to purchase activation
disconnected key for Remote maintenance, if it is
expired.
930 Severe system  PBX became  If this problem occurs frequently,
congestion severe congestion Please consult the seller where you
mode due to heavy purchased this PBX.
traffic
 PBX refuses all
making call
operation
931 System congestion  PBX became  If this problem occurs frequently,
Congestion mode Please consult the seller where you
due to heavy traffic purchased this PBX.
 PBX refuses 80% of
making call
operation
932 Minor congestion or  PBX is getting in
recovered severe congestion
congestion
937 Operation Mode  Standby unit started  Check LAN 1 of PBX unit where
Changed: Hot as active unit due to failure detected.
Standby System detection of failure
Failure Detection of active unit.
Time Out
938 Operation Mode  Standby unit started
Changed: Hot as active unit due to
Standby System detection of failure
Recovery Detection of active unit.
Time Out
939 Data Transfer  Some of data could  Check NAS device. If
Incomplete not be unsynchronised data found, send
synchronised. them to your Customer Service
Centre.
940 Data Transmission  LAN3 connection  Check LAN3 connection between
Stopped was disconnected primary and secondary units.
or hardware
malfunctions.
941 Hot Standby: Primary  Primary PBX unit  None (It is information indicating
started started with Hot that the primary unit started.)
Standby connection.
942 Hot Standby:  Secondary PBX unit  None (It is information indicating
Secondary started started with Hot that the secondary unit started.)
Standby connection.
943 Auto backup failed  Bad connection with  Check connection and status of
due to the NAS/USB NAS/USB device or NAS/USB device.
device connection they are not
error or backup working.
storage full
944 Hot Standby:  Some of settings of  Check setting parameters for
Configuration failure Hot Standby are hot-standby feature.
conflicted, or  Reboot PBX.
internal error
occurred.
950 Hot Standby: Data  Retry of data  Check network quality and
synchronisation retry transmission throughput for HA(LAN3) connection
occurred
951 Hot Standby: Data  Buffering of data to  Check network quality and
synchronisation be synchronized throughput for HA(LAN3) connection
buffering mode started
started
952 Hot Standby: Data  Recovered from the  PBX is working correctly.
synchronisation buffering mode
normal mode
recovered
953 Hot Standby:  Software version  Update primary or secondary PBX
Different software mismatch between with same version of software
version of primary primary and
and secondary PBX secondary PBX
Optional Service Card Initial Self Diagnosis
Error Code Error Message PROBABLE CAUSE SOLUTION
211 Speech path  Optional service  See if the corresponding
loop-back check card malfunction optional service card is
error installed properly
 Pull out and re-insert the
212 Echo canceller corresponding optional
access error service card
 Perform a system reset of the
214 DSP Boot check PBX through Web
error Maintenance Console (If the
system reset cannot be
performed, turn off the power
switch, and then turn it on)
 Replace the corresponding
optional service card

215 Framer IC access  Optional service  See if the corresponding


error card malfunction optional service card is
installed properly (Turn off the
power switch of the PBX
before doing so)
 Set the status of the optional
service card to OUS, then to
INS
 Replace the corresponding
optional service card

220 Flash ROM access  Detection of  See if the corresponding


error accessing error to optional service card is
Flash ROM of installed properly (Turn off the
optional service power switch of the PBX
card before doing so)
 Set the status of the optional
service card to OUS, then to
INS
 Replace the corresponding
optional service card

221 BUS Controller  Optional service  See if the corresponding


access error card malfunction: optional service card is
STACK-S installed properly
 Pull out and re-insert the
corresponding optional
service card
 Replace the corresponding
optional service card

223 FPGA access error  Optional service  Replace the corresponding


card malfunction: optional service card
FPGA
The sub code for the IP error log means the location of the virtual IP card.

PBX Sub Code Slot Number of Virtual Card


KX-NSX2000 1-8 1-8 V-IPGW / V-SIPGW
13-29 9-25 V-IPEXT / VSIPEXT
61-76 26-41 V-IPCS
KX-NSX1000 1-5 1-5 V-IPGW / V-SIPGW
13-21 6-14 V-IPEXT / VSIPEXT
61-76 15-30 V-IPCS
1-4 1-4 V-IPGW / V-SIPGW
Expansion Gateway
KX-NS300/500/700 17-20 5-8 V-IPEXT / VSIPEXT
37-44 9-16 V-IPCS

You might also like