NWA 033627 001 40 - System Maintenance Manual

System Maintenance Manual
NWA-033627-001
ISSUE 4.0
LIABILITY DISCLAIMER
NEC Corporation reserves the right to change the specifications,
functions, or features, at any time, without notice.
NEC Corporation has prepared this document for use by its employees and customers. The information contained herein is the property
of NEC Corporation and shall not be reproduced without prior written
approval from NEC Corporation.
Dterm is a registered trademark of NEC Corporation.
PCPro is a trademark of NEC Corporation.
Copyright 2010
NEC Corporation
TABLE OF CONTENTS
INTRODUCTION
PURPOSE ................................................................................................................
OUTLINE OF THIS MANUAL ...................................................................................
TERMS IN THIS MANUAL .......................................................................................
1
2
3
PBX System Designation .................................................................................................

Terminal Name ................................................................................................................
3
3
REFERENCE MANUAL ...........................................................................................

PRECAUTIONS ........................................................................................................
5
6
System Data Backup .......................................................................................................
Chapter 1
MAINTENANCE SERVICES
HOW TO READ THIS CHAPTER ............................................................................

FAULT MESSAGE ...................................................................................................
1-2
1-3
General Description .........................................................................................................

Fault Message .............................................................................................................
External Alarm Display Panel ......................................................................................
Service Conditions ...........................................................................................................
Fault Message .............................................................................................................
Programming Procedure ..................................................................................................
Fault Message .............................................................................................................
Operating Procedure .......................................................................................................
1-3
1-3
1-4
1-5
1-5
1-5
1-6
1-6
1-15
1-15
STATION LINE STATUS DISPLAY ..........................................................................
1-16

1-16
1-16
1-16
1-16
BATTERY RELEASE CONTROL .............................................................................
1-18

1-18
1-18
1-18
1-19
DIAGNOSTICS .........................................................................................................
1-20

1-20
1-20
1-21
1-21
NWA-033627-001 Rev.4.0
95toc001.fm
JULY/17/2009
BATTERY REPLACEMENT .....................................................................................

FAULT REPORT SCHEDULING ..............................................................................
1-28
1-29

1-29
1-29
1-30
1-31
VoIP LOG COLLECTION .........................................................................................
1-32

1-32
1-34
1-42
QoS DISPLAY ON IP MULTILINE TERMINAL ........................................................
1-46

1-46
1-47
1-47
STATION SERVICE STATUS DISPLAY ..................................................................
1-48

1-48
1-48
1-49
PING COMMAND .....................................................................................................
1-52

1-52
1-52
1-55
1-56
Chapter 2
TROUBLESHOOTING
PRECAUTIONS ........................................................................................................
2-2
Grounding Requirements .................................................................................................

Static Electricity Guard ....................................................................................................
Turning Power ON ...........................................................................................................
Turning Power OFF .........................................................................................................
2-2
2-3
2-6
2-6
OUTLINE OF TROUBLESHOOTING .......................................................................

FAULT DETECTION ................................................................................................
2-7
2-8
LED Indication on Blades ................................................................................................
2-9
FAULT INFORMATION DISPLAY ............................................................................
2-12
Display on PCPro/CAT ....................................................................................................

Fault Message .............................................................................................................
Fault Diagnosis and Troubleshooting ..............................................................................
Station Line Status Display .........................................................................................
Troubleshooting by LED Indication on Blades .................................................................
Troubleshooting by Contents of Complaint ......................................................................
Explanation of Symbols in Troubleshooting Procedure ..............................................
How to Follow the Tree .............................................................................................
2-12
2-12
2-16
2-30
2-33
2-37
2-38
2-38
ii
NWA-033627-001 Rev.4.0
95toc001.fm
JULY/17/2009
Station Line Fault ........................................................................................................

C.O. Line/Tie Line Fault ..............................................................................................
Power Failure Transfer (PFT) Fault ............................................................................
Digital Multiline Terminal Fault ....................................................................................
IP Station Fault ............................................................................................................
DESKCON Fault .........................................................................................................
DSS Console Fault ......................................................................................................
iii
2-40
2-42
2-51
2-52
2-54
2-56
2-57
NWA-033627-001 Rev.4.0
95toc001.fm
JULY/17/2009
THIS PAGE LEFT BLANK INTENTIONALLY.
iv
NWA-033627-001 Rev.4.0
95toc001.fm
JULY/17/2009
INTRODUCTION
PURPOSE
INTRODUCTION
PURPOSE
This manual explains the maintenance services provided with the SV8300, and the recommended troubleshooting procedure when a fault has occurred, for maintenance personnel of this system.
NWA-033627-001 Rev.4.0
95ch0001.fm
INTRODUCTION
OUTLINE OF THIS MANUAL
OUTLINE OF THIS MANUAL

This manual consists of two chapters. The following paragraphs summarize Chapters 1 and 2.
CHAPTER 1 MAINTENANCE SERVICES
This chapter describes the general description, service conditions, programming and
operating procedure of the maintenance services.
CHAPTER 2 TROUBLESHOOTING
This chapter describes the precautions before troubleshooting, and the troubleshooting procedure flow chart.
NOTE:
For the following features, refer to the PC Programming Manual.

CPU Program Upgrade
System Data Save/Load/Verify
NWA-033627-001 Rev.4.0
95ch0001.fm
NOVEMBER/21/2008
INTRODUCTION
TERMS IN THIS MANUAL

PBX System Designation
PBX system is designated as PBX or system usually.
When we must draw a clear line between the PBX systems, they are designated as follows.
SV8300: UNIVERGE SV8300
Terminal Name
The following terminals are designated as Multiline Terminal usually, unless we need to mention the
type of terminal in particular.
TERMINAL NAME
Multiline
Terminal
Digital Multiline Terminal
PRODUCT NAME
Dterm
Dterm70 (Elite)
Dterm75 (Series E)
Dterm85 (Series i)
DT300 Series
DT310
DT330
IP
IP Multiline Terminal
Station
IP Enabled Digital
Multiline Terminal
[North America
only]
Dterm75 (Series E)
(IP Adapter Type)
Dterm85 (Series i)
(IP Adapter Type)
DtermIP INASET
DtermIP
Soft Phone
Dterm85 (Series i)
(IP Bundled Type)
DtermSP30
SP350
SIP Multiline Terminal
DT700 Series
DT710
DT730
DT750
Continued on Next Page
NWA-033627-001 Rev.4.0
95ch0001.fm
APRIL/16/2010
INTRODUCTION
TERMINAL NAME
Multiline
Terminal
IP
SIP
SIP Wireless
Station Station Terminal
PRODUCT NAME
MH240
IP Single Line IP Single Line Telephone (SIP)

Telephone
(SIP)
NOTE:
Dterm75 (Series E)/Dterm85 (Series i) terminal can be used as the IP terminal by attaching the
IP Adapter (IP Enabled Digital Multiline Terminal). This terminal provides users with all features currently available in IP Station.
NWA-033627-001 Rev.4.0
95ch0001.fm
APRIL/16/2010
INTRODUCTION
REFERENCE MANUAL
REFERENCE MANUAL
Refer to the following manuals during maintenance and troubleshooting:
Command Manual:
Contains the Customer Administration Terminal (CAT) operation, command functions and data required for programming the system.
PC Programming Manual:
Contains the functional description and the installation procedure for the PCPro.
System Hardware Manual:
Contains the installation procedure for the PBX system and the hardware installation procedure for
the SV8300.
NWA-033627-001 Rev.4.0
95ch0001.fm
INTRODUCTION
PRECAUTIONS
PRECAUTIONS
System Data Backup
CAUTION
If you operate as follows without system data backup after system data setting or service
memory setting (registration of the features such as Call Forwarding and Speed Calling
[Speed Dialing] from a station), the data that has been set is invalid.
You must execute the system data backup before the following operations.
-Turning Off the system
-System Reset (reset of CPU blade)
-Changing the CPU blade to Off-Line Mode
-Changing the CPU blade to On-Line Mode after system data setting under Off-Line Mode
You can execute the system data backup by the following two ways.
-Executing the system data backup once a day at the time set by CM43 Y=5>00
(If no data is set, the default setting is 3:00 a.m.)
-Executing the system data backup from PCPro/CAT by CMEC Y=6>0: 0
Do not reset the CPU blade while SYSD LED on the CPU blade is flashing.
NWA-033627-001 Rev.4.0
95ch0001.fm
UNIVERGE SV8300
MAINTENANCE SERVICES
Chapter
This chapter describes the general description, service conditions,

programming and operating procedure of the maintenance services.
1-1
NWA-033627-001 Rev.4.0
95ch1001.fm
Chapter 1 MAINTENANCE SERVICES

HOW TO READ THIS CHAPTER
HOW TO READ THIS CHAPTER

In the programming procedure, the meaning of (1), (2) and marking are as follows:
(1): 1st Data
(2): 2nd Data
:
Default
With the system data clear command (CM00, CM01), the data with this marking is automatically
assigned for each command.
OFF LINE
: Command with this marking can be used only under Off-Line mode of the CPU
blade.
To set Off-Line mode,
(1) Set SENSE switch on the CPU blade to E or F.
(2) Press RESET switch on the CPU blade.
1-2
NWA-033627-001 Rev.4.0
95ch1001.fm

FAULT MESSAGE
FAULT MESSAGE
General Description
Fault Message
This feature stores fault information into the Fault Store Memory, and displays the fault information on the
PCPro or the Customer Administration Terminal (CAT). For CAT operation, refer to the Command Manual.
The display format using PCPro is shown below:
The fault information is displayed in the order that faults occur.
(1)
(2)
(3)
No.
(1)
Item
Access Date field
Description
Displays the date and time at which the fault information was last read.
Continued on next page
1-3
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE
No.
(2)
(3)
Item
Fault Display
Area
Description
Number field
Displays the unique number assigned to the fault information.
Occurrence Date
and Time field
Displays the date and time at which the fault occurred.
Error Type field
Displays the number of the fault type.
Alarm field
Displays the alarm type of the fault.

-- : No alarm
MN : MN alarm
MJ : MJ alarm
Unit/Slot/Circuit
field
Displays relevant information only if the fault information pertains to a unit, slot or circuit; otherwise, displays -.
Data field
Displays detailed information about the fault selected

in the Fault Display area.
External Alarm Display Panel

[8300R3 software required]
When a fault has occurred in the system, you can detect the fault by a Major (MJ) alarm or Minor (MN)
alarm indicated on external equipment (Alarm Display Panel).
Alarm Display Panel
SV8300
Fault Information
(MJ/MN Alarm)
1-4
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

FAULT MESSAGE
Service Conditions
Fault Message
(1) The maximum number of fault information that can be stored is 10.
(2)
The alarm kind (Major Alarm, Minor Alarm or No Alarm Indication) can be programmed by CMEA
Y=2 or set by PCPro for each fault kind.

(1)
MJ Alarm occurred or MN Alarm occurred displays on the external equipment.
(2)
The notification for maintenance is indicated by the alarm lamp (MJ/MN) on external alarm panel.
The MJ or MN alarm is assigned by CMEA Y=2.
(3)
External Alarm Indication of external equipment cannot be cleared by CMEA Y=0>F from PCPro/
CAT.
(4)
External Alarm Indication of external equipment can be cleared by CMEA Y=1>00/01/02 from
PCPro/CAT.
(5)
External Alarm Indication is cleared when the turn off the system or the system reset.
(6)
External Alarm Indication can be provided by external equipment with controlling relay.
(7)
External Alarm Indication can be accommodated only for the RELAY port of Main Unit (Unit01).
Remote Unit (Unit02-50) or PGD (2)-U10 ADP/External Relay Interface of CPU blade cannot be
accommodated.
(8)
Controlling relay of external equipment provides controlling relay ON/OFF only.
(9)
The conditions when controlling relay of MN alarm are shown below.

When MN alarm has occurred, External Relay turn ON.
When MN alarm has cleared, External Relay turn OFF.
(10) The relay control (MJ alarm ON/OFF) can be assigned by CM08>912 from PCPro/CAT.
1-5
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

FAULT MESSAGE
Programming Procedure
Fault Message
(1) To set the fault information storage from the PCPro by Command Operation
DESCRIPTION
START
DATA
CM08
Enable the fault information storage feature.
(1) 450
(2) 1 : To store
CMEA
Assign which kind of fault information is

stored into the fault information memory, and
which kind of alarm is indicated.
Y=2
(1) See the following table.
(2) See the following table.
NOTE:
CMEA programming can be set by the PCPro.

1ST DATA
DATA
2ND DATA
MEANING
Fault Kind: Occurrence

System reset
012
CS/ZT fault occurred
016
It is a day periodic maintenance
017
Activation Code error occurred during the

License Activation (Center Activation)
021
ISDN D-channel link connection failure
022
CCIS link connection failure
025
Number of lockout stations was more than

predetermined number
NOTE 2
026
DLC blade down
028
SMDR output buffer (SRAM) exceeded 80

%
029
SMDR output buffer (SRAM) overflow

02B
02C
LAN application fault occurred
MEANING
External Alarm Kind

0: Fault Memory store/No output of
External Alarm
1: Fault Memory store/External Alarm is
MN alarm
MJ alarm
3: No Fault Memory store/No External
Alarm output
NOTE 1
001
DATA
NOTE 3
1-6
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

FAULT MESSAGE
DESCRIPTION
A
CMEA
DATA
1ST DATA
2ND DATA
MEANING
DATA
MEANING
040
Traffic of IP network exceeded limit bandwidth
041
Traffic of IP network exceeded warning

bandwidth
042
Communication error occurrence between

Main Unit and Remote Unit
NOTE 4
043
SIP trunk failure
048
Remote System Upgrade
External Alarm Kind

External Alarm
MN alarm
MJ alarm
Alarm output
04A
Long call duration information
061
VoIPDB Startup Process is failure

100
Power failure
102
DTI line failure
104
SV8300 Blade down
106
SV8300 Blade reset with CME0 Y=3
107
Lack of option value
108
Lack of Highway Channel
109
Auto Blade Reset by TDM-Blade Lockup

10A
CPU SRAM failure

NOTE 6, NOTE 7
10B
Restricted blade
10C
Firmware version un-matching between

CPU blade and Line/Trunk blade
DATA
NOTE 5
External Alarm Kind

External Alarm
MN alarm
MJ alarm
3: Fault Memory store/No External
Alarm output
1-7
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE
DESCRIPTION
DATA
1ST DATA
CMEA
DATA
10D
2ND DATA
MEANING
MEANING
External Alarm Kind

External Alarm
MN alarm
MJ alarm
Alarm output
Lack of Highway Channel for data communication

DATA
10E
Illegal use of CPU blade for Remote Unit

only
External Alarm Kind

External Alarm
MN alarm
MJ alarm
MN alarm
110
Communication error occurrence between

active CPU and stand by CPU
External Alarm Kind

External Alarm
MN alarm
MJ alarm
Alarm output
112
Expansion Chassis (2U) failure

114
Automatic module reset due to Expansion

Chassis (2U) lockup
External Alarm Kind

External Alarm
MN alarm
MJ alarm
Alarm output
1-8
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE
DESCRIPTION
DATA
1ST DATA
CMEA
2ND DATA
MEANING
DATA
MEANING
115
Automatic module reset due to Expansion

Chassis (2U) lockup
External Alarm Kind

External Alarm
MN alarm
MJ alarm
Alarm output
116
All blades lockup in Expansion Chassis

(2U)
Fault Kind: Restoration

031
ISDN D-channel link connection returned

to normal condition
032
CCIS link connection returned to normal

condition
035
Number of lockout stations restored to less

than predetermined number
NOTE 8
036
DLC blade returned to normal condition
038
SMDR output buffer (SRAM) return to

normal condition from 80 % condition
039
SMDR output buffer (SRAM) return to

normal condition from overflow
03B
CS/ZT returned to normal condition
03C
LAN application returned to normal condition

NOTE 3
050
Traffic of IP network returned to normal

condition from limit bandwidth excess
051
Traffic of IP network returned to normal

condition from warning bandwidth excess
DATA
External Alarm Kind

External Alarm
MN alarm
MJ alarm
Alarm output
1-9
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE
DESCRIPTION
1ST DATA
CMEA
2ND DATA
DATA
MEANING
DATA
MEANING
052
Communication error restoration between

Main Unit and Remote Unit
NOTE 4
053
SIP trunk returned to normal condition
101
Power failure returned to normal condition
103
DTI line returned to normal condition
105
SV8300 Blade returned to normal condition
External Alarm Kind

External Alarm
MN alarm
MJ alarm
Alarm output
111
Communication error restoration between

active CPU and stand by CPU
113
Expansion Chassis (2U) returned to normal

condition
CM42
DATA
External Alarm Kind

External Alarm
MN alarm
MJ alarm
Alarm output
Assign the number of stations in line lockout to

give alarm.
(1) 01
(2) 01-99 : Number of lockout stations
NONE : No Lockout Alarm Display
Assign the number of detected faulty trunks to

give alarm.
[Australia Only]
(1) 06
(2) 01-99 : Number of Line Fault trunk
NONE : No detection
Assign the number of detected faulty trunks to

give alarm.
[Australia Only]
(1) 07
(2) 01-99 : Number of Line Fault trunk
NONE : No detection
Assign the time for monitoring long call duration of trunk call.
(1) 182
(2) 01-60 : 1-60 hours
NONE : 60 hours
1-10
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE
E
CM35
DESCRIPTION
DATA
Provide registering fault information when

long call duration of trunk call occurs.
Y=286
(1) 00-63: Trunk Route No.
(2) 0 : Not provided
1 : To provide
END
NOTE 1: Even if the external alarm is set as MN or MJ alarm for system reset (1st data=01), no alarm
is output in the case of Power On, Reset key operated, reset from the PCPro/CAT, and reset by
CPU SENSE switch selection.
NOTE 2: The External Alarm Kind for Number of lockout stations was more than predetermined number is fixed as MN. In the case of this office data, even if the 2nd data is set to 0/1/2/3, it simply
means the fault information is to be registered into Fault Memory. In this case, External Alarm
Kind cannot be changed.
NOTE 3: The fault information of the fault kind No, 02C/03C is also registered to the CPU blade when
the OAI fault occurs/the OAI fault is restored. The OAI fault contents that are registered to the
CPU blade as follows.
Fault Kind 02C (LAN application fault occurrence)
(a) ABOUT/RLRQ (U-ABOUT/RLRQ received)
(b) Fault detection by health check (health check IP T.O)
Fault Kind 03C (LAN application returned to normal condition)
(a) Association is established (AARQ received)
1-11
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE
NOTE 4: Confirm the following fault information, when you check Remote Unit operations by survival
mode as fault information from PCPro/CAT in Remote UNIT over IP.
001: System Reset
042: Communication error occurrence between Main Unit and Remote Unit
052: Communication error restoration between Main Unit and Remote Unit
When Remote Unit starts the survival mode operation, the fault information Reset by CAT or
PCPro (Fault occurrence kind No. 001) is registered to the CPU blade of Remote Unit.
In addition, Communication error occurrence between Main Unit and Remote Unit (Fault
occurrence kind No. 042) is registered to the CPU blade of Main Unit at 20 seconds later from
the predetermined time set by CM0B Y=1XX>80.
Remote Unit on survival mode checks at every 30 seconds if the communications to Main Unit
are possible. When the Remote Unit regards that the communications are possible, Communication error restoration between Main Unit and Remote Unit (Fault occurrence kind No.
052) is registered to the CPU blade of Main Unit at 20 seconds later from the predetermined
time set by CM0B Y=1XX>80.
NOTE 5: About long call duration of trunk call (fault kind: 04A)
When Long call duration failure occurs, Failure occurred is displayed on the PCPro.
After a trunk is seized, when the trunk is seized longer time than the monitoring time (1-60
hours) set by CM42>182, the call is registered as long call duration failure. However, there
is a tolerance up to 30 minutes between monitoring time set by office data and actual time to
be registered.
NOTE 6: When SRAM memory is unsettled at the time that the system is started up, this fault information
can be output.
(The SMDR data in SRAM memory cannot be guaranteed to save when the system is power-off
for over a week, because the battery of SRAM runs down about a week later.)
NOTE 7: Failure cannot be judged correctly when SRAM data all clear by CM00>02 is never executed.
NOTE 8: The External Alarm Kind for Number of lockout stations was less than predetermined number is fixed to No Alarm. In the case of this office data, even if the 2nd data is set to 0/1/2/3, it
simply means that the fault information is to be registered into Fault Memory. In this case, External Alarm Kind cannot be changed.
1-12
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE
(2)
To clear the MJ/MN alarm by external key

DESCRIPTION
START
CM05
DATA
Assign a Unit and Slot number to the DLC

blade.
BLADE RESET
NOTE:
When the PGD(2)-U10 ADP is

accommodated to the Remote Unit,
execute the system data copy by
CMEC Y=8 before executing the
blade reset.
Y=0
(1) XX ZZ
XX: 01-50: Unit No.
ZZ : 01-18: Slot No.
(2) 10: DLC blade
CM10
Assign the station number connected to

PGD(2)-U10 ADP to its associated Physical
Port number.
Y=00
(1) XX YY ZZ: Physical Port No.
XX: 01-50: Unit No.
YY: 01-18: Slot No.
ZZ : 01-32: Circuit No.
(2) FX-FXXXXXXXX: Station No.
CM12
Assign the Kind of PGD(2)-U10 station.
Y=65
(1) X-XXXXXXXX: Station No.
(2) 3: External relay/external key only
Specify the External Key group number.
Y=66
(2) 00-63 : External Key Group No.
Allow the accommodation of PGD(2)-U10

ADP.
BLADE RESET
Y=63
(2) 0 : To accommodate
1 : Not accommodated
CM13
NOTE1: Set this data only for a Base Port of DLC blade.
NOTE2: Whether the following equipments can be accommodated to the same DLC blade or not
are depended on this data.
- When the second data is set to 0
Accommodatable : DT300/Dterm85/Dterm70/PGD(2)-U10 ADP
Unaccommodatable : Dterm75/DESKCON
- When the second data is set to 1
Accommodatable : DT300/Dterm85/Dterm75/DESKCON
Unaccommodatable : Dterm70/PGD(2)-U10 ADP
A
1-13
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE
DESCRIPTION
DATA
CM61
Assign the function of MJ/MN alarm clear key

to the external key.
Y=30
(1) XX Z
XX : 00-63: Key Group No. assigned by
CM12 Y=66
Z : 0/1: Circuit No.
(2) 00: MJ/MN Alarm Clear key
END
(3)
To set Alarm Kind of Fault Information using PCPro

For the way of setting Alarm kind of Fault Information using PCPro, refer to PC Programming
Manual.
1-14
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

FAULT MESSAGE

NOTE:
Setting of MJ/MN alarm of Fault Occurrence and Restoration is already programmed.

DESCRIPTION
START
CM44
Select the external alarm kind.
NOTE:
CM08
DATA
Y=00
(1) 312, 313: External Relay Interface of CPU
blade
(2) 38XX
XX
: 01-02: Fault Information
01
: MJ Alarm
02
: MN Alarm
NONE : No Data
When connecting the RELAY port (Built-in CPU blade) and the MJ/MN lamp of Alarm
Display Panel, the first data must corresponding between the RELAY port and the Circuit
number assigned by CM44 Y=00. For detail of connecting the Alarm Display Panel, refer
to the System Hardware Manual.
ERELAY port (EXCNT1) 1st data=312
ERELAY port (EXCNT2) 1st data=313
Select the external relay control for MJ alarm.
(1) 912
(2) 0 : Relay OFF (External alarm is MJ
alarm/Relay ON (Clear the external
alarm (MJ))
1 : Relay ON (External alarm is MJ
alarm/Relay OFF (Clear the external
alarm (MJ))
END
Operating Procedure
To Display Fault Messages using PCPro
For details, refer to PC Programming Manual.
1-15
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

STATION LINE STATUS DISPLAY

General Description
This feature displays the line status for a single line telephone or a Multiline Terminal using the CAT or
the PCPro.
Service Conditions
This feature is not available when the system is off-line.
No programming is required.
Operating Procedure
Operation:
ST
COMMAND=_
EC1 +
DE
COMMAND=EC1
EC1>_
X-XXXXXXXX +
(Station No.)
DE
COMMAND=EC1
EC1>XXXXXXXX : XXXXXXXX : XX XX XX-_
1
Explanation of Screen Information:

1
Station Number: X-XXXXXXXX (1-8 digits)
1-16
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

Analog Line/Digital Line

00: LC (Single Line Tel.)
10: DLC (Digital Multiline Terminal)
20: IP Station
Hardware Test
See Status of Single Line Telephone/Multiline Terminal below.
Status of Single Line Telephone/Multiline Terminal

STATUS OF
SINGLE LINE TEL.
STATUS OF
DIGITAL MULTILINE
TERMINAL
00
Normal operation of
blade
NOTE
Terminal is not connected

or Tip wire is grounded
01
Blade is not mounted/

initialized
NOTE
Terminal is connected
02
Short circuit is made on

the line
03
Ring wire is grounded
04
DLC blade is not mounted
05
Terminal failure
06
DLC blade down
07
08
INDICATION
NOTE:
Line failure detected
STATUS OF
IP STATION
When using the single line telephone, Terminal is not connected or Terminal is connected
cannot be displayed.
Software Test
01 - FF: See Station Status Information
of CMF5.)
1-17
Page 1-22. (This data is same as the status code
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

BATTERY RELEASE CONTROL

General Description
When the AC power is to be cut off intentionally (such as maintenance for the building), this feature can
disconnect the batteries from the PBX, using the PCPro or the CAT, and prevent an excessive discharge of
the battery.
System Diagram of Battery Release Control

PBX
C.O.
NETWORK
PWR
MODEM
PCPro
ENTERING COMMAND
BATTERY
MODEM
CPU
BATTERY CONNECTION RELAY
Service Conditions
The battery disconnection is canceled if the system is initialized (Power off/on or Reset).
1-18
NWA-033627-001 Rev.4.0
95ch1001.fm

Operating Procedure
(1)
To disconnect the battery

ST
COMMAND=
EC0 +
DE
EC0>
00 +
DE
EC0>00:1
For the first data, specify the desired unit (01 to 50)
whose battery is to be disconnected. To specify
Unit 01,02,03 and 04 collectively, enter 00.
When the first data is entered, the current status of the
specified unit is displayed. (1: Normal operation)
0 +
EXE
EC0>00:1 0
Enter 0 for the second data to disconnect.
OK
(2)
To reconnect the battery

ST
COMMAND=
EC0 +
DE
EC0>
00 +
DE
EC0>00:0
For the first data, specify the desired unit (01 to 50)
whose battery is to be reconnected. To specify
Unit 01,02,03 and 04 collectively, enter 00.
When the first data is entered, the current status of the
specified unit is displayed. (0: Battery released)
1 +
EXE
EC0>00:0 1
Enter 1 for the second data to reconnect.
OK
1-19
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

DIAGNOSTICS
DIAGNOSTICS
General Description
To assist maintenance personnel, this feature provides diagnostic capabilities such as fault code generation, device status information and alarm information recording, which can be accessed from the PCPro
or the CAT.
Service Conditions
(1)
The following station status information can be displayed on the PCPro or the CAT by direct
command:
(2)
Idle
Line Lockout
Dialing
Tone Trunk Connection (reorder tone, busy tone, service set tone, etc.)
Types of Connection (station-to-station, three-way calling, voice calling, holding, etc.)
Destination number (trunk number, register number)
Short circuit on line
The following trunk status information can be displayed on the PCPro or the CAT by direct
command:
Idle
Ringing in
Incoming queue to Attendant Console
Holding
In a tandem connection
Incoming queue to UCD
Dialing
Receiving dialed digits
1-20
NWA-033627-001 Rev.4.0
95ch1001.fm

DIAGNOSTICS
(3)
The following information is stored and can be displayed on the PCPro or the CAT using a memory
dump command in hexadecimal format:
(4)
Program address where an endless loop has occurred

Last reset time for main program
Last reset time for firmware program
The reason for reset (power-on, RESET key, endless loop, rotary switch, command from PCPro or
CAT)
The PBX has a built-in patrol program that monitors the status of all connected devices. Additionally,
when no response or an invalid response from a device is received, this program stores in memory
the slot number of that device. From the PCPro or the CAT, a maintenance person can read the slot
number of any device which does not respond to the main processor or provides an illegal status to
the main processor.
Operating Procedure
(1)
Station Status Information

Operation:
ST
COMMAND=
F50 +
DE
F50>
0 + X-XXXXXXXX +
(Station No.)
or
0 + FX-FXXXXXXXX
(Multiline Terminal No.)
DE
XXXX : XXXXXXXX XXXXXXXXX

*a
*b
*c *d *e *f *g
XXXXXXXXXXXXXXXXXXXXXXX
*h *i *j *k *l *m *n *o *p *q *r
*a : Station No.
*b : Designated Address
*c-*r: Status Code of the designated Address 0-15
For the meaning of status code, see Station Status Information on next page.
1-21
NWA-033627-001 Rev.4.0
95ch1001.fm

DIAGNOSTICS

STATUS
CODE
DESCRIPTION
01
Idle
02
In Line Lockout mode
10
Dialing to an ORT
11
Dialing to a trunk
12
Dialing to an ORT (After consultation hold a station)
13
Dialing to an ORT (After consultation hold a trunk)
14
Dialing to a trunk (After consultation hold a station)
15
Dialing to a trunk (After consultation hold a trunk)
1F
Dialing to an ORT (After consultation hold 3 party Conference

Trunk)
20
In Reorder Tone connection
21
In Reorder Tone connection (While consultation hold a Station)
22
In Reorder Tone connection (While consultation hold a trunk)
23
In Reorder Tone connection (While consultation hold 3 party

Conference Trunk)
2C
In Howler Tone connection
30
In Service Set tone connection
32
In Service Set tone connection (While consultation hold a trunk)
40
In Ringback Tone Connection
41
In Ringback Tone Connection for the second call

(After consultation hold a station)
42
In Ringback Tone connection for the second call

(After consultation hold a trunk)
50
Ringing (Call from a station)
51
Ringing (Call from an outside party)
55
Ringing (Automatic Wake Up Call)
REMARKS
1-22
NWA-033627-001 Rev.4.0
95ch1001.fm

DIAGNOSTICS

STATUS
CODE
DESCRIPTION
60
In Station to Station connection
62
In Three-Way Calling
65
Holding
66
Voice Call to a Multiline Terminal
67
Voice Call from a Station
71
In Station to Trunk connection
72
Three-Way Calling with a station and a trunk
C4
In a CAT mode (For Multiline Terminal)
C8
In a UCD Queue
C9
In a UCD Queue after holding a station
CA
In a UCD Queue after holding a trunk
NOTE:
REMARKS
The status codes not described in Station Status Information mean busy conditions.
1-23
NWA-033627-001 Rev.4.0
95ch1001.fm

DIAGNOSTICS
(2)
Trunk Status Information

Operation:
ST
COMMAND=
F50 +
DE
F50>
0 + DXXX +
(Trunk No.)
DE
DXXX : XXXXXXXX XXXXXXXXX

*a
*b
*c *d *e *f *g
XXXXXXXXXXXXXXXXXXXXXXX
*h *i *j *k *l *m *n *o *p *q *r
*a : Trunk No.
*b : Designated Address
*c-*r: Status Code of the designated Address 0-15
For the meaning of status code, see Trunk Status Information on next page.
1-24
NWA-033627-001 Rev.4.0
95ch1001.fm

DIAGNOSTICS
Trunk Status Information

STATUS
CODE
DESCRIPTION
01
Incoming queue to Attendant Console
03
Attendant Camp On
04
In a trunk to station connection
05
Dialing In (Tie Line)
06
In a tandem connection
08
Hold by Exclusive/Nonexclusive Hold
09
TAS in progress
0A
Incoming queue to UCD
0B
Three-Way Calling with a station and two trunks
0D
In Ringback Tone/Busy Tone connection (Tie Line)
0E
Waiting for release signal from distant office
10
Sending dialed digits (Outgoing Trunk of a tandem connection)
11
Three-Way Calling with two stations
14
Dialing In (Incoming Trunk of a trunk to trunk connection)
19
Ringing In (Trunk Direct Appearance on Multiline Terminal)
1A
Ringing In (Direct In Termination-DIT)
1B
Ringing In (Trunk Direct Appearance and DIT)
20
Holding by Call Hold
21
Holding by Call Park
2A
Incoming Queue to UCD (While sending message)
2B
Incoming Queue to UCD (After sending message)
FF
Idle
1-25
REMARKS
NWA-033627-001 Rev.4.0
95ch1001.fm
NOVEMBER/21/2008

DIAGNOSTICS
(3)
Alarm Information
Operation:
ST
COMMAND=
F53 +
DE
F53>
XXXX +
(Memory Dump Data)
DE
XXXX : XXXXXXXX XXXXXXXXX

*a
*b
*c
XXXXXXXXXXXXXXXXXXXXXX
*a: Memory Dump Data
*b: Designated Address
*c: See Alarm Information on next page.
1-26
NWA-033627-001 Rev.4.0
95ch1001.fm

DIAGNOSTICS
Alarm Information
MEMORY DUMP
DATA
0000
ALARM INFORMATION
REMARKS
Last Reset Time for Central Processing Unit (CPU)

YYYY MM DD HH MM SS
Second (00-59)
Minute (00-59)
Hour (00-23)
Date (01-31)
Month (01-12)
Year (2010-2999)
0001
Reason for System Reset

00: Power on
01: RESET on CPU blade
02: Endless Loop in H-Rank
03: Endless Loop in L-Rank
05: Stack Trouble
06: Address Trouble
07: COP Alarm
08: Abort
09: SENSE on CPU blade
0B: Command from PCPro/CAT
1-27
No fault
System fault
No fault
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

BATTERY REPLACEMENT
BATTERY REPLACEMENT
The interval of battery replacement depends on the ambient temperature.
The following caution label shows battery replacement interval and attached to the CPU chassis.
When you set up the battery for the first time, you must keep the record of the installation date and the
replacement date. And you should refer to the BATTERY REPLACEMENT TABLE for exchanging the
battery.
1-28
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

FAULT REPORT SCHEDULING

General Description
This feature provides the system to register pre-determined date for periodic maintenance in advance and
notify the information on the day by the Multiline Terminal function key lamp or external alarm display
panel.
PBX
Alarm Panel
MJ MN
Indicate the lamp

on the scheduled date
1
2
AB
GH
I
PQ
RS
JK
L
TU
DE
F
Fe
atu
re
OP
ER
CPU
Multiline Terminal
Register the time of

periodic maintenance
Service Conditions
(1)
The maximum of eight pre-determined dates for periodic maintenance, for example, battery check,
are registered by CM43 Y=2 in advance.
(2)
The notification for maintenance is indicated by the alarm lamp (MJ/MN) on the external alarm
panel, or the Multiline Terminal function key lamp. The Multiline Terminal function key steady
lights as MJ alarm, or flashes with 60 IPM as MN alarm. The MJ or MN alarm is selected by CMEA
Y=2 in advance.
(3)
The number of Multiline Terminal which indicates the periodic maintenance is two in a system.
(4)
The alarm indication can be cleared by CMEA Y=1 from CAT/PCPro.
1-29
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

(1)
To set a periodic maintenance reminder, do the following programming:
START
CM43
DESCRIPTION
DATA
Assign the date and time setting for periodic

maintenance.
Y=2
(1) 00-07: Periodic maintenance
(2) YYYY MM DD HH
YYYY: 2010-2099 (Year)
MM : 01-12 (Month)
DD : 01-31 (Date)
HH : 00-23 (Hour)
Assign the check item for periodic maintenance.
Y=3
(1) 00-07: Periodic maintenance
(2) 0 : Battery check
1-7: Check item No. 1-No. 7
CM51
Specify the Multiline Terminal for alarm

display, if required.
Y=16
(1) 01: Multiline Terminal No. 1
02: Multiline Terminal No. 2
(2) X-XXXXXXXX: My line number of
Multiline Terminal
CM90
Assign the alarm indication key to Multiline

Terminal function key, if required.
Y=00
(1) My Line No. + , +Key No.
(2) F5020: Alarm display
CMEA
Set the alarm kind for periodic maintenance.
Y=2
(1) 016
(2) 1: MN alarm
2: MJ alarm
END
(2)
To clear the alarm, do the following programming:
START
CMEA
DESCRIPTION
DATA
Clear external alarms.
Y=1
(1) 00 : Clear all of MJ/MN/-- alarms
(2) CCC: Alarm clear
END
1-30
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

Operating Procedure
To clear the alarm display
Operation:
ST
COMMAND=
EA1
DE
EA1>
XX
DE
EA1>XX:XX
CCC +
EXE
OK
XX: 00: Clear all of MJ/MN/- - alarms

01: Clear MJ alarms
02: Clear MN alarms
1-31
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

VoIP LOG COLLECTION
VoIP LOG COLLECTION

General Description
By collecting the fault logs or call logs and outputting them, you can know the causes when faults or error
occur in the SV8300.
(1)
Fault Log Collection

You can collect the fault logs and output them to the RS port of CPU by system data setting.
When faults occur in the system, you can specify the cause of faults.
Fault Log Collection

Printer
PCPro (PC)
1. Designation of fault logs collection of station B

3. Confirmation of output fault logs
. Reset causes, Reset time
SV8300
. Number of sending/received control packets

. Number of re-sending control packets
. Number of failed re-sending control packets
. Number of received error control packets
. Number of error control sequences
Router
Router
2. Fault logs sending
Network
Exit
Exit
N
E
E
C
Help
Help
MIC
MIC
Station A
Station B
1-32
NWA-033627-001 Rev.4.0
95ch1001.fm

VoIP LOG COLLECTION
(2)
Call Log Collection

You can collect the call logs and output them to the RS port of CPU by system data setting.
You can analyze communication conditions of the IP network.
Call Log Collection

Printer
PCPro (PC)
4. Confirmation of output call logs

. Communication Time
SV8300
. Number of sending/received packets

. Number of lost received packets
Router
3. Call logs sending
Router
3. Call logs sending
Network
Exit
Exit
E
C
Help
MIC
Station A
(3)
Help
1. Communication between Station A and Station B

2. Communication is completed
MIC
Station B
RTP monitoring
RTP monitoring is the feature that monitors whether an RTP is received during call, by using the SIP
with connected party. If RTP is not received a certain amount of time (about 10 seconds) from SIP
trunk to CPU blade, a fault notification is sent and the call is restored to normal state. By this feature,
you can avoid occupying channels if a disconnected message is not received because of a network
failure.
1-33
NWA-033627-001 Rev.4.0
95ch1001.fm
NOVEMBER/21/2008

VoIP LOG COLLECTION
Service Conditions
(1)
General conditions
Terminals/blades and available firmware versions that enable to collect fault logs/call logs are as
follows.
Available:
Terminals/Blades
Firmware Version Fault Log Call Log

Collection Collection
Terminals Dterm85 (Series i) (IP Adapter Type) Ver. 2.80 or later

Dterm85 (Series i) (IP Bundled Type) Ver. 2.80 or later
NOTE
Blades
NOTE:
DtermIP INASET (ITR-240G-1)

Soft Phone (DtermSP30 only)
VoIPDB
E0 2.80 or later
F Ver. 7.3.0.0 or later
Fault information store/display is not available for the following Dterm85 (Series i) (IP Bundled
Type). But it will be available when the new firmware is installed.
- ITR-8D-2 (BK/WH) TEL (Available when firmware of ITR-8D-3 (BK/WH) TEL is installed)
- ITR-16D-2 (BK/WH) TEL (Available when firmware of ITR-16D-3 (BK/WH) TEL is installed)
- ITR-8D-2A (BK/WH) TEL (Available when firmware of ITR-8D-3A (BK/WH) TEL is installed)
- ITR-16D-2A (BK/WH) TEL (Available when firmware of ITR-16D-3A (BK/WH) TEL is installed)
- ITR-8D-2U (BK/WH) TEL (Available when firmware of ITR-8D-3 (BK/WH) TEL is installed)
- ITR-16D-2U (BK/WH) TEL (Available when firmware of ITR-16D-3 (BK/WH) TEL is installed)
Collected fault logs and call logs can be output to a PC via the RS port (RS-232C) of the CPU
blade. To output the fault logs and call logs, communication software (Hyper Terminal, etc.) must
be installed in the PC (PCPro cannot be used while using the communication software).
1-34
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

VoIP LOG COLLECTION
NOTE:
To use Hyper Terminal, select File
Properties, and set emulation to VT100.
To collect the fault logs and call logs, be sure to set the CPU blade to on-line mode (set SENSE
switch to 0-4).
(2)
Conditions of fault log collection

By collecting fault logs, you can specify the reset causes and reset time.
By collecting fault logs, you can calculate the number of sending control packets, the number of
re-sending control packets, the number of failed re-sending control packets, the number of
received control packets, the received error control packets, and the error number of control
sequences.
The fault logs are collected by the following timing.
- When IP Stations login to the system, and when the VoIPDB is in online status
- When you set the system data for fault logs collection (CMEA Y=6>11) from PCPro/CAT
The output format of fault logs is as follows.
STN31100 08/04/30 12:48:19
DATA=1:RESET CAUSE
1=06440755 08/04/25 17:38:35
2=06440755 08/04/25 18:23:19
3=06440755 08/04/25 18:26:06
4=06440755 08/04/28 10:34:17
5=06440755 08/04/28 14:50:03
6=06440755 08/04/28 16:23:48
7=06440755 08/04/28 20:26:53
8=06440755 08/04/30 12:48:03
DATA=2:CONTROL PACKET COUNTER (PROTOCOL=2)
6
1=000016AD
2=000016AD
3=00000008
5=000016A6
6=00000C0A
7=00000000
4=00000001
DATA=3:REGISTRATION NG
1=FF-DRS0
2=FF-DRS0
3=FF-DRS0
4=FF-DRS1
5=FF-DRS1
6=FF-DRS1
7=FF-DRS2
8=FF-DRS2
TIME OUT
1-35
NWA-033627-001 Rev.4.0
95ch1001.fm

VoIP LOG COLLECTION

1. Station No./VoIPDB Channel No.
For station: STNX-XXXXXXXX (X-XXXXXXXX=STA. No. [1-8 digits])
For VoIPDB: VoIPXXYYY (XX=Unit No. 01-50, YYY=VoIPDB Channel No. 001-128)
NOTE 1
2. Fault Log Collection Time: XX/XX/XX XX:XX:XX (YY/MM/DD HH:MM:SS)
3. Log No.: 1-F
4. Cause for reset: AABBCCDD (AA=major division, BB/CC/DD=not used) NOTE 2
<Dterm85 (Series i) (IP Bundled Type/IP Adapter Type)/Soft Phone>
AA
MEANING
01
Self Reset: Before the registration/Before DRS01 (required a default setting)
02
Self Reset: During the registration/Before DRS03 (confirmed a reply of signal pass
setting)
03
Self Reset: After the registration/During a default setting
04
Self Reset: Call processing
05
Self Reset: During a partial default setting
06
Self Reset: Diagnostic command unreceived/KeepAlive NG
07
Soft Reset Receiving
08
DHCP Invalid
09
Configuration mode finish (Dterm85 (Series i) (IP Bundled Type) only)
0A
Reset statement from PROTIMS (Dterm85 (Series i) (IP Bundled Type) only)
<VoIPDB>
AA
00
MEANING
VoIPDB Reset
5. Reset Occurrence Time: XX/XX/XX XX:XX:XX (YY/MM/DD HH:MM:SS) NOTE 2

6. Protocol Type: PROTOCOL=1 (iLP-PM) /=2 (PROTIMS) /=4 (UDP/H.245)
1-36
NWA-033627-001 Rev.4.0
95ch1001.fm
NOVEMBER/21/2008

VoIP LOG COLLECTION
7. Number of sending/received control packets: XXXXXXXX NOTE 3

For PROTOCOL=1 (iLP-PM)
1: Total number of sending control packets
2: Number of re-sending control packets
3: NG number of re-sending control packets
4: Total number of received control packets
5: Total number of received error packets
6: Number of error sequences
7: Number of overlapped sequences
For PROTOCOL=2 (PROTIMS)
1: Total number of packets sending
2: Number of ACK request packets sending
3: Number of packets re-sending
4: Number of third retry occurrence of re-sending
5: Total number of packets received
6: Number of ACK request packets received
7: Total number of error packets received
For PROTOCOL=4 (UDP/H.245)
1 : Total number of sending packets
2 : Number of master mode UDP sending packets
3 : Number of master mode UDP re-sending packets
4 : Number of slave mode UDP sending packets
5 : Number of slave mode UDP re-sending packets
6 : Number of H.245 packets sending
7 : Total number of received packets
8 : Number of master mode UDP received packets
9 : Number of master mode UDP timeout packets
A: Number of master mode UDP NG packets
B: Number of slave mode UDP received packets
C: Number of slave mode UDP timeout packets
D: Number of slave mode UDP NG packets
E: Number of H.245 packets received
F : Number of H.245 timeout, etc.
1-37
NWA-033627-001 Rev.4.0
95ch1001.fm

VoIP LOG COLLECTION
8. Registration NG Cause: XX-DRSY (XX=error notifications from DRS, Y=DRS No.) NOTE 4
[Output arbitrarily per component]
<Error Notification from XX=DRS>
XX
MEANING
01
ID Unregistered (There are not ID data in PBX.)
02
Disabled (Use of the device which tried to be registered is restricted.)
03
Over Registration (The assigned ID/station number has been already registered.)
05
Disabled Number (The assigned fixed station number to be registered is disabled.)
07
Obtaining PH Failed (The device to be registered failed to obtain appropriate PH.)
09
Device Type Unrecognized (The registration chassis failed to recognize the device type.)
0F
Obtaining PH Failed Partly
10
Registration Overrun
11
Resource Disabled
12
Message Content Error
FF
DRS Connection Time Out
<Y=DRS number: 1 to 4>

1: Primary
2: Secondary
3: Tertiary
4: Fourth
9. Fault log reading timeout display NOTE 5

NOTE 1: For the fault logs collection after the VoIPDB reset execution, the least channel number of the
VoIPDB is displayed.
NOTE 2: The maximum eight records of reset cause and reset occurrence time can be displayed. Two
items are displayed per line, however this is displayed only when the data has been notified.
NOTE 3: The counting items and its meaning are different according to the protocol type. Four items are
displayed per line, however this is displayed only when the data has been notified.
NOTE 4: The maximum eight records of DRS No. and the cause of registration NG occurrence can be
displayed. Four items are displayed per line, however this is displayed only when the data has
been notified.
NOTE 5: This is displayed if the fault log cannot be read from each IP component. It also is displayed if
the IP component does not provide the fault log collection.
1-38
NWA-033627-001 Rev.4.0
95ch1001.fm

VoIP LOG COLLECTION
To collect multiple fault logs, at least a four-second interval is required for collecting each log. Also,
you can reserve up to eight logs collection (the ninth or more reserved log is invalid).
Since the recorded reset time of fault logs depends on the terminal clock to collect logs, it may differ
from the PBX internal clock.
(3)
Conditions for call log collection

For the call logs collection feature, you can calculate the communication time, number of sending
packets, number of received packets, and number of lost received packets.
The communication time that logs are collected is the start time and end time of the communication. When the internal clock of system is changed during the communication, it may not match
the actual time.
If a call is forwarded during the communication, a new log is collected as another communication
with the forwarded destination.
The number of sending packets of call log is the number of voice packets sent from the terminal.
The number of received packets of voice log is the number of voice packets received from the
terminal of the connected party.
The number of lost received packets of call log is the number in which the total number of received
packets minus the number of voice packets that should be received in the normal communication.
When you cannot output the call logs to the RS port of the CPU due to disconnection, etc., the CPU
blade can be collected up to 256 logs. If the logs exceed 256 logs, you can specify whether to
overwrite them or not by system data setting (CMEA Y=6>02).
Call logs are collected when the communication is completed. Logs are not collected when a
connection fails.
Call logs collected in the CPU blade are deleted when the system is reset.
The output format of call logs is as follows.
08/04/28 20:37:51 08/04/28 20:37:52 STN31100 VoIP01004 192.168.30.1
00000007 00000003 00000000
08/04/28 20:37:52 08/04/28 20:37:52 VoIP01004 STN31100 192.168.30.100 00000010 00000003 00000000

1: Communication start time: XX/XX/XX XX:XX:XX (YY/MM/DD HH:MM:SS)
2: Communication end time: XX/XX/XX XX:XX:XX (YY/MM/DD HH:MM:SS)
1-39
NWA-033627-001 Rev.4.0
95ch1001.fm
NOVEMBER/21/2008

VoIP LOG COLLECTION
3: Own terminal/Blade type

4: Connected party terminal/Blade type
For connected party: M_XXXXXXXX (XXXXXXXX=Logical Collection Position No.
[8 digits])
NOTE: SIP is output as connected party.
5: IP address of connected party: XXX.XXX.XXX.XXX
6: Number of sent RTP packets: XXXXXXXX (8-digits fixed hexadecimal value)
7: Number of received RTP packets: XXXXXXXX (8-digits fixed hexadecimal value)
8: Number of received RTP packets lost: XXXXXXXX (8-digits fixed hexadecimal value)
Conditions for call log collection of SIP trunk are as follows.
(a) Call log of SIP trunk is notified from SIP trunk to CPU blade when sending/receiving of RTP
packet are completed.
(b) For the number of RTP packets sent in call log, the number of transmissions of SIP trunk is
saved.
(c) For the number of RTP packets received in call log, the number of receptions of renewable
packets is saved.
Conditions for call log collection of T.38 FAX are as follows.
(a) The number of packets sent, the number of packets received, and the number of receiving
packets lost in T.38 FAX communication can be displayed by using the existing call log
collection feature.
(b) Each number of packets in T.38 FAX communication is displayed in the order of the
description of (a) following the number of packets for voice communication.
1-40
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

VoIP LOG COLLECTION
(4)
Conditions for RTP monitoring

If the SIP trunk does not receive RTP for 10 seconds after establishing the path, the fault
information (fault kind 043) is registered and the path is released.
The fault information (fault kind 043) is registered whenever the path is released by RTP monitoring.
The RTP monitoring starts when one packet is received from the originating office after a path is
established. Even during ringing, RTP monitoring functions when sending/receiving RTP.
When the path is released by RTP monitoring, the SIP call disconnect message is sent to the
originating office.
1-41
NWA-033627-001 Rev.4.0
95ch1001.fm
APRIL/16/2010

VoIP LOG COLLECTION
(1)
To execute the fault logs/call logs collection, do the following programming.

DESCRIPTION
START
CM0B
DATA
Provide the call log collection with the

VoIPDB.
NOTE:
When changing this data for

VoIPDB accommodated in a remote
unit, execute the system data copy
by CMEC Y=8 to the remote unit.
Y=2XX (VOIP Port [2] + Unit No. [01-50])

(1) 90
(2) 0 : To provide
1 : Not provided
Provide the fault log collection with the

VoIPDB.
Y=2XX (VOIP Port [2] + Unit No. [01-50])

(1) 91
(2) 0 : Not provided
1 : To provide
CM12
Assign Service Restriction Class C to the

required stations.
Y=07
(1) X-XXXXXXXX: IP Station No.
(2) 00-15 : Service Restriction Class C
CM15
Allow call log collection in Service Restriction

Class C assigned by CM12 Y=07.
Y=194
(1) 00-15: Service Restriction Class C assigned
by CM12 Y=07
(2) 0 : Allow
1 : Restricted
NOTE:
When changing this data for

VoIPDB accommodated in a remote
unit, execute the system data copy
by CMEC Y=8 to the remote unit.
Allow fault log collection in Service Restriction Class C assigned by CM12 Y=07.
Y=195
(1) 00-15: Service Restriction Class C assigned
by CM12 Y=07
(2) 0 : Restricted
1 : Allow
1-42
NWA-033627-001 Rev.4.0
95ch1001.fm

VoIP LOG COLLECTION
DESCRIPTION
A
CMEA
Specify the output destination for the fault

logs/call logs.
NOTE:
CM40
DATA
Set the output port for fault logs/call

logs by CM40 Y=00.
Y=6
(1) 00: Output destination of logs
(2) 2 : RS port of CPU
3 : Not output
Specify the collection method of fault logs/call

logs.
Y=6
(1) 02: Collection method of logs
(2) 0 : Not overwritten
1 : Overwrite
Specify whether fault logs are collected when

the IP Stations login to the system or the
VoIPDB is in online status.
Y=6
(1) 10: Fault log collection
(2) 0 : To collect
1 : Not collected
Specify the RS port to collect VoIP log.
Y=00
(1) 0: Unit01 Port1
1: Unit01 Port2
(2) 08
: VoIP log collection
NONE : No data
Specify the data length for the RS port.
Y=01
(1) 0: Unit01 Port1
1: Unit01 Port2
(2) 0 : 7 bit
1 : 8 bit
NOTE:
When using CPU RS-232C port for

PCPro, set the default.
Specify the RS port to make effective the

parity check.
NOTE:

Specify the kind of parity for the RS port.

NOTE:

Y=02
(1) 0: Unit01 Port1
1: Unit01 Port2
(2) 0 : Effective
1 : Ineffective
Y=03
(1) 0: Unit01 Port1
1: Unit01 Port2
(2) 0 : Odd parity
1 : Even parity
1-43
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

VoIP LOG COLLECTION
DESCRIPTION
B
CM40
DATA
Specify the stop bit for the RS port.

NOTE:

Specify the DTR signal sent to terminal for the

RS port.
NOTE:

Specify the RTS signal sent to terminal for the

RS port.
NOTE:

Specify the data speed of the RS port.

NOTE:
When you communicate with CPU

built-in modem, be sure to set the
data speed of RS1 port as 4800 bps
or more (1200 bps and 2400 bps are
not available).
Y=04
(1) 0: Unit01 Port1
1: Unit01 Port2
(2) 0 : 1-Stop bit
1 : 2-Stop bit
Y=05
(1) 0: Unit01 Port1
1: Unit01 Port2
(2) 0 : Low
1 : High
Y=06
(1) 0: Unit01 Port1
1: Unit01 Port2
(2) 0 : Low
1 : High
Y=08
(1) 0: Unit01 Port1
1: Unit01 Port2
(2) 1
: 1200 bps
2
: 2400 bps
3
: 4800 bps
4
: 9600 bps
5
: 19200 bps
NONE : 9600 bps
END
(2)
To confirm whether the call logs is collected in the CPU or to clear logs, do the following
programming.
START
CMEA
DESCRIPTION
DATA
Display the call logs that are collected in the

CPU or clear the logs.
Y=6
(1) 01: Display of call log collection/log clear
(2) 0
: Logs are not collected
1
: Logs are collected
CCC: Log clear
END
1-44
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

VoIP LOG COLLECTION
(3)
To collect the fault logs manually, do the following programming.
START
DESCRIPTION
DATA
CMEA
Specify the terminals/VoIPDB to collect fault

logs.
Y=6
(1) 11: Specification of fault log collection terminal/VoIPDB
(2) X-XXXXXXXX: IP Station No.
DD XX ZZZ:
XX : 01-50 : Unit No.
ZZZ:001-128: VoIPDB Channel No.
NOTE:
When reading this data, second data

1 is displayed normally.
END
1-45
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

QoS DISPLAY ON IP MULTILINE TERMINAL

General Description
This feature allows IP Multiline Terminal to display the Number of lost packets, CODEC type, and Payload size of IP Multiline Terminal communication on the LCD by pressing the function key. This feature
also allows SIP Multiline Terminal to display the Number of lost packets, CODEC type, and Payload size
of SIP Multiline Terminal communication on the LCD by pressing the HELP key continuously.
Display Example:
When QoS Display Key is pressed while an IP Multiline Terminal communicates or HELP Key is pressed
continuously while a SIP Multiline Terminal communicates with the station number 3000, the LCD of IP
Multiline Terminal or SIP Multiline Terminal displays as follows:
Number of Lost Packets
34
G711u
1.Lost Packet:
2.Codec:
Exit
Down
Up
Payload Size
Exit
Help
G711u
40ms
2.Codec:
3.Payload
Press Down
Exit
Up
Down
Exit
Help
Press Up
CODEC Type
You can stop the QoS display with pressing Exit key. Press not the fixed EXIT button on far left, but the
Soft Key of Exit.
1:26
Exit
S&R
PM
MON
PICK
28
MAR
Station Number
3000
2005
>>>>
Help
You can easily diagnose the communication fault of IP Multiline Terminal or SIP Multiline Terminal by
this feature.
1-46
NWA-033627-001 Rev.4.0
95ch1001.fm
NOVEMBER/21/2008

Service Conditions
(1)
Number of lost packets, CODEC type, and Payload size are displayed with pressing the Function key
that has been set during a communication.
(2)
The displayed QoS information on the LCD is updated every 5 seconds.
(3)
All information sent from the PBX is not displayed while the QoS information is displayed on the
LCD.
(4)
To stop the display of QoS information, press Soft key of Exit. If you do not that, the QoS
information will keep being displayed.
(5)
This feature is available for the IP Multiline Terminal version 2.81 or later.
(6)
When using this feature for SIP Multiline Terminal, the data assignment of the QoS Display key
(second data of CM90 Y=00 is set to F1058) is not necessary. QoS information is displayed with
pressing the HELP key continuously.
START
DESCRIPTION
CM90
Assign the QoS Display key to the IP Multiline

Terminal.
NOTE:
DATA
This data is not activated even if this

data is assigned to the DT700 Series
Feature Keys.
Y=00
(1) My Line No. + , + Key No.
(2) F1058: QoS Display on IP Multiline
Terminal
END
1-47
NWA-033627-001 Rev.4.0
95ch1001.fm
NOVEMBER/21/2008

STATION SERVICE STATUS DISPLAY

General Description
This feature enables to readout the setting status of the service for each station.
Service Conditions
(1)
The services whose setting status can be readout by this feature are the features that are set to single
line telephone, Multiline Terminal, PS, virtual station and built-in modem. The features that are set
to DESKCON and ISDN telephone are not supported.
(2)
Station numbers entered by the setting status readout command (CME4 Y=00, 01) are the station
number set to single line telephone, Multiline Terminal, virtual station, virtual station for PS, and
built-in modem. The station numbers for ISDN telephone cannot be entered ([DATA ERROR] is
displayed if entered).
(3)
The terminal connection status and the line status cannot be readout in offline. For the other features,
the status can be readout regardless of online or offline.
(4)
For the line status, when Sub Line is accommodated to Multiline Terminal and My Line number is
input to the first data, the status Line is busy (1) is displayed when incoming/outgoing calls to My
Line, and the status Line is idle (0) is displayed when incoming/outgoing calls to Sub Line.
(5)
For Day/Night mode change, Day mode (D)/Night mode (N)/Mode A (A)/Mode B (B) are displayed
even if two kinds of modes (Day mode/Night mode) are set by CM65 Y=29.
1-48
NWA-033627-001 Rev.4.0
95ch1001.fm
NOVEMBER/21/2008

The following explains the procedures for command operation from PCPro/CAT.
CME4 Y=00 (Readout service status A for each station)
ST
COMMAND=
E400 +
DE
E400>
X~XXXXXXXX +
(Station Number)
DE
X~XXXXXXXX : a b c d e f g h
Station Number
a : Terminal connection status
b : Make Busy
c : Line status
d : Call Forwarding-All Calls
e : Call Forwarding-Busy Line
f : Call Forwarding-No Answer
g : Logout/Call Forwarding-PS out of cell (zone)
h : Do Not Disturb
For details of abcdefgh, refer to Table A
(Readout Service Status A for Each Station).
Page 1-50
CME4 Y=01 (Readout service status B for each station)
ST
COMMAND=
E401 +
DE
E401>
X~XXXXXXXX +
(Station Number)
DE
X~XXXXXXXX : i j k l m n o
Station Number
i : Mobility access (Station Access/Call Forwarding)
j : Day/Night mode change
k : Number Sharing
l : Split Call Forwarding-All Calls
m : Split Call Forwarding-Busy Line/No Answer
n : ACD/UCD Busy Out
o : Outgoing Call Restriction
For details of ijklmno, refer to Table B
(Readout Service Status B for Each Station).
Page 1-51
1-49
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

Table A (Readout Service Status A for Each Station)

DISPLAY
CONTENT
DISPLAYED
SERVICES
a: Terminal connection sta- 0
tus
1
MEANING
Terminal is connected (for Multiline Terminal only)
Terminal is not connected (for Multiline Terminal only)
Readout Error
_ (Underscore)
Off-line status or Terminal is not available
Make Busy is not set
Make Busy is set
Readout Error
Line is idle
Line is busy
Readout Error
_ (Underscore)
Off-line
d: Call Forwarding-All
Calls
Call Forwarding-All Calls is not set
Call Forwarding-All Calls is set
e: Call Forwarding-Busy
Line
Call Forwarding-Busy Line is not set
Call Forwarding-Busy Line is set
f : Call Forwarding-No
Answer
Call Forwarding-No Answer is not set
Call Forwarding-No Answer is set
b: Make Busy
c: Line status
g: Logout/Call Forward0
ing-PS out of cell (zone) 1
Logout/Call Forwarding-PS out of cell (zone) is not set
h: Do Not Disturb
Do Not Disturb for each station is not set
Do Not Disturb for each station is set
Readout Error
Logout/Call Forwarding-PS out of cell (zone) is set
1-50
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

Table B (Readout Service Status B for Each Station)

DISPLAY
CONTENT
DISPLAYED
FEATURES
i : Mobility access (Station 0

Access/Call Forward1
ing)
_ (Underscore)
j : Day/Night mode
change
k : Number Sharing
l : Split Call ForwardingAll Calls
m: Split Call ForwardingBusy Line/No Answer
n: ACD/UCD Busy Out
o: Outgoing Call Restriction
MEANING
Mobility access mode is not set
Mobility access mode is set
Mobility access mode is not available
Day mode
Night mode
Mode A
Mode B
Main station number/Sub station number not for Number Sharing
Main station number for Number Sharing
Readout Error
_ (Underscore)
No connection by CM12 Y=19
Split Call Forwarding-All Calls is not set
Split Call Forwarding-All Calls is set
Readout Error
Split Call Forwarding-Busy Line/No Answer is not set
Split Call Forwarding-Busy Line/No Answer is set
Readout Error
ACD/UCD Busy Out is not set
ACD/UCD Busy Out is set
Readout Error
_ (Underscore)
ACD/UCD Busy Out is not registered
Outgoing Call Restriction for each station is not set
Only Outgoing Call Restriction for each station is set
Readout Error
1-51
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

PING COMMAND
PING COMMAND
General Description
By executing a ping command from the PCPro or the Customer Administration Terminal (CAT), you can
send a ping request to IP Station from the PBX. This enables you to confirm whether the IP terminal is
correctly connected/set or not.
PBX
1 Executing a ping command
PCPro (PC)
(CMFA Y=2001)
2 Display of a ping request

transmission result
LAN
Exit
E
C
Help
MIC
IP Station
Service Conditions
(1)
By executing a ping command (CMFA Y=2001 [01: Unit No.]), only one ping request is sent from
the PBX to the terminal connected to the PBX with a LAN. And you confirm whether a reply to the
ping request is received from the terminal or not.
NOTE:
You can send a ping request only once by executing a ping command once. So you can not set
the ping request parameter such as number of times that the ping request is sent by executing a
ping command.
(2)
The LAN interface (Maintenance Port and VOIP Port) is automatically selected if the IP address of
the destination for the ping command assigned.
(3)
The time limit for replying to a ping request in this feature is fixed to about 2-4 seconds. If the time
limit is exceeded, REQUEST TIMEOUT is displayed.
1-52
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

PING COMMAND
(4)
You can not execute the ping command from multiple PCPro/CAT terminals at once. If you do that,
WAIT, BUSY NOW is displayed.
(5)
Even if a LAN port on the CPU blade is being used for PCPro/OAI or any other terminals, you can
execute the ping command.
(6)
The following key operations are effective when the reply message resulting by executing the ping
command is displayed.
DE (space key): To send again a ping request to the same IP address as the last one.
- (hyphen key) : To send a ping request to the IP address with 1 subtracted from the last one.
Example: The ping request is sent to 192.168.1.2 if you press DE (space key) after sending it
to 192.168.1.3.
S (return key) : To send a ping request to the IP address with 1 added to the last one.
Example: The ping request is sent to 192.168.1.3 if you press S (return key) after sending it to
192.168.1.2.
NOTE:
A LAN port on the CPU blade becomes occupied if you execute a ping command while DE
(space key) is pressed.
(7)
When LAN feature is not available due to a system data is not assigned or other reason,
HARDWARE ERROR is displayed.
(8)
The reply message resulting by executing the ping command is directly displayed in ICMP TYPE.
And OK/ ERROR displayed in PCPro is not displayed. The reply message is as follows.
Example 1 <The reply message resulting by executing the ping command>:
COMMAND=FA2001
FA2001>192.168.1.2
192.168.1.2: 0
ping OK (ICMP TYPE=0 Reply)
Example 2 <The reply message resulting by executing the ping command>:
COMMAND=FA2001
FA2001>192.168.1.2
192.168.1.2: 3
ping NG (ICMP TYPE=3 Host unreachable)
1-53
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

PING COMMAND
(9)
ICMP TYPE used in this feature is as follows.
List of ICMP TYPE

ICMP
TYPE
CLASSIFICATION
GENERAL DESCRIPTION
MEANING
Reply
Reply to the echo request by executing the ping command (echo

reply)
Ping reply (ping OK)
Reply
(error)
Reply message resulting by the ping

request has not arrived at a destination.
ICMP TYPE=3 is replied if the ping
request is rejected by firewall protection. And no reply is received if
the ping request cannot arrive at a
destination or ping request is disregarded by firewall protection.
11
Reply
(error)
Reply message resulting by time

excess.
The message of packet discard
caused by TTL (Time To Live)
becomes 0 during transit, or the
message of time excess caused by
TTL becomes 0 during waiting for
lost fragments for re-assembly.
TTL becomes 0 during transit

TTL becomes 0 during waiting for
lost fragments for re-assembly.
Network unreachable
Host unreachable
Protocol unusable
Port unusable
Fragmentation failed
Source routing failed
Destination network unknown
Destination host unknown
Source host isolated from network
Rejection of destination network
Rejection of destination host
Network unreachable for TOS
NOTE 2
Communication administratively
prohibited by filtering
Host precedence violation
Precedence cutoff in effect
1-54
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

PING COMMAND
List of ICMP TYPE

ICMP
TYPE
12
CLASSIFICATION
Reply
(error)
GENERAL DESCRIPTION
Reply message resulting by the IP
header being abnormal or a required
option is not effective.
MEANING
IP header abnormal
Required options are unknown.
Receiving ICMP TYPE=0 (ping reply) from the destination terminal means that the terminal is
correctly connected/set.
Receiving ICMP TYPE=3/11/12 (reply [error]) from the destination terminal means that the terminal is not correctly connected/set.
NOTE 1: If ICMP TYPE not listed above is received, HARDWARE ERROR is displayed.
NOTE 2: TOS (Type of Service) is present in IP header, and represents QoS (Quality of Service). Precedence/delay/throughput/reliability that determine quality are contained within TOS.
DESCRIPTION
START
CMFA
DATA
Execute a ping command.
NOTE:
Y=2001 (20 + Unit No. 01)

(1) XXX.XXX.XXX.XXX:
1.0.0.0-255.255.255.255:
IP address of the destination for the ping
command (7-15 digits)
(2) Reply for the ping command (Display
only):
XXX.XXX.XXX.XXX: Z:
XXX.XXX.XXX.XXX=
Sending destination IP address
Z=ICMP TYPE
You can not assign the following data to IP addresses of the destination for the ping command.
Top of the IP address is 0 (0.xxx.xxx.xxx)
END
1-55
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009

PING COMMAND
Operating Procedure
By executing the command (CMFA Y=20XX) from PCPro or CAT, you assign the IP address of the terminal you want to send a ping request to. Then you confirm an reply message resulting by executing the
ping command.
Example: Assign 192.168.1.3 to IP address.
ST
FA2001
DE
192.168.1.2
DE
The following key operations are effective when the reply message resulting by executing the ping command is displayed.
DE (space key): To send again a ping request to the same IP address as the last one.
- (hyphen key) : To send a ping request to the IP address with 1 subtracted from the last one.
Example: The ping request is sent to 192.168.1.2 if you press DE (space key) after sending it to
192.168.1.3.
S (return key) : To send a ping request to the IP address with 1 added to the last one.
Example: The ping request is sent to 192.168.1.3 if you press S (return key) after sending it to
192.168.1.2.
1-56
NWA-033627-001 Rev.4.0
95ch1001.fm
JULY/17/2009
UNIVERGE SV8300
TROUBLESHOOTING
Chapter
This chapter describes the precautions before troubleshooting, and

the troubleshooting procedure.
2-1
NWA-033627-001 Rev.4.0
95ch2001.fm
Chapter 2 TROUBLESHOOTING
PRECAUTIONS
PRECAUTIONS
Grounding Requirements
The system grounding must have a specific ground resistance and AC noise level, and is to be connected
to a predetermined terminal in the PBX. Standard grounding requirements are as shown below:
Communication grounding : Less than 10
Protective ground for Chassis: Less than 10
NOTE:
The AC ripple on these various grounds should be less than 0.5 Vp-p.
CAUTION
Grounding circuit continuity is vital for safe operation of telecommunication equipment.
Never operate this equipment with the grounding conductor disconnected.
The following specific requirements apply to ground wiring.
Install an equipment-grounding conductor that is at least as large as the ungrounded branch-supply
conductors as part of the circuit that supplies the PBX. Bare, covered, or insulated grounding
conductors are acceptable. Individually covered or insulated equipment grounding conductors shall
have a continuous outer finish that is either green, or green with one or more yellow stripes. The
equipment grounding connector is to be connected to ground at the service equipment.
The attachment-plug receptacles near the PBX are all to be of a grounding type, and the equipment
grounding conductors serving these receptacles are to be connected to earth ground at the service
equipment.
2-2
NWA-033627-001 Rev.4.0
95ch2001.fm
PRECAUTIONS
Static Electricity Guard

You must wear a grounded wrist strap to protect blades from static electricity.

WHEN PLUGGING/UNPLUGGING A BLADE
FRAME GROUND SCREW
SYSTEM
WRIST STRAP
WHEN HOLDING A BLADE

NEVER TOUCH THE COMPONENTS OR
SOLDERED SURFACE WITH BARE HANDS.
BLADE FRONT
2-3
NWA-033627-001 Rev.4.0
95ch2001.fm
PRECAUTIONS

WHEN MAKING A SWITCH SETTING ON A BLADE
BLADE
WEAR A WRIST STRAP AND PERFORM

THE WORK ON A GROUNDED
CONDUCTIVE WORK SURFACE.
WHEN CARRYING A BLADE
BLADE
CONDUCTIVE
POLYETHYLENE
BAG
WHEN CARRYING A BLADE AROUND,
KEEP THE BLADE IN A CONDUCTIVE
POLYETHYLENE BAG.
The mark shown below is attached to the sheet for the work in which blades are handled. When engaging in such work, the installer must be careful not to cause damage by static electricity.
ATTENTION
Contents
Static Sensitive
Handling
Precautions Required
2-4
NWA-033627-001 Rev.4.0
95ch2001.fm
PRECAUTIONS
CAUTION
1. You must hold the edge of a blade when plugging or unplugging the blade.
If you touch another area, you may be exposed to hazardous voltages.
SYSTEM
NEVER TOUCH THE COMPONENTS

OR SOLDERED SURFACE WITH BARE
HANDS.
BLADE FRONT
2. You must wait for 30 seconds before plugging the blade again when unplugging the blade
while the operating power is being supplied.
2-5
NWA-033627-001 Rev.4.0
95ch2001.fm
PRECAUTIONS
Turning Power ON
CAUTION
Do not turn the POWER switch of the Unit to OFF when the system is operating.
(1)
Turn the POWER switches of all the Units to ON.
Turning Power OFF

(1)
Turn the POWER switches of all the Units to OFF.
2-6
NWA-033627-001 Rev.4.0
95ch2001.fm
OUTLINE OF TROUBLESHOOTING
OUTLINE OF TROUBLESHOOTING
The outline of the recommended troubleshooting procedure is shown below:
Outline of Troubleshooting
START
Fault Detection Method (See

Page 2-8)
(1) Alarm Indication on PCPro, Alarm Display
Panel
(2) LED Indication on Blades
(3) Complaint from station user or operator
FAULT DETECTION
FAULT DIAGNOSIS
AND
TROUBLESHOOTING
Fault Diagnosis and Troubleshooting Method

(1) Display on PCPro/CAT (See
Page 2-12)
Fault Message
Station Line Status Display
(2) Troubleshooting by LED Indication
on Blades
(See
Page 2-33)
(3) Troubleshooting by Contents of Complaint
(See
Page 2-37)
END
2-7
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009
FAULT DETECTION
FAULT DETECTION
This section describes the way in which alarm indications are given. If a fault has occurred in the system,
you can detect the fault via the routes shown in Alarm Indication Routes.
Alarm Indication Routes

ALARM DISPLAY PANEL
PWR
MJ
MN
MJ/MN ALARM
INDICATION
MAINTENANCE
PERSONNEL
LED INDICATION
BLADE
COMPLAINT FROM
STATION USER OR OPERATOR
(1)
Fault Detection by Alarm Indication

When a fault has occurred in the system, you can detect the fault by a Major (MJ) alarm or Minor
(MN) alarm indicated PCPro or external Alarm Display Panel.
(2)
Fault Detection by LED Indication on Blades

When a fault has occurred in the system, you can also detect the fault by LED indication on blades.
LED Indication on Blades shows the alarm indication LEDs on each blade.
Page 2-9
For details of LED indication on blades, refer to the System Hardware Manual.
(3)
Fault Detection by Complaint from Station User or Operator

When you receive a complaint about a problem from a station user or an operator, you should collect
as much information on the problem as possible, and then troubleshoot the problem according to the
procedure shown in Troubleshooting by Contents of Complaint of this chapter.
Page 2-37
2-8
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009
FAULT DETECTION
LED Indication on Blades

LED Indications on Blades
KIND OF BLADE BLADE NAME
Control Blades
CC-CP00/CP31
(CPU)
CC-CP01 (CPU)
LED
NAME
COLOR
RUN
(LED1)
SYSD
S1
Blue
Red
Green
S2
ALM
LINK
100M
RUN
Green
Red
Green
Green
Blue
S1
Green
S2
Green
Orange
ALM
Red
Orange
INDICATIONS
NORMAL
ABNORMAL
120 IPM Flash/

Flash slowly
OFF
240 IPM Flash/
60 IPM Flash/
Flash specially
(ON: OFF=7: 3)/
Steady ON or
OFF
Steady ON/Flash
OFF
Steady ON/Flash
Steady ON
120 IPM Flash/
60 IPM Flash
240 IPM Flash/
60 IPM Flash/
Special Flash
(ON: OFF=7: 3)/
OFF
Steady ON/Flash
Steady ON/
120 IPM Flash
OFF
OFF
OFF
Flash
120 IPM Flash
OFF
Steady ON/Flash
OFF
OFF
OFF
120 IPM Flash
OFF
OFF/
Special Flash
(ON: OFF=1: 9)
Steady ON/Flash
Steady ON
2-9
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
FAULT DETECTION

INDICATIONS
LED
NAME
COLOR
LED1
LED2
LED3
LED1
LIVE LED
Green
Green
Green
Green
Green
Steady ON
Steady ON
Steady ON
Steady ON
Flash (120 IPM)
BUSY LED
Red
Steady ON/OFF
LIVE LED
Green
Flash (120 IPM)
BUSY LED
Red
Steady ON/OFF
CD-4DIOPA
LIVE LED
(LLC/DIOP/LDT)
BUSY LED
Green
Flash (120 IPM)
Red
Steady ON/OFF
CD-2BRIA (BRT) LIVE LED
Green
Flash (120 IPM)
BUSY LED
Red
Steady ON/OFF
LIVE LED
Green
Flash (120 IPM)
BUSY LED
Red
Steady ON/OFF

Control Blades
PZ-BS10 (BUS0)
Access Blades
PZ-BS11 (BUS1)
CD-4COTA/
4COTB (COT)
CD-4ODTA
(ODT)
CD-PRTA
(PRT/DTI/QSIG)
NORMAL
ABNORMAL
OFF
OFF
OFF
OFF
Steady ON/
Flash (1S)/OFF
Steady ON/
Flash (100 ms)/
Flash (1s)/OFF
Steady ON/
Flash (1S)/OFF
Steady ON/
Flash (100 ms)/
Flash (1s)/OFF
Steady ON/
Flash (1S)/OFF
Steady ON/
Flash (100 ms)/
Flash (1s)/OFF
Steady ON/
Flash (1S)/OFF
Steady ON/
Flash (100 ms)/
Flash (1s)/OFF
Steady ON/
Flash (1S)/OFF
Steady ON/
Flash (100 ms)/
Flash (1s)/OFF
2-10
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
FAULT DETECTION

Access Blades
CD-CCTA (CCT)
CD-4LCA/
8LCA (LC)
CD-8DLCA/
16DLCA (DLC)
CD-4CSIB (CSI)
CD-4CSIB-A
(CSI)
PZ-64IPLA/
128IPLA
(VoIPDB)
LED
NAME
COLOR
LIVE LED
Green
BUSY LED
Red
LIVE LED
Green
BUSY LED
Red
LIVE LED
Green
BUSY LED
Red
LIVE LED
Green
BUSY LED
Red
LIVE LED
Green
BUSY LED
Red
L1
L2
L3
L4
Red
Red
Orange
Green
2-11
INDICATIONS
NORMAL
ABNORMAL
Flash (120 IPM) Steady ON/

Flash (1S)/OFF
Steady ON/OFF Steady ON/
Flash (100 ms)/
Flash (1s)/OFF
Flash (1S)/OFF
Flash (100 ms)/
Flash (1s)/OFF
Flash (1S)/OFF
Flash (100 ms)/
Flash (1s)/OFF
Flash (1S)/OFF
Flash (100 ms)/
Flash (1s)/OFF
Flash (1S)/OFF
Flash (100 ms)/
Flash (1s)/OFF
ON
OFF
ON
OFF
ON
OFF
ON
Flash
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
FAULT INFORMATION DISPLAY

Display on PCPro/CAT
When the MJ/MN alarm has been indicated, you can diagnose the contents of the fault by the Fault Message and the Station Line Status Display features which are displayed on the PCPro or the CAT, and restore
the fault.
Fault Message
The fault information is displayed on PCPro/CAT. An example of fault information display is provided
below:
CAT mode
ST
COMMAND=
EA0 + DE
EA0>_
EA0>0: XXXXXXXXXXXXXXXX-
Fault Information 0
Fault Information 1
Fault Information 2
Fault Information 3
Fault Information 4
Fault Information 5
Fault Information 6
Fault Information 7
Fault Information 8
Fault Information 9
+ DE
(1)
(2)
EA0>0: XXXXXXXXXXXXXXXXFor details of (1), (2), see next page.
2-12
NWA-033627-001 Rev.4.0
95ch2001.fm
EXPLANATION OF SCREEN INFORMATION

1: Date and Time of Fault Occurrence and Restoration
2: Fault Kind No./Restoration Kind No.
FAULT
KIND NUMBER
FAULT CONTENT
001
System reset
012
016
It is a day periodic maintenance
017
Activation Code error occurred during the License Activation

(Center Activation)
021
ISDN D-channel link connection failure
022
CCIS link connection failure
025
Number of lockout stations was more than predetermined number
026
DLC blade down
028
SMDR output buffer (SRAM) exceeded 80 %

029
SMDR output buffer (SRAM) overflow

02B
02C
LAN application fault occurred
040
Traffic of IP network exceeded limit bandwidth
041
Traffic of IP network exceeded warning bandwidth
042
Communication error occurrence between Main Unit and Remote Unit
043
SIP trunk failure
048
CPU Program Upgrade
04A
Long call duration information
061
VoIPDB Startup Process is failure

100
Power failure
102
DTI line failure

2-13
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
FAULT
KIND NUMBER
FAULT CONTENT
104
SV8300 Blade down
106
SV8300 Blade reset with CME03
107
Lack of option value
108
109
Auto Blade Reset by TDM-Blade Lockup

10A
CPU SRAM failure

10B
Restricted blade
10C
Firmware version un-matching between CPU blade and Line/Trunk blade

[8300R3 software required
10D
Lack of Highway Channel for data communication

10E
Illegal use of CPU blade for Remote Unit only

110
Communication error occurrence between active CPU and stand by CPU

112
Expansion Chassis (2U) failure

114
Automatic module reset due to Expansion Chassis (2U) lockup

115
Automatic system reset due to Expansion Chassis (2U) lockup

116
All blades lockup in Expansion Chassis (2U)

2-14
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
RESTORATION
KIND NUMBER
RESTORATION CONTENT
031
ISDN D-channel link connection returned to normal condition
032
CCIS link connection returned to normal condition
035
Number of lockout stations restored to less than predetermined number
036
DLC blade returned to normal condition
038
SMDR output buffer (SRAM) return to normal condition from 80% condition
039
SMDR output buffer (SRAM) return to normal condition from overflow

03B
CS/ZT returned to normal condition
03C
LAN application returned to normal condition
050
Traffic of IP network returned to normal condition from limit bandwidth

excess
051
Traffic of IP network returned to normal condition from warning bandwidth

excess
052
Communication error restoration between Main Unit and Remote Unit
053
SIP trunk returned to normal condition
101
Power failure returned to normal condition
103
DTI line returned to normal condition
105
SV8300 Blade returned to normal condition
111
Communication error restoration between active CPU and stand by CPU

113
Expansion Chassis (2U) failure returned to normal condition

2-15
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
Fault Diagnosis and Troubleshooting

When you detect the fault occurrence by PCPro, do the following remedial action.
Recommended troubleshooting procedure is shown below:
Fault kind number, Fault

content and Fault information
is displayed.
Remedial Action on Each Fault Kind

FAULT
KIND
NUMBER
001
FAULT
CONTENT
System Reset
FAULT INFORMATION
Reset kind: Power On Initialize
REMEDIAL ACTION
No specific action is required.
Reset kind: Initialize by Reset Button

(SW1)
Reset kind: Serious failure 1
Replace the CPU blade.

2-16
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010

FAULT
KIND
NUMBER
001
012
FAULT
CONTENT
System Reset
CS/ZT fault
FAULT INFORMATION
REMEDIAL ACTION
Reset kind: SENSE switch was

changed to 0
Reset kind: Reset by CAT or PCPro
Changeover of Dual CPU System
Fault Kind Details: Fault notice from

CS/ZT
Fault Kind Details: CS/ZT reset failure

Fault Kind Details: CS/ZT condition
read failure
Make the CS/ZT busy or

idle condition by CME5
Y=3.
2 Turn OFF and ON the
CS/ZT power switch.
1

unmatched
Fault Kind Details: B channel condition unmatched
Fault Kind Details: SYS-ID upload

failure
Check the CS/ZT with

SYS-ID is correct by
CMAE Y=00>09.
2 Make the CS/ZT busy or
Y=3.
CS/ZT power switch.
1
2-17
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010

FAULT
KIND
NUMBER
FAULT
CONTENT
012
CS/ZT fault
FAULT INFORMATION
Fault Kind Details: SYS-ID download
failure
Fault Kind Details: CS/ZT make busy

failure
Fault Kind Details: CS/ZT data load
failure
Fault Kind Details: B channel make
busy failure
Fault Kind Details: CS/ZT operation
parameter change
failure
REMEDIAL ACTION
When input the SYS-ID
from PCPro, check if the
number is correct.
2 Check the CS/ZT is CS/
ZT without SYS-ID.
Y=3.
CS/ZT power switch.
1
Make the CS/ZT busy or idle

condition by CME5 Y=3.
Y=3.
CS/ZT power switch.
1
Fault Kind Details: LCCH sending

position failure
Fault Kind Details: Carrier selection
failure
[North America/Latin America
Only]
No specific action is required
2-18
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009

FAULT
KIND
NUMBER
012
FAULT
CONTENT
CS/ZT fault
FAULT INFORMATION
Fault Kind Details: CS/ZT expansion
data read failure
data setting failure
parameter 2 change
failure
016
It is a day for
periodic
maintenance
Check Item: Battery check
REMEDIAL ACTION
Y=3.
CS/ZT power switch.
1
Exchange the battery.
Check Item: Check item No. 1

017
Activation
Code error
occurred
during the
License Activation (Center
Activation)
Authentication result: Authenticated

Authentication result: CPU Serial No.
Error
2-19
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009

FAULT
KIND
NUMBER
017
FAULT
CONTENT
Activation
Code error
occurred
during the
License Activation (Center
Activation)
FAULT INFORMATION
Authentication result: ID Code Error
REMEDIAL ACTION
Enter the correct activation code.
2 Check the capitals, symbol and register the preliminary activation code
or the formal activation
code again.
3 Access to the Software
License Activation Center.
Obtain the activation
code and register to the
PBX.
1
Authentication result: PS location

registration
restriction/
origination
restriction
021
ISDN Dchannel link

connection
failure
Check the status of the local

office line or public network
line.
022
CCIS link
connection
failure IPT
link connection failure
Check the status of the local

office line or remote office
line.
2-20
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009

FAULT
KIND
NUMBER
FAULT
CONTENT
025
Number of
lockout stations was more
than predetermined number
026
DLC blade
down
FAULT INFORMATION
REMEDIAL ACTION
Search for stations in line
lockout by the configuration report on the PCPro.
2 Place the handset of any
station in line lockout
back onto the hookswitch.
3 If the station remains in
the line lockout state,
check the line state (the
line between the station
and the PBX may be
shorted).
1
Alarm kind: Terminal was cut off
Check the cable

connection between the
terminal and the PBX.
2 Check to see if the cable
is cut off.
3 Check to see if the Tip
wire of the cable is
grounded.
1
Alarm kind: Short circuit was made on

the line
Check to see if a short circuit

exists on the line.
Alarm kind: Ring wire was grounded
Check to see if the Ring wire

of the cable is grounded.
2-21
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009

FAULT
KIND
NUMBER
026
028
FAULT
CONTENT
DLC blade
down
SMDR output
buffer
exceeded 80 %
FAULT INFORMATION
Alarm kind: Tip wire was grounded or
terminal was unconnected
REMEDIAL ACTION
Check the cable
connection between the
terminal and the PBX.
2 Check to see if the cable
is cut off.
3 Check to see if the Tip
wire of the cable is
grounded.
1
Alarm kind: Terminal failure
Replace the terminal with a

known good one and check to
see if the same failure occurs.
Alarm kind: Terminal Disconnected
Check the cable connection

between the terminal and the
PBX.
Check to see if the modular
code is correctly connected.
Alarm kind: Terminal circuit failure
Replace the terminal with a

known good one and check to
Fault Kind Details: RS-232C port
Collect the charge information from the SMDR.
Fault Kind Details: LAN port

Fault Kind Details: To PMS
Fault Kind Details: To Center office for
Centralized
Billing-CCIS
2-22
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009

FAULT
KIND
NUMBER
029
FAULT
CONTENT
SMDR output
buffer overflow
FAULT INFORMATION
REMEDIAL ACTION
Fault Kind Details: RS-232C port
Collect the charge information from the SMDR.
Fault Kind Details: LAN port

Fault Kind Details: To PMS
Fault Kind Details: To Center office for
Centralized
Billing-CCIS
02B
CS/ZT fault
occurred
Fault Kind Details: Fault notice from

CS/ZT
Fault Kind Details: CS/ZT reset failure
read failure

Y=3.
CS/ZT power switch.
1

unmatched
Fault Kind Details: B channel condition unmatched
Fault Kind Details: SYS-ID upload

failure
Check the CS/ZT with

SYS-ID is correct by
CMAE Y=00>09.
Y=3.
CS/ZT power switch.
1
2-23
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010

FAULT
KIND
NUMBER
02B
FAULT
CONTENT
CS/ZT fault
occurred
FAULT INFORMATION
Fault Kind Details: SYS-ID download
failure
Fault Kind Details: CS/ZT make busy

failure
Fault Kind Details: CS/ZT data load
failure
Fault Kind Details: B channel make
busy failure
parameter change
failure
REMEDIAL ACTION
When input the SYS-ID
from PCPro, check if the
number is correct.
2 Check the CS/ZT is CS/
ZT without SYS-ID.
Y=3.
CS/ZT power switch.
1
Make the CS/ZT busy or idle

condition by CME5 Y=3.
Y=3.
CS/ZT power switch.
1
Fault Kind Details: LCCH sending

position failure
Fault Kind Details: Carrier selection
failure
[North America/Latin America
Only]
2-24
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009

FAULT
KIND
NUMBER
02B
FAULT
CONTENT
CS/ZT fault
occurred
FAULT INFORMATION
data read failure
data setting failure
parameter 2 change
failure
02C
LAN application fault

occurred
When Terminal kind is SMDR:

Fault Content: Connection Timeout
Fault Content: Connection Cut Off text
receive
When Terminal kind is PMS:
Fault Content: Connection Timeout
Fault Content: Connection Cut Off text
receive
REMEDIAL ACTION
Y=3.
CS/ZT power switch.
1
Check to see if the LAN

cable is correctly connected.
2 Confirm the condition of
the LAN device connected to the CPU.
(ex.Power of HUB)
1
When Terminal kind is OAI:

Fault Content: ABOUT/RLRQ
Fault Content: detect the fault by a
health check
040
Traffic of IP
network
exceeded limit
bandwidth
Reduce the number of equipments connected to the IP

network.
041
Traffic of IP
network
exceeded
warning
bandwidth
Reduce the number of equipments connected to the IP

network.
2-25
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009

FAULT
KIND
NUMBER
FAULT
CONTENT
FAULT INFORMATION
REMEDIAL ACTION
042
Communication error
occurrence
between Main
Unit and
Remote Unit

(ex.Power of HUB)
3 Confirm the programming data for the Remote
Unit over IP system,
which is set to the Main
Unit and Remote Unit.
043
SIP-TRK
failure
048
Remote
System
Upgrade

(ex.Power of HUB)
Result: OK
Result: Interrupted
Result: NG: Other than below
Confirm the upgrading

procedure of the CPU program.
Result: NG: FTP double open

Result: NG: FTP server connection
failed/Missing files
Result: NG: Data transfer error
2-26
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009

FAULT
KIND
NUMBER
04A
FAULT
CONTENT
Long call
duration information
FAULT INFORMATION
Connection Status: Call from a station
Connection Status: Termination to station
Connection Status: Call with tandem
connection
REMEDIAL ACTION
Confirm the call status of
the terminal.
2 Disconnect the call when
the line is not released.
1
Connection Status: Termination with

tandem connection
061
VoIPDB
Startup
Process
is failure
100
Power failure
FAN
Check to see if the FAN cable

is correctly connected.
AC input failure
Check to see if the AC power

source is cut off or the plug is
disconnected.
JACK insertion condition

Power Off
Battery
Check to see if the Battery

1U/2U info
102
DTI line failure [PRI]

FTDK: 4
[BRI/CCT]
FTDK: 3
FTDK: 4
FTDK: 5
[DTI]
FTDK: 15
Check to see if the MDF

2-27
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010

FAULT
KIND
NUMBER
FAULT
CONTENT
FAULT INFORMATION
REMEDIAL ACTION
104
SV8300 Blade
down
Plug the blade.
106
SV8300 Blade
reset with
CME03
107
Lack of Option
value
108
109
Automatic
blade reset due
to blade lockup
10A
CPU SRAM
failure
10B
Restricted
blade
Replace the blade for

SV8300.
10C
Firmware
version unmatching
between CPU
blade and Line/
Trunk blade
Upgrade the software of the

blade.
Access to the Software

License Activation Center.
Obtain the activation code
and register to the PBX.
Assign the highway
channel for ISDN communication by CMF7
Y=9 again.
2 Reduce the number of
blades connected to the
Line/Trunk chassis.
1
2-28
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010

FAULT
KIND
NUMBER
FAULT
CONTENT
FAULT INFORMATION
REMEDIAL ACTION
10D

for data communication
Confirm if the highway channel for ISDN communication

is correctly set (CM05 Y=2).
10E
Illegal use of
CPU blade for
Remote Unit
only
Replace the blade for SV8300.
110
Communication error
occurrence
between active
CPU and stand
by CPU
112
Expansion
Chassis (2U)
failure
116
All blades
lockup in
Expansion
Chassis (2U)
Fault Content: Fault detection by a

health check
Check to see if the LAN cable

is correctly connected.
Fault Content: Stand by CPU down
Check the stand by CPU for

abnormal conditions.
Replace the Expansion Chassis

(2U) with a new one.
cable is correctly connected to the Expansion
Chassis (2U).
2 Check the condition of the
BUS cards of the Controlling Chassis (1U) and the
Expansion Chassis (2U),
and replace with a new
one if necessary.
3 Replace the Expansion
Chassis (2U) with a new
one.
1
2-29
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
Station Line Status Display

Item (1) shows the display format for the Station Line Status Display feature, and item (2) shows the fault
diagnosis and troubleshooting method.
For details of the Station Line Status Display feature, see STATION LINE STATUS DISPLAY of Chapter 1.
Page 1-16
(1)
Display Format
XXXX
XX
XX
XX
Station Number
Analog Line/Digital Line
00: LC (Single Line Telephone)
10: DLC (Digital Multiline Terminal)
20: IP Station
Hardware Test Result (See Line Status and Remedial Action for Hardware
Test
Page 2-31)
Software Test Result (See Line Status and Remedial Action for Software
Test
Page 2-32)
(2)
Fault Diagnosis and Troubleshooting

Line Status Remedial Action shows the line status and the remedial action on each indicated data.
Diagnose the contents of the fault and perform the remedial action by referring to Line Status and
Remedial Action for Hardware Test and Line Status and Remedial Action for Software Test.
Page 2-31, Page 2-32
2-30
NWA-033627-001 Rev.4.0
95ch2001.fm
NOVEMBER/21/2008
Line Status and Remedial Action for Hardware Test

SINGLE LINE TELEPHONE
INDICATED
DATA
00
LINE STATUS
Blade is not mounted/
initialized
REMEDIAL ACTION
1
2
Check the cable connection between the terminal

and the PBX.
Check to see if the cable is cut off.
01
Normal Operation of blade
No action is required.
02
Check to see if a short circuit exists on the line.
03
Check to see if the Ring wire of the cable is grounded.
04
Check to see if the LC blade is properly mounted.
05
DIGITAL MULTILINE TERMINAL
INDICATED
DATA
00
LINE STATUS
or Tip wire is grounded
REMEDIAL ACTION
1
2
3
Check the cable connection between the terminal

and the PBX.
Check to see if the cable is cut off.
Check to see if the Tip wire of the cable is
grounded.
01
02
Short circuit is made on the

line
Check to see if a short circuit exists on the line.
03
Ring wire is grounded
Check to see if the Ring wire of the cable is grounded.
04
DLC blade is not mounted
Check to see if the DLC blade is properly mounted.
05
Terminal failure
Replace the terminal with a known good one and check

to see if the same failure occurs.
2-31
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009
Line Status and Remedial Action for Hardware Test

INDICATED
DATA
LINE STATUS
REMEDIAL ACTION
06
DLC blade down
Replace the blade with a known good one and check to

08
Line failure detect
Replace the terminal with a known good one and check

to see if the same failure occurs.
IP STATION
INDICATED
DATA
00
LINE STATUS
REMEDIAL ACTION
1
2
3
01
Check the LAN cable connection between the terminal and the PBX.
Check the condition of LAN cable connection by
transmitting the ping packet.
Confirm the condition of the LAN device (such as
power of the HUB) connected to the VoIPDB.
Line Status and Remedial Action for Software Test

SINGLE LINE TELEPHONE/MULTILINE TERMINAL
INDICATED
DATA
LINE STATUS
REMEDIAL ACTION
01
Idle
02
Line Lockout
Place the handset of the station in line lockout back

onto the hookswitch.
Busy
Other than
01, 02
2-32
NWA-033627-001 Rev.4.0
95ch2001.fm
Troubleshooting by LED Indication on Blades

This section describes the method for fault diagnosis and troubleshooting when you detect the fault occurrence by LED indication on blades.
Remedial Action on Each LED Status shows contents of the fault and the remedial action on each LED
status.
You can also confirm the status of blade by the PCPro.
Remedial Action on Each LED Status

BLADE
NAME
CC-CP00/
CP31 (CPU)
CC-CP01
(CPU)
LED STATUS
FAULT
CONTENT
REMEDIAL ACTION
RUN LED is off
Abnormal operation of
CPU blade
Check to see if the SENSE switch is

set to 0-4 (On Line).
2 If the fault cannot be cleared,
replace the blade.
ALM LED is on
or flashing
Major trouble or Minor

trouble has occurred.
LINK LED is off
LAN connection failure
RUN LED is off
CPU blade
ALM LED is on
or flashing
Major trouble or Minor

trouble has occurred.
See PC Programming Manual.

Check to see if the LAN cable is
correctly connected.
2 Confirm the condition of the LAN
device (such as power of the HUB)
connected to the CPU blade.
replace the blade.
Check to see if the SENSE switch is
set to 1 (On Line).
replace the blade.
See PC Programming Manual.
2-33
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010

BLADE
NAME
CC-CP01
(CPU)
PZ-BS10
(BUS0)
PZ-BS11
(BUS1)
LED STATUS
FAULT
CONTENT
LINK LED is off
LAN connection failure
S2 LED is flashing orange in a

special pattern,
ON: OFF=1: 9.
(This applies only
when the CPU is
operating as a
standby CPU.)
Communication error
occurrence between the
active CPU and the
stand by CPU
LED1 is not on
Expansion Chassis 1
connection failure
LED2 is not on
Expansion Chassis 2
connection failure
LED3 is not on
Expansion Chassis 3
connection failure
LED1 is not on
Expansion Chassis 1
connection failure
REMEDIAL ACTION
2 Confirm the condition of the LAN
device (such as power of the HUB)
connected to the CPU blade.
replace the blade.
replace the blade.
Check to see if the BUS cable is

replace the blade.
replace the blade.
replace the blade.
replace the blade.
2-34
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010

FAULT
CONTENT
BLADE
NAME
LED STATUS
CD-4COTA/
4COTB
(COT)
LIVE LED is not

flashing at 120
IPM
COT blade
CD-4ODTA
(ODT)
LIVE LED is not

flashing at 120
IPM
ODT blade
CD-4DIOPA
(DIOP)
LIVE LED is not

flashing at 120
IPM
DIOP blade
CD-2BRIA
(BRT)
LIVE LED is not

flashing at 120
IPM
BRT blade
CD-PRTA
(PRT/DTI)
LIVE LED is not

flashing at 120
IPM
PRT/DTI blade
REMEDIAL ACTION
Confirm the programming data:
CM05 Y=0.
2 Check to see if the cable is correctly
connected.
replace the blade.
CM05 Y=0.
connected.
replace the blade.
CM05 Y=0.
connected.
replace the blade.
CM05 Y=0.
connected.
replace the blade.
CM05 Y=0.
connected.
replace the blade.
2-35
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010

BLADE
NAME
LED STATUS
FAULT
CONTENT
REMEDIAL ACTION
CD-CCTA
(CCT)
LIVE LED is not

flashing at 120
IPM
CCT blade
CD-4LCA/
8LCA (LC)
LIVE LED is not

flashing at 120
IPM
LC blade
CD-8DLCA/
16DLCA
(DLC)
LIVE LED is not

flashing at 120
IPM
DLC blade
CD-4CSIB
(CSI)
LIVE LED is not

flashing at 120
IPM
CSI blade
CD-4CSIB-A LIVE LED is not

(CSI)
flashing at 120
IPM
CSI blade
2-36

CM05 Y=0.
connected.
replace the blade.
CM05 Y=0.
connected.
replace the blade.
CM05 Y=0.
connected.
replace the blade.
CM05 Y=0.
connected.
replace the blade.
CM05 Y=0.
connected.
replace the blade.
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
Troubleshooting by Contents of Complaint

This section describes the troubleshooting method when you receive a complaint of a problem from a station user or an operator. Select the appropriate section corresponding to the problem by Section for Troubleshooting Procedure, and perform the troubleshooting.
Sections for Troubleshooting Procedure

Complaint from Station User/Operator
Station Line Fault

Page 2-40
(1) At Calling Station
(2) At Called Station
C.O. Line/Tie Line Fault
Page 2-42
(1) On Outgoing Call
(2) On Incoming Call
(3) On Answering Call
Power Failure Transfer (PFT) Fault
Page 2-51
Digital Multiline Terminal Fault
Page 2-52
IP Station Fault
Page 2-54
DESKCON Fault
Page 2-56
DSS Console Fault
Page 2-57
2-37
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009
Explanation of Symbols in Troubleshooting Procedure

The following explains the instruction marks being used in the Troubleshooting Procedure in Station Line
Fault through DSS Console Fault.
CHECK
: With respect to the item indicated on the right side of this mark, perform a check or required work. If an abnormality is found, take the required remedial action, such as repair,
replacement, etc.
REPLACE : Replace the equipment or device (considered to be the fault) indicated on the right side of
the mark with a spare and confirm the recovery of the fault.
How to Follow the Tree

In Station Line Fault through DSS Console Fault, the Troubleshooting Procedure is explained in the
form of a Tree. Troubleshooting can be performed accurately, as well as efficiently, by following the related Tree path according to the information available on the fault. In the following are given step-bystep explanations about how to use the Tree.
STEP1: The maintenance personnel gathers information concerning the fault, and selects the tree (to be)
used from Sections for Troubleshooting Procedure.
STEP2: In the selected tree, search the item concerned by checking the symptom one by one following
the tree downward from the START point. If the related item has not been found, gather more
detailed information concerning the fault.
STEP3: The items indicated by CHECK mark on the right side of the items concerned indicate elements which are possibly responsible for the fault. Check each of these items. If an abnormality
has been found, perform necessary remedial action such as repair, replacement, etc.
STEP4: When the fault is not recovered even if a check has been made on the items indicated by
CHECK mark and necessary actions have been taken, replace the blades and other hardwares indicated by REPLACE mark with spares. In this case, every time a hardware has been
replaced with a spare, check as to whether the fault has been recovered or not.
2-38
NWA-033627-001 Rev.4.0
95ch2001.fm
How to Follow the Tree

START
Symptom
STEP 2
CHECK
REPLACE
(1)
STEP 3-1
(2)
STEP 3-2
(3)
STEP 3-3
(1)
STEP 4-1
(2)
STEP 4-2
END
2-39
NWA-033627-001 Rev.4.0
95ch2001.fm
Station Line Fault

(1) At Calling Station
START
Side Tone cannot be heard.
CHECK
(1) On the MDF, connect a test telephone set to

the faulty station line.
(2) If Side Tone can be heard, check for trouble
with the cabling and telephone set.
(3) If no Side Tone, check for trouble with wiring on the MDF and LC blade.
REPLACE
(1) LC blade
(2) Telephone set
Dial Tone is not returned.

The station telephone set is
DTMF type.
CHECK
(1) System Data Programming for the station:

CM05 Y=0, CM10 Y=00, CM12 Y=00
System does not receive any

digits dialed by the station.
CHECK
(1) RUN LED on the CPU blade is flashing.
REPLACE
(1) CPU blade
After dialing the first digit, Dial

Tone is not disconnected.
At DTMF Telephone set
CHECK
REPLACE

CM12 Y=00
(1) LC blade
(2) Telephone set
At any type of telephone set
CHECK
REPLACE

CM12 Y=00
(1) LC blade
(2) Telephone set
END
2-40
NWA-033627-001 Rev.4.0
95ch2001.fm
(2)
At Called Station
START
At the called station, the telephone
does not ring.
CHECK
REPLACE
(1) Volume Control of the telephone set.

(1) LC blade
(2) Telephone set
The call is routed to a station other

than the dialed number.
CHECK
(1) System Data Programming for destination

station Number: CM05 Y=0, CM10 Y=00
(2) Call Forwarding-All Calls feature is activated at the destination station.
Ringing Signal is not disconnected

after going off-hook.
REPLACE
(1) LC blade
(2) CPU blade
(3) Telephone set
END
2-41
NWA-033627-001 Rev.4.0
95ch2001.fm
C.O. Line/Tie Line Fault

(1) On Outgoing Call
START
After dialing the trunk access code,
tone (Reorder Tone) is returned.
BUSY LED on the trunk
blade is flashing.
CHECK
(1) System Data programming for the trunk:

CM05 Y=0, CM10 Y=00

blade is on.
CHECK
(1) Disconnect the trunk from the line on the

MDF.
(2) If the LED goes out, there is a problem with
the Central Office/Distant Office or Cable.
(3) If not, check for a problem with wiring on
the MDF or the trunk blade.
REPLACE
No LED indication on the
trunk blade.
CHECK
(1) Trunk blade

(1) System Data Programming for the station
restriction service class: CM12 Y=01
2-42
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
A
Dial Tone is not returned from distant office.
In case of COT blade
CHECK

MDF.
(2) Connect a test telephone set to the C.O. line
(distant office side) on the MDF.
SW
MDF
TRUNK
To Distant Office
Test Telephone Set
(3) If Dial Tone is returned by going off-hook

on the test telephone set, check for trouble
with wiring on the MDF and the trunk
blade.
(4) If not, there is a problem with the distant
office or the C.O. line.
REPLACE
In case of ODT blade
CHECK
(1) Trunk blade.

MDF.
(2) To perform a Loopback Test, make a back
to back connection of the trunk blade and
another trunk within the system at the
MDF.
NOTE:
This test only works when the

trunks are assigned for type V
operation.
2-43
NWA-033627-001 Rev.4.0
95ch2001.fm
MDF
DT
ODT
E
M
ODT
E
M
(3) If Dial Tone is returned after seizing the

original trunk, there is a problem with the
distant office, the Carrier Equipment or the
line.
(4) If not, check for trouble with wiring on the
MDF and the trunk blade.
Any dialed digit is not transmitted
to the distant office.
CHECK
(1) System Data Programming for the trunk

route: CM35 Y=001, 008, 020
(2) When the Sender Start condition is set to
Wink or Delay Dial by CM35 Y=020,
check if answer signal is returned from the
distant office.
REPLACE
(1) Trunk blade

(2) CPU blade
2-44
NWA-033627-001 Rev.4.0
95ch2001.fm
C
After dialing the first digit, Dial
Tone from the distant office is not
disconnected.
CHECK
(1) Appropriate signal (DP/DTMF) to distant

office is transmitted.
System Data Programming for DP
signal: CM35 Y=001, 013, 023, 025
System Data Programming for DTMF
signal: CM35 Y=001, 013, 024, 026, 046
(2) System Data Programming for Numbering
Plan: CM20 Y=0-3: A100-A163,
CM20 Y=0-3: A230-A231,
CM22, CM23
REPLACE
(1) Trunk blade

(2) CPU blade
END
2-45
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
(2)
On Incoming Call
START
C.O. Incoming Call is not terminated to DESKCON Station, DIT
or TAS Buzzer.
blade is not turned on.
CHECK

MDF.
(2) Connect a test telephone set to the line on
the MDF.
TRUNK
MDF
To C.O. Line
DESKCON
Test Telephone Set
(3) If the telephone rings, check for trouble

with wiring on the MDF and the trunk
blade.
(4) If not, there is a problem with the distant office or the line.
REPLACE
The BUSY LED is turned
on.
CHECK
(1) Trunk blade

(1) System Data Programming for the trunk
In case of Termination to DIT station:
CM30 Y=02, 03, 04, 05, 13, 14, 17,
CM35 Y=009
In case of Termination to TAS Buzzer:
CM30 Y=02, 03
2-46
NWA-033627-001 Rev.4.0
95ch2001.fm
NOVEMBER/21/2008
A
No Dial Tone Connection on Tie
Line Incoming Call (only for the
2nd dial tone system)
In case of ODT blade
CHECK
(1) In case all Tie Line Trunks fail, check if

DTMF Receivers for Tie Line Incoming
Call are installed (only when the signal kind
of the trunk is DTMF).
CHECK
(1) System Data Programming for the trunk:

CM35 Y=001, 009, 010
(2) Disconnect trunk from the line on the MDF.
(3) To perform a Loopback Test, make a back
to back connect of the trunk and another
trunk within the system at the MDF.
MDF
DT
ODT
E
M
ODT
E
M
(4) If Dial Tone is returned when the call is terminated to the original trunk, there is a
problem with the distant office, the Carrier
Equipment, or the line.
(5) If not, check for trouble with wiring on the
MDF and the trunk blade.
REPLACE
(1) Trunk blade
2-47
NWA-033627-001 Rev.4.0
95ch2001.fm
NOVEMBER/21/2008
B
The Tie Line Incoming Call/DID
Call is routed to a different station
other than the dialed station, or to
Reorder Tone.
CHECK
REPLACE

CM35 Y=001, 017, 061-068
(1) Trunk blade
(2) CPU blade
END
2-48
NWA-033627-001 Rev.4.0
95ch2001.fm
(3)
On Answering the Call
START
Speech Path Trouble:
No connection/One way connection
CHECK

MDF.
(2) To perform the Speech Path Test internally,
make the following connection on the MDF
according to type of blade.
In case of COT card

MDF
COT
DESKCON
STATION PORT
In case of ODT card
MDF
ODT
E
M
ODT
E
M
(3) If the trouble remains, replace the trunk

blade.
(4) If not, there is a problem with the distant office.
REPLACE
(1) Trunk blade

(2) CPU blade
A
2-49
NWA-033627-001 Rev.4.0
95ch2001.fm
NOVEMBER/21/2008
A
Call is dropped (This condition
excludes the Line Fault detected
within a system).
When the station user
flashes the switch-hook.
CHECK

CM35 Y=016
The failure occurs suddenly.
CHECK

MDF.
(2) Connect a test telephone set to the line on
the MDF, and check if the failure reoccurs.
(3) If the failure recurs, there is a problem with
the distant office.
(4) If not, replace the trunk blade.
REPLACE
(1) Trunk blade

(2) CPU blade
Transmission quality is not acceptable.

Noise/Distortion
CHECK
REPLACE
(1) Cabling between the PBX and the MDF or

between the MDF and the lines is properly
run to avoid induction from an AC Power
Cable, motor or power supply equipment.
(1) Trunk blade
(2) CPU blade
Low Voice Level
CHECK
REPLACE
(1) Loose connection of cables on the MDF.

(1) Trunk blade
(2) CPU blade
Cross Talk
CHECK
REPLACE
(1) Wiring on the MDF is properly.

(1) Trunk blade
(2) CPU blade
END
2-50
NWA-033627-001 Rev.4.0
95ch2001.fm
Power Failure Transfer (PFT) Fault

START
Preassigned stations are not connected to the C.O. line when
system alarm or power failure has
occurred.
PFT operates without Power

Failure or Emergency Alarm.
CHECK
(1) Between the Station and the BRI/COT

blade is properly connected.
REPLACE
(1) BRI/COT blade
REPLACE
(1) BRI/COT blade
END
2-51
NWA-033627-001 Rev.4.0
95ch2001.fm
JULY/17/2009
Digital Multiline Terminal Fault

This troubleshooting procedure covers faults with Digital Multiline Terminal function only. For other
faults, see Station Line Fault.
Page 2-40
START
All Keys on the Digital Multiline
Terminal are ineffective.
CHECK
(1) Wiring on Modular Box (Rosette)

(2) DLC blade is properly mounted.
(3) System Data Programming for the Digital
Multiline Terminal station: CM05 Y=0,
CM10 Y=00, CM11, CM12, CM13, CM90
Y=00, CM93
REPLACE
(1) Digital Multiline Terminal

(2) DLC blade
(3) CPU blade

No Connection/One Way Connection
Hands Free Operation is not
available.
REPLACE

(2) DLC blade
CHECK
(1) MIC LED is on.

(2) Adjust speaker volume.
(3) Built-in Hands Free Unit is properly
mounted.
REPLACE
LCD does not display any information
CHECK
REPLACE
(1) Hands Free Unit within Digital Multiline

Terminal
(1) Adjust Display contrast.
(2) DLC blade
2-52
NWA-033627-001 Rev.4.0
95ch2001.fm
NOVEMBER/21/2008
A
No Tone Ringer
CHECK
(1) System Data Programming for Digital Multiline Terminal Tone Ringer: CM90 Y=01
(2) Adjust Ringer Volume on Digital Multiline
Terminal.
REPLACE
END
2-53
NWA-033627-001 Rev.4.0
95ch2001.fm
NOVEMBER/21/2008
IP Station Fault
This troubleshooting procedure covers faults with IP Station function only. For other faults, see Station
Line Fault.
Page 2-40
START
All Keys on the IP Station are ineffective.
CHECK
(1) Wiring on the LAN

(2) VoIPDB is properly mounted.
(3) System Data Programming for the IP Station and VoIPDB: CM0B, CM10 Y=01,
CM11, CM12, CM13, CM90 Y=00, CM93
(4) IP Station setup is properly completed by IP
Station menu.
REPLACE
(1) IP Station
(2) VoIPDB
(3) CPU blade

No Connection/One Way Connection
Hands Free Operation is not
available.
REPLACE
(1) IP Station
(2) VoIPDB
CHECK
(1) MIC LED is on.

(2) Adjust speaker volume.
(3) Built-in Hands Free Unit is properly
mounted.
REPLACE
(1) Hands Free Unit within IP Station

(2) IP Station
2-54
NWA-033627-001 Rev.4.0
95ch2001.fm
NOVEMBER/21/2008
A
LCD does not display any information
CHECK
REPLACE
(1) Adjust Display contrast.

(1) IP Station
(2) VoIPDB
No Tone Ringer
CHECK
(1) System Data Programming for IP Station

Tone Ringer: CM90 Y=01
(2) Adjust Ringer Volume on IP Station.
REPLACE
(1) IP Station
END
NOTE:
You can check the condition of LAN cable connection by transmitting the ping packet to the
VoIPDB from PC on the LAN.
2-55
NWA-033627-001 Rev.4.0
95ch2001.fm
DESKCON Fault
DESKCON means SN716 DESKCON.
START
All keys on the DESKCON are

ineffective.
CHECK
(1) DESKCON Lock-out has been set via
the function key.
(2) Wiring on Modular Box (Rosette)

(4) System Data Programming for the
console: CM05 Y=0, CM10 Y=00, CM60,
CM90 Y=00.
(5) RUN Lamp on the CPU blade is flashing.
REPLACE
(1) DESKCON
(2) DLC blade
(3) CPU blade
Speech Path Trouble

(No Connection/One-Way
Connection)
CHECK
(1) Headset or Handset on the console.

(2) DESKCON
(3) DLC blade
LCD does not display any information.
CHECK
REPLACE
(1) Adjust Display Contrast.

(1) DESKCON
(2) DLC blade
No Tone Ringer
CHECK
(1) System Data Programming for the console

tone ringer: CM60 Y=16, 27
(2) Adjust Ringer Volume on the console.
REPLACE
(1) DESKCON
END
2-56
NWA-033627-001 Rev.4.0
95ch2001.fm
APRIL/16/2010
DSS Console Fault

START
Keys on the DSS Console are
ineffective.
CHECK

(2) System Data Programming for DSS
Console: CM05 Y=0, CM10 Y=00, CM96,
CM97
REPLACE
(1) DSS Console

(2) DLC blade
(3) CPU blade
END
2-57
NWA-033627-001 Rev.4.0
95ch2001.fm
THIS PAGE LEFT BLANK INTENTIONALLY.
2-58
NWA-033627-001 Rev.4.0
95ch2001.fm
NOVEMBER/21/2008

NWA 033627 001 40 - System Maintenance Manual

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

NWA 033627 001 40 - System Maintenance Manual

Încărcat de

Drepturi de autor:

Formate disponibile

System Maintenance Manual

PBX System Designation .................................................................................................

REFERENCE MANUAL ...........................................................................................

System Data Backup .......................................................................................................

HOW TO READ THIS CHAPTER ............................................................................

General Description .........................................................................................................

STATION LINE STATUS DISPLAY ..........................................................................

General Description .........................................................................................................

BATTERY RELEASE CONTROL .............................................................................

General Description .........................................................................................................

General Description .........................................................................................................

BATTERY REPLACEMENT .....................................................................................

General Description .........................................................................................................

VoIP LOG COLLECTION .........................................................................................

General Description .........................................................................................................

QoS DISPLAY ON IP MULTILINE TERMINAL ........................................................

General Description .........................................................................................................

STATION SERVICE STATUS DISPLAY ..................................................................

General Description .........................................................................................................

PING COMMAND .....................................................................................................

General Description .........................................................................................................

Grounding Requirements .................................................................................................

OUTLINE OF TROUBLESHOOTING .......................................................................

LED Indication on Blades ................................................................................................

FAULT INFORMATION DISPLAY ............................................................................

Display on PCPro/CAT ....................................................................................................

Station Line Fault ........................................................................................................

THIS PAGE LEFT BLANK INTENTIONALLY.

OUTLINE OF THIS MANUAL

For the following features, refer to the PC Programming Manual.

TERMS IN THIS MANUAL

Digital Multiline Terminal

SIP Multiline Terminal

IP Single Line IP Single Line Telephone (SIP)

This chapter describes the general description, service conditions,

Chapter 1 MAINTENANCE SERVICES

HOW TO READ THIS CHAPTER

Chapter 1 MAINTENANCE SERVICES

Chapter 1 MAINTENANCE SERVICES

Displays the unique number assigned to the fault information.

Displays the date and time at which the fault occurred.

Error Type field

Displays the number of the fault type.

Displays the alarm type of the fault.

Displays detailed information about the fault selected

External Alarm Display Panel

Chapter 1 MAINTENANCE SERVICES

External Alarm Display Panel

MJ Alarm occurred or MN Alarm occurred displays on the external equipment.

Controlling relay of external equipment provides controlling relay ON/OFF only.

The conditions when controlling relay of MN alarm are shown below.

Chapter 1 MAINTENANCE SERVICES

Enable the fault information storage feature.

Assign which kind of fault information is

CMEA programming can be set by the PCPro.

Fault Kind: Occurrence

CS/ZT fault occurred

It is a day periodic maintenance

Activation Code error occurred during the

ISDN D-channel link connection failure

CCIS link connection failure

Number of lockout stations was more than

DLC blade down