NEC Electronics America Cell Phone NDA 24300 User Manual

•

When the range of faulty conditions has been specified and a faulty circuit card can be assumed

See Section 4, Reporting Fault to NEC, in Chapter 2.

•

When investigating the system for the purpose of a fault repair

See Section 2, Basic Knowledge, in Chapter 2.

•

When replacing a unit/circuit card with a spare

Chapter 4

When performing routine maintenance

Chapter 7

CHAPTER 1

Page 2

NDA-24300

Issue 1

CHAPTER 2

SYSTEM MAINTENANCE OUTLINE

1. GENERAL

1.1 Purpose

This chapter explains the outline of fault diagnosis and duties necessary to maintain the PBX.

1.2 Administrative Management Procedures

Figure 2-1 shows the work flow of the administrative management procedures.

Administrative

Management Procedures

Administrative Procedures

Office Data Management and Office

Data Protection

Expansion and Change of

Station Users

Traffic Management

Actions on Claims from

Station Users and/or Operators

(A)

Management Procedures

Station Message Detail

Recording System (SMDR)

Routine Diagnosis

Diagnosis result, system message displays abnormality

(B)

Routine Maintenance

System Status Monitor

See Chapter 7

Line fault

Alarm Indications

Fault Analysis/

Test Operation/

Changeover/

Circuit card fault

Refer to

Collection of System Messages

Indication of Lockout Stations

Terminal

(Tel., etc.) fault

Make-Busy/Circuit

Card Change/

Initialization

Fault cause not

able to be localized

(A)

(B)

(Abnormal

Congestion)

Line Load Control

See Section 3, How to Read Precautions, Diagnostic, and Fault Repair Information.

Figure 2-1 Flow of Administrative Management Procedures

NDA-24300

CHAPTER 2

Page 3

Issue 1

SYSTEM MAINTENANCE OUTLINE

1.3 Summary of This Manual’s Contents

Table 2-1 provides a brief description of the contents for each chapter in this manual.

Table 2-1 Summary of This Manual’s Contents

CHAPTER

DESCRIPTION

See Section 2, Basic Knowledge.

Explains basic knowledge of fault detection and indication, functions and fault range of the system,

etc.

Explains the methods of procedure performance and various symbols used in the description.

See Section 4, Reporting Fault to NEC.

Explains the method of forwarding faulty circuit cards, the method of creating a history record for fu-

ture fault repair, and the method of reporting faults to NEC.

Explains how to read and analyze system messages.

Explains the method of replacing a unit/circuit card due to a fault.

Explains repair procedures corresponding to the faults of processors or equipment.

Explains how to control the system in service management functions and precautions required in the

system control process.

Explains routine maintenance.

Explains the commands used in the system administrative management procedure.

2. BASIC KNOWLEDGE

This section identifies the information necessary for the system operations and maintenance procedures.

2.1 System Configuration

2.2 Line Equipment Numbers (LENS)

2.3 Local Partition (LP) Number

2.4 System Messages

2.5 Fault Detecting Function

2.6 Range of Faults Specification

2.7 Explanation of Terms

CHAPTER 2

Page 4

NDA-24300

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.1 System Configuration

Figure 2-2 shows the system configuration of the fully expanded 4-IMG type. For details on each module

accommodation, see Figure 2-3 through Figure 2-5.

IMG0

IMG1

IMG2

IMG3

TOPU

PIM3

PIM2

FANU

PIM1

PIM2

FANU

PIM1

PIM2

FANU

PIM1

PIM2

FANU

PIM1

PIM0

LPM

TSWM

DUMMY

BASEU

DUMMY

BASEU

FRONT VIEW

BASEU: Base Unit

DUMMY: Dummy Box

FANU:

LPM:

PIM:

TOPU:

TSWM:

Fan Unit

Local Processor Module

Port Interface Module

Top Unit

Time Division Switch Module

Figure 2-2 System Configuration

NDA-24300

CHAPTER 2

Page 5

Issue 1

SYSTEM MAINTENANCE OUTLINE

Figure 2-3 shows the face layout of IMG0.

IMG0

TOPU

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 3

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 2

FANU

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

00 01 02 03 04

PIM 1

PIM 0

LPM

BASEU

Front View

Note: The 2nd IOC card (optional) may be mounted in this slot.

Figure 2-3 Face Layout of IMG0

NDA-24300

CHAPTER 2

Page 6

Issue 1

SYSTEM MAINTENANCE OUTLINE

Figure 2-4 shows the face layout of IMG1.

IMG1

TOPU

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 3

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 2

FANU

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 1

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 0

21 22 23

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20

TSWM

BASEU

Front View

PWRSW: PH-PW14

DLKC: PH-PC20

GT: PH-GT09

TSW: PH-SW12

PLO: PH-CK16/17/16-A/17-A

Note: No circuit card is mounted in Slot 02 of TSWM. Instead, on the backboard of this slot, a

terminal resistor with a total of two in a dual system is fastened.

Figure 2-4 Face Layout of IMG1

NDA-24300

CHAPTER 2

Page 7

Issue 1

SYSTEM MAINTENANCE OUTLINE

Figure 2-5 shows the face layout of IMG 2/3.

IMG2/3

TOPU

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 3

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 2

FANU

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM 1

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21

PIM 0

DUMMY

BASEU

Front View

Figure 2-5 Face Layout of IMG2/3

NDA-24300

CHAPTER 2

Page 8

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.2 Line Equipment Numbers (LENS)

The Line Equipment Numbers (LENS) are used to specify the location of a circuit (trunk/port) in any of

the PIM universal slots. Refer to the figures in this section, and confirm the LENS format used in the

system.

As shown in Figure 2-6, the LENs consists of six digits: two digits for MG, one digit for U, two digits for

G, and one digit for Lv.

LENS = XX X XX X

Lv (Level) : 0 - 7

G (Group) : 00 - 23

U (Unit) : 0 - 3

Note

MG (Module Group) : 00 - 07

Note: If an FCH (PA-FCHA) card is used, line groups 24-31 can be used as the extended group numbers.

Figure 2-6 LENS Format

2.2.1 Module Group

Figure 2-7 explains the Module Group (MG). In a fully expanded system, the MG number ranges from

00 to 07.

IMG0

TOPU

IMG1

TOPU

IMG2

TOPU

IMG3

TOPU

PIM3

PIM2

MG01

MG03

MG05

MG07

FANU

PIM1

PIM0

MG00

MG02

MG04

MG06

LPM

TSWM

DUMMY

BASEU

DUMMY

BASEU

FRONT VIEW

Figure 2-7 Module Group Allocations

NDA-24300

CHAPTER 2

Page 9

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.2.2 Unit

Figure 2-8, which represents a fully expanded system, explains the Unit (U) numbers. The numbers

range from 0 to 3, and each unit represents the PIM universal slots, No. 04-12 (U 0/2) or No. 15-23 (U

1/3).

On each Module Group (MG: #00 - 07), a total of four Units (U0 - U3) can be assigned.

IMG0

TOPU

IMG1

TOPU

IMG2

TOPU

IMG3

TOPU

PIM3

PIM2

MG01

MG03

MG05

MG07

FANU

PIM1

PIM0

MG00

MG02

MG04

MG06

LPM

TSWM

DUMMY

BASEU

DUMMY

BASEU

FRONT VIEW

Unit Number (U = 0/2)

Unit Number (U = 1/3)

Slots No.

04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

192 TS

Number

PIM

Time Slots

16 16 16 16 16 16 32 32 32

(16)

Control

Figure 2-8 Unit Number Allocations

NDA-24300

CHAPTER 2

Page 10

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.2.3 Group

The Group (G) numbers are allocated as shown in Figure 2-9. A total of two Groups are assigned on

each universal slots within the PIM. Slot numbers 10, 11, 12, 21, 22, 23 can contain a total of four

Groups as an exception.

A total of two or four Groups (G) can be assigned on each PIM universal slot.

IMG0

TOPU

IMG1

TOPU

IMG2

TOPU

IMG3

TOPU

Slot No. 10

PIM3

PIM2

M G01

FANU

MG03

FANU

MG05

FANU

MG07

FANU

G = 15

G = 14

G = 13

G = 12

PIM1

PIM0

M G00

MG02

MG04

MG06

Slot No. 05

LPM

TSWM

DUMMY

BASEU

DUMMY

BASEU

G = 03

04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

G = 02

PIM

FRONT VIEW

15 19 23

14 18 22

13 17 21

12 16 20

01 03 05 07 09 11

14 18 22

13 17 21

12 16 20

PIM

Group No.

(24)

(25) 00 02 04 06 08 10

00 02 04 06 08 10

Extended

Group No.

Note

Slot No.

04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

U = 0 / 2 U = 1 / 3

Note: In addition to Group No. 00 - 23, the system can use No. 24 - 31 as theoretically valid numbers.

Figure 2-9 Group Number Allocations

NDA-24300

CHAPTER 2

Page 11

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.2.4 Level

Figure 2-10 explains the Level (Lv) numbers. There are a total of eight Levels (Lv0 - Lv7) on every

Group number, which ranges from 00 to 31.

A total of eight Levels (Lv0 - Lv7) can be assigned on each Group.

IMG0

IMG1

IMG2

IMG3

TOPU

PIM3

PIM2

MG01

FANU

MG03

FANU

M G05

FANU

MG07

FANU

PIM1

PIM0

MG00

MG02

M G04

MG06

LPM

TSWM

DUMMY

BASEU

DUMMY

BASEU

FRONT VIEW

U = 0 / 2

U = 1 / 3

02 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

Level (Lv)

151923

141822

131721

121620

15 19 23

14 18 22

13 17 21

12 16 20

010305 07 0911

000204 06 0810

010305070911

000204060810

PIM

Group No.

(24) (25)

27 29

26 28

27 29 31

26 28 30

Group

(G = 15/19/23)

Level (Lv)

Group

(G = 14/18/22)

Group

(G = Odd No., < 11)

Group

(G = 13/17/21)

Group

(G = Even No., < 10)

Group

(G = 12/16/20)

Figure 2-10 Level Number Allocations

NDA-24300

CHAPTER 2

Page 12

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.3 Local Partition (LP) Number

The Local Partition (LP) number refers to a logical local processor number, theoretically assigned for each

IMG that consists of four (or less) Port Interface Modules (PIM). Though the local processor does not

actually exist in any of the IMGs, except for IMG0, the system can apply the two-digit LP number to each

IMG (see Figure 2-11) on its data memory program. The LP numbers are used primarily in the following

cases:

•

Display of system messages

Assignment of line load control data (ALLC command)

Backup for Call Forwarding/Speed Calling data (MEM_HDD command), etc.

The Local Partition No. (two digits, even number) is assigned on each IMG.

IMG0

TOPU

PIM3

IMG1

TOPU

PIM3

IMG2

TOPU

PIM3

IMG3

TOPU

PIM3

PIM2

FANU

PIM1

PIM2

FANU

PIM1

PIM2

FANU

PIM1

PIM2

FANU

PIM1

PIM0

LPM

TSWM

DUMMY

BASEU

DUMMY

BASEU

LP No. = 00

LP No. = 02

LP No. = 04

LP No. = 06

FRONT VIEW

Figure 2-11 LP Number Allocations

NDA-24300

CHAPTER 2

Page 13

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.4 System Messages

System messages display during routine diagnosis, system operation status controlling, and fault

occurrence. Figure 2-12 shows an example of a system message.

Refer to Chapter 3 for details on each message.

(1)

(2)

SYSTEM MESSAGE 3-E SUP LOCK UP FAILURE (TEMPORARY)

NEC TOKYO

LP00-0-ACT

JUL 24 09:35

(3)

(4)

1:1102 0000 0000 0000

4:0000 0000 0000 0000

7:0000 0000 0000 0000

2:0000 0000 0000 0000

5:0000 0000 0000 0000

8:0000 0000 0000 0000

3:0000 0000 0000 0000

6:0000 0000 0000 0000

9:0000 0000 0000 0000

Meaning:

(1)

SYSTEM MESSAGE 3-E SUP LOCK-UP FAILURE (TEMPORARY)

Meaning of the message

System Message Level

(Indicated by Alarm Lamp) Note

System Message Number

Note: There are four kinds of alarm information to be indicated by alarm lamps: MN,

MJ, SUP, and No Indication.

(2) : Office Name, Date and Time

(3) : LP00-0-ACT

ACT/STBY indication for dual systems

No.0/No.1 system indication for dual systems

Faulty processor/Related processor

(4) : Message detail data (notation by hexadecimal numbers)

Figure 2-12 System Message Example

CHAPTER 2

Page 14

NDA-24300

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.5 Fault Detecting Function

The system finds a fault by its fault detecting circuit and the fault detecting program. Once a fault occurs,

the system initiates a remedial action such as system changeover, make-busy setting, or restart processing

by the automatic diagnosis function. This action reduces the influence of the fault so that system servicing

may be minimized. The result of the process taken and the fault situation are indicated for equipment

concerned.

Among the faults, those related to speech path (noise, one-way speech, speech inability, etc.) are not

detectable. Since these fault reports are to be obtained from a station or operator, periodic trunk tests must

be performed without failure to detect the faults related to speech path.

Figure 2-13 shows an outline of fault detection, and Figure 2-14 shows a block diagram of fault detection.

Fault Occurrence

Indication

Information

Collection and Diagnosis

Example of Faults

IOC

Fault of line/trunk card

Display of

System Messages

CPU

TSW write failure,

Fault of clocks, etc.

NEAX 2400 IMS

NEC

Indication of

Alarm Lamps

on TOPU

Abnormal temperature,

power supply failure,

fuse blowing, etc., within

the equipment frame

EMA

Figure 2-13 Fault Detection General Diagram

NDA-24300

CHAPTER 2

Page 15

Issue 1

SYSTEM MAINTENANCE OUTLINE

Alarm Lamps on TOPU

Thermal Reed Relay

Symbols

: Circuit Card

: Main faults to be detected

: Speech path

Firmware

Fault

LC/TRK

: Flow of fault information

RDY

Clock

etc.

MUX

TSWM

RDY

Clock

Write

etc.

TSW/INT

Ready

DLKC

C-level

monitor

Howler

Ringing

Circuit

To MAT,

Printer, etc.

IOC

CPU

PWR

PWR Supply

Failure,

Fuse Blown

Fault

Information

Note

Note: MJ, MN fault

Power, Fuse blown fault

Temperature, CPU fault

Speech Path System fault (SPE)

RGU, Howler fault

PFT fault

EMA

CPU Clock fault

SYMBOL

CPU

NAME

SYMBOL

DLKC

INT

NAME

Central Processing Unit

Emergency Alarm Controller

I/O Controller

Data Link Controller

EMA

Speech Path Control Interface

Time Division Switch

Multiplexer

IOC

TSW

LC/TRK

Line/Trunk

MUX

Gate

TSWM

Time Division Switch Module

PWR

Power Supply

Figure 2-14 Fault Detection Block Diagram

NDA-24300

CHAPTER 2

Page 16

Issue 1

SYSTEM MAINTENANCE OUTLINE

(a) Main Faults

Faults that may occur in the system can be generally categorized into Processor System Fault, Speech

Path System Fault, Line/Trunk Fault, etc.

•

Processor System Fault

The CPU alarm detecting circuit continuously monitors whether the CPU is working normally. If

a fault is detected, the CPU calls up the diagnostic program, which identifies the cause of the fault

and determines whether the fault is temporary or permanent. When the fault affects system

operations, Active/Standby status of the CPU is changed over (provided that the system has dual

configuration).

•

Bus System Fault

The CPU transfers line/trunk card control information to the associated peripheral circuits via IO

Bus. When a parity error is detected in the transfer data or when the required information cannot

be transferred from a circuit card, the CPU identifies the cause of the fault, changes over the CPU

so that system operation is not affected, and executes restart processing.

Speech Path Fault

The CPU monitors the operating status of the TSW card, the occurrence of errors in writing data

to the switch memory, and the basic clocks supplied to the speech path. Upon detecting a fault, the

CPU identifies the cause of the fault, determines whether the fault is temporary or permanent, and

executes required processing such as changeover of the TSW card.

Others

The alarm detecting circuit on the EMA card continuously monitors the occurrence of faults in the

PWR supply cards, such as abnormal temperatures within the equipment frame, and lights the

alarm lamp on the TOPU when a fault is detected.

(b) Lamp Indications on the TOPU

When a fault occurs, the corresponding lamp on the TOPU indicates the location of the fault. For the

meaning of each lamp indication, refer to Chapter 6.

NDA-24300

CHAPTER 2

Page 17

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.6 Range of Faults Specification

(1) Upon receiving a fault report from a station user or an operator, the technician can assume a faulty card

exists if the range to be affected by the fault can be determined. For the detailed procedure, refer to Chap-

ter 5. Use the following actions to check the MDF:

(a) Check the LENS of the reporter (Station or ATTCON/DESKCON).

(b) Check other circuits of the circuit card in which the reporter (station lineor ATTCON/DESKCON)

is located.

reporter is located.

(d) Check lines in each of the other modules on the basis of plural lines.

(2) If the fault cannot be detected by the system (a fault related to the speech path such as noise during speech,

one-way speech, speech inability), the range of (a) through (d) (itemized above) should be limited.

(3) When a major fault is detected in the dual systems, the CPU or TSW system automatically changes over

if the fault range is (c) and (d). In this case, the whole module involved is placed into make-busy status

even if the fault is partial, and the station lines currently operating normally become faulty status.

Diagnose the fault from the content of the system message displayed and repair the fault as required.

(4) When limiting the range of faults, consider the system circuitry that consists of the control (see Figure 2-

16, where CPU 0 is active) and speech path systems (see Figure 2-17).

(5) As seen from the block diagrams in Figure 2-15 through Figure 2-18, if a fault occurs within the common

portions to be controlled, all other associated portions are affected by that fault occurrence. If the range

of faults is outside PIM fault, CPU/TSW system changeover is executed (only when the fault is detectable

by the system).

CHAPTER 2

Page 18

NDA-24300

Issue 1

SYSTEM MAINTENANCE OUTLINE

SERIAL BUS

IMG0

MUX

PM BUS

LC/TRK LC/TRK

PM BUS

LC/TRK LC/TRK

PM BUS

LC/TRK LC/TRK

PM BUS

LC/TRK LC/TRK

PM BUS

LC/TRK LC/TRK

PM BUS

LC/TRK LC/TRK

PM BUS

E1/DS1

with

Fusion Link

E1/DS1

DTI

FCH LC/TRK

LC/TRK

FCH DTI

with

Fusion Link

TSWM

TSW 00

TSW 10

To MUX

TSW 01

TSW 11

To MUX (IMG2)

TSW 02

TSW 12

To MUX (IMG3)

TSW 03

TSW 13

PLO 0

PLO 1

MISC I/O BUS

MISC

DLKC 0 DLKC 1

GT 0

GT 1

LPM

MISC I/O BUS

EMA

ISAGT

CPU 0

ISAGT

CPU 1

MISC

IOC

LANI LANI

RS-232C

MAT

HUB

10 BASE-T

MAT

10 BASE-T

HUB

Symbols

EMA: PH-PC40

TSW: PH-SW12

ISAGT: PZ-GT13

DLKC: PH-PC20

LANI: PZ-PC19

MUX: PH-PC36

GT: PH-GT09

PLO: PH-CK16/17/16-A/17-A

IOC: PH-IO24

: Circuit Card

Figure 2-15 General System Block Diagram

NDA-24300

CHAPTER 2

Page 19

Issue 1

SYSTEM MAINTENANCE OUTLINE

IMG0

IMG1

PIM 3

PIM 2

PIM 1

PIM 0

PM BUS

MUX

LC/TRK

MUX

PM BUS

PIM 2

PIM 1

PIM 0

PM BUS

MUX

LC/TRK

PM BUS

LC/TRK

PM BUS

LC/TRK

MUX

PM BUS

To IMG 2 To IMG 3

TSWM

TSW

/INT

TSW

/INT

TSW

/INT

TSW

/INT

U U U U

X X X X

TSW

003002001000

013 012 011010

100101102103

110111112113

TSW/INT

TSW 00

TSW 01

TSW 10

TSW 11

TSW I/O BUS

MISC BUS

BUS

TSW I/O

MISC BUS

DLKC 1

DLKC 0

LPM

IOP1

MISC BUS

GT 0

MISC BUS

Note 1

PLO 0

PLO 1

Note 3

GT 1

CPR

Note 2

MISC BUS

ISAGT 0 ^T

IOP0

CPU clock

ISA BUS

Symbols

PCI BUS

LANI

MISC BUS

CPU 0

: Controlling Routes of CPU

: Circuit card (active)

: External Cable

: Cable

: Circuit card (STBY)

: Clock Oscillator

Reset Signal

PWR

IOC /

MISC

EMA

MEMORY

CPR

(ST-BY)

: Signral

CPU board

EMA:

LANI:

IOC:

PH-PC40

PZ-PC19

PH-IO24

ISAGT: PZ-GT13

ISAGT

MISC BUS

GT:

PH-GT09

PH-SW12

PH-CK16/17/16-A/17-A

TSW:

PLO:

PWR

DLKC: PH-PC20

MUX: PH-PC36

Note 1: The circuit cards, drawn by dotted lines, indicate they are in STBY state. These cards (TSW, MUX and

DLKC) are totally changed over to the ACT mode, when the MBR key of the active GT (PH-GT09) card is

once flipped. However, PLO (PH-CK16/17/16-A/17-A) is independent and not affected by the development.

Note 2: If the ACT/STBY of CPU is once changed over, the system of GT (in TSWM) also changes over.

Note 3: Though an external cable is physically connected between ISAGT0 and GT1, the actual control signal is

sent/received only between ISAGT0 and GT0. This is because GT0 and GT1 are having a multiple connection

on the backboard side. (Refer to Chapter 6, Section 12.)

Figure 2-16 CPU Controlling Block Diagram

CHAPTER 2

NDA-24300

Page 20

Issue 1

SYSTEM MAINTENANCE OUTLINE

IMG3

IMG2

PM BUS

PIM 3

MUX

LC/TRK

MUX

PM BUS

PIM 2

PM BUS

LC/TRK

PM BUS

PIM 1

LC/TRK

PM BUS

PIM 0

LC/TRK

MUX

PM BUS

To IMG 0 To IMG 1

TSWM

TSW

/INT

TSW

/INT

TSW

/INT

TSW

/INT

U U U U

X X X X

TSW

023022021020

033032031030

120121122123

130131132133

TSW/INT

TSW 02

TSW 03

TSW 12

TSW 13

TSW I/O BUS

MISC BUS

TSW I/O BUS

MISC BUS

DLKC 1

DLKC 0

LPM

IOP1

MISC BUS

GT 0

MISC BUS

Note 1

Note 3

PLO 0

PLO 1

CPR

Note 2

MISC BUS

GT 1

ISAGT 0 ^T

IOP0

CPU clock

ISA BUS

Symbols

PCI BUS

LANI

MISC BUS

CPU 0

: Controlling Routes of CPU

: Circuit card (active)

: External Cable

: Cable

: Circuit card (STBY)

: Clock Oscillator

Reset Signal

PWR

IOC /

MISC

EMA

MEMORY

CPR

(ST-BY)

: Signral

CPU board

EMA:

LANI:

IOC:

PH-PC40

PZ-PC19

PH-IO24

ISAGT: PZ-GT13

GT:

TSW:

PLO:

ISAGT

MISC BUS

PH-GT09

PH-SW12

PH-CK16/17/16-A/17-A

PWR

DLKC: PH-PC20

MUX: PH-PC36

Note 1: The circuit cards, drawn by dotted lines, indicate they are in STBY state. These cards (TSW, MUX and

DLKC) are totally changed over to the ACT mode, when the MBR key of the active GT (PH-GT09) card is

once flipped. However, PLO (PH-CK16/17/16-A/17-A) is independent and not affected by the development.

Note 2: If the ACT/STBY of CPU is once changed over, the system of GT (in TSWM) also changes over.

Note 3: Though an external cable is physically connected between ISAGT0 and GT1, the actual control signal is

sent/received only between ISAGT0 and GT0. This is because GT0 and GT1 are having a multiple connection

on the backboard side. (Refer to Chapter 6, Section 12.)

Figure 2-16 CPU Controlling Block Diagram (Continued)

NDA-24300

CHAPTER 2

Page 21

Issue 1

SYSTEM MAINTENANCE OUTLINE

IMG0

IMG1

PIM 3

PIM 2

PIM 1

PIM 0

MUX

LC/TRK LC/TRK LC/TRK

PIM 2

PIM 1

PIM 0

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

To IMG2 To IMG2 To IMG3 To IMG3

LVDS (Low Voltage Differential Signaling)

TSW 01

TSWM

TSW 00

MUX 003

TSW/

INT

TSW/

INT

TSW/

INT

TSW/

INT

MUX 013

TSW

MUX 002

MUX 012

MUX 011

MUX 010

MUX 001

MUX 000

TSW/INT

TSW 10

TSW 11

MUX 100

MUX 110

MUX 101

MUX 102

MUX 103

MUX 111

MUX 112

MUX 113

TSW/INT

Symbols

: Speech Path

: Circuit Card (active)

: Cable

: Circuit Card (STBY)

TSW: PH-SW12

MUX: PH-PC36

Figure 2-17 Speech Path Block Diagram

CHAPTER 2

NDA-24300

Page 22

Issue 1

SYSTEM MAINTENANCE OUTLINE

IMG2

IMG3

PIM 3

PIM 2

PIM 1

PIM 0

PIM 3

PIM 2

PIM 1

PIM 0

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

To IMG0 To IMG0 To IMG1 To IMG1

LVDS (Low Voltage Differential Signaling)

TSW 03

TSWM

TSW 02

MUX 023

TSW/

INT

TSW/

INT

TSW/

INT

TSW/

INT

MUX 033

TSW

MUX 022

MUX 032

MUX 031

MUX 030

MUX 021

MUX 020

TSW/INT

TSW 12

TSW 13

MUX 120

MUX 130

MUX 121

MUX 122

MUX 123

MUX 131

MUX 132

MUX 133

TSW/INT

Symbols

: Speech Path

: Circuit Card (Active)

: Cable

: Circuit Card (STBY)

TSW: PH-SW12

MUX: PH-PC36

Figure 2-17 Speech Path Block Diagram (Continued)

NDA-24300

CHAPTER 2

Page 23

Issue 1

SYSTEM MAINTENANCE OUTLINE

A fault within this range affects two slots.

LC/TRK

A fault within this range

affects this module.

32ch

LC/TRK

PIM 3

MUX

512ch

A fault within this range

affects the circuit card.

A fault within this range

affects two slots.

LC/TRK

A fault within this range

affects this module.

32ch

LC/TRK

PIM 2

PIM 1

PIM 0

512ch

MUX

A fault within this range

affects the circuit card.

A fault within this range

affects two slots.

LC/TRK

A fault within this range

affects this module.

32ch

LC/TRK

512ch

MUX

A fault within this range

affects the circuit card.

A fault within this range

affects two slots.

LC/TRK

A fault within this range

affects this module.

32ch

512ch

MUX

A fault within this range

affects the circuit card.

TSW

TSW/INT

Symbols

: Circuit Card

: Possible fault range to be affected

: Speech Path

Figure 2-18 Speech Path Range of Fault

CHAPTER 2

Page 24

NDA-24300

Issue 1

SYSTEM MAINTENANCE OUTLINE

2.7 Explanation ofTerms

•

C-Level Infinite Loop

The program repeatedly executes specific routines due to a fault of the main memory, data destruction,

etc. The program is not able to be processed normally. This faulty condition is referred to as Program

Infinite Loop. C-Level infinite loop is a state where a clock-level program, which runs under clock

interrupt disable state, is in an infinite loop status.

•

B-Level Infinite Loop

This is a state where a program infinite loop has occurred during a connection processing and the

connection for the next call is not able to be processed.

Port Microprocessor (PM)

Each line/trunk card mounted in the PIM is equipped with a processor called Port Microprocessor

(PM), which continuously supervises the lines/trunks.

Ready Error

For acknowledging the connection between the CPU and a circuit card, an interface signal called

Ready Signal is used. When the CPU has accessed a specific circuit card and the normality of the

connection is acknowledged, the Ready Signal is returned to the CPU within 6 µs. If the Ready signal

is not returned to the CPU within 6 µs after access, the situation is referred to as Ready Error.

•

Parity Error

For confirming the normality of data transfer between the CPU and the circuit card under the control

of the CPU, parity check is made. When an error is detected in a parity check, it is referred to as Parity

Error. Parity check means to confirm the normality of data by adding an error detecting parity bit to

a set of data to be transferred.

When a set of data is transferred, a parity bit is added to the data so that the data has an even-number

of “1” bits (it is referred to as Even Parity). When there is an odd-number of “1” bits in the received

one set of data, it is detected as an error.

•

Monitor Restart

Monitor restart processing suspends current processings in progress without applying any hardware

controlling, allowing the system to restart its operations from the monitor program.

The system abandons only the processings of the calls being handled by the program, and maintains

all the connections that have already been established.

Circuit Card Front Initializing Restart

The whole system is forcibly initialized. However, the initialization varies with the setting of the

SENSE switch on the DSP of CPU (see Table 2-2).

NDA-24300

CHAPTER 2

Page 25

Issue 1

SYSTEM MAINTENANCE OUTLINE

Table 2-2 Kinds of Circuit Card Front Restart

SENSE (0~F)

KIND OF RESTART

DM Clear Restart

REMARKS

DM Load Restart

When the system is in operation

OAI Memory Clear Restart

OFF-line Restart

•

PM (Line/Trunk Card) Make-Busy Restart

In this processing, the faulty PM (Line/Trunk Card) is isolated from the system and, at the same time,

the calls associated with that faulty PM (Line/Trunk Card) are released. No calls related to the faulty

PM (Line/Trunk Card) are processed and the system normally runs without the faulty PM (Line/Trunk

Card).

Data Copy Restart

In a system of dual CPU configuration, the RAM memory (including the data memory) is copied from

the ACT side CPU into the STBY side CPU, and ACT/STBY is changed over and monitor restart is

executed.

In the case of this restart processing, only the ACT side CPU and the STBY side CPU are changed

over without any effect on the current connections. However, no call processings are executed while

the restart processing is in progress (from copying until the end of the changeover).

3. HOW TO READ PRECAUTIONS, DIAGNOSTIC, AND FAULT REPAIR INFORMATION

3.1 Precaution about Diagnostic Procedure/Fault Repair Procedure

When performing diagnostic procedures/fault repair procedures, always adhere to the following actions:

(1) When replacing a circuit card with a spare, handle the circuit card using the Field Service Kit.

(a) To protect the circuit card from static electricity, wear a wrist strap before handling the circuit card.

(b) Before extracting the circuit card from its mounting slot, set its MB switch to the UP side (ON).

(2) When holding a circuit card by hand, wear gloves and be careful not to touch mounted parts, gold-plated

terminal, etc., on the circuit card.

The 3M Model 8012 Portable Field Service Kit, shown in Figure 2-19, is recommended as an effective

countermeasure against static electricity.

CHAPTER 2

Page 26

NDA-24300

Issue 1

SYSTEM MAINTENANCE OUTLINE

Connect ground wire to the Earth

terminal of the Module Group.

Place the Circuit

Card on a

conductive sheet.

Wrist Strap

Note: 3M is a registered trademark of Minnesota Mining and Manufacturing, Inc.

Figure 2-19 3M^®Model 8012 Portable Field Service Kit

Gold Plated Terminal

OFF

Circuit Card

OFF

Circuit Card

Note

Card Puller Tab

Plastic Bag

Note: Do not touch the Gold-Plated Terminal with bare hands.

Figure 2-20 How to Hold a Circuit Card

NDA-24300

CHAPTER 2

Page 27

Issue 1

SYSTEM MAINTENANCE OUTLINE

(3) When a circuit card appears to be faulty, check the following items before replacing it with a spare:

(a) Poor connector contact at the circuit card may be responsible for the fault. Repeat insertion and ex-

traction of the circuit card a few times. Clean the connector portion, and recheck for proper operation.

(b) Check the lead wires of vertically-mounted parts (resistors, capacitors, etc.) to ensure they have not

shorted each other or broken.

ified cross connection wires erroneously left unconnected.

(d) Check the ROMs to ensure proper seating in the IC socket. Figure 2-21 shows a leg that is bent and

not set in the socket.

A pin is bent, not

inserted in the socket.

ROM

SOCKET

Figure 2-21 How to Set the ROM in IC Socket

CHAPTER 2

Page 28

NDA-24300

Issue 1

SYSTEM MAINTENANCE OUTLINE

(4) How to clean the connector portion (gold-plated terminal):

(a) Dip the gold-plated terminal portion in the cleaning fluid for 3 to 5 seconds (only PA-XX type circuit

card), as shown in Figure 2-22.

Cleaning

Fluid

Circuit

Card

Container

Figure 2-22 How to Clean the Connector Portion

Note 1: Some of the parts are subject to damage if they come in contact with the cleansing liquid. Be careful

to allow only the connector portion (gold-plated terminal) to contact the cleaning liquid.

Note 2: Be sure to use fresh cleaning fluid (FREON or isopropyl alcohol).

(b) Using a soft cotton cloth, wipe both sides of the connector portion (gold-plated terminal) clean (only

PA-XX type circuit card), as shown in Figure 2-23.

gauze

Gold-plated terminal

Figure 2-23 How to Clean Gold-Plated Terminal

Note 1: Use cloth (gauze, etc.) to clean.

Note 2: After wiping, be careful not to leave lint on the surface of the circuit card.

(5) When a check on the flat cable or LT cable is directed in the tree, check the following items:

(a) Make a visual check to see if the connector is properly connected.

(b) Poor connector contact may be responsible for the fault. Repeat connection and disconnection a few

times, and check again to see if the connector is properly connected.

(6) When replacing the circuit card is directed in the tree, replace the circuit card with a spare as per Chapter 4.

(7) When multiple circuit cards appear to be faulty, before replacing them with spares, remount them (one at

a time) into their slots, to determine which cards should be replaced.

NDA-24300

CHAPTER 2

Page 29

Issue 1

SYSTEM MAINTENANCE OUTLINE

The following is an example where the fault was recovered after the replacement of circuit cards:

•

START

Set the 1st circuit card back into its mounting slot

If the fault recurs: Replace the circuit card.

Set the 2nd circuit card back into its mounting slot

If the fault recurs: Replace the circuit card.

Set the 3rd circuit card back into its mounting slot

If the fault recurs: Replace the circuit card.

If a circuit card is found to be faulty, send the faulty circuit card for repair.

The fault may be a temporary one, or due to poor contact of the circuit card. Observe the

situation for a while.

END

(8) When a fault recovery is completed, use the RALM command to clear all the alarm indications and

registered system messages. If required, restore temporary cross connections and transient data for testing

to the original ones.

3.2 How to Follow Diagnostic Procedure/Fault Repair Procedure

(a) Diagnostic Work

A fault diagnostic procedure by system message is explained in the “TREE” format on an individual

system message basis.

•

Proceed with judgment as to whether the fault status coincides with the indicated status, following

the sequence beginning from START.

How to proceed with the diagnosis work is explained in Figure 2-24.

STEP 1 Determine whether the fault coincides with the fault status (1) in Figure 2-24.

STEP 2 If the fault status does coincide, the fault is indicated by (2). Repair the fault by referring to the

relevant section in Chapter 5. Otherwise, proceed to (3).

STEP 3 Perform the work indicated by (3). The result of the work (3) is broken down as indicated by

(4).

STEP 4 Determine whether the result of work (3) coincides with the status indicated by (5). If so, the

fault(s) is/are indicated either by (6) or by (7). If not, proceed to the next Step.

CHAPTER 2

NDA-24300

Page 30

Issue 1

SYSTEM MAINTENANCE OUTLINE

STEP 5 Perform the work indicated by (8), and if the result of the work is the same as the status indi-

cated, the fault is indicated by (9). If the fault repair work indicated by (9) affects another nor-

mal line, recheck the work as indicated by (10).

(b) Fault Repair Procedure

A fault repair procedure is explained by means of “TREE” format in Chapter 5. The following ex-

plains how to follow the “TREE” format and proceed with designated work. See Figure 2-25.

•

Begin from START and proceed with the necessary repair work following the sequence.

When a faulty circuit card (or circuit cards) is suspected, replace the faulty circuit card with a spare

in accordance with the work procedure pertaining to that specific circuit card.

STEP 1 Replace the circuit card indicated by (A) with a spare and check it. Perform the detailed work

as per (B). If the fault status is beyond repair, proceed to the next step.

STEP 2 If the range of the fault or the system configuration is as indicated by (C), perform a check as

indicated by (D). If the fault status is beyond repair, proceed to the next step.

STEP 3 Replace the circuit card indicated by (E) with a spare and check it. The detailed procedure in-

dicated by (G) varies with the system configuration indicated by (F).

NDA-24300

CHAPTER 2

Page 31

Issue 1

SYSTEM MAINTENANCE OUTLINE

(2)

FAULT

START

(1)

(3)

When

: It is the fault of

Section No.

(Chapter 5)

(11)

(5)

Perform

FAULT SUPERVISION

(7)

When

(6)

(4)

FAULT

When

: It is the fault of

(Chapter 5)

(11)

Section No.

(8)

(9)

FAULT

with

performed

When

CHECK OF WORK

(10)

(Chapter 5)

(11)

Section No.

END

Note: (1):

Judgment of fault status

(2),(6),(7),(9): When the fault status coincides with the indication, the cause of the fault is indicated.

(11):

(3):

(4):

(5):

(8):

When repairing the fault, refer to the relevant section in Chapter 5.

Operating items for diagnosis

Branching of the result of the operation

Judgment of the status of the result of the operation

When operating method is unknown, refer to Chapter 6.

Figure 2-24 DiagnosticWork Items and Symbols Example

CHAPTER 2

NDA-24300

Page 32

Issue 1

SYSTEM MAINTENANCE OUTLINE

START

(A)

(C)

(B)

Check

When

(D)

Check

(E)

Check

(F)

(G)

When

(F)

END

Figure 2-25 Recovery Procedure Example

4. REPORTING FAULT TO NEC

When the cause of a fault is uncertain, make note of the situation involved and report it to NEC. When for-

warding faulty circuit cards to NEC, exercise caution to protect from static electricity.

4.1 Fault Reporting Method

The following three items must be included in the report without fail:

(1) Faulty situation (reports should be similar to “dial tone is not heard only on individual lines,” “incoming

C.O. line calls are not able to be terminated only to a specific ATTCON/DESKCON,” etc.)

•

Faulty phenomena

On lifting the handset, dial tone is not heard but side tone is heard, etc.

NDA-24300

CHAPTER 2

Page 33

Issue 1

SYSTEM MAINTENANCE OUTLINE

•

History of fault

When did the fault occur? What kind of repair procedure has been executed? Does the fault still exist

or not exist? etc.

•

Range of fault

Range of fault should be reported: Single line?, Specific trunk?, Specific circuit card?, Specific PIM?,

Whole system?, etc.

(2) Circuit Card Version Number, Program Name, and Program Package Version Number of the circuit card.

See Figure 2-26.

PA-

16LCBE

Circuit Card Name

Circuit Card Version Number

Program Name

SPA-

16LCBE

SP 785

A 6A

Program Package

Version Number

Front

Right View of Circuit Card

Figure 2-26 Circuit Card Version Number, Program Name, and Program Package Version Number

CHAPTER 2

NDA-24300

Page 34

Issue 1

SYSTEM MAINTENANCE OUTLINE

4.2 Forwarding Faulty Circuit Card Method

Send the faulty circuit card to the NEC agent to whom a request is made for a replacement card. Adhere

to the following procedure for sending the faulty circuit card:

(1) Insert connector covers onto the circuit card terminals.

(2) Put the circuit card into a static electricity protective bag.

(3) Pack the circuit card with air cap, etc.

(4) Set the circuit card into the cardboard box for that specific circuit card.

(5) If multiple circuit cards are to be sent, set each circuit card in a separate cardboard box and stuff the box

with shock absorbing material.

Note: When sending a faulty circuit card, put it in a static guard bag. To prevent damage, never place the cir-

cuit card in a vinyl bag or ship it without a protective bag.

NDA-24300

CHAPTER 2

Page 35

Issue 1

This page is for your notes.

CHAPTER 2

Page 36

NDA-24300

Issue 1

CHAPTER 3

SYSTEM MESSAGES

This chapter explains how to read and analyze system messages displayed during routine diagnosis, system op-

eration status controlling, and occurrence of a fault within the system. Table 3-1 provides a list of system mes-

sages.

Table 3-1 System Messages Lis t

MESSAGE NO.

SYSTEM MESSAGE

C-Level Infinite Loop

Memory Failure

B1-Level Infinite Loop (Permanent)

B1-Level Infinite Loop (Temporary)

2-T

2-U

2-V

2-W

Both TSW Failure (Permanent)

TSW Failure (Permanent)

Both TSW Write Failure

TSW Write Failure

Both TSW Clock Failure

TSW Clock Failure

Both PLO Failure

PLO Failure

Module Group Down Failure

TSW ACT Change Report

DLKC Data Transfer Failure (Permanent)

DLKC Data Transfer Failure (Temporary)

PLO Restore

AP-INT Data Transfer Failure (Permanent) Note 4

AP-INT Data Transfer Failure (Temporary) Note 4

IP Data Transfer Failure (Permanent) Note 4

IP Data Transfer Failure (Temporary) Note 4

NDA-24300

CHAPTER 3

Page 37

Issue 1

SYSTEM MESSAGES

MESSAGE NO.

Table 3-1 System Messages List (Continued)

SYSTEM MESSAGE

C-Level Infinite Loop (Permanent)

C-Level Infinite Loop (Temporary)

Lock-Up Failure (Permanent)

Lock-Up Failure (Temporary)

4-R

Both TSW Ready Failure

TSW Ready Failure

DLKC Ready Failure

IO Ready Failure for UAP Note 4

MUX Ready Failure

Both MUX Ready Failure

PCI Card Failure

PCI Card Failure Recovered

System Failure

RGU & Howler Failure

Line Load Control Start

Line Load Control Stop

Bad Call Notification

S T A -Test Connection Data

Emergency Control Start

Emergency Control Stop

Abnormal Call Duration Data

SMDR Output Buffer Overflow Alarm

SMDR Output Buffer Overflow Release

System Initialize With Data Load

CHAPTER 3

Page 38

NDA-24300

Issue 1

SYSTEM MESSAGES

Table 3-1 System Messages List (Continued)

SYSTEM MESSAGE

MESSAGE NO.

Cyclic Diagnosis Normal

Cyclic Diagnosis Information (Error Detected)

CCH C-Level Infinite Loop Failure (Permanent)

CCH C-Level Infinite Loop Failure (Temporary)

CCH Lock-Up Failure (Permanent)

CCH Lock-Up Failure (Temporary)

CCH B-Level Infinite Loop Failure (Permanent)

CCH B-Level Infinite Loop Failure (Temporary)

CCS Link Failure (Permanent)

CCS Link Failure (Temporary)

Restoration From CCS Link Failure

CCH Reset Interrupt Failure

Digital Line Warning

Digital Line Failure

NDA-24300

CHAPTER 3

Page 39

Issue 1

SYSTEM MESSAGES

MESSAGE NO.

Table 3-1 System Messages List (Continued)

SYSTEM MESSAGE

23-J

DRU Battery Operation

DRU Line Operation

Power Failure

VPS Failure (Temporary)

VPS Failure (Permanent)

VPS Restore

Inside Trunk All Busy

Virtual Tie Line Set Report

Virtual Tie Line Cancel Report

Virtual Tie Line Set Time Out

Sender Start Time Out

I/O Port Line OFF

I/O Port Line Restore

Hard Clock Failure

Hard Clock Restore

IOC Failure (Temporary)

IOC Failure (Permanent)

Station Exchanged Report

Day/Night Change Information

ATM Interface Warning Note 2

ATM Interface Failure Note 2

23-K

CHAPTER 3

Page 40

NDA-24300

Issue 1

SYSTEM MESSAGES

Table 3-1 System Messages List (Continued)

SYSTEM MESSAGE

MESSAGE NO.

23-L

23-P

23-Q

23-R

23-S

23-T

23-U

23-W

23-X

23-Y

23-Z

25-J

ATM Interface Recovered Note 2

DCH Back-Up Automatic Change Start/End

DCH Back-Up Manual Change Start/End

ATM Interface Change Report Note 2

FCCH Failure Note 1

FCCH Failure Recovered Note 1

FCCH Status Notice Note 1

FCCH Advancing Start Note 1

FCCH Advancing End Note 1

MUX Clock Failure

Both MUX Clock Failure

ZT Operation Start Note 3

ZT Set Up NG Note 3

25-K

25-L

25-M

25-N

27-C

27-D

ZT Fault Note 3

ZT Fault Recovery Note 3

ZT Carrier Fault Note 3

M A T L og

Call Trace

LAN Interface Error Report

LAN Interface Release Report

ATM Interface Port MB Key ON Note 2

ATM Interface Port MB Key OFF Note 2

SDT Interface Change Notify

Note 1: Refer to Fusion Network System Manual.

Note 2: Refer to the manual related to ATM.

Note 3: Refer to Wireless System Manual.

Note 4: Refer to the manual related to OAI.

NDA-24300

CHAPTER 3

Page 41

Issue 1

SYSTEM MESSAGES

Reset Interrupt

0-C

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the processor is reset due to a failure in the system.

1: XXXX XX00 XXXX 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀ ➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Self-CPU Restart Information

b0: 0/1 = -/Monitor Restart

b1: 0/1 = -Phase 1 Restart Note 1

b3: 0/1 = -/Initialization

b7 b6

b4 b3

b1 b0

b4: 0/1 = -/Data Copy Restart executed (for Dual-CPU system only)

b6: 0/1 = Program Load not executed/executed

b7: 0/1 = ACT/STBY (active system indication after restart)

➀ Mate-CPU Restart Information (FF

b0: 0/1 = -/Monitor Restart

b1: 0/1 = -Phase 1 Restart Note 1

H: not mounted)

b3: 0/1 = -/Initialization

b7 b6

b4 b3

b1 b0

b4: 0/1 = -/Data Copy Restart executed (for Dual-CPU system only)

b6: 0/1 = Program Load not executed/executed

b7: 0/1 = ACT/STBY (active system indication after restart)

➀ Related-call Release Result

b7: 0/1 = Call Release Processing after restart ->“Normal End”/“Abnormal

End”

Reference: See Chapter 5, Section 6.2 and Section 6.3, for the repair procedure.

CHAPTER 3

NDA-24300

Page 42

Issue 1

SYSTEM MESSAGES

0/1 = Office Data Load ->“Normal End”/“Abnormal End”

0/1 = Data Load ->“Normal End”/“Abnormal End”

0/1 = Individual Speed Calling data load is “Normal End”/“Abnormal

End”

➀ Data Load Result after restart

b0:

b1:

b2:

processing

b7 b6 b5 b4 b3 b2 b1 b0

b3:

b4:

0/1 = PS transfer service data load is “Normal End”/“Abnormal End”

0/1 = PS Name Display service data load is “Normal End”/“Abnormal

End”

b5:

b6:

b7:

b8:

0/1 = -/Network DM Load ->“Normal End”/“Abnormal End”

0/1 = -/Local DM Load ->“Normal End”/“Abnormal End”

0/1 = -/DM Non Load

0/1 = User Assign Soft Key data load is “Normal End”/“Abnormal

End”

b15

b11

b9 b8

b9:

0/1 = Number Sharing data load is “Normal End”/“Abnormal End”

b11: 0/1 = Call Block data load is “Normal End”/“Abnormal End”

Note 1: Phase 1 Restart is executed when initializing the system without disrupting the following two-way

connections that have already been established:

•

Basic two-way connections (STN-STN, STN-TRK, TRK-TRK)

Fixed connections

Two-way connections established on a Fusion link

For more details, see Chapter 6, Section 12.2.3.

Note 2: Number sharing data load also affects the data load of Dual Station Calling Over-FCCS.

NDA-24300

CHAPTER 3

Page 43

Issue 1

SYSTEM MESSAGES

CPU Clock Down

0-D

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a fault has occurred to the clock oscillator in the CPU.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀ ➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Self-CPU Restart Information

b0:

b3:

b4:

b5:

b7:

0/1=-/Monitor Restart

0/1=-/Initialization

0/1=Data Copy restart (for Dual-CPU system only)

0/1=-/MB control

0/1=ACT/STBY (active system indication after restart)

b5 b4 b3

➀ Male-CPU Restart Information (FF

b0:

b3:

b4:

b5:

b7:

0/1=-/Monitor Restart

0/1=-/Initialization

0/1=-/Data Copy restart (for Dual-CPU system only)

0/1=-/MB control

0/1=ACT/STBY (active system indication after restart)

H: not mounted)

b5 b4 b3

➀ Related Call Information

b7:

0/1=Released/Not released

Reference: See Chapter 5, Section 6.2, for the repair procedure.

CHAPTER 3

NDA-24300

Page 44

Issue 1

SYSTEM MESSAGES

C-Level Infinite Loop

0-E

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

C-level infinite loop is a state where a clock-level program, running under clock interrupt disable state, is in

an infinite loop. This message displays when the counter value to check the normality of the processing has

become abnormal.

0-E C-level Infinite Loop

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀

➀ ➀ ➀➀➀ ➀➀➀ ➀

➀

4: XXXX XXXX XXXX XXXX 5: XXXX XXXX XXXX XXXX 6: XXXX XXXX XXXX XXXX

➀

7: XXXX XXXX XXXX XXXX 8: XX00 0000 0000 0000 9: 0000 0000 0000 0000

➀

➀ Self-CPU Restart Information after

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MBcontrol

0/1 = ACT/STBY (active system indication after restart)

clock fault occurrence

b5 b4 b3

➀ Mate-CPU Restart Information

b7 b5 b4 b3

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MBcontrol

0/1 = ACT/STBY (active system indication after restart)

➀ NMI Factor

b7 b6 b5 b4 b3 b2 b1 b0

b0:

b1:

b2:

b3:

b4:

b5:

b6:

0/1 = -/Reset by Power On

0/1 = -/Watchdog Timer timeout

0/1 = ISAGT is mounted/ISGAT is not mounted

0/1 = -/OSC clock interrupt on ISGAT

0/1 = -/IO parity Alarm

0/1 = -/IO ready Alarm

0/1 = -/External NMI

Reference: See Chapter 5, Section 6.2, for the repair procedure.

NDA-24300

CHAPTER 3

Page 45

Issue 1

SYSTEM MESSAGES

➀ System Controlling Port B

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = Timer 2 Gate ON/OFF

0/1 = Speaker Gate ON/OFF

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = Parity Check Enable/MASK

0/1 = Channel Check Enable/MASK

0/1 = -/RAM Refresh Pulse Output State

0/1 = -/Timer 2 Output State

0/1 = -/Channel Check Error Detected

0/1 = -/Parity Error Detected

➀ CPU Alarm

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = -/ACT-side Processor CLK Alarm

0/1 = -/ACT-side Processor COP Alarm

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = -/ACT-side Processor MEM Alarm

0/1 = -/ACT-side Processor Emergency Timer Overflow

0/1 = -/STBY-side Processor CLK Alarm

0/1 = -/STBY-side Processor COP Alarm

0/1 = -/STBY-side Processor MEM Alarm

0/1 = -/STBY-side Processor Emergency Timer Overflow

➀ CPU Changeover Factors

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = -/CLK Alarm

0/1 = -/Emergency Timer Overflow

0/1 = -/SOFT EMA

0/1 = -/SOFT changeover

0/1 = -/Emergency Counter Overflow

0/1 = STBY/ACT

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = Dual/Single

0/1 = CPU #0/CPU#1

➀ System ALM

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = -/Main Power Alarm

0/1 = -/Power Alarm

0/1 = -/FUSE Alarm

0/1 = -/TEMP MJ Alarm

0/1 = -/TEMP MN Alarm

0/1 = -/Parity Alarm

0/1 = Card is not mounted/mounted

0/1 = -/EMA CLK Alarm

b7 b6 b5 b4 b3 b2 b1 b0

➀ Data Analyzed by NEC Engineers

CHAPTER 3

Page 46

NDA-24300

Issue 1

SYSTEM MESSAGES

Memory Failure

0-F

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a CPU memory read/write error occurs.

0-F Memory Failure

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀

➀ ➀ ➀➀➀ ➀➀➀ ➀

➀

4: XXXX XXXX XXXX XXXX 5: XXXX XXXX XXXX XXXX 6: XXXX XXXX XXXX XXXX

➀

7: XXXX XXXX XXXX XXXX 8: XX00 0000 0000 0000 9: 0000 0000 0000 0000

➀

➀ Information on Self-CPU Restart

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MBcontrol

0/1 = ACT/STBY (active system indication after restart)

after detection of a clock fault

b5 b4 b3

➀ Mate-CPU Restart Information

b7 b5 b4 b3

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MBcontrol

0/1 = ACT/STBY (active system indication after restart)

➀ NMI Factor

b7 b6 b5 b4 b3 b2 b1 b0

b0:

b1:

b2:

b3:

b4:

b5:

b6:

0/1 = -/Reset by Power On

0/1 = -/Watchdog Timer timeout

0/1 = ISGAT is mounted/ISGAT is not mounted

0/1 = -/OSC clock interrupt on ISGAT

0/1 = -/IO parity Alarm

0/1 = -/IO ready Alarm

0/1 = -/External NMI

Reference: See Chapter 5, Section 6.2, for the repair procedure.

NDA-24300

CHAPTER 3

Page 47

Issue 1

SYSTEM MESSAGES

➀ System Controlling Port B

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = Timer 2 Gate ON/OFF

0/1 = Speaker Gate ON/OFF

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = Parity Check Enable/MASK

0/1 = Channel Check Enable/MASK

0/1 = -/RAM Refresh Pulse Output State

0/1 = -/Timer 2 Output State

0/1 = -/Channel Check Error Detected

0/1 = -/Parity Error Detected

➀ CPU Alarm

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = -/ACT-side Processor CLK Alarm

0/1 = -/ACT-side Processor COP Alarm

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = -/ACT-side Processor MEM Alarm

0/1 = -/ACT-side Processor Emergency Timer Overflow

0/1 = -/STBY-side Processor CLK Alarm

0/1 = -/STBY-side Processor COP Alarm

0/1 = -/STBY-side Processor MEM Alarm

0/1 = -/STBY-side Processor Emergency Timer Overflow

➀ CPU Changeover Factors

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = -/CLK Alarm

0/1 = -/Emergency Timer Overflow

0/1 = -/SOFT EMA

0/1 = -/SOFT changeover

0/1 = -/Emergency Counter Overflow

0/1 = STBY/ACT

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = Dual/Single

0/1 = CPU #0/CPU #1

➀ System ALM

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = -/Main Power Alarm

0/1 = -/Power Alarm

0/1 = -/FUSE Alarm

0/1 = -/TEMP MJ Alarm

0/1 = -/TEMP MN Alarm

0/1 = -/Parity Alarm

0/1 = Card is not mounted/mounted

0/1 = -/EMA CLK Alarm

b7 b6 b5 b4 b3 b2 b1 b0

➀ Data Analyzed by NEC Engineers

CHAPTER 3

Page 48

NDA-24300

Issue 1

SYSTEM MESSAGES

B1-Level Infinite Loop (Permanent)

0-G

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a B-level infinite loop failure occurs.

0-F Memory Failure

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀ ➀ ➀➀

➀

4: XXXX XXXX XXXX XXXX 5: XXXX XXXX XXXX XXXX 6: XXXX XXXX XXXX XXXX

➀

7: XXXX XXXX XXXX XXXX 8: XX00 0000 0000 0000 9: 0000 0000 0000 0000

➀

➀ Information on Self-CPU Restart

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

after detection of a clock fault

b5 b4 b3

➀ Mate-CPU Restart Information

b7 b5 b4 b3

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MBcontrol

0/1 = ACT/STBY (active system indication after restart)

➀ B-level Infinite Loop

b0:

b1:

0/1 = -/B-level Infinite Loop

0/1 = -/Task Timer Timeout

b1 b0

➀ Data Analyzed by NEC Engineers

Reference: See Chapter 5, Section 6.2, for the repair procedure.

NDA-24300

CHAPTER 3

Page 49

Issue 1

SYSTEM MESSAGES

B1-Level Infinite Loop (Temporary)

0-H

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when, in the CPU program processing, the counter value to check the normality of the

processing has become abnormal.

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀➀➀ ➀

➀

4: XXXX XXXX XXXX XXXX 5: XXXX XXXX XXXX XXXX 6: XXXX XXXX XXXX XXXX

➀

7: XXXX XXXX XXXX XXXX 8: XX00 0000 0000 0000 9: 0000 0000 0000 0000

➀

➀ Self-CPU Restart Information

b0:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

b3:

b4:

b5:

b7:

b5 b4 b3

➀ Mate-CPU Restart Information (FF

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

H: not mounted)

b5 b4 b3

➀

b0:

b1:

0/1 = -/B-level Infinite Loop

0/1 = -/Task Timer Timeout

b1 b0

➀ Data Analyzed by NEC Engineers

Reference: See Chapter 5, Section 6.2 and Section 6.3, for the repair procedure.

CHAPTER 3

NDA-24300

Page 50

Issue 1

SYSTEM MESSAGES

Mate CPU Failure

0-I

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a fault, such as the Clock down or C-level infinite loop error, has occurred.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Mate-CPU Restart Information

b0:

b1:

b2:

b3:

0/1 = -/CPU clock down

0/1 = -/C-level infinite loop

0/1 = -/Memory error, Parity alarm

0/1 = -/Emergency Timer Overflow

b3 b2 b1 b0

Reference: See Chapter 5, Section 6.2 and Section 6.3, for the repair procedure.

NDA-24300

CHAPTER 3

Page 51

Issue 1

SYSTEM MESSAGES

Abnormal Interrupt

0-J

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the system is interrupting abnormally in the processing.

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀➀➀ ➀➀➀

➀

4: XXXX XXXX XXXX XXXX 5: XXXX XXXX XXXX XXXX 6: XXXX XXXX XXXX XXXX

➀

7: XXXX XXXX XXXX XXXX 8: XX00 0000 0000 0000 9: 0000 0000 0000 0000

➀

➀ Self-CPU Restart Information

b0:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

b3:

b4:

b5:

b7:

b5 b4 b3

➀ Mate-CPU Restart Information (FF

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

H: not mounted)

b5 b4 b3

➀

b0:

b3:

0/1 = -/Abnormal Interruption (Hardware)

0/1 = -/Program Exception

➀ Data Analyzed by NEC Engineers

Reference: See Chapter 5, Section 6.2 and Section 6.3, for the repair procedure.

CHAPTER 3

NDA-24300

Page 52

Issue 1

SYSTEM MESSAGES

Both TSW Failure (Permanent)

1-A

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when link information cannot be written into the switch memory of the TSW in both

systems.

1: XXXX XXXX XXXX XXXX 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ TSW system in which a fault is

b0:

0/1 = TSW No. 0/TSW No. 1

detected

➀ Status at the time of fault detection

b7 b6 b0

b0:

b6:

0/1 = TSW No. 0 system/TSW No. 1 system

Speech Path in ACT status

0/1 = No. 0 system/No. 1 system

➀➀Data Analyzed by NEC Engineers

Reference: See Chapter 5, Section 5.3, for the repair procedure.

NDA-24300

CHAPTER 3

Page 53

Issue 1

SYSTEM MESSAGES

TSW Failure (Permanent)

1-B

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when link information cannot be written into the switch memory of the TSW card in

one of the dual systems.

1: XXXX XXXX XXXX XXXX 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ TSW system in which a fault is

b0:

0/1 = TSW No. 0/TSW No. 1

detected

➀ Status at the time of fault detection

b7 b6 b0

b0:

b6:

0/1 = TSW No. 0/TSW No. 1

0/1 = Speech Path in ACT status

No. 0 system/No. 1 system

➀ Data Analyzed by NEC Engineers

Reference: See Chapter 5, Section 5.4, for the repair procedure.

CHAPTER 3

NDA-24300

Page 54

Issue 1

SYSTEM MESSAGES

Both TSW Write Failure

1-C

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the link information cannot be written into the switch memory of the TSW in both

systems.

1: XXXX XXXX XXXX XXXX 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ TSW system in which a fault is

b0:

0/1 = TSW No. 0/TSW No. 1

detected

➀

b0:

b6:

0/1 = TSW No. 0/TSW No. 1

0/1 = Speech Path in ACT status

No. 0 system/No. 1 system

b7 b6

➀ Data Analyzed by NEC Engineers

Reference: See Chapter 5, Section 5.2 and Section 6.2, for the repair procedure.

NDA-24300

CHAPTER 3

Page 55

Issue 1

SYSTEM MESSAGES

TSW Write Failure

1-D

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the link information cannot be written into the switch memory of the TSW card

in one of the dual systems.

1: XXXX XXXX XXXX XXXX 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ TSW system in which a fault is

b0:

0/1 = TSW No. 0/TSW No. 1

detected

➀ Status at the time of fault detection

b7 b6 b0

b0:

b6:

0/1 = TSW No. 0/TSW No. 1

0/1 = Speech Path ACT status

TSW No. 0 system is ACT/TSW No. 1 system is ACT

➀ Data Analyzed by NEC Engineers

Reference: See Chapter 5, Section 5.2, Section 5.4, and Section 6.2, for the repair procedure.

CHAPTER 3

NDA-24300

Page 56

Issue 1

SYSTEM MESSAGES

Both TSW Clock Failure

1-E

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the system detects a clock failure, such as TSW internal clock down or Frame

Head down, in both systems.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ TSW card in which a fault is

b0:

b1:

0/1 = -/TSW No. 0 system

0/1 = -/TSW No. 1 system

detected

b1 b0

➀ Clock status of No. 0 TSW

b7 b6 b2

b2:

b6:

b7:

0/1 = -/DTG output down

0/1 = -/External 32 ch Clock (PLO) No. 0 System down

0/1 = -/External 32 ch Clock (PLO) No. 1 System down

➀ Clock status of No. 1 TSW

Note: Refer to the meaning of ➀.

Reference: See Chapter 5, Section 5.3, for the repair procedure.

NDA-24300

CHAPTER 3

Page 57

Issue 1

SYSTEM MESSAGES

TSW Clock Failure

1-F

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the system detects a clock failure, such as TSW internal clock down or Frame

Head down, in one of the dual systems.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ TSW card in which a fault is

b0:

b1:

0/1 = -/TSW No. 0

0/1 = -/TSW No. 1 system

detected

b1 b0

➀ Clock status of No. 0 TSW

b7 b6 b2

b2:

b6:

b7:

0/1 = -/DTG output down

0/1 = -/External 32 ch Clock (PLO) No. 0 System down

0/1 = -/External 32 ch Clock (PLO) No. 1 System down

➀ Clock status of No. 1 TSW

Note: Refer to the meaning of ➀.

Reference: See Chapter 5, Section 5.4, for the repair procedure.

CHAPTER 3

NDA-24300

Page 58

Issue 1

SYSTEM MESSAGES

Both PLO Failure

1-O

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the system detects a fault, such as input clock all down or output clock down in

the PLO cards, at both sides.

1: XXXX XXXX XX00 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Detected PLO number

b0:

0/1 = No. 0 PLO/No. 1 PLO

➀ Valid Information bit for Scan Data

b0-b7: Bit position corresponding to the detected information in Scan Data 1

) is flagged “1”.

(

➀

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Valid Information bit for Scan Data

b0-b7: Bit position corresponding to the detected information in Scan Data 2

) is flagged “1”.

(

➀

b7 b6 b5 b4 b3 b2 b1 b0

Reference: See Chapter 4, Section 2.3.2 and Section 2.3.4, for the circuit card replacement procedure.

NDA-24300

CHAPTER 3

Page 59

Issue 1

SYSTEM MESSAGES

➀ Scan Data 1: Current Status of PLO

b0:

b1:

b2:

Clock status at time of detection

0/1 = STBY/ACT

Circuit Card status at time of detection

0/1 = PLO synchronizing/PLO self running or drift abnormal

0/1 = -/Input clock down

card

b7 b6 b5 b4 b3 b2 b1 b0

b3, b4:Route of Input clock

DCS Input Route

Route Of Input Clock

b5:

b6:

b7:

0/1 = -/PLO input all down

0/1 = -/PLO output down

0/1 = -/Drifting

➀ Scan Data 2: Current Status of PLO

b0:

b1:

b4:

0/1 = -/5msec Burst Clock down

0/1 = -/Frame Synchronization from SYNC card is down

0/1 = -/Internal OSC clock down

card

b1 b0

CHAPTER 3

Page 60

NDA-24300

Issue 1

SYSTEM MESSAGES

PLO Failure

1-P

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the system detects all the failures concerned with input clock down or output clock

down in the PLO card at the ACT side. When this message is indicated, the PLO card changeover executes.

Note: The No. 0 PLO card automatically changes over to No. 1. The changeover of No. 1 to No. 0 is not

automatic.

1: XXXX XXXX XX00 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Self-CPU Restart Information

b0:

0/1 = No. 0 PLO/No. 1 PLO

➀ Valid Information bit for Scan Data

b0-b7: Bit position corresponding to the detected information in Scan Data 1

) is flagged “1”.

(

➀

b7 b6 b5 b4 b3 b2 b1 b0

➀ Valid Information bit for Scan Data

b0-b7: Bit position corresponding to the detected information in Scan Data 2

) is flagged “1”.

(

➀

b7 b6 b5 b4 b3 b2 b1 b0

Reference: See Chapter 4, Section 2.3.2 and Section 2.3.4, for the circuit card replacement procedure.

NDA-24300

CHAPTER 3

Page 61

Issue 1

SYSTEM MESSAGES

➀ Scan Data 1: Status of PLO card

b0:

b1:

b2:

Clock status at time of detection

0/1 = STBY/ACT

Circuit card at time of detection

0/1 = PLO synchronizing/PLO self running or drifting

0/1 = -/Input clock down

b7 b6 b5 b4 b3 b2 b1 b0

b3, b4:Route of Input clock

DCS Input Route

Route Of Input Clock

b5:

b6:

b7:

0/1 = -/PLO input all down

0/1 = -/PLO output down

0/1 = -/Drifting

➀ Scan Data: Status of PLO card

b0:

b1:

b4:

0/1 = -/5msec Burst Clock down

0/1 = -/Frame Synchronization from SYNC card is down

0/1 = -/Internal OSC clock down

b1 b0

CHAPTER 3

Page 62

NDA-24300

Issue 1

SYSTEM MESSAGES

Module Group Down Failure

1-S

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a fault of the speech path system has occurred in a specific Module Group. The

specific Module Group is placed into make-busy state.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ MG number of fault detection

b0:

0/1 = Even-numbered MG/Odd-numbered MG

➀ Kind of failure

b0-b7: 00H/01H = -/ACT side TSW fault

b7 b6 b5 b4 b3 b2 b1 b0

➀ Speech Path/Clock System

b0:

b1:

ACT side speech path

0/1 = No. 0 system/No. 1 system

ACT side clock

b1 b0

0/1 = No. 0 system/No. 1 system

Reference: See Chapter 4, Section 2.3.2, for the circuit card replacement procedure.

NDA-24300

CHAPTER 3

Page 63

Issue 1

SYSTEM MESSAGES

TSW ACT Change Report

1-T

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the changeover of the TSW system is executed.

1: XXXX 0000 XXXX XXXX 2: 0000 0000 0000 0000 3: 0000 0000 XXXX XXXX

➀➀ ➀

➀➀ ➀ ➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ ACT side Speech Path (TSW) after

b0:

0/1 = No. 0 system/No. 1 system

changeover

➀ Reason for changeover

b7 b6 b5 b4 b3 b2 b1 b0

b7-b4

b3-b0

Card

Contents

TSW I/O Alarm

32ch Clock down, FH down

24ch Clock down, FH down

TSW SW Memory write failure

I/O Alarm release

32ch Clock down recovered,

FH down recovered

24ch Clock down recovered,

FH down recovered

TSW MBR key OFF

TSW ACT/STBY changeover by CMOD

command

MUX MUX circuit card Ready failure

MUX circuit card clock failure

CHAPTER 3

Page 64

NDA-24300

Issue 1

SYSTEM MESSAGES

➀~➀➀Status of ACT side TSW card

➀

MG00

MG02

MG04

MG06

MG01

MG03

MG05

MG07

b7 b6 b5 b4 b3 b2 b1 b0

b7-b4

b3-b0

b0-b3, b4-b7: The status of TSW card in each MG (00~07)

0000 = Normal

0001 = Abnormal (Impossible to make links)

➀~➀➀Status of ST-BY side TSW card

➀

MG00

MG02

MG04

MG06

MG01

MG03

MG05

MG07

b7 b6 b5 b4 b3 b2 b1 b0

b7-b4

b3-b0

b0-b3, b4-b7: The status of TSW card in each MG (00~07)

0000 = Normal

0001 = Abnormal (Impossible to make links)

NDA-24300

CHAPTER 3

Page 65

Issue 1

SYSTEM MESSAGES

DLKC Data Transfer Failure (Permanent)

1-U

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when DLKC data transfer failure (temporary), shown in message [1-V], occurs more

than 16 times an hour. At this time, the faulty DLKC card is down and its switching network automatically

changes over.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ System status of faulty DLKC card

b0:

0/1 = No. 0 system / No. 1 system

➀ Error Code

01H: Firmware fault

02H: Data transfer time out to DLKC

03H: No answer time out (at DLKC)

04H: Data parity error

b7 b6 b5 b4 b3 b2 b1 b0

➀ Details on Switching Network

b0:

b1:

Status of Speech Path System (including DLKC)

0/1 = No. 0 system is ACT/No. 1 system is ACT

Status of basic clock

b1 b0

0/1 = No. 0 system is ACT/No. 1 system is ACT

CHAPTER 3

Page 66

NDA-24300

Issue 1

SYSTEM MESSAGES

DLKC Data Transfer Failure (Temporary)

1-V

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a data sending error or no answer error occurs at the time of data transfer from

CPU to DLKC card.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ System status of faulty DLKC card

b0:

0/1 = No. 0 system / No. 1 system

➀ Error Code

01H: Firmware fault

02H: Data transfer time out to DLKC

03H: No answer time out (at DLKC)

04H: Data parity error

b7 b6 b5 b4 b3 b2 b1 b0

➀ Details on Switching Network

b0:

b1:

b7:

Status of Speech Path System (including DLKC)

0/1 = No. 0 system is ACT/No. 1 system is ACT

Status of basic clock

0/1 = No. 0 system is ACT/No. 1 system is ACT

Information on Reset of STBY DLKC Note

0/1 = - /STBY DLKC card was reset

b1 b0

Note: This data displays when the STBY DLKC card is detected as faulty.

NDA-24300

CHAPTER 3

Page 67

Issue 1

SYSTEM MESSAGES

PLO Restore

1-W

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a failure such as internal clock down occurred to PLO is restored.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Restoration of PLO fault

b0:

0/1 = PLO No. 0 system/PLO No. 1 system

➀ Current Status of PLO card

b0:

b1:

b2:

0/1 = Clock is in STBY side/ACT side

0/1 = PLO synchronizing/PLO self running or drifting

0/1 = -/Input clock down

b7 b6 b5 b4 b3 b2 b1 b0

b3, b4:Route of input clock (see the table below)

Connected With Primary

b4 b3

Connected With

External Clock

Oscillator (M-OSC)

No. 0 M-OSC

Route 0

Route 1

Route 2

Route 3

No. 1 M-OSC

–

b5:

b6:

b7:

0/1 = -/PLO input all down

0/1 = -/PLO output down

0/1 = -/Drifting

➀ Current Status of PLO card

b0:

b1:

b4:

0/1 = -/5msec clock down

0/1 = -/Frame Synchronization from SYNC card is down

0/1 = -/Internal OSC clock down

b1 b0

CHAPTER 3

Page 68

NDA-24300

Issue 1

SYSTEM MESSAGES

C-Level Infinite Loop (Permanent)

3-B

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a C-level program abnormal state is detected as permanent. When the Port Mi-

croprocessor (PM) on an LC/TRK card detects the abnormal state, the PM places the card into make-busy sta-

tus. If the failure occurs more than 15 times an hour, the system judges the failure as permanent and issues the

this system message.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Faulty Circuit Card Mounting

b0-b4: Group

b5-b6: Unit (0-3)

b7: Module Group (0/1)

Location

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 69

Issue 1

SYSTEM MESSAGES

C-Level Infinite Loop (Temporary)

3-C

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when C-level program is detected as abnormal by the Port Microprocessor (PM) mount-

ed on an LC/TRK card. If the failure occurs less than 15 times/hour, and a B-monitor/Initial restart executes

as the result, the failure is judged as temporary and this message is created.

1: XX0X 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Faulty Circuit Card Mounting

b0-b4: Group

b5-b6: Unit (0-3)

Location

b7:

Module Group (0/1)

b7 b6 b5 b4 b3 b2 b1 b0

➀ PM Restart Type

b0:

0/1 = B-monitor/Initial Restart Note

Note: B-monitor Restart: Ports whose link has already been established remain connected. Ports processing

a call-origination may be released.

Initial Restart: All ports on the circuit card are forcibly released to be placed in idle state.

CHAPTER 3

Page 70

NDA-24300

Issue 1

SYSTEM MESSAGES

Lock-Up Failure (Permanent)

3-D

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

At the periodic interval, the CPU sends diagnosis data to the Port Microprocessor (PM) on LC/TRK cards in

order to monitor the PM. If the CPU cannot receive the return data within a predetermined period of time, the

system displays this data. When the failure is detected more than 15 times per hour, the failure is judged as

permanent.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Faulty Circuit Card Location

b0-b4: Group

b5-b6: Unit (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

Module Group

0/1 = Even-numbered MG/Odd-numbered MG

Reference: See Chapter 5, Section 6.2, for the repair procedure.

NDA-24300

CHAPTER 3

Page 71

Issue 1

SYSTEM MESSAGES

Lock-Up Failure (Temporary)

3-E

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

At the periodic interval, the CPU sends diagnosis data to the Port Microprocessor (PM) on LC/TRK cards in

order to monitor the PM. If the CPU cannot receive the return data within a predetermined period of time, the

system displays this data. When the failure is detected less than 15 times per hour, the failure is judged as tem-

porary.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Faulty Circuit Card Location

b0-b4: Group

b5-b6: Unit (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

Module Group

0/1 = Even-numbered MG/Odd-numbered MG

➀ PM Restart Type

b0:

0/1 = B-monitor/Initial Restart

CHAPTER 3

Page 72

NDA-24300

Issue 1

SYSTEM MESSAGES

-48V Over Current

3-F

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when over current of the operating power (DC-48V) is supplied from the ATI/ELC cir-

term

cuit card to the Attendant Console/D

busy state and stops supplying power.

. When this fault occurs, the related circuit card is placed into make-

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty PM

b0-b4: Group

b5, b6:Unit

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 73

Issue 1

SYSTEM MESSAGES

Ground Failure

3-G

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a wire of the line between the LC circuit card and the telephone set is short-

circuited with ground.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty circuit card

b0-b2: Circuit No. (0-7)

b3-b7: Circuit card No. (0-31)

b7 b6 b5 b4 b3 b2 b1 b0

➀ Location of faulty circuit card

b0, b1:Unit No. (0-3)

b2-b7: MG No. (0-1)

b7 b6 b5 b4 b3 b2 b1 b0

Note: This message displays when the specific LC card providing the above function is used.

CHAPTER 3

Page 74

NDA-24300

Issue 1

SYSTEM MESSAGES

Digital Line Warning

3-H

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the DTI card detects an abnormal state of a digital line but this failure has no in-

fluence on the speech path. When the status worsens, the system issues [3-I] Digital Line Failure message.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of PM (LENS) with a

b0-b4: Group

b5, b6:Unit

fault

b7:

0/1 = Even-numbered MG/Odd-numbered MG

b7 b6 b5 b4 b3 b2 b1 b0

➀ Kind of fault

01H = Frame alignment loss occurs three times a day

02H = Bit error rate is over 10^-6

03H = Slip occurs twice a day

b7 b6 b5 b4 b3 b2 b1 b0

04H = Multiframe alignment loss occurs three times a day

08H = Fault detection on the CCIS Bch

➀ Time Slot No. of fault (This data is

valid only when the kind of fault is

08H.)

b0-b4: Time slot No. in which the digital line failure occurred (1-16, 17-31)

b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 75

Issue 1

SYSTEM MESSAGES

Digital Line Failure

3-I

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays after [3-H] Digital Line Warning lasts in the DTI card over the particular time. This

failure may cause a speech path fault to the DTI card.

1: XXXX 0000 XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀➀➀

➀➀➀ ➀➀➀ ➀➀➀ ➀➀➀

4: XXXX XXXX 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

➀➀➀ ➀➀➀

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty PM

b0-b4: Group

b5, b6:Unit

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

➀ Kind of fault

01H = Frame alignment loss occurs 100 times a day

03H = Slip occurs 50 times a day

04H = Multiframe alignment loss occurs 110 times a day

06H = Frame alignment loss lasts for 2 to 3 sec.

07H = Bit error rate is over 10^-4

b7 b6 b5 b4 b3 b2 b1 b0

09H = Warning signal (AIS) from the opposite office has been received for 1

sec. continuously.

0BH = Multiframe alignment loss lasts for 2 to 3 sec.

0FH = Digital Line is not restored

➀ Location of faulty circuit card (This

b3-b7: Group No.

data is valid when ➀➀is 0FH)

b7 b6 b5 b4 b3

➀ Location of faulty circuit card (This

b0, b1:Unit No.

b2-b7: MG No.

data is valid when ➀➀is 0FH)

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 76

NDA-24300

Issue 1

SYSTEM MESSAGES

Digital Line Restore

3-J

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a digital line fault is restored.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty line

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/odd-numbered MG

NDA-24300

CHAPTER 3

Page 77

Issue 1

SYSTEM MESSAGES

Both TSW Ready Failure

4-C

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a Ready Failure occurs in both systems as a result of the TSW card having a failure

or the card is not mounted properly.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Unit and MG number of fault

b0:

0/1 = TSW No. 0 system/TSW No. 1 system

detection

Note: When Ready Failure occurs in both systems, the [4-C]

message is separately issued twice: “0” displays in one

message, and “1” in the other message.

Reference: See Chapter 5, Section 5.3, for the repair procedure.

CHAPTER 3

Page 78

NDA-24300

Issue 1

SYSTEM MESSAGES

TSW Ready Failure

4-D

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a Ready Failure occurs in one of the dual systems because the TSW card fails or

the card is not mounted properly.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Unit and MG number of fault

b0:

0/1 = TSW No. 0 system/TSW No. 1 system

detection

Reference: See Chapter 5, Section 5.4, for the repair procedure.

NDA-24300

CHAPTER 3

Page 79

Issue 1

SYSTEM MESSAGES

DLKC Ready Failure

4-Q

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when I/O Ready Failure occurs on a DLKC card.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Details on faulty DLKC card

b0:

b7:

0/1 = No. 0 system/No. 1 system

0/1 = ACT/STBY

CHAPTER 3

Page 80

NDA-24300

Issue 1

SYSTEM MESSAGES

MUX Ready Failure

4-S

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MUX (PH-PC36) card has a Ready Failure in one of the dual systems. When

the card is not ready for service function because of the failure or because the card is not mounted properly,

the system creates this message.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Unit and MG number for MUX

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = -/MUX ready fault in even-numbered MG, Unit 0

0/1 = -/MUX ready fault in even-numbered MG, Unit 1

0/1 = -/MUX ready fault in even-numbered MG, Unit 2

0/1 = -/MUX ready fault in even-numbered MG, Unit 3

0/1 = -/MUX ready fault in odd-numbered MG, Unit 0

0/1 = -/MUX ready fault in odd-numbered MG, Unit 1

0/1 = -/MUX ready fault in odd-numbered MG, Unit 2

0/1 = -/MUX ready fault in odd-numbered MG, Unit 3

card with ready fault

b7 b6 b5 b4 b3 b2 b1 b0

➀ MG and system number for faulty

b0:

b1:

b2:

MG number for faulty MUX card

0/1 = Even number/Odd number

0/1 = Ready failure in MUX No. 0 system/Ready failure in MUX No.

1 system

ACT or STBY status of faulty MUX.

0/1 = ACT/STBY

MUX card

b2 b1 b0

Reference: See Chapter 5, Section 4.3 and Section 4.4, for the repair procedure.

NDA-24300

CHAPTER 3

Page 81

Issue 1

SYSTEM MESSAGES

Both MUX Ready Failure

4-T

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MUX (PH-PC36) card has a Ready Failure in both of the dual systems. When

the card is not ready for service function because of the failure or because the card is not mounted properly,

the system creates this system message.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Unit and MG number for MUX

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1 = -/MUX ready fault in even-numbered MG, Unit 0

0/1 = -/MUX ready fault in even-numbered MG, Unit 1

0/1 = -/MUX ready fault in even-numbered MG, Unit 2

0/1 = -/MUX ready fault in even-numbered MG, Unit 3

0/1 = -/MUX ready fault in odd-numbered MG, Unit 0

0/1 = -/MUX ready fault in odd-numbered MG, Unit 1

0/1 = -/MUX ready fault in odd-numbered MG, Unit 2

0/1 = -/MUX ready fault in odd-numbered MG, Unit 3

card with the ready fault

b7 b6 b5 b4 b3 b2 b1 b0

➀ MG and system number for faulty

b0:

b1:

b2:

MG number for faulty MUX card

0/1 = Even number/Odd number

0/1 = Ready failure in MUX No. 0 system/Ready failure in MUX No.

1 system Note 1

ACT or STBY status of the faulty MUX Note 2

0/1 = ACT/STBY

MUX card

b2 b1 b0

Note 1: Though this message indicates the Ready Failure in both systems, the information displayed here only

relates to the ACT-side MUX status. (Two messages are not displayed separately.)

Note 2: Fixed as “0 (=ACT).” See Note 1.

Reference: See Chapter 5, Section 4.3 and Section 4.4, for the repair procedure.

CHAPTER 3

Page 82

NDA-24300

Issue 1

SYSTEM MESSAGES

PCI Card Failure

4-U

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a PCI card failure occurs.

1: 0X0X 0X0X 0X00 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Fault detection on PCI card

b0:

b1:

b2:

b3:

0/1 = -/Error detection on PCI slot 0 (LANI-A)

0/1 = -/Error detection on PCI slot 1

0/1 = -/Error detection on PCI slot 2 (Not used)

0/1 = -/Error detection on PCI slot 3 (LANI-B)

b3 b2 b1 b0

➀➀Error status on PCI slot 0

b0:

b1:

0/1 = -/Physical connection error Note 1

0/1 = -/Hardware Fault Note 2

b1 b0

➀➀Error status on PCI slot 1

b0:

b1:

0/1 = -/Physical connection error Note 1

0/1 = -/Hardware Fault Note 2

b1 b0

➀➀Not used

NDA-24300

CHAPTER 3

Page 83

Issue 1

SYSTEM MESSAGES

➀➀Error status on PCI slot 3

b0:

b1:

0/1 = -/Physical connection error Note 1

0/1 = -/Hardware Fault Note 2

b1 b0

Note 1: Physical Connection Error

•

Ethernet cable is disconnected.

Ethernet cable has short-circuited.

Ethernet straight/cross cable selection error

Note 2: Hardware Fault

•

Transmitter failure

Controller lock-up

CHAPTER 3

Page 84

NDA-24300

Issue 1

SYSTEM MESSAGES

PCI Card Failure Recovered

4-V

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the PCI card, which was detected as faulty, is recovered.

1: 0X0X 0X0X 0X00 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Detection of PCI restoration

b0:

b1:

b2:

b3:

0/1 = -/Error detection on PCI slot 0 (LANI-A)

0/1 = -/Error detection on PCI slot 1

0/1 = -/Error detection on PCI slot 2 (Not used)

0/1 = -/Error detection on PCI slot 3 (LANI-B)

b3 b2 b1 b0

➀ Details on error restoration (PCI

b0:

0/1 = -/Physical connection error restoration Note

slot 0)

➀ Details on error restoration (PCI

b0:

0/1 = -/Physical connection error restoration Note

slot 1)

➀ Not used

NDA-24300

CHAPTER 3

Page 85

Issue 1

SYSTEM MESSAGES

➀ Details on error restoration (PCI

b0:

0/1 = -/Physical connection error restoration Note

slot 3)

Note: Physical Connection Error

•

Ethernet cable is disconnected.

Ethernet cable has short-circuited.

Ethernet straight/cross cable selection error

CHAPTER 3

Page 86

NDA-24300

Issue 1

SYSTEM MESSAGES

System Failure

6-A

Default Alarm:

NON

Default Grade:

Grade Modified:

(FIXED) NON

Lamp Modified:

(FIXED) 3

This message displays when any of the following faults are detected:

•

Power failure

Fuse blowing

In-Frame abnormal temperature

1: XX00 XXXX 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀ ➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Probable cause for failure

b0:

b1:

b2:

b3:

b4:

Input power (-48V) down/abnormal detected

PWR Supply abnormal detected

PWR Supply Fuse Blown detected

Abnormal temperature MJ (70ºC (158ºF))

Abnormal temperature MN (60ºC (140ºF))

b4 b3 b2 b1 b0

➀ Frame in which a fault is detected

b0-b3: Frame No. (0 Only)

0/1 = CPU is mounted/Not mounted

b4, b5:Frame Group No.

b6, b7:Kind of frame

00 = IMG

b7 b6 b5 b4 b3 b2 b1 b0

➀ Factor of failure

b0:

b1:

b2:

b3:

b4:

0/1 = -/OBP Alarm 0 side

0/1 = -/OBP Alarm 1 side

0/1 = -/OBP Alarm MISC side

0/1 = -/Power Alarm 0 side

0/1 = -/Power Alarm 1 side

b4 b3 b2 b1 b0

Reference: See Chapter 5, Section 8, for the repair procedure.

NDA-24300

CHAPTER 3

Page 87

Issue 1

SYSTEM MESSAGES

RGU & Howler Failure

6-B

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a fault in either the ringer or howler tone occurs in the PWR card.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Unit and MG number of fault

b0, b1:Unit No. (0-3)

detection

b2:

0/1 = Even-numbered MG/Odd-numbered MG

b2 b1 b0

➀ Kind of fault

b0:

b1:

0/1 = -/RGU (Ringing Unit) Fault

0/1 = -/Howler Fault

b1 b0

CHAPTER 3

Page 88

NDA-24300

Issue 1

SYSTEM MESSAGES

Line Load Control Start

6-C

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the CPU usage (occupancy) rate exceeds the value assigned to ASYD, SYS1, In-

dex 56, and the call origination from the pre-selected group of stations is restricted (i.e., Line Load Control is

set). This system message is always indicated as 0.

1: 0000 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

NDA-24300

CHAPTER 3

Page 89

Issue 1

SYSTEM MESSAGES

Line Load Control Stop

6-D

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the CPU usage (occupancy) rate becomes lower than the value assigned to ASYD,

SYS1, Index 57, and Line Load Control is cancelled. This system message is always indicated as 0.

1: 0000 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

CHAPTER 3

NDA-24300

Page 90

Issue 1

SYSTEM MESSAGES

Bad Call Notification

6-H

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays to indicate the result of Bad Call Notification.

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀➀➀ ➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀

b0-b3: Station number digit with the fault. (This data is always indicated as

“0” when Type of connection is 2 (ACD Trunk).)

b4-b7: Type of connection

0 = Station connection

1 = Trunk connection

b7 b6 b5 b4 b3 b2 b1 b0

2 = ACD Trunk connection

When type of connection is Station connection

➀ - ➀ Station number (see table)

b7 b6 b5 b4 b3 b2 b1 b0

b4-b7

b0-b3

➀

DC0

DC1

DC2

DC4

DC3

DC5

➀ The called station number

b0-b3: Number of digits for called station number

b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 91

Issue 1

SYSTEM MESSAGES

➀➀-➀ ➀➀Called station number (See

table)

b4-b7

b0-b3

b7 b6 b5 b4 b3 b2 b1 b0

➀

DC0

DC1

DC2

DC4

DC3

DC5

➀ Time Slot Number of Link 1

➀ Not used

¹¹Time Slot Number of Link 2

¹²Not used

When type of connection is Trunk connection

➀ - ➀ Station number (See table)

b4-b7

b0-b3

b7 b6 b5 b4 b3 b2 b1 b0

➀

DC0

DC1

DC2

DC4

DC3

DC5

➀ Remote Route No.

b0-b5: Route No. (1-63)

b6:

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = Data in OPRT is invalid/valid

b7:

0/1 = Internal trunk/External trunk

➀ Remote Route No.

b0-b3: OPRT Route No. (Over 64)

b3 b2 b1 b0

CHAPTER 3

Page 92

NDA-24300

Issue 1

SYSTEM MESSAGES

➀ Called Trunk No.

b0-b7: Trunk No.

b7 b6 b5 b4 b3 b2 b1 b0

➀ Not used

➀ Time Slot Number of Link 1

➀ Not used

¹¹Time Slot Number of Link 2

¹²Not used

NDA-24300

CHAPTER 3

Page 93

Issue 1

SYSTEM MESSAGES

When type of connection is ACD Trunk connection

b0-b7: ACD trouble kind

➀ ACD Trouble Kind

01H=ACD trunk trouble key Note 1

14H=ACD reset start Note 2

b7 b6 b5 b4 b3 b2 b1 b0

15H=Insufficient ACD memory

16H=Insufficient ACD call record

17H=Excessive business station on ACD calls

18H=Excessive calls queued

21H=Unknown Pilot No. called Note 3

24H=Illegal execution of ACD timeout procedure Note 4

30H=ACD pointer error detection and recovery Note 5

33H=ACDP reset completion Note 6

34H=Call recovery failure on unknown Pilot No. Note 7

37H=ACD Traffic (incoming) Capacity Over

99H=Illegal ACD processing-trace stored Note 4

Note 1: When “(ACD Trouble Kind)” is 01 Hex:

➀-➀➀Information on Calling Party

(a) Station

(b) Trunk

My Line No.

Route No. + Trunk No.

b4-b7

b0-b3

DC0

DC2

DC0

DC2

b4-b7

DC0

DC2

DC4

b0-b3

DC1

DC3

DC5

➀

Route No.

Trunk No.

DC1

Example: RT125,TKl0

01 25 00 l0

➀ ➀ Not Used

➀➀➀ Information on Calling Party

➀ ➀ ➀ ➀

Refer to ➀~➀

11 12

Information on Held Party or 3rd Station/Trunk in 3-Party Connection

Refer to ➀~➀

Note 2: When “(ACD Trouble Kind)” is 14 Hex:

➀➀ Issue of ACDP (First digit of decimal place)

➀➀ Issue of ACDP (Second digit of decimal place)

Note 3: When “(ACD Trouble Kind)” is 21 Hex:

➀~➀ Information on Calling Party

Refer to ➀~➀ of Note 1

➀ ➀ Not used

➀➀➀ Information on Unknown Pilot No.

Refer to ➀~➀, (a) Station of Note 1

CHAPTER 3

NDA-24300

Page 94

Issue 1

SYSTEM MESSAGES

Note 4: When “(ACD Trouble Kind)” is 24 or 99 Hex:

➀~➀ Not used

➀ ➀ Error Counter

Note 5: When “(ACD Trouble Kind)” is 30 Hex:

➀~➀ Pointer Address

➀

Not used

Error Kind

Note 6: When “(ACD Trouble Kind)” is 33 Hex:

➀

ACDP Data Memory

00 = Used

01 = Not used

➀

ACDP System Capacity

02 = 50 Agent Positions

04 = 200 Agent Positions

07 = 500 Agent Positions

12 = 900 Agent Positions

15 = 2,000 Agent Positions

Section 1.3.1, CPR Replacement Procedure

Note: If other data is output, the ACD system may not be working correctly. In this case, be sure to install the

ACD application again by using the MSVIP command.

Note 7: When “(ACD Trouble Kind)” is 34 Hex:

➀~➀ Information on Unknown Pilot No.

Refer to ➀~➀, (a) Station of Note 1

NDA-24300

CHAPTER 3

Page 95

Issue 1

SYSTEM MESSAGES

STA-Test Connection Data

6-I

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays to indicate the result of a designated connection test (Individual Trunk Access) from a

station.

1: XXXX XXXX XXXX XXXX 2: XXXX 00XX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀➀➀ ➀➀➀ ➀➀➀ ➀ ➀

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Test Item (b0-b3 is valid only for

b0-b2: Kind of Signal

Outgoing trunk test)

2 = Second Dial Tone

6 = Sender (Delay Dial Start)

7 = Sender (Wink Start)

0/1 = Data is invalid/valid

b7 b6 b5 b4 b3 b2 b1 b0

b3:

b4-b7: Test item

1 = Outgoing Trunk Test

2 = ORT/IRT Test

3 = Sender Test

4 = Digital Conference

5 = Tone Test

6 = Ringing Signal test

0 = Test NG

CHAPTER 3

Page 96

NDA-24300

Issue 1

SYSTEM MESSAGES

➀

b0-b3: Number of digits of the testing station No.

b4-b7: Error Numbers (see table below)

b7 b6 b5 b4 b3 b2 b1 b0

Error Numbers and Their Meanings

MEANING

ERROR NO.

---

The testing station is restricted from activating the service.

Route Number Error of the designated trunk

Trunk Number Error of the designated trunk

Trunk busy

Sender busy

SMDR failure

Call origination restriction

Trunk Number Error - when the trunk has been designated

by SHF.

Trunk busy - when the trunk has been designated by SHF.

Inter-digit timer expiration

Tone fault

Test Processing Error

➀-➀ Station number of testing station

(see table)

b4-b7

DC0

b0-b3

➀

DC1

DC2

DC4

DC3

DC5

➀ Tenant No.

b0-b3: Tenant No. (1-15)

b7: OP

0/1 = Data in OPTN ( )➀is invalid/valid

b3 b2 b1 b0

➀

➀➀OPTN data

b0-b3: Tenant No. (Over 15)

b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 97

Issue 1

SYSTEM MESSAGES

➀➀Tested Route No.

b0-b5: Route No. (1-63) Note

b6:

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = Data in OPRT ( ➀➀) is invalid/valid

b7:

0/1 = Internal trunk/External trunk

Note: When Logical Routes are assigned, Logical Route Numbers are displayed here.

➀ OPRT data

b7 b6 b5 b4 b3 b2 b1 b0

b0-b7: Route No. ( 64) Note

Note: When Logical Routes are assigned, Logical Route Numbers are displayed here.

➀➀(This data is not for Ringing Signal

b0-b7: Trunk No. for Outgoing trunk test, ORT/IRT Test, Sender Test and

Test)

Digital Conference test

Tone Slot No. for Tone Test

b7 b6 b5 b4 b3 b2 b1 b0

0 = DT

1 = SPDT

2 = RBT

4 = BT

3 = CRBT, CWT

5 = RBT

6 = SST, WT

8 = TRG

10 = CWRBT

7 = SDT

9 = SDTT

14 = MSC

Digit of Dialed Number (for test)

b0-b4: Dialed number digit sent by the test Trunk/Sender

b4 b3 b2 b1 b0

Dialed Number digit received by the test Register

Dialed Number (for test)

b7 b6 b5 b4 b3 b2 b1 b0

(a) Dialed Number sent by the test Trunk/Sender

(b) Dial Number received by the test Register

b4-b7

b0-b3

b4-b7

b0-b3

b4-b7

b0-b3

dc0

dc2

dc4

dc6

dc8

dc10

dc1

dc3

dc5

dc7

dc9

dc11

dc12

dc14

dc16

dc18

dc20

dc13

dc15

dc17

dc19

dc21

dc0

dc2

dc4

dc6

dc8

dc10

dc1

dc3

dc5

dc7

dc9

dc11

CHAPTER 3

Page 98

NDA-24300

Issue 1

SYSTEM MESSAGES

Emergency Call

6-J

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a call terminates to the Emergency Telephone.

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX 0000 0000 3: 0000 0000 0000 0000

11 12

➀➀➀ ➀➀➀ ➀➀➀

➀➀➀

➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ - ➀ Called Station (Emergency

➀ DC0 (1st digit)

Telephone) No. (ASCII Code)

➀ DC1 (2nd digit)

➀ DC2 (3rd digit)

b7 b6 b5 b4 b3 b2 b1 b0

➀ DC3 (4th digit)

➀ DC4 (5th digit)

➀ DC5 (6th digit)

➀ -

Calling Station No. (ASCII

Code)

DC0 (1st digit)

DC1 (2nd digit)

➀

➀ DC2 (3rd digit)

b7 b6 b5 b4 b3 b2 b1 b0

➀ DC3 (4th digit)

DC4 (5th digit)

12 DC5 (6th digit)

NDA-24300

CHAPTER 3

Page 99

Issue 1

SYSTEM MESSAGES

Emergency Control Start

6-L

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the LCR-Attendant Manual Override is set at the Attendant Desk Console.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Route Selection Time Pattern No.

b0-b2: Pattern No. (1-7)

assigned at Attendant Desk

Console

b2 b1 b0

Note: Route Selection Time Pattern 0-7 corresponds to TDPTN No. 0-7 in the AOPR command.

CHAPTER 3

Page 100

Issue 1

NDA-24300

SYSTEM MESSAGES

Emergency Control Stop

6-M

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the LCR-Attendant Manual Override is cancelled at the Attendant Desk Console.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Suspension of Emergency Control

b0:

Fixed 0.

0 = Outgoing call restriction is released by Attendant Desk Console

Note: Route Selection Patterns 0-7 corresponds to TDPTN No. 0-7 in the AOPR command.

NDA-24300

CHAPTER 3

Page 101

Issue 1

SYSTEM MESSAGES

Abnormal Call Duration Data

6-N

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the system detects abnormal duration in the line connection between the calling

and called party. When the calling and called party establish a line connection and continue the hook-up for an

extremely short or long period of time (predetermined by the ASYD command (SYS1 Index 45, 46)), this mes-

sage is created.

1: XXXX XXXX XXXX XX00 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XX00

➀➀➀ ➀➀➀ ➀➀➀ ➀➀

➀➀➀ ➀➀➀ ➀➀➀ ➀➀➀

➀➀➀ ➀➀➀ ➀➀➀ ➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Calling party information

b0-b3: Type of Calling party

0 = Station

1 = Attendant console

2 = Trunk

b3 b2 b1 b0

b7:

0/1 = Short/Long Time

➀➀Tenant No. of Calling/Called party (Hex.)

➀➀Calling party Information

When calling party is Station

Calling station No. (See table)

b4-b7

b0-b3

DC1

b3 b2 b1 b0

DC0

DC2

DC4

DC3

DC5

CHAPTER 3

Page 102

Issue 1

NDA-24300

SYSTEM MESSAGES

When calling party is ATTCON/DESKCON

Attendant/Desk console No. (See

table.)

b4- b7

b0-b3

b7 b6 b5 b4 b3 b2 b1 b0

DC0

DC1

When calling party is Trunk

Route No. and Trunk No. (See table.)

b0-b7

(a)

(b)

(c)

(d)

Route No. (Hex) Note

Trunk No. (Hex)

Note:

Route No. (a)

b0-b5: Route No. (1-63)

b6:

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = Data in OPRT is invalid/valid

b7:

0/1 = Internal trunk/External trunk

Route No. (b)

b0-b3: OPRT

Route No. (Over 64)

b3 b2 b1 b0

➀➀Called party information

b7 b3 b2 b1 b0

b0-b3:

00 = Station-to-Station call

01 = Outgoing call to outside

02 = Incoming call from outside

NDA-24300

CHAPTER 3

Page 103

Issue 1

SYSTEM MESSAGES

➀➀Called Party Information

Station to Station Call

(a) Type of called party

00 = Station

b4-b7

b0-b3

(a)

01 = Attendant Console

Tenant No.

b7 b6 b5 b4 b3 b2 b1 b0

DC0

DC2

DC4

DC1

DC3

DC5

OG Call to outside (IC Call from outside)

b4-b7

b0-b3

b0-b7

Route No. (Hex)

Trunk No. (Hex)

Route No. (Hex)

Trunk No. (Hex)

DC0

DC1

DC3

DC2

DC4

DC5

DC6

DC7

DC8

DC9

DC10

DC12

DC14

DC16

DC18

DC11

DC13

DC15

DC17

DC19

CHAPTER 3

Page 104

Issue 1

NDA-24300

SYSTEM MESSAGES

SMDR Output Buffer Overflow Alarm

6-O

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the SMDR output buffer usage rate has exceeded the value assigned to ASYD,

SYS1, Index 249.

1: XXXX XXXX 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Detail Information

b0-b3: FS

b4-b7: FE

b7 b6 b5 b4 b3 b2 b1 b0

This system message varies depending on the data.

FS FE

MEANING

(a)

SMDR output buffer usage rate exceeds the value

assigned by ASYD, SYS1, Index 249.

After SMDR output buffer usage rate exceeds the

value assigned by ASYD, SYS1, Index 249, usage

rate lowered less than the value assigned by Index

250.

(b)

(c)

Data output is impossible due to SMDR apparatus

failure.

(a) FS = 0, FE = 0/1

➀

b0:

0/1 = Data assigned by the ASYD, SYS1, Index 249, 250 is valid/

invalid

NDA-24300

CHAPTER 3

Page 105

Issue 1

SYSTEM MESSAGES

➀➀Buffer Usage Rate Assigned by

b0-b3: Units

b4-b7: Tens

ASYD, SYS1, Index 249

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Buffer Usage Rate Assigned by

b0-b3: Units

b4-b7: Tens

ASYD, SYS1, Index 250

b7 b6 b5 b4 b3 b2 b1 b0

(b) FS = 1, FE = 0

➀

b0:

Fault Grade by ALMG command

00 = NON CONT

10 = MN

01 = SUP

11 = MJ

b2 b1 b0

➀➀Overflow Rate

b0:

0/1 = -/100% Overflow

➀➀Overflow Rate

b4-b7: 1-9 = 10%-90% Overflow

b7 b6 b5 b4

CHAPTER 3

Page 106

Issue 1

NDA-24300

SYSTEM MESSAGES

➀ SMDR Group No.

b0-b3: SMDR Group No. to which failure occurred

b3 b2 b1 b0

➀➀Port No.

b0-b7: Port No. allocated for SMDR Group to which failure occurred (0-7)

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Not used

(d) FS = 3, FE = 0

➀

b0-b3: SMDR Group No. to which failure occurred

b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 107

Issue 1

SYSTEM MESSAGES

SMDR Output Buffer Overflow Release

6-P

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the SMDR output buffer usage rate has been lowered to less than the value as-

signed in the ASYD, SYS1, Index 250 after the rate exceeds the value assigned by Index 249.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Detail Information

b0-b7: 00H = After SMDR output buffer usage rate exceeds the value

assigned by ASYD, SYS1, Index 249, the rate lowered less than the

b7 b6 b5 b4 b3 b2 b1 b0

value assigned by Index 250.

CHAPTER 3

Page 108

Issue 1

NDA-24300

SYSTEM MESSAGES

System Initialize With Data Load

7-A

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays after the office data is loaded and system initialization has executed.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀

b0:

b1:

b2:

b3:

b4:

0/1 = IPL/PWR ON

0/1 = Load Key OFF/ON

0/1 = IPL KEY/MAT INITIAL

0/1 = Program load is executed/-

0/1 = -/Phase1 Restart Note 1

b4 b3 b2 b1 b0

➀➀Load Status

b0:

b1:

b2:

b3:

b4:

b5:

b6:

Office Data Load Status

0/1 = Load OK/NG

Call Forwarding Data Load Status

0/1 = Load OK/NG

Individual Speed Calling Data Load Status

0/1 = Load OK/NG

Wireless Call Forwarding Data Load Status

0/1 = Load OK/NG

Name Display Data Load Status

0/1 = Load OK/NG

Network DM Load Status

0/1 = Load OK/NG

Local DM Load Status

b7 b6 b5 b4 b3 b2 b1 b0

b15

b11

b9 b8

0/1 = Load OK/NG

b7:

b8:

0/1 = DM Load/Non Load

User assign Soft Key Data Load Status

0/1 = Load OK/NG

b9:

Number Sharing Data Load Status

0/1 = Load OK/NG Note 2

b11: Call Block Data Load Status

0/1 = Load OK/NG

NDA-24300

CHAPTER 3

Page 109

Issue 1

SYSTEM MESSAGES

Note 1: Phase1 Restart is executed when initializing the system without disrupting the following two-way con-

nections that have already been established:

•

Basic two-way connections (STN-STN, STN-TRK, TRK-TRK)

Fixed connections

Two-way connections established on a Fusion link

For more details, see Section Chapter 6, Section 12.2.3.

Note 2: Number Sharing data load also affects the data load of Dual Station Calling Over-FCCS.

CHAPTER 3

NDA-24300

Page 110

Issue 1

SYSTEM MESSAGES

System Initialize

7-B

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when system initialization is activated.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀

b2:

b3:

b4:

0/1 = IPL KEY/MAT INITIAL

0/1 = Program Load/Non Load

0/1 = -/Phase1 Restart Note

b4 b3 b2

Note: Phase1 Restart is executed when initializing the system without disrupting the following two-way

connections that have already been established:

•

Basic two-way connections (STN-STN, STN-TRK, TRK-TRK)

Fixed connections

Two-way connections established on a Fusion link

For more details, see Chapter 6, Section 12.2.3.

NDA-24300

CHAPTER 3

Page 111

Issue 1

SYSTEM MESSAGES

CPU MBR Key Turn ON

7-C

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MBR switch on the GATE card is turned ON at the time of CPU changeover

or speech path changeover.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Self-CPU Restart information

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

b5 b4 b3

➀➀Mate-CPU Restart information

b7 b5 b4 b3

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

CHAPTER 3

Page 112

Issue 1

NDA-24300

SYSTEM MESSAGES

CPU MBR Key Turn OFF

7-D

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MBR switch on the GATE card is turned OFF at the time of CPU changeover

or speech path changeover.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Self-CPU Restart information

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

b5 b4 b3

➀ Mate-CPU Restart information

b7 b5 b4 b3

b0:

b3:

b4:

b5:

b7:

0/1 = -/Monitor Restart

0/1 = -/Initialization

0/1 = -/Data Copy Restart (for Dual-CPU system only)

0/1 = -/MB control

0/1 = ACT/STBY (active system indication after restart)

NDA-24300

CHAPTER 3

Page 113

Issue 1

SYSTEM MESSAGES

TSW MBR Key Turn ON

7-E

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MBR switch on the TSW card is turned ON at CPU changeover or speech path

changeover.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ System status of TSW card

b0:

b7:

0/1 = No. 0 system/No. 1 system

Kind of Circuit Card

0/1 = SW12/GT19

CHAPTER 3

Page 114

Issue 1

NDA-24300

SYSTEM MESSAGES

TSW MBR Key Turn OFF

7-F

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MBR switch on the TSW card is turned OFF at CPU changeover or speech

path changeover.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ System status of TSW card

b0:

b7:

0/1 = No. 0 system/No. 1 system

Kind of Circuit Card

0/1 = SW12/GT09

NDA-24300

CHAPTER 3

Page 115

Issue 1

SYSTEM MESSAGES

TSW PLO Key Turn ON

7-G

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the PLO MBR switch is turned ON (UP).

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Information on PLO MBR

b0:

0/1=System 0/System 1

operation

CHAPTER 3

Page 116

Issue 1

NDA-24300

SYSTEM MESSAGES

TSW PLO Key Turn OFF

7-H

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the PLO MBR switch is turned OFF (DOWN).

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Information on PLO MBR

b0:

0/1=System 0/System 1

operation

NDA-24300

CHAPTER 3

Page 117

Issue 1

SYSTEM MESSAGES

ALMC MB Key Turn ON

7-I

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the EMA card is turned ON while extracting or inserting a

circuit card or at PM initialization. This message displays with the [7-J]: ALMC MB Key Turn OFF message.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Frame No. and its kind

b0-b3: Frame No. (0 only)

b4-b5: Frame Group No. (0 only)

b6-b7: Kind of Frame

b7 b6 b5 b4 b3 b2 b1 b0

00=IMG

CHAPTER 3

Page 118

Issue 1

NDA-24300

SYSTEM MESSAGES

ALMC MB Key Turn OFF

7-J

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the EMA card is turned OFF while extracting or inserting a

circuit card or at PM initialization.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Frame No. and its kind

b0-b3: Frame No. (0 only)

b4, b5:Frame Group No. (0 only)

b6, b7:Kind of Frame

b7 b6 b5 b4 b3 b2 b1 b0

00=IMG

NDA-24300

CHAPTER 3

Page 119

Issue 1

SYSTEM MESSAGES

PM MB Key Turn ON

7-K

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the line/trunk card is turned ON while extracting or inserting a

circuit card or at PM initialization.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Location of faulty Line/Trunk card

b0-b4: Circuit card No. (0-31)

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 120

Issue 1

NDA-24300

SYSTEM MESSAGES

PM MB Key Turn OFF

7-L

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the line/trunk card is turned OFF while extracting or inserting

a circuit card or at PM initialization.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty Line/Trunk card

b0-b4: Circuit card No. (0-31)

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 121

Issue 1

SYSTEM MESSAGES

NCU MB Key Turn ON

7-M

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the PFT card is turned ON while extracting or inserting a circuit

card, or at PM initialization.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Faulty PFT card No.

b0-b2: Circuit card No. (0-7)

b2 b1 b0

➀ Location of faulty PFT card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 122

Issue 1

NDA-24300

SYSTEM MESSAGES

NCU MB Key Turn OFF

7-N

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the PFT card is turned OFF while extracting or inserting a cir-

cuit card, or at PM initialization.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Faulty PFT card No.

b0-b2: Circuit card No. (0-7)

b2 b1 b0

➀ Location of faulty PFT card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 123

Issue 1

SYSTEM MESSAGES

Cyclic Diagnosis Normal

7-O

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

In a specific time cycle, the system allows a routine diagnosis in its hardware and software to determine if they

are operating properly. This message indicates that the system has been checked by the routine diagnosis pro-

gram and the result of the diagnosis is normal.

1: XXXX XXXX XXXX XXXX 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

Note

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Performed Diagnosis Item

[00H] Routine Diagnosis Start

[10H] Program Memory Verification Normal End

[20H] Data Memory Verification Normal End

b7 b6 b5 b4 b3 b2 b1 b0

[30H] TSW ACT/STBY Changeover Normal End

[40H] CPU ACT/STBY Changeover Normal End

[50H] No Trunk Ineffective Hold

[70H] Call Forwarding Memory Clear Normal End

[A0H] Periodic Back-up Normal End

[C0H] Detection of Remaining Link Normal End

Note: The data in this area will be diverse, according to the diagnosis specified in ➀. For details on each

item data, see the following pages.

CHAPTER 3

Page 124

Issue 1

NDA-24300

SYSTEM MESSAGES

[00H] Routine Diagnosis Start

1: 00XX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Performed Diagnosis Item

[00H] Routine Diagnosis Start

➀➀Pending Diagnosis Menu (SYS1,

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

0/1=-/Program Memory Verification

0/1=-/Data Memory Verification

Index 89)

0/1=-/TSW ACT/STBY Changeover

0/1=-/CPU ACT/STBY Changeover

0/1=-/Trunk Ineffective Hold Check

0/1=-/Trunk Ineffective Hold Detection

0/1=-/Call Forwarding Memory clear

0/1=-/IP ACT/STBY changeover

b7 b6 b5 b4 b3 b2 b1 b0

➀ Pending Diagnosis Menu (SYS1,

b0:

b1:

Not used

Periodic Back-up

Index 90)

b2-b7: Not used

b1 b0

NDA-24300

CHAPTER 3

Page 125

Issue 1

SYSTEM MESSAGES

[10H] Program Memory Verification Normal End

1: 10XX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Routine Diagnosis

[10H] Program Memory Verification Normal End

➀➀Information on HD

b0:

b1:

0/1 = -/HFC 0 is normal

0/1 = -/HFC 1 is normal

b1 b0

➀ Verification of Drive Number

b0:

b1:

b2:

b3:

0/1 = -/Drive Number 0

0/1 = -/Drive Number 1

0/1 = -/Drive Number 2

0/1 = -/Drive Number 3

b3 b2 b1 b0

CHAPTER 3

Page 126

Issue 1

NDA-24300

SYSTEM MESSAGES

[20H] Data Memory Verification Normal End

1: 20XX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Routine Diagnosis

[20H] Data Memory Verification Normal End

➀➀Verification of HD

b0:

b1:

0/1 = -/HFC 0 is normal

0/1 = -/HFC 1 is normal

b1 b0

➀ Verification of Data Memory

b7 b2 b1 b0

b0:

b1:

b2:

0/1 = -/Data Memory

0/1 = -/Local Data Memory

0/1 = -/Network Data Memory

NDA-24300

CHAPTER 3

Page 127

Issue 1

SYSTEM MESSAGES

[30H] TSW ACT/STBY Changeover Normal End

1: 30XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Routine Diagnosis

[30H] TSW ACT/STBY Changeover Normal End

➀➀Active TSW system after

b0:

0/1 = TSW No. 0 is ACT/

TSW No. 1 is ACT

changeover

CHAPTER 3

Page 128

Issue 1

NDA-24300

SYSTEM MESSAGES

[40H] CPU ACT/STBY Changeover Normal End

1: 40XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Routine Diagnosis

[40H] CPU ACT/STBY Changeover Normal End

➀➀Active CPU system

b0:

b1:

CPU

0/1 = #0 is ACT/#1 is ACT

TSW

b1 b0

0/1 = #0 is ACT/#1 is ACT

NDA-24300

CHAPTER 3

Page 129

Issue 1

SYSTEM MESSAGES

[50H] No Trunk Ineffective Hold

1: 50XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Routine Diagnosis

[50H] Trunk Ineffective Hold

➀ MG and Unit of No. of Trunk

b0:

b1:

b2:

b3:

b4:

b5:

b6:

b7:

Unit 0, Even-numbered MG

1 = No Trunk Ineffective Hold

Unit 1, Even-numbered MG

1 = No Trunk Ineffective Hold

Unit 2, Even-numbered MG

1 = No Trunk Ineffective Hold

Unit 3, Even-numbered MG

1 = No Trunk Ineffective Hold

Unit 0, Odd-numbered MG

1 = No Trunk Ineffective Hold

Unit 1, Odd-numbered MG

1 = No Trunk Ineffective Hold

Unit 6, Odd-numbered MG

1 = No Trunk Ineffective Hold

Unit 3, Odd-numbered MG

1 = No Trunk Ineffective Hold

Ineffective Hold

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 130

Issue 1

NDA-24300

SYSTEM MESSAGES

[70H] Call Forwarding Memory Clear Normal End

1: 7000 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Routine Diagnosis

[70H] Call Forwarding Memory Clear Normal End

NDA-24300

CHAPTER 3

Page 131

Issue 1

SYSTEM MESSAGES

[A0H] Periodic Back-up Normal

1: A0XX XX00 0000 XX00 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Routine Diagnosis

[A0H] Periodic Back-up Normal

➀➀Information on Periodic Backup

b0:

b1:

0/1 = HFD0 Normal end/Abnormal end

0/1 = HFD1 Normal end/Abnormal end

Normal End

b1 b0

➀ Backup Data to No. 0 system

b0:

b1:

b2:

b3:

b4:

b5:

b6:

0/1 = -/Individual Speed Calling Data

0/1 = -/Call Forwarding Data

0/1 = -/RCF

0/1 = -/Name Display Data

0/1 = -/User Assign Soft Key Data

0/1 = -/Number Sharing Data Note

0/1 = -/Call Block Data

b7 b6 b5 b4 b3 b2 b1 b0

➀ Backup Data to No. 1 system

b0:

b1:

b2:

b3:

b4:

b5:

b6:

0/1 = -/Individual Speed Calling Data

0/1 = -/Call Forwarding Data

0/1 = -/RCF

0/1 = -/Name Display Data

0/1 = -/User Assign Soft Key Data

0/1 = -/Number Sharing Data Note

0/1 = -/Call Block Data

b7 b6 b5 b4 b3 b2 b1 b0

Note: Number Sharing data load also affects the data load of Dual Station Calling Over-FCCS.

CHAPTER 3

NDA-24300

Page 132

Issue 1

SYSTEM MESSAGES

[C0H] Detection of Remaining Link Normal End

1: C0XX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Performed Diagnosis Item

[C0H] Detection of Remaining Link Normal End

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 133

Issue 1

SYSTEM MESSAGES

Cyclic Diagnosis Information (Error Detected)

7-P

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

In a specific time cycle, the system allows a routine diagnosis in its hardware and software to determine if they

are operating properly. This message indicates that the system has been checked by the routine diagnosis pro-

gram and the result of the diagnosis is not normal.

1: XXXX XXXX XXXX XXXX 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

Note

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Detected Error Item

[10H] Program Memory Verification Discrepancy

[11H] Program Memory Verification Impossible (HFD Fault)

[12H] Program Memory Verification Impossible (Fault at CPU side)

b7 b6 b5 b4 b3 b2 b1 b0

[20H] Data Memory Verification Discrepancy

[21H] Data Memory Verification Impossible (HFD Fault)

[30H] TSW ACT/STBY Changeover Failure

[31H] TSW ACT/STBY Changeover Failure (MUX Fault)

[41H] CPU ACT/STBY Changeover Failure (Single CPU System)

[42H] CPU ACT/STBY Changeover Failure (DM Verification NG)

[43H] CPU ACT/STBY Changeover Failure (PCI Fault)

[44H] CPU ACT/STBY Changeover Failure (Changeover NG or CPU

RAM Copy NG)

[50H] Trunk Ineffective Hold Detected

[51H] Trunk Ineffective Hold Detected and Released

[52H] Trunk Ineffective Hold Detected Impossible

[70H] Call Forwarding Memory Clear NG

[A0H] Periodic Backup Abnormal End

[C0H] Detection of Remaining Link Abnormal End

(for Release 4 or later)

Note: The data in this area will be diverse, according to the diagnosis specified in ➀. For details on each

item data, see the following pages.

CHAPTER 3

Page 134

Issue 1

NDA-24300

SYSTEM MESSAGES

[10H] Program Memory Verification Discrepancy

1: 1000 XXXX XXXX XXXX 2: XXXX 0000 0000 0000 3: 0000 0000 0000 0000

➀

➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[10H] Program Memory Verification Discrepancy

Diagnosis

➀➀Verification of HFD number

b0:

b1:

0/1 = -/HFD 0

0/1 = -/HFD 1

b1 b0

➀➀Verification of Drive Number

b0:

b1:

b2:

b3:

0/1 = -/Drive Number 0

0/1 = -/Drive Number 1

0/1 = -/Drive Number 2

0/1 = -/Drive Number 3

b3 b2 b1 b0

➀➀Data analyzed by NEC Engineers

NDA-24300

CHAPTER 3

Page 135

Issue 1

SYSTEM MESSAGES

[11H] Program Memory Verification Impossible (HFD Fault)

1: 11XX XXXX XXXX 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

➀➀ ➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[11H] Program Memory Verification Impossible (HFC Fault)

Diagnosis

➀➀Verification Impossible of HD

b0:

b1:

0/1 = -/HFC 0

0/1 = -/HFC 1

b1 b0

➀➀Error Type

00H: HD Processing NG

01H: HD Not Connected

02H: HD Busy

b7 b6 b5 b4 b3 b2 b1 b0

03H: HD Fault (Fault processing/Not equipment, etc.)

04H: Transfer NG

05H: Response Timeout

➀➀Data analyzed by NEC Engineers

➀➀Error Drive

b0:

b1:

b2:

b3:

0/1 = -/Drive Number 0

0/1 = -/Drive Number 1

0/1 = -/Drive Number 2

0/1 = -/Drive Number 3

b3 b2 b1 b0

CHAPTER 3

Page 136

Issue 1

NDA-24300

SYSTEM MESSAGES

[12H] Program Memory Verification Impossible (Fault at CPU side)

1: 12XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[12H] Program Memory Verification Impossible (Fault at CPU side)

Diagnosis

➀➀Cause for suspension of Program

01H: CPU-to-CPU communication failed

02H: Check sum file copy failed

Memory Verification (Error Code)

b1 b0

NDA-24300

CHAPTER 3

Page 137

Issue 1

SYSTEM MESSAGES

[20H] Data Memory Verification Discrepancy

1: 20XX XX00 XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: 0000 0000 0000 0000

➀➀➀ ➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[20H] Data Memory Verification Discrepancy

Diagnosis

➀➀Verification of HFC

b0:

b1:

0/1 = -/HFC 0 is normal

0/1 = -/HFC 1 is normal

b1 b0

➀➀ Verification of Data Memory

b0:

b1:

b2:

0/1 = -/Present Data Memory (DM)

0/1 = -/Local Data Memory (LDM)

0/1 = -/Network Data Memory (NDM)

b2 b1 b0

➀➀Data analyzed by NEC Engineers

CHAPTER 3

Page 138

Issue 1

NDA-24300

SYSTEM MESSAGES

[21H] Data Memory Verification Impossible (HFC Fault)

LDM

NDM

1: 21XX XX00 XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: 0000 0000 0000 0000

➀➀➀ ➀ ➀➀➀ ➀➀➀

➀➀➀ ➀➀➀ ➀➀➀ ➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[21H] Data Memory Verification Impossible (HFC Fault)

Diagnosis

➀➀HFC Impossible Verification

b0:

b1:

0/1 = -/HFC 0 is abnormal

0/1 = -/HFC 1 is abnormal

b1 b0

➀➀Verification of Data Memory

b0:

b1:

b2:

0/1 = -/Data Memory (DM)

0/1 = -/Local Data Memory (LDM)

0/1 = -/Network Data Memory (NDM)

b2 b1 b0

➀➀Error Type

00H: HD Processing NG

01H: HD Not Connected

02H: HD Busy

b7 b6 b5 b4 b3 b2 b1 b0

03H: HD Fault (Fault processing/Not equipment etc.)

04H: Transfer NG

05H: Response Timeout

➀➀Single Code

51H: Data Transfer starts

53H: File Transfer starts

55H: Data Load

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 139

Issue 1

SYSTEM MESSAGES

➀➀Data analyzed by NEC Engineers

➀➀Error Drive

b0:

b1:

b2:

b3:

0/1 = -/Drive Number 0

0/1 = -/Drive Number 1

0/1 = -/Drive Number 2

0/1 = -/Drive Number 3

b3 b2 b1 b0

Note: When ➀ (Error Type) is 00H, ➀➀Signal Code, ➀➀and ➀➀Error Drive are valid.

CHAPTER 3

Page 140

Issue 1

NDA-24300

SYSTEM MESSAGES

[30H] TSW ACT/STBY Changeover Failure

1: 30XX XXXX XXXX XXXX 2: XXXX 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀➀➀ ➀➀➀

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Detected Error Item

[30H] TSW ACT/STBY Changeover Failure

➀ Active TSW No.

b0:

0/1=TSW #0 is ACT/#1 is ACT

➀-➀ MUX card (ACT-side) linkage

As shown in the following table, each bit represents the Unit No. allocated

for each MUX card in position. When “1” is set, the corresponding MUX

card (status: ACT) has a functional failure or is not mounted in the proper

location.

condition

b7 b6 b5 b4 b3 b2 b1 b0

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

➀

MG1

MG0

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG3

MG2

0: -

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

1: MUX connection error

(functional fault/not

mounted)

MG5

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG4

MG7

MG6

NDA-24300

CHAPTER 3

Page 141

Issue 1

SYSTEM MESSAGES

➀-➀➀MUX card (STBY) linkage

As shown in the following table, each bit represents the Unit No. allocated

for each MUX card in position. When “1” is set, the corresponding MUX

card (status: STBY) has a functional failure or is not mounted in the proper

location.

condition

b7 b6 b5 b4 b3 b2 b1 b0

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

➀

MG1

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG0

MG3

MG2

0: -

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

1: MUX connection error

(functional fault/not

mounted)

MG5

MG4

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG7

MG6

CHAPTER 3

Page 142

Issue 1

NDA-24300

SYSTEM MESSAGES

[31H] TSW ACT/STBY Changeover Failure (MUX Fault)

1: 31XX XXXX XXXX XXXX 2: XXXX 0000 0000 0000 3: 0000 0000 0000 0000

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

Detected Error Item

Active TSW No.

[31H] TSW ACT/STBY Changeover Failure (MUX Fault)

b0:

0/1=TSW #0 is ACT/#1 is ACT

MUX card (ACT-side) linkage

condition

As shown in the following table, each bit represents the Unit No. allocated

for each MUX card in position. When “1” is set, the corresponding MUX

card (status: ACT) has a functional failure or is not mounted in the proper

location.

b7 b6 b5 b4 b3 b2 b1 b0

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG1

MG0

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG3

MG2

0: -

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

1: MUX connection error

(functional fault/not

mounted)

MG5

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG4

MG7

MG6

NDA-24300

CHAPTER 3

Page 143

Issue 1

SYSTEM MESSAGES

➀-➀➀MUX card (STBY) linkage

As shown in the following table, each bit represents the Unit No. allocated

for each MUX card in position. When “1” is set, the corresponding MUX

card (status: STBY) has a functional failure or is not mounted in the proper

location.

condition

b7 b6 b5 b4 b3 b2 b1 b0

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

➀

MG1

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG0

MG3

MG2

0: -

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

1: MUX connection error

(functional fault/not

mounted)

MG5

MG4

Unit 3 Unit 2 Unit 1 Unit 0 Unit 3 Unit 2 Unit 1 Unit 0

MG7

MG6

CHAPTER 3

Page 144

Issue 1

NDA-24300

SYSTEM MESSAGES

[41H] CPU ACT/STBY Changeover Failure

1: 41XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Error detection by Routine

[41H] CPU ACT/STBY Changeover Failure

Diagnosis

➀ ACT system after changeover

b0:

b1:

CPU

0/1 = #0 is ACT/#1 is ACT

TSW

b1 b0

0/1 = #0 is ACT/#1 is ACT

NDA-24300

CHAPTER 3

Page 145

Issue 1

SYSTEM MESSAGES

[42H] CPU ACT/STBY Changeover Failure (DM Verification NG or PM Verification NG)

1: 42XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[42H] CPU ACT/STBY Changeover Failure

Diagnosis

(DM Verification NG)

➀ ACT system after changeover

b0:

b1:

CPU

0/1 = #0 is ACT/#1 is ACT

TSW

b1 b0

0/1 = #0 is ACT/#1 is ACT

CHAPTER 3

Page 146

Issue 1

NDA-24300

SYSTEM MESSAGES

[43H] CPU ACT/STBY Changeover Failure (PCI Fault)

1: 43XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[43H] CPU ACT/STBY Changeover Failure (PCI Fault)

Diagnosis

➀ ACT system after changeover

b0:

b1:

CPU

0/1 = #0 is ACT/#1 is ACT

TSW

b1 b0

0/1 = #0 is ACT/#1 is ACT

NDA-24300

CHAPTER 3

Page 147

Issue 1

SYSTEM MESSAGES

[44H] CPU ACT/STBY Changeover Failure (Changeover NG or CPU RAM Copy NG)

1: 44XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Error detection by Routine

[44H] CPU ACT/STBY Changeover Failure

Diagnosis

Changeover NG or CPU RAM Copy NG)

➀➀ACT system after changeover

b0:

b1:

CPU

0/1 = #0 is ACT/#1 is ACT

TSW

b1 b0

0/1 = #0 is ACT/#1 is ACT

CHAPTER 3

Page 148

Issue 1

NDA-24300

SYSTEM MESSAGES

[50H] Trunk Ineffective Hold Detected

1: 50XX 00XX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀➀➀

➀

4: XXXX XXXX XXXX XXXX 5: XXXX XX00 0000 0000 6: 0000 0000 0000 0000

➀

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[50H] Trunk Ineffective Hold Detected

Diagnosis

➀➀LENS of Trunk Ineffective Hold

(MG, U)

0 = Unit 0

1 = Unit 1

0 = Unit 2

b2 b1 b0

1 = Unit 3

b2:

0/1 = Even No./Odd No. Module

➀➀LENS of Ineffective Hold Trunk (G, LV)

Group No.

1: 500X 00XX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

Group

Number

13 14

15 16

17 18

19 20

11 12

➀ ➀➀➀ ➀➀➀

➀➀➀ ➀➀➀ ➀➀➀

4: XXXX XXXX XXXX XXXX 5: XXXX XX00 0000 0000 6: 0000 0000 0000 0000

27 28

29 30

21 22

23 24

25 26

7: 0000 0000 0000 0000 8: 000 0000 0000 0000 9: 0000 0000 0000 0000

<Level>

Level

0/1 = -/Ineffectively held

G30

G31

NDA-24300

CHAPTER 3

Page 149

Issue 1

SYSTEM MESSAGES

[51H] Trunk Ineffective Hold Detected and Released

1: 50XX 00XX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀➀➀

➀

4: XXXX XXXX XXXX XXXX 5: XXXX XX00 0000 0000 6: 0000 0000 0000 0000

➀

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[51H] Trunk Ineffective Hold Detected and Released

Diagnosis

➀➀LENS of Trunk Ineffective Hold

Detected and Released (MG, U)

0 = Unit 0

1 = Unit 1

0 = Unit 2

b2 b1 b0

1 = Unit 3

b2:

0/1 = Even No./Odd No. Module

➀➀LENS of Ineffective Hold Trunk (G, LV)

Group No.

1: 500X 00XX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

Group

Number

13 14

15 16

17 18

19 20

11 12

➀ ➀➀➀ ➀➀➀

➀➀➀ ➀➀➀ ➀➀➀

4: XXXX XXXX XXXX XXXX 5: XXXX XX00 0000 0000 6: 0000 0000 0000 0000

27 28

29 30

21 22

23 24

25 26

7: 0000 0000 0000 0000 8: 000 0000 0000 0000 9: 0000 0000 0000 0000

<Level>

Level

0/1 = -/Ineffectively held

G30

G31

CHAPTER 3

Page 150

Issue 1

NDA-24300

SYSTEM MESSAGES

[52H] Trunk Ineffective Hold Detected Impossible

1: XX00 XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Error detection by Routine

[52H] Trunk Ineffective Hold Detected Impossible

Diagnosis

➀ Cause for suspended detection of

Trunk Ineffective Hold

1 = CPU to detect is abnormal

0 = Data transfer error

1 = No Answer error

b1 b0

NDA-24300

CHAPTER 3

Page 151

Issue 1

SYSTEM MESSAGES

[70H] Call Forwarding Memory Clear NG

1: 7000 XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error detection by Routine

[70H] Call Forwarding Memory Clear NG

Diagnosis

➀➀Cause for which Transfer Memory

was stopped

1 = CPU is abnormal

0 = Data Transfer error

b1 b0

CHAPTER 3

Page 152

Issue 1

NDA-24300

SYSTEM MESSAGES

[A0H] Periodic Backup Abnormal End

1: A0XX XX00 XXXX XX00 2: XXXX XXXX XXXX XX00 3: 0000 0000 0000 0000

➀➀➀ ➀ ➀➀➀ ➀

➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Error detection by Routine

[A0H] Periodic Backup Abnormal End

Diagnosis

➀➀Information of Periodic Backup

b0:

b1:

0/1 = HFD 0 Normal end/Abnormal end

0/1 = HFD 1 Normal end/Abnormal end

Abnormal End

b1 b0

➀ Backup Data to No. 0 system

b0:

b1:

b2:

b3:

b4:

b5:

b6:

0/1 = -/Individual Speed Calling Data

0/1 = -/Call Forwarding Data

0/1 = -/RCF

0/1 = -/Name Display Data

0/1 = -/User Assign Soft Key Data

0/1 = -/Number Sharing Data Note

0/1 = -/Call Block Data

b7 b6 b5 b4 b3 b2 b1 b0

➀ Error Code of No. 0 system HD

21H:

40H~47H:

53H:

b7 b6 b5 b4 b3 b2 b1 b0

Parameter

57H:

59H~5BH:

80H~84H:

A0H:

A2H~A6H:

BDH:

HD Fault

C0H:

01H:

02H:

Failed installation

HD being used by another program

HD not equipped

Note: Number Sharing data load also affects the data load of Dual Station Calling Over-FCCS.

NDA-24300

CHAPTER 3

Page 153

Issue 1

SYSTEM MESSAGES

➀➀Error Status of No. 0 system HD

Error occurs;

b0:

b1:

b2:

b3:

0/1 = -/At the time data transfer started

0/1 = -/At the time data saved

0/1 = -/At the time data transfer ended

0/1 = -/At the time file transfer started

b3 b2 b1 b0

➀ Backup data to No. 1 system

Refer to No. ➀

Refer to No.➀

b7 b6 b5 b4 b3 b2 b1 b0

➀ Error Code of No. 1 system HD

b7 b6 b5 b4 b3 b2 b1 b0

➀ Error Status of No. 1 system HD

b3 b2 b1 b0

➀➀Data analyzed by NEC Engineers

CHAPTER 3

Page 154

Issue 1

NDA-24300

SYSTEM MESSAGES

[C0H] Detection of Remaining Link Abnormal End

1: C000 XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀ ➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Performed Diagnosis Item

[C0H] Detection of Remaining Link Abnormal End

b7 b6 b5 b4 b3 b2 b1 b0

➀ ED (Error Data)

1 = CPU is not normal

0 = Data transfer error

1 = No Answer error

b1 b0

NDA-24300

CHAPTER 3

Page 155

Issue 1

SYSTEM MESSAGES

PLO MB Key Turn ON

7-U

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the PLO card is turned on while extracting or inserting a circuit

card.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Faulty PLO card No.

b0:

0/1 = PLO No. 0 system/PLO No. 1 system

CHAPTER 3

Page 156

Issue 1

NDA-24300

SYSTEM MESSAGES

PLO MB Key Turn OFF

7-V

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the PLO card is turned off while extracting or inserting a circuit

card.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Faulty PLO card No.

b0:

0/1 = PLO No. 0 system/PLO No. 1 system

➀➀Status of PLO card at the time of

b0:

b1:

b2:

0/1 = Clock STBY/ACT

0/1 = PLO Synchronizing/PLO self-running or drifting

0/1 = -/Input clock down

failure detection (Scan Data 1)

b7 b6 b5 b4 b3 b2 b1 b0

b3, b4:Route of Input clock (see table)

b5:

0/1 = -/PLO input all down

Connected With Primary

Connected With

External Clock

b4 b3

Oscillator (M-OSC)

NO. 0 M-OSC

Route 0

Route 1

Route 2

Route 3

NO. 1 M-OSC

b6:

b7:

0/1 = -/PLO output down

0/1 = -/Drifting

➀ Status of PLO card at the time of

b0:

b1:

b4:

0/1 = -/n × 5msec clock down

0/1 = -/Frame Synchronization down from SYNC card

0/1 = -/Internal OSC clock down

failure detection (Scan Data 2)

b1 b0

NDA-24300

CHAPTER 3

Page 157

Issue 1

SYSTEM MESSAGES

CCH Clock Failure

13-A

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a clock down failure occurs in the CCH/DCH circuit card. When this message is

indicated, the related CCH/DCH card is placed into make-busy status.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 158

Issue 1

NDA-24300

SYSTEM MESSAGES

CCH C-Level Infinite Loop Failure (Permanent)

13-B

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when C-level infinite loop of the Port Microprocessor (PM) in the CCH/DCH circuit

card has occurred.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 159

Issue 1

SYSTEM MESSAGES

CCH C-Level Infinite Loop Failure (Temporary)

13-C

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when C-level infinite loop of the Port Microprocessor (PM) in the CCH/DCH circuit

card has occurred.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 160

Issue 1

NDA-24300

SYSTEM MESSAGES

CCH Lock-Up Failure (Permanent)

13-D

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a Port Microprocessor (PM) of the CCH/DCH card did not send an answer to the

CPU.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 161

Issue 1

SYSTEM MESSAGES

CCH Lock-Up Failure (Temporary)

13-E

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a Port Microprocessor (PM) of the CCH/DCH card did not send an answer to the

CPU.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 162

Issue 1

NDA-24300

SYSTEM MESSAGES

CCH B-Level Infinite Loop Failure (Permanent)

13-F

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when B-level infinite loop of the Port Microprocessor (PM) in the CCH/DCH circuit

card has occurred.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 163

Issue 1

SYSTEM MESSAGES

CCH B-Level Infinite Loop Failure (Temporary)

13-G

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when B-level infinite loop of the Port Microprocessor (PM) in the CCH/DCH circuit

card has occurred.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 164

Issue 1

NDA-24300

SYSTEM MESSAGES

CCS Link Failure (Permanent)

13-H

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a failure has occurred numerous times to a common channel signaling link and

the link has been placed into make-busy state.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

➀ Data Analyzed by NEC Engineers

NDA-24300

CHAPTER 3

Page 165

Issue 1

SYSTEM MESSAGES

➀ Probable cause for failure

b0-b3: See Table.

b3 b2 b1 b0

CCITT

ERROR

FLT ID

FACTOR

S (F = 1) frame is received.

DM (F = 1) response is received.

UA (F = 1) response is received.

UA (F = 0) response is received.

DM (F = 0) response is received.

SABME command is received.

N200 Timeout (Link is set)

N200 Timeout (Link is disconnected)

N200 Timeout (Link failure is restored

to normal)

N (R) frame error is received.

FRMR frame is received (Link is re-set-

up).

Undefined frame is received.

Improper long frame is received.

I frame with I field which exceeds

N201 is received.

Layer 1 down (for ILC)

FRMR frame is received. (Link is not

re-setup)

CHAPTER 3

Page 166

Issue 1

NDA-24300

SYSTEM MESSAGES

CCS Link Failure (Temporary)

13-I

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a failure has occurred numerous times to a common channel signaling link and

the link has been placed into make-busy state. When this fault lasts over three minutes, the system message

changes to [13-H] CCS Link Failure (Permanent).

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

➀ Data Analyzed by NEC Engineers

NDA-24300

CHAPTER 3

Page 167

Issue 1

SYSTEM MESSAGES

➀ Probable cause for the failure

b0-b3: See Table.

b3 b2 b1 b0

CCITT

ERROR

FLT ID

FACTOR

S (F = 1) frame is received.

DM (F = 1) response is received.

UA (F = 1) response is received.

UA (F = 0) response is received.

DM (F = 0) response is received.

SABME command is received.

N200 Timeout (Link is set)

N200 Timeout (Link is disconnected)

N200 Timeout (Link failure is restored

to normal)

N (R) frame error is received.

FRMR frame is received (Link is re-set-

up).

Undefined frame is received.

Improper long frame is received.

I frame with I field which exceeds

N201 is received.

Layer 1 down (for ILC)

FRMR frame is received. (Link is not

re-setup)

CHAPTER 3

Page 168

Issue 1

NDA-24300

SYSTEM MESSAGES

Restoration From CCS Link Failure

13-J

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the faults pertaining to CCIS/ISDN Link are restored to normal.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

➀ CKT No. of faulty circuit

b0-b7: CKT No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 169

Issue 1

SYSTEM MESSAGES

CCH Reset Interrupt Failure

13-K

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a fault occurred to the Port Microprocessor (PM) within the CCH/DCH circuit

card and the restart processing is executed.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of faulty CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 170

Issue 1

NDA-24300

SYSTEM MESSAGES

Digital Line Warning

13-N

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a digital line failure occurs.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Accommodated location

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

➀ Kind of Fault

b7 b4 b3 b2 b1 b0

b0-b4: Kind of Fault (HEX)

00 = -

01 = Frame alignment loss PCM down

02 = Bit error rate is over 10^-6

03 = Slip is detected

04 = -

05 = Dch down

06 = Multi-frame alignment loss

07 = -

10 = -

11 = Frame alignment loss PCM down (frequently)

12 = Bit error rate is over 10^-4

13 = Slip is detected (frequently)

14 = Opposite office alarm is detected

15 = -

16 = Multi-frame alignment loss (frequently)

17 = Frame alignment loss PCM down (continuously)

18 = Multi-frame alignment loss (continuously)

NDA-24300

CHAPTER 3

Page 171

Issue 1

SYSTEM MESSAGES

Digital Line Failure

13-O

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a digital line failure occurs.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Accommodated location

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

➀ Kind of Fault

b0-b4: Kind of Fault (HEX)

00 = -

01 = Frame alignment loss PCM down

02 = Bit error rate is over 10^-4

03 = Slip is detected

b4 b3 b2 b1 b0

04 = Opposite office alarm (AIS) is detected

05 = -

06 = Multi-frame alignment loss

07 = Frame alignment loss PCM down (continuously)

08 = Multi-frame alignment loss (continuously)

CHAPTER 3

Page 172

Issue 1

NDA-24300

SYSTEM MESSAGES

Digital Line Restore

13-P

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a digital line failure is restored to normal.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Accommodated location

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

➀➀Kind of Fault

b7 b4 b3 b2 b1 b0

b0-b4: Kind of Fault (HEX)

00 = -

01 = Frame alignment loss PCM down

02 = Bit error rate is over 10^-4

03 = -

04 = Opposite office alarm (AIS) is detected

05 = Dch restores to normal

06 = Multi-frame alignment loss

NDA-24300

CHAPTER 3

Page 173

Issue 1

SYSTEM MESSAGES

DRU Battery Operation

13-Q

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the battery is operated in the DRU system.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Accommodated location

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 174

Issue 1

NDA-24300

SYSTEM MESSAGES

DRU Line Operation

13-R

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the main power of the DRU system is restored to normal.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Accommodated location

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 175

Issue 1

SYSTEM MESSAGES

Power Failure

13-Z

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a PWR circuit card failure is detected.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀MG No. and Unit No. of fault

b0, b1:Unit No. (0-3)

detection

b2:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

b2 b1 b0

➀ Kind of Power

b7 b4 b3 b2 b1 b0

b1:

b2:

b3:

b4:

0/1 = -/-5V Power Failure

0/1 = -/+12V Power Failure

0/1 = -/+5V Power Failure

0/1 = -/-48V Power Failure

➀ Location of faulty circuit card

b0:

0/1 = Group 24 (0 side) / Group 25 (1 side)

Reference: See Chapter 4, Section 3.3.3, for the circuit card replacement procedure.

CHAPTER 3

NDA-24300

Page 176

Issue 1

SYSTEM MESSAGES

VPS Failure (Temporary)

15-A

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a VPS failure is detected.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Probable cause for failure

b0-b7: 0 = -

1 = Sector error

b7 b6 b5 b4 b3 b2 b1 b0

FF = Other than above

➀ LENS of VPS with the failure

b0-b2: Level

b3-b7: Group

b7 b6 b5 b4 b3 b2 b1 b0

➀ LENS of VPS with the failure

b0, b1:Unit No.

b2-b7: MG No.

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 177

Issue 1

SYSTEM MESSAGES

VPS Failure (Permanent)

15-B

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a VPS failure is detected.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Probable cause for failure

b0-b7: 0 = -

1 = Sector error

b7 b6 b5 b4 b3 b2 b1 b0

FF = Other than above

➀ LENS of VPS with the failure

b0-b2: Level

b3-b7: Group

b7 b6 b5 b4 b3 b2 b1 b0

➀ LENS of VPS with the failure

b0, b1:Unit No.

b2-b7: MG No.

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 178

Issue 1

NDA-24300

SYSTEM MESSAGES

VPS Restore

15-C

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a VPS failure is restored to normal.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ LENS of VPS with the failure

b0-b2: Level

b3-b7: Group

b7 b6 b5 b4 b3 b2 b1 b0

➀ LENS of VPS with the failure

b0, b1:Unit No.

b2-b7: MG No.

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 179

Issue 1

SYSTEM MESSAGES

Inside Trunk All Busy

16-A

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when Intra-Office Trunks (ATI, RST, etc.) have all become busy.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Intra-Office trunks that have

b0-b7: Intra-Office trunks that have become all busy (01-1F)

(See table on the following page)

become all busy

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 180

Issue 1

NDA-24300

SYSTEM MESSAGES

ROUTE DATA

TRUNK NAME

NO.

901

902

903

904

905

906

(HEX.)

NO.

917

918

919

920

921

922

(HEX.)

Attendant Console

Originating Register Trunk

Incoming Register Trunk

MF Receiver

MFC Sender

Not used

MODEM

Sender Trunk DP/PB

PB Receiver for Automated

Attendant Service

907

908

909

AMP

Not used

923

924

925

MODEM

Three-Way Conference Trunk

910

911

912

Not used

926

927

928

MODEM

Not used

Originating Register Trunk for

ATTCON/DESKCON

913

Three-Way Conference Trunk for

ATTCON/DESKCON

929

Data Signaling Trunk-Option

914

915

Not used

930

931

Rate Adaptation Conversion Trunk

Not used

Night ATTCON/DESKCON

916

MFC Register

NDA-24300

CHAPTER 3

Page 181

Issue 1

SYSTEM MESSAGES

Virtual Tie Line Set Report

16-B

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when virtual tie line setup has completed.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Counter

b0:

00=-

01=Re-setup

➀ Virtual Tie Line Call Header

b0,b1: Unit No.

Accommodated Location

b2:

Module Group No.

b2 b1 b0

➀ Virtual Tie Line Call Header

b0-b2: Level

b3-b7: Group No.

Accommodated Location

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 182

Issue 1

NDA-24300

SYSTEM MESSAGES

Virtual Tie Line Cancel Report

16-C

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when virtual tie line cancel has completed.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Counter

b0:

0/1=-/Re-setup

➀ Virtual Tie Line Call Header

b0,b1: Unit No.

Accommodated Location

b2:

Module Group No.

b2 b1 b0

➀ Virtual Tie Line Call Header

b0-b2: Level

b3-b7: Group No.

Accommodated Location

b2 b1 b0

NDA-24300

CHAPTER 3

Page 183

Issue 1

SYSTEM MESSAGES

Virtual Tie Line Set Time Out

16-E

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when virtual tie line setup has failed due to a fault in the network of the terminating

office concerned.

1: 00XX XX8X XXXX 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Virtual Tie Line Call Header

b0,b1: Unit No.

Accommodated Location

b2:

Module Group No.

b2 b1 b0

➀➀Virtual Tie Line Call Header

b0-b2: Level

b3-b7: Group No.

Accommodated Location

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 184

Issue 1

NDA-24300

SYSTEM MESSAGES

➀ Virtual Tie Line Call Header

b3-b7: Call Source

Accommodated Location

DATA

CALL SOURCE

b7 b6 b5 b4 b3 b2 b1 b0

User

Private network to which the user is directly connected.

(Self side)

National network to which the user is directly connected.

(Self side)

Tie-Line Network

National network to which the opposite party is directly

connected. (Opposite party’s side)

Private network to which the opposite party is directly

connected. (Opposite party’s side)

International Network

Network from Interworking

Spare

Other

b4-b7: “8” is always indicated.

➀ Fault Cause

b0-b3: Reason Kind

b4-b6: Class

b7 b6 b5 b4 b3 b2 b1 b0

0=No Answer

Other than 0=Refer to the following table

REASON

CLASS

KIND

DATA

REASON KIND

VALUE

000

001

0001

0010

0011

0110

0111

0000

0001

0010

0011

0101

0110

1010

1011

1100

1101

1110

1111

Dead Number

No route to the designated transit network

No route to the opposite Party

Use of channel not allowed

Call terminated to a setup channel

Normal disconnection

Reason Kind

Class

Value

Called user busy

No response from called user

Called party being rung/no answer

Communication denied

Opposite party’s terminal number changed

Disconnection and release of the user not selected

Opposite party’s terminal out of order

Invalid number format (Incomplete Number)

Facility denied

8765

4321(bit)

xxxx

-000

-001

Normal Event Class

Answer to status inquiry

Other normal class

NDA-24300

CHAPTER 3

Page 185

Issue 1

SYSTEM MESSAGES

REASON

KIND

CLASS

DATA

REASON KIND

VALUE

010

0010

0110

1001

1010

1011

1100

1111

No usable channel/line

Network failure

Temporary failure

Switching system congested

Access information discarded

Use of requested line/channel not allowed

Class not allowed use of other resources

010 xxxx

Classes not allowed use of resources

Reason Kind

011

0001

0010

1001

1010

1111

Use of QOS not allowed

Requested facility not contracted

Bearer capability not allowed

Bearer capability not allowed at present

Class not allowed to use other services or options

Class

Value

8765

011

4321(bit)

xxxx

Classes not allowed use of services

100

0001

0010

0101

0110

1111

Unprovided bearer capability designated

Unprovided channel kind designated

Unprovided facility requested

Restricted digital information bearer capability

Class unprovided with other services or options

100 xxxx

Classes not provided with services

101

0001

0010

0011

0100

0101

0110

1000

1011

1111

Invalid call number used

Invalid channel number used

Designated transit call ID number unused

Transit call ID number being used

No transit call

Designated transit call disconnected and released

Terminal attributes unmatch

101 xxxx

Invalid message class

Invalid transit network selected

Other invalid message class

110

0000

0001

0010

Mandatory information elements inadequate

Message kind undefined or unprovided

Call status and message unmatching or message

kind undefined

110 xxxx

Procedure error (ex: unrecognized

message) class

110

0011

0100

0101

0110

1111

Information element undefined

100 Content of information element invalid

101 Call status and message unmatching

102 Recovery due to timer over

111 Class of other procedure errors

111 xxxx

Interworking class

111

127 Other interworking class

Reserved

Others

CHAPTER 3

Page 186

Issue 1

NDA-24300

SYSTEM MESSAGES

Sender Start Time Out

16-F

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message indicates that an outgoing call (by connection acknowledge system) has not received an ac-

knowledgment signal from the opposite office. As a result, the attempted outgoing call is routed to Reorder

Tone (ROT) connection.

1: XXXX XXXX XX0X XX0X 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀➀➀ ➀➀➀ ➀➀➀ ➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

In Case of Station OG/ATT OG/ATT Tandem Connection

➀ Type of connection and station

b0-b2: Digits of station number (origination)

b6-b7: 0H=Station OG connection

4H=ATT OG connection

number digits

b7 b6

b2 b1 b0

CH=ATT Tandem connection

➀-➀ Calling station number

(See table)

b4-b7

b0-b3

b7 b6 b5 b4 b3 b2 b1 b0

➀

DC0

DC2

DC4

DC1

DC3

DC5

NDA-24300

CHAPTER 3

Page 187

Issue 1

SYSTEM MESSAGES

➀ Tenant No. of calling station (Hex.)

b7:

OP data (0/1)

When OPTN data of ➀➀is valid, “1” displays.

b7 b6

b2 b1 b0

b0-b3: Tenant No. of calling station

• bit7=0

• bit7=1

Tenant No.<16

15<Tenant No.₌255

Refer to the OPTN

data of ➀

➀ OPTN data

b0-b3: OPTN data Note

b3 b2 b1 b0

Note: This data displays when the Tenant No. of the calling station is larger than 15, and bit7 of ➀ displays

as “1” (otherwise, “0” displays at any time). While the four-bit data of ➀➀is self-sufficient in verifying

the Tenant No. “1-15,” this OPTN data provides a supportive role to cover the larger Tenant No.

ranging from 16 to 255. Use the following method to analyze the data:

Tenant No. of Calling Station (1-15)

Tenant No.

OPTN data (0: fixed)

bit 0 - bit 3 of ➀

Tenant No. of Calling Station (16-255)

OPTN data

Tenant No.

OPTN data (variable)

bit 0 - bit 3 of ➀

➀ OG route number (Hex.)

b7:

b6:

AC data

0/1=Internal trunk/External trunk

OP data (0/1)

b7 b6 b5 b4 b3 b2 b1 b0

When OPRT data of ➀➀is valid, “1” displays,

b0-b5: OG route number

• bit 6=0

Route No.<64

Refer to the OPTN

• bit 6=1

63<Route No. data of ➀

CHAPTER 3

Page 188

Issue 1

NDA-24300

SYSTEM MESSAGES

➀ OPRT data

b0-b3: OPRT data Note

b3 b2 b1 b0

Note: This data displays when the OG Route No. is larger than 63, and bit6 of ➀ displays as “1” (otherwise,

“0” displays at any time). While the six-bit data of ➀ is self-sufficient in verifying the Route No. “1-

63,” this OPRT data provides a supportive role to cover the Route No., which is larger than 63. Use the

following method to analyze the data:

OG Route No. (1-63)

OG Route No.

OPTN data (0:fixed)

bit0 - bit5 of ➀

OG Route No. (64 or larger)

OPTN data

OG Route No.

OPTN data (variable)

bit0 - bit5 of ➀

➀ Trunk No. of OG trunk

b0-b7:

b0-b4:

Trunk No. of OG trunk

b7 b6 b5 b4 b3 b2 b1 b0

➀ Trunk No. of sender

Trunk No. of sender

b7 b6 b5 b4 b3 b2 b1 b0

11 Number of digits dialed by caller

Number of digits dialed by caller

b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 189

Issue 1

SYSTEM MESSAGES

Number dialed by caller (See table)

b7 b6 b5 b4 b3 b2 b1 b0

b4-b7

b0-b3

DC0

DC2

DC1

DC3

DC4

DC5

DC6

DC7

DC8

DC9

DC10

DC12

DC14

DC16

DC18

DC20

DC11

DC13

DC15

DC17

DC19

DC21

In Case of Tandem Connection

➀ Type of connection

0 = Tandem connection

b7 b6

➀ IC route number (Hex.)

b7:

b6:

AC data

0/1=Internal trunk/External trunk

OP data (0/1)

b7 b6 b5 b4 b3 b2 b1 b0

When OPRT data of ➀➀is valid, “1” displays.

b0-b5: IC route number

• bit 6=0

• bit 6=1

Route No.<64

<63 Route No.

Refer to the OPTN

data of ➀

CHAPTER 3

Page 190

Issue 1

NDA-24300

SYSTEM MESSAGES

➀ OPRT data

b0-b3: OPRT data Note

b3 b2 b1 b0

Note: This data displays when the IC Route No. is larger than 63, and bit6 of ➀➀displays as “1” (otherwise,

“1” displays at any time). While the six-bit data of ➀ is self-sufficient in verifying the Route No. “1-

63,” this OPRT data provides a supportive role to cover the Route No., which is larger than 63. Use the

following method to analyze the data:

IC Route No. (1-63)

IC Route No.

OPRT data (0:fixed)

bit0 - bit5 of ➀

IC Route No. (64 or larger)

OPRT data

IC Route No.

OPRT data (variable)

bit0 - bit5 of ➀

➀➀-➀➀➀Trunk No. of IC trunk

b0-b7: Trunk No. of IC trunk

b7 b6 b5 b4 b3 b2 b1 b0

➀ Not used

➀ OG route number (Hex.)

b7:

b6:

AC data

0/1=Internal trunk/External trunk

OP data (0/1)

b7 b6 b5 b4 b3 b2 b1 b0

When OPRT data of ➀➀is valid, “1” displays,

b0-b5: OG route number

• bit 6=0

• bit 6=1

Route No.<64

<63 Route No.

Refer to the OPTN

data of ➀

NDA-24300

CHAPTER 3

Page 191

Issue 1

SYSTEM MESSAGES

➀ OPRT data

b0-b3: OPRT data Note

b3 b2 b1 b0

Note: This data displays when the OG Route No. is larger than 63, and bit6 of ➀ displays as “1” (otherwise,

“0” is displays at any time). While the six bit data of ➀ is self-sufficient in verifying the Route No. “1-

63,” this OPRT data provides a supportive role to cover the Route No., which is larger than 63. Use the

following method to analyze the data:

OG Route No. (1-63)

OG Route No.

OPRT data (0: fixed)

bit 0 - bit 5 of ➀

OG Route No. (64 or larger)

OPRT data

OG Route No.

OPRT data (variable)

bit 0 - bit 5 of ➀

➀ Trunk No. of OG trunk

b0-b7:

b0-b4:

Trunk No. of OG trunk

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Trunk No. of sender

Trunk No. of sender

b7 b6 b5 b4 b3 b2 b1 b0

11 Number of digits dialed by caller

Number of digits dialed by caller

b4 b3 b2 b1 b0

CHAPTER 3

Page 192

Issue 1

NDA-24300

SYSTEM MESSAGES

➀Number dialed by caller (See table)

b7 b6 b5 b4 b3 b2 b1 b0

b4-b7

b0-b3

DC0

DC2

DC1

DC3

DC4

DC5

DC6

DC7

DC8

DC9

DC10

DC12

DC14

DC16

DC18

DC20

DC11

DC13

DC15

DC17

DC19

DC21

NDA-24300

CHAPTER 3

Page 193

Issue 1

SYSTEM MESSAGES

I/O Port Line OFF

16-K

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the DR signal of the RS-232C, connected to the port designated by the system

data, remains off for 30 consecutive seconds while the system is in service (immediately after startup in the

case of system start-up).

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Faulty Port No.

0/1 = -/Link Down

b0:

b1:

b2:

b3:

Port 0

Port 1

Port 2

Port 3

b4: Port 4

b5: Port 5

b6: Port 6

b7: Port 7

b7 b6 b5 b4 b3 b2 b1 b0

IOC0

IOC1

CHAPTER 3

Page 194

Issue 1

NDA-24300

SYSTEM MESSAGES

I/O Port Line Restore

16-L

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when [16-K] I/O Port Line Down Failure is restored to normal.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Faulty Port No.

b7 b6 b5 b4 b3 b2 b1 b0

0/1 = -/Link Down

b0:

b1:

b2:

b3:

Port 0

Port 1

Port 2

Port 3

b4: Port 4

b5: Port 5

b6: Port 6

b7: Port 7

IOC0

IOC1

NDA-24300

CHAPTER 3

Page 195

Issue 1

SYSTEM MESSAGES

Hard Clock Failure

16-M

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the timer circuit in the EMA card becomes faulty and stops functioning and 64-

Hz clock alarm is output.

1: 0000 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Message Detail Data

This system message is always indicated as 0000.

CHAPTER 3

Page 196

Issue 1

NDA-24300

SYSTEM MESSAGES

Hard Clock Restore

16-N

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when [16-M] 64 Hz Clock Down Detected is restored to normal.

1: 0000 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Message Detail Data

This system message is always indicated as 0000.

NDA-24300

CHAPTER 3

Page 197

Issue 1

SYSTEM MESSAGES

IOC Failure (Temporary)

16-T

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the IOC card fails.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ IOC circuit card No.

b0:

0/1 = No. 0/No. 1

➀ Cause for fault

b0:

b1:

b2:

b3:

b4:

0/1 = -/COP Alarm

0/1 = -/CLK Alarm

0/1 = -/MEM bus CLK Alarm

0/1 = -/Abnormal Interruption

0/1 = -/Infinite Loop Detected

b4 b3 b2 b1 b0

CHAPTER 3

Page 198

Issue 1

NDA-24300

SYSTEM MESSAGES

IOC Failure (Permanent)

16-U

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the IOC card failure, observed in the message [16-T], is detected more than 8

times a day.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ IOC circuit card No.

b0:

0/1 = No. 0/No. 1

➀➀Cause for fault

b0:

b1:

b2:

b3:

b4:

0/1 = -/COP Alarm

0/1 = -/CLK Alarm

0/1 = -/MEM bus CLK Alarm

0/1 = -/Abnormal Interruption

0/1 = -/Infinite Loop Detected

b4 b3 b2 b1 b0

Reference: See Chapter 4, Section 1.3.3, for the circuit card replacement procedure.

NDA-24300

CHAPTER 3

Page 199

Issue 1

SYSTEM MESSAGES

Station Exchanged Report

16-X

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the user uses Follow Phone (SWAP) service.

1: XXXX XXXX XXXX XX00 2: XXXX XXXX XXXX 00XX 3: XXXX 0000 0000 0000

12 13

➀➀➀ ➀➀➀ ➀➀➀ ➀

➀➀➀ ➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Error code

b0-b7: See table

b7 b6 b5 b4 b3 b2 b1 b0

ERROR CODE (HEX)

FAILURE

Normal End

MG unmatch

Called party is not the station

TEC of Calling or Called station is abnormal

TEC unmatch

Hunting group unmatch

Call Pick Up group unmatch

Calling or Called station is Night station

Call Pick Up Expand group unmatch

Calling or Called D^termhas Data Line

Calling or Called D^termhas OAI function key

Calling or Called station is Agent/Supervisor (ACD)

13-15

Called station is busy

MW has been set to Calling or Called station

CHAPTER 3

NDA-24300

Page 200

Issue 1

SYSTEM MESSAGES

ERROR CODE (HEX)

FAILURE

Call Back/OG queuing has been set to Calling or Called station

Call Forwarding - All Calls has been set to Calling or Called station

Call Forwarding - Busy Line has been set to Calling or Called station

Call Forwarding - Don’t Answer has been set to Calling or Called station

22-31

Under processing of Data Memory Back Up

• Collision of swap service

• Under swapping of One Touch Memory

• Memory overflow (Max. 4 stations)

Data Memory read error

Data Memory swap failure

OAI Terminal Information swap failure (CM Data)

OAI Terminal Information swap failure (LP Data)

SST Time out

➀ Tenant No. of calling station

b0-b3: Tenant No. (1-15)

b4-b7: Tenant No. (over 15)

b7 b6 b5 b4 b3 b2 b1 b0

➀ Accommodated location of calling

b0-b2: Level

b3-b7: Group (0-22)

station after Follow Phone service

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Accommodated location of calling

b0, b1:Unit No. (0-3)

b2-b7: MG No.

station after Follow Phone service

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 201

Issue 1

SYSTEM MESSAGES

➀-➀ Station No. of calling station

b7 b6 b5 b4 b3 b2 b1 b0

b4-b7

b0-b3

➀

DC0

DC1

DC2

DC4

DC3

DC5

➀ Tenant No. of called station

b0-b3: Tenant No. (1-15)

b4-b7: Tenant No. (over 15)

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Accommodated location of called

b0-b2: Level

b3-b7: Group

station

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Accommodated location of called

b0, b1:Unit No. (0-3)

b2-b7: MG No.

station

b7 b6 b5 b4 b3 b2 b1 b0

11➀-➀13➀Station No. of called station

b7 b6 b5 b4 b3 b2 b1 b0

b4-b7

b0-b3

DC0

DC1

DC2

DC4

DC3

DC5

14 Data Analyzed by NEC Engineers

CHAPTER 3

Page 202

Issue 1

NDA-24300

SYSTEM MESSAGES

CCH MBR Key Turn ON

17-A

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MBR switch on the CCH/DCH card is turned ON.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

➀ CKT No.

b0, b1:CKT No. (0-3)

b1 b0

NDA-24300

CHAPTER 3

Page 203

Issue 1

SYSTEM MESSAGES

CCH MBR Key Turn OFF

17-B

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MBR switch on the CCH/DCH card is turned OFF.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Location of CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

➀ CKT No.

b0, b1:CKT No. (0-3)

b1 b0

CHAPTER 3

Page 204

Issue 1

NDA-24300

SYSTEM MESSAGES

CCH MB Key Turn ON

17-C

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the CCH/DCH card is turned ON while extracting or inserting

a circuit card or at PM initialization, etc.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Location of CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 205

Issue 1

SYSTEM MESSAGES

CCH MB Key Turn OFF

17-D

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the CCH/DCH card is turned OFF while extracting or inserting

a circuit card or at PM initialization, etc.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Location of CCH/DCH card

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

MG No.

0/1 = Even-numbered MG/Odd-numbered MG

CHAPTER 3

Page 206

Issue 1

NDA-24300

SYSTEM MESSAGES

Day/Night Change Information

17-H

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the NIGHT switch on the ATTCON/DESKCON is operated or when the DAY/

NIGHT change is executed by the external switch operation.

1: XXXX XXXX 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Tenant No.

b0-b3: Tenant No. (1-15)

b4-b7: Tenant No. (over 15)

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Changing Method

b0-b7:

1=Night Key onATTCON/DESKCON

2=External Key

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 207

Issue 1

SYSTEM MESSAGES

➀ Day/Night Mode Specification

b0-b3: Mode after changing

b4-b7: Mode before changing

b7 b6 b5 b4 b3 b2 b1 b0

Note: This data is programmed as initial data.

b0 b1 b2 b3

MEANING

b4 b5 b6 b7

Day Mode

Night Mode 1

Night Mode 2 available only for Japan

Night Mode 3 (DIT-Night Connection Fixed) Note

➀ External Switch Status

b0-b7:

01=Not used

02=Day/Night Change

03=Not used

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 208

Issue 1

NDA-24300

SYSTEM MESSAGES

IOC MB Key Turn ON

17-O

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the IOC card is turned ON while extracting or inserting a circuit

card.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀Circuit Card No.

b0:

0/1 = IOC 0/IOC 1

NDA-24300

CHAPTER 3

Page 209

Issue 1

SYSTEM MESSAGES

IOC MB Key Turn OFF

17-P

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MB switch on the IOC card is turned OFF.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Circuit Card No.

b0:

0/1 = IOC 0/IOC 1

CHAPTER 3

Page 210

Issue 1

NDA-24300

SYSTEM MESSAGES

IOC MBR Key Turn ON

17-Q

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MBR switch on the IOC card is turned on at the time of CPU changeover or

speech path changeover.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Circuit Card No.

b0:

0/1 = IOC 0/IOC 1

NDA-24300

CHAPTER 3

Page 211

Issue 1

SYSTEM MESSAGES

IOC MBR Key Turn OFF

17-R

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MBR switch on the IOC card is turned off at the time of CPU changeover or

speech path changeover.

1: XX00 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Circuit Card No.

b0:

0/1 = IOC 0/IOC 1

CHAPTER 3

Page 212

Issue 1

NDA-24300

SYSTEM MESSAGES

DCH Back-Up Automatic Change Start/End

23-P

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the Primary Dch fails, and the Dch Back-Up function is operated automatically.

1: XXXX XXXX XXXX 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Condition of Dch

b0-b7:

1 = Back-up Start

2 = Back-up End

b7 b6 b5 b4 b3 b2 b1 b0

3 = Back-up Failed

➀ Location of Dch (Primary)

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

➀ Location of Dch (Back-up)

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 213

Issue 1

SYSTEM MESSAGES

➀➀Changeover Information

b0, b1:

b2, b3:

00 = Change from Primary Dch to Dch for Back-up

01 = Change from Dch for Back-up to Primary Dch

10 = Place Primary Dch to ACT status

b3 b2 b1 b0

11 = Place Dch for Back-up to ACT status

00 = Change signal is received

01 = Change signal is sent

➀ Status of the Primary/Back-up Dch

b0-b2: Status of Primary Dch

0 = In service

b5 b4 b3 b2 b1 b0

1 = Standby

2 = Out of Service

3 = Make Busy

4 = Changing status from STBY to In Service

5 = Manual out of service

b3-b5: Status of Primary Dch

0 = In service

1 = Standby

2 = Out of Service

3 = Make Busy

4 = Changing status from STBY to In Service

5 = Manual out of service

➀ EVENT No.

b0-b7: EVENT No.

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 214

Issue 1

NDA-24300

SYSTEM MESSAGES

DCH Back-Up Manual Change Start/End

23-Q

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the Primary Dch fails, and the Dch Back-Up function is operated manually.

1: XXXX XXXX XXXX 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀➀➀ ➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Condition of Dch

b0-b7:

1 = Back-up Start

2 = Back-up End

b7 b6 b5 b4 b3 b2 b1 b0

3 = Back-up Failed

➀ Location of Dch (Primary)

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

➀ Location of Dch (Back-up)

b0-b4: Group No.

b5, b6:Unit No. (0-3)

b7 b6 b5 b4 b3 b2 b1 b0

b7:

0/1 = Even-numbered MG/Odd-numbered MG

NDA-24300

CHAPTER 3

Page 215

Issue 1

SYSTEM MESSAGES

➀ Detailed information on changing

b0, b1:

Dch

00 = Change from Primary Dch to Dch for Back-up

01 = Change from the Dch for Back-up to Primary Dch

10 = Place Primary Dch to ACT status

b3 b2 b1 b0

11 = Place Dch for Back-up to ACT status

b2, b3:Way of changing

00 = Changed by the MAT

01 = Changed by the MB switch of the circuit card

02 = Changed by placing Dch to Make-Busy

03 = Unknown

➀ Status of Primary/Back-up Dch

b7 b5 b4 b3 b2 b1 b0

b0-b2: Status of Primary Dch

0 = In service

1 = Standby

2 = Out of Service

3 = Make Busy

4 = Changing status from STBY to In Service

5 = Manual out of service

b3-b5: Status of Back-up Dch

0 = In service

1 = Standby

2 = Out of Service

3 = Make Busy

4 = Changing status from STBY to In Service

5 = Manual out of service

➀ EVENT No.

b0-b7: EVENT No.

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 216

Issue 1

NDA-24300

SYSTEM MESSAGES

MUX Clock Failure

23-Y

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MUX (PH-PC36) card has a clock failure in one of the dual systems.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Unit, MG, system number for MUX

b0-b1: Unit number where a clock failure occurred

card with a clock failure

b2:

b3:

MG number where a clock failure occurred

0/1 = a clock failure in MUX No. 0 system/

a clock failure in MUX No. 1 system

0/1 = Faulty MUX is in ACT/

b4 b3 b2 b1 b0

b4:

Faulty MUX is in STBY

➀ Scan Data

Scan Data:Clock alarm information on the faulty MUX card

b1:

b2:

b3:

0/1 = -/FH failure for 2M PCM Highway

0/1 = -/CLK failure for 2M PCM Highway

0/1 = -/4M CLK failure for PM

b3 b2 b1 b0

Reference: See Chapter 5, Section 4.3, Section 4.4, and Section 5.3, for the repair procedure.

NDA-24300

CHAPTER 3

Page 217

Issue 1

SYSTEM MESSAGES

Both MUX Clock Failure

23-Z

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MUX (PH-PC36) card has a clock failure in both of the dual systems.

1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀ ➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ MUX card location

b0-b1: Unit No.

b2:

MG No.

b2 b1 b0

b3 b2 b1 b0

➀ Scan Data 1

Scan Data 1:Details on clock alarm information (ACT mode)

b1:

b2:

b3:

0/1 = -/FH failure for 2M PCM Highway

0/1 = -/CLK failure for 2M PCM Highway

0/1 = -/4M CLK failure for PM

➀ Scan Data 2

Scan Data 2:Details on clock alarm information (STBY mode)

b1:

b2:

b3:

0/1 = -/FH failure for 2M PCM Highway

0/1 = -/CLK failure for 2M PCM Highway

0/1 = -/4M CLK failure for PM

Reference: See Chapter 4, Section 3.3.2, for the circuit card replacement procedure.

CHAPTER 3

NDA-24300

Page 218

Issue 1

SYSTEM MESSAGES

MAT Log

26-N

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MAT is log-in or log-out.

1: XX00 XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀➀ ➀➀➀ ➀➀➀ ➀➀➀

➀➀➀ ➀➀➀ ➀➀➀ ➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Port No. of the MAT logged in/out

b0-b2: I/O Port No.

000 = Port 0 001 = Port 1

010 = Port 2 011 = Port 3

b7 b6 b5 b4 b3 b2 b1 b0

100 = Port 4 101 = Port 5

110 = Port 6 111 = Port 7

b4-b7: 0000 = Login

0001 = Logout

0010 = Command is startup

0011 = Command END

➀ Command Name

b0-b7: Command name

b7 b6 b5 b4 b3 b2 b1 b0

➀ User Name

b0-b7: User name entered by the MAT

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 219

Issue 1

SYSTEM MESSAGES

Call Trace

26-R

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This massage is issued when a call, originated via a station/trunk, is judged as malicious, and then, the details

on the call is traced with the called party pressing an access code or the “Call Trace” key.

[When a call is originated from a station]

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀

4: XXXX XXXX XXXX XXXX 5: XXXX XX00 0000 0000 6: 0000 0000 0000 0000

➀

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

• Information on Called Party (Informer)

b4 - b7 b0 - b3

➀ Fusion Point Code (FPC) (Hex.) Note

dc0

dc2

dc1

dc3

b7 b6 b5 b4 b3 b2 b1 b0

➀

b4 - b7 b0 - b3

➀➀Tenant No. (Hex.) Note

b7 b6 b5 b4 b3 b2 b1 b0

dc0

dc2

dc1

dc3

b4 - b7 b0 - b3

➀➀Physical Station No. (Hex.) Note

dc0

dc2

dc4

dc1

dc3

dc5

b7 b6 b5 b4 b3 b2 b1 b0

➀

➀ User Group No. (UGN) (Hex.) Note

b7 b6 b5 b4 b3 b2 b1 b0

b4 - b7 b0 - b3

dc0

dc2

dc1

dc3

b4 - b7 b0 - b3 b4 - b7 b0 - b3

➀ Telephone No. (Hex.) Note

b7 b6 b5 b4 b3 b2 b1 b0

dc0

dc2

dc4

dc6

dc1

dc3

dc5

dc7

dc8

dc9

dc10

dc12

dc14

dc11

dc13

dc15

➀

CHAPTER 3

Page 220

Issue 1

NDA-24300

SYSTEM MESSAGES

• Information on Malicious call

➀ Kind of Call (Hex.)

10H=Call from a station

b7 b6 b5 b4 b3 b2 b1 b0

b4 - b7 b0 - b3

➀ Fusion Point Code (FPC) (Hex.) Note

b7 b6 b5 b4 b3 b2 b1 b0

dc0

dc2

dc1

dc3

➀

b4 - b7 b0 - b3

dc0

dc2

dc1

dc3

➀ Tenant No. (Hex.) Note

b7 b6 b5 b4 b3 b2 b1 b0

b4 - b7 b0 - b3

dc0

dc2

dc4

dc1

dc3

dc5

➀ Physical Station No. (Hex.) Note

b7 b6 b5 b4 b3 b2 b1 b0

➀

b4 - b7 b0 - b3

➀ User Group No. (UGN) (Hex.) Note

b7 b6 b5 b4 b3 b2 b1 b0

dc0

dc2

dc1

dc3

b4 - b7 b0 - b3 b4 - b7 b0 - b3

Telephone No. (Hex.) Note

dc0

dc2

dc4

dc6

dc1

dc3

dc5

dc7

dc8

dc9

b7 b6 b5 b4 b3 b2 b1 b0

dc10

dc12

dc14

dc11

dc13

dc15

Note: Each No./code is output in hexadecimal. Detailed meanings are as follows:

Output Data (Hex.)

Actual Meaning

1~9

→

1~9

blank

NDA-24300

CHAPTER 3

Page 221

Issue 1

SYSTEM MESSAGES

[When a call is originated from a trunk]

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

➀

4: XXXX XXXX XXXX XXXX 5: XXXX 0000 0000 0000 6: 0000 0000 0000 0000

➀

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

• Information on Called Party (Informer)

➀ Fusion Point Code (FPC) (Hex.) Note

b4 - b7 b0 - b3

b7 b6 b5 b4 b3 b2 b1 b0

dc0

dc2

dc1

dc3

➀

➀ Tenant No. (Hex.) Note

b4 - b7 b0 - b3

dc0

dc2

dc1

dc3

b7 b6 b5 b4 b3 b2 b1 b0

➀ Physical Station No. (Hex.) Note

b4 - b7 b0 - b3

dc0

dc2

dc4

dc1

dc3

dc5

b7 b6 b5 b4 b3 b2 b1 b0

➀

➀ User Group No. (UGN) (Hex.) Note

b4 - b7 b0 - b3

dc0

dc2

dc1

dc3

b7 b6 b5 b4 b3 b2 b1 b0

➀ Telephone No. (Hex.) Note

b4 - b7 b0 - b3

dc0

dc2

dc1

dc3

b7 b6 b5 b4 b3 b2 b1 b0

dc4

dc5

dc6

dc8

dc7

dc9

➀

dc10

dc12

dc14

dc11

dc13

dc15

CHAPTER 3

Page 222

Issue 1

NDA-24300

SYSTEM MESSAGES

• Information on Malicious Call

➀ Kind of Call (Hex.) Note

20H=Call from a trunk

b7 b6 b5 b4 b3 b2 b1 b0

b4 - b7 b0 - b3

dc0

dc2

dc1

dc3

➀ Calling No. of Trunk Call (Caller ID) (Hex.)

Note, Note 1

dc4

dc6

dc5

dc7

b7 b6 b5 b4 b3 b2 b1 b0

dc8

dc9

dc10

dc12

dc14

dc16

dc18

dc20

dc22

dc24

dc26

dc28

dc30

dc11

dc13

dc15

dc17

dc19

dc21

dc23

dc25

dc27

dc29

dc31

Note: Each No./Code is output in hexadecimal.

➀

Detailed meanings are as follows:

Output Data (Hex.)

Actual Meaning

1~9

→

blank

Note 1: If the number of the trunk call (Caller-ID) cannot be identified, the data

here is output as “0”.

NDA-24300

CHAPTER 3

Page 223

Issue 1

SYSTEM MESSAGES

LAN Interface Error Report

26-V

Default Alarm:

SUP

Default Grade:

Grade Modified:

Lamp Modified:

This message is issued when the connection error related to external LAN Interface equipment occurs in the

system.

TCP/IP Part

Application Part

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

11 12

13 14

15 16

17 18

19 20

21 22

23 24

➀➀➀ ➀➀➀ ➀➀➀ ➀ ➀

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀~➀ IP Address for external equipment in which error has been detected. (Hex.)

b7 b6 b5 b4 b3 b2 b1 b0

➀,➀➀➀Port No. (Client Port No.) (Hex.)

b7 b6 b5 b4 b3 b2 b1 b0

➀ Socket No. (Used Socket No.) (Hex.)

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Error Code (TCP/IP Error Code) (Hex.)

See Table 3-2.

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 224

Issue 1

NDA-24300

SYSTEM MESSAGES

Definition

Table 3-2 Error Code

Output Data

(Hex.)

Output Data

(Hex.)

Definition

BSD SOCKET ERROR

Address family not supported

User parameter error

Host not reachable

PROTOCOL FAMILY

Address already in use

Can’t assign requested address

Network is down

Timeout

Protocol error

No buffer space

*//62

Network is unreachable

Network dropped connection

Connection block invalid

Invalid pointer argument

Operation would block

Message too long

RESET

Connection reset by peer

Socket is already connected

Socket is not connected

Can’t send after socket shutdown

Connection refused

Protocol not available

Destination address required

Protocol wrong type for socket

Protocol not supported

Socket type not supported

Operation not supported on socket

Protocol family not supported

Host is down

Operation already in progress

Operation now in progress

NDA-24300

CHAPTER 3

Page 225

Issue 1

SYSTEM MESSAGES

➀ Application Type

b0-b7 : (Hex)

01=SUPER SERVER

b7 b6 b5 b4 b3 b2 b1 b0

02=MAT

03=SMDR

04=MCI

05=OAI

06=PMS

07=MIS

[When =03 (SMDR) / 04 (MCI) ]

b0-b7: (Hex)

➀ Device Number of Error detected client PC

Device Number of error detected Client PC.

If the Machine Number is not determined, “FF”

is output.

b7 b6 b5 b4 b3 b2 b1 b0

b0-b7: (Hex)

Kind of Error

01=SEND Execution Error

02=RECEIVE Execution Error

03=SEND Execution Count Over

04=RECEIVE Execution Count Over

05=System Data is not assigned

06=Time Over

b7 b6 b5 b4 b3 b2 b1 b0

07=Parity Error

08=Connection Error

➀Details on Detected Error

09=Connection Port Capacity Over

0A=Detection of B-level Infinite Loop

0B~FF=Not Used

b7 b6 b5 b4 b3 b2 b1 b0

-When 01/02 is output at

b0-b7: Cause of error (Hex)

-When 05 is output at

b0-b7: 01=Data (Data Output via LAN) not assigned

02=Device No. not assigned

-When 07 is output at

13 24

Not used

b0-b7: 00H=No Parity is set

01H=Odd Parity is set

02H=Even Parity is set

-When 08 is output at

b0-b7: Cause of error (Hex)

CHAPTER 3

Page 226

Issue 1

NDA-24300

SYSTEM MESSAGES

[When =05 (OAI) / 07 (MIS) ]

➀ Faulty Logical Port No. (Hex)

b7 b6 b5 b4 b3 b2 b1 b0

b0-b7 : Error Kind (Hex)

Refer to Table 3-3:

Error Kind (ERRK)

b7 b6 b5 b4 b3 b2 b1 b0

Table 3-3 Error Kind (ERRK)

Output Data

Error Situation

SEND Execution Error

Required Check

01H

[1] Check the TCP/IP Transmission

capacity on the UAP side is proper

or not.

TCP/IP connection is down because the text is not transmit-

ted continuously.

[2] Check the operation status on the UAP

side is normal.

02H

RECEIVE Execution Error

[1] Check the software operation on the

MIS or Host side.

Incorrect text format is received.

[2] Check the LAN cable connection

status.

03H

04H

05H

TCP/IP Connection Error

Re-start the MIS or HOST computer.

TCP/IP connection is released due to the TCP port discon-

nection order from the MIS or Host.

Connection Error (B-level Infinite Loop, etc.)

Re-check the operation status of MIS or

Host.

TCP port is released due to the detection of abnormal state in

the MIS or HOST operation.

TCP/IP Port Capacity Over

The number of allowed ports for applica-

tion use via TCP/IP must be 16 or less. Ad-

TCP/IP connection cannot be established due to the connec- just the used application number not to

tion port capacity over. exceed “16” in total.

12 24

Not used

NDA-24300

CHAPTER 3

Page 227

Issue 1

SYSTEM MESSAGES

LAN Interface Release Report

26-W

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the LAN Interface Connection Failure, detected in Message [26-V], recovers. The

message displays when the LAN Interface Connection Failure is restored. The first data is normally sent/re-

ceived by the recovered application equipment.

TCP/IP Part

Application Part

1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX

11 12

13 14

15 16

17 18

19 20

21 22

23 24

➀➀➀ ➀➀➀ ➀➀➀ ➀ ➀

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀-➀ IP Address for external equipment in which error has been detected. (Hex.)

b7 b6 b5 b4 b3 b2 b1 b0

➀,➀➀➀Port No. (Client Port No.) (Hex.)

b7 b6 b5 b4 b3 b2 b1 b0

➀ Socket No. (Used Socket No.) (Hex.)

b7 b6 b5 b4 b3 b2 b1 b0

➀➀Error Code (TCP/IP Error Code) (Hex.)

See Table 3-2.

b7 b6 b5 b4 b3 b2 b1 b0

CHAPTER 3

Page 228

Issue 1

NDA-24300

SYSTEM MESSAGES

b0-b7: (Hex)

01=SUPER SERVER

➀ Application Type

b7 b6 b5 b4 b3 b2 b1 b0

02=MAT

03=SMDR

04=MCI

05=OAI

06=PMS

07=MIS

➀

[When ➀=03 (SMDR) / 04 (MCI) ]

b0-b7: (Hex)

➀ Device Number of recovered client PC

Device Number of recovered Client PC

for external LAN Interface.

b7 b6 b5 b4 b3 b2 b1 b0

b0-b7: (Hex)

Recovery Information

01=Recovered

02~FF=Not defined

b7 b6 b5 b4 b3 b2 b1 b0

NDA-24300

CHAPTER 3

Page 229

Issue 1

SYSTEM MESSAGES

MUX Clock Restore

33-A

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the MUX (PH-PC36) card, whose clock function was detected as faulty, is recov-

ered.

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀ Unit, MG number for MUX card,

b0-b1: Unit number for the recovered MUX card

which recovered from a clock

failure

b2:

b3:

MG number for the recovered MUX card

0/1 = fault recovery in the MUX No. 0 system / fault recovery in

MUX No. 1 system

b4 b3 b2 b1 b0

b4:

0/1 = faulty MUX is in ACT/

Faulty MUX is in STBY

➀ RLS Data

RLS Data:Clock alarm information on the recovered MUX card

b1:

b2:

b3:

0/1 = -/FH failure for 2M PCM Highway

0/1 = -/CLK failure for 2M PCM Highway

0/1 = -/4M CLK failure for PM

b3 b2 b1 b0

CHAPTER 3

Page 230

Issue 1

NDA-24300

SYSTEM MESSAGES

SDT Alarm Warning

33-B

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when an abnormal state is detected temporarily on the SDT (PA-SDTA/B) card.

1: X0XX 00XX XXXX XX00 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀ MG (Module Group)

b7:

0/1 = Even-number MG/Odd-number MG

➀➀Details on alarm

b4, b3

0 0

0 1

1 0

b2-b0

0 0 0

b4 b3 b2 b1 b0

0 0 1 Hardware Failure

0 1 0 Optical Line Failure

0 1 1 Onboard Power Alarm

0 0 0

SDT Card

Trouble

0 0 1 PCM Loss

0 1 0 Frame Alignment Loss

0 1 1 Receiving Section Failure

1 0 0 Mistake Rate Degradation

1 0 1 Sending Section Failure

1 1 0 Mistake Detection

0 0 0

0 0 1 Receiving Path Failure

0 1 0 Pointer Failure

0 1 1 Sending Path Failure

1 0 0 Receiving Path Error

1 0 1 Sending Path Error

52M Interface

Alarm

VC-11 Path

Trouble

Note

b7:

SDT Card Status

0/1=No. 0 System/No.1 System

Note: Alarm-detected HW is specified in ➀ (next page).

NDA-24300

CHAPTER 3

Page 231

Issue 1

SYSTEM MESSAGES

➀➀Alarm-detected HW

The data here specifies the HW, on which any of the VC-11 Path

Trouble was detected in data ➀ (see Note). Refer to the table below:

b7 b6 b5 b4 b3 b2 b1 b0

28 27 26 25

24 23 22 21 20 19 18 17

0/1=-/VC-11 Path Trouble

16 15 14 13 12 11 10

Note: This data displays only when b4 is “1” and b3 is “0” in data ➀.

Repair Procedure

Basically, fault repair work is not required by the display of this message. However, if the message is created

frequently, it is recommended that the repair work be performed as shown in the message [33-C] SDT Alarm

Trouble.

CHAPTER 3

NDA-24300

Page 232

Issue 1

SYSTEM MESSAGES

SDT Alarm Trouble

33-C

Default Alarm:

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when a grave failure occurs on the SDT (PA-SDTA/B) card. If this is issued, remember

the ACT/STBY change of the SDT card may be followed, as a result of fault detection in the optical fiber line

(see [33-E] message).

1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀ MG (Module Group)

b7:

0/1 = Even-number MG/Odd-number MG

➀➀Details on alarm

b4, b3

0 0

0 1

1 0

b2-b0

0 0 0

b4 b3 b2 b1 b0

0 0 1 Hardware Failure

0 1 0 Optical Line Failure

0 1 1 Onboard Power Alarm

1 0 0 Abnormal MB Key Operation

0 0 0

SDT Card

Trouble

0 0 1 PCM Loss

0 1 0 Frame Alignment Loss

0 1 1 Receiving Section Failure

1 0 0 Mistake Rate Degradation

1 0 1 Sending Section Failure

1 1 0 Mistake Detection

0 0 0

0 0 1 Receiving Path Failure

0 1 0 Pointer Failure

0 1 1 Sending Path Failure

1 0 0 Receiving Path Error

1 0 1 Sending Path Error

52M Interface

Alarm

VC-11 Path

Trouble

Note

b7:

SDT Card Status

0/1=No. 0 System/No.1 System

Note: Fault repair procedure on each alarm is shown on the next page.

NDA-24300

CHAPTER 3

Page 233

Issue 1

SYSTEM MESSAGES

Repair Procedure

Depending on the fault status shown in data ➀, perform necessary repair work:

(1) Hardware Failure/Onboard Power Alarm

SDT (PA-SDTA/B) card is faulty. Replace the card with a spare by referring to Chapter 4, Section 3.3.3,

SDT Card Replacement Procedure.

(2) Optical Line Failure

Diagnosis: In addition to this alarm, is the “PCM Loss” alarm also indicated?

YES → Optical line side is faulty.

Verify that the SDT card in the distant node is not placed into make-busy state. Also, perform the

light level check of the optical fiber cables.

NO → SDT card is faulty.

Replace the SDT card with a spare by referring to Chapter 4, Section 3.3.3, SDT Card Replace-

ment Procedure.

(3) Abnormal MB Key Operation

This alarm is indicated when the MB key on the PA-SDTA card is turned ON, even though the MBR key

has been on the OFF side. Place the MBR key UP (=ON) and then turn ON the MB key.

(4) PCM Loss

Abnormal state is detected on the optical line side. Verify that the SDT card in the distant node is not

placed into make-busy state. Also, perform the light level check of the optical fiber cables.

(5) 52M Interface Alarm

- Frame Alignment Loss

- Receiving Section Failure

- Mistake Rate Degradation

- Sending Section Failure

- Mistake Detection

Clock synchronization with the distant node might be lost, or a trouble might occur on the optical line

side. Check the PLO cards first in both self-node and distant node. When no fault is found, proceed with

the light level check of the optical fiber cables.

CHAPTER 3

Page 234

Issue 1

NDA-24300

SYSTEM MESSAGES

(6) Receiving Path Failure/Receiving Path Error

Abnormal state is detected in the process of multiplexing the “Receive” signals. To restore this, perform

the following:

STEP 1 Initialization of SDT card (distant node)

Initialize the SDT card in the distant node, and observe the situation. If the fault is not restored,

proceed with STEP 2.

STEP 2 Initialization of SDT card (self-node)

Initialize the SDT card in the self-node, and observe the situation. If the fault is not restored,

proceed with STEP 3.

STEP 3 Replacement of SDT card

It cannot be confirmed which node side (self-node or distant node) is faulty. By referring to

Chapter 4, Section 3.3.3, SDT Card Replacement Procedure, first replace the SDT card only in

one of the nodes. When the fault does not recover, then also replace the SDT card in other side

of the nodes.

(7) Pointer Failure/Sending Path Failure/Sending Path Error

Abnormal state is detected in the process of multiplexing the “Send” signals. To restore this, perform the

following:

STEP 1 Initialization of SDT card

Initialize the SDT card in the self-node, and observe the situation. If the fault is not restored,

proceed with STEP 2.

STEP 2 Replacement of SDT card

By referring to Chapter 4, Section 3.3.3, SDT Card Replacement Procedure, replace the SDT

card in the self-node with a spare.

NDA-24300

CHAPTER 3

Page 235

Issue 1

SYSTEM MESSAGES

SDT Alarm Restore

33-D

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the SDT (PA-SDTA/B) card or optical fiber line, which was once detected as

faulty, recovers.

1: X0XX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀ MG (Module Group)

b7:

0/1 = Even-number MG/Odd-number MG

➀➀Details on the fault

b4, b3

0 0

0 1

1 0

b2-b0

0 0 0

b4 b3 b2 b1 b0

0 0 1 Hardware Failure

0 1 0 Optical Line Failure

0 1 1 Onboard Power Alarm

1 0 0 Abnormal MB Key Operation

0 0 0

SDT Card

Trouble

0 0 1 PCM Loss

0 1 0 Frame Alignment Loss

0 1 1 Receiving Section Failure

1 0 0 Mistake Rate Degradation

1 0 1 Sending Section Failure

1 1 0 Mistake Detection

0 0 0

0 0 1 Receiving Path Failure

0 1 0 Pointer Failure

0 1 1 Sending Path Failure

1 0 0 Receiving Path Error

1 0 1 Sending Path Error

52M Interface

Alarm

VC-11 Path

Trouble

b7:

SDT Card Status

0/1=No. 0 System/No.1 System

CHAPTER 3

Page 236

Issue 1

NDA-24300

SYSTEM MESSAGES

SDT Interface Change Notify

33-E

Default Alarm:

NON

Default Grade:

Grade Modified:

Lamp Modified:

This message displays when the ACT/STBY of the SDT (PA-SDTA) card is changed over as a result of fault

detection in the optical fiber line. When the ACT/STBY change cannot be performed, this message also indi-

cates the cause for the changeover execution failure.

1: X0XX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000

➀➀➀

4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000

7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000

➀➀ MG (Module Group)

b7:

0/1 = Even-number MG/Odd-number MG

➀➀Detailed information

b0:

b1:

Active SDT after Changeover

0/1=No.0 System/No.1 System

Operating Status of SDT

b7 b6 b5 b4 b3 b2 b1 b0

0/1=In service/Out of service

b2, b3: Result of Changeover

0/1=Success/Failure

b7-b4

0001

0010

Cause for Changeover

SDT had a serious failure

MB key on SDT card was turned ON

➀➀Cause for changeover execution failure

b7 b6 b5 b4 b3 b2 b1 b0

0H: (Changeover Success)

1H: Optical interface isn’t dual

2H: Optical interface has a serious failure in each No.0/No.1 system

Repair Procedure

Once this message displays, be sure to check other messages, such as [33-C] SDT Alarm Trouble, and review

the cause for the changeover. If any fault is implicated, repair the whole fault(s) according to the situation.

NDA-24300

CHAPTER 3

Page 237

Issue 1

This page is for your notes.

CHAPTER 3

Page 238

Issue 1

NDA-24300

CHAPTER 4

Unit/Circuit Card Replacement Procedure

1. LPM Accommodating Unit/Circuit Card Replacement Procedure

This section explains how to replace unit/circuit cards mounted in the LPM.

1.1 Precaution

•

Use this procedure to replace a faulty unit/circuit card with a spare or to check a spare card.

There are functional switches (having set the default switch) on some of the circuit cards to be replaced.

As for switch setting on the circuit cards, confirm the circuit card mounting face layout for the LPM.

When a circuit card with a default switch setting is replaced with a spare card, always make the switch

setting on the new circuit card the same as on the replaced card. Otherwise, electronic components on

the circuit card may be destroyed, or the circuit card itself may fail to function normally.

•

When handling a circuit card, always use the field service kit for countermeasures against static elec-

tricity. Touching a circuit card without using the field service kit may destroy the card due to static elec-

tricity on the human body.

1.2 Circuit Card Mounting Face Layout

Figure 4-1 shows the face layout of circuit cards mounted in the LPM. The circuit cards marked with * are

optional.

NDA-24300

CHAPTER 4

Page 239

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

PZ-PW92

PZ-IO27

Note

LANI(PZ-PC19)

GATE(PZ-GT16)

HDDMB

FDD

CPUOPEWDT IMG0

MBR

IMG1 IMG2 IMG3

OFF

SYSTEM SELECT0

STATUS

OFF

SYSTEM SELECT1

SENSE

OUT PWR

OFF

PALM

^EC

SYSTEM SELECT2

CPURST

OFF

IN PWR

SLOT No.

LPM

HDDMB

FDD

CPUOPEWDT IMG0

IMG1 IMG2 IMG3

MBR

OFF

SYSTEM SELECT0

STATUS

OFF

SYSTEM SELECT1

SENSE

OUT PWR

OFF

PALM

^EC

SYSTEM SELECT2

CPURST

OFF

IN PWR

OFF

SLOT No.

CPR

FRONT VIEW

Note: In place of PZ-IO27, the CPR may be equipped with PZ-IO28, which does not have the MB

(Make-busy) key.

Figure 4-1 Circuit Card Mounting Face Layout of LPM

CHAPTER 4

NDA-24300

Page 240

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

1.3 Operating Procedures

The following paragraphs provide operating procedures to replace unit/circuit cards of the LPM. Perform

the operations that correspond to each Reference Item specified in T a ble 4-1.

Table 4-1 LPM Unit/Circuit Cards and Reference Items

UNIT/CIRCUIT CARD

REFERENCE ITEM

REMARKS

CPR

CPU, ISAGT,

LANI

EMA Card

IOC Card

Section 1.3.2, EMA Card Replacement Procedure

Section 1.3.3, IOC Card Replacement Procedure

Section 1.3.4, Power Supply Unit Replacement Procedure

Section 1.3.5, MISC Card Replacement Procedure

PWR Unit

MISC Card

Improper key operations may result in a system down. Operate the key using extreme care.

During replacement of a circuit card, the system issues system messages and activates the related

alarm. Reset the indicated alarm after completing the replacement procedure.

WARNING

If the indicated alarm is cleared via the RALM command, the system also clears the contents of the system

message. Before using the RALM command, print the messages using the DFTD command.

Use the ALM RST button only to reset the alarm lamps.

NDA-24300

CHAPTER 4

Page 241

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

1.3.1 CPR Replacement Procedure

This section explains how to replace the Control Processor Rack (CPR). Before

starting the procedures, make a backup copy of the main data, such as office data,

Call Forwarding (CF) data and Speed Calling (SPD) data, on to the hard disk of the

HFC. Figure 4-2 shows the front view of the CPR. Operate the related keys and con-

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

nectors to replace the CPU with a new one. Using a Phillips screwdriver, remove the four screws and

extract the CPR with care, as shown in Figure 4-3.

Note

PZ-IO27

HDD MB

FDD

CPUOPEWDT IMG0

MBR

IMG1 IMG2 IMG3

OFF

SYSTEM SELECT0

STATUS

OFF

SYSTEM SELECT1

SENSE

OUT PWR

OFF

^EC

PALM

SYSTEM SELECT2

CPURST

OFF

IN PWR

SLOT No.

PZ-PW92

Note: In place of PZ-IO27, the CPR may be equipped with PZ-IO28, which does not have the MB

(Make-Busy) key.

Figure 4-2 CPR Face Layout

CHAPTER 4

NDA-24300

Page 242

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

PBX

..........

LPM

SLO

No.

.....

SLOT No.

CPR

Figure 4-3 How to Replace the CPU

NDA-24300

CHAPTER 4

Page 243

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

[Circuit Card Accommodation into the New CPR]

The steps below show the procedure to install the new CPR into the LPM.

ATTENTION

Contents

Static Sensitive

STEP 1 Using the Phillips Screwdriver, remove the 4 + 8 screws. Then, detach the

front panel and top cover from the new CPR. (Refer to Figure 4-4)

Handling

Precautions Required

As shown in Figure 4-4, detach the front panel of the new CPR by removing the 4 screws.

Then, also lift away the top cover by removing the 8 screws.

Top Cover

Front Panel

CPR

Figure 4-4 Removal of Front Panel and Top Cover from CPR

CHAPTER 4

Page 244

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

STEP 2 Insert the ISAGT (PZ-GT13) and LANI (PZ-PC19) cards into the

following slots of the new CPR (refer to Figure 4-5):

ISAGT (PZ-GT13) →

Slot #6 (ISA)

ATTENTION

Contents

Static Sensitive

LANI (PZ-PC19)

→

Slot #0 (PCI)(For Fusion Link)

Slot #1 (PCI)(When connecting MAT via 10-

Handling

Precautions Required

LANI (PZ-PC19)

BASE T and PCI buses)

→

LANI (PZ-PC19)

Section 2.3.1, GT Card Replacement Procedure

→

Slot #3 (PCI)(When LANI for Fusion Link is in dual configuration)

Figure 4-5 shows how to insert the ISAGT and LANI cards into CPR slots #6 (ISA),

and #0, #1 and #3 (PCI), respectively.

ISAGT

LANI

Slot 6 (ISA)

Slot 3 (PCI)

Slot 1 (PCI)

Slot 0 (PCI)

CPR

Note: Accommodation of the second LANI (in PCI Slot 3) is optional.

Figure 4-5 Insertion of ISAGT and LANI Cards

NDA-24300

CHAPTER 4

Page 245

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

STEP 3 Reattach the top cover and front panel by fastening the removed screws.

(Refer to Figure 4-6)

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

After mounting the ISAGT/LANI cards, reattach the top cover by tightening the 8 screws.

Then, attach the Front Panel by fastening the 4 screws.

Top Cover

Front Panel

CPR

Figure 4-6 Reattachment of CPR Top Cover and Front Panel

CHAPTER 4

Page 246

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

STEP 4 After turning “ON” the MBR key on the DSP of the new CPR, insert the

new CPR into the LPM. Then, fasten the retained four screws. (Refer to

Figure 4-7)

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

As shown in Figure 4-7, insert the new CPR into the LPM. Then, fasten the four screws.

LPM

CPR

Figure 4-7 Accommodation of New CPR into LPM

NDA-24300

CHAPTER 4

Page 247

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

STEP 5 Insert the new HFD into the CPR. Then, fasten the two screws.

(Refer to Figure 4-8)

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

By using the two screws, fasten the new HFD onto the CPR.

LPM

HFD (PZ-IO27/PZ-IO28)

Figure 4-8 Insertion of New HFD into CPR

CHAPTER 4

Page 248

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

Replacement Procedure

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

DSP

CPUOPEWDT IMG0

MBR

IMG1 IMG2 IMG3

Make a backup copy of the main data (office data,

CF/SPD data, etc.) onto the hard disk of the HFC.

OFF

^EC

OFF

FRONT VIEW

Turn ON the MBR key on the DSP of the CPU

to be replaced. Then turn OFF the MBR key again.

• System Changeover of the CPU

from ACT to STBY mode.

• IMG0 lamp on the DSP begins to

flash green.

Confirm the mate CPU's ACT mode.

• Check the mate CPU’s lamp

indications:

CPU OPE=Steady green

IMG0, IMG1, IMG2, IMG3=Flash

green

Turn ON the EMA SUP key on the

EMA (PH-PC40) card.

• EMA SUP lamp on the EMA card is

green.

PWR (PZ-PW92)

Disconnect the power alarm cable from

the PALM connector on PZ-PW92.

OFF

-48V

PALM

Cable Name to be disconnected

CPU #0: 10AL-(110) FLT CA

CPU #1: 10AL-(130) FLT CA

OUTPWR

ALM

INPWR

FRONT VIEW

NDA-24300

CHAPTER 4

Page 249

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

PWR (PZ-PW92)

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

OFF

-48V

Turn OFF the SW key on PZ-PW92.

PALM

OUTPWR

INPWR

Disconnect power cables from the OUTPWR

connector and INPWR connector on PZ-PW92.

ALM

Cable to be disconnected from OUTPWR

CPU #0: 6P-(4P-3P) PWR CA-A

CPU #1: 6P-(4P-3P) PWR CA-B

FRONT VIEW

Cable to be disconnected from INPWR

CPU #0: 4P-2P PWR CA-A

CPU #1: 4P-2P PWR CA-B

• Refer to Figure 4-2 for CPR

Disconnect bus cables from the front connectors

on the PZ-GT16.

face layout.

Cables to be disconnected

EXGT BUSCA-A for CN-A connector

50-40 GT BUS CA-A for CN-B connector

• Refer to Figure 4-2 for CPR

Disconnect Ethernet cables from the front

connectors on the PZ-PC19 (LANI).

face layout.

Cables to be disconnected

Ether cable: UTP CTG5 ST CA-n

Note: The kind of Ethernet cable may vary,

vary, depending on its connecting

conditions.

• Refer to Figure 4-3 to replace

Take off the four screws fastened onto the CPR.

(Keep the removed screws.)

the CPU.

CHAPTER 4

NDA-24300

Page 250

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

• Refer to Figure 4-3 to replace

the CPU.

Extract the CPR from the LPM.

DSP

CPUOPEWDT IMG0

MBR

IMG1 IMG2 IMG3

Turn ON the MBR key on the DSP of

the new CPR.

OFF

^EC

OFF

FRONT VIEW

Mount ISAGT (PZ-GT13) and LANI (PZ-PC19)

cards onto the new CPR. Then, insert the new

CPR into the LPM.

• Refer to Circuit Card Installation

Into New CPR procedure in this

section.

NDA-24300

CHAPTER 4

Page 251

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Connect the disconnected and Ethernet cables

to the connectors on the PZ-PC19.

Connect the disconnected bus cables

to the connectors on the PZ-GT13.

Connect the disconnected power cables to

the OUTPWR and INPWR connectors.

PWR (PZ-PW92)

Note: Do not connect the cable for the

PALM connector yet.

OFF

-48V

PALM

Turn ON the SW key on PZ-PW92.

OUTPWR

INPWR

ALM

Connect the disconnected power alarm cable

to the PALM connector on PZ-PW92.

FRONT VIEW

CHAPTER 4

NDA-24300

Page 252

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

• EMA SUP lamp on the EMA card

Turn OFF the EMA-SUP key on the EMA

(PH-PC40) card.

goes OFF.

MBR(DSP)

Flip the MBR key on the DSP of the new

CPR from ON to OFF.

Initial Program Load (IPL)

starts automatically.

Confirm that IPL has completed successfully.

• IMG0 lamp on the DSP flashes

green.

DSP

CPUOPEWDT IMG0

MBR

END

IMG1 IMG2 IMG3

OFF

^EC

OFF

FRONT VIEW

NDA-24300

CHAPTER 4

Page 253

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

Circuit Card Installation Into New CPR

This procedure shows how to install the new CPR into the LPM.

ATTENTION

Contents

Static Sensitive

(1) Detach the front panel of the new CPR by using the Phillips screwdriver to remove

the four screws, as shown in Figure 4-9. Then, lift the top cover by removing the

eight screws.

Handling

Precautions Required

As shown in the figure below, detach the front panel of the new CPR by removing the 4 screws.

Then, also lift away the top cover by removing the 8 screws.

Top Cover

Front Panel

CPR

Figure 4-9 Removal of Front Panel and Top Cover From CPR

CHAPTER 4

NDA-24300

Page 254

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

(2) Insert the ISAGT (PZ-GT13) and LANI (PZ-PC19) cards into the following slots of

the new CPR (refer to Figure 4-10):

ATTENTION

ISAGT (PZ-GT13) →Slot #6 (ISA)

Contents

Static Sensitive

Handling

Precautions Required

LANI (PZ-PC19) →Slot #0 (PCI) (For Netfusing Link)

LANI (PZ-PC19) →Slot #1 (PCI) (When connecting MAT via 10-BASE T and PCI buses)

LANI (PZ-PC19) →Slot #3 (PCI) (When LANI for Netfusing Link is in dual configuration)

Note: The location of the second LANI (PCI Slot 3) is optional.

This figure (example) shows how to insert the ISAGT and LANI cards into CPR slots #6 (ISA),

and #0, #1 and #3 (PCI), respectively.

ISAGT

LANI

Slot 6 (ISA)

Slot 3 (PCI)

Slot 1 (PCI)

Slot 0 (PCI)

CPR

Note : Accommodation of the second LANI (in PCI slot 3) is optional (since Release 3 or later).

Figure 4-10 Insertion of ISAGT and LANI Cards

NDA-24300

CHAPTER 4

Page 255

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

(3) Reattach the top cover by fastening the removed eight screws. Then, reattach the

front panel by fastening the removed four screws. Refer to Figure 4-11.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Top Cover

Front Panel

CPR

Figure 4-11 Reattachment of CPR Top Cover and Front Panel

CHAPTER 4

Page 256

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

(4) After turning ON the MBR key on the DSP of the new CPR, insert the new CPR into

the LPM as shown in Figure 4-12. Then, fasten the retained four screws.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

LPM

CPR

Figure 4-12 Location of New CPR Into LPM

NDA-24300

CHAPTER 4

Page 257

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

(5) Lastly, insert the new HFD into the CPR. Then, fasten the two screws

as shown in Figure 4-13.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

By using the two screws, fasten the new HFD onto the CPR.

LPM

HFD (PZ-IO27/PZ-IO28)

Figure 4-13 Insertion of New HFD Into CPR

1.3.2 EMA Card Replacement Procedure

The EMA (PH-PC40) card is mounted in Slot No. 04 of the LPM. The main func-

tions of the card are as follows:

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

•

Designation of ACT/STBY status of the CPU and forced changeover of the sys-

tem

•

Shutoff of the system’s power supply and detection of rising temperature within the system

Music source for Music-On-Hold (for 1-IMG system only)

Control of the NCU (PA-M53) card

CHAPTER 4

NDA-24300

Page 258

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

Before replacing the EMA card, check the CPU #0’s ACT mode. Attempting to replace the card

WARNING

when the CPU is active will result in the system being initialized.

Replacement Procedure

• Check the CPU OPE lamp of DSP

#1. When the lamp is steady-green,

perform the system changeover.

CPU is Active?

YES

Turn ON the MBR key on the DSP #1.

(System Changeover of CPU #1: ACT

STBY)

Turn ON the MB key on the EMA (PH-PC40) card.

• OPE/MB lamp on the EMA card

lights red from green.

• When NCU (PA-M53) cards are

mounted, Power Failure Transfer

(PFT) is activated.

Extract the EMA card from the LPM.

NDA-24300

CHAPTER 4

Page 259

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Set the keys on the new card by referring to the

card being replaced.

Turn ON the MB and EMA SUP keys on the

new card.

Insert the new card into the LPM.

Turn OFF the MB and EMA SUP keys on the card.

• OPE/MB lamp on the EMA card is

steady-green.

• PFT service is cancelled:

Assign the time data by using the ATIM command.

resumption of normal operation.

END

CHAPTER 4

Page 260

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

1.3.3 IOC Card Replacement Procedure

The IOC (PH-IO24) card is mounted in Slot No. 02 and/or 03 of the LPM. The

card’s main function is to provide a serial interface between the system and its ex-

ternal equipment, such as the Maintenance Administration Terminal (MAT), Sta-

tion Message Detail Recording System (SMDR), Message Center Interface (MCI),

Property Management System (PMS), etc.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

The equipment connected to the I/O ports of each card (MAT, SMDR, etc.) cannot be used while

replacing the IOC card.

ATTENTION

Replacement Procedure

• OPE lamp on the IOC card first

flashes and then becomes red.

Turn ON the MBR key on the IOC (PH-IO24)

card to be replaced.

• All I/O ports are closed and the

equipment, such as MAT and

SMDR, loses connections.

Note: The text data (such as

billing

information),

registered before this step,

will be safely transmitted

later. However, the data,

recorded after this step,

will not be sent out, and

instead is stored in the

buffer.

Turn ON the MB key on the card.

Extract the card from the LPR.

• OPE lamp on the IOC card goes

Set the keys on the new card, referring to the

card to be replaced.

NDA-24300

CHAPTER 4

Page 261

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Turn ON the MB and MBR keys on the

new card.

Insert the new card into the LPM.

Turn OFF the MB key on the card.

• OPE lamp on the IOC card is red.

• Release of I/O ports: new IOC card

is initialized, and I/O port channels

reopens.

Turn OFF the MBR key on the card.

• OPE lamp is green.

END

CHAPTER 4

Page 262

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

1.3.4 Power Supply Unit Replacement Procedure

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

• CPU System

Set the mode of the PWR UNIT (PZ-PW92)

to be replaced into STBY mode.

Changeover

Refer to Sectio n 1 2.1.2

in Chapter 6.

On the EMA (PH-PC40) card, set EMA SUP

switch UP.

Disconnect the power alarm cable from the

PALM connector on the PZ-PW92.

PWR (PZ-PW92)

Cable Name to be disconnected

CPU #0: 10AL-(110) FLT CA

CPU #1: 10AL-(130) FLT CA

OFF

-48V

Turn OFF the SW key on the PWR UNIT.

PALM

OUTPWR

ALM

INPWR

Disconnect the power cables from the OUTPWR

connector and INPWR connector on the PZ-PW92.

FRONT VIEW

Cable to be disconnected from OUTPWR

CPU #0: 6P-(4P-3P) PWR CA-A

CPU #1: 6P-(4P-3P) PWR CA-B

Cable to be disconnected from INPWR

CPU #0: 4P-2P PWR CA-A

CPU #1: 4P-2P PWR CA-B

NDA-24300

CHAPTER 4

Page 263

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Extract the PWR UNIT from the CPR.

Insert the new PWR UNIT into the LPM.

Reattach power cables to OUTPWR

and INPWR Connector on the PZ-PW92.

Turn ON the SW key on the PWR UNIT.

Reattach power alarm cable to the PALM

Connector on the PZ-PW92.

On the EMA card, set EMA SUP switch DOWN.

END

CHAPTER 4

Page 264

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

1.3.5 MISC Card Replacement Procedure

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

On the MISC card, set MB switch UP.

Extract the MISC card from its mounting slot.

• Keep MB switch UP.

Insert the new circuit card into the same

mounting slot.

On the MISC card, set MB switch DOWN.

END

NDA-24300

CHAPTER 4

Page 265

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

2. TSWM ACCOMMODATING CIRCUIT CARD REPLACEMENT PROCEDURE

This section explains the procedure for replacing circuit cards accommodated in the TSWM.

2.1 Precaution

•

This procedure is applied when replacing a faulty circuit card with a spare. It is also able to be applied

when checking a spare card.

There are the functional switches (having set the default switch) on some of the circuit cards to be

replaced. As for switch setting on the circuit cards, confirm the circuit card mounting face layout for

the PIM. When a circuit card that has default switch settings has been replaced with a spare card, be

sure to make switch settings on the new circuit card the same as on the replaced card. Otherwise, elec-

tronic components on the circuit card may be destroyed, or the circuit card itself may fail to function

normally.

•

When handling a circuit card, be sure to use the field service kit for countermeasures against static

electricity. If you touch a circuit card without using the field service kit, electronic components like

an IC on the card may be destroyed by the static electricity on the human body.

2.2 Circuit Card Mounting Face Layout

The face layout of the circuit cards housed in the TSWM is shown in Figure 4-4 Circuit Card Mounting

Face Layout of TSWM. Note that the circuit cards marked with * are optional.

TSWM

Slot No.

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PWRSW: PH-PW14

DLKC: PH-PC20

GT: PH-GT09

TSW: PH-SW12

PLO: PH-CK16/17

Figure 4-14 Circuit Card Mounting Face Layout of TSWM

Improper key operations may result in a system down. Operate the key, using extreme care.

WARNING

By replacing a circuit card, the system will issue system messages and activate the related alarm. Be sure to reset

the indicated alarm after the replacement procedure is complete.

If the indicated alarm is cleared via the RALM command, the system also clears the contents of the system mes-

sage. Be sure to print out the messages (using the DFTD command) BEFORE using the RALM command.

The ALM RST button is used to reset the alarm lamps only.

CHAPTER 4

Page 266

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

2.3 Operating Procedures

The following paragraphs explain the operating procedures to replace circuit cards located in the PIM.

Perform the operations corresponding to each Reference Item specified in Table 4-2.

Table 4-2 TSWM Circuit Cards and Reference Items

CIRCUIT CARD

FUNCTION NAME

REFERENCE ITEM

REMARKS

TSW

Section 2.3.2, TSW Card Replacement Procedure

Section 2.3.3, DLKC Card Replacement Procedure

Section 2.3.4, PLO Card Replacement Procedure

Section 2.3.5, PWR SW Card Replacement Procedure

Section 2.3.6, MISC Card Replacement Procedure

DLKC

PLO

PWR SW

MISC

NDA-24300

CHAPTER 4

Page 267

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

2.3.1 GT Card Replacement Procedure

The GT (PH-GT09) card is located in Slot No. 10 or 11 within the TSWM. The card’s main function

is to provide both MISC and I/O Local bus interface between the microprocessor of CPU and other

lower echelons, such as DLKC, TSW and MUX cards. Follow the procedures below to replace a GT

card with a spare.

Note: To replace the GT card, the ACT/STBY status of GT must be changed over first. This must be done by

operating the MBR key (or by using the CMOD command) on the DSP of active CPR. Figure 4-15

shows a system block diagram centering upon the CPU and its controlling GT. If the ACT/STBY of GT

is to be changed over, the system of CPU must be manually changed over. For more details on the GT

changeover, refer to Section 12.1.2, How to Control CPU Block, in Chapter 6.

IMG0

IMG1

IMG2

IMG3

MUX MUX MUX MUX

TSW 10

TSW 00

TSW 11

TSW 01

TSW 12

TSW 02

TSW 13

TSW 03

TSW I/O BUS

DLKC 1

DLKC 0

PLO 1

PLO 0

Note

GT 1

GT 0

CPR 1

ISAGT

CPR 0

ISAGT

CPU 0

GT 1

IOP0

GT 0

CPU 1

LANI LANI

Backboard Bus

Backboard

MISC BUS

ISAGT0

External Cable

IOC/

MISC

EMA

CPU

ISAGT: PZ-GT13

DLKC: PH-PC20

LANI: PZ-PC19

PLO: PH-CK16/17

GT: PH-GT09

EMA: PH-PC40

TSW: PH-SW12

IOC: PH-IO24

MUX: PH-PC36

Note: The connection between ISAGT and GT is somewhat unique in this system. As shown, though an

external cable is physically connected between ISAGT #0 and GT#1, the actual control signal is

sent/received only between ISAGT 0 and GT 0. This is because GT 0 and GT 1 have a multiple

connection on the backboard side.

Figure 4-15 System Block Diagram (Connections Between GT and CPU)

CHAPTER 4

NDA-24300

Page 268

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

GT Card Replacement Procedure

Use extreme care when operating the keys on the DSP of CPR and PH-GT09 card.

WARNING

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

• System changeover of GT from

On the DSP of active CPR, turn ON the MBR key.

Turn OFF the MBR key again.

ACT to STBY mode

DSP

GT (PH-GT09)

CPUOPE WDT IMG0

MBR

OPE/MB

IMG1 IMG2 IMG3

MBR

OFF

^EC

OFF

FRONT VIEW

Check the following lamp indications

on the GT card to be replaced and on

the DSP of CPR that controls the GT:

• OPE/MB (GT card) = OFF

• CPU OPE (CPU DSP) = OFF

• IMG0 (CPU DSP) = Flash (green)

Confirm the mate GT's ACT mode.

• IMG1-3 (CPU DSP) = OFF

Check the following lamp indications

on the mate GT card and the DSP of

the mate CPR:

• OPE/MB (GT card) = Steady-green

On the EMA (PH-PC40) card, set the

EMA SUP key UP.

• CPU OPE (CPU DSP) = Steady-

green

• IMG0-3 (CPU DSP) = Flash

(green)

EMA SUP lamp on the EMA card is

steady-green.

NDA-24300

CHAPTER 4

Page 269

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

On the GT card to be replaced,

set the MBR switch UP.

• OPE/MB lamp on the GT card

On the GT card to be replaced,

set the MB switch UP.

remains OFF.

Extract the GT card to be replaced

from the TSWM.

Set the MBR and MB keys on the new card UP.

Insert the new GT card into the TSWM.

Set the MB key on the new card DOWN.

• OPE/MB lamp on the new card is

OFF.

• OPE/MB lamp on the new card

Set the MBR key on the new card DOWN.

remains OFF.

CHAPTER 4

Page 270

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

EMA SUP lamp on the EMA card goes

OFF.

On the EMA card, set the EMA SUP switch DOWN.

System Changeover

Flip the MBR key on the DSP of CPU which controls

the mate GT. Confirm the new GT functions normally.

• Replaced GT: STBY to ACT

• Mate GT: ACT to STBY

Check the following lamp indications on

the new GT card and the DSP of the CPR

which controls the GT.

• OPE/MB (GT card) = Steady-green

• CPU OPE (CPU DSP) = Steady-green

• IMG0-3 (CPU DSP) = Flash (green)

Note: IMG2~3 lamp indications may

vary depending on the system

configuration.

Check the following lamp indications on

the mate GT card and the DSP of the

mate CPR:

END

• OPE/MB (GT card) = OFF

• CPU OPE (CPU DSP) = OFF

• IMG0 (CPU DSP) = Flash (green)

• IMG1-3 (CPU DSP) = OFF

Note: The system changeover of GT can be executed also by using the CMOD command. For details, refer to

Chapter 8, Maintenance Commands.

NDA-24300

CHAPTER 4

Page 271

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

2.3.2 TSW Card Replacement Procedure

The TSW (PH-SW12) card is located in the Slot Nos. ranging from 12 to 19 within the TSWM.

Equipped with the Time Division Switch (TSW) and Speech Path Controlling Interface (INT), the

card’s main function is to provide a maximum of 8192 × 2048 Time Slot (TS) switching for a desig-

nated single IMG. Because a single TSW card only enables the TS switching associated with a single,

individual IMG alone, note that the fully expanded 4-IMG system requires a total of 4 TSW cards

when it adopts a single configuration, or as many as 8 in the case of dual configuration. If your system

adopts the latter’s dual configuration, the card’s replacement procedures are as follows:

Note: To replace a TSW card in dual configuration, the system of the card must be changed over from ACT to

STBY mode. The changeover can be done by flipping the MBR key on the active GT (PH-GT09) card

or by using the CMOD command. For more details, refer to Section 12, System Control Procedures, in

Chapter 6.

Figure 4-16 provides the system block diagram centering upon the TSW cards. If the system of TSW/

INT is changed over, the ACT/STBY of DLKC and MUX in the same switching block are also totally

changed over. The changeover can be performed by flipping the MBR key on the active GT (PH-GT09)

card, or by using the CMOD command.

CHAPTER 4

Page 272

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

IMG0

IMG1

IMG2

IMG3

Line/Trunk PM

MUX MUX MUX MUX

MUX MUX MUX MUX MUX MUX MUX MUX

MUX MUX MUX MUX

TSW 10

TSW 00

TSW 11

TSW 12

TSW 13

TSW 03

TSW 01

TSW 02

TSW I/O BUS

DLKC 1

DLKC 0

PLO 1

PLO 0

GT 1

GT 0

CPR 1

ISAGT

CPU 1

CPR 0

ISAGT

CPU 0

LANI LANI

ISAGT: PZ-GT13

DLKC: PH-PC20

LANI: PZ-PC19

PLO: PH-CK16/17

GT: PH-GT09

TSW: PH-SW12

MUX: PH-PC36

Figure 4-16 System Block Diagram (TSW and Other Speech Path Echelons)

NDA-24300

CHAPTER 4

Page 273

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

TSW Card Replacement Procedure

Use extreme care when operating the keys on the circuit card.

WARNING

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

System Changeover. Check the following

lamp indications on the circuit cards to be

affected and ensure that they are all OFF:

On the active GT (PH-GT09) card, set the MBR key

UP. Then, return the key DOWN.

• TSW ACT (TSW cards)

• OPE/MB (DLKC card) Note

• MUX ACT (MUX cards)

Note: If the TSW card to be replaced

represents system status #0, all

the circuit cards with #0 status

are totally affected. Check the

whole cited cards' lamp

indications. (See Figure 4-16

and Figure 4-17.)

Check the ACT mode of the mate

Speech Path System.

Check the following lamp indications on

the mate Speech Path block and ensure that

they are all steady-green:

On the TSW (PH-SW12) card to be replaced,

set the TSW MBR key UP.

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

• MUX ACT (MUX cards)

TSW ACT lamp on the TSW card remains

OFF.

GT (PH-GT09)

OPE/MB

MUX (PH-PC36)

DLKC (PH-PC20)

OPE/MB

TSW (PH-SW12)

TSW ACT

MUX ACT

MBR

TSW MBR

FRONT VIEW

Figure 4-17 LEDs and Switches for TSW Changeover

NDA-24300

CHAPTER 4

Page 274

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

• TSW ACT lamp on the TSW card is

On the TSW card to be replaced,

set the MB switch UP.

red.

Extract the TSW card to be replaced

from the TSWM.

Set the keys on the new card,

referring to the card replaced.

Set TSW MBR and MB keys on the new card UP.

Insert the new TSW card into the TSWM.

• TSW ACT lamp on the new card is

red.

Confirm M0SY, M1SY, M2SY, and M3SY

LEDs on the new card are all green.

NDA-24300

CHAPTER 4

Page 275

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

• TSW ACT lamp on the new card

goes OFF.

Set the MB key on the new card DOWN.

• TSW ACT lamp on the new card

Set the TSW MBR key on the new card DOWN.

remains OFF.

MBR (on the active GT card)

Flip the MBR key on the active GT card. Confirm the

new TSW card functions normally.

System Changeover

• Replaced TSW: STBY to ACT

• Mate TSW: ACT to STBY

Check the following lamp indications

on the Speech Path block to which the

new TSW card belongs and ensure that

they are all steady-green:

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

END

• MUX ACT (MUX cards)

Check the following lamp indications

on the mate Speech Path block and en-

sure that they are all OFF:

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

• MUX ACT (MUX cards)

Note: The system changeover of TSW card can be executed also by using the CMOD command. For details,

refer to Chapter 8, Maintenance Commands.

CHAPTER 4

NDA-24300

Page 276

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

2.3.3 DLKC Card Replacement Procedure

The DLKC (PH-PC20) card is located in Slot No. 08 or 09 within the TSWM. The card’s main function

is to provide all the Attendant/Desk Consoles with information such as termination/answer/release

(abandoned) of ATT calls or idle/busy status of a station via the link of the TSW system. Use the fol-

lowing procedures to replace the DLCK card with a spare.

Note: The system changeover of DLKC must be executed by the MBR key operation on the active GT (PH-

GT09) card or by using the CMOD command. Before starting this work, confirm the system block

diagram shown in Figure 4-16, or Section 12, System Control Procedures, in Chapter 6.

Replacement Procedure

Use extreme care when operating the keys on the circuit card.

WARNING

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

System Changeover

On the active GT (PH-GT09) card, set the MBR key

Check the following lamp indications

UP. Then, return the key DOWN.

on the circuit cards to be affected and

ensure that they are all OFF:

• TSW ACT (TSW cards)

• OPE/MB (DLKC card) Note

• MUX ACT (MUX cards)

Note: If the DLKC card to be

replaced represents system

status #0, all circuit cards

with #0 status are totally

Check the ACT mode of the mate

Speech Path System.

affected. Check the cited

cards' lamp indications. See

Figure 4-16 and Figure 4-

17.

On the DLKC (PH-PC20) card to be

replaced, Set the MB switch UP.

Check the following lamp indications

on the mate Speech Path Block and en-

sure that they are all steady-green:

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

• MUX ACT (MUX cards)

OPE/MB lamp on the DLKC card is

red.

NDA-24300

CHAPTER 4

Page 277

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Extract the DLKC card to be replaced

from the TSWM.

• TSW ACT lamp on the new card is red.

• TSW ACT lamp on the new card goes

On the new DLKC card, set the MB switch UP.

Insert the new DLKC card into the TSWM.

On the new DLKC card, set the MB key DOWN.

OFF.

System Changeover

• Replaced DLKC: STBY to ACT

• Mate DLKC: ACT to STBY

MBR (on the active GT card)

Check the following lamp indications on the

Speech Path block to which the new DLKC

card belongs and ensure that they are all

steady-green:

Flip MBR key on the active GT card. Confirm the

new DLKC card functions normally.

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

• MUX ACT (MUX cards)

Check the following lamp indications on the

mate Speech Path block and ensure that they

are all OFF:

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

END

• MUX ACT (MUX cards)

Refer to Figure 4-16 and Figure 4-17.

Note: The changeover of speech path system can be performed also by using the CMOD command. For

details, refer to Chapter 8, Maintenance Commands.

CHAPTER 4

NDA-24300

Page 278

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

2.3.4 PLO Card Replacement Procedure

The PLO (PH-CK16/17/16-A/17-A) card is located in Slot No. 21 or 23 within the TSWM. Used to-

gether with a different direct digital interface circuit card, the card’s main function is to set up the clock

synchronization on the network. In addition, the MUSIC ROM supplies the hold tone to each station

line via the TSW circuit card. Use the procedures below to replace the PLO card with a spare.

Note: The ACT/STBY of PLO can be changed over via a single MB key operation on the circuit card. Though

its circuit is controlled by the GT (PH-GT09) card via TSW I/O bus, the switching system of PLO is not

affected by the speech path system changeover, differing from other echelons such as TSW, MUX,

DLKC. Refer to Section 12, System Control Procedures, in Chapter 6.

Replacement Procedure

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

On the PLO (PH-CK16/17/16-A/17-A) card to be

replaced, set the MB key UP.

• PLO system is changed over from

ACT to STBY mode.

• OPE lamp on the PLO card goes

OFF.

Check the mate PLO's ACT mode.

Check the mate PLO card's following

lamp indication:

• OPE = Steady-green

Extract the PLO card to be replaced

from the TSWM.

Set the keys on the new card according to

the card replaced.

NDA-24300

CHAPTER 4

Page 279

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

On the new PLO card, set the MB key UP.

Insert the new PLO card into the TSWM.

Set the MB key on the new card DOWN.

END

• OPE lamp on the new card is OFF.

Note

Note: After all steps are completed, check the ACT mode of TSW cards, which are in the same switching block

with the replaced PLO. Because the PLO-located MUSIC ROM supplies hold tones only to the TSW

cards belonging to the same switching block, verify all the TSW cards are also in the ACT-mode status.

Refer to Section 12, System Control Procedures, in Chapter 6.

CHAPTER 4

NDA-24300

Page 280

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

2.3.5 PWR SW Card Replacement Procedure

The PWR SW (PH-PW14) card is located in Slot No. 00 or 01 within the TSWM. The card’s main

function is to supply DC -48V operating power to the same TSWM circuit cards and also DC +5, -5V,

and +12V output power to the MISC slots. Use the following procedures to replace the card with a new

one.

Replacement Procedure

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

On the PWR SW (PH-PW14) card, set the

SW key DOWN.

• P-ON lamp on the PWR SW card

goes OFF.

• ALM lamp on the PWR SW card is

red.

Extract the PWR SW card to be replaced

from the TSWM.

On the new PWR SW card, set the SW key DOWN.

Insert the new PWR SW card into the TSWM.

• P-ON lamp on the new card is OFF.

• ALM lamp on the PWR SW card is

red.

• P-ON lamp on the new card is

On the new PWR SW card, set the SW key UP.

steady-green.

• ALM lamp on the PWR SW goes

OFF.

END

NDA-24300

CHAPTER 4

Page 281

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

2.3.6 MISC Card Replacement Procedure

ATTENTION

Contents

START

Static Sensitive

Handling

Precautions Required

On the MISC card, set MB switch UP.

Extract the MISC card from its mounting slot.

• Keep MB switch UP.

Insert the new circuit card into the same

mounting slot.

On the MISC card, set MB switch DOWN.

END

CHAPTER 4

Page 282

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

3. PIM Accommodating Circuit Card Replacement Procedure

This section covers the procedures for replacing circuit cards mounted in the PIM (IMG0/1/2/3).

3.1 Precaution

•

Use this procedure to replace a faulty circuit card with a spare or to check a spare card.

There are functional switches (having set the default switch) on some of the circuit cards to be re-

placed. As for switch setting on the circuit cards, confirm the circuit card mounting face layout for the

PIM. When a circuit card with a default switch setting is replaced with a spare card, always make the

switch setting on the new circuit card the same as on the replaced card. Otherwise, electronic compo-

nents on the circuit card may be destroyed, or the circuit card itself may fail to function normally.

•

When handling a circuit card, always use the field service kit as countermeasures against static elec-

tricity. Touching a circuit card without using the field service kit may destroy the card due to static

electricity on the human body.

3.2 Circuit Card Mounting Face Layout

Figure 4-18 shows the face layout of the circuit cards mounted in the PIM.

Universal Slots

PIM

Slot No.

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

Note: This section also covers the procedure to replace the SDT (PA-SDTA/PA-SDTB) card. The card can

be mounted in any of the universal slots (Slots 04-12 or 15-23).

Figure 4-18 Circuit Card Mounting Face Layout of PIM

Improper key operations may result in a system down. Operate the keys with extreme care.

WARNING

During replacement of a circuit card, the system issues system messages and activates the

related alarm. Reset the indicated alarm after completing the replacement procedure.

If the indicated alarm is cleared via the RALM command, the system also clears the whole

contents of the system message. Before using the RALM command, print the messages using

the DFTD command.

Use the ALM RST button only to reset the alarm lamps.

NDA-24300

CHAPTER 4

Page 283

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

3.3 Operating Procedures

The following sections provide operating procedures to replace circuit cards mounted in the PIM. Perform

the operations corresponding to each Reference Item specified in Table 4-3. Note that the procedures as-

sume that the system adopts the dual configuration.

Table 4-3 PIM Circuit Cards and Reference Items

CIRCUIT CARD

REFERENCE ITEM

REMARKS

FUNCTION NAME

LC/TRK

Section 3.3.1, LC/TRK Circuit Card Replacement

Section 3.3.2, MUX Card Replacement Procedure

MUX

SDT

Section 3.3.3, SDT Card Replacement Procedure

Section 3.3.4, PWR Card Replacement Procedure

PWR

CHAPTER 4

Page 284

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

3.3.1 LC/TRK Circuit Card Replacement Procedure

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

On the circuit card to be replaced,

set the MB switch UP.

Extract the circuit card from its mounting slot.

Insert the new card into its mounting slot.

• Keep MB switch set at UP.

On the new card, set MB switch DOWN.

END

NDA-24300

CHAPTER 4

Page 285

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

3.3.2 MUX Card Replacement Procedure

The MUX (PH-PC36) card is mounted in Slot No. 13 and/or 14 of each Port Interface Module (PIM).

The card’s main function is to provide an interface between the CPR and Port Microprocessor (PM) of

the line/trunk circuit, and also to provide an interface for multiplexing/de-multiplexing of voice Pulse

Code Modulation (PCM) information and digital data information. Use the procedures below to re-

place the MUX card with a spare:

Note: Execute the system changeover of MUX by using the MBR key operation on the active GT (PH-GT09)

card or by using the CMOD command. Before starting this task, be sure to confirm the system block

diagram shown in Figure 4-16, or Section 12, System Control Procedures, in Chapter 6.

MUX Card Replacement Procedure

Apply extreme care when operating the keys on the circuit cards.

WARNING

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

System Changeover

On the active GT (PH-GT09) card, set the MBR key

UP. Then, return the key DOWN.

Check the following lamp indications

on the circuit cards to be affected and

ensure that they are all OFF:

• TSW ACT (TSW cards)

• OPE/MB (DLKC card) Note

• MUX ACT (MUX cards)

Note: If the MUX card to be

replaced represents system

status #0, all circuit cards

with #0 status are totally

affected. Check the cited

cards’ lamp indications.

Refer to Figure 4-16 and

Figure 4-17.

Check the mate GT block's ACT mode.

On the MUX (PH-PC36) card to

Check the following lamp indications

on the mate Speech Path Block and en-

sure that they are all steady-green:

be replaced, Set the MB switch UP.

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

• MUX ACT (MUX cards)

MUX/ACT lamp on the DLKC card is

red.

CHAPTER 4

NDA-24300

Page 286

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Disconnect the cable for the MUX front

connector on the card to be replaced.

Extract card to be replaced from the mounted PIM.

On the new card, set the MB key UP.

Insert the new card into the PIM.

• MUX ACT lamp on the new card is

red.

Connect the disconnected cable to the

MUX front connector on the new card.

NDA-24300

CHAPTER 4

Page 287

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Verify that the SYNC LED on the new card

lights green.

MBR (on the active GT card)

On the new MUX card, set the MB key DOWN.

System Changeover

Replaced MUX: STBY to ACT

Mate MUX: ACT to STBY

Flip the MBR key on the active GT card. Confirm the

new MUX card functions normally.

Check all the following lamp indica-

tions on the Speech Path block to

which the new MUX card belongs

and ensure that they are all steady-

green:

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

• MUX ACT (MUX cards)

Check the following lamp indications

on the mate Speech Path block and

ensure that they are all steady-green:

• TSW ACT (TSW cards)

• OPE/MB (DLKC card)

• MUX ACT (MUX cards)

END

Refer to Figure 4-16 and Figure 4-17.

Note: The changeover of Speech Path System can be performed also by using the CMOD command. For

details, refer to Chapter 8, Maintenance Commands.

CHAPTER 4

NDA-24300

Page 288

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

3.3.3 SDT Card Replacement Procedure

The SDT (PA-SDTA/PA-SDTB) card, mounted in a universal slot of a PIM, is used

to provide a 52M interface for the optical fiber lines. Use the following procedure

to replace the SDT card with a spare.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

While this card is being replaced, the connected optical fiber line cannot be used.

WARNING

Procedure to Replace Optical Fiber Cable

ATTENTION

Contents

START

Static Sensitive

Handling

Precautions Required

• ACT lamp onPA-SDTA card goes

OFF. (When card is provided in a dual

configuration, the card becomes

STBY.)

On the PA-SDTA card, turn ON Switch 4

of the P-SW key.

The following occurs in call processing:

When card is provided in dual

configuration

All calls (including already established

calls plus newly attempted calls) can

normally be handled by the mate card.

When card is in single configuration,

or mate card is faulty in dual configu-

ration

Though any call attempt is rejected, al-

ready established calls are not affected.

When any connection link exists, the

link is still maintained.

On the PA-SDTA card, set the MB key UP (=ON).

• OPE lamp on the PA-SDTA card is red.

The following occurs in call processing:

When card is in single configuration,

or mate card is faulty in dual

configuration

Already established calls (while in

speech) lose voice/tone. Any connec-

tion link is severed after a few seconds.

NDA-24300

CHAPTER 4

Page 289

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Remove the optical fiber cable from the front

connector on the PA-SDTA card.

Connect the new optical fiber cable to the front

connector on the PA-SDTA card.

On the PA-SDTA card, set the MB key DOWN

(=OFF) and turn OFF Switch 4 of the P-SW key.

• OPE lamp on the PA-SDTA card is

steady-green.

END

CHAPTER 4

Page 290

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

Procedure to Replace PA-SDTA/PA-SDTB card

ATTENTION

Contents

START

Static Sensitive

Handling

Precautions Required

• ACT lamp on the PA-SDTA card

On the PA-SDTA card, turn ON Switch 4

of the P-SW key.

goes OFF.

• Though any call attempt is rejected,

already established calls are safely

maintained. When any connection

link exists, the link is maintained.

Note: When the card is in a dual

configuration, perform this

for both system sides, in the

order of STBY → ACT.

By using the SPTS command, verify that no calls

are being handled by the SDT card.

• OPE lamp on the PA-SDTA card is

red.

On the PA-SDTA card, set the MB key UP (=ON).

• Whenalready established calls exist,

the connections lose voice/tone.

When any connection link exists, the

link is severed after a few seconds.

Note: When the card is in a dual

configuration, perform this

for both system sides (both

ACT and STBY sides).

NDA-24300

CHAPTER 4

Page 291

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

• OPE lamp on the PA-SDTB card is

On the PA-SDTB card, set the MB key UP (=ON).

red.

• When any connection link exists, the

nailed-downconnectionbetweenthe

FCH (PA-FCHA) and SDT (PA-

SDTB) cards is cut off. Already

established calls, while in speech,

are all disconnected.

Extract both PA-SDTA/PA-SDTB cards,

simultaneously.

Remove the flat cables from the front connectors, I/O

and PCM, on both PA-SDTB and PA-SDTA cards.

When replacing the PA-SDTB, also remove MT24

TSW cables from all the front connectors on the card.

• Confirm that the MB key on the new

card is set UP (=ON). If the new card

is PA-SDTA, also confirm that

Referring to the card removed, perform

the switch settings on the new card.

Switch 4 of the P-SW key is ON.

CHAPTER 4

Page 292

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

• OPE lamp on the new card is red.

Connect the disconnected flat cables to the connectors

on the new card and other PA-SDTA/PA-SDTB cards.

When the new card is PA-SDTB, also connect the MT

24 TSW cables to all the required front connectors.

Insert both PA-SDTA/PA-SDTB cards (including new

card) simultaneously into the same slots of the PIM.

Note 1: When the card is in a dual

configuration, perform this

action for both system sides

(both ACT and STBY sides).

On the PA-SDTA card, set the MB key DOWN (=OFF).

Note 1

Note 2: When the card is in a dual

configuration, perform this

action for both system sides,

in the order of STBY → ACT.

On the PA-SDTA card, turn OFF Switch 4 of the

P-SW key. Note 2

• OPE lamp on the new card is steady-

On the PA-SDTB card, set the MB key DOWN (=OFF).

green.

END

NDA-24300

CHAPTER 4

Page 293

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

3.3.4 PWR Card Replacement Procedure

The PWR (PA-PW55-A/PA-PW55-B) and DPWR (PA-PW54-A/PA-PW54-B)

cards are mounted respectively in Slot No. 1 and Slot No. 3 of each PIM. The card’s

main function is to provide operating power to the circuit cards accommodated in

the PIM. The procedures to replace the PWR/DPWR card are as follows:

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Replacement Procedure

• OPE lamp on the card goes OFF.

Turn ON the MB key on the PWR/DPWR card

to be replaced.

Turn OFF the -48V SW on the card to be replaced.

Disconnect the power cable from the -48V IN

connector.

Extract the card to be replaced.

Turn OFF the -48V SW on the new card.

Confirm the mate CPU's "ACT" mode

CHAPTER 4

NDA-24300

Page 294

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Turn ON the MB key on the new card.

• OPE lamp on the new card is OFF.

Insert the new card into the PIM.

Connect the power cable to the -48V IN

connector.

Extract the card to be replaced.

• OPE lamp on the new card is green.

Turn OFF the MB key on the card.

END

NDA-24300

CHAPTER 4

Page 295

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

4. Fan Unit Replacement

This section explains how to replace the Fan Unit (FANU), which is fastened on the TOPU or inside the ded-

icated fan box within the system. Because the fan is a vital device to protect the system from heated air, it is

recommended that the fan (a total of three per unit) be replaced at least every two years to guarantee its high

performance.

The mounting location of FANU differs, depending on the module configuration of each cabinet. When the

system consists of a total of three modules or less, the FANU is mounted on the TOPU of the cabinet. Other-

wise, the FANU is housed in the dedicated fan box in the center of the cabinet. Refer to Figure 4-19.

NEAX 2400 IMX

TOPU

NEC

FAN BOX

NEAX 2400 IMX

NEC

TOPU

FANU is

located here.

FRONT VIEW

/ / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / /

When FANU is mounted on TOPU

When FANU is mounted in FAN BOX

Figure 4-19 FANU Locations

Replacement Procedure: FANU on TOPU

When the FANU is mounted on the TOPU, perform the following replacement procedure:

STEP 1 Using a Phillips screwdriver, remove the four screws. Lift away the top cover.

STEP 2 Turn OFF the PWR SW on the PZ-M369. (Refer to Figure 4-20.)

STEP 3 Remove the fan fuse (5A) on the PZ-M369.

STEP 4 Remove the fan cables from the fan connector and the connector(s) corresponding to the fan to

be replaced (for example, when replacing FAN #0, disconnect the FC0 connector together with

the fan connector).

CHAPTER 4

NDA-24300

Page 296

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Top Cover

PBX

NEAX 2400 IMS

NEC

........

...................

........

.....

.........

..............

.........

...................

.....

........

FANU

.........

PZ-M369

. . .

NEAX 2400 IMX

NEC

Turn PWR SW OFF

Unscrew the top cover by using

a Phillips Screwdriver and

remove it from the TOPU.

OFF

PZ-M369

TALM0 TALM1

TH0

TH1

TH2

FAN

FC1 FCF0C2

FC1 FC2

FC0

OFF

Auto

Disconnect the cable(s) and

Disconnect the FAN cable

Remove this FAN fuse.

the connector(s) here used for

the FAN to be replaced.

from this power connector.

Figure 4-20 Preparation forFANU Replacement (Fans on TOPU)

STEP 5 Remove the four screws fastening the fan to be replaced. Refer to Figure 4-21.

Note: The removed screws are used in STEP 7 again. Do not dispose of them when unscrewing the fan here.

STEP 6 Remove the unscrewed fan from the FANU.

STEP 7 Fasten the new fan with the removed screws.

STEP 8 Connect the new fan cables to the fan connector and the connector(s) disconnected in STEP 4.

STEP 9 Fix the fan fuse (5A) onto the PZ-M369.

NDA-24300

CHAPTER 4

Page 297

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

STEP 10 Set the PWR SW on the PZ-M369 to the AUTO position.

Note: The switch setting of the PWR SW can be ON, depending on the location conditions of the system.

STEP 11 Attach the top cover again to the original location.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

PZ-M369

FANU

TOPU

PBX

(FAN)

Figure 4-21 How to Replace FANU (Fans on TOPU)

CHAPTER 4

Page 298

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

Replacement Procedure: FANU in Fan Box

When the FANU is mounted in the fan box, perform the following replacement:

STEP 1 Remove the front cover of the fan box. Then, extract the FANU.

STEP 2 Turn OFF the PWR SW on the PZ-M369. (Refer to Figure 4-22.)

STEP 3 Remove the fan fuse (5A) on the PZ-M369.

STEP 4 Remove the fan cables from the fan connector and the connector(s) corresponding to the fan to

be replaced (for example, when replacing FAN #1, disconnect the FC0 connector together with

the fan connector).

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

PBX

NEAX 2400 IMS

NEC

PZ-M369

FAN BOX

Remove the Front Cover

and pull out the FANU.

Front Cover

Turn PWR SW OFF

OFF

These dotted squares indicate the fans.

They reside in the back side of PZ-M369.

PZ-M369

TALM0 TALM1

TH0

TH1

TH2

FAN

FC1 FCF0C2

FC1 FC2

FC0

OFF

Auto

Disconnect the FAN cable(s) and

Remove this FAN fuse.

Disconnect the FAN cable

the connector(s) here used for the

FAN to be replaced.

from this connector.

Figure 4-22 Preparation for FANU Replacement (Fans in Fan Box)

NDA-24300

CHAPTER 4

Page 299

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

STEP 5 Take off the four screws fastening the fan to be replaced. (Refer to Figure 4-23.)

Note: The removed screws are used in STEP 7 again. Do not dispose of them when unscrewing theFAN here.

STEP 6 Remove the unscrewed fan from the FANU.

STEP 7 Fasten the new fan with the removed screws.

STEP 8 Connect the new fan cables to the fan connector and the connector(s) disconnected in STEP 4.

STEP 9 Fix the fan fuse (5A) again onto the PZ-M369.

STEP 10 Insert the FANU into the fan box and fasten it with the two screws.

STEP 11 Set the PWR SW on the PZ-M369 to the AUTO position.

Note: The switch setting of the PWR SW can be ON, depending on the location conditions of the system.

STEP 12 Attach the front cover to the original location.

PBX

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

FAN power cable

PZ-M369

(FAN)

FAN BOX

(FAN)

FAN power cable

FAN BOX

Figure 4-23 How to Replace FANU (Fans in Fan Box)

CHAPTER 4

Page 300

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

5. CPR Cooling Fan Replacement

This section explains how to replace a cooling fan in the back side of the CPR. This procedure is necessary

when a fault is detected in the cooling fan. Because the fan is a vital device to protect the CPR from heated air,

it is also recommended that the fan be replaced at least every two years, even if a fault is not detected.

STEP 1 Set the CPU, whose rack houses the fan to be replaced, in STBY mode via the MBR key on

the DSP (Refer to Figure 4-24.) Note

Note: For the ACT/STBY changeover of the CPU, see Chapter 6.

STEP 2 Disconnect the power alarm cable from the PALM connector on PZ-PW92.

STEP 3 Turn OFF the PWR SW on the PZ-PW92 (Refer to Figure 4-24 Face Layout of CPR.)

PZ-IO27

Section 1.3, Line Fault - When Dial

PZ-GT16 and PZ-GT13 (ISAGT)

HDD M B

CPUOPE WDT IMG0

M BR

FDD

IMG1 IMG2 IMG3

OFF

SYSTEM SELECT0

STATUS

OFF

SYSTEM SELECT1

SENSE

OUT PW R

OFF

PALM

SYSTEM SELECT2

CPURST

OFF

IN PW R

OFF

SLOT No.

PZ-PC19 (LANI)

PZ-PW92

Note: In place of PZ-IO27, the CPR may be equipped with PZ-IO28, which does not have the MB (Make-

busy) key.

Figure 4-24 CPR Face Layout

STEP 4 Disconnect the power and bus and ether cables from the relevant connectors.

•

Power cables from OUTPWR, INPWR connectors on PZ-PW92

Bus cables from the front connectors on PZ-GT13 and PZ-GT16

Ether (UTP CTG5 ST CA-n) cables from the front connectors on the PZ-PC19.

STEP 5 Remove the front bracket, and then take off the four screws fastened onto the CPU. (Refer to

Figure 4-25.)

STEP 6 Extract the CPR from the LPM. (Refer to Figure 4-25.)

NDA-24300

CHAPTER 4

Page 301

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

PBX

..........

LPM

SLOT

No.

..........

SLOT No.

CPR

Figure 4-25 Extraction of CPR from LPM

STEP 7 Disconnect the fan cable from the connector in the backbone of CPR.

Note: The cooling fan is located in the backbone of CPR and the cable connector lies in its right side. Refer

to Figure 4-26.

Connector for Cooling FAN Cable

CPR

Cooling FAN

PZ-M14

Figure 4-26 Rear View of CPR

STEP 8 Loosen the two screws fastening the box that contains the fan inside. Slightly lift the box and

remove it from the CPR. Refer to Figure 4-26 and Figure 4-27.

STEP 9 Take off the four screws and remove the cooling fan from the CPR. Refer to Figure 4-27.

STEP 10 Fasten the new cooling fan and CPR with screws. Then, connect the fan cable again to the con-

nector. Refer to Figure 4-26 and Figure 4-27.

CHAPTER 4

NDA-24300

Page 302

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

STEP 11 Insert the CPR back into the LPM.

STEP 12 Fasten the CPR and LPM with the four screws.

STEP 13 Connect the disconnected power, bus, and ether cables to the relevant connectors.

STEP 14 Turn ON the SW key on the PZ-PW92.

STEP 15 Connect the disconnected power alarm cable to the PALM connector on the PZ-PW92.

STEP 16 Analyze the indicated system message. The message displayed when the PWR SW on the PZ-

PW92 was turned OFF.

STEP 17 Clear the indicated ALM and confirm that the ALM lamp is not lit again, indicating that the

cooling fan is replaced securely.

REAR

FRONT

CPR

Figure 4-27 How to Remove the Cooling FAN

NDA-24300

CHAPTER 4

Page 303

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

6. Fuse Replacement

The system uses the fuses shown in Figure 4-28 as a protection against an overload resulting from a short cir-

cuit.

1.5A

25A

12.5V

Figure 4-28 Fuses Used by System

When excessive current is applied to a PWR circuit card, the related fuse is blown. The blown fuse after a fault

can be confirmed as shown in Figure 4-29.

If a fuse is blown,

this area turns white.

A normal fuse

A blown fuse

Figure 4-29 Blown Fault Example

The purpose of fuses is to let them blow before the components are damaged. If any fuse gets blown, replace

it immediately with a new one using the following procedure:

(1) Confirm the blown fuse via the system message [6-A] or MJ lamp on the top of IMG0.

(2) Replace the fuse with a new one, referring to Figure 4-30 and Figure 4-31.

(3) Determine the cause of the blown fault, referring to Figure 4-32 (case of RGU fuse) or Figure 4-33 (DC-

48V fuse.)

CHAPTER 4

NDA-24300

Page 304

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

Figure 4-30 shows the location of fuses within the system. In Chapter 4-30, the fuses are indicated by or

PA-PW54

PBX [Front View]

NEAX 2400 IMS

NEC

25A

5.0A

0.5A

25A

PZ-M369

5.0A

PA-PW55

25A

5.0A

0.5A

..........

5.0A

3.2A 5.0A

PZ-PW92

PZ-M377

Figure 4-30 Fuse Locations Within System

NDA-24300

CHAPTER 4

Page 305

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

In the TSWM, the fuse shown in Figure 4-31 is used for the PWR SW (PH-PW14) card, which is housed in

Slot No. 00 and/or 01.

PBX (IMG1)

PH-PW14

(PWR SW)

TSWM

FUSE: 15A

Front View

Figure 4-31 Fuse Location Within TSWM

CHAPTER 4

Page 306

Issue 1

NDA-24300

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

Perform the procedure in Figure 4-32 to confirm the cause of the RGU fuse blown fault.

Start

Visual check: No pin contacting

or backboard melting?

OPE Lamp (green) of

each LC card remains lit?

Yes

1. Turn ON (UP) the MB key

on the LC card.

2. Remove the card from the PIM.

3. Replace the fuse with a new one.

Replace the blown fuse with a new

one. The fuse is blown again?

Yes

The replaced fuse

is blown again?

Perform station-to-station

connections within the PIM.

Is any fuse blown?

Turn ON (UP) the MB

keys on all LC cards,

and remove them from the

PIM. (Only PWR cards are

inside the PIM)

Yes

Perform station-to-station

connections within the PIM.

Is any fuse blown?

Yes

Turn ON (UP) the MB

keys on the whole LC cards,

and remove them from the

PIM. (Only PWR cards are

inside the PIM)

Fault of LC card that accompanied

the fuse blowing.

Yes

Fault of LC card

that was removed

Replace the blown fuse

with a new one.

Fault in LC card that accompanied

the fuse blowing.

Probable Cause: Not confirmed.

Needs further observation of the fault

The replaced fuse is

blown again?

Replace the blown fuse

with a new one.

Yes

The replaced fuse

is blown again?

Yes

Insert the removed cards

one by one (into the PIM).

Is any fuse blown?

Replace the PWR card

Yes

Fuse is still blown?

Yes

Fault in LC card that accompanied

the fuse blowing.

Fault of PWR card.

Perform system initialization

after inserting all removed cards.

There is a short circuit

on the backboard of the PIM.

Figure 4-32 RGU Fuse Blown Fault Flowchart

NDA-24300

CHAPTER 4

Page 307

Issue 1

UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

Perform the procedure in Figure 4-33 to confirm the cause of the DC-48V fuse blown fault.

Start

Visual check: No pin contacting

or backboard melting?

OPE Lamps (green) of

LC/TRK/NCU cards remain lit?

Yes

1. Turn ON (UP) the MB key

on the circuit card.

2. Remove the card from the PIM.

3. Replace the fuse with a new one.

The replaced fuse

is blown again?

Yes

LPM / TSWM / PIM

Make sure in which module

the fuse has blown

Fault of circuit card

that was removed

Turn ON (UP) the MB

keys on the whole circuit

cards, and remove them from

the PIM. (Only PWR cards

are inside the PIM)

Turn ON (UP) the MB

keys on the whole circuit

cards, and remove them from

the PIM. (Only PWR cards

are inside the PIM)

Replace the blown fuse

with a new one.

Replace the blown fuse

with a new one.

Insert the removed cards

one by one (into the PIM).

Is there any fuse blowing?

The replaced fuse

is blown again?

Yes

Insert the removed cards

one by one (into the PIM).

Is any fuse blown?

Perform system initialization

after inserting all removed cards.

Fault of circuit card that

accompanied the fuse blown.

Replace the PWR card

Yes

The fuse is still blown?

Yes

Fault of circuit card that

accompanied the fuse blown.

Fault of PWR card.

Perform system initialization

after inserting all removed cards.

There is a short circuit on the

backboard of the PIM.

Figure 4-33 DC -48V Fuse Blown Fault Flowchart

NDA-24300

CHAPTER 4

Page 308

Issue 1

CHAPTER 5

FAULT REPAIR PROCEDURES

This chapter provides information on how to repair the fault(s) within the system. If any of the components or

equipment listed in Table 5-1 has a failure, move on to the repair procedure explained for each faulty condition.

Table 5-1 Fault Repair Procedure Quick Reference

FAULTY ITEM

Line Fault

FAULTY SITUATION

DP/PB Telephone Dial tone is not heard.

REFERENCE SECTION

T o ne (DT) Cannot Be Heard

Dialing results in a wrong

connection.

Section 1.4, Line Fault - When

Dialing Results in Wrong

Connection

Bell does not ring.

Section 1.5, Line Fault - When Bell

Does Not Ring

Answer/speech cannot be

made.

Section 1.6, When Call Cannot Be

Answered and Speech Cannot Be

Made

D^term

• D^termcannot be operated. Section 1.7, D^termFault

• Operations are abnormal.

Trunk Fault

• No connections can be set up.

Section 2.3, Trunk (ORT, SND,

CFT) Fault and Section 2.4, Trunk

(COT, TLT, DTI) Fault

• PB/DP signals are erroneously received or set out

from ORT/SND.

• No three-way calling can be made on CFT, or noise

gets in a established connection.

• A connection results in no speech.

• Noise gets in a established connection.

ATTCON/DESKCON

Unit Fault

• No speech can be made.

Section 3.3, A T TCON/DESKCON

Fault

• No control operations can be made.

Faults related to speech.

Section 4.2, Unit Fault - Fault

Related to Speech

Dial tone is not heard.

Section 4.3, Unit Fault - When Dial

T o ne (DT) Cannot Be Heard

The ACT MUX card side has become faulty and system Section 4.4, Unit Fault - ACT-Side

changeover has been executed.

MUX Card Is Faulty and System

Has Changed Over

NDA-24300

CHAPTER 5

Page 309

Issue 1

FAULT REPAIR PROCEDURES

Table 5-1 Fault Repair Procedure Quick Reference (Continued)

FAULTY ITEM

FAULTY SITUATION

Faults related to speech.

REFERENCE SECTION

Speech System Fault

Section 5.2, Speech Path System

Fault - Fault Related to Speech

Dial tone is not heard.

STBY side is faulty.

Section 5.3, Speech Path System

Fault - When Dial T o ne (DT)

Cannot Be Heard

Section 5.4, Speech Path System

Fault - STBY Side Has Become

Faulty

Control System Fault

Alarm Indication Fault

Power Supply Fault

Fault occurs occasionally at the ACT side.

STBY side is faulty.

Section 6.2, Control System Fault -

Fault Occurs Intermittently

Section 6.3, Control System Fault -

STBY Side Is Faulty

No fault indication is made on the Alarm Indicator

Panel.

Section 7.2, Fault of Alarm

Indicating Panel

Fault is not detected.

Section 7.3, Fault That Cannot Be

Detected

Fuse for RGU/-48V has blown.

Section 8.2, Fuse Blown Fault

The circuit breaker of PWR supply is off.

Section 8.3, Circuit Breaker OFF

Fault in PWR Supply

Alarm lamp on the PWR supply is lit.

Section 8.4, Fault of Alarm Lamps

on PWR Supply

Fan Unit Fault

• Fan are not activated even if the temperature has risen Section 9.2, Fan Unit Fault

higher than a predetermined degree.

• Fans are not activated even if the FAN START switch

is set to AUTO position.

Tone Fault

Tone is distorted.

Section 10.2, T o ne Fault

System Down Fault

Cause for the fault cannot be identified.

Section 11.1, When Cause for Fault

Cannot Be Identified

The faulty circuit card can be detected.

Section 11.2, When Faulty Circuit

Cards Can Be Assumed From

System Message

CCIS Line Fault

• A Specific CCH/CCT card is faulty. When the signal Section 12.3, Specific CCH/CCT

transmission line is a digital line, transmission/re-

ceiving of control signals cannot be performed.

Card Is Faulty and

Section 12.4, Fault of CCH, DTI

and Related Flat Cable

• When the signal transmission line is an analog line,

transmission/receiving of control signals cannot be

performed.

CHAPTER 5

Page 310

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

Table 5-1 Fault Repair Procedure Quick Reference (Continued)

FAULTY ITEM

ISDN Line Fault

FAULTY SITUATION

REFERENCE SECTION

• A specific DCH/PRT card is faulty.

Section 13.3, Specific DCH/PRT

Card Is Faulty and

Section 13.4, Fault of DCH, DTI,

and Related Flat Cable

• When the signal transmission line is a digital line,

transmission/receiving of control signals cannot be

performed.

Hard Time Clock Fault

EMA card is faulty.

Section 14, Hard Time Clock Fault

1. LINE FAULT

This section explains the fault repair procedure in a case where only one specific station line is in any of the

faulty conditions listed in Table 5-2.

Table 5-2 Line Fault Situation

FAULTY SITUATION

When Dial Tone cannot be heard

REFERENCE SECTION

Section 1.3, Line Fault - When Dial T o ne (DT) Cannot Be Heard

When dialing results in a wrong connection

Section 1.4, Line Fault - When Dialing Results in Wrong

Connection

When the bell does not ring

Section 1.5, Line Fault - When Bell Does Not Ring

When call cannot be answered and speech cannot be

made

Section 1.6, When Call Cannot Be Answered and Speech

Cannot Be Made

D^termFault

Section 1.7, D^termFault

NDA-24300

CHAPTER 5

Page 311

Issue 1

FAULT REPAIR PROCEDURES

1.1 Check Point

When repairing a line fault, consider the following items:

(1) Check alarm lamps on line circuit cards.

(2) When an outgoing call cannot be originated to a specific line/trunk or when an incoming call cannot be

terminated from a specific line/trunk, check Tenant Restriction Data (assigned via ATNR command) and

Route Restriction Data (assigned via ARSC command).

1.2 Line Control

Each line in a specific Line circuit (LC/ELC) card is controlled by the PM in that line circuit card. The

line circuit cards are controlled from the CPU via the MUX. Figure 5-1 shows the control route of line

circuit cards.

MDF

LC/ELC

LT Cable

Control Signal

Speech Path

MUX

LT Cable

Ordinary Telephone/

term

LC/ELC

LT Cable

Control Signal

Speech Path

Ordinary Telephone/

TDSW/INT

TSW

term

Control Signal

Symbols:

: Circuit Card

: Control Signal

: Speech Path

ISAGT

CPU

TSW: PH-SW12

MUX: PH-PC36

GT: PH-GT09

ISAGT: PZ-GT13

CPR

Figure 5-1 Controlling LC/ELC Circuit Cards and Speech Path

CHAPTER 5

Page 312

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

1.3 Line Fault - When Dial Tone (DT) Cannot Be Heard

Note: If a circuit card is replaced because only one line is

faulty, no other lines in that circuit card can be used

until the replacement is complete.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

When OPE lamp on the LC circuit card

does not illuminate

Confirm MB switch of the LC circuit card is in

ON position (UP).

Use ASDT command to confirm that station

data in the LC circuit card is assigned.

Replace the LC circuit card with a spare.

When BL lamp for each line is flashing or

illuminating on the LC circuit card

Confirm MB switch of the LC circuit card is in

ON position (UP side).

Use MBST command to confirm LC circuit

card has not been placed into make-busy state.

Use ASDT command to check the station data

assignment.

Replace the LC circuit card with a spare.

NDA-24300

CHAPTER 5

Page 313

Issue 1

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Check the faulty line on the MDF.

Isolate the faulty line to the in-house wiring

side and to the system side.

Connect the test telephone to the system side

and check to see if dial tone can be heard.

When Dial Tone (DT) is heard

Check the in-house wirings.

Replace the station telephone set with a spare.

When no DT or side tone is

heard

Check LT cables.

Replace the LC circuit card with a spare.

When DT is not heard, but side

tone can be heard.

Replace the LC circuit card with a spare.

END

CHAPTER 5

Page 314

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

1.4 Line Fault - When Dialing Results in Wrong Connection

Note: If a circuit card is replaced because only one line is

faulty, no other lines in that circuit card can be used

until the replacement is complete.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

When a call addressed to a specific station

has terminated to another station

Check to see if Call Forwarding-All Calls data

has been deleted.

Check the faulty line on the MDF.

On the MDF, isolate the faulty line to the in-

house wiring side and to the system side.

Connect the test telephone to the system side.

Repeat station-to-station connections and

check to see if the connection is established

normally.

When the dialed station is called

The station telephone set is faulty. Replace the

station telephone set with a spare.

When a wrong connection

occurs

Replace the LC circuit card with a spare.

END

NDA-24300

CHAPTER 5

Page 315

Issue 1

FAULT REPAIR PROCEDURES

1.5 Line Fault - When Bell Does Not Ring

Note: If a circuit card is replaced because only one line is

faulty, no other lines in that circuit card can be used

until the replacement is complete.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

Call the faulty station line by Station-to-

Station calling and check to see if the bell

of the telephone rings.

Replace the telephone set and check to see if

its bell rings.

Check the faulty line on the MDF.

Isolate the faulty line to the in-house wiring

side and to the system side.

Connect the test telephone to the system side.

Call the faulty line by station-to-station

calling and check to see if the bell rings.

When the bell does not ring

Replace the LC circuit card with a spare.

When the bell rings

The in-house wiring side is faulty. Confirm

that the A wire is not short-circuiting with

ground.

END

CHAPTER 5

Page 316

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

1.6 When Call Cannot Be Answered and Speech Cannot Be Made

Note: If a circuit card is replaced because only one line is

faulty, no other lines in that circuit card can be used

until the replacement is complete.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

Check the faulty line on the MDF.

Isolate the faulty line to the in-house wiring

side and to the system side.

Connect the test telephone to the system side.

Call the faulty line by station-to-station

calling.

When speech can be made

Replace the telephone set with a spare.

Replace the LC circuit card with a spare.

When speech cannot be made

END

NDA-24300

CHAPTER 5

Page 317

Issue 1

FAULT REPAIR PROCEDURES

term

1.7 D

Fault

Note 1: If a circuit card is replaced because only one line

is faulty, no other lines in that circuit card can be

used until the replacement is complete.

ATTENTION

Note 2: If any of the in-house cable wirings short-circuit,

the POW ALM lamp on the ELC circuit card

lights. Remove the cause of the short-circuit and

initialize the ELC circuit card.

Contents

Static Sensitive

Handling

Precautions Required

START

When OPE lamp on the ELC circuit card

does not illuminate

Confirm that MB switch of the ELC circuit

card is in ON position (UP).

Confirm that station data (ASDT command)

in the ELC circuit card is assigned.

Replace ELC circuit card with a spare.

When BL lamp for each line is flashing or

illuminating on the ELC circuit card

Confirm that MB switch of the ELC circuit

card is in ON position (UP).

Use MBST command to confirm that ELC

circuit card has not been placed into make-

busy state.

Check the station data (ASDT command)

assignment.

Replace the ELC circuit card with a spare.

CHAPTER 5

Page 318

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Check the faulty line on the MDF.

Isolate the faulty line to the in-house wiring

side and to the system side.

term

Connect the test D

to the system side.

Confirm speech by Station-to-Station calling.

When no speech can be made.

When speech can be made.

Check LT cables.

Replace ELC circuit card with a spare.

Check to see if the modular plug is firmly

connected with the D

term

Check the wiring inside the rosette.

Check the in-house wiring for any

abnormality.

term

Replace the D

with a spare.

END

NDA-24300

CHAPTER 5

Page 319

Issue 1

FAULT REPAIR PROCEDURES

2. TRUNK FAULT

This paragraph explains the fault repair procedure when a fault, shown in Table 5-3, has occurred to a specific

trunk.

Table 5-3 Trunk Fault Situation

TRUNK

FAULTY SITUATION

No connection can be set up.

REFERENCE SECTION

ORT

Section 2.3, Trunk (ORT, SND,

CFT) Fault

PB/DP signals are erroneously received or cannot be received.

SND

CFT

No connections can be set up.

PB/DP signals are erroneously sent out or cannot be sent out.

No connections can be set up.

No three-way calling can be made.

Noise gets in an established connection.

COT

TLT

DTI

No connections can be set up.

A connection results in no speech.

Noise gets in an established connection.

Section 2.4, Trunk (COT, T L T, D TI)

Fault

2.1 Check Point

When repairing a trunk fault, consider the following items:

(1) Check alarm lamps on trunk circuit cards.

(2) When an outgoing call cannot be originated to a specific trunk or when an incoming call cannot be termi-

nated from a specific trunk, check Tenant Restriction Data (assigned via ATNR command) and Route Re-

striction Data (assigned via ARSC command).

(3) Three-Way Conference Trunk (CFT) is on the MUX (PH-PC36) circuit cards. If a three-way conference

call cannot be established, check the MUX cards.

(4) If the present timing for supervising the trunk/sender status is considered to be responsible for the fault,

change the timing. The specifications for timings that can be changed with respect to trunks and senders

are shown in Table 5-4 and Table 5-5.

CHAPTER 5

NDA-24300

Page 320

Issue 1

FAULT REPAIR PROCEDURES

TIMING SPECIFICATIONS

Table 5-4 Timings for Trunks

ITEMS FOR STATUS

SUPERVISION

CONDITIONS FOR SUPERVISION

Detection of Call

Termination

• Ring Down System

Ringing signal of more than 4 cycles

is detected within 800 ms.

Detection by ringing signal (20Hz) from

the opposite office.

Detection within 16 ms after call

termination.

• Loop System

Detection by loop from the opposite office.

• E&M System

Detection by incoming signal (ground or –

48V) on E (RG2) lead.

Acknowledge Signal

Sending

• Wink Signal

160 ms (standard)

Timing can be assigned using ARTD

command.

• Delay Start

Detection of Release at the • E&M System

288 ms (standard)

time of Incoming

Connection

• Loop System

160 ms (standard)

Timing can be assigned using ARTD

command.

Timing for Restricting Call After release of the user’s trunk or the trunk at 3070 ms (standard)

Origination after Release

the opposite office has been detected, a new

call origination is restricted.

Timing can be assigned using ARTD

command.

Seizure of Opposite Office • Loop System

Closure of DC loop.

• E&M System

Supply of outgoing call signal (ground or –

48V) onto M (DL) lead.

Detection of Acknowledge • Wink Signal

Timing is assigned using ARTD

command.

Signal

• Delay Start

Trunk Hold Time

Even if answer signal has not reached from the • If DP Signal is 10 sec. (standard)

opposite office, the call is regarded as

answered.

after dial pulses are sent out

Timing can be assigned using

ARTD command.

• If PB Signal is 30 sec. (standard)

after seizure of the trunk

Timing can be assigned using

ASYD SYS 1 Index 156 (only

when 2nd Dial Tone System).

Detection of Release at the • Loop System

608 ms (standard)

time of Outgoing

Connection

Detection of polarity reversal across tip and Timing can be assigned using ARTD

ring.

command.

• E&M System

Detection of Release Signal (ground or –

48V) on E lead.

NDA-24300

CHAPTER 5

Page 321

Issue 1

FAULT REPAIR PROCEDURES

Table 5-5 Timings for Senders

CONDITIONS FOR SUPERVISION

ITEMS FOR STATUS

SUPERVISION

TIMING SPECIFICATIONS

Sender Acknowledge Wait Timing limit for waiting to receive connection 4 sec. (standard)

Timer

acknowledgement signal from the opposite

office after seizing the opposite office.

Timing can be assigned using ASYD

SYS 1 Index 130 command.

Sender Prepause Timer

Time from sender seizure till sending of the

DP: 3 sec. (standard)

1st digit where connection acknowledgment is PB: 2.5 sec. (standard)

made by interface with the opposite office.

Timing can be assigned using ASYD

SYS 1 Index 131 command.

Sender Inter-digit Timer

Inter-digit timing for the numbers to be sent

out by the sender.

• For DP

10 pps: 860 ms (standard)

20 pps: 460 ms (standard)

Timing can be assigned using

ASYD SYS 1 Index. 132 com-

mand.

• For PB

60 ms/120 ms (to be selected by

ONSG of ARTD command.)

Timing can be changed using

ASYD SYS 1 Index 133 com-

mand.

CHAPTER 5

Page 322

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

2.2 Trunk Control

Trunk circuit cards are controlled from the CPU via the MUX. Each trunk line in a specific trunk circuit

card is controlled by the Port Microprocessor (PM) in a trunk circuit card. Figure 5-2 shows the control

route of the trunk circuit card.

ORT/SND

Control Signal

Speech Path

TRK

MUX

MDF

COT/TLT

LT Cable

Control Signal

Speech Path

TRK

Note

CFT

COT/TLT

Network

LT Cable

TRK

Control Signal

Speech Path

MUX

ORT/SND

TRK

Control Signal

Speech Path

Note

CFT

TRK

TDSW/INT

TSW

Symbols:

Control Signal

: Circuit Card

: Control Signal

: Speech Path

TSW: PH-SW12

MUX: PH-PC36

GT: PH-GT09

ISAGT: PZ-GT13

ISAGT

CPU

Note: Eight CFTs are provided on the MUX (PH-PC36) cards.

CPR

Figure 5-2 Controlling Trunk Circuit Cards and Speech Path

NDA-24300

CHAPTER 5

Page 323

Issue 1

FAULT REPAIR PROCEDURES

2.3 Trunk (ORT, SND, CFT) Fault

Note: If a circuit card is replaced because only one line is faulty, no

other lines in that circuit card can be used until the replace-

ment is complete.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

When only one line is faulty

Place the faulty line into make-busy state.

For ORT/SND, set MB switch of

each circuit to ON position.

For CFT, place it into make-busy

state using command MBTK.

Replace the circuit card with spare.

Set MB switch UP and extract the circuit card

from its mounting slot.

Set MB switch of the new circuit card UP and

insert the circuit card into its mounting slot.

Set MB switch DOWN.

If the line is under make-busy state, cancel it.

END

CHAPTER 5

Page 324

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

2.4 Trunk (COT, TLT, DTI) Fault

Note 1: If a circuit card is replaced because only one line

is faulty, any other lines in that circuit card cannot

be used until the replacement is complete.

ATTENTION

Contents

Note 2: If the polarities of the external line is reversed, it

Static Sensitive

is detected in the form of Trunk Ineffective Hold.

Handling

Precautions Required

START

When OPE lamp on the trunk circuit card

does not illuminate

Confirm that MB switch of the trunk circuit

card is in ON position (UP side).

Confirm that trunk data (ATRK command) in

the trunk circuit card is assigned.

Replace trunk circuit card with a spare.

When BL lamp is flashing or illuminating

on the trunk circuit card

Confirm that MB switch of trunk circuit card

is in ON position (UP side).

Use MBTK command to confirm that trunk

circuit card has not been placed into make-

busy state.

Check trunk data (ATRK command)

assignment.

Replace trunk circuit card with a spare.

NDA-24300

CHAPTER 5

Page 325

Issue 1

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Check the faulty line on the MDF.

If the C.O./Tie Line is in Loop Start system:

Isolate the faulty line to C.O. side and

to the system side.

Connect the test telephone to the C.O.

side.

Note 1: Check can be made

only on temporarily

opened C.O./Tie Lines.

Confirm that Dial Tone (DT) is heard

and the call is connected to the desti-

nation party at the opposite office.

Note 2: Cross

connection

If C.O./Tie Line is any other type than Loop

Start:

methods are explained on

the following pages.

By cross connections on the MDF,

connect the faulty line to a normal

trunk.

By a designated connection from the

ATTCON/DESKCON, seize the

trunk connected with the faulty line

(*E).

When the connection is not set up,

the C.O./Tie Line is faulty

After the trunk has been seized, check

to see if a call can be originated.

term

When the connection is set up

Replace the D

with a spare.

END

CHAPTER 5

Page 326

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

Note: When performing loop-back connection tests on the trunks at the user’s office,

provide cross connection as follows:

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

(1) For a COT

COT

•

Set up a loop-back connection between the COT (C.O. Trunk) to be tested and station line.

The trunk route must be assigned for Loop Start.

(2) For a TLT (for DID)

TLT

•

Set up a loop-back connection between the Tie Line Trunk (TLT) to be tested and another TLT.

If the TLT is a Direct Inward Dialing (DID) Trunk, connect the related leads as shown below:

TLT

•

If the TLT is a 4-wire E & M System, connect the related leads as shown below:

Receive

Send

Receive

Send

TLT

NDA-24300

CHAPTER 5

Page 327

Issue 1

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

•

If the TLT is a 2W E & M System, connect the related leads as shown below:

TLT

(3) For a DTI

DTI

•

Set up a loop-back connection between the DTI Trunk to be tested and another DTI Trunk as shown

below:

Receive

DTI

Send

•

If the office is the PLO-source office, perform the tests by disconnecting the PLO and M-OSC. The

mode of the PLO becomes Self Operation Mode.

When the loop-back test is performed at the time of PCM LOSS, FRM LOSS, or MERM LOSS alarm

lamp (red) illuminates. If the alarm lamp goes out, the DTI circuit card side is normal.

When only one DTI circuit card is to be checked, make the following connections and confirm that

no alarm lamps illuminates.

Loop-back

Cross Connection

Receive

DTI

Send

CHAPTER 5

Page 328

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

3. ATTCON/DESKCON FAULT

This section explains the fault repair procedure when a specific Attendant Console (ATTCON) is in any of the

following faulty conditions.

•

No speech can be made.

No operations can be made.

3.1 Check Point

When repairing an ATTCON/DESKCON fault, consider the following items:

(1) Check the cable connections on the backplane.

(2) When replacing the ATI circuit card for master ATTCON/DESKCON, the system is placed under Night

Mode during replacement procedure.

(3) When replacing the master ATTCON/DESKCON, the system is placed under Night Mode during replace-

ment procedure.

3.2 ATTCON/DESKCON Control

Each ATTCON/DESKCON is controlled from an ATI (PA-CS33) circuit card. The ATI circuit card is con-

trolled from the CPU card via the INT on the TSW card. Figure 5-3 shows the control route of the ATI

circuit card.

The ATI (PA-CS33) circuit card is used as an interface card between the PBX and ATTCON/DESKCON.

The card is mounted in Slots 12 or 23.

NDA-24300

CHAPTER 5

Page 329

Issue 1

FAULT REPAIR PROCEDURES

PIM Backplane

LT11 is used when PA-CS33 is mounted in Slot 23.

LT5 is used when PA-CS33 is mounted in Slot 12.

LT11

LT5

PA-CS33 Pin Assignment

BN4800

BN4801

for

ATTCON/

DESKCON #0

BN4820

BN4821

TAS1B

BN4810

TAS0B

BN4830

TAS1A

BN4811

TAS0A

BN4831

for

ATTCON/

DESKCON

Installation Cable

MDF

ATTCON/

DESKCON #1

for

#0 - #1

Rosette

ATTCON/

DESKCON #0

Installation Cable

for

ATTCON/

DESKCON #1

#0 - #1

Figure 5-3 ATT Connector Cabling and Connector Leads Accommodation

CHAPTER 5

Page 330

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

3.3 ATTCON/DESKCON Fault

Note 1: No speech can be made.

Note 2: While replacement of the ATI circuit card

for the master ATTCON/DESKCON is in

progress, the system is placed under Night

Mode.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

On the ATTCON/DESKCON, LCHK

(Lamp Check) key has been pressed but

no lamps have illuminated.

Check the ATT connector cable between the

ATTCON/DESKCON and the PBX.

When the OPE lamp of the ATI (PA-

CS33) circuit card does not illuminate

Confirm that MB switch of the ATI circuit

card is in ON position (UP side).

Confirm that trunk data (ATRK command) in

the ATI circuit card are assigned.

Replace the ATI circuit card with a spare.

When the BL lamp of the ATI circuit card

is flashing or illuminating

Confirm that MB switch of the ATI circuit

card is in ON position (UP side).

Use MBTK command to confirm ATI circuit

card is placed into make-busy state.

Check assignment of ATI data (ATRK

command.)

Replace the ATI circuit card with a spare.

When keys cannot be operated

Replace the operator’s headset.

Replace the ATI circuit card with a spare.

END

NDA-24300

CHAPTER 5

Page 331

Issue 1

FAULT REPAIR PROCEDURES

Note: No operations can be made.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

Replace the ATTCON/DESKCON with a

spare.

Set the MB switch of ATI PA-CS33 circuit

card UP.

If the circuit card is equipped with a fuse,

remove the fuse.

Disconnect the CHAMP connector of the

ATTCON/DESKCON and replace the

ATTCON/DESKCON.

If the circuit card is equipped with a fuse,

insert the fuse into its position.

Set the MB switch of the ATI circuit card

DOWN.

Confirm the PA lamp illuminates on the

ATTCON/DESKCON.

END

CHAPTER 5

Page 332

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

4. UNIT FAULT

This section explains the fault repair procedure in a case where any of the faults shown in T a ble 5-6 has oc-

curred to all the line/trunk circuit cards mounted in a specific unit. Figure 5-4 shows the range of units.

Table 5-6 Unit Fault Situation

FAULT SITUATION

Noise, one-way speech, no tone.

REFERENCE SECTION

Section 4.2, Unit Fault - Fault Related to Speech

Even if dialing has been made, dial tone does not stop.

Dial Tone cannot be heard.

Section 4.3, Unit Fault - When Dial Tone (DT)

Cannot Be Heard

MUX card has become faulty and, as a result the CPU has changed Section 4.4, Unit Fault - AC T -Side MUX Card Is

over. Faulty and System Has Changed Over

IMG0

TOPU

IMG1

TOPU

IMG2

TOPU

IMG3

TOPU

PIM3

Unit 2

Unit 0

Unit 3

Unit 1

Unit 2

Unit 0

Unit 3

Unit 1

Unit 2

MG07

Unit 0

Unit 3

Unit 1

Unit 2

MG03

Unit 0

Unit 3

Unit 1

MG01

FANU

MG00

MG05

FANU

MG04

PIM2

FANU

PIM1

PIM0

Unit 2

Unit 0

Unit 3

Unit 1

Unit 2

MG02

Unit 0

Unit 3

Unit 1

Unit 2

Unit 0

Unit 3

Unit 1

Unit 2

MG06

Unit 0

Unit 3

Unit 1

LPM

TSWM

DUMMY

BASEU

DUMMY

BASEU

FRONT VIEW

Unit No. = 0/2

Unit No. = 1/3

Slot No. 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

PIM

Figure 5-4 Range of Units

NDA-24300

CHAPTER 5

Page 333

Issue 1

FAULT REPAIR PROCEDURES

4.1 Check Point

When repairing a unit fault, consider the following items:

(1) Speech paths and control paths in the unit are connected to line/trunks via the MUX circuit cards. Be sure

to check the alarm lamps on the MUX circuit cards, and check to see if the front cable between each MUX

circuit card and TSW circuit card is connected correctly. Figure 5-5 and Figure 5-6 show the block dia-

gram within the unit.

(2) The MUX circuit cards are operating in the ACT/STBY modes under control of the CPU circuit. When

the ACT-side CPU has detected a fault in the ACT-side MUX circuit card, CPU changeover is executed

and the ACT/STBY mode of the Speech Path System is also changed over. When both of the MUX circuit

cards have become faulty, all the lines/trunks in that unit are placed into make-busy state. (If a PFT circuit

card is located in that specific unit, the PFT is activated.) Figure 5-7 shows the location of the MUX cards.

(3) When both units in a specific PIM are faulty, it is possible that the PWR circuit card mounted in that spe-

cific PIM is faulty. In such a case, refer to Section 8, Power Supply Fault.

MUX0

MUX1

Clock

(B)

Clock

(B)

TSW/INT

Speech

Path

Speech

Path

(A)

Control of

CPU No. 0

Control of

CPU No. 1

ACT/STBY of

CPU No. 0

ACT/STBY of

CPU No. 1

LC/TRK

Line/

Trunk

Circuit Card

SYMBOLS

: Circuit Card

(A)

(B)

: Control on ACT/STBY of Speech Path Systems

: Control on ACT/STBY of Clock Systems

Figure 5-5 Unit Control Block Diagram (Dual Configuration)

CHAPTER 5

Page 334

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

MUX X

Clock

TSW/INT

Speech

Path

(A)

Control of

CPU

Line/

LC/TRK

Trunk

Circuit Card

LC/TRK

Figure 5-6 Unit Control Block Diagram (Single Configuration)

IMG0/1/2/3

13 14

PIM 3

PIM 2

PIM 1

PIM 0

UNIT = 2

UNIT = 0

UNIT = 2

UNIT = 0

UNIT = 3

UNIT = 1

UNIT = 3

UNIT = 1

MUX (PH-PC36) card is mounted

in Slot No. 13 and/or 14 of each

PIM.

13 14

Front View

Figure 5-7 MUX Card Locations

NDA-24300

CHAPTER 5

Page 335

Issue 1

FAULT REPAIR PROCEDURES

4.2 Unit Fault - Fault Related to Speech

Faulty Situation:

•

Noise, one-way speech, no tone, etc. occurs only within a unit.

Even if dialing has started, dial tone does not stop.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

(1) For Dual Configuration

START

Replace the MUX circuit card referring to

Procedure, in Chapter 4.

Check by replacing the MUX (PH-PC36)

circuit card.

Place the MUX circuit card into ACT mode

by flipping the MBR key on the active GT

(PH-GT09) card. Refer to Section 12.1.6,

System, in Chapter 6.

After replacement of the MUX

circuit card, make a station-to-

station call in the faulty unit and

see if speech is normal.

Check by replacing the TSW circuit card.

Replace the TSW circuit card by referring to

Procedure, in Chapter 4.

After replacement of the TSW

circuit card, make a station-to-

station call in the faulty unit and

see if speech is normal.

Place the TSW circuit card into ACT mode

by flipping the MBR key on the active GT

(PH-GT09) card. Refer to Section 12.1.6,

System, in Chapter 6.

CHAPTER 5

Page 336

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Check the line/trunk circuit cards mounted

in the unit to see if they are faulty.

Set the MB switch of the line/trunk circuit card

UP and extract it from its mounting slot.

Make a station-to-station call and see if a fault

occurs.

Perform this check on an individual basis.

If the fault has stopped occurring,

the circuit card extracted at that

time is faulty. Replace the circuit

card with a spare.

If the fault continues, check the

next circuit card.

END

NDA-24300

CHAPTER 5

Page 337

Issue 1

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

(2) For Single Configuration

START

Check by replacing the MUX (PH-PC36)

circuit card.

Replace the MUX circuit card by referring to

Procedure, in Chapter 4.

After replacement of the MUX

Press the RESET button on the EMA card

(*D).

circuit card, make a station-to-

station call in the faulty unit and

see if speech is normal.

Check by replacing the TSW circuit card.

Replace the TSW circuit card referring to

Procedure, in Chapter 4.

Press the RESET button on the EMA card

(*D).

After replacement of the TSW

circuit card, make a station-to-

station call in the faulty unit and

see if speech is normal.

CHAPTER 5

Page 338

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Check the line/trunk circuit cards mounted

in the unit to see if they are faulty.

Set the MB switch of the line/trunk circuit

card UP and extract it from its mounting slot.

Make a station-to-station call and see if a fault

occurs.

Perform this check on an individual basis.

If the fault has stopped, the

circuit card extracted at that time

is faulty. Replace the circuit card

with a spare.

If the fault continues, check the

next circuit card.

END

NDA-24300

CHAPTER 5

Page 339

Issue 1

FAULT REPAIR PROCEDURES

4.3 Unit Fault - When DialTone (DT) Cannot Be Heard

Faulty Situation:

•

Dial Tone (DT) cannot be heard except within a unit.

[4-T] Both MUX Failure / [4-S] MUX Ready Failure

[23-Y] MUX Clock Failure

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Note: For dual system configuration, if a system message indicates that both systems are faulty, first repair

the fault in the indicated system and then proceed to repair the PIM in the other system.

(1) For Dual Configuration

START

Check to see if the MUX (PH-PC36) circuit

card is making poor contact.

Set the MUX circuit card into STBY mode by

flipping the MBR key on the active GT (PH-

GT09) card. Refer to Section 12.1.6, Manual

Chapter 6.

Set the MB switch of the MUX circuit card UP.

Extract the MUX circuit card from its mounting

slot and clean the contact portion.

If cleaning cannot be done, repeat insertion and

extraction of the circuit card two or three times.

Set the MB switch of the MUX circuit card UP

and insert the circuit card into its mounting slot.

Set the MB switch of the MUX circuit card

DOWN.

Check to see if a station-to-station connection

can be set up within the faulty unit.

Check by replacing the MUX circuit card

with a spare.

Place the MUX circuit card into STBY mode by

flipping the MBR key on the active GT (PH-

GT09) card. Refer to Section 12.1.6, Manual

Chapter 6.

Replace the MUX circuit card. Refer to Section

3.3.2, MUX Card Replacement Procedure, in

Chapter 4.

CHAPTER 5

Page 340

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Place the MUX circuit card into ACT mode by

flipping the MBR key on the active GT (PH-

GT09) card. Refer to Section 12.1.6, Manual

tion 3.3.2, MUX Card Replacement Procedure,

Chapter 6.

Check to see if a station-to-station connection

can be set up to identify the circuit card respon-

sible for the fault.

Extract all the line/trunk circuit cards from

their mounting slots in the unit. Insert the

cards back into their slots one after another

and see if the dial tone is heard each time.

Extract all the line/trunk circuit cards from their

slots.

Note: Set the MB switch of the line/trunk

circuit card UP and extract.

Confirm the MUX ACT lamp on the MUX cir-

cuit card illuminates.

Set the MB switch of an extracted line/trunk

circuit card UP and insert the circuit cards into

their mounting slots one by one.

Confirm the OPE lamp of the inserted circuit

card illuminates by setting the MB switch

DOWN.

If Dial Tone (DT) is heard, check

the next circuit card.

Make a station-to-station call and see if DT can

be heard.

Note: Perform this check on the rest of the

circuit cards by inserting them into

their slots individually.

If DT is not heard, replace the cir-

cuit card with a spare.

END

NDA-24300

CHAPTER 5

Page 341

Issue 1

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

(2) For Single Configuration

START

Check to see if the MUX (PH-PC36)

Set the MB switch of the MUX circuit card UP.

circuit card is making poor contact.

Extract the MUX circuit card from its mounting

slot and clean the contact portion.

If cleaning cannot be done, repeat insertion and

extraction of the circuit card two or three times.

Set the MB switch of the MUX circuit card UP

and insert the circuit card into its mounting slot.

Set the MB switch of the MUX circuit card

DOWN.

Check to see if a station-to-station connection

can be set up within the faulty unit.

Check by replacing the MUX circuit card

with a spare.

Replace the MUX circuit card referring to Sec-

in Chapter 4.

Place the MUX circuit card into ACT mode by

flipping the MBR key on the active GT (PH-

GT09) card. Refer to Section 12.1.6, Manual

Chapter 6.

Check to see if a station-to-station connection

can be set up to identify a circuit card responsi-

ble for the fault.

CHAPTER 5

Page 342

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Extract all the line/trunk circuit cards from

their mounting slots in the unit. Insert the

cards back into their slots one after

another and see if the dial tone is heard

each time.

Extract all the line/trunk circuit cards from

their slots.

Note: Set the MB switch of the line/trunk

circuit card UP and extract.

Confirm the MUX ACT lamp on the MUX

circuit card illuminates.

Set the MB switch of an extracted Line/Trunk

circuit card UP and insert the circuit cards

into their mounting slots one by one.

Confirm the OPE lamp of the inserted circuit

card illuminates by setting the MB switch

DOWN.

Make a station-to-station call and see if dial

tone can be heard.

If DT is heard, check the next

circuit card.

Note: Perform this check on the reset of

the circuit cards by inserting them

into their slots individually.

If DT is not heard, replace the

circuit card with a spare.

END

NDA-24300

CHAPTER 5

Page 343

Issue 1

FAULT REPAIR PROCEDURES

4.4 Unit Fault - ACT-Side MUX Card Is Faulty and System Has Changed Over

Faulty Situation:

•

The ACT side has become faulty and the system changeover has executed in the

dual configuration system.

ATTENTION

Contents

Static Sensitive

•

[4-S] MUX Ready Failure / [4-T] Both MUX Failure

[23-Y] MUX Clock Failure

Handling

Precautions Required

START

Check to see if the MUX (PH-PC36)

circuit card of the STBY side is making

poor contact.

Set the MB switch of the MUX circuit card

UP.

Extract the MUX circuit card from its

mounting slot and clean the contact portion.

If cleaning cannot be done, repeat insertion

and extraction of the circuit card two or three

times.

Set the MB switch of the MUX circuit card

UP and insert the circuit card into its

mounting slot.

Set the MB switch of the MUX circuit card

DOWN.

Set the faulty system to ACT side by flipping

the MBR key on the active GT (PH-GT09)

card. Refer to Section 12.1.6, Manual System

Changeover of Speech Path System, in

Chapter 6.

If the connection is set up, set the

faulty system into STBY side.

Check to see if a station-to-station connection

can be set up within the faulty unit.

CHAPTER 5

Page 344

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Replace the MUX circuit card with a

spare, and check it.

Replace the MUX circuit card referring to

Procedure in Chapter 4.

Place the MUX circuit card into ACT mode

by flipping the MBR key on the active GT

(PH-GT09) card. Refer to Section 12.1.6,

Section 5.2, Speech Path System Fault - Fault

System, in Chapter 6.

Check to see if a station-to-station connection

can be set up and identify a circuit card

responsible for the fault.

If the connection is set up, set

the faulty system into STBY

side.

Perform the above check by extracting each

MUX circuit card individually.

END

NDA-24300

CHAPTER 5

Page 345

Issue 1

FAULT REPAIR PROCEDURES

5. SPEECH PATH (TSW) SYSTEM FAULT

This section explains the fault repair procedure when any of the faults shown in T a ble 5-7 has occurred in the

whole system.

Table 5-7 Speech Path (TSW) System Fault Situation

FAULTY SITUATION

• Noise, one-way speech, no tone

REFERENCE SECTION

Related to Speech

• Even if dialing has been made, dial tone does not stop.

Dial tone cannot be heard.

Section 5.3, Speech Path System Fault - When Dial

T o ne (DT) Cannot Be Heard

A fault occurring in the STBY side TSW is indicated by a system

message or an alarm lamp.

Section 5.4, Speech Path System Fault - STBY Side

Has Become Faulty

5.1 Check Point

When repairing a speech path fault, consider that when any of the faults shown in Table 5-7 have occurred

in the system, it is possible that the TSW circuit card is at fault. Always check the alarm lamps on the

TSW circuit card.

CHAPTER 5

NDA-24300

Page 346

Issue 1

FAULT REPAIR PROCEDURES

IMG0

IMG1

PIM 3

PIM 2

PIM 1

PIM 0

PIM 3

PIM 2

PIM 1

PIM 0

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

To IMG2 To IMG2 To IMG3 To IMG3

LVDS (Low Voltage Differential Signaling)

TSW 01

TSWM

TSW 00

MUX 003

TSW/

INT

TSW/

INT

TSW/

INT

TSW/

INT

MUX 013

MUX 012

MUX 011

MUX 010

TSW

MUX 002

MUX 001

MUX 000

TSW/INT

TSW 10

TSW 11

MUX 100

MUX 110

MUX 101

MUX 102

MUX 103

MUX 111

MUX 112

MUX 113

TSW/INT

Symbols

: Speech Path

: Circuit Card (active)

: Cable

: Circuit Card (STBY)

TSW: PH-SW12

MUX: PH-PC36

Figure 5-8 Speech Path Block Diagram

NDA-24300

CHAPTER 5

Page 347

Issue 1

FAULT REPAIR PROCEDURES

IMG2

IMG3

PIM 3

PIM 2

PIM 1

PIM 0

MUX

LC/TRK LC/TRK LC/TRK

PIM 2

PIM 1

PIM 0

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

To IMG0 To IMG0 To IMG1 To IMG1

LVDS (Low Voltage Differential Signaling)

TSW 03

TSWM

TSW 02

MUX 023

TSW/

INT

TSW/

INT

TSW/

INT

TSW/

INT

MUX 033

MUX 032

MUX 031

MUX 030

TSW

MUX 022

MUX 021

MUX 020

TSW/INT

TSW 12

TSW 13

MUX 120

MUX 130

MUX 121

MUX 122

MUX 123

MUX 131

MUX 132

MUX 133

TSW/INT

Symbols

: Speech Path

: Circuit Card (Active)

: Cable

: Circuit Card (STBY)

TSW: PH-SW12

MUX: PH-PC36

Figure 5-8 Speech Path Block Diagram (Continued)

CHAPTER 5

NDA-24300

Page 348

Issue 1

FAULT REPAIR PROCEDURES

5.2 Speech Path System Fault - Fault Related to Speech

Faulty Situation:

•

Fault related to speech such as noise, one-way speech, no-speed, etc. occurs.

ATTENTION

Even if dialing started, Dial Tone (DT) does not stop.

[1-C] Both TSW Write Failure

Contents

Static Sensitive

Handling

Precautions Required

[1-D] TSW Write Failure

(1) For Dual Configuration

START

Check to see if fault occurs by extracting

TSW circuit cards one by one.

Replace the TSW circuit card referring to

System Changeover of Speech Path System,

Procedure, in Chapter 4.

Place the TSW circuit card into ACT mode by

flipping the MBR key on the active GT (PH-

GT09) card. Refer to Section 12.1.6, Manual

in Chapter 6.

Check to see if a station-to-station connection

can be set up and identify a TSW circuit card

responsible for the fault.

Perform the above check by extracting the

TSW circuit cards individually.

Check to see if fault occurs by extracting

MUX circuit cards one by one.

Replace the MUX circuit card referring to

Procedure, in Chapter 4.

Place the MUX circuit card into ACT mode

by flipping the MBR key on the active GT

(PH-GT09) card. Refer to Section 12.1.6,

12.1.6, Manual System Changeover of

System, in Chapter 6.

NDA-24300

CHAPTER 5

Page 349

Issue 1

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Check to see if a station-to-station connection

can be set up and identify a circuit card respon-

sible for the fault.

Perform the above check by extracting the

MUX circuit cards individually.

When the PLO (PH-CK16/17/16-A/17-A)

Set MB switch of the PLO circuit card to UP

side.

circuit card is mounted for digital interface,

replace PLO circuit card with a spare and

check.

Confirm OPE lamp on the PLO circuit card of

the mate system illuminates.

Extract PLO circuit card from its mounting slot.

Set MB switch UP and insert the new PLO cir-

cuit card into its mounting slot.

Set MB switch DOWN.

Set MB switch of the ACT-side PLO circuit

card UP.

Confirm that the new PLO circuit card becomes

the ACT side (OPE lamp on the new card lights

green).

Set MB switch of the STBY side PLO DOWN.

Confirm that speech can be carried out normal-

ly by a station-to-station call.

Set the faulty speech path system to STBY

side by flipping the MBR key on the active

GT (PH-GT09) card. Refer to Section

Speech Path System, in Chapter 6.

END

CHAPTER 5

Page 350

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

(2) For Single Configuration

START

Check to see if the fault occurs by

extracting TSW circuit cards one by one.

Replace the TSW circuit card referring to

Procedure, in Chapter 4.

Check to see if a station-to-station connection

can be set up and identify a TSW circuit card

responsible for the fault.

Perform the above check by extracting the TSW

circuit cards individually.

Check to see if the fault occurs by

extracting MUX circuit cards one by

one.

Replace the MUX circuit card referring to

tion 2.3.2, TSW Card Replacement Procedure

Procedure, in Chapter 4.

Initialize the system by pressing the START

button on the TOPU.

Check to see if a station-to-station connection

can be set up and identify a TSW circuit card

responsible for the fault.

Perform the above check by extracting the TSW

circuit cards individually.

NDA-24300

CHAPTER 5

Page 351

Issue 1

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

When the PLO (PH-CK16/17) circuit card

Set MB switch of the PLO circuit card to UP

side.

is mounted for digital interface, replace

the PLO circuit card with a spare and

check it.

Confirm ACT lamp on the PLO circuit card

goes out.

Extract PLO circuit card from its mounting

slot.

Set MB switch UP and insert the new PLO

circuit card into its mounting slot.

Set MB switch DOWN.

Confirm the ACT lamp on the new PLO

circuit card illuminates.

Confirm that speech can be carried out

normally by a station-to-station call.

END

CHAPTER 5

Page 352

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

5.3 Speech Path System Fault - When Dial Tone (DT) Cannot Be Heard

Faulty Situation:

•

Dial Tone (DT) cannot be heard.

[1-A] Both TSW Failure (Permanent)

[1-E] Both TSW Clock Failure

[4-C] Both TSW Ready Failure

[23-Y] MUX Clock Failure

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Note: For dual system configuration, if a system message indicates that both systems are faulty, first repair

the fault in the indicated system and then proceed to repair the PIM in the other system.

START

Check to see if the TSW circuit card is

making poor contact.

Set TSW circuit card into STBY mode by flip-

ping the MBR key on the active GT (PH-GT09)

card. Refer to Section 12.1.6, Manual System

Changeover of Speech Path System, in Chapter

Set TSW MBR switch on the TSW card UP.

Set MB switch of the TSW circuit card UP.

Extract the TSW circuit card from its mounting

slot and clean the contact portion.

If cleaning cannot be done, repeat insertion and

extraction of the circuit card two or three times.

Set TSW MBR and MB switches on the TSW

circuit card UP and insert the circuit card into

its mounting slot.

Set MB switch of the TSW circuit card DOWN.

Set TSW MBR switch DOWN.

Check if a station-to-station connection can be

set up.

Check front cables.

Check the front cables. (See Figure 5-8).

END

Initialize the system by pressing the START

button on the TOPU and see if a station-to-sta-

tion connection can be set up.

NDA-24300

CHAPTER 5

Page 353

Issue 1

FAULT REPAIR PROCEDURES

5.4 Speech Path System Fault - STBY Side Has Become Faulty

Faulty Situation:

•

A fault occurred in the STBY side of the dual configuration system.

[1-B] TSW Failure (Permanent)

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

[1-D] TSW Write Failure

[1-F] TSW Clock Failure

•

[4-D] TSW Ready Failure

START

Check to see if the TSW circuit card is mak-

ing poor contact.

Set the TSW MBR switch of the TSW circuit

card UP.

Set the MB switch of the TSW circuit card UP

and extract the circuit card from its mounting

slot.

Extract the TSW circuit card from its mounting

slot and clean the contact portion.

If cleaning cannot be done, repeat insertion and

extraction of the circuit card two or three times.

Set the TSW MBR and MB switches of the

TSW circuit card UP and insert the circuit card

into its mounting slot.

Set the MB switch of the TSW circuit card

DOWN.

Set the TSW MBR switch DOWN.

Check if a station-to-station connection can be

set up.

Check PCM cables.

Check the PCM cables. See Figure 5-8.

Initialize the system by pressing the START

button on the TOPU and see if a station-to-sta-

tion connection can be set up.

CHAPTER 5

Page 354

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

Faulty Situation:

•

Fault related to speech such as noise, one-way speech, no-speed, etc. occurs.

Even if dialing started, Dial Tone (DT) does not stop.

[1-C] Both TSW Write Failure

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

[1-D] TSW Write Failure

Replace the TSW circuit card referring to Sec-

in Chapter 4.

Check to see if fault occurs by extracting

TSW circuit cards one by one.

Set the TSW circuit card into ACT mode by

flipping the MBR key on the active GT (PH-

GT09) card. Refer to Section 12.1.6, Manual

tion 3.3.2, MUX Card Replacement Procedure,

Chapter 6.

Initialize the system by pressing the START

button on the TOPU.

Check to see if a station-to-station connection

can be set up to identify a TSW circuit card re-

sponsible for the fault.

Perform the above check by extracting the TSW

circuit cards individually.

Check to see if the fault occurs by

extracting MUX circuit cards one by one.

Replace the MUX circuit card referring to Sec-

in Chapter 4.

Set the MUX circuit card into ACT mode by

flipping the MBR key on the active GT (PH-

GT09) card. Refer to Section 12.1.6, Manual

Section 6.2, Control System Fault - Fault Occurs Intermittently

Chapter 6.

Check to see if a station-to-station connection

can be set up and identify a TSW circuit card re-

sponsible for the fault.

Perform the above check by extracting the

MUX circuit cards individually.

END

NDA-24300

CHAPTER 5

Page 355

Issue 1

FAULT REPAIR PROCEDURES

6. CONTROL SYSTEM FAULT

This section explains the fault repair procedure for the control system listed in Table 5-8.

Table 5-8 Control System Fault Situation

FAULTY SITUATION

REFERENCE SECTION

Fault occurs occasionally at the STBY side.

STBY side is faulty.

Section 6.3, Control System Fault - STBY Side Is Faulty

6.1 Check Point

When repairing the control system, check the status of the following lamps:

•

CPR

TSW

MUX

EMA circuit cards

Figure 5-9 shows a block diagram of the CPU controlling block, where CPU #0 is active.

CHAPTER 5

NDA-24300

Page 356

Issue 1

FAULT REPAIR PROCEDURES

IMG0

IMG1

PIM 3

PIM 2

PIM 1

PIM 0

PIM 3

PIM 2

PIM 1

PIM 0

PM BUS

MUX

LC/TRK

MUX

PM BUS

LC/TRK

PM BUS

LC/TRK

PM BUS

LC/TRK

MUX

PM BUS

To IMG 2 To IMG 3

TSWM

TSW

/INT

TSW

/INT

TSW

/INT

TSW

/INT

U U U U

X X X X

TSW

003002001000

013 012 011 010

100101102103

110111112113

TSW/INT

TSW 00

TSW 01

TSW 10

TSW 11

TSW I/O BUS

MISC BUS

BUS

TSW I/O

MISC BUS

DLKC 1

DLKC 0

LPM

IOP1

MISC BUS

GT 0

MISC BUS

Note 1

Note 3

PLO 0

PLO 1

CPR

Note 2

MISC BUS

GT 1

ISAGT 0 ^T

IOP0

CPU clock

ISA BUS

Symbols

PCI BUS

LANI

MISC BUS

CPU 0

: Controlling Routes of CPU

: Circuit card (active)

: External Cable

: Cable

: Circuit card (STBY)

: Clock Oscillator

Reset Signal

PWR

IOC /

MISC

EMA

MEMORY

CPR

(ST-BY)

: Signral

CPU board

EMA:

LANI:

IOC:

PH-PC40

PZ-PC19

PH-IO24

ISAGT: PZ-GT13

ISAGT

MISC BUS

GT:

PH-GT09

PH-SW12

PH-CK16/17/16-A/17-A

TSW:

PLO:

PWR

DLKC: PH-PC20

MUX: PH-PC36

Note 1: The circuit cards, drawn by dotted lines, indicate they are in STBY state. These cards (TSW, MUX and

DLKC) are totally changed over to the ACT mode, when the MBR key of the active GT (PH-GT09) card is

once flipped. However, PLO (PH-CK16/17/16-A/17-A) is independent and not affected by the development.

Note 2: If the ACT/STBY of CPU is once changed over, the system of GT (in TSWM) also changes over.

Note 3: Though an external cable is physically connected between ISAGT0 and GT1, the actual control signal is

sent/received only between ISAGT0 and GT0. This is because GT0 and GT1 are having a multiple connection

on the backboard side. (Refer to Chapter 6, Section 12.)

Figure 5-9 CPU Controlling Block Diagram

NDA-24300

CHAPTER 5

Page 357

Issue 1

FAULT REPAIR PROCEDURES

IMG3

IMG2

PM BUS

PIM 3

MUX

LC/TRK

MUX

PM BUS

PIM 2

PM BUS

LC/TRK

PM BUS

PIM 1

LC/TRK

PM BUS

PIM 0

LC/TRK

MUX

PM BUS

To IMG 0 To IMG 1

TSWM

TSW

/INT

TSW

/INT

TSW

/INT

TSW

/INT

U U U U

X X X X

TSW

023022021020

033032031030

120121122123

130131132133

TSW/INT

TSW 02

TSW 03

TSW 12

TSW 13

TSW I/O BUS

MISC BUS

TSW I/O BUS

MISC BUS

DLKC 1

DLKC 0

LPM

IOP1

MISC BUS

GT 0

MISC BUS

Note 1

PLO 0

PLO 1

Note 3

GT 1

CPR

Note 2

MISC BUS

ISAGT 0 ^T

IOP0

CPU clock

ISA BUS

Symbols

PCI BUS

LANI

MISC BUS

CPU 0

: Controlling Routes of CPU

: Circuit card (active)

: External Cable

: Cable

: Circuit card (STBY)

: Clock Oscillator

Reset Signal

PWR

IOC /

MISC

EMA

MEMORY

CPR

(ST-BY)

: Signral

CPU board

EMA:

LANI:

IOC:

PH-PC40

PZ-PC19

PH-IO24

ISAGT: PZ-GT13

GT:

TSW:

PLO:

ISAGT

MISC BUS

(ST-BY)

PH-GT09

PH-SW12

PH-CK16/17/16-A/17-A

PWR

DLKC: PH-PC20

MUX: PH-PC36

Note 1: The circuit cards, drawn by dotted lines, indicate they are in STBY state. These cards (TSW, MUX and

DLKC) are totally changed over to the ACT mode, when the MBR key of the active GT (PH-GT09) card is

once flipped. However, PLO (PH-CK16/17/16-A/17-A) is independent and not affected by the development.

Note 2: If the ACT/STBY of CPU is once changed over, the system of GT (in TSWM) also changes over.

Note 3: Though an external cable is physically connected between ISAGT0 and GT1, the actual control signal is

sent/received only between ISAGT0 and GT0. This is because GT0 and GT1 are having a multiple connection

on the backboard side. (Refer to Chapter 6, Section 12.)

Figure 5-9 CPU Controlling Block Diagram (Continued)

CHAPTER 5

NDA-24300

Page 358

Issue 1

FAULT REPAIR PROCEDURES

6.2 Control System Fault - Fault Occurs Intermittently

Faulty Situation:

•

Fault occurs intermittently at ACT side in the dual configuration system.

Fault occurs intermittently in the single configuration system.

[0-C] ~ [0-K] CPU Failure

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

[1-C] Both TSW Write Failure

[1-D] TSW Write Failure

[3-D], [3-E] Lock-Up Failure (Permanent/Temporary)

(1) For Dual Configuration

START

Replace ACT-side related circuit card

(CPU, GT, TSW, MUX, EMA) with a spare,

and check.

Replace the circuit cards (CPU, GT, TSW, MUX,

EMA) individually referring to the following sec-

tions in Chapter 4:

• Section 1.3.1, CPR Replacement Procedure

• Section 1.3.2, EMA Card Replacement

• Section 2.3.1, GT Card Replacement

• Section 2.3.2, TSW Card Replacement

• Section 3.3.2, MUX Card Replacement

12.1.6, Manual System Changeover of Speech

Place the circuit card (CPU, GT, TSW, MUX)

into ACT mode individually by executing CPU or

Speech Path System changeover. Refer to Section

Path System, in Chapter 6.

Check to see if a station-to-station connection can

be set up and identify a circuit card responsible

for the fault.

After all the steps are complete, place the whole

circuit card (CPU, GT, TSW, MUX examined

above) to the ACT mode. Refer to Section 12.1.6,

Manual System Changeover of Speech Path Sys-

tem, in Chapter 6.

When a fault is not indicated, set the

faulty system to STBY mode. Refer

to Section 12, System Control Pro-

cedures, in Chapter 6.

Check to see if a fault is indicated.

NDA-24300

CHAPTER 5

Page 359

Issue 1

FAULT REPAIR PROCEDURES

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

(2) For Single Configuration

Replace the related circuit card (CPU, GT,

TSW, MUX, EMA) with a spare, and check.

Replace the circuit card (CPU, GT, TSW, MUX,

EMA) individually by referring to the following

sections in Chapter 4:

• Section 1.3.1, CPR Replacement Procedure

• Section 1.3.2, EMA Card Replacement

• Section 2.3.1, GT Card Replacement

• Section 2.3.2, TSW Card Replacement

• Section 3.3.2, MUX Card Replacement

• Section 1.3.1, CPR Replacement Procedure

Initialize the system by pressing the START

button on the TOPU and check to see if a

station-to-station connection can be set up and

identify a circuit card responsible for the fault.

END

CHAPTER 5

Page 360

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

6.3 Control System Fault - STBY Side Is Faulty

Faulty Situation:

•

Fault has occurred in the STBY side of dual configuration system.

[0-I] STBY CPU Failure

ATTENTION

Contents

•

Static Sensitive

Handling

Precautions Required

•

The ACT side has become faulty, and system changeover has executed.

[0-C], [0-H], [0-J] Processor Failure (ACT side)

START

Replace STBY side related circuit cards

(CPU, GT, TSW, MUX, EMA) with a spare,

and check.

Replace the circuit cards (CPU, GT, TSW,

MUX, EMA) individually by referring to the

following paragraphs in Chapter 4:

• Section 1.3.2, EMA Card Replacement

• Section 2.3.1, GT Card Replacement

• Section 2.3.2, TSW Card Replacement

• Section 3.3.2, MUX Card Replacement

Section 7.2, Fault of Alarm

Place the circuit cards (CPU, GT, TSW, MUX)

into ACT mode by executing CPU changeover.

Refer to Section 12.1.6, Manual System

Changeover of Speech Path System, in Chapter

Check to see if a station-to-station connection

can be set up to identify the circuit card

responsible for the fault.

When a fault is not indicated, set

the faulty systems to STBY side in

advance by executing CPU

changeover. Refer to Section 12,

System Control Procedures, in

Chapter 6.

END

NDA-24300

CHAPTER 5

Page 361

Issue 1

FAULT REPAIR PROCEDURES

IMG 0

IMG 1

TOPU

DSPL

DSPM

PZ-DK222

PIM 3

ALMB

PWR

MUX 0

LC/TRK

MUX 1

MUX 0

LC/TRK

MUX 1

DPWR

ALMA

ALMB

ALMA

ALMB

PIM 2

PWR

MUX 1

DPWR

ALMA

ALMB

ALMA

ALMB

PIM 1

PWR

DPWR

MUX 1

DPWR

ALMA

ALMB

ALMA

ALMB

PIM 0

PWR

MUX 0

LC/TRK

MUX 1

DPWR

ALMA

TSWM

PZ-PW92

LANI 1

GT 1

PWR1

EMA

PZ-PW92

LANI 0

GT 0

ALM

DSP

PWR0

ALM

EMA

LPM (REAR VIEW)

LPM (FRONT VIEW)

REAR VIEW

- Symbols -

Alarm related connector

Circuit card

Cable

EMA: PH-PC40

LANI: PZ-PC19

MUX: PH-PC36

ISAGT: PZ-GT13

: External Cable

Figure 5-10 Alarm Bus Cable Connections Diagram

NDA-24300

CHAPTER 5

Page 362

Issue 1

FAULT REPAIR PROCEDURES

IMG 2

IMG 3

TOPU

DSPM

PZ-DK222

PIM 3

ALMB

PWR

MUX 0

LC/TRK

MUX 1

MUX 0

LC/TRK

MUX 1

DPWR

ALMA

ALMB

ALMA

ALMB

PIM 2

PWR

MUX 0

LC/TRK

MUX 1

DPWR

ALMA

ALMB

ALMA

ALMB

PIM 1

PWR

MUX 0

MUX 1

DPWR

ALMA

ALMB

ALMA

ALMB

PIM 0

PWR

MUX 0

MUX 1

DPWR

ALMA

PZ-PW92

LANI 1

GT 1

PWR1

EMA

PZ-PW92

LANI 0

GT 0

DSP

PWR0

DSP

LPM (REAR VIEW)

LPM (FRONT VIEW)

- Symbols -

Alarm related connector

Circuit card

Cable

EMA: PH-PC40

LANI: PZ-PC19

MUX: PH-PC36

ISAGT: PZ-GT13

: External Cable

Figure 5-10 Alarm Bus Cable Connections Diagram (Continued)

NDA-24300

CHAPTER 5

Page 363

Issue 1

FAULT REPAIR PROCEDURES

7. ALARM INDICATION FAULT

This section explains the fault repair procedure where any of the faults shown in T a ble 5-9 occur.

Table 5-9 Alarm Indication Fault Situation

FAULTY SITUATION

REFERENCE SECTION

A fault is indicated on the TOPU, but it is not indicated on the Alarm Indicating Panel

(External Alarm Indicating Panel).

Indicating Panel

• A system message is indicated, but no alarm indication is made on the TOPU.

Section 7.3, Fault That

Cannot Be Detected

• An alarm lamp on the circuit card is lighting, but no alarm indication is made on the MAT

or on the TOPU.

7.1 Check Point

When repairing an alarm indication fault, check the alarm cable route shown in Figure 5-11 and Figure 5-

12.

7.2 Fault of Alarm Indicating Panel

START

ATTENTION

Contents

Static Sensitive

Handling

Confirm lamps and power supply circuit of the Alarm Indicating Panel.

Confirm cross connections on the MDF.

Precautions Required

Confirm that the connector of 16 PH EXALM CA is firmly plugged in the EXALM connector on

the backplane of LPR.

END

CHAPTER 5

Page 364

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

TOPU

PIM3

Alarm Lamps

DSPL

ALMA

ALMB

PIM2

ALMA

ALMB

PIM1

PIM0

ALMA

ALMB

ALMA

EMA

DSP

ALM

Alarm

Indicating

Panel

LPM

MDF

16PH EXALM CA

Symbols

: Flat Cable

: Connector

: CHAMP Connector-Ended Cable

: To alarm information of PWR, MUX, TSW

: Circuit Card

Figure 5-11 Cable Routing for Alarm Indications

16PH EXALM CA

CHAMP Connector Cable

MDF

MJA

LPM

MNA

EXALM

Alarm

Indicating

Panel

BELL

MJB

MNB

Backplane

RPT1

RPT0

-48V

Fuse

-48V

Power Receiving Terminal

Figure 5-12 Cabling Related to Alarm Indicating Panel

NDA-24300

CHAPTER 5

Page 365

Issue 1

FAULT REPAIR PROCEDURES

7.3 Fault That Cannot Be Detected

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

Check the DSP flat cable (See Figure 5-10.).

If the EMA card is removed from the system while the system is in operation under

the control of the CPU #1, the system will reset and stop all call processing. See

Section 1.3.2, EMA Card Replacement Procedure, in Chapter 4 for detailed instructions.

WARNING

Replace the EMA circuit card with a spare.

Set the MB switch of the EMA circuit card, and extract the circuit card from its mounting

slot.

Make necessary switch settings on the new circuit card.

Set MB switch UP side and insert the circuit card into its mounting slot.

Set the MB switch DOWN.

Check to see if a fault is detected.

END

CHAPTER 5

Page 366

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

8. POWER SUPPLY FAULT

This section explains the fault repair procedure when any of the faults shown in Table 5-10 occur.

Table 5-10 PWR Supply Fault Situation

FAULTY SITUATION

Fuse Blown Fault

REFERENCE SECTION

Section 8.2, Fuse Blown Fault

Circuit Breaker OFF, Fault in PWR Supply

Fault of Alarm Lamps on PWR Supply

Section 8.3, Circuit Breaker OFF Fault in PWR Supply

Section 8.4, Fault of Alarm Lamps on PWR Supply

8.1 Check Point

When repairing a power supply fault, consider the following items:

(1) Before checking the system, check the rectifier, battery, and power cables.

(2) The PWR circuit card is equipped with the circuits to supply ringing signal and howler tone. When a fault

occurs that causes the bell of the telephone not to ring, or howler tone cannot be heard, etc., check the

alarm lamp on the PWR circuit card.

(3) Figure 5-13 through Figure 5-15 show the block diagrams for the power supply to each module.

IMG0

PIM3

PWR

LC/TRK

EMA

MUX0 MUX1

PIM2

LC/TRK

INT1

LC/TRK

MISC

PWR

Note

PWR

LC/TRK

MUX0 MUX1

PIM1

PWR

Note

PWR

LC/TRK

MUX0 MUX1

PIM0

PWR

Note

PWR

LC/TRK

MUX0 MUX1

LPM

PWR

Note

PWR

IOC

ISAGT0

CPU0

Note

BASEU

Note: PWR1 is mounted when power supply system is a dual

system configuration.

Figure 5-13 Block Diagram of Power Supply System (IMG0)

NDA-24300

CHAPTER 5

Page 367

Issue 1

FAULT REPAIR PROCEDURES

IMG1

PIM3

PWR

LC/TRK

MUX0 MUX1

PIM2

LC/TRK

INT1

LC/TRK

PWR

Note

PWR

LC/TRK

MUX0 MUX1

PIM1

PWR

Note

PWR

LC/TRK

MUX0 MUX1

PIM0

PWR

Note

PWR

LC/TRK

MUX0 MUX1

LPM

PWR

Note

PWR

MISC

PWR

GT0 TSW00 TSW01 TSW02 TSW03 PLO0

DLKC0

Note

BASEU

Note: PWR1 is mounted when power supply system is a dual

system configuration.

Figure 5-14 Block Diagram of Power Supply System (IMG1)

IMG2/3

PIM3

PWR

LC/TRK

MUX0 MUX1

PIM2

LC/TRK

INT1

LC/TRK

PWR

Note

PWR

LC/TRK

MUX0 MUX1

PIM1

PWR

Note

PWR

LC/TRK

MUX0 MUX1

PIM0

PWR

Note

PWR

LC/TRK

MUX0 MUX1

DUMMY

PWR

Note

Note: PWR1 is mounted when power supply system is a dual

BASEU

system configuration.

Figure 5-15 Block Diagram of Power Supply System (IMG2/3)

CHAPTER 5

Page 368

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

(4) Figure 5-16 shows the power supply system for PIM.

PWR0

PWR1

DC-DC

CONV

DC-DC

CONV

+5V, +12V, -5V

RGU

CR (for LC)

HOW

REL

HOW

REL

HOW (for LC)

-48V

NFB

-48V (for LC, TRK)

+80V

rel

+80V

-48V

+80V Note

+80V

-48V

Note: +80V is for message waiting lamp.

Figure 5-16 Power Supply to PIM

(5) Figure 5-17 shows the power supply system for LPM.

(To CPR#0)

(To CPR#1)

PWR0

PWR1

DC-DC

CONV

DC-DC

CONV

+5V,+12V

(To EMA, MISC, Cards, etc.)

REL

-48V

(To EMA, MISC, Cards, etc.)

-48V

+80V

-48V

Figure 5-17 Power Supply to LPM

NDA-24300

CHAPTER 5

Page 369

Issue 1

FAULT REPAIR PROCEDURES

(6) Figure 5-18 shows the power supply system for TSWM.

PWR0

PWR1

DC-DC

CONV

DC-DC

CONV

+5V, +12V, +5V

(To MISC Cards)

REL

-48V

(To MISC, GT, TSW, DLKC,

PLO Cards)

-48V

+80V

-48V

Figure 5-18 Power Supply to TSWM

CHAPTER 5

Page 370

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

8.2 Fuse Blown Fault

START

Check the backplane of the PIM.

Make a visual check on the backplane for pin

contacting, melting or burn, etc.

Extract all the circuit cards from the PIM,

and insert them back into their slots

individually to see if the fuse blows.

Set the MB switch of the PWR supply UP.

Set the circuit breaker of the PWR supply

DOWN.

Extract all the circuit cards from their mounting

slots, except PWR supply.

Replace the fuse with spare.

Set the circuit breaker of the PWR supply UP

side.

Set the MB switch of the PWR supply DOWN.

Insert the circuit cards into their mounting slots

individually, with their MB switch to UP side.

Check to see if the fuse blows when the MB

switch has been set to DOWN.

END

NDA-24300

CHAPTER 5

Page 371

Issue 1

FAULT REPAIR PROCEDURES

8.3 Circuit Breaker OFF Fault in PWR Supply

START

Check the backplane of the PIM.

Make a visual check on the backplane for pin

contacting, melting or burning, etc.

Extract all the circuit cards from the PIM,

and make a visual check of the circuit

cards.

Set MB switch of the PWR supply UP.

Set the circuit breaker of the PWR supply

DOWN.

Extract all circuit cards out of their mounting

slots.

Make a visual check of the extracted circuit

cards. Check ICs, resistors, and capacitors to

see if any are burned.

END

CHAPTER 5

Page 372

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

8.4 Fault of Alarm Lamps on PWR Supply

START

Press RESET button of the PWR supply.

Alarm lamp goes out.

FAULT SUPERVISION

Alarm lamp illuminates again.

Set the MB switch on the PWR supply UP.

Turn circuit breaker OFF.

Set MB switch on all the circuit cards, except

PWR supply.

Extract all circuit cards from their mounting

slots.

Turn circuit breaker ON.

Set the MB switch to DOWN side.

Check to see if the alarm lamp illuminates.

If the alarm lamp illuminates,

replace the PWR supply with a

spare.

If the alarm lamp does not

illuminate, insert the circuit cards

END

into

their

mounting

slot

individually to see if the alarm

lamp illuminates.

Note: Insert each PWR supply with its MB switch to UP side, and then set it back to DOWN side.

NDA-24300

CHAPTER 5

Page 373

Issue 1

FAULT REPAIR PROCEDURES

9. FAN UNIT FAULT

This section explains the fault repair procedure where a fan in the Fan Unit (FANU) does not operate.

9.1 Check Point

(1) When repairing a FANU fault, exercise care about the following conditions. The fans (a total of 3) are

activated by operating the PWR SW key located on the PZ-M369. The conditions for starting the fan are

as follows:

•

With PWR SW key for the fan set to ON position:

With PWR SW key for the fan set to AUTO position:

Always operating

Starts operating if the in-frame tempera-

ture is higher than 40°C (104°F); stops op-

erating at temperatures lower than 32°C

(90°F). See Figure 5-19.

(2) When replacing the FANU with a spare, refer to Section 4., Fan Unit Replacement, in Chapter 4.

Fan Unit

FAN 0

Thermal Unit

Thermal

Relay

FAN 1

FAN 2

Thermal

Thermal Thermal

Relay

32 C

89 F

104 F

158 F

140 F

FC0

FC1

POW

FC2

FUSE ALM

FUSE

-48V

Power

Filter

To PIM

FAN

OFF

AUTO

FE LM -48V

FAN START Switch

MN MJ

FAN

To PIM

To Display

Section

of TOPU

Figure 5-19 Circuit Diagram of Fan Unit and Thermal Unit

NDA-24300

CHAPTER 5

Page 374

Issue 1

FAULT REPAIR PROCEDURES

9.2 Fan Unit Fault

START

Set the PWR SW key on the PZ-M369 to the ON position.

When the fan spins

Set PWR SW key to AUTO position, and short the thermal relay of the thermal

unit.

If the fan does not

operate

Check the connector cable between

the FANU and the thermal unit.

If the fan operates

Replace thermal relay with a spare.

Disconnect

the

fan

connector of the cable for

the thermal unit.

Replace thermal relay with

a spare.

Connect the fan connector.

If the fan does not operate

Check the voltage (DC -48 V) at connectors FC0 through FC2.

If the voltage is less

than -48 V

Check the connector cable (fan con-

nector) between the FANU and the

PIM.

If the voltage is -48 V

Replace the fan with a spare. Refer to

Section 4., Fan Unit Replacement, in

Chapter 4.

After the fault is corrected, set PWR SW key to the AUTO position. If the fans are to continue operating

constantly, set PWR SW key to the ON position.

END

NDA-24300

CHAPTER 5

Page 375

Issue 1

FAULT REPAIR PROCEDURES

10. TONE FAULT

This section explains the fault repair procedure when any of the various tones cannot be heard in the whole

system.

10.1 Check Point

When repairing a tone fault, consider that the tone generator circuit is equipped in the TSW circuit card

and supplies tone.

Figure 5-20 shows an example of the related trunking for dial tone connection.

TSW

Dial

Tone

ORT

Figure 5-20 DialTone Connection

CHAPTER 5

Page 376

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

10.2 Tone Fault

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

START

Replace the TSW circuit card with a spare

and check.

When only Hold Tone is faulty

If External Hold Tone source is in

use

Check the external equipment which sends out

hold tone.

Check cross connections on the MDF. Figure 5-

21 shows a block diagram of external hold tone

supply (optional).

Replace the EMA/PLO circuit

card with a spare.

Set the MB switch of the EMA/PLO circuit

card to UP side and extract the circuit card from

its mounting slot.

Note: When system is 1-IMG

configuration, replace

EMA card. Otherwise,

replace PLO card.

If the EMA card is removed

Make necessary switch settings on the new

circuit card, referring to the card extracted.

WARNING

from the system while the

system is in operation under

the control of the CPU #1, the

system will reset and stop all

call processing. Refer to

Section 1.3.2, EMA Card

Replacement Procedure, in

Chapter 4, for detailed

instructions.

Set the MB switch of the new circuit card UP

and insert the circuit card into its mounting slot.

Set the MB switch DOWN.

Initialize the system and confirm the tone.

END

NDA-24300

CHAPTER 5

Page 377

Issue 1

FAULT REPAIR PROCEDURES

IMG1

PIM 3

PIM 2

PIM 1

PIM 0

TSWM

External

Tone

Source

(Option)

PLO 1

PLO 0

TSW 10

TSW 00

TSW 11

TSW 01

TSW 12

TSW 02

TSW 13

TSW 03

Melody

To Music

Connector

for EMA

Card (IMG0)

MDF

Note

Symbols

: Circuit Card

: Connector

: External Cable

PLO : PH-CK16/17/16-A/17-A

EMA : PH-PC40

TSW : PH-SW12

Note: If PH-CK16-A/PH-CK17-A is used, multiple connections are made between PLO#0 and PLO#1.

Refer to the description of PH-CK16-A or PH-CK17-A in the Circuit Card Manual.

Figure 5-21 External Hold Tone Supply Block Diagram

CHAPTER 5

NDA-24300

Page 378

Issue 1

FAULT REPAIR PROCEDURES

11. SYSTEM DOWN FAULT

This section explains the fault repair procedure when both the CPU and TSW systems are faulty. Figure 5-22

shows the sequence of repair for system down fault.

When cause for the fault cannot be identified:

Section 11.1

When faulty circuit cards can be assumed from

system message: Section 11.2

Check power supply.

Replace doubtful circuit card with a spare.

Minimize system configuration.

Execute system initialization and see if the mode becomes ON-LINE.

Figure 5-22 System Down Fault Repair Sequence

NDA-24300

CHAPTER 5

Page 379

Issue 1

FAULT REPAIR PROCEDURES

11.1 When Cause for Fault Cannot Be Identified

START

Check power supply circuits.

Check voltage (DC: -48V, ±5V) at LOAD side

of the rectifier.

Confirm that NFB (circuit breaker) on all PWR

supplies is at ON position (UP side).

Check to see if there is any PWR supply to

which the alarm lamp illuminates.

System Initialization by loading office data

and program data from the hard disk (Refer

to Chapter 6.)

Service connections such as

See “Check by Minimizing the System

station-to-station

cannot be set up.

connection

Configuration” on the next page.

Service connections such as

station-to-station connection can

be set up.

Data in the memory is temporarily destroyed.

Observe the situation for a while.

CHAPTER 5

Page 380

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

(1) Check by minimizing the system configuration

Mount only the basic circuit cards in CPU

No. 0 system and initialize.

Remove all circuit cards from CPU No. 0

system except the basic circuit cards.

Circuit cards to be mounted are as follows:

CPU, EMA, TSW, MUX

(EMA: PH-PC40, TSW: PH-SW12, MUX:

PH-PC36)

On the CPU Display Panel (DSP), set its SENSE

switch to “1.”

Press Reset (RST) button on the DSP.

CPU OPE lamp should be illuminated on the

DSP.

Initialization cannot be made.

Check by replacing the basic circuit cards indi-

vidually.

Set MB switch of the circuit card UP and

extract the circuit card from its mounting

slot.

Make necessary switch settings on the new

circuit card.

Set MB switch of the new circuit card UP

and insert the circuit card into its mounting

slot.

Set MB switch DOWN.

On the DSP (CPU), set SENSE switch to “1.”

Press RST button on the DSP.

CPU OPE lamp should illuminate on the DSP.

If CPU OPE lamp of the DSP does not

illuminate, replace next circuit card and check it.

(Repeat the above steps for all basic circuit

cards.)

END

NDA-24300

CHAPTER 5

Page 381

Issue 1

FAULT REPAIR PROCEDURES

11.2 When Faulty Circuit Cards Can Be Assumed From System Message

Faulty Situation:

When the system is down with message [0-C] ~ [0-J] indicated, faulty circuit cards can be assumed from

the message detail data. Replace circuit cards with spares.

START

Replace faulty circuit card with a spare.

Set MB switch UP and extract the circuit card

from its mounting slot.

Make necessary switch settings on the new

circuit card.

Set the MB switch UP and insert the circuit

card into its mounting slot.

Set the MB switch DOWN.

Initialize the system by loading the office data

and program data from the hard disk.

Confirm that service connections such as

station-to-station connection can be set up.

END

CHAPTER 5

Page 382

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

12. COMMON CHANNEL INTEROFFICE SIGNALING (CCIS) LINE FAULT

This section explains the fault repair procedure when any of the faults shown in T a ble 5-11 occur to a specific

CCIS line.

Table 5-11 CCIS Line Fault Situation

FAULTY SITUATION

A specific CCH/CCT card is faulty.

REFERENCE SECTION

Section 12.3, Specific CCH/CCT Card Is Faulty

When the signal transmission line is a digital line, transmitting/

receiving of control signals cannot be performed.

Section 12.4, Fault of CCH, DTI and Related Flat

Cable

12.1 Check Point

When repairing a CCIS Line fault, consider the following items:

(1) Check alarm lamps on the CCH or CCT circuit card.

(2) Refer to Figure 5-23, and check the cable connection.

12.2 CCIS Line Control

The CCH/CCT circuit card controls the signal link (digital) of the interoffice common channel signaling

system and transmitting/receiving call processing information. The signal link controls permit normal

transmission and reception of call processing information.

A break in signal links is detected, then restored to establish signal links. The call processing information

is converted into No. 7 signal format for channel 1 (any channel) of the DTI before being transmitted to a

distant office. Figure 5-23 shows the CCIS line control route.

MDF

MUX

LT Cable

DTI

Front

Cable

CCH

CCT

To CCIS Line

LT Cable

CPU

TSW

Figure 5-23 Controlling CCIS Line

NDA-24300

CHAPTER 5

Page 383

Issue 1

FAULT REPAIR PROCEDURES

12.3 Specific CCH/CCT Card Is Faulty

START

Check by replacing CCH/CCT card with

a spare.

On CCH/CCT card, set the MBR switch UP.

On CCH/CCT card, set MBR switch UP and

extract the card from its mounting slot.

Make switch settings on a new CCH/CCT

card.

On new CCH/CCT card, set MBR and MB

switches UP and insert the card into its

mounting slot.

On new CCH/CCT card, set MB switch

DOWN.

On new CCH/CCT card, set MBR switch

DOWN.

Check whether the fault is still indicated.

END

CHAPTER 5

Page 384

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

12.4 Fault of CCH, DTI and Related Flat Cable

START

Check connectors and flat cables between

DTI and CCH.

On DTI cards, set MB switch UP. On CCH

card, set MBR switch UP.

Check the connector.

Check whether the connector is correctly con-

nected or not. If the connection is found im-

proper, plug and unplug the connector a few

times.

On DTI cards, set MB switch DOWN. On CCH

card, set MBR switch DOWN.

Check whether the fault is still indicated.

Check the flat cable.

On DTI cards, set MB switch UP. On CCH

card, set MBR switch UP.

Test the continuity of the flat cable. If found to

be abnormal, replace the flat cable with a spare.

On DTI cards, set MB switch DOWN. On CCH

card, set MBR switch DOWN.

Check whether the fault is still indicated.

Check by replacing the DTI card with

spare.

On DTI card, set MB switch UP and extract the

card from the mounting slot.

On a new DTI card, make the switch setting.

On new DTI card, set MB switch UP and insert

the card into the mounting slot.

On new DTI card, set MB switch DOWN.

Check whether the fault is still indicated.

END

NDA-24300

CHAPTER 5

Page 385

Issue 1

FAULT REPAIR PROCEDURES

13. INTEGRATED SERVICE DIGITAL NETWORK (ISDN) LINE FAULT

This section explains the fault repair procedure when any of the faults shown in T a ble 5-12 occur to a specific

ISDN.

Table 5-12 ISDN Line Fault Situation

FAULTY SITUATION

A specific CCH/CCT card is faulty.

REFERENCE SECTION

Section 13.3, Specific DCH/PRT Card Is Faulty

When the signal transmission line is a digital line, transmitting/

receiving of control signals cannot be performed.

Section 13.4, Fault of DCH, DTI, and Related Flat

Cable

13.1 Check Point

When repairing an ISDN Line fault, consider the following items:

(1) Check alarm lamps on the DCH or PRT circuit card.

(2) Refer to Figure 5-24, and check the cable connection.

13.2 ISDN Line Control

The DCH/PRT circuit card controls the signal link (digital) of the ISDN line and transmits/receives call

processing information.

The signal link controls permit normal transmission and reception of call processing information. Figure

5-24 shows the ISDN line control route.

MDF

MUX

LT Cable

DTI

Front

Cable

DCH

PRT

To ISDN Line

LT Cable

CPU

TSW

Figure 5-24 Controlling ISDN Line

NDA-24300

CHAPTER 5

Page 386

Issue 1

FAULT REPAIR PROCEDURES

13.3 Specific DCH/PRT Card Is Faulty

START

Check by replacing the DCH/PRT card with

a spare.

On DCH/PRT card, set MBR switch UP.

On DCH/PRT card, set MB switch UP and

extract the card from its mounting slot.

Make switch setting on a new DCH/PRT card.

On new DCH/PRT card, set MBR and MB

switches UP and insert the card into its

mounting slot.

On new DCH/PRT card, set MB switch

DOWN.

On new DCH/PRT card, set MBR switch

DOWN.

Check whether the fault is still indicated.

END

NDA-24300

CHAPTER 5

Page 387

Issue 1

FAULT REPAIR PROCEDURES

13.4 Fault of DCH, DTI, and Related Flat Cable

START

Check the connectors and flat cables

between DTI and DCH.

Check the connector.

On DTI cards, set MB switch UP. On DCH

card, set MBR switch UP.

Check whether the connector is correctly

connected. If the connection is found improper,

plug and unplug the connector a few times.

On DTI cards, set MB switch DOWN. On DCH

card, set MBR switch DOWN.

Check whether the fault is still indicated.

Check the flat cable.

On DTI cards, set MB switch UP. On DCH

card, set MBR switch UP.

Test the continuity of the flat cable. If abnormal,

replace the flat cable with spare.

On DTI cards, set MB switch DOWN. On DCH

card, set MBR switch DOWN.

Check whether the fault is still indicated.

Check by replacing the DTI card with a

spare.

On DTI card, set MB switch UP and extract the

card from the mounting slot.

On a new DTI card, make switch setting.

On new DTI card, set MB switch UP and insert

the card into the mounting slot.

On new DTI card, set MB switch DOWN.

Check whether the fault is still indicated.

END

CHAPTER 5

Page 388

Issue 1

NDA-24300

FAULT REPAIR PROCEDURES

14. HARD TIME CLOCK FAULT

This section explains the procedure for repairing a hard time clock failure which occurs within the EMA card.

START

Replace the EMA card.

If the EMA card is removed from the

Replace the EMA card referring to Section

1.3.2, EMA Card Replacement Procedure,

in Chapter 4.

WARNING

system while the system is in operation

under the control of the CPU #1, the

system will reset and stop all call

processing. See Section 1.3.2, EMA

Card Replacement Procedure, in

Chapter 4, for detailed instructions.

END

NDA-24300

CHAPTER 5

Page 389

Issue 1

This page is for your notes.

CHAPTER 5

Page 390

Issue 1

NDA-24300

CHAPTER 6

SYSTEM OPERATIONS

To maintain the system in a normal state, maintenance technicians need to monitor the servicing status of the

system. Figure 6-1 shows the flow of the system status monitor.

When trouble occurs in any part of the system or to any phase of system operations, maintenance technicians

are alerted by an alarm indication or by a report from a station user or an operator. When the system becomes

overloaded, maintenance technicians can execute Line Load Control.

SYSTEM STATUS MONITOR

1. ALARM INDICATIONS

•

Alarm Lamps on Circuit Card

Alarm Lamps on TOPU

Alarm Lamps on Attendant Console

2. COLLECTION OF SYSTEM MESSAGES

3. INDICATION OF LOCKOUT STATUS

4. LINE LOAD CONTROL

Figure 6-1 System Status Monitor

1. ALARM INDICATIONS

When trouble occurs in the system, the system activates an appropriate remedial action (system changeover,

make-busy shift of the circuit card, restart processing, etc.) by executing the automatic diagnostic function. Re-

sults of the action taken and the faulty situation are displayed.

1.1 Kinds of Alarm Indications

Figure 6-2 shows the kinds of alarm indications.

TOPU

CIRCUIT CARDS

TROUBLE

ALARM INDICATION

ATTENDANT/DESK CONSOLE

MAT

SYSTEM MESSAGE

SYSTEM DEDICATED PRINTER

Figure 6-2 Alarm Indications

NDA-24300

CHAPTER 6

Page 391

Issue 1

SYSTEM OPERATIONS

1.2 How to Stop Alarm Indications

To stop the alarm indication, press ALM RST key on the TOPU or use the RALM command.

Note: If the RALM command is executed, the system messages that show the reason for the failure will be

cleared. Always print the indicated system message before using this command.

1.3 Alarm Indications on TOPU

The system has alarm lamps on the TOPU as shown in Figure 6-3. T a ble 6-1 lists the meaning of each

lamp.

PRW

SMJ

SMN

ALM

SUP

PWR

ALM

NEAX2400 IMX

NEC

Figure 6-3 Alarm Indications on TOPU

Table 6-1 Description of Alarm Indications on TOPU

LAMP

COLOR

FUNCTION

CONTENTS

PWR ON

Green

Power ON Indication

Lights when the power is turned ON to the LPR (EMA card

mounted)

ALM MJ

ALM MN

ALM SUP

SMJ

Red

Alarm urgency level

The kind of lamp indications are programmable by variable alarm

indicating lamps for each indication. Refer to Section 1.4, V a riable Alarm Indication.

IMG

Yellow

Red

Alarm urgency level

indicating lamps for

IMG0

Lights when any abnormal state is detected within the system

(System Alarm MJ/MN)

SMN

Red

CHAPTER 6

Page 392

Issue 1

NDA-24300

SYSTEM OPERATIONS

1.4 Variable Alarm Indication

This feature allows PBX users to make a flexible change of system message output grades which range 0

to 3 and alarm lamp grades which consist of MJ, MN, SUP and NONE. Thus, the PBX users can give a

proper alarm grade to each system message according to their requirements. When assigning no data, the

default alarm grades are automatically adopted.

COMMAND

ALMG

COMMAND FULL NAME

Assignment of Alarm Grade Data

2. COLLECTION OF SYSTEM MESSAGES

System messages are collected in the following ways:

•

Automatic printout to the system message dedicated printer

Automatic printout to the MAT printer

Printout by DFTD command

2.1 Automatic Printout to System Message Dedicated Printer

Figure 6-4 shows the operating procedure.

Power on to printer.

If a message is registered, the contents will

print out.

Automatic

Printout Status

YES

Is printout

stopped

temporarily?

Set printer port to Make-Busy

status using MBSM command.

Figure 6-4 Automatic Printout to System Message Dedicated Printer Operating Procedure

COMMAND

COMMAND FULL NAME

Make Busy of System Message Printout

MBSM

NDA-24300

CHAPTER 6

Page 393

Issue 1

SYSTEM OPERATIONS

2.2 Display on MAT

Set Scanning to Scanning ON (default) on the Scanning PBX form to collect system messages. If any mes-

sage is collected, the information is displayed in the text box on the DFTD command form.

3. INDICATION OF LOCKOUT STATIONS

When a station is in lockout status (permanent signaling state, shorting across speech wires, etc.), it can quickly

be discovered, preventing the situation from developing into serious trouble.

3.1 Indicating Method

By entering the following commands from the MAT, information pertaining to the lockout station con-

cerned will display.

COMMAND

COMMAND FULL NAME

Display of Lockout Station - LENS

Display of Lockout Station - Number

DLSL

DLSS

3.2 Recovery Procedure

Go on-hook and then go off-hook again.

If dial tone is heard, the station is in permanent

signaling status.

Confirm the state of the handset of

the displayed station.

PBX

MDF

On the MDF, connect the test

telephone to the displayed station

and confirm Dial Tone (DT).

LOCKOUT STATION

SEPARATING

TEST TEL.

The in-house wiring (from the MDF to

the lockout station) is shorting.

Check the wiring.

YES

Here DT?

Figure 6-5 Recovery Procedure From Lockout Station

NDA-24300

CHAPTER 6

Page 394

Issue 1

SYSTEM OPERATIONS

Forcibly release the lockout station circuit.

RLST command

(Confirm: DT)

Go off-hook again and confirm DT.

YES

Circuit may be faulty temporarily.

Observe situation for a while.

Hear DT?

Replace 16LC card

with a spare.

Figure 6-5 Recovery Procedure From Lockout Station (Continued)

COMMAND

COMMAND FULL NAME

RLST

Release Station/Trunk

NDA-24300

CHAPTER 6

Page 395

Issue 1

SYSTEM OPERATIONS

4. LINE LOAD CONTROL

In the PBX, Line Load Control can be activated automatically or manually as a countermeasure against abnor-

mal traffic congestion.

In the case of automatic control, the system automatically monitors an overloaded situation and restricts out-

going calls from stations and incoming calls from trunks.

In the case of manual control, the operator at an Attendant/Desk Console or the MAT restricts outgoing calls

from stations and incoming calls from trunks.

This section covers the following methods to activate Line Load Control:

•

Control by dialing an access code from theATTCON/DESKCON

Control by entering command data from the MAT

System automatic monitoring

Operating Procedure

(1) Operations on the Attendant Console

By the operations on the ATTCON, restriction is effected on an outgoing call from a station having SFC

in which the SFI = 16 (Line Load Control) of ASFC command is set as RES=0 (incoming calls to that

station are allowed). For restricting incoming calls from a trunk, system data ASYD, SYS1, INDEX59,

b0=1 should be assigned.

•

Setting

Press LOOP key.

Dial the access code for setting

Line Load Control.

• Lamp (Figure 6-8) on control

panel lights.

(SST)

• System message [6-C] displays.

Press CANCEL key.

Figure 6-6 Line Load Control Operationson ATTCON—Setting

CHAPTER 6

Page 396

Issue 1

NDA-24300

SYSTEM OPERATIONS

•

Cancelling

Press LOOP key.

Dial the access code for cancelling

Line Load Control.

• Lamp (Figure 6-8) on control

panel lights.

(SST)

• System message [6-D] displays.

Press CANCEL key.

Figure 6-7 Line Load Control Operations on ATTCON—Cancelling

NEC

LAMP

Figure 6-8 Locations of Lamps (ATTCON)

NDA-24300

CHAPTER 6

Page 397

Issue 1

SYSTEM OPERATIONS

(2) Key Operations on the Desk Console (DESKCON)

By the operations on the Desk Console, restriction is applied on an outgoing call from a station having

SFC in which the SFI = 16 (Line Load Control) of ASFC command is set as RES=0 (incoming calls to

that station are allowed). For restricting incoming calls from a trunk, system data ASYD, SYS1,

INDEX59, b0=1 should be assigned.

•

Setting

Press Lx (L1-L6) key.

Dial the access code for setting

Line Load Control.

• LLC displays on desk console

(Figure 6-11).

(SST)

• System message [6-C] displays.

Press CANCEL key.

Figure 6-9 Line Load Control Key Operations on DESKCON—Setting

Cancelling

•

Press Lx (L1-L6) key.

Dial the access code for cancelling

Line Load Control.

• LLC displays on desk console

(Figure 6-11).

(SST)

• System message [6-D] displays.

Press CANCEL key.

Figure 6-10 Line Load Control Key Operations on DESKCON—Cancelling

CHAPTER 6

Page 398

Issue 1

NDA-24300

SYSTEM OPERATIONS

LLC is displayed on a Desk Console, when Line Load Control starts.

Line Load indication

LLC

Desk Console

Figure 6-11 Line Load Control Indication (DESKCON)

(3) Operations on the MAT

By entering ALLC command from the MAT, Line Load Control executes. The station to be controlled and

the contents of the Line Load Control executed on the MAT are the same as those in Step (1), Operations

on the Attendant Console.

COMMAND

ALLC

COMMAND FULL NAME

Assignment of Line Load Control

(4) Automatic Setting

If the usage rate of the CPU exceeds the system data usage rate, Line Load Control is automatically set.

In this case, system message [6-C] displays. The station to be controlled and the contents of the Automatic

Line Load Control are the same as those in Step (1), Operations on the Attendant Console.

If the usage rate of the CPU drops below the system data usage rate, the Line Load Control is automati-

cally cancelled. In this case, system message [6-D] displays. While the Line Load Control is set, the lamps

on the control panel of the Desk/Attendant Console remain lit.

NDA-24300

CHAPTER 6

Page 399

Issue 1

SYSTEM OPERATIONS

5. IOC LINE MONITOR

(1) Functional Outline

This function monitors the IOC port status. As a result of the monitoring by this function, the following

is executed:

•

When the connection with a port has been disconnected, it is reported by a message.

When the connection with a port is set up, it is reported by a message.

The port status is stored in the memory and updated continuously.

(2) Message Judgment Criteria

Table 6-2 describes the message judgement criteria.

Table 6-2 Message Judgment Criteria

MESSAGE

Port Normal

CONTENT

System data is assigned, and DR signal is ON.

System data is assigned, and DR signal is OFF.

Port Abnormal

Output of Port Disconnected

This message is output when Port Abnormal status has lasted for 30 seconds.

This message is immediately output if port abnormal occurs after the IOC card is

initialized.

Output of Port Status Restored

This message is output when DR signal is ON for the port about which Output of Port

Disconnected message is output.

CHAPTER 6

Page 400

Issue 1

NDA-24300

SYSTEM OPERATIONS

6. LINE MANAGEMENT

The following explanations apply to line management:

•

Make-Busy/Make-Busy Cancel of Station and Data Terminal

Class Change and Number Change of Station and Data Terminal

Make-Busy/Make-Busy Cancel of C.O. Line/Tie Line

6.1 Make-Busy/Make-Busy Cancel of Station and Data Terminal

Stations and data terminals can be put into make-busy state by the following operations:

(1) On each station basis using the MBST command.

Assign the station number in the STN parameter and choose “1” for the MB box of the MBST command.

For the make-busy cancellation, choose “0” for the MB box.

(2) On each circuit basis using the MBLE command.

Assign LENS number in the LENS parameter and choose “1” for the MB box of the MBLE command.

For the make-busy cancellation, choose “0” for the MB box.

(3) On each circuit card basis using the MBPM command or operating the MB (toggle) key on the card.

•

Assign the required LENS number in the MG, UNIT and Group parameters and choose “3” for the

MB box of the MBPM command.

For the make-busy cancellation, choose “2” for the MB box.

•

Set to UP the MB key on the circuit card (= ON).

For make-busy cancellation, return the MB key down (= OFF).

NDA-24300

CHAPTER 6

Page 401

Issue 1

SYSTEM OPERATIONS

6.2 Class Change and Number Change of Station and Data Terminal

Figure 6-12 shows the procedure for class change and number change of station and data terminal.

START

Line Make-Busy

Refer to Section 6.1.

Class change and number

change

• For changing class, use ASCL command Note 1

• For changing station number, use ASTN command

Note 2

Line Make-Busy Cancel

END

Refer to Section 6.1.

Note 1: For guest station of Hotel System, use AGCL command.

Note 2: For guest station of Hotel System, use AGSN command.

Figure 6-12 Class Change and Number Change of Station and Data Terminal Procedure

6.3 Make-Busy/Make-Busy Cancel of C.O. Line/Tie Line

Figure 6-13 shows the procedure to make-busy/make-busy cancel of C.O. line/tie line.

START

• For make-busy/make-busy cancel by line basis MBLE

command

Make-Busy/Make-Busy Cancel of

C.O./Tie Line

• For make-busy/make-busy cancel by route basis MBRT

command

• For make-busy/make-busy cancel by each circuit card

MBPM commands or MB (toggle) switch setting on the

circuit card

END

Figure 6-13 Make-Busy/Make-Busy Cancel of C.O. Line/Tie Line Procedure

CHAPTER 6

Page 402

Issue 1

NDA-24300

SYSTEM OPERATIONS

6.4 Line Management Commands

COMMAND

COMMAND FULL NAME

AGCL

AGSN

ASCL

ASTN

Assignment of Guest Station Class

Assignment of Alternated Guest Station Number

Assignment of Station Class Data

Assignment of Station Number

Make Busy of LENS

Make Busy of Port Microprocessor

Make Busy of Route

Make Busy of Station

Make Busy of Trunk

Display of LENS Data

7. STATION MESSAGE DETAIL RECORDING SYSTEM (SMDR)

Billing information can be managed by connecting the PBX system and an external computer (SMDR equip-

ment).

Note: The SMDR equipment and its software must be provided by the user.

The PBX system provides the SMDR equipment with the following information:

•

Calling Party Information

Called Party Number

Call Start Time

Call End Time

Call Data

Authorization Code/Account Code

Upon receiving the above information from the PBX system, the SMDR equipment performs editing and man-

agement of the information and outputs the resulting information. This section explains the information pro-

vided to the SMDR equipment and also explains the method of controlling the interface port (IOC card)

between the SMDR equipment and the PBX system.

NDA-24300

CHAPTER 6

Page 403

Issue 1

SYSTEM OPERATIONS

7.1 Transmission Data to SMDR Equipment

(1) Transmission Format

As seen in the figure below, the basic information to be transmitted (Transmission Message) is a block

which begins with Start of Text (STX) and ends with End ofText (ETX). When the call ends, the whole

contents of this information is transmitted to the SMDR equipment.

TRANSMISSION MESSAGE

STX:

ETX:

SA:

START OF TEXT

END OF TEST

SYSTEM ADDRESS

UNIT ADDRESS

UA:

(2) Transmission Message

One transmission message consists of 128 bytes of data. Each byte represents by ASCII codes the data to

be transmitted (Refer to Table 6-3). The contents of the data to be transmitted vary with the kind of call,

but the first byte is always transmitted by ASCII code K (4B hex.). The second byte to be transmitted is

the data which specifies the kind of call.

Note: In case the Fusion service is involved, the message can consist of more than 128 byte data.

Figure 6-14 shows the transmission message of an outgoing call. Figure 6-15 shows the transmission mes-

sage of an incoming call. Also, Figure 6-16 shows the transmission message of a station-to-station call.

CHAPTER 6

NDA-24300

Page 404

Issue 1

SYSTEM OPERATIONS

Table 6-3 ASCII Code

ASCII CODE

CHARAC-

TER

BINARY DIGIT

REMARKS

HEX.

SPACE

STX

ETX

Special Characters Code

NDA-24300

CHAPTER 6

Page 405

Issue 1

SYSTEM OPERATIONS

BYTE DATA

MONTH

BYTE DATA

104

CALLED

NUMBER

AUTHORI-

ZATION

CODE

(SEE

PARAGRAPH

7.2.4)

DAY

ROUTE

NUMBER

CALL END

TIME

ORIGINATING

TRUNK

INFORMATION

(SEE

PARAGRAPH

7.2.3)

HOUR

(SEE

PARAGRAPH

7.2.2)

TRUNK

NUMBER

MINUTE

SECOND

ORIG

TENANT

CALLING

PARTY

INFORMATION

(SEE

PARAGRAPH

7.2.1)

114

116

118

ACCOUNT

CODE

YEAR

(SEE

PARAGRAPH

7.2.4)

STATION

ATTEND-

ANT

ROUTE

TRUNK

NUMBER

MONTH

DAY

SPACE

(20 Hex.)

(SEE

PARAGRAPH

7.2.7)

CALL

METER-

ING

CALL START

TIME

CALLING

PARTY

(SEE

TENANT

HOUR

PARAGRAPH

7.2.2)

OFFICE

CODE

CALLING

PARTY

MINUTE

SECOND

CONDI-

TION

128

ONLY FOR

NO. 7 CCIS

(SEE

PARAGRAPH

7.2.8)

100

OFFICE

CODE OF

BILLING

PROCESS

OFFICE

ROUTE

NUMBER

ROUTE

ADVANCE

INFORMATION

(SEE

PARAGRAPH

7.2.5)

ROUTE

NUMBER

Figure 6-14 Message Format for Outgoing Call

CHAPTER 6

Page 406

Issue 1

NDA-24300

SYSTEM OPERATIONS

BYTE DATA

MONTH

BYTE DATA

104

EI-K

CALLED

NUMBER

AUTHORI-

ZATION

CODE

(SEE

SECTION

7.2.4)

DAY

ROUTE

NUMBER

TERMINATING

CALL END

TIME

(SEE

SECTION

7.2.3)

TRUNK

INFORMATION

HOUR

(SEE

SECTION

7.2.2)

TRUNK

NUMBER

MINUTE

SECOND

ORIG

TENANT

CALLED

PARTY

INFORMATION

(SEE

SECTION

7.2.1)

114

116

118

ACCOUNT

CODE

YEAR

(SEE

SECTION

7.2.4)

STATION

ATTEND-

ANT

ROUTE

TRUNK

NUMBER

MONTH

DAY

SPACE

(20 Hex.)

(SEE

SECTION

7.2.7)

CALL

METER-

ING

CALL START

TIME

CALLED

PARTY

(SEE

TENANT

HOUR

SECTION

7.2.2)

OFFICE

CODE

CALLED

PARTY

MINUTE

SECOND

CONDI-

TION

128

ONLY FOR

NO. 7 CCIS

(SEE

SECTION

7.2.8)

100

OFFICE

CODE OF

BILLING

PROCESS

OFFICE

ROUTE

NUMBER

ROUTE

ADVANCE

INFORMATION

(SEE

SECTION

7.2.5)

Figure 6-15 Message Format for Incoming Call

NDA-24300

CHAPTER 6

Page 407

Issue 1

SYSTEM OPERATIONS

BYTE DATA

MONTH

BYTE DATA

TENANT

BYTE DATA

104

AUTHORI-

ZATION

CODE

(SEE

SECTION

7.2.4)

DAY

STATION

ATTEND-

ANT

CALL END

TIME (SEE

SECTION 7.2.2)

CALLED

PARTY

INFORMATION

(SEE SECTION

7.2.1)

SPACE

HOUR

(20 Hex.)

MINUTE

SECOND

ORIG

TENANT

CALLING

114

ACCOUNT

CODE

(SEE SECTION

7.2.4)

PARTY

YEAR

INFORMATION

(SEE SECTION

7.2.1)

SPACE

(20 Hex.)

116

118

STATION

ATTEND-

ANT

MONTH

DAY

SPACE

(20 Hex.)

SPACE

(20 Hex.)

CALL START

TIME (SEE

SECTION 7.2.2)

CALLING

PARTY

TENANT

HOUR

(SEE SECTION

7.2.6)

MINUTE

SECOND

CONDI-

TION

128

SPACE

(20 Hex.)

SPACE

(20 Hex.)

Figure 6-16 Message Format for Station-to-Station Call

CHAPTER 6

Page 408

Issue 1

NDA-24300

SYSTEM OPERATIONS

7.2 Details on Transmission Data

7.2.1 Calling Party Information/Called Party Information

•

The 9th byte indicates the type of the calling (or called) party. The 10th through 17th bytes are data

pertaining to this calling (or called) party.

ORIG (Originating Source Identification):

0 = Calling (or called) Party is a station

1 = Calling (or called) Party is an Attendant

2 = Calling (or called) Party is an outside (inside) party

•

The contents of 12th through 17th bytes vary with the type of the calling (or called) party.

(1) For a station (ORIG = 0): Data showing Station Number

DATA

EXAMPLE

BYTE

1st DIGIT

2nd DIGIT

3rd DIGIT

4th DIGIT

5th DIGIT

6th DIGIT

SPACE

(2) For an Attendant (ORIG = 1): Data showing Attendant Number

DATA

EXAMPLE

BYTE

1st DIGIT

2nd DIGIT

3rd DIGIT

4th DIGIT

5th DIGIT

6th DIGIT

SPACE

(3) For a trunk (ORIG = 2): Data showing Route Number and Trunk Number

Data

Example

Byte

1st DIGIT

2nd DIGIT

3rd DIGIT

1st DIGIT

Route

Number

RT No. = 1

Trunk

Number

TR No. = 50

2nd DIGIT

3rd DIGIT

NDA-24300

CHAPTER 6

Page 409

Issue 1

SYSTEM OPERATIONS

7.2.2 Call Start/Call End Time Information

•

The data which indicates Call Start Time is as follows:

BYTE

DATA

MONTH

(01-12)

DAY

EXAMPLE

THIS INFORMATION SHOWS THAT THE CALL

STARTED AT 1 O’CLOCK P.M. ON JUNE 1st,

1998

(01-31)

HOUR

(00-23)

MINUTE

(00-59)

SECOND

(00-59)

YEAR INFORMATION IS SENT OUT ONLY BY

THE LAST TWO DIGITS AS IN ‘98 FOR 1998.

114

115

YEAR

(00-99)

•

The data which indicates Call End Time is as follows:

BYTE

DATA

MONTH

(01-12)

DAY

EXAMPLE

THIS INFORMATION SHOWS THAT THE CALL

ENDED AT 9 O’CLOCK 10 MIN. 30 SEC. A.M.

ON OCT. 20, 1998.

(01-31)

HOUR

(00-23)

MINUTE

(00-59)

SECOND

(00-59)

YEAR INFORMATION IS SENT OUT ONLY BY

THE LAST TWO DIGITS AS IN ‘98 FOR 1998.

116

117

YEAR

(00-99)

CHAPTER 6

NDA-24300

Page 410

Issue 1

SYSTEM OPERATIONS

7.2.3 Called Number

The data which indicates the Called Number is as follows:

•

BYTE

DATA

EXAMPLE

1st DIGIT

2nd DIGIT

3rd DIGIT

4th DIGIT

5th DIGIT

9-0471-83-0351 HAS BEEN DIALED.

9: OG ACCESS CODE

SPACE

12th DIGIT

30th DIGIT

32nd DIGIT

SPACE

NDA-24300

CHAPTER 6

Page 411

Issue 1

SYSTEM OPERATIONS

7.2.4 Account Code/Authorization Code

•

The data which indicates the Account Code is as follows:

DATA

BYTE

EXAMPLE

1st DIGIT

2nd DIGIT

3rd DIGIT

4th DIGIT

5th DIGIT

ACCOUNT CODE: 1115 HAS BEEN DIALED.

SPACE

9th DIGIT

SPACE

10th DIGIT

Note: An Account Code is a numerical code to be dialed (up to 10 digits) by a station user with the capa-

bility to enter a cost accounting.

•

The data which indicates the Authorization Code is as follows:

DATA

BYTE

104

105

106

107

108

EXAMPLE

1st DIGIT

2nd DIGIT

3rd DIGIT

4th DIGIT

5th DIGIT

AUTHORIZATION CODE: 4001 HAS BEEN DIALED

SPACE

9th DIGIT

112

113

SPACE

10th DIGIT

Note: An Authorization Code is a numerical code to be dialed (up to 10 digits) by station users which will

override the station’s class (RSC or SFC) for facilities access restriction.

CHAPTER 6

NDA-24300

Page 412

Issue 1

SYSTEM OPERATIONS

7.2.5 Route Advance Information

When a call has been originated by route advancing, the following data is transmitted.

DATA

BYTE

EXAMPLE

1st DIGIT

2nd DIGIT

3rd DIGIT

1st DIGIT

2nd DIGIT

3rd DIGIT

ROUTE

NUMBER 1

THE CALL ORIGINATES

VIA NO. 3 ROUTE BECAUSE

NO. 30 ROUTE IS BUSY.

ROUTE

NUMBER 2

ROUTE NUMBER 1: The route which was actually used.

ROUTE NUMBER 2: The route which should have been selected first.

7.2.6 Condition B Information

The 51st through 53rd bytes are Condition B Information. The Condition B Information indicates the

following data:

DATA

OUTPUT NUMBER

0, 1 or SPACE

0–3 or SPACE

0–5 or SPACE

BYTE

C2:

C1:

0 = Call is not transferred

1 = Call is transferred

0 = Normal Call

1 = Call originated by OG trunk queuing

2 = Call originated by dialing with Account Code

3 = Call originated by OG trunk queuing and dialing with Account Code

C0:

0 = Regular Call (Direct Dialing from a station)

1 = Regular Call (Call is made through an ATTCON/DESKCON)

2 = Call through route advance (Direct Dialing from a station)

3 = Call through route advance (Call is made through anATTCON/DESKCON)

4 = Call through Least Cost Routing (Direct Dialing from a station)

5 = Call through Least Cost Routing (Call is made through an ATTCON/DESKCON)

NDA-24300

CHAPTER 6

Page 413

Issue 1

SYSTEM OPERATIONS

7.2.7 Call Metering Information

The value of call metering from the Central Office is transmitted via the data from the 92nd byte to

95th byte.

DATA

1000

100

BYTE

EXAMPLE

WHEN 5200 METERING PULSES

ARE RECEIVED FROM C.O.

7.2.8 Office Code of Calling (Called) Party and Billing Process Office

The 96th byte through 99th byte indicates the Office Code of Calling (Called) Party terminated via

CCIS line.

The 100th byte through 103rd byte indicates the Office Code of the office processing centralized bill-

ing for CCIS network.

Note: Office Code includes the CCIS line access code.

BYTE

DATA

EXAMPLE

1st DIGIT

2nd DIGIT

3rd DIGIT

4th DIGIT

1st DIGIT

2nd DIGIT

3rd DIGIT

4th DIGIT

OFFICE CODE OF

CALLING (CALLED)

PARTY

OFFICE CODE = 812

SPACE

100

101

102

103

OFFICE CODE OF

BILLING PROCESS

OFFICE

OFFICE CODE = 813

SPACE

CHAPTER 6

Page 414

Issue 1

NDA-24300

SYSTEM OPERATIONS

7.2.9 Text Format of Centralized Billing - Fusion

Below is the text format for billing information (Fusion) to be transmitted to the SMDR equipment.

On the following pages, Figure 6-17 through Figure 6-19, provide detailed information.

Kind

Data

Note

Kind

Data

Length

Data

Length

Transmission Data

STX : Start of Text

KK : Outgoing

KM : Extension

ETX : End of Text

KL : Incoming

Note: For details on the Kind of Data, see T a ble 6-4.

Table 6-4 Centralized Billing—Fusion Kinds of Data

KIND

DATA

(STATION)

CONTENTS

(OUTGOING)

(INCOMING)

Not Used

Outgoing Trunk/Incoming Trunk Information

Calling Party Information (Station Number)

Calling Party Information (Telephone Number)

Provided

Conditionally

Provided

Conditionally

Provided

Called Party Information (Station Number)

Called Party Information (Telephone Number)

Provided

Conditionally

Provided

Conditionally

Provided

Call Start/Call End Time

Account Code

Provided

Conditionally

Provided

Conditionally

Provided

Conditionally

Provided

Condition B Information

Provided

Alternate Routing Information/Incoming Route

Number

Dial Code

Provided

Conditionally

Provided

Office Code Information (For CCIS)

Authorization Code

Conditionally

Provided

Conditionally

Provided

Conditionally

Provided

Conditionally

Provided

Condition C Information + Billing Info/Call Metalling

Info

Provided

Conditionally

Provided

NDA-24300

CHAPTER 6

Page 415

Issue 1

SYSTEM OPERATIONS

Table 6-4 Centralized Billing—Fusion Kinds of Data (Continued)

KIND

DATA

(STATION)

CONTENTS

(OUTGOING)

(INCOMING)

Condition D Information + Bill Notification Attendant

Console Number

Conditionally

Provided

Department Code

Conditionally

Provided

Automatic Number Indication

Converted Number

Conditionally

Provided

Conditionally

Provided

Conditionally

Provided

18-99 Not Used

Note: Conditionally Provided: Information is provided when data is effective. Provided: Information is

provided on every call with no exception. -: Not available.

CHAPTER 6

NDA-24300

Page 416

Issue 1

SYSTEM OPERATIONS

Byte Data

STX

220

225

230

235

240

Billing

Informa-

tion

/Call

Metering

Condition C

Information

Note

Minute

Second

150

155

Milli-Second

Ye a r

For more

information on

the data to

which the Note

marks are

Condition D

Information

Note

FPC

(3 digits)

Outgoing

Trunk

Information

Bill Notifi-

cation ATT

CON No.

Month

Day

Physical

Route No.

Call End

Time

attached, see

Reference.

160

165

170

Department

Code

Trunk No.

Dial Code

(Max. 32

digits)

Hour

Dial Code

Department

Code

Minute

Second

Logical

Route No.

Milli-Second

245

250

255

ORIG

Calling

Party

Information

(Station No.)

Tenant

(3 digits)

100

175

180

185

Note

STN No.

ATT CON

No.

RT/TK No.

(6 digits)

Account

Code

105

110

115

Account

Code

(Max. 16

digits)

Automatic

Number

Indication

(Max. 32

digits)

Automatic

Number

Indication

Note

FPC

(3 digits)

260

265

Office

Code of

Calling

Party

User

Group

Number

Office Code

Information

Calling

Party

Information

(Telephone No.)

190

195

Office

Code of

Billing Pro-

cess Office

Condition B

Information

Note

120

125

Telephone

Number

(Max. 16

digits)

270

275

280

Authoriza-

tion Code

200

205

210

Logical

Route No.

FPC1

Authoriza-

tion Code

(Max 16

digits.)

130

Alternate

Routing

Information

Note

Physical

RT No. 1

Converted

Number

Converted

Number

(Max. 6

digits)

Logical

RT No. 1

135

140

285

FPC2

Year

ETX

Call

Start

Time

Physical

RT No. 2

215

Month

Day

0, 0, 0

Logical

RT No. 2

145

Hour

Figure 6-17 Message Format for Outgoing Call - Fusion

NDA-24300

CHAPTER 6

Page 417

Issue 1

SYSTEM OPERATIONS

Byte Data

Authorization

Code

STX

Call

Start

Time

Authoriza-

tion Code

Logical

RT No. 1

135

140

145

Month

Day

(Max. 16

digits)

205

210

215

FPC2

Hour

Minute

Second

Physical

RT No. 2

Logical

RT No. 2

FPC

(3 digits)

Incoming

Trunk

Information

Milli-Second

Year

Physical

Route No.

Condition C

Information

Note

Trunk No.

150

155

Call End

Time

220

225

Call

Metering

Month

Day

Logical

Route No.

Hour

Minute

ORIG (Note)

Called

Party

Information

(Station No.)

160

165

170

Second

Tenant

(3 digits)

230

235

240

Dial Code

(Max. 32

digits)

Dial Code

Milli-Second

STN No.

ATT CON

No.

RT/TK No.

(6 digits)

100

Account

Code

Automatic

Number

Indication

(Max. 32

digits)

105

110

115

FPC

(3 digits)

Automatic

Number

Indication

175

180

185

Account

Code

(Max. 16

digits)

UserGroup

Number

(3 digits)

Note

245

250

255

Called

Party

Information

(Telephone No.)

Telephone

Number

(Max. 16

digits)

Office

Code of

Calling

Party

Condition

Information

120

125

Note

Logical

Route No.

(3 digits)

Office Code

Information

190

195

Office Code

of Billing

Process

Office

ETX

Incoming

Route

Number

FPC1

130

Note

Physical

RT No. 1

200

Year

For more information on the data to which the Note marks are attached, see Reference.

Figure 6-18 Message Format for Incoming Call - Fusion

CHAPTER 6

Page 418

Issue 1

NDA-24300

SYSTEM OPERATIONS

Byte Data

(3 digits)

Byte Data

STX

135

140

145

Called

Party

Information

(Telephone No.)

Telephone

Number

(Max. 16

digits)

Calling

Party

Information

(Station No.)

ORIG (Note)

Condition B

Information

Note

Tenant

(3 digits)

ETX

STN No.

ATT CON

No.

(6 digits)

Call

Start

Time

Year

Calling

Party

Information

(Telephone No.)

FPC

(3 digits)

Month

Day

UserGroup

Number

(3 digits)

Hour

Minute

Second

100

Telephone

Number

(Max. 16

digits)

Milli-Second

Year

105

110

115

Call End

Time

Month

Day

Hour

Minute

ORIG (Note)

Called

Party

Second

Tenant

Information

(Station No.)

(3 digits)

Milli-Second

120

125

STN No.

ATT CON

No.

(6 digits)

Account

Code

FPC

Account

Code

(Max. 16

digits)

130

(3 digits)

UserGroup

Number

For more information on the data to which the Note marks are attached, see Reference.

Figure 6-19 Message Format for Station-to-Station Call - Fusion

NDA-24300

CHAPTER 6

Page 419

Issue 1

SYSTEM OPERATIONS

Reference

Data = 02: Calling Party Information (Station Number)

Station No.

ATTCON No.

RT / TK No.

(6 digits)

Tenant

(3 digits)

ORIG:

Originating Source Identification

ORIG = 0:

ORIG = 1:

ORIG = 2:

Transmitted data depicts information on Station

Transmitted data depicts information on Attendant Console

Transmitted data depicts information on Trunk

Data = 08: Condition B Information

C0 =

0: Call Origination - Direct

1: Call Origination - via ATTCON

2: Call Origination - Direct (Alternate Routing)

3: Call Origination - via ATTCON (Alternate Routing)

4: Call Origination - Direct (LCR Routing)

5: Call Origination - via ATTCON (LCR Routing)

6: Call Origination - Direct (Called No. - first 6 digits of change code)

7: Call Origination - via ATTCON (Called No. - first 6 digits of change code)

C1 =

1: Call Origination by OG Queuing

2: Call Origination by dialing with accounted code

3: Call Origination by OG Queuing & dialing with accounted code

4: Call Origination by Call Forwarding Outside

6: Call Origination by Call Forwarding Outside & dialing with accounted code

C2 =

1: Call was transferred

2: Billing is continued

3: Call was transferred & billing is continued

4: Call was transferred to last called party

CHAPTER 6

Page 420

Issue 1

NDA-24300

SYSTEM OPERATIONS

Data = 09: Alternate Routing Information (KK) / Incoming Route Number (KL)

FPC1

Physical

Logical

FPC2

Physical

Logical

(3 digits) RT No. 1 RT No. 1 (3 digits) RT No. 2 RT No. 2

FPC1:

FPC actually used

Physical Route No. 1:

Logical Route No. 1:

FPC2:

Physical route actually used

Logical route actually used

FPC first selected

Physical Route No. 2:

Logical Route No. 2:

Physical route first selected

Logical route first selected

Data = 13: Condition C Information + Billing Info / Call Metering Info.

•

Billing Info

Call Metering

Charge Data (Basic Charge Unit x 10 )

Charge Data (Basic Charge Unit x10 )

In case of

Billing Information

Charge Data (Basic Charge Unit x10 )

0: No Charge Information

1: Charge Information for 1 cent unit

2: Charge Information for 0.1 cent unit

3: Charge Information for 10 cent unit

4: Charge Information for $1 unit

5: Charge Information for $10 unit

6: Calling Metering (4 digits)

F: Charge Information Error

NDA-24300

CHAPTER 6

Page 421

Issue 1

SYSTEM OPERATIONS

Data = 14: Condition D Information + Bill Notification ATT CON Number

Bill

•

Notification

ATTCON

Number

D -

Bill Notification (by ATTCON) Not Available

0 : Bill Notification (by ATTCON) Not Applied

1 : Bill Notification (by ATTCON) Available

Data = 16: Automatic Number Indication

Automatic Number Indication (Max. 32 digits)

* Information Element Identifier =

0: Unable to Output

1: Display

2: Unable to Notify

3: Out of Service (Out of Area)

4: Public Telephone Origination

CHAPTER 6

Page 422

Issue 1

NDA-24300

SYSTEM OPERATIONS

7.2.10 Text Format of SMDR - TCP/IP Interface

When using SMDR - TCP/IP interface, billing information is output to the billing output devices con-

nected by an external LAN in the form of socket interface as shown in Figure 6-20.

PBX(Server)

Billing Information

LAN

SMDR(A)

(Client)

SMDR(B)

(Client)

SMDR(C)

(Client)

SMDR(D)

(Client)

Note: A maximum of 4 clients can be designated as SMDR equipment for each LN.

Figure 6-20 SMDR—TCP/IP Interface Billing Output Devices

Details on the text format for SMDR - TCP/IP Interface are explained below.

(1) Identifier 1: Data Request Text

A text to be sent by the client when it requests the server to send billing data.

Text

identifier

(1)

Data length

(00002)

Device

No.

Parity

Text sending direction: Client

Server

NDA-24300

CHAPTER 6

Page 423

Issue 1

SYSTEM OPERATIONS

(2) Identifier 2: Sending Data Text

A text for sending billing data in response to “(1) Data Request Text” from the client.

Text

identifier

(2)

Data length

(XXXXX)

Billing data

(IPX Format)

Sequence

No.

Device

No.

Parity

Note

Note: Text format of billing data is IPX format only. (Refer to Section 7.2.9, T ext Format

of Centralized Billing - Fusion.)

Text sending direction: Client

Server

The number of billing data records is 64 or less.

(3) Identifier 3: Server Response Text

A text to be sent to the client when there is no billing data to send in response to “(1) Data RequestText”

or as a response to a “(5) Status Monitoring Text.”

Text

identifier

(3)

Data length

(00003)

Device Response

No.

Parity

Text sending direction: Client

(4) Identifier 4: Client Response Text

Server

A response text to be sent to the server by the client which has received the data by a “(2) Sending Data

Text.”

Text

identifier

(4)

Data length

(00002)

ACK/

NAK

Device

No.

Se-

quence

No.

Parity

Text sending direction: Client

Server

CHAPTER 6

NDA-24300

Page 424

Issue 1

SYSTEM OPERATIONS

(5) Identifier 5: Status Monitoring Text

A text for use in monitoring the server status from the client’s viewpoint or the client from the server’s

viewpoint. At the same time, the text is used to notify the server of the client status.

Client

device

information

Text

identifier

(5)

Data length

(00005)

ACK/

NAK

Device

No.

Parity

Text sending direction: Client

Server

(6) Identifier 6: Connection Disconnect Text

A text to be sent from the client to the server to disconnect the connection. In response to this text, the

server promptly performs processing to disconnect the connection.

Text

identifier

(6)

Data length

(00003)

ACK/

NAK

Device

No.

Parity

Text sending direction: Client

Server

8. TRAFFIC MANAGEMENT

To obtain the value of common equipment usage, the system provides traffic measurement feature. It can im-

prove the system efficiency.

8.1 Kind ofTraffic Measurement

Table 6-5 shows the kinds of traffic measurements.

Table 6-5 Traffic MeasurementTypes

KIND OF

TYPE

DESCRIPTION

MEASUREMENT

Terminal Traffic

Measurement

Measurement of traffic on a per LENS basis, and measurement of the total traffic on

a PIM basis.

Route Traffic

Measurement

Measurement of traffic on a per route basis.

Station Peg Count

Measurement of the number of outgoing connections, intra-office calls, outgoing

C.O. line calls, Tie Line calls, etc. originated by each station.

NDA-24300

CHAPTER 6

Page 425

Issue 1

SYSTEM OPERATIONS

Table 6-5 Traffic MeasurementTypes (Continued)

DESCRIPTION

KIND OF

TYPE

MEASUREMENT

ATTCON Peg Count

Measurement of the number of each type of call handled at theATTCON/

DESKCON.

Route Peg Count

Service Peg Count

Measurement of the number of various types of call connections on a per route basis.

Measurement of the number of times the following services are operated:

Call Hold

Call Back

Executive Right of Way

Call Waiting

Call Pickup - Group

Call Pickup - Direct

Call Forwarding - All Calls

Call Forwarding - Busy Line

Call Forwarding - Don’t Answer

Speed Calling - System

Speed Calling - Station

Off-Hook Outgoing Trunk Queuing

Outgoing Trunk Queuing

Consultation Hold - All Call

Call Transfer - All Calls

Three-Way Calling

UCD Route Peg Count

UCD Group Peg Count

UCD Station Peg Count

ATT Answer Peg Count

Measurement of the number of incoming calls, answered calls, and abandoned calls

handled at UCD Groups on a per route basis.

Measurement of the number of incoming calls, answered calls and abandoned calls

on a UCD Group basis.

Measurement of the number of incoming calls, answered calls and abandoned calls

for each station on a UCD Group basis.

Measurement of the number of answered calls handled by each attendant.

Connection Route Peg

Count

Measurement of the number of various type of call connection on a connection route

basis.

Connection Route Traffic Measurement of traffic on a connection route basis.

Note: Asterisk (*) identifies the traffic measurements that can be saved on the HD of the MAT.

CHAPTER 6

NDA-24300

Page 426

Issue 1

SYSTEM OPERATIONS

8.2 Operating Procedure

Procedure for Set-up and Start

The procedure to set up and start the traffic measurement is as follows:

STEP 1

By using the ASYD/ASYDN command, assign the necessary system data as follows:

When performing traffic measurement on a node basis:

• SYS1, INDEX8 (Number of Tenants)

ASYD

• SYS1, INDEX9 (Number of Attendant Consoles)

• SYS1, INDEX47, bit 0 (Unit of Traffic Measurement): 0/1 = CCS/Erlang

• SYS1, INDEX47, bit 7 (Traffic Measurement Service): 0/1 = Out/In Service

Assign “1.”

When performing traffic measurement on a network basis (via TCP/IP):

• SYS1, INDEX8 (Number of Tenants)

ASYDN

• SYS1, INDEX9 (Number of Attendant Consoles)

• SYS1, INDEX47, bit 0 (Unit of Traffic Measurement): 0/1 = CCS/Erlang

• SYS1, INDEX47, bit 7 (Traffic Measurement Service): 0/1 = Out/In Service

Assign “1.”

STEP 2

ATRF

By using the ATRF/ATRFN command, assign the traffic measurement programs as follows:

When performing traffic measurement on a node basis:

Assign traffic measurement “TYPE” (Note), “PORT” number to be used, and the output

“INTERVAL” and “Time (HOUR/MINUTE),” etc. For more details, see the A T RF command in

CHAPTER 8.

When performing traffic measurement on a network basis (via TCP/IP):

Assign traffic measurement “TYPE” (Note), “PORT” number to be used, and the output “INTER-

VA L ” and “Time (HOUR/MINUTE),” etc. For more details, see the A T RF command in CHAP-

TER 8.

ATRFN

Note:

You can select one measurement “TYPE” at a time. If you need two or more measurement

“TYPE,” repeat the same steps, following the entry of this command.

STEP 3: Terminate all the MAT commands.

An image of IPX “MAT Menu” is shown in Figure 6-21. Terminate all MAT commands, and

make sure no commands are currently running via the “Processes” button.

STEP 4: Set the programmed Traffic Measurement in routine operation.

Click the “Scan New Alarms/Traffic” and “Collect New Alarms” buttons on the IPX “MAT

Menu” (confirm the clicked buttons remain in the pressed state). Then, the Traffic Measurement is

activated as programmed.

END

NDA-24300

CHAPTER 6

Page 427

Issue 1

SYSTEM OPERATIONS

Figure 6-21 shows the IPX “MAT Menu” display image. The display should look similar to the following:

Scan New Alarms/Traffic

Office Name (assigned by ASYD/AOFC command

Collect New Alarms

Collect New Traffic

Major Alarm Indicator

Abort Data Collections

Minor Alarm Indicator

View Scanning Log

Supervisory Message Indicator

Traffic Data Indicator

About

Log Manager

Log out

Configure

Processes

Command Name Input Text Box

Figure 6-21 IPX “MAT Menu” Display Image (Example)

CHAPTER 6

Page 428

Issue 1

NDA-24300

SYSTEM OPERATIONS

(2) Data Output - Details on DTFD/DTFDN Command

To obtain the collected Traffic data, you can use the “DTFxxx” or “DTFxxxN” command as shown below.

The commands can be activated by your direct log-in operation onto the MAT, but in normal cases, the com-

mands are to be activated automatically at predetermined intervals assigned by the ATRF/ATRFN command.

Also, each command below corresponds to the Traffic Measurement “TYPE” assigned by the ATRF/ATR-

FN command.

When performing traffic measurement on a node basis:

Measurement “TYPE”

(by ATRF Command)

Command

Name

Full Command Name

Display of Terminal Traffic Data

Terminal Traffic

DTF101

DTF102

DTF103

DTF104

DTF105

DTF201

DTF301

DTF302

DTF303

DTF501

DTF601

DTF602

Route Traffic

Display of Route Traffic Data

Station Peg Count

ATTCON Peg Count

Route Peg Count

Display of Station Peg Count Data

Display of Attendant Peg Count Data

Display of Route Peg Count Data

Service Peg Count

UCD Route Peg Count

UCD Group Peg Count

Display of Service Peg Count Data

Display of UCD Route Peg Count Data

Display of UCD Group Peg Count Data

Display of UCD Station Peg Count Data

Display of Attendant Answering Peg Count Data

Display of Connection Route Peg Count Data

Display of Connection Route Traffic Data

10 UCD Station Peg Count

15 ATT Answer Peg Count

18 Connection Route Peg Count

19 Connection Route Traffic

When performing traffic measurement on a network basis (via TCP/IP):

Measurement “TYPE”

(by ATRFN Command)

Command

Name

Full Command Name

Terminal Traffic

DTF101N Display of Terminal Traffic Data for Fusion Network

DTF102N Display of Route Traffic Data for Fusion Network

Route Traffic

Station Peg Count

ATTCON Peg Count

Route Peg Count

DTF103N Display of Station Peg Count Data for Fusion Network

DTF104N Display of Attendant Peg Count Data for Fusion Network

DTF105N Display of Route Peg Count Data for Fusion Network

DTF201N Display of Service Peg Count Data for Fusion Network

DTF301N Display of UCD Route Peg Count Data for Fusion Network

DTF302N Display of UCD Group Peg Count Data for Fusion Network

DTF303N Display of UCD Station Peg Count Data for Fusion Network

DTF501N Display of Attendant Answering Peg Count Data for Fusion Network

DTF601N Display of Connection Route Peg Count Data for Fusion Network

DTF602N Display of Connection Route Traffic Data for Fusion Network

Service Peg Count

UCD Route Peg Count

UCD Group Peg Count

10 UCD Station Peg Count

15 ATT Answer Peg Count

18 Connection Route Peg Count

19 Connection Route Traffic

Note: For information on the command display images, see Figure 6-22, Figure 6-23, and Figure 6-24.

NDA-24300 CHAPTER 6

Page 429

Issue 1

SYSTEM OPERATIONS

Figure 6-22 shows the DTFD command display image (example). The DTFD/DTFDN command should look

similiar to this.

Data collecting Log

This area displays the current Traffic

Measurement data, based on the selected

“Traffic Data” TYPE.

Traffic Data

Check box to specify the “Traffic Data”

TYPE.

Tool Buttons

•

Collect Data

Used to collect the Traffic report with regard to the selected “Traffic Data” TYPE. The result test is shown in

the “Data Collection Log” display area.

•

Stop

Used to quit the currently performedTraffic Data collection.

Print Log

Used to print out the text data now displayed in the “Data Collection Log” area

View Database

Used to view the whole data (based on the selected “Traffic Data” TYPE), so far stored in the database. More

details are shown in figure 6-11-3.

•

Clear Database

Used to delete (clear) the whole data (based on the selected “Traffic Data” TYPE), so far stored in the data-

base.

•

Log Colors

Used to designate/change the text font color of the “Data Collection Log” display area.

Exit

Used exit this command. (Note that the database contents are not cleared by pressing this button.)

Figure 6-22 DTFD Command Display Image (Example)

NDA-24300

CHAPTER 6

Page 430

Issue 1

SYSTEM OPERATIONS

Figure 6-23 shows a sample image of the “Listup Report” window for the DTFD/DTFDN command. This window appears by taking

the following operations, and is used to obtain a sequence of Traffic data, so far collected and stored in the database. The window is

also used to save the Traffic data text (now displayed in the window) onto your desired PC directory.

- To activate this window:

1. Designate a specific “Traffic Data” TYPE out of the DTFD/DTFDN command check boxes. (see Figure 6-22).

2. Press the “View Database” button on the left-bottom part of the DTFD/DTFDN command (see Figure 6-22).

Listup Report

[

TROUBLE :: DTFA

]

ABCDE

Terminal Traffic Data (DTF101) *

Display Area

Start Time:

End Time:

12/25 12:00

12/25 13:00

This area displays the details

on the Traffic report, specified

by the “Page (UP)/Page

(DOWN)” buttons.

Shown here is an example of a

certain first page of “Terminal

Traffic Data (DTF101).”

Module Group Unit

G roup

Type

Level

CCS

09252.000

09215.859

09179.718

09143.576

09107.435

09071.294

09035.153

08999.012

69 of 69

Total: 69

100%

Cancel

Save Text File

When saving the currently displayed text page, press this button.

Then, a dialog box, as shown in Figure 6-24, appears.

Page (UP)

Page (DOWN)

Any Traffic data, now in the database, can easily be found via these buttons. Select “UP” or

“DOWN,” according to the text display pattern: “the newest the first, the oldest the last.”

tion 12.1.2, How to Control CPU Block.

Note: When this window is activated, the initial text to appear is the newest file data, out of a sequence of Traffic reports. Like

this, the newest text (in the database) appears on the first page, and the next new, the next page.

Figure 6-23 “Listup Report” Window when “View Database” is Selected (Example)

The dialog box, as shown below, appears, if the “SaveText File” button is selected on the “Listup Report” window

(see Figure 6-23 above). If the file is to be saved:

E xport

1. Select “Character-separated values” on the “Format”

Form at:

D estination:

D isk file

list box.

Character separated values

2. Select “Disk file” on the “Destination” list box.

C ancel

O K

3. Click OK.

After these steps, a new dialog, asking the saved file name and directory, also appears. Then, complete the data saving by

filling out these necessary items.

Figure 6-24 “Export” Dialog for Traffic Report Text File Saving

NDA-24300

CHAPTER 6

Page 431

Issue 1

SYSTEM OPERATIONS

(3) Service Conditions (when performing Traffic Measurement via TCP/IP)

(a) The NDM (network-level) data for the traffic measurement order is replaced/updated, at each time

the system is initialized or data change is requested from theATRFN command.

(b) When the network-level data is once assigned via the ATRFN command, the node-level data for

ATRF command cannot be changed or modified.

by the ATRF command is not cleared, but becomes ineffective.

(d) When a data transfer error occurs, the following are performed in order:

Traffic measurement is suspended momentarily and system message is displayed (notification

of fault)

Traffic measurement, concerning all the remaining data except for the fault-involved one, is re-

sumed

Retry is made repeatedly for the transfer of fault-involved data, until the fault has been eradicat-

If the fault hasn’t been eradicated still until the time of next measurement routine, the data is

finally discarded, and next traffic measurement routine starts

(e) When the same Individual ATT Numbers exist on the network, the traffic measurement concerning

the ATTCON/DESKCON cannot be performed correctly.

CHAPTER 6

Page 432

Issue 1

NDA-24300

SYSTEM OPERATIONS

9. OFFICE DATA MANAGEMENT

This section explains how to manage various kinds of data such as Call Forwarding Data, Individual Speed

Calling Data, and Office Data, etc.

9.1 Office Data Stored Locations

The office data is stored in the memory (MEM) and on the Hard Disk (HD). While the system is in service,

it operates by the office data stored in the memory. Should the contents of the office data be destroyed due

to trouble, the system restarts its operations by loading the office data from the hard disk into the memory.

The office data of the system in operation is being backed up by the hard disk.

9.2 Office Data Preservation

Since the PBX keeps operating by the assigned office data, be sure to preserve the latest office data. If the

office data is not preserved, all office data must be reassigned if the contents of the data memory have been

destroyed, because of trouble occurrence, etc. The system will remain in a system down state until reas-

signment of the office data is complete.

Practice to verify and confirm the valid office data by routine maintenance is considered an effective

means to prevent loss of the office data and occurrence of trouble due to the office data. For this reason,

be sure to keep the following items near the system at all times so that they may be available when needed.

(1) Office Data Programming Sheets

As the most up-to-date data must be recorded in the sheets, be sure to make entries by pencil.

(2) Floppy Disks for Data Saving

To back up the office data stored on the HD, use floppy disks. The necessary number of Floppy Disks (FD)

is determined by the following factors:

•

Mounting capacity of office data depends upon the system data (SYS1, Index30).

Each floppy disk can save 1MB of data. After a large-scale office data change, in particular which

includes system data, unpredictable failures might occur. To deal with such failures, prepare an FD

for saving the office data before the changing. In addition, prepare an FD for saving the latest office

data.

NDA-24300

CHAPTER 6

Page 433

Issue 1

SYSTEM OPERATIONS

9.3 Office Data Management Procedure

The procedure generally taken when changing the office data is shown below.

CREATION OF DATA CHANGE PLAN

DATA CHANGING

Entry Into Office Data Programming Sheets

LISTING OFFICE DATA

Entry Into Office Data Programming Sheets

MEM_HDD command Note

Direction Select : Memory to Hard Disk

Data Type Select : Data Memory, etc.

DATA SAVE FROM MEM INTO HDD

MEM_HDD command Note

Direction Select : Verify HDD against MEM

Data Type Select : Data Memory, etc.

DATA VERIFY

HDD_M A T command Note

DATA SAVE FROM HDD INTO FD

Direction Select : PBX Hard Disk to MAT

Data Type Select : Data Memory, etc.

HDD_M A T command Note

Direction Select : Verify HDD against MAT

Data Type Select : Data Memory, etc.

DATA VERIFY

Note: Refer to Figure 6-29 for each command function.

Figure 6-25 Office Data Change Procedure

CHAPTER 6

Page 434

Issue 1

NDA-24300

SYSTEM OPERATIONS

CREATION OF DATA CHANGE PLAN

DATA CHANGING

Entry Into Office Data Programming Sheets

LISTING OFFICE DATA

Entry Into Office Data Programming Sheets

MEM_HDD command Note

Direction Select : Memory to Hard Disk

Data Type Select : Data Memory, etc.

DATA SAVING FROM MEM INTO HDD

DATA VERIFICATION

MEM_HDD command Note

Direction Select : Verify HDD against MEM

Data Type Select : Data Memory, etc.

HDD_FDD command Note

DATA SAVING FROM HDD INTO FD

DATA VERIFICATION

System Select

: HFD0/HFD1

Direction Select : Hard Disk to Floppy Disk

Data Type Select : Data Memory, etc.

HDD_FDD command Note

System Select

: HFD0/HFD1

Direction Select : Verify HDD against FDD

Data Type Select : Data Memory, etc.

Note: Refer to Figure 6-27 for each command function.

Figure 6-26 Office Data Change Procedure

NDA-24300

CHAPTER 6

Page 435

Issue 1

SYSTEM OPERATIONS

Figure 6-27 shows the function of three backup commands: HDD to FDD, HDD to MAT, and MEM to

HDD.

PBX

NEAX 2400 IMS

NEC

MEM

M M E E M M __H H D D D D

HDD_M A T

MAT

HDD_MAT

NDM

LDM

RCF

SPD

USK

NDM

LDM

RCF

SPD

USK

HDD

CBK

HDD_FDD

FDD

NDM

LDM

RCF

SPD

USK

HDD

FDD

DM:

Data Memory

CBK

NDM: Network Data Memory

LDM:

ND:

Local Data Memory

Name Display Data

RCF:

CF:

Wireless Call Forwarding Data

Call Forwarding Data

SPD:

USK:

NS:

Speed Calling-System Data

User Assign Soft Key Data (for Release 3 or later)

Number Sharing Data (for Release 3 or later) Note

Call Block Data (for Release 5 or later)

: Command

CBK:

Note: Number Sharing data load/backup also affects the data load/backup of Dual Station Calling

Over-FCCS.

Figure 6-27 Backup Commands

CHAPTER 6

NDA-24300

Page 436

Issue 1

SYSTEM OPERATIONS

9.4 Call Forwarding Data/Individual Speed Calling Data Management

Call Forwarding Data and Individual Speed Calling Data are changed at any time because these services

are set/cancelled from the station involved. In the PBX, these data are backed up by FD.

Call Forwarding Data:

HDD_MAT command

Individual Speed Calling Data: HDD_MAT command

9.5 One-Touch Speed Call Memory Data Management

term

One-Touch Speed Call Memory data of D

is destroyed when DLC/ELC circuit card has been replaced

with a spare or its mounting slot has been changed. The data can be backed up onto FD before replacement

or mounting slot change of DLC/ELC card.

Backup:

BOSD command

9.6 Data Management Commands

COMMAND

COMMAND FULL NAME

BOSD

One-Touch Speed Call Memory Data Backup

Data Control Between HDD and FDD

Data Control Between HDD and MAT

Data Control Between Memory and HDD

HDD_FDD

HDD_M A T

MEM_HDD

NDA-24300

CHAPTER 6

Page 437

Issue 1

SYSTEM OPERATIONS

10. TEST OPERATIONS OF VARIOUS KINDS

This section explains the methods of test operations (shown in Figure 6-28) to be performed in case a fault

recovery occurs.

Display of connection status of designated station/trunk

COMMAND

COMMAND FULL NAME

DCON

Display of Connection Status

Test connection by designating trunks, tones, and ringback tone from test station

10.1 Designated Connection Test (Station)

Test connection by designating trunks (outgoing only) from Attendant/Desk Console

10.2 Designated Connection Test (ATTCON/DESKCON)

Display of line failure indication when faulty condition occurred while a call is in progress

10.3 Bad Call Notification

Figure 6-28 Test Operation Method Examples

CHAPTER 6

Page 438

Issue 1

NDA-24300

SYSTEM OPERATIONS

10.1 Designated Connection Test (Station)

(1) General

The purpose of this test is to confirm the operations related to a trunk or tone that is designated from the

test station. Refer to Table 6-6. The test result displays on the MAT screen as system message [6-I].

Table 6-6 Designated Connection Test (Station) Operations

ITEM

TEST ITEM

CONTENT OF CONFIRMATION

REMARKS

received correctly is to be confirmed.

Sender

Whether the numbers (1, 2, 3, 4, 5, 6, 7, 8, 9, 0, *, #) can all be sent out

is to be confirmed.

3-Party Conference By connecting the test tone to each port of a 3-Party Conference Trunk,

Trunk

whether the test tone can be heard is to be confirmed.

Tone

Various kinds of tone are to be confirmed.

Interrupted Ringing Interrupt ringing (IR) is to be confirmed.

(IR)

Trunk

Connections of trunks are to be confirmed.

(2) Precaution

Designated connection to a trunk—A designated connection to trunk is limited only to an individual line

of either 2nd DT system or sender system.

NDA-24300

CHAPTER 6

Page 439

Issue 1

SYSTEM OPERATIONS

(3) Designated Connection Test Procedure

(a) Register Test Procedure

Lift handset

(DT)

Dial access code for

designated connection

•

Access code is assigned by ASPA command, CI=N,

SRV=SSC, SID=17

“9xx

“xxx”

Route numbers to be designated are as follows.:

RT No.

TRK No.

RT NUMBER

TRUNK NAME

902

Originating Register Trunk

(DT)

903

Incoming Register Trunk

Dial “1,2,3,4,5,6,7,8,9,0” (*, #

in case of PB signal)

consecutively

•

If any of the dialed numbers are not received correctly, a

Reorder Tone (ROT) is heard.

₍SST₎

(NO)

Hang Up

Is next register to

be tested, too?

TRUNK DESIGNATION

TEST IN PROGRESS

(YES)

UNDER TEST

ORT

Make switch hook flash

Note

Note: If the trunk number of the next register is not assigned, the test ends.

Figure 6-29 RegisterTest Procedure/Connection Diagram

CHAPTER 6

Page 440

Issue 1

NDA-24300

SYSTEM OPERATIONS

(b) Sender Test Procedure

Lift handset

(DT)

Dial access code for

designated connection

•

Access code is assigned by ASPA command, CI=N,

SRV=SSC, SID=17

“9xx”

“xxx”

Route number to be designated is as follows:

RT No.

TRK No.

RT NUMBER

TRUNK NAME

Sender Trunk DP/PB

905

Connection test is automatically

(Music On Hold)

(SST)

performed Note 1

•

If any of the dialed numbers are received correctly, a Reorder

Tone (ROT) is heard.

Is next

tested, too?

Hang Up

YES

TRUNK DESIGNATION

TEST IN PROGRESS

MUSIC ON

HOLD

Make switch hook flash

Note 2

ORT

SND

OR PB

Note 1: After the sender to be tested is connected to the register, the sender sends out 1 ~ 9, 0 by DP

signals and 1 ~ 9, 0, *, # by PB signals, thus checking to see if the dialed numbers are sent out

correctly.

Note 2: If the trunk number of the next sender is not assigned, the test ends.

Figure 6-30 Sender Test Procedure/Connection Diagram

NDA-24300

CHAPTER 6

Page 441

Issue 1

SYSTEM OPERATIONS

Lift handset

(DT)

Dial access code for

designated connection

• Access code is assigned by ASPA command, CI=N,

SRV=SSC, SID=17

• Route numbers to be designated are as follows:

“9xx”

“xxx”

RT No.

TRK No.

RT NUMBER

TRUNK NAME

3-party conference trunk

(for station, ATTCON, trunk)

909

(SST)

3-party conference trunk

(only for ATTCON)

913

As shown in Figure 6-32,

tone sending is repeated.

(SST)

Is next

tested, too?

Hang Up

YES

Make switch hook flash

Note

Note: If the trunk number of the next 3-Party Conference Trunk is not assigned, the test ends.

Figure 6-31 3-Party Conference Test Procedure

CHAPTER 6

NDA-24300

Page 442

Issue 1

SYSTEM OPERATIONS

TRUNK DESIGNATION

TEST IN PROGRESS

1 SEC.

ORT

SST

TSTT

(DT)

TSTT

(SST)

TSTT

(DT)

1 SEC.

TSTT

(SST)

TSTT

(DT)

TSTT

(SST)

Figure 6-32 3-Party Conference Test Connection Diagram

NDA-24300

CHAPTER 6

Page 443

Issue 1

SYSTEM OPERATIONS

(d) Tone Test Procedure

Lift handset

(DT)

Dial access code for

designated connection

•

Access code is assigned by ASPA command, CI=N, SRV=SSC,

SID=17

Dial “000”

(DT)

Dial “x x”

•

For Tone No. to be designated, refer to T a ble 6-7.

Tone designated by Tone No. is heard.

Tone Number

(Tone)

Hang Up

TRUNK DESIGNATION

TEST IN PROGRESS

TONE

ORT

Figure 6-33 Tone Test Procedure/Connection Diagram

CHAPTER 6

NDA-24300

Page 444

Issue 1

SYSTEM OPERATIONS

REMARKS

Table 6-7 Tone Numbers

KIND OF TONE

TONE NO.

Dial Tone (DT)

Special Dial Tone (SPDT)

Ring Back Tone (RBT)

Continuous Ring Back Tone (CRBT)

Busy Tone (BT)

Reorder Tone (ROT)

Service Set Tone (SST)

Second Dial Tone (SDT)

No Tone

Sender Transmitting Tone (SDTT)

Call Waiting Ring Back Tone (CWRBT)

No Tone

Test Tone (TSTT)

Music On Hold (MSC)

No Tone

NDA-24300

CHAPTER 6

Page 445

Issue 1

SYSTEM OPERATIONS

(e) Interrupt Ringing (IR) Test Procedure

Lift handset

(DT)

Dial access code for

designated connection

•

Access code is assigned by ASPA command, CI=N, SRV=SSC,

SID=17

Dial “999”

(SST)

Hang Up

Bell Rings

Lift handset and answer

(SST)

Hang Up

DESIGNATION

TEST IN PROGRESS

ANSWER

SST

HANGUP

SST

ORT

Figure 6-34 Interrupt Ringing (IR)Test Procedure/Connection Diagram

NDA-24300

CHAPTER 6

Page 446

Issue 1

SYSTEM OPERATIONS

(f) Trunk Test Procedure

Lift handset

(DT)

Dial access code for

designated connection

•

Access code is assigned by ASPA command, CI=N,

SRV=SSC, SID=17

“9xx”

“xxx”

RT No.

TRK No.

Dial the called party

number

(RBT)

The called party at the

distant office answers

and talks

Is next

Hang Up

tested, too?

YES

Make switch hook flash

Note

Note: If the trunk number of the next trunk is not assigned, the test ends.

Figure 6-35 Trunk Test Procedure

NDA-24300

CHAPTER 6

Page 447

Issue 1

SYSTEM OPERATIONS

TRUNK DESIGNATION

CALLED PARTY DIALING

2nd DT SYSTEM

SENDER

SYSTEM

ORT

CHARGING SERVICE

PROVIDED

TRK

ORT

CALLED PARTY DIALING

NUMBER SENDING

SND

TRK

ORT

Figure 6-36 Trunk Test Connection Diagram

CHAPTER 6

Page 448

Issue 1

NDA-24300

SYSTEM OPERATIONS

10.2 Designated Connection Test (DESKCON/ATTCON)

(1) General

The purpose of this test is to confirm the operations related to a trunk which has been designated from the

Desk/Attendant Console (DESKCON/ATTCON).

(2) Test Procedure

(a) Trunk seizure with TKSL key

Press TKSL or TRKSL key

“xxx”

•

Whether dialing RT No. + TRK No.

RT No.

TRK No.

Dialing C.O. Line NO. is determined per ASYD

command, SYS1. INDEX68. b1.

“xxxx”

C.O. Line No. is assigned by ACOC command.

C.O. Line NO.

(DT from Distant Office)

Dial called party

number

(RBT)

Called party at distant

office answers and talks

Press CANCEL key

NDA-24300

CHAPTER 6

Page 449

Issue 1

SYSTEM OPERATIONS

(b) Trunk seizure by access code dialing

Press LOOP key or Lx (L1-L6) key

Dial access code

for designated connection

• Special Code is assigned by ASPA command.

• CI=N, SRV=SSC, SID-17

Dial “xxxx”

• C.O. Line No. is assigned by ACOC command.

C.O. Line No.

(DT from distant office)

Dial called party number

(RBT)

Called party at the distant

office answers and talks

Press CANCEL key

CHAPTER 6

NDA-24300

Page 450

Issue 1

SYSTEM OPERATIONS

10.3 Bad Call Notification

(1) General

When a station user has trouble because of hearing noise during a call, or has other difficulty having a

normal call, the line involved is recorded as a bad call notification.

The record displays on the MAT screen as system message [6-H], which indicates the recording source

(Station Number), Called Station Number or Trunk Number, etc.

(2) Operating Procedure

• SFC of the station user who can perform this operation must

be allowed ASFC, SFI=46

Talking

• SFC of the station user who can perform this operation must

be allowed ASFC, SFI=46

Switch hook flash

(SPDT)

• Access code is assigned by ASPA command, CI=H,

SRV=SSC, SID=46

Dial access code for

bad call notification

(SST)

System message [6-H] displays

Station user returns

to talking state

NDA-24300

CHAPTER 6

Page 451

Issue 1

SYSTEM OPERATIONS

11. ROUTINE DIAGNOSIS

For confirming its own servicing status, the system automatically executes self diagnosis every day, and dis-

plays the result of the diagnosis on a system message. By this function, possible causes for trouble can be dis-

covered in an early stage and possible trouble can be prevented from remaining undetected.

11.1 Related System Data

•

ASYD, SYS1, INDEX86,

b0 –

When routine diagnosis starts, and the result of the routine diagnosis is normal, the result

displays as system message [7-O].

0/1: Not displayed/To display

b1 –

When the result of the routine diagnosis is abnormal, it displays as system message [7-P].

0/1: Not displayed/To display

b3, b2 – Processing at the time when Trunk Ineffective Hold is detected. Note

Except the trunks being held on two-way calls All trunks being held at

(station-to-station call, station-to-trunk, trunk- present are forcibly

LENS of the trunk detected

display as system message

[7-P]

Bit

to-trunk call), the trunks being held at present

are forcibly released

released

—

Note: Trunk Ineffective Hold is a continuous state other than idle state within a predetermined duration while

routine diagnosis is in progress. Whether it is to be detected/not detected is assigned by ASYD, SYS1,

INDEX89.

•

SYS1, INDEX87, 88 - Routine Diagnosis Start Time

Start time should be such a time at which the traffic of the office is the lowest.

INDEX 87 0

INDEX 88 0

(Hour)

2:00 a.m. is the start time.

(Minute)

To stop the routine diagnosis, set FF respectively to INDEX87, 88.

CHAPTER 6

Page 452

Issue 1

NDA-24300

SYSTEM OPERATIONS

•

SYS1, INDEX89, 90 — Routine Diagnosis Items: The item corresponding to each bit is to execute

once a day.

Single System Configuration

INDEX89

b0 — Main Memory Check (MM Program Memory)

0/1 = No/Yes

b1 — DM Check (DM = Data Memory)

0/1 = No/Yes

b4 — Trunk Ineffective Hold Check

0/1= No/Yes

b5 — Trunk Ineffective Hold Detection

0/1 = No/Yes

INDEX90

b1 — Backup of Call Forwarding, Individual Speed Data, Name Display Data, User

Assign Soft Key Data and Number Sharing Data to HDD (see Index 304)

0/1 = No/Yes

b3 — Residual Link Detection

0/1 = No/Yes

INDEX304 b0 — Individual Speed Calling Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

b1 — Call Forwarding Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

b3 — Name Display Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

b4 — User Assign Soft Key Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

b5 — Number Sharing Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

•

Dual System Configuration

INDEX89

b0 — Main Memory Check (MM Program Memory)

0/1 = No/Yes

b1 — DM Check (DM = Data Memory)

0/1 = No/Yes

b2 — TSW ACT/STBY Changeover for Dual Systems

0/1 = No/Yes

b3 — CPU ACT/STBY Changeover for Dual Systems

0/1 = No/Yes

b4 — Trunk Ineffective Hold Check

0/1 = No/Yes

b5 — Trunk Ineffective Hold Detection

0/1 = No/Yes

NDA-24300

CHAPTER 6

Page 453

Issue 1

SYSTEM OPERATIONS

b6 — Call Forwarding Data Clear (See Index 232)

0/1 = No/Yes

INDEX90

b1 — Backup Call Forwarding, Individual Speed Data and Name Display Data to

HDD (see Index 304)

0/1 = No/Yes

b3 — Residual Link Detection

0/1 = No/Yes

INDEX304 b0 — Individual Speed Calling Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

b1 — Call Forwarding Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

b3 — Name Display Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

b4 — User Assign Soft Key Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

b5 — Number Sharing Data Saving

0/1 = Out/In Service (This data is valid when SYS1, INDEX90, b1=1)

11.2 Routine Diagnosis Result

The result of routine diagnosis displays as a system message.

Normally ended:

[7-O]

Abnormality detected [7-P] Refer to Chapter 3 for more details.

In case an abnormality is detected, initiate necessary processing explained in Chapter 5.

CHAPTER 6

NDA-24300

Page 454

Issue 1

SYSTEM OPERATIONS

12. SYSTEM CONTROL PROCEDURES

Although the system is remarkably maintenance free, maintenance technicians occasionally may confront a

situation in which they have to manually control the system. This chapter describes system control procedures

focusing on the following four items.

•

Changeover/Make-busy/Make-busy Cancel of Equipment

Initialization

How to Turn On/Off the Whole System

System Start-up

Note: Changeover of equipment is available for common control equipment, which is provided in a dual con-

figuration.

12.1 Changeover/Make-Busy/Make-Busy Cancel of Equipment

12.1.1 General

This section explains system operations which are necessary for Changeover/Make-Busy/Make-Busy

Cancel of equipment dividing them into the following two blocks.

•

CPU Block

Switching Block (TSW, PLO)

Prior to performing these operations, see Figure 6-37 through Figure 6-47 to obtain general under-

standing on the system configuration.

Figure 6-37 shows a general block diagram of a dual-configuration system. Referring to the diagram,

confirm the routes to be affected by any of the following operations:

CPU Changeover:

The ACT/STBY of CPU can be changed over by using the CMOD com-

mand or operating the MBR key on the CPU front panel. If the system of

CPU is changed over, the ACT/STBY of GT (in TSWM), as well as of the

belonging ISAGT and LANI, are also changed over.

Note: The changeover of CPU can be performed by operating the CPU SEL key on the EMA (PH-PC40) card.

However, this method is not normally used except in cases of unavoidable circumstances. Refer to Sec-

Speech Path Changeover: The ACT/STBY of Speech Path System can be changed over by using the

CMOD command or operating the MBR key on the active GT circuit card.

If the system of Speech Path is once changeover, all the TSW, DLKC, and

MUX in the same switching block are also totally changed over.

NDA-24300

CHAPTER 6

Page 455

Issue 1

SYSTEM OPERATIONS

PLO Changeover:

Though PLO is included in the switching block together with the TDSW,

MUX, and DLKC, its ACT/STBY changeover should be performed inde-

pendently by operating the MB key on the card. The changeover of PLO

does not affect any other systems.

IMG0

IMG1

IMG2

IMG3

Line/Trunk PM

MUX MUX MUX MUX

MUX MUX MUX MUX MUX MUX MUX MUX

MUX MUX MUX MUX

TSW 10

TSW 00

TSW 11

TSW 12

TSW 13

TSW 03

TSW 01

TSW 02

TSW I/O BUS

DLKC 1

DLKC 0

PLO 1

PLO 0

GT 1

GT 0

CPR 1

ISAGT

CPU 1

CPR 0

ISAGT

CPU 0

LANI LANI

MISC BUS

EMA

IOC/

MISC

ISAGT: PZ-GT13

DLKC: PH-PC20

LANI: PZ-PC19

PLO: PH-CK16/17/16-A/17-A

GT: PH-GT09

EMA: PH-PC40

TSW: PH-SW12

IOC: PH-IO24

MUX: PH-PC36

Figure 6-37 Switching Network General Block Diagram

CHAPTER 6

NDA-24300

Page 456

Issue 1

SYSTEM OPERATIONS

To perform the ACT/STBY system changeover, check the lamp indicators shown in Figure 6-38, and

then operate the related key.

Note 1: LED indications cited in Figure 6-38 are only an example. The indicating pattern (ON/Flash/OFF)

can differ, depending on each system setting.

Note 2: STATUS 7-seg. LED provides information on ACT/STBY status of the belonging CPU. For details on

the LED’s checking method, refer Figure 6-41.

IMG0

TOPU

System State

13 14

CPU 0 -> ACT

MUX ACT

TSW 0 -> ACT

MUX

PIM3

MUX ACT

13 14

MUX ACT

PIM2

FANU

PIM1

FRONT

13 14

MUX ACT

13 14

MUX ACT

PIM0

DSP 1 (PZ-DK224)

..........

OPEOPE/MB

OFF

^EC

OFF

PZ-DK224

LPM

CPUOPE WDT IMG0

..........

MBR

OFF

IMG1 IMG2 IMG3

STATUS

OFF

^EC

OFF

Note 2

BASEU

DSP 0 (PZ-DK224)

OFF

^EC

OFF

FRONT VIEW

FRONT

Legend

: Lamp is ON

: Lamp is Flashing

: Lamp is OFF

Figure 6-38 How to Check LEDs and SW Keys for System Changeover (IMG0)

NDA-24300

CHAPTER 6

Page 457

Issue 1

SYSTEM OPERATIONS

To perform ACT/STBY system changeover, check the lamp indicators shown in Figure 6-39, and then

operate the related key.

Note: LED indications cited in Figure 6-39 are only an example. The indicating patterns (ON/Flash/OFF)

can differ, depending on each system setting.

IMG1

System State

TOPU

TSW 0 -> ACT

13 14

PLO 0 -> ACT

DLKC 0 -> ACT

MUX

PIM3

MUX ACT

13 14

PIM2

FANU

PIM1

FRONT

13 14

TSW

TSW ACT

OPE/MB

13 14

TSW MBR

MBR

PIM0

FRONT

PLO

FRONT

08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23

ACT

TSWM

DLKC

FRONT

OPE/MB

BASEU

FRONT VIEW

Legend

: Lamp is ON

: Lamp is OFF

FRONT

Note: Use any of the following circuit cards: PH-CK16, PH-CK17, PH-CK16-A, PH-CK17-A

Figure 6-39 How to Check LEDs and SW Keys for System Changeover (IMG1)

CHAPTER 6

NDA-24300

Page 458

Issue 1

SYSTEM OPERATIONS

To perform the ACT/STBY system changeover, check the lamp indicators shown in Figure 6-40, and

then operate the related key.

Note: LED indications cited in Figure 6-40 are only an example. The indicating pattern (ON/Flash/OFF) can

differ, depending on each system setting.

IMG 2/3

System State

TSW 0 -> ACT

TOPU

13 14

MUX

PIM3

MUX ACT

13 14

PIM2

FANU

PIM1

FRONT

13 14

PIM0

DUMMY/APM

BASEU

FRONT VIEW

Legend

: Lamp is ON

: Lamp is OFF

Figure 6-40 How to Check LEDs and SW Keys for System Changeover (IMG2/3)

NDA-24300

CHAPTER 6

Page 459

Issue 1

SYSTEM OPERATIONS

How to check the STATUS 7-segment LEDs

•

The ACT/STBY status of CPU can be confirmed by viewing the STATUS 7-segment LEDs.

Visually check the LED indications and confirm which CPU is active in your system.

When the STATUS LEDs display any of the two-digit numbers (00 - 99), the belonging CPU is

active. If the LEDs display the three letters (S, B and Y) in rotation, the CPU system is in STBY

mode. Note that the numbers (00 - 99), displayed on the active CPU front panel (DSP), conform

to the percentage points showing CPU occupancy rate.

DSP (Front View)

IMG0

CPUOPE

WDT

IMG0

IMG3

CPUOPE WDT

MBR

IMG1 IMG2 IMG3

STATUS

IMG1 IMG2

STATUS

If the CPU is in ST-BY mode,

the left-side LED here goes

OFF and the right side beams

S, b and y in rotation.

If the CPU is active, the

LEDs here indicate CPU

occupancy rate.

OFF

^EC

OFF

Active

ST-BY

Legend

Lamp is OFF

Lamp is Flashing

Lamp is ON

Figure 6-41 How to Check STATUS LEDs

Note: Except for the indication of the STATUS 7-segment LEDs, the ACT/STBY of the CPU also can be con-

firmed via the lamps on the DSP. If the CPU OPE lamp light steady-green and IMG0-3 are flashing,

the CPU is active. If CPU OPE appears OFF and IMG0 is flashing, the CPU is in STBY mode.

CHAPTER 6

NDA-24300

Page 460

Issue 1

SYSTEM OPERATIONS

12.1.2 How to Control CPU Block

The CPU, when it is provided in a dual configuration, can be switched over by

one of the operations shown in Table 6-8. If the system of CPU is changed over,

the ACT/STBY of GT (in TSWM) also changes over.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Table 6-8 Changeover of CPU Block

TYPE

OPERATIONS

REMARKS

Changeover by

CMOD

Use the CMOD command.

CPU OPE lamp

lights steady green

on the DSP of the

CPU, which is

placedintoact-mode

by this operation.

OPE/MB lamp of

GT (PH-GT09)

Note 1 See Chapter 8.

Changeover by key Turn ON the MBR key on the active DSP of the active CPU. After a few

operation

seconds, return the MBR key to the previous position.

Note 1 See Section 12.1.3, Manual System Changeover of CPU.

Forced Changeover ACT/STBY mode of CPU can be controlled by CPU SEL key operation on the

card, which is in the

controlling route,

lights green.

Note 2 EMA (PH-PC40) card.

UP:

No. 0 system (ACT)

DOWN: No. 1 system (ACT)

Normally, this key must be placed in the center position when the CPU is

provided in a dual configuration.

See Section 12.1.4, Forced Changeover of CPU.

Note 1: While changeover of the CPU is in progress, any call attempt is rejected. Already established calls,

however, will not be affected.

Note 2: When the forced changeover is executed, the entire system is initialized. For this reason, do not use

this operation except in unavoidable circumstances.

Figure 6-42 shows a system block diagram centering upon the CPU and its controlling GT. Though the

two sides have a complicated cable connection, the controlling route of CPU 0 directly goes to GT 0,

and that of CPU 1 to GT 1. Therefore, if the system of CPU is changed over, the ACT/STBY of GT

also changes over.

Because the ACT/STBY changeover of CPU also affects the GT status, the MBR key on the GT card

is not used for GT system changeover. The key is used to switch over the Speech Path System, involv-

ing the TSW, DLKC, and MUX circuit cards. Refer to Section 12.1.6, Manual System Changeover of

Speech Path System.

NDA-24300

CHAPTER 6

Page 461

Issue 1

SYSTEM OPERATIONS

IMG0

IMG1

IMG2

IMG3

MUX MUX MUX MUX

TSW 10

TSW 11

TSW 01

TSW 12

TSW 02

TSW 13

TSW 03

TSW 00

TSW I/O BUS

DLKC 1

DLKC 0

PLO 1

PLO 0

Note

GT 1

GT 0

CPR 1

ISAGT

CPR 0

ISAGT

CPU 0

GT 1

IOP0

GT 0

CPU 1

LANI LANI

Backboard Bus

Backboard

MISC BUS

ISAGT0

External Cable

IOC/

MISC

EMA

CPU

ISAGT: PZ-GT13

DLKC: PH-PC20

LANI: PZ-PC19

PLO: PH-CK16/17

GT: PH-GT09

EMA: PH-PC40

TSW: PH-SW12

IOC: PH-IO24

MUX: PH-PC36

Note: The connection between ISAGT and GT is somewhat unique in this system. As shown, though an

external cable is physically connected between ISAGT #0 and GT#1, the actual control signal is

sent/received only between ISAGT 0 and GT 0. This is because GT 0 and GT 1 have a multiple con-

nection on the backboard side.

Figure 6-42 System Block Diagram (Switching Network Between CPU and GT)

CHAPTER 6

NDA-24300

Page 462

Issue 1

SYSTEM OPERATIONS

12.1.3 Manual System Changeover of CPU

To change over the CPU system, the CMOD command is normally used. However, if the command

cannot be used for some reason, use the key operations listed below:

Note: For system changeover via the command, see Chapter 8.

Improper key operations may result in a system down. Operate the related keys, applying

extreme care.

WARNING

STEP 1 Determine which CPU is active.

(1) Check the lamp indications. Refer to Figure 6-43 and Table 6-8.

DSP (Front View)

CPUOPE WDT IMG0

MBR

IMG1 IMG2 IMG3

STATUS

IMG1 IMG2 IMG3

STATUS

OFF

^EC

OFF

Active

ST-BY

Lamp is Flashing

Legend

Lamp is ON

Lamp is OFF

Figure 6-43 CPU in ACT/STBY Mode

The CPU changeover also affects the ACT/STBY of GT in the TSWM. Refer to Figure 6-44

for more information, also check the lamp indications on the GT (PH-GT09) card.

GT (PH-GT09)

green

OPE/MB

MBR

GT: Active

GT: ST-BY

Legend

Lamp is ON

FRONT VIEW

Lamp is OFF

Figure 6-44 GT in ACT/STBY Mode

NDA-24300

CHAPTER 6

Page 463

Issue 1

SYSTEM OPERATIONS

(2) Check the mate CPU’s STBY mode. Also check the mate GT’s STBY mode. Refer to Fig-

ure 6-43 and Figure 6-44.

The system changeover of CPU can be done only when the mate CPU is in STBY mode. Do

not attempt the changeover if the mate CPU is closed.

WARNING

STEP 2 Flip the MBR key on the DSP of the active CPU. Refer to Figure 6-45.

After the above steps, set the MBR key as shown below.

The system changeover starts automatically.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

STATUS

OFF

^EC

OFF

DSP (Active)

Figure 6-45 CPU Changeover via MBR Key

Note: If the MBR key remains in the UP position, the CPU stays in its make-busy status. Be sure to return the

key to the DOWN position except in the case of a special purpose.

STEP 3 Confirm the changed lamp indications.

To confirm the CPU changeover, check the lamps in Figure 6-46 on both DSPs. LED indica-

tions must change as shown when the CPU system has been correctly changed over.

CPU Formerly Active

After Changeover

CPU OPE

: Steady-ON (green)

OFF

IMG0

IMG1-3

: Flash (green)

Flash (green)

OFF

MB/OPE (GT Card) : Steady-ON (green)

CPU Formerly in STBY Mode

After Changeover

CPU OPE

: OFF

Steady-ON (green)

IMG0

IMG1-3

: Flash (green)

: OFF

Steady-ON (green)

Flash (green)

MB/OPE (GT Card) : OFF

Steady-ON (green)

Figure 6-46 LED Indications Before and After CPU Changeover

STEP 4 Analyze the displayed system messages.

After STEPs 1 through 3 are performed, the system messages [7-C] and [7-D] automatically

display. Confirm that no errors occurred during the CPU changeover process.

Note: When the CPU mode change executes, the MAT (TCP/IP) is once disconnected. Then, log in to the sys-

tem again.

CHAPTER 6

NDA-24300

Page 464

Issue 1

SYSTEM OPERATIONS

12.1.4 Forced Changeover of CPU

Figure 6-47 shows how to perform the forced changeover of CPU by key oper-

ation on the EMA (PH-PC40) card. Because the key operation will cause the en-

tire system to initialize, do not rely on this method except as a last resort.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

ISAGT(PZ-GT13)

LANI(PZ-PC19)

HDDMB

FDD

CPUOPEWDT IMG0

IMG1 IMG2 IMG3

MBR

OFF

SYSTEM SELECT0

STATUS

OFF

SYSTEM SELECT1

SENSE

OUT PWR

OFF

^EC

SYSTEM SELECT2

CPURST

OFF

IN PWR

OFF

SLOT No.

LPM

HDDMB

FDD

CPUOPEWDT IMG0

IMG1 IMG2 IMG3

MBR

OFF

SYSTEM SELECT0

STATUS

OFF

SYSTEM SELECT1

SENSE

OUT PWR

OFF

^EC

SYSTEM SELECT2

CPURST

OFF

IN PWR

OFF

SLOT No.

CPR

For the forced system changeover, set the CPU-SEL

switch from middle to Up or Down. Note this operation

also leads to system initialization.

OPE/MB

1) UP

: The CPU#1 is placed into the ACT-side.

ACT1

CKERR1

ACT0

2) MIDDLE : Normal setting for dual CPU configuration.

3) DOWN : The CPU#0 is placed into the ACT-side.

(This setting is mandatory for single CPU

system.)

CKERR0

EMASUP

CPU SEL

CPU-SEL

MIDDLE

DOWN

NMI SEL

SW65

SW73

SW70

SW92

For more information, see the Circuit Card Manual.

CPU-SEL Key

SW62

SW A0

EMA(PH-PC40) FACE LAYOUT

Figure 6-47 Forced CPU Changeover

NDA-24300

CHAPTER 6

Page 465

Issue 1

SYSTEM OPERATIONS

12.1.5 How to Control Switching Block

The Switching Block denoted here includes the following system equipment:

ATTENTION

•

TSW (PH-SW12)

Contents

Static Sensitive

Handling

Precautions Required

MUX (PH-PC36)

DLKC (PH-PC20)

PLO (PH-CK16/17/16-A/17-A)

Perform the required system changeover by using the CMOD command or by operating the relevant

key on the GT/PLO card. Refer to T a ble 6-9.

Table 6-9 Changeover of Switching Block

Type

Operations

Use CMOD command.

Remarks

Speech Path Changeover by the

CMOD command

All OPE or ACT lamps on the

Speech Path System, which were

formerly active, go OFF.

All OPE or ACT lamps on the

Speech Path System, which were

formerly STBY, light steady-

green.

See Chapter 8.

Note

Speech Path System Changeover by On active GT card, turn MBR key UP.

Key Operation on the active GT card

All OPE or ACT lamps on the

Speech Path System, which were

Return MBR key to original position (DOWN) formerly active, go OFF.

after OPE/MB lamp goes OFF on GT card.

All OPE or ACT lamps on the

See Section 12.1.6, Manual System Changeover other side Speech Path System,

Note

of Speech Path System.

light steady-green.

PLO Changeover by Key Operation On active PLO card, turn MBR key UP.

ACT lamp on the PLO card, which

was formerly active, goes OFF.

Return MB key to original position (DOWN)

after ACT lamp goes OFF on PLO card.

ACT lamp on the PLO card, which

was formerly STBY, goes steady-

See Section 12.1.7, Manual System Changeover green.

of PLO.

Note

Note: These operations cause a momentary interruption in speech paths. Since the interruption is momentary,

it can be ignored as far as ordinary telephone calls are concerned. However, care should be take when

data communications are involved, as the interruption might cause bit errors.

CHAPTER 6

NDA-24300

Page 466

Issue 1

SYSTEM OPERATIONS

12.1.6 Manual System Changeover of Speech Path System

To changeover the ACT/STBY of Speech Path System, the CMOD command is normally used. How-

ever, if for some reason the command cannot be used, use the key operations listed below.

Note 1: As explained in this section, the ACT/STBY of the Speech Path System can be changed over via the

MBR key on the GT (PH-GT09) card. Because each GT (GT0 and GT1) can control both the Speech

Path System #0 an #1, perform the key operation on the active GT card, not on the card in STBY mode.

Refer to Figure 6-48.

Note 2: Figure 6-48 shows a system block diagram centering upon the GT and its controlling Speech Path Sys-

tem. By changing over the ACT/STBY of Speech Path System, all the related systems, such as TDSW/

INT, DLKC, and MUX, are totally switched over. The changeover can be executed by a key operation

on the active GT card. If the MBR key is flipped on the active GT card, all the Speech Path-related

systems (TSW/INT, DLKC, and MUX) in the same switching block are totally changed over. However,

the ACT/STBY of GT and PLO is not affected.

NDA-24300

CHAPTER 6

Page 467

Issue 1

SYSTEM OPERATIONS

IMG0

IMG1

IMG2

IMG3

Line/Trunk PM

MUX MUX MUX MUX

MUX MUX MUX MUX MUX MUX MUX MUX

MUX MUX MUX MUX

TSW 10

TSW 00

TSW 11

TSW 12

TSW 13

TSW 03

TSW 01

TSW 02

TSW I/O BUS

DLKC 1

DLKC 0

PLO 1

PLO 0

GT 1

GT 0

CPR 1

ISAGT

CPU 1

CPR 0

ISAGT

CPU 0

LANI LANI

ISAGT: PZ-GT13

DLKC: PH-PC20

LANI: PZ-PC19

PLO: PH-CK16/17/16-A/17-A

GT: PH-GT09

TSW: PH-SW12

MUX: PH-PC36

Figure 6-48 System Block Diagram (Switching Network for Speech Path System)

CHAPTER 6

Page 468

Issue 1

NDA-24300

SYSTEM OPERATIONS

STEP 1 Make sure the active Speech Path System.

(1) Check all the lamp indications in Figure 6-49, which are in the same switching block.

Legend

Lamp is ON

FRONT VIEW

green

OPE/MB

MUX ACT

TSW ACT

TSW MBR

TSW (PH-SW12)

DLKC (PH-PC20)

MUX (PH-PC36)

TSW: Active

DLKC: Active

MUX: Active

Figure 6-49 TSW/DLKC/MUX in ACT Mode

Note: Because this 4-IMG uses multiple TSW and MUX cards, be sure to check all the circuit cards concerned,

which are in the same Switching Block.For example, if your system adopts the fully expanded system,

you must check a total of 4 TSW cards and a total of 16 MUX cards in this step.

(2) Make sure the STBY mode of mate Speech Path System. Check all the lamp indications in

Figure 6-50, which are in the same Switching Block.

The ACT/STBY of Speech Path System can be changed over only when the mate system is

in STBY mode. Do not attempt the changeover if the mate Speech Path System is closed.

WARNING

Legend

Lamp is OFF

FRONT VIEW

OPE/MB

MUX ACT

TSW ACT

TSW MBR

TSW (PH-SW12)

DLKC (PH-PC20)

MUX (PH-PC36)

TSW: ST-BY

DLKC: ST-BY

MUX: ST-BY

Figure 6-50 TSW/DLKC/MUX in STBY Mode

NDA-24300

CHAPTER 6

Page 469

Issue 1

SYSTEM OPERATIONS

Note: Because this 4-IMG uses multiple TSW and MUX cards, be sure to check all the circuit cards concerned,

which are in the same Switching Block.For example, if your system adopts the fully expanded system,

you must check a total of 4 TSW cards and a total of 16 MUX cards in this step.

Improper key operations may result in a system down. Operate the related keys, using extreme

care.

WARNING

STEP 2 Flip the MBR key on the active GT card. Refer to Figure 6-51.

After STEP 1 and STEP 1.5 are taken, set the MBR key

as shown below. The system changeover starts automatically.

Steady-green

ATTENTION

OPE/MB

Contents

Static Sensitive

Handling

Precautions Required

MBR

GT (Active)

Figure 6-51 Speech Path System Changeover via Active GT MBR Key

Note: If the MBR and MB keys are turned ON (UP), the GT card is forcibly placed in a make-busy status.

Therefore, do not operate the MB key by mistake. Also, after the MBR key is flipped, be sure to return

the key to the original position (DOWN).

STEP 3 Confirm the changed lamp indications.

(1) To confirm the imposed Speech Path System changeover, check all the lamps on the cards

shown in Figure 6-52, which are in the relevant switching blocks.

Switching Block Formerly Active

After Changeover

OFF

TSW ACT

: Steady-ON (green)

OPE/MB (DLKC)

MUX ACT

: Steady-ON (green)

OFF

Switching Block Formerly STBY

After Changeover

TSW ACT

: OFF

Steady-ON (green)

OPE/MB (DLKC)

MUX ACT

: OFF

Steady-ON (green)

Figure 6-52 LED Indications Before and After Speech Path System Changeover

NDA-24300

CHAPTER 6

Page 470

Issue 1

SYSTEM OPERATIONS

(2) If the system uses PH-CK16 or PH-CK17 as the PLO, make sure the active PLO and the

newly activated TSW systems are in the same Switching Block. Refer to Figure 6-53.

Because this card’s MUSIC ROM supplies hold tones only to the TSW cards that are in

the same Switching Block, be sure to check the active PLO and the newly activated TSW

systems are all in the same Switching Block. If not, perform the PLO changeover, referring

to Section 12.1.7, Manual System Changeover of PLO.

Note: If the system has PH-CK16-A/PH-CK17-A card, this step is not required.

PH-CK16/17 (Front View)

green

ACT

PLO (PH-CK16/17)

PLO: Active

PLO: ST-BY

Legend

: Lamp is ON

: Lamp is OFF

Figure 6-53 Check of Active PLO

STEP 4 Analyze the displayed system messages.

After STEPs 1 through 3 are performed, the system messages [7-E], [7-F], and [1-T] will au-

tomatically display. Confirm that no errors occurred during the Speech Path System

changeover process.

NDA-24300

CHAPTER 6

Page 471

Issue 1

SYSTEM OPERATIONS

12.1.7 Manual System Changeover of PLO

To change over the system of Phase Lock Oscillator (PLO), use the key operations listed below.

Note: Though the PLO belongs to the Switching Block as explained in Section 12.1.5, its ACT/STBY Switching

Network is separate from that of the Speech Path System. Therefore, the changeover of the PLO must

be independently performed.

Improper key operations may result in a system down. Operate the related keys, using extreme

care.

WARNING

STEP 1 Make sure the PLO system is active.

(1) When the PLO system is active, ACT or OPE lamp on the PLO card lights green. If the

LED is OFF, the system is STBY mode.

(2) Check the mate PLO’s STBY mode. Refer to Figure 6-54.

The changeover of PLO system can be done only when the mate PLO is in STBY mode. Do

not attempt the changeover if the mate PLO is closed.

WARNING

PLO (Front View)

green

ACT/OPE Note

PLO

PH-CK16

PLO

PH-CK16

PH-CK17

PH-CK16-A

PH-CK17-A

PH-CK16-A

PH-CK17-A

PLO: Active

PLO: STBY

Legend

Lamp is ON

Lamp is OFF

Note: ACT lamp for PH-CK16/PH-CK17, OPE lamp for PH-CK16-A/PH-CK17-A.

Figure 6-54 PLO in ACT/STBY Mode

CHAPTER 6

NDA-24300

Page 472

Issue 1

SYSTEM OPERATIONS

STEP 2 Flip the MB key on the PLO card. Refer to Figure 6-55.

After the above steps, set the MB key as shown below.

Then, the system changeover starts automatically.

ATTENTION

ACT

Contents

Static Sensitive

Handling

Precautions Required

MB key

PLO: Active

Figure 6-55 PLO Changeover via MB Key

Note: If the MB key remains in the UP position, the PLO system also stays in its make-busy status. Be sure to

return the key DOWN except in the case of a special purpose.

STEP 3 Confirm the changed lamp indications.

(1) To confirm the imposed PLO changeover, check the following lamps on both PLO cards.

The LED indications must change as shown in Figure 6-56when the PLO system has been

correctly changed over.

PLO Formerly Active

After Changeover

OFF

ACT/OPE: Steady-ON (green)

PLO Formerly in STBY Mode

After Changeover

Steady-ON (green)

ACT/OPE:

OFF

Figure 6-56 LED Indications Before and After PLO Changeover

(2) If your system uses PH-CK16/PH-CK17, make sure the active TSW cards and the newly

activated PLO are in the same switching block.

Because this card’s MUSIC ROM does not supply hold tones to the TSW cards which are

in different Switching Blocks, make sure the newly activated PLO and currently active

TSW cards are both in the same Switching Block. If not, perform the Speech Path System

changeover, referring to Section 12.1.6.

Note: If the system uses PH-CK16-A/PH-CK17-A, this step is not required.

NDA-24300

CHAPTER 6

Page 473

Issue 1

SYSTEM OPERATIONS

STEP 4 Analyze the displayed system messages.

After STEPs 1 through 3 are performed, the system messages [7-U] and [7-V] will automati-

cally display. Make sure that no errors occurred during the PLO changeover process.

12.2 Initialization

12.2.1 General

This section explains the initialization types:

System Initialization

•

System Initialization by Turning ON the Power Supply, Section 12.2.2

System Initialization by Key Operations on the TOPU, Section 12.2.3

Procedure #1 through Procedure #5

•

System Initialization by the keys on the CPU Front Panel, Section 12.2.4

System Initialization by the SINZ Command, Section 12.2.5

Peripheral Equipment Initialization (Line/Trunk Initialization), Section 12.2.6

CHAPTER 6

Page 474

Issue 1

NDA-24300

SYSTEM OPERATIONS

12.2.2 System Initialization by Turning ON Power Supply

This initialization executes when the power supply to the system has stopped.

Follow the procedure in Table 6-10.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Table 6-10 System Initialization by Turning On Power Supply Procedure

ACTION

REMARKS

START

Confirm all switches are turned OFF on PWR cards.

Power supply to the PBX is restored.

Refer to Section 12.3.

Check INPUT voltage is nor-

mal at power terminals.

Confirm input source power to the PBX is normal.

Turn ON power supply at PWR cards.

Execution of Initialization

Refer to Section 12.3.

When initialization completes,

ACT0 lamp lights green and

ACT1 lamp goes OFF on

EMA (PH-PC40) card.

Confirm the following lamp indications:

[CPU DSP#0]

CPU OPE: steady-green

IMG0-3: flash (green)

[CPU DSP#1]

IMG0:

flash (green)

Clear alarm by pressing ALM RST key on TOPU.

Use ATIM command to adjust date and time.

END

NDA-24300

CHAPTER 6

Page 475

Issue 1

SYSTEM OPERATIONS

12.2.3 System Initialization by Key Operations on TOPU

Table 6-11 shows the system initialization procedure. Figure 6-57 shows the initial program load con-

ceptional diagram.

Table 6-11 System Initialization ProcedureTypes

TYPE

DESCRIPTION

Procedure #1 System Initialization without Loading

(T a ble 6-12)

Whole system is initialized. All communications are

forcibly released. System restarts with current Main

Memory Files and Office Data Files that exist on DRAM.

Procedure #2 System Initialization with Office Data Loading Whole system is initialized. All communications are

(T a ble 6-13)

forcibly released. System transfers Office Data Files from

HDD to DRAM. System restarts with the transferred

Office Data Files and the current Main Memory Files.

Procedure #3 System Initialization with Program Loading

(T a ble 6-14)

Whole system is initialized. All communications are

forcibly released. System transfers Main Memory Files

from HDD to DRAM. System restarts with the

transferred Main Memory Files and the current Office

Data Files.

Procedure #4 System Initialization with Office Data and

Whole system is initialized. All communications are

forcibly released. System transfers both Main Memory

Files and Office Data Files from HDD to DRAM. System

restarts with the transferred Main Memory Files and the

transferred Office Data Files.

(T a ble 6-15)

Program Loading

Procedure #5 System Initialization by Phase 1 Restart

(T a ble 6-16)

System is initialized. All communications, except for the

following two-way connections that have already been

established, are forcibly released:

• Basic two-way connections (STN-STN, STN-TRK,

TRK-TRK)

• Fixed connections

• Two-way connections established on a Fusion Link

Note 1: STN-ATT connection is not included in

the two-way connection list cited

above. These kind of calls are forcibly

released once the initialization exe-

cutes.

Note 2: When a calling party hears the Ring

Back Tone, the ORT is additionally

provided, and the call is placed into the

Dial Tone (DT) connection.

CHAPTER 6

Page 476

Issue 1

NDA-24300

SYSTEM OPERATIONS

Initial Program Load

H D D

Basic Software (#2-11)s

Main Memory Files

(=PROGRAM)

DRAM

Standard Service Software

IMAT Software (#1-2)

TCP/IP Software (#1)

Data Memory (ASYD, AUNT,

ANPD, ASPA, ASDT, etc.)

Call Forwarding Data

Speed Calling Data

Name Display Data

RCF

Office Data Files

(=SYSTEM DATA)

CPU

NDM

LDM

User Assign Soft Key Data

Number Sharing Data

Call Block

PBX

Figure 6-57 Conceptional Diagram of Initial Program Load

NDA-24300

CHAPTER 6

Page 477

Issue 1

SYSTEM OPERATIONS

To initialize the system, check the lamp indications in Figure 6-58, and operate the keys on PZ-DK222

(TOPU).

PZ-DK222: Face Layout

SYSTEM DATA

NON LOAD

PFT

PROGRM

LOAD

INITIAL

START

EFFECT

ALM

RST

LOAD

OFF

NON LOAD

OFF

To initialize the system, operate the keys

shaded here.

IMG0

13 14

03 04

..........

OFF

To confirm the imposed system initialization, check

the lamp indicators shaded here.

FRONT VIEW

CPR: Face Layout

Note 2

Note 1

HDDMB

CPUOPE WDT IMG0

MBR

FDD

IMG1

IMG2 IMG3

STATUS

OFF

SYSTEM SELECT0

OFF

SYSTEM SELECT1

SENSE

OUT PWR

OFF

^EC

SYSTEM SELECT2

CPURST

OFF

IN PWR

OFF

SLOT No.

Note 1: This figure assumes that the CPR is equipped with PZ-IO27 (HDD/FDD), in place of PZ-

IO28. If PZ-IO28 is used, the MB (Make-busy) key is not furnished on the card.

Note 2: The LED indication cited above is only an example. The actual indicating patterns (ON/

Flash/OFF) may vary, depending on the system configuration.

Figure 6-58 Related Keys and LEDs for System Initialization

CHAPTER 6

NDA-24300

Page 478

Issue 1

SYSTEM OPERATIONS

Table 6-12 System Initialization Without Loading [Procedure #1]

7SEG LED/OPE LAMP/KEY

SETTINGS

ACTION

CPU OPE lamp on the DSP of

active CPU lights steadily green.

IMG0-3 lamps flash.

START

Confirm system is operating normally.

IMG0 lamp on the DSP of mate

CPU flashes green.

Turn ON the EFFECT key on the TOPU. (See Figure 6-58)

Set the keys on the TOPU as follows.

SYSTEM DATA

• PROGRAM KEY

→

NON LOAD

PROGRM

NON LOAD

• SYSTEM DATA KEY → NON LOAD

LOAD

NON LOAD

PZ-DK222

Press INITIAL START button on the TOPU.

CPU OPE and IMGX lamps on

both DSP go OFF.

STATUS LED (right) on

the CPU is ON.

• HD Initial

• System Initialization

STATUS LED (right) on

the DSP of CPU is ON.

• System starts up again.

CPU OPE lamp on the DSP of

active CPU lights steadily green.

IMG0-3 lamps flash.

IMG0 lamp on the DSP of mate

CPU flashes green.

STATUS LED (right) on

the DSP of active CPU is

ON. (ON LINE)

END

NDA-24300

CHAPTER 6

Page 479

Issue 1

SYSTEM OPERATIONS

Table 6-13 System Initialization With Office Data Loading From HD [Procedure #2]

7SEG LED/OPE LAMP/KEY

ACTION

SETTINGS

CPU OPE lamp on the DSP of

active CPU lights steadily green.

IMG0-3 lamps flash.

START

Confirm system is operating normally.

IMG0 lamp on the DSP of mate

CPU flashes green.

Turn ON the EFFECT key on the TOPU. (See Figure 6-58)

SYSTEM DATA

Set the keys on the TOPU as follows.

PROGRM

NON LOAD

• PROGRAM KEY

→

NON LOAD

LOAD

• SYSTEM DATA KEY → LOAD

LOAD

NON LOAD

PZ-DK222

Press INITIAL START button on the TOPU.

CPU OPE and IMGX lamps on

both DSP go OFF.

STATUS LED (right) on

the DSP of CPU is ON.

• HD Initialization

STATUS LED (right) on

the DSP of CPU is ON.

• Office Data Load

• System Initialization

• System starts up again.

STATUS LED (right) on

the DSP of active CPU

is ON.

CPU OPE lamp on the DSP of

active CPU lights steadily green.

IMG0-3 lamps flash.

IMG0 lamp on the DSP of mate

CPU flashes green.

STATUS LED (right) on

the DSP of active CPU

is ON. (ON LINE)

END

CHAPTER 6

NDA-24300

Page 480

Issue 1

SYSTEM OPERATIONS

Table 6-14 System Initialization with Program Loading From HD [Procedure #3]

7SEG LED/OPE LAMP/KEY

SETTINGS

ACTION

CPU OPE lamp on the DSP of

active CPU lights steadily green.

IMG0-3 lamps flash.

START

Confirm system is operating normally.

IMG0 lamp on the DSP of

active CPU flashes green.

Turn ON the EFFECT key on the TOPU. (See Figure 6-58)

SYSTEM DATA

Set the keys on the TOPU as follows.

PROGRM

NON LOAD

• PROGRAM KEY

→

LOAD

• SYSTEM DATA KEY → NON LOAD

LOAD

NON LOAD

PZ-DK222

Press INITIAL START button on the TOPU.

CPU OPE and IMGX lamps on

both DSP go OFF.

• HD Initialization

STATUS LED (right) on

the DSP of CPU is ON.

• Program Load

STATUS LED (right) on

the DSP of CPU is ON.

• System Initialization

STATUS LED (right) on

the DSP of active CPU

is ON.

• System starts up again.

CPU OPE lamp on the DSP of

active CPU lights steadily green.

IMG0-3 lamps flash.

IMG0 lamp on the DSP of mate

CPU flashes green.

STATUS LED (right) on

the DSP of active CPU

is ON. (ON LINE)

END

NDA-24300

CHAPTER 6

Page 481

Issue 1

SYSTEM OPERATIONS

Table 6-15 System Initialization With Office Data And Program Loading From HD [Procedure #4]

7SEG LED/OPE LAMP/KEY

ACTION

SETTINGS

CPU OPE lamp on the DSP of

START

active CPU lights steadily green.

IMG0-3 lamps flash.

Confirm system is operating normally.

IMG0 lamp on the DSP of mate

CPU flashes green.

Turn ON the EFFECT key on the TOPU. (See Figure 6-58)

Set the keys on the TOPU as follows.

SYSTEM DATA

PROGRM

NON LOAD

• PROGRAM KEY

→

LOAD

• SYSTEM DATA KEY → LOAD

LOAD

NON LOAD

PZ-DK222

Press INITIAL START button on the TOPU.

CPU OPE and IMGX lamps on

both DSP go OFF.

STATUS LED (right) on

the DSP of CPU is ON.

• HD Initialization

• Program Load

STATUS LED (right) on

the DSP of CPU is ON.

STATUS LED (right) on

the DSP of CPU is ON.

• Office Data Load

• System Initialization

• System starts up again.

STATUS LED (right) on

the DSP of active CPU

is ON.

CPU OPE lamp on the

DSP of active CPU lights

steadily green. IMG0-3 lamps

flash.

IMG0 lamp on the DSP of mate

CPU flashes green.

STATUS LED (right) on

the DSP of active CPU

is ON. (ON LINE)

CHAPTER 6

NDA-24300

Page 482

Issue 1

SYSTEM OPERATIONS

Table 6-16 System Initialization by Phase 1 Restart [Procedure #5]

7SEG LED/OPE LAMP/KEY

SETTINGS

ACTION

CPU OPE lamp on the DSP of

active CPU light steadily green.

(IMG0-3 lamps flash.)

START

Confirm system is operating normally.

IMG0 lamp on the DSP of mate

CPU flashes green.

Set the SENSE switch on the DSP of CPR to “3”.

Turn ON the EFFECT key on the TOPU. (See Figure 6-58)

Set the keys on the TOPU as follows.

SYSTEM DATA

PROGRM

NON LOAD

LOAD

• PROGRAM KEY

• SYSTEM DATA KEY → NON LOAD

→

NON LOAD

LOAD

NON LOAD

PZ-DK222

Press INITIAL START button on the TOPU.

CPU OPE and IMGX lamps on

both DSP go OFF.

STATUS LED (right) on

the CPU is ON.

• HD Initialization

STATUS LED (right) on

the DSP of CPU is ON.

• System Initialization

• System starts up again.

CPU OPE lamp on the DSP of

active CPU lights steady green.

(IMG0-3 lamps flash.)

IMG0 lamp on the DSP of mate

CPU flashes green.

STATUS LED (right) on

the DSP of active CPU

is ON. (ON LINE)

END

NDA-24300

CHAPTER 6

Page 483

Issue 1

SYSTEM OPERATIONS

12.2.4 System Initialization by Keys on CPU Front Panel

This initialization executes when the INITIAL key on the TOPU cannot be used.

The CPU’s active status must be confirmed before executing this type of initial-

ization. Perform the procedure in T a ble 6-17.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Table 6-17 System Initialization by Keys on CPU Front Panel Procedure

ACTION

REMARKS

START

EMA: PH-PC40

Check ACT0/ACT1

lamps on the EMA

card.

ACT0 lights green.)

Confirm SENSE switch on the

(ACT1 lights green.)

Confirm SENSE switch on the

DSP of CPU #0 is 2 (DM Load

Restart).

DSP of CPU #1 is 2 (DM Load

Restart).

Press CPU RST key on the

DSP of CPU #1.

Press CPU RST key on the

DSP of CPU #0.

(CPU #1 is being initialized.)

(CPU #0 is being initialized.)

Confirm ACT0 lamp lights

green again.

Confirm ACT1 lamp lights

green again.

Use ATIM command to adjust date and

time. (Refer to Chapter 8)

END

CHAPTER 6

Page 484

Issue 1

NDA-24300

SYSTEM OPERATIONS

12.2.5 System Initialization by SINZ Command

The entire system can be initialized by execution of the SINZ command from the MAT, which is useful

for maintenance technicians who have to control the system from a distant location. Perform the pro-

cedure in Table 6-18.

Table 6-18 System Initialization by SINZ Command Procedure

ACTION

REMARKS

START

For information about SINZ

command, see Chapter 8.

Use SINZ command to execute

initialization.

Execution of Initialization

When the initialization com-

pletes, ACT0 lamp lights

green and ACT1 lamp goes

OFF on EMA (PH-PC40)

card.

Confirm the following lamp indications:

[CPU DSP #0] CPU OPE: steady-green

IMG0-3: flash (green)

[CPU DSP #1] IMG0:

flash (green)

Note: When the system is

initialized, the MAT is

once disconnected. Then,

Use ATIM command to adjust date and

time.

END

NDA-24300

CHAPTER 6

Page 485

Issue 1

SYSTEM OPERATIONS

12.2.6 Peripheral Equipment Initialization (Line/Trunk Initialization)

Line/trunk initialization can be divided into two types: initialization on an indi-

vidual channel basis and initialization on a circuit card basis. Follow the proce-

dure in Table 6-19.

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Table 6-19 Line/Trunk Initialization Procedure

ACTION

REMARKS

Note: When initializa-

tion executes on a

START

circuitcardbasis, all

channels on the cir-

cuit card are placed

into make-busy state.

Is initialization on

individual channel basis or on

circuit card basis?

Circuit card basis

Individual channel basis

Turn the MB switch UP on

the circuit card.

Use RLST command.

(Refer to Chapter 8)

Return MB switch to the

previous position after the

MB lamp has turned ON.

END

CHAPTER 6

NDA-24300

Page 486

Issue 1

SYSTEM OPERATIONS

12.3 How to Turn ON/OFF Whole System

A switching system, once put into service, is seldom stopped. However, there may be a case when a

switching system must be stopped due to module expansion work, etc. In preparation for such a case, this

section explains the procedure for stopping the system and turning ON the power supply.

12.3.1 How to Turn On Whole System

START

ATTENTION

Confirm SENSE switch on DSP of Active

CPU is set at 2 (DM Load Restart).

Contents

Static Sensitive

Handling

Precautions Required

Turn ON power supply at PIMs of IMG3.

PIM0 PIM1 PIM2 PIM3

(1) Turn ON -48V SW on PWR card in PIM0.

(2) Turn ON -48V SW on DPWR card in PIM0.

(3) Repeat (1) and (2) for PIM1, 2, 3 in turn

(depending on system configuration).

Turn ON power supply at TSWM1.

(1) Turn ON -48V SW on PH-PW14 (PWR SW#0).

(2) Turn ON -48V SW on PH-PW14 (PWR SW#1).

Turn ON power supply at PIMs of IMG2.

PIM0 PIM1 PIM2 PIM3

(1) Turn ON -48V SW on PWR card in PIM0.

(2) Turn ON -48V SW on DPWR card in PIM0.

(3) Repeat (1) and (2) for PIM1, 2, 3 in turn

(depending on system configuration).

Turn ON power supply at TSWM0.

(1) Turn ON -48V SW on PH-PW14 (PWR SW#0).

(2) Turn ON -48V SW on PH-PW14 (PWR SW#1).

Turn ON power supply at PIMs of IMG1.

PIM0 PIM1 PIM2 PIM3

(1) Turn ON -48V SW on PWR card in PIM0.

(2) Turn ON -48V SW on DPWR card in PIM0.

(3) Repeat (1) and (2) for PIM1, 2, 3 in turn

(depending on system configuration).

Turn ON power supply at LPM.

(1) Turn ON the SW on PZ-PW92 CPU #0.

(2) Turn ON the SW on PZ-PW92 CPU #1.

Turn ON power supply at PIMs of IMG0.

PIM0 PIM1 PIM2 PIM3

(1) Turn ON -48V SW on PWR card in PIM0.

(2) Turn ON -48V SW on DPWR card in PIM0.

(3) Repeat (1) and (2) for PIM1, 2, 3 in turn

(depending on system configuration).

END

Note: Start from bigger number depending on configuration of IMG stack.

(i.e. 1.5 stack: IMG3 IMG2 IMG1 IMG0).

Figure 6-59 How to Turn ON the Whole System

NDA-24300

CHAPTER 6

Page 487

Issue 1

SYSTEM OPERATIONS

12.3.2 How to Turn OFF Whole System

Confirm that the memory data has been backed up on the HD before turning OFF the system power.

When turning OFF the power supply, follow the procedure shown below.

Turn OFF the power supply in the uppermost PIM of the IMG stack whose number is larger. Then

move down to the bottommost PIM and repeat the procedure for the smaller IMGs.

IMG0

IMG1

IMG2

IMG3

PIM3

PIM2

PIM1

PIM0

LPM

PIM2

PIM1

PIM2

PIM1

PIM2

PIM1

ATTENTION

Contents

PIM0

Static Sensitive

Handling

Precautions Required

TSWM

DUMMY

(1) Turn OFF -48V SW on DPWR (first) and PWR (next) cards in PIM3 of IMG3.

(2) Repeat (1) for PIM2, PIM1, PIM0 (IMG3) in this order.

(3) Turn OFF -48V SW on DPWR (first) and PWR (next) cards in PIM3 of IMG2.

(4) Repeat (3) for PIM2, PIM1, PIM0 (IMG2) in this order.

(5) Turn OFF -48V SW on DPWR (first) and PWR (next) cards in PIM3 of IMG1.

(6) Repeat (5) for PIM2, PIM1, PIM0 (IMG1) in this order.

(7) Turn OFF SW on PH-PW14 (both PWR SW #1 and #0) in TSWM.

(8) Turn OFF -48V SW on DPWR (first) and PWR (next) cards in PIM3 of IMG0.

(9) Repeat (8) for PIM2, PIM1, PIM0 (IMG0) in this order.

(10) Turn OFF SW on PZ-PW92 of CPU #1.

(11) Turn OFF SW on PZ-PW92 of CPU #0.

Figure 6-60 How To Turn OFF the Whole System

CHAPTER 6

NDA-24300

Page 488

Issue 1

SYSTEM OPERATIONS

12.4 System Start-Up

The system start-up procedures consist of the following types:

Procedure #1 (see T a ble 6-20)

Executed when the Basic Software and Application Software

have already been installed in the HD. Office Data has not

been installed.

Procedure #2 (see T a ble 6-21)

Executed when the Basic Software, Application Software and

Office Data have been already installed in the HD.

Note: For the start-up procedure in case any Basic Software, Application Software and Office Data have not been in-

stalled in the HD, refer to the Installation Manual (4-IMG Type).

NDA-24300

CHAPTER 6

Page 489

Issue 1

SYSTEM OPERATIONS

Table 6-20 Start-Up When Basic & Application Software Is

Installed [Procedure #1]

7SEG LED/OPE LAMP/KEY

ACTION

SETTINGS

When Power is ON

and OFF LINE

➀

When Power is OFF

➀

START

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

Set SENSE switch at “1” (DM

Clear Restart) on the DSP of

active CPU.

Set SENSE switch at “1” (DM

Clear Restart) on the DSP of

CPU #0.

Press the CPU RST button

on the DSP of active CPU.

Turn ON the SW on the PZ-

PW92 of CPU #0.

Turn OFF the SW on the PZ-

PW92 of active CPU and

turn it ON again.

STATUS LED (right) on

the DSP of CPU is ON.

• HD Initialization

STATUS LED (right) on

the DSP of CPU is ON.

• Program Load

• System Initial

STATUS LED (right) on

the DSP of CPU is ON.

CPU OPE lamp on the

DSP of active CPU

lights steady green. IMG0-3

lamps flash.

System starts up, clearing the Office Data on the HD.

• The system starts up again

IMG0 lamp on the DSP of mate

CPU flashes green.

➀ when Power is ON and ON

LINE

STATUS LED (right) on

the DSP of CPU is ON

(ON LINE).

START

CHAPTER 6

NDA-24300

Page 490

Issue 1

SYSTEM OPERATIONS

Table 6-20 Start-Up When Basic & Application Software Is

Installed [Procedure #1] (Continued)

7SEG LED/OPE LAMP/KEY

SETTINGS

ACTION

Set SENSE switch at “2” (DM Load Restart) on the DSP of active

ATTENTION

Contents

CPU.

Static Sensitive

Handling

Precautions Required

Enter your Office Data.

Back up Office Data using the MEM_HDD command.

Turn ON the EFFECT key on the TOPU. (See Figure 6-58)

Set the keys on the TOPU as follows.

SYSTEM DATA

PROGRM

NON LOAD

• PROGRAM KEY

→

NON LOAD

LOAD

• SYSTEM DATA KEY → LOAD

LOAD

NON LOAD

PZ-DK222

Press INITIAL START button on the TOPU.

CPU OPE and IMGX lamps on

both DSP go OFF.

• HD Initial

STATUS LED (right) on

the DSP of CPU is ON.

STATUS LED (right) on

the DSP of CPU is ON.

• DM Load

• System Initial

STATUS LED (right) on

the DSP of CPU is ON.

• System starts up again.

CPU OPE lamp on the

DSP of active CPU

lights steady-green. IMG0-3

lamps flash.

IMG0 lamp on the DSP of mate

CPU flashes green.

STATUS LED (right) on

the DSP of CPU is ON.

(ON LINE)

END

NDA-24300

CHAPTER 6

Page 491

Issue 1

SYSTEM OPERATIONS

Table 6-21 Start-Up When Basic, Application Software, and

Office Data Installed [Procedure #2]

7SEG LED/OPE LAMP/KEY

ACTION

SETTINGS

When Power is ON

and OFF LINE

➀

When Power is OFF

➀

START

ATTENTION

Contents

Static Sensitive

Set the SENSE switch at “2”

(DM Load Restart) on the DSP

of active CPU.

Set the SENSE switch at “2”

(DM Load Restart) on the DSP

of CPU #0.

Handling

Precautions Required

Press the CPU RST button

on the DSP of active CPU.

Turn ON the SW on the PZ-

PW92 of CPU #0.

Turn OFF the SW on the PZ-

PW92 of active CPU and

turn it ON again.

• HD Initial

STATUS LED (right) on

the DSP of CPU is ON.

• Program Load

• Office Data Load

• System Initial

STATUS LED (right) on

the DSP of CPU is ON.

STATUS LED (right) on

the DSP of CPU is ON.

STATUS LED (right) on

the DSP of CPU is ON.

CHAPTER 6

NDA-24300

Page 492

Issue 1

SYSTEM OPERATIONS

Table 6-21 Start-Up When Basic, Application Software, and

Office Data Installed [Procedure #2] (Continued)

7SEG LED/OPE LAMP/KEY

SETTINGS

ACTION

ATTENTION

Contents

Static Sensitive

Handling

Precautions Required

CPU OPE lamp on the DSP of

active CPU lights steady-green.

IMG0-3 light steady-green.

• System starts up again.

IMG0 lamp on the DSP of mate

CPU flashes green.

STATUS LED (right) on

the DSP of CPU is ON.

(ON LINE)

END

NDA-24300

CHAPTER 6

Page 493

Issue 1

This page is for your notes.

CHAPTER 6

Page 494

Issue 1

NDA-24300

CHAPTER 7

1. GENERAL

ROUTINE MAINTENANCE PROCEDURE

When a fault has occurred in the system, (for example when a fault has occurred to No. 1 circuit on the 16LC

card), the stations connected to No. 1 circuit become unserviceable. When the 16LC card has been replaced with

a spare to analyze the cause of the fault or to repair the fault, other normal lines also become unserviceable. As

in this example, even when the fault is restricted to a single component, it very often harms the system operations

as a whole.

Even if the system is operating normally, it is necessary to perform a routine check to prevent a fault occurrence

before it is too late to discover any latent cause of a fault.

This chapter categorizes the routine maintenance procedures of the PBX into the following three types, and ex-

plains the minimum required work steps and precautions pertaining to each of the three procedures.

•

Daily Maintenance Procedure

Monthly Maintenance Procedure

Quarterly Maintenance Procedure

1.1 Flow of Procedures

The scheduling of routine maintenance (daily, monthly, quarterly) will vary with each installation and or-

ganization. Figure 7-1 shows the flow of the routine maintenance procedures.

Section 2.7, Explanation of Terms in Chapter 2

Section 2, Routine Maintenance Procedures

•

Daily Maintenance Procedures

Monthly Maintenance Procedures

Quarterly Maintenance Procedures

Chapter 5, Fault Repair Procedures

Chapter 6, System Operations

Note: Perform procedure performance per

each divided section

Chapter 4, Unit/Circuit Card

Replacement Procedure

Section 3, Routine Maintenance Check Lists

•

Recording of checked items

Figure 7-1 Flow of Procedures

NDA-24300

CHAPTER 7

Page 495

Issue 1

ROUTINE MAINTENANCE PROCEDURE

1.2 Required Test Equipment and Tools

Table 7-1 shows the tools and equipment required for test procedures.

Table 7-1 Test Equipment and Tools

NO.

TEST EQUIPMENT/TOOLS

PURPOSE

REMARKS

Telephone Set

A telephone set is used when performing connection tests

on trunks, etc.

Blown Fuse

A blown fuse is used when performing alarm tests.

VOM Digital Meter

VOM digital meter is used when checking output voltages

of the rectifier and the battery.

Phillips Screwdriver

A screwdriver is used when replacing the fan with a spare.

CHAPTER 7

Page 496

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

2. ROUTINE MAINTENANCE PROCEDURES

This section explains general routine maintenance procedures to be performed on a daily, monthly, and quar-

terly basis. Table 7-2 lists each procedure according to the time each procedure is to be performed. Use the

Reference Section to locate the detailed procedure.

Table 7-2 List of Routine Maintenance Procedures

TIME

PROCEDURE

REFERENCE SECTION

REMARKS

Daily

Check the temperature and relative humidity in

the switch room.

Sectio n 2 .1, Ambien t C onditions

in Switch Room Check

Check to see if any of the alarm indicator lamps Section 2.2, Alarm Check

on the TOPU are lit.

Check the operating status of the MAT and the

printer, remaining quantity of paper, etc.

Section 2.3, M A T /Printer Check

Check to see if a system message indicating a

fault is displayed.

Section 2.4, Collection of Sys-

tem Messages

Check whether any station is in lockout state.

Section 2.5, Display of Locked-

out Station

Check whether the FANU is operating normally. Section 2.6, Fan Unit Check

Monthly Generate an alarm and check whether an indica- Section 2.7, Alarm Tests

tion appears on the TOPU.

Check the conditions of the rectifier and batteries. Section 2.8, Main Power System

Check

Check trunk circuits individually. Also check the Section 2.9, Trunk RGU Check

RGU circuit in the PWR Supply of each

Module.

Check each operation and lamps of DESKCON/ Section 2.10, A T TCON/

ATTCON.

DESKCON Check

Quarterly Check the CPU, TSW, and line/trunk Port Micro- Section 2.11, System Check

processors (PMs).

NDA-24300

CHAPTER 7

Page 497

Issue 1

ROUTINE MAINTENANCE PROCEDURE

2.1 Ambient Conditions in Switch Room Check

START

Check the room temperature.

Check whether the room temperature is within

the range of 5°C (41°F) to 30°C (86°F).

Check the humidity in the room.

Check whether the relative humidity in the

room is within the 15% to 65% range.

If the temperature or the humidity is

outside the allowable range, adjust the air

conditioner.

END

CHAPTER 7

Page 498

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

2.2 Alarm Check

START

Check alarm indications on the TOPU.

If an alarm is indicated

Check whether the alarm lamp on the power

supply of any module is lit.

Check whether an alarm lamp is lit on any

circuit card(s).

Alarm recovery

Refer to Chapter 5, diagnose the alarm, and

perform the indicated recovery procedures.

END

NDA-24300

CHAPTER 7

Page 499

Issue 1

ROUTINE MAINTENANCE PROCEDURE

2.3 MAT/Printer Check

START

Check the MAT.

Turn ON the MAT’s power.

Confirm that the menu appears on the screen.

System messages are automatically sent to

the MAT HD for output.

Leave the MAT power ON continuously (lower

the CRT brightness when not in use).

System messages are automatically sent to

the external printer for output.

Confirm that printer power is ON and that the

SEL lamp is lit.

Check the remaining quantity of printer paper.

END

CHAPTER 7

Page 500

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

2.4 Collection of System Messages

START

Cause system messages to be displayed.

When a system message is displayed.

Refer to Chapter 3.

If the system message indicates a fault,

diagnose the fault by referring to Chapter 5,

and perform fault recovery.

Check the results of routine diagnosis.

System message [7-O] indicates that the

system is normal.

System message [7-P] indicates that the system

is abnormal. Perform fault recovery by

referring to Chapter 3 or Chapter 5.

When the system is operating normally or

after a fault is restored

Use the RALM command to clear the alarm

indication and registered system message.

END

NDA-24300

CHAPTER 7

Page 501

Issue 1

ROUTINE MAINTENANCE PROCEDURE

2.5 Display of Locked-out Station

START

Check the displays of relevant commands

to locate any locked-out stations.

Check the displays of the following

commands:

•

DLSL: Display in the order of LENS

DLSS: Display in the order of Station

Numbers

When any station in locked-out

state is displayed

Recover the locked-out station(s) referring to

Section 3, Indication of Lockout Stations, in

Chapter 6.

END

CHAPTER 7

Page 502

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

2.6 Fan Unit Check

START

When fan is set for automatic start

Pull FAN START switch toward the front and

set it to ON (UP) position.

Confirm that the fan has started running.

Pull FAN START switch toward the front and

set it to AUTO (DOWN) position.

When fan is set for constant operation

When fan is out of order

Confirm that the fan is running.

Refer to Section 9, Fan Unit Fault, in Chapter

Replace the fan with a spare by referring to

Section 4., Fan Unit Replacement, in Chapter

END

NDA-24300

CHAPTER 7

Page 503

Issue 1

ROUTINE MAINTENANCE PROCEDURE

2.7 Alarm Tests

START

An alarm is to be generated which will be displayed at the DESKCON/ATTCON. Be sure to inform

the attendant of the test in advance.

Replace the –48V fuse in the FANU with a blown fuse.

Confirm that an alarm is indicated on the TOPU.

Replace the blown fuse with the original –48V fuse.

Using the RALM command, reset all alarm indications.

END

CHAPTER 7

Page 504

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

2.8 Main Power System Check

START

Check the load voltage (DC –48V ±5 V) of the rectifier.

Check the batteries.

Check the forced-charge voltage and floating

voltage.

Check the specific gravity, liquid level and

rated capacity of each battery.

END

Note: For a longer battery life, observe the following items:

•

Place the batteries in a dark, cool place.

Keep the room temperature within the range of 10°C to 35°C (40°F to 85°F).

Floating voltage must be kept within the range of the battery specification at all times.

After discharging, perform equalized charging as per the battery specification.

NDA-24300

CHAPTER 7

Page 505

Issue 1

ROUTINE MAINTENANCE PROCEDURE

2.9 Trunk RGU Check

START

Check alarm lamps on the line/trunk circuit cards.

Check to see if a system message pertaining to a circuit card has been output.

Check the speech path for each PIM and also check ringing signal.

END

CHAPTER 7

Page 506

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

2.10 ATTCON/DESKCON Check

(1) Attendant Console Check

START

Ask the operator at each ATTCON if the ATTCON is operating normally.

Each operator presses the LCHK button on the ATTCON and confirms that all the lamps on the

control panel light up.

When the ATTCON is equipped with a Time Indicator Section, the operator also checks the displayed

time.

END

Note: Adjusting Time Method (see Figure 7-2.)

•

If the Hour (H) button is pushed once, the time will advance one hour. (To push the button, use a thin

object, such as a toothpick.)

•

If the H button is held continuously, the time will advance one hour each second.

If the Minute (M) button is pushed once, the time will advance one minute.

If the M button is held continuously, the time will advance one minute each second.

AM PM

ADJUST.

TIME

STATION/TRUNK NUMBER

Figure 7-2 Adjusting Time on ATTCON

NDA-24300

CHAPTER 7

Page 507

Issue 1

ROUTINE MAINTENANCE PROCEDURE

(2) Desk Console Check

START

Ask the operator at each DESKCON if the DESKCON is operating normally.

On the DESKCON control panel, each operator presses the L3, SRC, and Release keys simultaneously

and confirms that all the lamps on the control panel light red.

Operator presses the # key and confirms that all the lamps on the same transverse line between the

EMG and Mute lamps light green. Refer to Figure 7-3.

Operator presses the # key and confirms that all the green lamps (in the step above) go OFF and the

LCD on the DESKCON displays black.

Operator presses the # key and confirms the black LCD display is cleared and a ringing tone is heard.

Operator presses the # key and confirms the provided ringing tone has suspended.

Operator presses the keys on the DESKCON one by one and confirms that each lamp, corresponding

to the pressed key, emits a light and the name of the key displays on the LCD, respectively.

Operator presses the * button and completes the lamp checks. Note 1

Operator checks the displayed time on the right part of LCD. Note 2

END

Note 1: The lamp checks can be suspended any time when the * key on the control panel is pressed.

Note 2: The DESKCON obtains time information only from the PBX side. Therefore, adjust the time and date

using the MAT command.

3:25 PM WED 1

Alarm

Position

Available

Position

Busy

Night

LDN

TIE

BUSY

ATND

NANS RECALL

PAGE

Start

REC

Mute

EMG

TRKSL Call Park

SVC

Cancel

SRC

DEST

Talk

Release

Hold

Answer

Figure 7-3 Desk Console

NDA-24300

CHAPTER 7

Page 508

Issue 1

ROUTINE MAINTENANCE PROCEDURE

2.11 System Check

START

Check the OPE lamps (green) on all circuit cards.

Check whether a system message pertaining to the CPU/TSW has been output.

Check speech conditions by establishing a station-to-station connection at each PIM.

If the condition is abnormal, determine the nature of the problem (dial tone cannot be heard,

no speech can be established, etc.)

Does the condition occur in No. 0 TSW or in No. 1 TSW?

Does the condition occur in No. 0 CPU or in No. 1 CPU?

Using MEM_HDD command, check the data memory.

END

NDA-24300

CHAPTER 7

Page 509

Issue 1

ROUTINE MAINTENANCE PROCEDURE

3. ROUTINE MAINTENANCE CHECK LISTS

This section provides check lists (Maintenance Procedure Reports) to be used when performing routine main-

tenance. The Routine Maintenance Check Lists consists of the following items:

•

Maintenance Procedure Report

C.O. Trunk/Tie Line

Digital Conference Function

Speech Path for each PIM, and Ringing Generator Unit

Attendant/Desk Console

CHAPTER 7

Page 510

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

WORK TIME

SIGNATURE OF

SUPERVISOR

USER NAME

(FROM -

)

Name of User (Company)

Date:

Maintenance

Classification

Routine/Non-

routine

Control No.

Maintenance

Company

Name of Equipment

Room Temperature - °C Name of Worker

°F & humidity %

Reference Item

Section

Detail

Check Reference Item

Section

Detail

Check

2.1

Check of Ambient Ambient

2.9

Trunk RGU Check SND Trunk

Conditions in the

Switch Room

Temperature

Relative humidity

TOPU

DCF Function

Tone

2.2

2.3

Alarm Check

MAT/Printer Check MAT

Printer

MAT

2.10

2.11

ATTCON Check

System Check

Ringing Signal

2.4

2.5

Collection of

Related to Fault

System Messages

Result of Routine

Diagnosis

CPU

TSW

Display of Locked- Locked out

out Station

Stations

2.6

2.7

2.8

Fan Unit Check

Alarm Tests

TOPU

Main Power

System Check

Rectifier

Battery

2.9

Trunk RGU Check C.O. Trunk

Tie Trunk

ORT

IRT

Condition And Cause

Procedure and Parts Used

NDA-24300

CHAPTER 7

Page 511

Issue 1

ROUTINE MAINTENANCE PROCEDURE

C.O. Trunk/Tie Line

TEST TYPE

TEST ITEM

CONNECTION DIAGRAM

C.O. Trunk/Tie Line

Speech Path Test

• Set up a speech path test by • Connection Test-Station

seizing a trunk using the

Stationor ATTCON/DESKCON

connection test diagrammed to

the right.

C.O./Tie

Line

TRK

• Connection Test-ATTCON/DESKCON

C.O./Tie

Line

ATI

TRK

ATTCON/

DESKCON

C.O. Trunk/Tie Line

ACCESS

NUMBER

ROUTE

NUMBER

TRUNK

NUMBER

NAME OF TRUNK ROUTE

CHECK

REMARKS

CHAPTER 7

Page 512

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

CONNECTION DIAGRAM

TEST TYPE

TEST ITEM

ORT Function

•

Perform the test by specifying DP/PB

an ORT using the Connection

Test-Station.

ORT

Confirm that [6-I] system

message displays as a result of

the test.

SENDER Function

Perform the test by specifying

an ORT using the Connection

Test-Station.

Confirm that [6-I] system

message displays as a result of

the test.

SND

ORT

NDA-24300

CHAPTER 7

Page 513

Issue 1

ROUTINE MAINTENANCE PROCEDURE

RST (/)

ORT

FUNCTION

SENDER

REMARKS

TRUNK NO.

PB RECEIVING DP RECEIVING

ORT0

SND0

RST No.

CHAPTER 7

Page 514

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

CONNECTION DIAGRAM

Digital Conference Function

TEST TYPE

TEST ITEM

Three-way

Conversation

• Perform the test by specifying

an 8CFT using the Connection

Test-Station.

INT / TSW

8CFT

• Confirm that [6-I] system

message displays as a result of

the test.

TSTT

FUNCTION

SPEECH

RELEASE

REMARKS

TRUNK NO.

CFT0

Speech Path for Each PIM, and Ringing Generator Unit

NO.

TEST TYPE

TEST ITEM

CONNECTION DIAGRAM

The ATTCON/

Normal speech path is confirmed

DESKCON is called by calling the attendant from a

from one station in station located in each PIM.

each PIM.

ATI

ATTCON/

DESKCON

NDA-24300

CHAPTER 7

Page 515

Issue 1

ROUTINE MAINTENANCE PROCEDURE

Speech Path for Each PIM, and Ringing Generator Unit (Continued)

NO.

TEST TYPE

TEST ITEM

CONNECTION DIAGRAM

The operator calls

the station back.

After normal speech path has

been confirmed, the attendant

calls the station back. Confirm

that the station rings.

ATI

ATTCON/

DESKCON

PWR0, 1

(RINGING)

MOUNTING LOCATION

CHECK

REMARKS

MODULE NAME UNIT NAME

PIM1

PIM2

PIM3

PIM4

CHAPTER 7

Page 516

Issue 1

NDA-24300

ROUTINE MAINTENANCE PROCEDURE

CONNECTION DIAGRAM

Attendant Console (ATTCON/DESKCON)

TEST TYPE

TEST ITEM

Call Termination Test

•

Station dials the operator

access code and confirm that

the call termination is

indicated at all the ATTCON/

DESKCON.

•

Station dials the operator

access code. An attendant

answers and speaks with the

caller. This process is repeated

at all the ATTCON/

ATI

ATTCON/

DESKCON

DESKCON.

Call Origination Test

•

Attendant originates a call to

the station by pressing LOOP

keys one after another.

ATI

ATTCON/

DESKCON

(RINGING)

NDA-24300

CHAPTER 7

Page 517

Issue 1

ROUTINE MAINTENANCE PROCEDURE

FUNCTION

CALL TERMINATION

CALL ORIGINATION

REMARKS

INCOMING CALL

INDICATION

ATTCON/

DESKCON NO.

SPEECH RELEASE SPEECH RELEASE

CHAPTER 7

Page 518

Issue 1

NDA-24300

CHAPTER 8

1. GENERAL

MAINTENANCE COMMANDS

This chapter explains various commands and list up commands which are used in the system administrative

management procedure. The table below shows the list of commands.

Table 8-1 Command List

COMMAND

COMMAND FULL NAME

Assignment of Line Load Control

REMARKS

ALLC

ALMG

A T RF

Assignment of Alarm Grade Data

Assignment of Traffic Measurement Order

Assignment of Traffic Measurement Order for Fusion Network

Back Up One-Touch Speed Call Memory Data

Continuous Assignment of Station Data

Continuous Assignment of Alternative Route Restriction

Continuous Assignment of Alternative Route Restriction for NDM

Continuous Assignment of Trunk Data

Control of Broadcasting for NDM

C A T K

Change of Common Signaling Channel Equipment

Change of System Mode

Control Message Waiting Lamp

Control Message Waiting Lamps – Telephone Number

Controlled Alternate PRSCs

CSCL

Continuous Change of Station Class

Continuous Change of Station Number

Display of Call Block Entry Data

Display of Connection Trunk LENS Data for LDM

Display of Connection Status

Display of System Message Details

Display of Program Issue

DLEN

DLSL

Display of LENS Data

Display of Lockout Station - LENS

DLSS

Display of Lockout Station - Number

NDA-24300

CHAPTER 8

Page 519

Issue 1

MAINTENANCE COMMANDS

COMMAND

Table 8-1 Command List (Continued)

COMMAND FULL NAME

REMARKS

DLSS_T

D L TEL

Display of Lock Out Station – Number – Telephone Number

Display of Telephone Number from LENS for LDM

Display of Telephone Number from LENS for NDM

Display of Setting Port Package

DNTEL

DPKG

DPSW

Display Package Switch Status

DSTN

Display of Station Data

Display of Telephone Number Data for NDM

Display of Terminal Traffic Data

Display of Route Traffic Data

Display of Station Peg Count Data

Display of Attendant Peg Count Data

Display of Route Peg Count Data

Display of Service Peg Count Data

Display of UCD Route Peg Count Data

Display of UCD Group Peg Count Data

Display of Station Peg Count Data

Display of Attendant Answering Peg Count Data

Display of Connection Route Peg Count Data

Display of Connection Route Traffic Data

Display of Terminal Traffic Data for Fusion Network

Display of Route Traffic Data for Fusion Network

Display of Station Peg Count Data for Fusion Network

Display of Attendant Peg Count Data for Fusion Network

Display of Route Peg Count Data for Fusion Network

Display of Service Peg Count Data for Fusion Network

Display of UCD Route Peg Count Data for Fusion Network

Display of UCD Group Peg Count Data for Fusion Network

Display of UCD Station Peg Count Data for Fusion Network

Display of Attendant Answering Peg Count Data for Fusion Network

Display of Connection Route Peg Count Data for Fusion Network

Display of Connection Route Traffic Data for Fusion Network

CHAPTER 8

Page 520

Issue 1

NDA-24300

MAINTENANCE COMMANDS

REMARKS

Table 8-1 Command List (Continued)

COMMAND FULL NAME

COMMAND

Data Control Between HDD and FDD

Data Control Between HDD and M A T

HDD_M A T _N Data Control Between HDD and M A T f or NDM

HDFP

MBCT

HDD Format of PBX

Make Busy of Connection Trunk for LDM

Make Busy of LENS

MBLE

MBPM

Make Busy of Port Microprocessor

Make Busy of Route-Logical Route Number

Make Busy of System Message Printout

Make Busy of Station – Telephone Number

Make Busy of Trunk-Continuous

Make Busy of Trunk-Continuous-Logical Route Number

Make Busy Trunk-Logical Route Number

Data Control Between Memory and HDD

MEM_HDD_N Data Control Between Memory and HDD for NDM

Port Microprocessor Back Up

Release Alarm

Release Alarm for NDM

Release Station/Trunk

RLST_T

SINZ

Release of Station/Trunk – Telephone Number

System Initialization

SPTS

Scanning of Port Status

SRTS

Scanning of Route Status

SRTS_LR

XHFD

Scanning of Route Status-Logical Route Number

X-R A Y H D or FDD Diagnosis

NDA-24300

CHAPTER 8

Page 521

Issue 1

ALLC: Assignment of Line Load Control

ALLC:

Assignment of Line Load Control

1. Functional Outline

This command is used to designate start and stop of line load control.

2. Parameters

Input data

ALL/ONE: Operation Mode Selection

O/A=Only One LP/All LPs 2 is not valid for 1IMG-system.

LP:

Local Partition (LP) Number Note

The data is designated as 00 for 1IMG-system.

Line Load Control Status (0-3)

STATUS:

0=Stop Line Load Control

1=Start Line Load Control

2=Automatic Line Load Control is in effect (display only)

3=Status of all LPs do not match (display only)

Note: This parameter appears when “O (only on LP)” is set in “ALL/ONE” input data.

CHAPTER 8

NDA-24300

Page 522

Issue 1

ALMG: Assignment of Alarm Grade Data

ALMG:

Assignment of Alarm Grade Data

1. Functional Outline

This command is used to make a flexible change of system message output grades. Thus, the PBX user can

give a proper alarm grade to each system message according to their requirements. When no data is assigned,

the default alarm grades are automatically adopted.

Note: This command cannot change the alarm grade for system message “6-A.”

2. Parameters

Input data

FK:

FI:

Fault Message Kind (0-7, 10-17, 20-27, 30-37)

Fault Message Index (A-Z)

LMP:

Fault Message Lamp Data (0-3)

0=Lamp OFF

1=SUP Lamp ON

2=MN Lamp ON

3=MJ Lamp ON

GRD:

Printout Grade (0-3)

TYPE:

Listup Type

1=All Data

2=Changed Data

3=Default Data

SYSM GRD: System Message Output Grade

Note: 0=All Messages

1=Not Used

2=MN/MJ Grade Messages

3=MJ Grade Messages

Note: When using ALMG command for system message output grade assignment, be sure to set “ASYD, SYS

1, Index 91, b2 and b3 = 0, 0”. For more information, refer to the Office Data Specifications.

NDA-24300

CHAPTER 8

Page 523

Issue 1

ATRF: Assignment of Traffic Measurement Order

ATRF:

Assignment of Traffic Measurement Order

1. Functional Outline

This command is used to assign and delete traffic measurement programs. A request for traffic measurement

is performed when a traffic measurement instruction has been assigned by this command. The collected traffic

measurement data can be stored on the HD of the MAT, which can be designated on the basis of traffic

measurement type.

2. Parameters

Input Data

TYPE:

Type of Traffic Measurement (1-19) (See T a ble 8-2.)

Table 8-2 Type ofTraffic Measurement Explanation

DATA

MEANING

DATA

MEANING

Terminal Traffic

Route Traffic

Station Peg Count

ATT Peg Count

Route Peg Count

Service Peg Count

UCD Route Peg Count

UCD Station Peg Count

Connection Route Peg Count

UCD Group Peg Count

ATT Answering Peg Count

Connection Route Traffic

PORT:

INTERVAL:

Traffic Information Output Terminal Number (0-7:IOC, 8:LAN, 9:NMS)

Output interval (0, 30-120)

Assign the data (30-120) in 10 minute increments. When assigning 0 (available

when any of TYPE 3-18 is selected), instead specify your desired output time in

the “OUTPUT HOUR/MINUTE” parameters below.

START HOUR

START MINUTE

END HOUR

END MINUTE

OUTPUT HOUR:

OUTPUT MINUTE:

START RT:

END RT:

START C_RT:

END C_RT:

This data is valid only when INTERVAL=0.

This data is valid only when INTERVAL= 0.

Start External Route Number (available when TYPE 2/5/8 is selected)

End External Route Number (available when TYPE 2/5/8 is selected)

Start Connection Route Number (available when TYPE 18/19 is selected)

End Connection Route Number (available when TYPE 18/19 is selected)

Note 1: Assign the traffic measurement time period between START HOUR/MINUTE and END HOUR/

MINUTE longer than an hour. Also, if the measurement should be executed throughout a day, assign

the same data in both START HOUR/MINUTE and END HOUR/MINUTE parameters.

Note 2: Traffic Type 15 only works on Ring DownTrunks.

CHAPTER 8

NDA-24300

Page 524

Issue 1

ATRFN: Assignment of Traffic Measurement Order for Fusion Network

1. Functional Outline

This command is used to assign and delete traffic measurement programs available on the Ethernet. A request

for traffic measurement is performed on a network basis when a traffic measurement instruction has been

assigned by this command. The collected traffic measurement data can be stored on the HD of the MAT

(connected to the NCN: Network Control Node), which can be designated on the basis of traffic measurement

type. Note that this command can be used at the NCN only.

2. Parameters

Input Data

TYPE:

Type of Traffic Measurement (1-19) (See T a ble 8-3)

Table 8-3 Type ofTraffic Measurement Explanation

DATA

MEANING

DATA

MEANING

Terminal Traffic

Route Traffic

Station Peg Count

ATT Peg Count

Route Peg Count

Service Peg Count

UCD Route Peg Count

UCD Station Peg Count

Connection Route Peg Count

UCD Group Peg Count

ATT Answering Peg Count

Connection Route Traffic

PORT:

INTERVAL:

Traffic Information Output Terminal Number (0-7: IOC, 8: LAN, 9:NMS)

Output interval (0, 30-120)

Assign the data (30-120) in 10 minute increments. When assigning 0 (available

when any of TYPE 3-18 is selected), instead specify your desired output time in

the “OUTPUT HOUR/MINUTE” parameters below.

Note 2, Note 3

START HOUR

START MINUTE

END HOUR

END MINUTE

OUTPUT HOUR:

OUTPUT MINUTE:

START RT:

END RT:

START C_RT:

END C_RT:

Note 2, Note 3

This data is valid only when INTERVAL=0.

Start External Route Number (available when TYPE 2/5/8 is selected)

End External Route Number (available when TYPE 2/5/8 is selected)

Start Connection Route Number (available when TYPE 18/19 is selected)

End Connection Route Number (available when TYPE 18/19 is selected)

Note 1: The selected traffic measurement data, except for TYPE 1 (Terminal Traffic), is collected with the

whole network systems as a single unit.

Note 2: When time difference exists between the nodes, confirm that the related time difference data, based on the

UCT (Universal Coordinated Time) standard, has been assigned at each node via the ATDF command.

Note 3: Assign the traffic measurement time period between START HOUR/MINUTE and END HOUR/

MINUTE longer than an hour. Also, if the measurement should be executed throughout a day, assign

the same data in both START HOUR/MINUTE and END HOUR/MINUTE parameters.

Note 4: If the data for this command is once assigned, the node-level data by the ATRF command is not

cleared, but loses its validity (the network-level data takes precedence).

NDA-24300

CHAPTER 8

Page 525

Issue 1

BOSD: Back Up One-Touch Speed Call Memory Data

BOSD:

Back Up One-Touch Speed Call Memory Data

1. Functional Outline

•

Save Function

Saves the data residing in the One-Touch Speed Call Memory of DLC/ELC card onto a floppy disk.

Verify Function

Verifies the One-Touch Speed Call Memory data saved on the floppy disk with the data residing in the

One-Touch Speed Call Memory of DLC/ELC card.

•

Load Function

Loads the One-Touch Speed Call Memory data saved in the floppy disk into the One-Touch Speed Call

Memory of DLC/ELC card.

2. Parameters

Input data

Direction Select:

PBX Memory to MAT

MAT to PBX Memory

Verify MAT against MEM

Data Type Selection:

by Station

by LEN

Begin TN:

End TN:

Begin STN:

End STN:

Begin LEN:

End LEN:

Auto Verify Afterward:

Click ON=Checked

OFF=Unchecked

File Name and Path

Note 1: When by Station is designated

Note 2: When by LEN is designated

CHAPTER 8

NDA-24300

Page 526

Issue 1

CADSD: Continuous Assignment of Station Data

1. Functional Outline

This command can assign/delete many station data simultaneously which have consecutive numbers.

2. Parameters

Input Data

Type:

Assign/Delete

[When Assign is selected in the Type selection list box]

TN(START):

TN(END):

STN(START):

STN(END):

STEP:

Start Tenant Number

End Tenant Number

Start Station Number [Max. 6 digits] Note 1

End Station Number [Max. 6 digits] Note 1

Station Count-up Step

If using * and # → [1-12]

If not using * and # → [1-10]

First Line Equipment Number [6 digits]

Last Line Equipment Number [6 digits]

First Group Number [0-31]

Last Group Number [0-31]

First Level Number [0-7]

Last Level Number [0-7]

LENS(START):

LENS(END):

GROUP(START):

GROUP(END):

LEVEL(START):

LEVEL(END):

Note 1: In the bottom part of the display, a check box is provided to determine whether to use "*" and "#" as

a part of the Station Number. If necessary, check the box.

Note 2: In the parameter here, specify the size of increment between the consecutive station numbers to be

assigned. See the example below:

Example:

Inputdata

STN(START)=100

STN(END)=200

STEP=10

Result

Station Number is assigned by 10 increments:

∇ When * and # are not used as part of STN

100 110 120 130 ... 190 200

∇ When * and # are used as part of STN

10* 118 126 134 ... 1** 1#8

→

NDA-24300

CHAPTER 8

Page 527

Issue 1

CADSD: Continuous Assignment of Station Data

TEC:

Telephone Equipment Class [1-31]

1=DP (10pps)

3=DP/PB

2=PB

4=DP (20pps)

term

5-11=Not used

13=Data Terminal via D

15=CAS Line

17=Not used

12=D

term

14=Hot Line

16=Data Terminal via Data Module

term

18=Virtual Line Appearance (for D

23=ISDN Terminal

Multi-Line)

19-22=Not used

24-26=Not used

28-31=Not used

27=8 Conference Equipment

RSC:

SFC:

Route Restriction Class [0-15]

Service Feature Class [0-15]

Buttons

Execute:

Cancel:

Exit:

Click to make the input data valid.

Click to cancel the input data.

Click to exit this command.

Display Data (after “Execute” button is pressed)

TN:

Tenant Number

STN:

Assigned Station Number

Line Equipment Number

Data Entry Result

LENS:

STATUS:

OK=Data Assignment is successful Note

Note: If not OK (i.e. the data entry is not successful), related error message is displayed here.

CHAPTER 8

NDA-24300

Page 528

Issue 1

CADSD: Continuous Assignment of Station Data

When Delete is selected in the Type selection list box

Input Data

TN(START):

TN(END):

STN(START):

STN(END):

STEP:

First Tenant Number

Last Tenant Number

First Station Number [Max. 6 digits]

Last Station Number [Max. 6 digits]

Station Count-up Step Note 1

If using * and # → [1-12]

If not using * and # → [1-10]

Note 1: In this parameter, specify the size of increment between the consecutive station numbers to be deleted.

See the example below:

Example:

Inputdata

STN(START)=100

STN(END)=200

STEP=10

Result

Station Number is deleted by 10 increments:

∇ When * and # are not used as part of STN

100 110 120 130 ... 190 200

∇ When * and # are used as part of STN

10* 118 126 134 ... 1** 1#8

→

Buttons

Execute:

Click to delete the input data.

Click to cancel the deletion.

Click to exit this command.

Cancel:

Exit:

Display Data

TN:

Tenant Number

STN:

Station Number

STATUS:

Result of Deletion Note 2

Note 2: When the deletion is successful, OK is displayed here. Otherwise (i.e. the deletion is rejected), related

error message is displayed.

NDA-24300

CHAPTER 8

Page 529

Issue 1

CARR: Continuous Assignment of Alternative Route Restriction

CARR:

Continuous Assignment of Alternative Route Restriction

1. Functional Outline

This command is used to continuously assign/delete the restriction data of relay connections between the

outgoing route and the incoming route.

2. Parameters

Input Data

TYPE:

Assign/Delete

ICRT (START/END):

OGRT (START/END):

ARI A-RES:

Incoming Route Logical Number (External Route only)

Outgoing Route Number (External Route only)

Restriction Data for Alternative Route Index-A [0/1]

Restriction of the trunk-to-trunk (tandem) connection via ATTCON or station

when a C.O./Tie Line call terminates.

0=Alternate routing is restricted.

1=Alternate routing is allowed.

ARI D-RES:

Restriction Data for Alternative Route Index-D [0/2]

Restriction of the trunk-to-trunk (tandem) connection by Direct Dial Access

from a station when a C.O./Tie Line call terminates.

0=Alternate routing is restricted.

1=Alternate routing is allowed.

2=Toll Restriction is restricted.

Display Data

ICRT:

Incoming Route

OGRT:

STATUS:

Outgoing Route

OK or error message is displayed.

CHAPTER 8

NDA-24300

Page 530

Issue 1

CARRN: Continuous Assignment of Alternative Route Restriction for NDM

CARRN : Continuous Assignment of Alternative Route Restriction for NDM

1. Functional Outline

This command is used to continuously assign/delete the restriction data of relay connections between the

outgoing route and the incoming route. The data assigned by this command is written in the Network Data

Memory (NDM) of the Network Control Node (NCN), updating the NDM at each Local Node (LN).

2. Parameters

Input Data

TYPE:

Assign/Delete

IC LGRT (START/END): Incoming Logical Route Number [1-899]

OG LGRT (START/END): Outgoing Logical Route Number [1-899]

ARI A-RES:

Restriction Data for Alternative Route Index-A [0/1]

Restriction of the trunk-to-trunk (tandem) connection via ATTCON or sta-

tion when a C.O./Tie Line call terminates.

0=Alternate routing is restricted.

1=Alternate routing is allowed.

ARI D-RES:

Restriction Data for Alternative Route Index-D [0/2]

Restriction of the trunk-to-trunk (tandem) connection by Direct Dial Access

from a station when a C.O./Tie Line call terminates.

0=Alternate routing is restricted.

1=Alternate routing is allowed.

2=Toll Restriction is restricted.

Display Data

IC LGRT:

OG LGRT:

STATUS:

Incoming Logical Route Number [1-899]

Outgoing Logical Route Number [1-899]

OK or error message is displayed.

NDA-24300

CHAPTER 8

Page 531

Issue 1

CATK: Continuous Assignment of Trunk Data

CATK:

Continuous Assignment of Trunk Data

1. Functional Outline

This command can assign/delete many trunk data simultaneously which have consecutive numbers.

2. Parameters

Type/KIND Note Note::Assign/Delete

Note: Type

KIND

[When “Assign” is selected in the “Type/KIND” selection list box]

Input Data

RT:

Route Number

TK (START):

TK (END):

STEP:

LENS (START):

LENS (END):

TN:

First Trunk Number [1-768]

Last Trunk Number [1-768]

Trunk Count-up Step [1-10] Note 1

First Line Equipment Number [6 digits]

Last Line Equipment Number [6 digits]

Tenant Number

RSC:

SFC:

Route Restriction Class [0-15] Note 2

Service Feature Class [0-15] Note 2

First Group Number [0-31]

Last Group Number [0-31]

First Level Number [0-7]

GROUP (START):

GROUP (END):

LEVEL (START):

LEVEL (END):

TYPE:

Last Level Number [0-7]

Count-up Type [1-6] Note 3

1 = LEVEL→ GROUP→ UNIT

2 = LEVEL→ UNIT → GROUP

3 = GROUP→ UNIT → LEVEL

4 = GROUP→ LEVEL→ UNIT

5 = UNIT → LEVEL→ GROUP

6 = UNIT → GROUP→ LEVEL

Note 1: In the parameter here, specify the size of increment between the consecutive trunk numbers to be as-

signed. See the example below:

Example:

Inputdata

TK(START)=1

TK(END)=21

STEP=2

Result

Trunk Number is assigned by 2 increments:

→

... 19

Note 2: Data entry for this parameter is necessary when “RT” is “901” or “915.”

Note 3: “TYPE” parameter here determines how to arrange the trunk data. See [Details on Trunk Arrange-

ment “TYPE” ] (later pages) for details.

CHAPTER 8

NDA-24300

Page 532

Issue 1

CATK: Continuous Assignment of Trunk Data

Buttons

Execute:

Click to make the input data valid.

Click to cancel the input data.

Click to exit this command.

Cancel:

Exit:

Display Data

TK:

Assigned Trunk Number

Line Equipment Number

Data Entry Result

LENS:

STATUS:

OK=Data Assignment is successful Note 4

Note 4: If not OK (i.e. the data entry is not successful), related error message is displayed here.

NDA-24300

CHAPTER 8

Page 533

Issue 1

CATK: Continuous Assignment of Trunk Data

[When “Delete” is selected in the “Type/KIND” selection list box]

Input Data

RT:

Route Number

TK(START):

TK(END):

STEP:

First Trunk Number [1-768]

Last Trunk Number [1-768]

Trunk Count-up Step [1-10] Note 1

Buttons

Execute:

Cancel:

Click to delete the input data.

Click to cancel the deletion.

Click to exit this command.

Exit:

Display Data

TK:

Trunk Number

STATUS:

Result of Deletion

OK=Deletion Success Note 2

Note 1: In the parameter here, specify the size of increment between the consecutive trunk numbers to be de-

leted. See the example below:

Example:

Inputdata

TK(START)=1

TK(END)=21

STEP=2

Result

Trunk Number is deleted by 2 increments:

→

... 19

Note 2: When the deletion is successful, “OK” is displayed here. Otherwise (i.e. the deletion is rejected), re-

lated error message is displayed.

CHAPTER 8

NDA-24300

Page 534

Issue 1

CATK: Continuous Assignment of Trunk Data

[Details on Trunk Arrangement “TYPE”]

When assigning the consecutive trunk data by using the CATK command, you must select the trunk

arrangement type (1-6) in the “TYPE” parameter. See the detailed examples below:

The following are the examples when the 16 COT circuit cards are accommodated as shown below.

U=2

U=3

16 16

PIM C/E

16 16

PIM C/E

U=0

U=1

TYPE=1 (Level → Group → Unit)

Trunk data is arranged in the following numerical order.

U=2

U=3

Slot No.

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

56 64

72 80 88 96

49 57

16 24 32

65 73 81 89

40 48

1MG

17 25

33 41

Level No.

02 03 04 05

00 01 02 03

Group No.

U=0

U=1

NDA-24300

CHAPTER 8

Page 535

Issue 1

CATK: Continuous Assignment of Trunk Data

TYPE=2 (Level → Unit → Group)

Trunk data is arranged in the following numerical order.

U=2

U=3

Slot No.

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

24 56

32 64 80 96

17 49

40 72 88

25 57 73 89

16 48

1MG

33 65 81

Level No.

02 03 04 05

00 01 02 03

Group No.

U=0

U=1

U=3

TYPE=3 (Group → Level → Unit)

Trunk data is arranged in the following numerical order.

U=2

Slot No.

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

63 64

51 52

49 50

47 48

1MG

35 36

33 34

Level No.

02 03 04 05

00 01 02 03

Group No.

U=0

U=1

CHAPTER 8

Page 536

Issue 1

NDA-24300

CATK: Continuous Assignment of Trunk Data

TYPE=4 (Group → Unit → Level)

Trunk data is arranged in the following numerical order.

U=2

U=3

Slot No.

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

91 92

19 20

89 90

1MG

17 18

Level No.

02 03 04 05

00 01 02 03

Group No.

U=0

U=1

U=3

TYPE=5 (Unit → Level → Group)

Trunk data is arranged in the following numerical order.

U=2

Slot No.

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

31 63

32 64 80 96

40 68 84

36 66 82

1MG

29 61 79 95

30 62

37 67 83

33 65 81

Level No.

02 03 04 05

00 01 02 03

Group No.

U=0

U=1

NDA-24300

CHAPTER 8

Page 537

Issue 1

CATK: Continuous Assignment of Trunk Data

TYPE=6 (Unit → Group → Level)

Trunk data is arranged in the following numerical order.

U=2

U=3

Slot No.

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

LV7

LV6

LV5

LV4

LV3

LV2

LV1

LV0

87 91

89 92 94 96

15 19

16 20 22 24

10 12

1MG

85 89 93 95

86 90

13 17 21 23

14 18

Level No.

02 03 04 05

00 01 02 03

Group No.

U=0

U=1

CHAPTER 8

Page 538

Issue 1

NDA-24300

CBCN: Control of Broadcasting for NDM

CBCN:

Control of Broadcasting for NDM

1. Functional Outline

This command is used to specify the destination of NDM data broadcast from the NCN. This command is

available only at the NCN (Network Control Node).

2. Parameters

Input Data

TYPE:

FPC:

ALL (All the Nodes)/ONE (One designated Node)

FPC of the designated Node Note

Broadcasting Interval

Interval:

Note: This parameter appears when ONE is selected at “TYPE” parameter.

NDA-24300

CHAPTER 8

Page 539

Issue 1

CCSE: Change of Common Signaling Channel Equipment

CCSE:

Change of Common Signaling Channel Equipment

1. Functional Outline

This command is used to set/reset the make busy state of CCH circuit card.

2. Parameters

CCH LENS:

Line Equipment Number of CCH circuit card [5 digits]

MG=XX, UNIT=X, GROUP=XX

Link Status [0-2]

LINK:

0=Link Open

1=Link Close

2=Not Available

MB:

Make Busy Information [0-2]

0=Make Idle

1=Make Busy

2=Not Available

Note: This command cannot be used for the ISDN-related circuit card (such as PRT, DCH card).

CHAPTER 8

NDA-24300

Page 540

Issue 1

CDBU: Change of Dch Backup

CDBU:

Change of Dch Backup

1. Functional Outline

This command is used to execute the D-channel route changeover, associated with the D-CHANNEL

BACKUP-PRI feature (for AT&T/NT/N-ISDN2).

2. Parameters

Input Data

MG:

Module Group Number [00-07] Note

CNT:

Number of Dch Backup Route [1-32] Note

Buttons

Get:

Change:

Stop:

Click to get information on the Dch Routes.

Click to execute the Dch route changeover.

Click to cancel the Dch route changeover.

Click to exit this command.

Exit:

Display Data

RT:

External Route Number

STS0:

Primary-side DCH Status [ACT/ST-BY/OOS (out of service)]

Backup-side DCH Status [ACT/ST-BY/OOS (out of service)]

Primary DCH LENS (6 digits)

STS1:

P-LENS:

B-LENS:

CHG-STS:

Backup DCH LENS (6 digits)

Change Status [Completed/Executing]

Note: Data entry procedure by this command is as follows:

1. Specify the Module Group No. in the “MG” parameter.

2. Click the “Get” button. Then, the related Dch data appears in the display data field.

3. Referring to the display data, enter the “CNT” No. attached to the Dch to be changed over.

4. Click the “Change” button.

→ Now, the Dch changeover starts automatically.

NDA-24300

CHAPTER 8

Page 541

Issue 1

CMOD: Change of System Mode

CMOD:

Change of System Mode

1. Functional Outline

This command is used to execute ACT/ST-BY change of the processor (CPU)/TSW and display the status of

CPU/CLK/TSW.

2. Parameters

Input Data

TYPE:

Type of Process (1,2)

1/2=Change Operating Mode/Make Busy of TSW

DEVICE:

Device to be changed (1,2)

1=CPU

2=TSW

SW:

Type of Switch

1=TSW (fixed)

SYSTEM:

System of Switch (0,1)

0/1=System 0/System 1

Note 1: This parameter appears only when TYPE=1.

Note 2: When the CPU mode change is executed, the MAT (TCP/IP) is once disconnected. Then, log in to the system

again.

Note 3: This parameter appears only when TYPE=2.

Display data

Status:

CPU 0/1, TSW 0/1, PLO 0/1 (0-3)

0=Not Mounted

1=Standby

2=ACT

3=Make-Busy

CHAPTER 8

NDA-24300

Page 542

Issue 1

CMWL: Control Message Waiting Lamp

CMWL:

Control Message Waiting Lamp

1. Functional Outline

This command is used to indicate ON/OFF status and to control the Message Waiting Lamp ON/OFF (MW

term

Lamp) at the station. If the station is a D , this command can also be used to control Message Waiting

term

Display on the D

2. Parameters

Input data

TYPE:

Type of Input (1,2)

1/2=Designation by Station Number/Designation by LEN

TN:

STN:

LENS:

MCI:

Maximum 5 digits for Business system, and 6 digits for Hotel system. Note 1

Message Center MW Status (0,1)

0/1=OFF/ON

ATT:

Attendant Console MW Status (0,1) See the parameter MCI.

STA:

Station MW Status (0,1)

See the parameter MCI.

VMM:

MWLAMP:

Voice Mail Module MW Status (0,1)See the parameter MCI.

MW Lamp Status

0/1=OFF/ON

Note 1: This parameter appears when TYPE= “1.”

Note 2: This parameter appears when TYPE= “2.”

NDA-24300

CHAPTER 8

Page 543

Issue 1

CMWL_T: Control Message Waiting Lamps – Telephone Number

1. Functional Outline

This command is used to control/display the Message Waiting Lamp’s ON/OFF status, by using Telephone

term

Numbers. When the station is a D , this command can also be used to control the Message Waiting Lamp

Display. This command is available at NCN (for Fusion network) only.

2. Parameters

Input Data

TYPE:

UGN:

TELN:

LENS:

MWLAMP:

MCI:

Designation by Telephone Number/Designation by LEN

User Group Number Note 1

Telephone Number (max. 16 digits) Note 1

Line Equipment Number

MW Lamp Status OFF/ON

Message Center MW Status OFF/ON

Attendant Console MW Status OFF/ON

Station MW Status OFF/ON

ATT:

STA:

VMM:

Voice Mail Module MW Status OFF/ON

Note 1: This parameter is valid when Type =1 is selected.

Note 2: This parameter is valid when Type =2 is selected.

Display Data

FPC:

TN:

Fusion Point Code (1-253)

Tenant Number

STN:

Physical Station Number (max. 5 digits for Business/max. 6 digits for Hotel system)

Note 3: These parameters are for display only.

Buttons

Get:

Set:

Exit:

Click to get information on the MW status.

Click to execute the assigned MW lamp control.

Click to exit this command.

CHAPTER 8

Page 544

Issue 1

NDA-24300

CPRS: Controlled Alternate PRSCs

CPRS:

Controlled Alternate PRSCs

1. Functional Outline

This command is necessary for the Controlled Alternate PRSCs function. It either selects the class used

between two priority restriction classes (Normal or Urgent), or indicates the class used. This command is

allowed only when bit1 of SYS 1, INDEX 59 is “1” (Controlled Alternate PRSCs in service).

2. Parameters

N/U:

Priority Restriction Class [N/U]

N=Normal

U=Urgent

NDA-24300

CHAPTER 8

Page 545

Issue 1

CSCL: Continuous Change of Station Class

CSCL:

Continuous Change of Station Class

1. Functional Outline

This command can change the station class information (TEC, RSC, SFC) en bloc by designating the range of

the station number.

2. Parameters

Input Data

TN:

Tenant Number

STN(START):

STN(END):

TEC(OLD):

TEC(NEW):

RSC(OLD):

RSC(NEW):

SFC(OLD):

SFC(NEW):

First Station Number [0-9, #, * (Max. 6 digits)]

Last Station Number [0-9, #, * (Max. 6 digits)]

Telephone Equipment Class before change [1-31] Note 2, Note 3

Telephone Equipment Class after change [1-31] Note 2

Route Restriction Class before change [0-15]

Route Restriction Class after change [0-15]

Service Feature Class before change [0-15]

Service Feature Class after change [0-15]

Note 1: In the bottom part of the display, a check box is provided to determine whether to use "*" and "#" as

a part of the Station Number. If necessary, check the box.

Note 2: Details on TEC (Telephone Equipment Class) are shown below:

1=DP (10pps)

3=DP/PB

5-11=Not used

13=Data Terminal via D

15=CAS Line

17=Not used

19-22=Not used

24-26=Not used

28-31=Not used

2=PB

4=DP (20pps)

12=D

14=Hot Line

16=Data Terminal via Data Module

18=Virtual Line Appearance (for D

23=ISDN Terminal

term

Multi-Line)

27=8 Conference Equipment

Note 3: If you want to change all classes of all specified stations, enter “**” for this parameter.

Buttons

Execute:

Cancel:

Exit:

Click to make the input data valid.

Click to cancel the input data.

Click to exit this command.

Display Data

STN:

Station Number

STATUS:

Data Entry Result

OK=Data Assignment is successful Note

Note: If not OK (i.e. the data entry is not successful), related error message is displayed here.

CHAPTER 8 NDA-24300

Page 546

Issue 1

CSTN: Continuous Change of Station Number

CSTN:

Continuous Change of Station Number

1. Functional Outline

This command can change the consecutive station numbers en bloc by designating the station number range.

2. Parameters

Input Data

TN:

Tenant Number

OLD STN(START):

OLD STN(END):

NEW STN(START):

NEW STN(END):

First Station Number before change [0-9, #, * (Max. 6 digits)] Note

Last Station Number before change [0-9, #, * (Max. 6 digits)] Note

First Station Number after change [0-9, #, * (Max. 6 digits)] Note

Last Station Number after change [0-9, #, * (Max. 6 digits)]

Note: In the bottom part of the display, a check box is provided to determine whether to use “*” and “#” as

a part of the Station Number. If necessary, check the box.

Buttons

Execute:

Cancel:

Click to make the input data valid.

Click to cancel the input data

Click to exit this command.

Exit:

Display Data

OLD STN:

NEW STN:

STATUS:

Station Number before change

Station Number after change

Data Entry Result

OK=Data Assignment is successful Note

Note: If not OK (i.e. the data entry is not successful), related error message is displayed here.

NDA-24300

CHAPTER 8

Page 547

Issue 1

DCBD: Display of Call Block Entry Data

DCBD:

Display of Call Block Entry Data

1. Functional Outline

This command is used to display the following Call Block data, assigned to a station:

•

Number of station/trunk whose call is to be blocked (in the remainder of this page, denoted as “Restriction

Number”)

Registered “Restriction Numbers” in total

These data can be obtained by entering any of the station’s Telephone Number (TYPE 1), Physical Station

Number (TYPE 2) or LENS (TYPE 3) in the parameters below:

2. Parameters

Input Data

TYPE: Selection of Input Data Type

TYPE 1 (Input Data = UGN, TELN)

TYPE 2 (Input Data = FPC, TN, STN) Note

TYPE 3 (Input Data = FPC, LENS)

READ (button to view the Display Data)

EXIT (button to exit)

Note: When using this command, first choose the input data type (Type 1 - 3) in the “TYPE” selection list box.

Then the following parameters appear, according to the selected data type.

•

When TYPE 1 is selected : UGN (User Group Number)

TELN (Telephone Number [Max.16 digits])

When TYPE 2 is selected : FPC (Fusion Point Code [1-253])

TN (Tenant Number [Max.3 digits])

STN (Physical Station Number [Max.6 digits])

•

When TYPE 3 is selected : FPC

(Fusion Point Code [1-253])

LENS (Line Equipment Number)

CHAPTER 8

NDA-24300

Page 548

Issue 1

DCBD: Display of Call Block Entry Data

Display Data

CNT: Registered “Restriction Numbers” in total (1-5)

DC: Each “Restriction Number”

•

When Physical Station Number is registered – Max. 6 digits

When Telephone Number is registered – Max. 16 digits

When Trunk Call Number is registered – Max. 32 digits

NDA-24300

CHAPTER 8

Page 549

Issue 1

DCEN: Display of Connection Trunk LENS Data for LDM

DCEN:

Display of Connection Trunk LENS Data for LDM

1. Functional Outline

This command is used to display the registered connection trunk/route data by designating LENS.

2. Parameters

Input Data

C_LENS:

Display Data

C_RT:

Line Equipment Number [6 digits]

Connection Route Number [1-1023]

Connection Trunk Number [1-4095]

External Route Number

C_TK:

RT:

TK:

Trunk Number [1-255]

TN:

Tenant Number

CHAPTER 8

NDA-24300

Page 550

Issue 1

DCON: Display of Connection Status

DCON:

Display of Connection Status

1. Functional Outline

This command displays the connection status of the station and trunks. If the specified station or trunk is busy,

the connected party is displayed.

2. Parameters

Input data

Type:

Kind of Connection Status (1-4)

1=Station of Connection Status

2=Trunk of Connection Status

3=LENS of Connection Status

4=Connection Trunk of Connection Status (Fusion Network)

TN:

STN:

RT:

Maximum number of digits is 5 for Business system, and 6 for Hotel system. Note 1

TK:

LEN:

C_RT:

C_TK:

Connection Route Number (1-1023) Note 4

Connection Trunk Number (1-4095) Note 4

Note 1: This data is valid when Type=1.

Note 2: This data is valid when Type=2.

Note 3: This data is valid when Type=3.

Note 4: This data is valid when Type=4.

NDA-24300

CHAPTER 8

Page 551

Issue 1

DFTD: Display of System Message Details

DFTD:

Display of System Message Details

1. Functional Outline

This command is necessary to print the system messages detected by the Fault Diagnostic programs.

When the fault scanning (Scanning PBX) is effective, the MAT can scan the PBX status by polling every 20

sec, (default setting is Effective.)

If the PBX has faults, this command executes automatically.

2. Parameters

Input data

New/Old

Show Details:

YES/NO

CHAPTER 8

NDA-24300

Page 552

Issue 1

DISS: Display of Program Issue

DISS:

Display of Program Issue

1. Functional Outline

This command outputs to the printer and displays at the MAT, the program information (version, issue No. and

date) in the main memory, and the program information (SP No.and issue No.) in the port microprocessor

memory mounted in each circuit card in the PBX.

2. Parameters

Input data

Type of Issue:

Main Memory

Port Microprocessor

Module Group: Note 1

Unit:

Display data

Type:

Main Memory

Boot ROM

ACDP Note 2

Version:

Issue:

Date:

Group:

SP No.:

Issue:

00-23

4 digits

ASCII 2 digits

Note 1: This data is valid when Port Microprocessor is designated.

Note 2: This data is valid when Main Memory is designated.

NDA-24300

CHAPTER 8

Page 553

Issue 1

DLEN: Display of LENS Data

DLEN:

Display of LENS Data

1. Functional Outline

This command displays the data (station data or trunk data) assigned for a designated LEN. For Hotel system,

Room Class and Floor Service Data [Annex (ANX), Ground/Underground (G), Floor (FLR)] displays also.

2. Parameters

Input data

LENS

Display data

STN:

TEC:

Maximum 6 digits

Telephone Equipment Number (1-31) (See Table 8-4.)

Table 8-4 Telephone Equipment Number Explanation

DATA

MEANING

DATA

MEANING

DP (10pps)

DP/PB

DP (20 pps)

D^term

5-11

Not used

Data Terminal via D^term

Hot Line

CAS Line

Data Terminal via Data Module

ISDN Terminal

Not used

Virtual Line Appearance

(for D^termMulti-Line)

19-22

Not used

24-26

28-31

Not used

Eight Conference Equipment

RSC:

SFC:

Route Restriction Class (0-15)

Service Feature Class (0-15)

ROOM CLASS: (0-15)

ANX: Annex (0-3)

CHAPTER 8

Page 554

Issue 1

NDA-24300

DLEN: Display of LENS Data

0=Ground

1=Underground

FLR:

RT:

Floor (1-127)

Internal Route Number (See T a ble 8-5.)

Table 8-5 Internal Route Number Explanation

DATA

MEANING

Attendant Console

DATA

MEANING

Originating Register Trunk

901

903

902

904

906

908

Incoming Register Trunk

Sender Trunk DP/PB

AMP

MF Receiver

905

PB Receiver for Automated Attendant Service

Not used

907

909

Three-Way Conference Trunk

Three-Way Conference Trunk for ATTCON

Night Attendant Console

MFC Sender

910, 911 Not used

913

914

916

918

Not Used

915

MFC Register

Not used

917

919-926

929

Modem

927, 928 Not used

930 Rate Adapter Conversion Trunk

Data Signaling Trunk-Option

Not used

931-947

C_RT:

C_TK:

Connection Route Number (1-1023)

Connection Trunk Number (1-4095)

NDA-24300

CHAPTER 8

Page 555

Issue 1

DLSL: Display of Lockout Station - LENS

DLSL:

Display of Lockout Station - LENS

1. Functional Outline

This command prints the LENS of stations in lockout state.

2. Parameters

Input data

Type:

Type of Printout (1-3)

1=Printout of all LEN in lockout

2=Printout of locked out LEN in the designated Module Group

3=Printout of locked out LEN in the designated Unit

MG:

Note 1, Note 2

UNIT:

Note 1: The parameter is valid only whenType=2.

Note 2: The parameter is valid only whenType=3.

Display data

LENS

CHAPTER 8

NDA-24300

Page 556

Issue 1

DLSS: Display of Lockout Station - Number

DLSS:

Display of Lockout Station - Number

1. Functional Outline

This command prints the stations in lockout state by station number.

2. Parameters

Input data

Type:

Type of Printout (1-3)

1=Printout of all lockout stations

2=Printout of lockout stations by tenant

3=Printout of lockout stations within a specified range of station number.

TN:

Note 1, Note 2

Start STN:

End STN:

Maximum 6 digits

Note 1: The parameter is valid only whenType=2.

Note 2: The parameter is valid only whenType=3.

Display data

CNT:

Count

STN

LENS

NDA-24300

CHAPTER 8

Page 557

Issue 1

DLSS_T: Display of Lock Out Station – Number – Telephone Number

1. Functional Outline

This command is used to print out stations in lockout state, by using Telephone Numbers. This command is

available at NCN (for Fusion network) only.

2. Parameters

Input Data

TYPE:

Printout of all lockout stations

Printout of lockout stations by tenant

Printout of lockout stations within a specified range of station number

UGN:

User Group Number

Note 1, Note 2

Start TELN:

End TELN:

First Telephone Number (max. 16 digits)

End Telephone Number (max. 16 digits)

Note 1: This parameter is valid when “Type =Printout of lockout stations by tenant” is selected.

Note 2: This parameter is valid when “Type =Printout of lockout stations within a specified range of station

number” is selected.

Display Data

FPC:

Fusion Point Code (1-253)

Tenant Number

TN:

Start STN:

First Physical Station Number

(max. 5 digits for Business/max. 6 digits for Hotel system)

End STN:

End Physical Station Number

(max. 5 digits for Business/max. 6 digits for Hotel system)

CNT:

Count

UGN:

TELN:

LENS:

User Group Number

Telephone Number (max. 16 digits)

Line Equipment Number

Buttons

Get:

Click to get information on the lockout status.

Click to exit this command.

Exit:

CHAPTER 8

Page 558

Issue 1

NDA-24300

DLTEL: Display of Telephone Number from LENS for LDM

DLTEL:

Display of Telephone Number from LENS for LDM

1. Functional Outline

This command, available at each Local Node (LN), is used to display the Telephone Number or other station

data by designating a specific LEN.

2. Parameters

Input Data

LENS:

Display Data

UGN:

Line Equipment Number [6 digits]

User Group Number

TELN:

TN:

Telephone Number [Max. 16 digits]

Tenant Number

STN:

Station Number [Max. 6 digits]

Telephone Equipment Class [1-31]

Route Restriction Class [0-15]

Service Feature Class [0-15]

TEC:

RSC:

SFC:

NDA-24300

CHAPTER 8

Page 559

Issue 1

DNTEL: Display of Telephone Number from LENS for NDM

1. Functional Outline

This command, available at Network Control Node (NCN) only, is used to display the Telephone Number or

other station data by designating a specific FPC and LEN.

2. Parameters

Input Data

FPC:

LENS:

Display Data

UGN:

TELN:

NID:

Fusion Point Code [1-253]

Line Equipment Number [6 digits]

User Group Number

Telephone Number [Max. 16 digits]

Network ID Note

TN:

Tenant Number

STN:

Station Number [Max. 6 digits]

Telephone Equipment Number [1-31]

Route Restriction Class [0-15]

Service Feature Class [0-15]

TEC:

RSC:

SFC:

Note: Network ID (NID) is allocated automatically when the Module Group/Unit data is assigned by the

AFMU command. Refer to the “Fusion Network System Manual” for more information.

CHAPTER 8

NDA-24300

Page 560

Issue 1

DPKG: Display of Setting Port Package

DPKG:

Display of Setting Port Package

1. Functional Outline

This command is used to display the circuit card name accommodated in each Group of a specific UNIT.

Note: When using this command, make sure that each circuit card related database files have already been

installed to your MAT. (See FLINST command for more information.)

2. Parameters

Input Data

MG:

Module Group (MG) number [00-07]

Unit (U) number [0-3]

UNIT:

Buttons

Get:

Click to get information on mounted circuit cards.

Click to exit this command.

Close:

Note: When the Input Data above is entered and the “Get” button is pressed, the related circuit card name is

displayed on a Group basis. However, if the name is not found for some reasons, the following mark

may appear in the relevant display field.

•

→ Unidentifiable firmware type.

## → Data not found in the FMID (database).

### → Group data not assigned.

→ Circuit card name not found (for the card is in make-busy state, etc.).

NDA-24300

CHAPTER 8

Page 561

Issue 1

DPSW: Display Package Switch Status

DPSW:

Display Package Switch Status

1. Functional Outline

This command is used to display the following information on a Line/Trunk or Control circuit card:

[When MAT is in On-Line Mode (=connected to the system)]

•

Current status of each switch

Explanation of each switch function

[When MAT is in Off-Line Mode (= not connected to the system)]

Explanation of each switch function

•

Note 1: When using this command, make sure that each circuit card related database files have already been

installed to your MAT. (See FLINST command for more information.)

2. Parameters

Input Data

KIND:

Display Kind (selection)

• (MAT=) On-Line Mode

• (MAT=) Off-Line Mode

Circuit Card Type (selection)

• Line Trunk Package

• Control Package

TYPE:

PMN:

PKG NAME:

LP:

Port Micro Processor Number

Circuit Card Name

Local Partition Number [00-06

(Even Number only)]

System

SYSTEM:

0=No.0 System

l=No.1 System

MG:

Module Group Number [00-07] Note 2

UNIT:

ACT/STBY:

Unit Number [0-3]

ACT/ST-BY information

0=ACT

l=ST-BY

2=Not used

No:

IOC Card Number [0/1]

Note 2: This parameter may appear when “Control Package” is selected in the “TYPE” parameter.

Buttons

Get:

Click to view the display data

Page Up:

Page Down:

Exit:

Click to view the next page data (when next page exists).

Click to return to the previous page data.

Click to exit this command.

Display Data

PKG Name:

Circuit Card Name

Firm Name/Issue: Firm Name/Issue of the circuit card

Each switch data is also displayed on the dedicated display page.

CHAPTER 8

NDA-24300

Page 562

Issue 1

DSTN: Display of Station Data

DSTN:

Display of Station Data

1. Functional Outline

This command is used to display the registered Station Data corresponding to the designated Tenant and

term

Station Number. In addition, the information of Hot Line, D

Key Layout, Hunting, and Call Pickup, etc,

can also be displayed as the data related to the designated stations.

2. Parameters

Input Data

TN:

Tenant Number

STN:

Station Number [0-9, #, * (Max. 6 digits)]

Buttons

[For display data selection]

SHP:

KYD:

CPG:

CPE:

PHN:

SHC:

SHU:

HLS:

Station Hunting Group-Pilot

Key Data for D

Call Pickup Group

Call Pickup Expand Group

Phantom Station Number

Station Hunting-Circular

Station Hunting-UCD

Hot Line Station

term

Note: When the designated station has any of these data, the corresponding button(s) can be selected. If the

data is necessary, click the button(s).

[For execution order]

Get:

Close:

Click to view the display data.

Click to exit this command.

Display Data (by Parameters)

ETN:

LENS:

TEC:

Effective Tenant Number

Line Equipment Number (6 digits)

Telephone Equipment Class [1-31]

l=DP (10pps)

2=PB

3=DP/PB

4=DP (20pps)

12=D

14=Hot Line

16=Data Terminal via Data Module

18=Virtual Line Appearance (for D

23=ISDN Terminal

27=8 Conference Equipment

term

5-11=Not used

13=Data Terminal via D

15=CAS Line

17=Not used

19-22=Not used

24-26=Not used

28-31=Not used

term

Multi-Line)

RSC:

SFC:

Route Restriction Class [0-15]

Service Feature Class [0-15]

NDA-24300

CHAPTER 8

Page 563

Issue 1

DTELN: Display of Telephone Number Data for NDM

1. Functional Outline

This command is used to display the registered station data corresponding to specified User Group Number

(UGN) and Telephone Number (TELN). The following data related to Number Group can be displayed by

clicking the selection button for each data. This command can be used only when logging in to Network

Control Node (NCN).

•

ACPGN:

ACPEN:

ASHUN:

ASHCN:

AHLSN:

ASHPN:

AKYD:

Call Pickup Group (NDM)

Call Pickup Expand Group (NDM)

Station Hunting Group-UCD (NDM)

Station Hunting Group-Circular (NDM)

Hot Line Station (NDM)

Station Hunting Group-Pilot (NDM)

term

Key Data for D

2. Parameters

Input Data

UGN:

User Group Number

Telephone Number

TELN:

Display Data

FPC:

Fusion Point Code (1-253)

Tenant Number

TN:

STN:

Station Number

LENS:

Line Equipment Number (6 digits)

MG:

UNIT:

Module Group Number

Unit Number

Group Number

Level Number

LV:

TEC:

RSC:

SFC:

Telephone Class (1-31)

Route Restriction Class (0-15)

Service Feature Restriction Class (0-15)

CHAPTER 8

Page 564

Issue 1

NDA-24300

DTELN: Display of Telephone Number Data for NDM

Selection Button

CPGN:

Call Pickup Group (NDM)

CPEN:

Call Pickup Expand Group (NDM)

Station Hunting Group-UCD (NDM)

Station Hunting Group-Circular (NDM)

Hot Line Station (NDM)

SHUN:

SHCN:

HLSN:

SHPN:

Station Hunting Group-Pilot (NDM)

term

KYD:

Key Data for D

NDA-24300

CHAPTER 8

Page 565

Issue 1

DTF101: Display of Terminal Traffic Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=1 (Terminal Traffic) assigned by the

ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

CHAPTER 8

NDA-24300

Page 566

Issue 1

DTF102: Display of Route Traffic Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=2 (Route Traffic) assigned by the

ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

NDA-24300

CHAPTER 8

Page 567

Issue 1

DTF103: Display of Station Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=3 (Station Peg Count) assigned by the

ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

CHAPTER 8

NDA-24300

Page 568

Issue 1

DTF104: Display of Attendant Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=4 (ATT Peg Count) assigned by the

ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

NDA-24300

CHAPTER 8

Page 569

Issue 1

DTF105: Display of Route Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=5 (Route Peg Count) assigned by the

ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

CHAPTER 8

NDA-24300

Page 570

Issue 1

DTF201: Display of Service Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=6 (Service Peg Count) assigned by the

ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

NDA-24300

CHAPTER 8

Page 571

Issue 1

DTF301: Display of UCD Route Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=8 (UCD Route Peg Count) assigned

by the ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

CHAPTER 8

NDA-24300

Page 572

Issue 1

DTF302: Display of UCD Group Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=9 (UCD Group Peg Count) assigned

by the ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

NDA-24300

CHAPTER 8

Page 573

Issue 1

DTF303: Display of Station Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=10 (UCD Station Peg Count) assigned

by the ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

CHAPTER 8

NDA-24300

Page 574

Issue 1

DTF501: Display of Attendant Answering Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=15 (ATT Answering Peg Count)

assigned by the ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

NDA-24300

CHAPTER 8

Page 575

Issue 1

DTF601: Display of Connection Route Peg Count Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=18 (Connection Route Peg Count)

assigned by the ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

CHAPTER 8

NDA-24300

Page 576

Issue 1

DTF602: Display of Connection Route Traffic Data

1. Functional Outline

This command displays the result of traffic measurement data for Type=19 (Connection Route Traffic)

assigned by the ATRF command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101

Route Traffic-DTF102

Station Peg Count-DTF103

Attendant Peg Count-DTF104

Route Peg Count-DTF105

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201

UCD Route Peg Count-DTF301

UCD Group Peg Count-DTF302

UCD Station Peg Count-DTF303

Traffic Data 5:

Traffic Data 6:

Attendant Ans. Peg Count-DTF501

Connection Route Peg Count-DTF601

Connection Route Traffic-DTF602

NDA-24300

CHAPTER 8

Page 577

Issue 1

DTF101N: Display of Terminal Traffic Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=1 (Terminal Traffic)

assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

CHAPTER 8

NDA-24300

Page 578

Issue 1

DTF102N: Display of Route Traffic Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=2 (Route Traffic)

assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

NDA-24300

CHAPTER 8

Page 579

Issue 1

DTF103N: Display of Station Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=3 (Station Peg Count)

assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

CHAPTER 8

NDA-24300

Page 580

Issue 1

DTF104N: Display of Attendant Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=4 (ATT Peg Count)

assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

NDA-24300

CHAPTER 8

Page 581

Issue 1

DTF105N: Display of Route Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=5 (Route Peg Count)

assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

CHAPTER 8

NDA-24300

Page 582

Issue 1

DTF201N: Display of Service Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=6 (Service Peg Count)

assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

NDA-24300

CHAPTER 8

Page 583

Issue 1

DTF301N: Display of UCD Route Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=8 (UCD Route Peg

Count) assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

CHAPTER 8

NDA-24300

Page 584

Issue 1

DTF302N: Display of UCD Group Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=9 (UCD Group Peg

Count) assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

NDA-24300

CHAPTER 8

Page 585

Issue 1

DTF303N: Display of UCD Station Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=10 (UCD Station Peg

Count) assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

CHAPTER 8

NDA-24300

Page 586

Issue 1

DTF501N: Display of Attendant Answering Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=15 (ATT Answering

Peg Count) assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

NDA-24300

CHAPTER 8

Page 587

Issue 1

DTF601N: Display of Connection Route Peg Count Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=18 (Connection Route

Peg Count) assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

CHAPTER 8

NDA-24300

Page 588

Issue 1

DTF602N: Display of Connection Route Traffic Data for Fusion Network

1. Functional Outline

This command is used for displaying the result of traffic measurement data for “Type”=19 (Connection Route

Traffic) assigned by the ATRFN command.

2. Parameters

Traffic Data 1:

Terminal Traffic-DTF101N

Route Traffic-DTF102N

Station Peg Count-DTF103N

Attendant Peg Count-DTF104N

Route Peg Count-DTF105N

Traffic Data 2:

Traffic Data 3:

Service Peg Count-DTF201N

UCD Route Peg Count-DTF301N

UCD Group Peg Count-DTF302N

UCD Station Peg Count-DTF303N

Attendant Ans. Peg Count-DTF501N

Connection Route Peg Count-DTF601N

Connection Route Traffic-DTF602N

Traffic Data 5:

Traffic Data 6:

NDA-24300

CHAPTER 8

Page 589

Issue 1

FLINST: File Install

1. Functional Outline

This command is used to install the DPSW-dedicated database files to your MAT. This command is necessary

to provide each circuit card’s various information (such as circuit card name, equipped switch names, etc.)

when your system uses the DPSW/DPKG command.

2. Parameters

Input Data

None

Buttons

Copy:

Click to start the data file install.

Click to exit this command.

Exit:

(1) Start up the FLINST command from the Start menu.

(2) Initial Display of the FLINST command appears. Make sure the proper FD drive name is selected in the

FDD parameter.

(3) Click the Copy button. Then, a message, requiring to insert the first FD into the FDD drive, appears.

(4) Insert the first FD into the FDD of the MAT. Then, click OK.

(5) File copy starts automatically, and the Copy End message appears upon completion.

(6) Click OK. Another message asks you whether the next FD is to be installed or not.

(7) Click OK.

(8) A message, requiring you to insert the second FD into the FDD drive is displayed. Insert the second FD

into the FDD, and click OK.

(9) File copy starts automatically, and the Copy End message appears upon completion.

(10) Click OK. A message asks you whether the next (fourth) FD is to be installed or not.

(11) Click Cancel.

CHAPTER 8

NDA-24300

Page 590

Issue 1

HDD_FDD: Data Control Between HDD and FDD

1. Functional Outline

This command is used to install the program data from FDD of PBX to HDD of PBX, and to verify the program

data between FDD of PBX and HDD of PBX.

2. Parameters

Input data

System Select:

HFD0/HFD1

Direction Select:

Floppy Disk to Hard Disk/Verify HDD against FDDNote

Data Type Selection: Program data (others are invalid.)

LP Select:

Not used

Auto Verify Afterward

Note: “Hard Disk to Floppy Disk” cannot be selected.

Input data

System Select:

HFD0/HFD1

Direction Select:

Floppy Disk to Hard Disk/Verify HDD against FDD/Hard Disk to Floppy Disk

Data Type Selection: Data Memory

Name Display

Wireless Call Forwarding Note 1

Program data

Call Forwarding

Speed Calling

User Assign Soft Key

Number Sharing

Call Block

Note 4

ACD Data Memory

NDA-24300

CHAPTER 8

Page 591

Issue 1

HDD_FDD: Data Control Between HDD and FDD

File Name Select

Auto Verify Afterward

Note 1: When this data is selected, specify the file names in the “File Name Select” parameter.

Note 2: “Program data” can be valid when you select “Floppy Disk to Hard Disk” or “Verify HDD against

FDD” in the “Direction Select” list box.

Note 3: By saving the Number Sharing data, the data concerning “Dual Station Calling Over-FCCS” is also

saved/verified automatically.

Note 4: When this data is selected, an “LP Select” dialog appears. Then, specify the LP number in the “LP

Select” parameter.

CHAPTER 8

Page 592

Issue 1

NDA-24300

HDD_MAT: Data Control Between HDD and MAT

1. Functional Outline

This command is used to save the following data from HDD of PBX to MAT.

2. Parameters

Input data

Direction Select:

PBX Hard Disk to MAT

MAT to PBX Hard Disk

Verify HDD against MAT

Data Type Selection:

Data Memory

Name display

Wireless Call Forwarding

Program data

Call Forwarding

Speed Calling

User Assign Soft Key

Number Sharing

Call Block

ACD Data Memory

LP Select:

This data appears only when Call Forwarding, Speed Calling, User Assign Soft

Key, Number Sharing, or Call Block data is designated.

Auto Verify Afterward

Note 1: When Data Memory is selected, Network Data Memory (NDM) and Local Data Memory (LDM) are

also saved/verified simultaneously.

Note 2: Program data can be valid when MAT to PBX Hard Disk option in the Direction Select list box is se-

lected.

Note 3: By saving the Number Sharing data, the data concerning Dual Station Calling Over-FCCS is also

saved/verified automatically.

NDA-24300

CHAPTER 8

Page 593

Issue 1

HDD_MAT_N: Data Control Between HDD and MAT for NDM

1. Functional Outline

This command, available at the NCN only, installs (overwrites) the updated Program data from the centralized

MAT onto the HDD of all local nodes. To use this command, first install the updated program data on the HDD

of the MAT and then execute the program installing onto the HDD of each LN.

2. Parameters

Input data

Data Type Selection:

Execution Button:

Select all the listed program data

Installing of program data is to be executed

CHAPTER 8

NDA-24300

Page 594

Issue 1

HDFP: HDD Format of PBX

HDFP:

HDD Format of PBX

1. Functional Outline

This command is used to execute the formatting of the HDD of PBX.

2. Parameters

Input Data (Selection by check)

0 System:

1 System:

HDD of No.0 System

HDD of No.1 System

Buttons

Execute:

Close:

Click to execute the formatting.

Click to exit this command.

NDA-24300

CHAPTER 8

Page 595

Issue 1

MBCT: Make Busy of Connection Trunk for LDM

MBCT:

Make Busy of Connection Trunk for LDM

1. Functional Outline

This command is used to set/reset the make busy state of the connection trunk.

2. Parameters

Input Data

C_RT:

C_TK:

MB:

Connection Route Number [1-1023]

Trunk Number [1-4095]

Make Busy Information [0/1]

0=Make Idle

1=Make Busy (Outgoing)

CHAPTER 8

NDA-24300

Page 596

Issue 1

MBLE: Make Busy of LENS

MBLE:

Make Busy of LENS

1. Functional Outline

This command assigns the IDLE/BUSY status of Line Equipment Numbers (LENS).

2. Parameters

Input data

LENS

MB:

0=Make Idle

1=Make Busy

NDA-24300

CHAPTER 8

Page 597

Issue 1

MBPM: Make Busy of Port Microprocessor

MBPM:

Make Busy of Port Microprocessor

1. Functional Outline

This command sets or resets the make-busy state of the circuit card that contains the port microprocessor. This

setting and resetting is performed individually for each circuit card. If the location of the circuit card containing

the port microprocessor is specified in this command, the operating state of all circuit cards mounted in the

associated unit is displayed.

2. Parameters

Input data

Unit

Group

Display data

MB:

0=Make Idle

1=Make Busy

Note: Idle/Busy status can be displayed and assigned by the MB parameter.

CHAPTER 8

NDA-24300

Page 598

Issue 1

MBRT: Make Busy of Route

MBRT:

Make Busy of Route

1. Functional Outline

This command assigns Idle/Busy status for all the trunks in the route designated.

2. Parameters

Input data

RT:

Route Number of the external route/internal route. Table 8-6 provides the meaning of

the internal route numbers.

MB:

0=Make Idle

1=Make Busy

Table 8-6 Route Number Explanation

DATA

MEANING

Attendant/Desk Console

DATA

MEANING

901

903

905

907

909

913

915

917

902

904

Originating Register Trunk

Incoming Register Trunk

Sender Trunk DP/PB

MF Receiver

906

PB Receiver for Automated Attendant Service

AMP

908

Not used

Three-Way Conference Trunk

Three-Way Conference Trunk for ATTCON

Night Attendant Console

MFC Sender

910-912

914

Not used

916

MFC Register

Not used

918

919-926 Modem

927, 928 Not used

930 Rate Adapter Conversion Trunk

929

Data Signaling Trunk-Option

931-947 Not used

NDA-24300

CHAPTER 8

Page 599

Issue 1

MBRT_LR: Make Busy of Route-Logical Route Number

1. Functional Outline

This command is used for assigning IDLE/BUSY status of all the trunks in the logical route designated. Route

number of the MBRT command can be assigned by using logical route.

Note 1: When logging in to the NCN (Network Control Node), the data of other LN (Local Node) can be

changed. If logging in to a LN, only the DM of self-Node can be changed by this command.

2. Parameters

Input Data

LGRT:

MB:

Logical route number allocated to the external/internal route. Refer to the MBRT com-

mand as to the Internal route number and its meaning. Note

Make Busy Information

Make Idle

Make Busy

Note: Prior to this command, logical route number must be allocated by using the ALRTN command.

Display Data

FPC:

RT:

Fusion Point Code [1-253]

External Route Number

CHAPTER 8

NDA-24300

Page 600

Issue 1

MBSM: Make Busy of System Message Printout

MBSM:

Make Busy of System Message Printout

1. Functional Outline

This command allows or inhibits the system message printer to output system messages.

2. Parameters

Input data

PORT NO.:

MB:

Port Number of the printer

0=Make Idle

1=Make Busy

NDA-24300

CHAPTER 8

Page 601

Issue 1

MBST: Make Busy of Station

MBST:

Make Busy of Station

1. Functional Outline

This command assigns the Idle/Busy status of stations.

2. Parameters

Input data

STN:

MB:

Maximum 5 digits for Business system/Maximum 6 digits for Hotel system.

0=Make Idle

1=Make Busy

CHAPTER 8

NDA-24300

Page 602

Issue 1

MBST_T: Make Busy of Station – Telephone Number

1. Functional Outline

This command is used to assign the IDLE/BUSY status of stations, by using Telephone Numbers. This

command is available at NCN (for Fusion network) only.

2. Parameters

Input Data

UGN:

TELN:

MB:

User Group Number

Telephone Number (max. 16 digits)

Make Busy/Make Idle

Display Data

FPC:

Fusion Point Code (1-253)

Tenant Number

TN:

STN:

Physical Station Number

(max. 5 digits for Business system/max. 6 digits for Hotel system)

Note: This data is for display only.

Buttons

Get:

Set:

Click to get information on the station.

Click to execute the BUSY/IDLE performance.

Click to exit this command.

Exit:

NDA-24300

CHAPTER 8

Page 603

Issue 1

MBTC: Make Busy of Trunk-Continuous

MBTC:

Make Busy of Trunk-Continuous

1. Functional Outline

This command is used to assign the IDLE/BUSY status of trunks. By using this command, plural trunks can

be placed into IDLE/BUSY state simultaneously per a route designated in “RT” parameter.

2. Parameters

Input Data

RT:

Route Number

TK:

MB:

Trunk Number

0=Make Idle

1=Make Busy (Outgoing)

2=Make Busy (Bothway)

Note 1: Multiple trunks can be assigned simultaneously per a route designated in “RT” parameter.

Note 2: 2=Make Busy (Bothway) is not used.

CHAPTER 8

NDA-24300

Page 604

Issue 1

MBTC_LR: Make Busy of Trunk-Continuous-Logical Route Number

1. Functional Outline

This command is used to assign the IDLE/BUSY status of trunks. By using this command, plural trunks can

be placed into IDLE/BUSY state simultaneously per a logical route designated in “LGRT” parameter. Route

number of the MBTC command can be assigned by using logical route.

Note 1: When logging in to the NCN (Network Control Node), the data of other LN (Local Node) can be

changed. If logging in to a LN, only the DM of self-Node can be changed by this command.

2. Parameters

Input Data

LGRT:

TK:

Logical route number allocated to the Route Number. Note 1

Trunk Number Note 2

START

END

MB:

Make Busy Information [0-2]

0=Make Idle

1=Make Busy (Outgoing)

2=Make Busy (Bothway) Note 3

Note 1: Prior to this command, logical route number must be allocated by using the ALRTN command.

Note 2: The status of plural trunks can be changed simultaneously, according to the range of trunk number

assigned and per a logical route.

Note 3: 2=Make Busy (Bothway) is not used.

Display Data

FPC:

RT:

Fusion Point Code [1-253]

Route Number

NDA-24300

CHAPTER 8

Page 605

Issue 1

MBTK: Make Busy of Trunk

MBTK:

Make Busy of Trunk

1. Functional Outline

This command assigns the Idle/Busy status of trunks.

2. Parameters

RT:

Route Number

Trunk Number

TK:

MB:

0=Make Idle

1=Make Busy (Outgoing)

CHAPTER 8

Page 606

Issue 1

NDA-24300

MBTK_LR: Make Busy Trunk-Logical Route Number

1. Functional Outline

This command is used to assign the IDLE/BUSY status of trunks. Route number of the MBTK command can

be assigned by using logical route number.

Note 1: When logging in to the NCN (Network Control Node), the data of other LN (Local Node) can be

changed. If logging in to a LN, only the DM of self-Node can be changed by this command.

2. Parameters

Input Data

LGRT:

TK:

Logical route number [1-899] Note 1

Trunk Number [1-255]

MB:

Make Busy Information [0-2]

0=Make Idle

1=Make Busy (Outgoing)

2=Make Busy (Bothway) Note 2

Note 1: Prior to this command, logical route number must be allocated to the route number by the ALRTN

command.

Note 2: 2=Make Busy (Bothway) is available in Australia only.

Display Data

FPC:

Fusion Point Code [1-253]

Route Number

RT:

STATUS:

Make Busy Status for MB=2

Self trunk MB

Other trunk MB

Both trunk MB

Self trunk MB ready

Both trunk MB ready

NDA-24300

CHAPTER 8

Page 607

Issue 1

MEM_HDD: Data Control Between Memory and HDD

1. Functional Outline

This command is used to save the following data from MEM of PBX to HDD of PBX, and vice versa.

2. Parameters

Input data

Direction Select:

Memory to Hard Disk

Hard Disk to Memory

Verify HDD against MEM

Data Type Selection:

Data Memory

Name Display

Wireless Call Forwarding

Call Forwarding

Speed Calling

User Assign Soft Key

Number Sharing

Call Block

ACD Data Memory

LP Select:

This data is valid when Call Forwarding, Speed Calling, User Assign Soft Key,

Number Sharing or Call Block data is designated.

Auto Verify Afterward

Note 1: When Data Memory is selected, Network Data Memory (NDM) and Local Data Memory (LDM) are

also saved/verified simultaneously.

Note 2: By saving the Number Sharing data, the data concerning Dual Station Calling Over-FCCS is also

saved/verified automatically.

CHAPTER 8

NDA-24300

Page 608

Issue 1

MEM_HDD_N: Data Control Between Memory and HDD for NDM

1. Functional Outline

This command, available at the NCN only, is used to save/verify a series of Office Data from the Memory of

all Local Nodes to the HDD of each same node.

2. Parameters

Input data

Direction Select:

MEM to HDD

Verify HDD against MEM

Data Type Selection:

Data Memory

Name Display

Wireless Call Forwarding

Call Forwarding

Speed Calling

User Assign Soft Key

Number Sharing

Call Block

LP Select:

The parameter is valid when Call Forwarding, Speed Calling, User Assign Soft

Key, Number Sharing or Call Block data is designated.

Auto Verify Afterward

Note 1: When Data Memory is selected, Network Data Memory (NDM) and Local Data Memory (LDM) are

also saved/verified simultaneously.

Note 2: By saving the Number Sharing data, the data concerning Dual Station Calling Over-FCCS is also

saved/verified automatically.

Display data

Information:

FPC of Node in which saving/verifying is executed

Result of the execution

Direction:

Data Type:

MEM to HDD

Verify HDD against MEM

Selected Data Type

NDA-24300

CHAPTER 8

Page 609

Issue 1

MFCH: Make Busy of FCCH

MFCH:

Make Busy of FCCH

1. Functional Outline

This command is used to set or reset the make busy state of the FCH card.

2. Parameters

Input Data

FCHN:

MB:

FCH Number [1-255]

Make Busy Information [0/1]

0=Make Idle

1=Make Busy

CHAPTER 8

NDA-24300

Page 610

Issue 1

PMBU: Port Microprocessor Back Up

PMBU:

Port Microprocessor Back Up

1. Functional Outline

This command saves the contents of Port Microprocessor (PM) onto Floppy Disk (FD) or verifies them.

Information of firmware (Program Code) also appears on the screen.

2. Parameters

Input data

Direction Select:

PM Information:

Port Microprocessor to MAT

Verify Port Microprocessor

Verify PM with Error List Auto Verify Afterward can be performed when desig-

nating Port Microprocessor to MAT.

Module Group

Unit

Group

Data Size (1-6)

1=2 Kbytes

2=4 Kbytes

3=8 Kbytes

4=16 Kbytes

5=32 Kbytes

6=64 Kbytes

Display data

Office

SP Number:

SP Issue:

Information of firmware (Program Code)

NDA-24300

CHAPTER 8

Page 611

Issue 1

RALM: Release Alarm

RALM:

Release Alarm

1. Functional Outline

This command clears the fault indications.

2. Parameters

Input data

WRT:

Y=Alarm is released

N=Not released

RETURN TO MENU?: Y=Return to MENU

N=Start operation again

Display data

Alarms Released

CHAPTER 8

NDA-24300

Page 612

Issue 1

RALMN: Release Alarm for NDM

1. Functional Outline

This command, available at the NCN only, clears the fault indications of all the Nodes by clicking the release

button on the display.

2. Parameters

Display data

FPC:

FPC of alarm released Nodes

Result of releasing the alarm

OK/NG

Status:

NDA-24300

CHAPTER 8

Page 613

Issue 1

RLST: Release Station/Trunk

RLST:

Release Station/Trunk

1. Functional Outline

This command releases a station or trunk.

2. Parameters

Input data

TYPE:

Type of Select (1-4)

1=Stations

2=Trunk

3=LENS

4=Connection Trunk

TN:

STN:

Maximum 6 digits

RT:

TK:

LENS:

Connection RT:

Connection TK:

(1-1023)

Note 4

(1-4095)

Note 1: This parameter is valid only when TYPE=1.

Note 2: This parameter is valid only when TYPE=2.

Note 3: This parameter is valid only when TYPE=3.

Note 4: This parameter is valid only when TYPE=4.

Display data

STATUS:

Status of Station/Trunk (1-4)

1=Idle

2=Busy

3=Lockout

4=Make Busy

FPC:

Fusion Point Code (1-253)

Information of the connected party Note

INFORMATION:

Note: This parameter appears only when STATUS=2.

CHAPTER 8

NDA-24300

Page 614

Issue 1

RLST_T: Release of Station/Trunk –Telephone Number

RLST_T: Release of Station/Trunk – Telephone Number

1. Functional Outline

This command is used to release a station/trunk, by using Telephone Numbers. This command is available at

NCN (for Fusion network) only.

2. Parameters

Input Data

TYPE:

Telephone Number

Trunk

LENS

Connection Trunk

UGN:

TELN:

RT:

User Group Number

Telephone Number (max. 16 digits) Note 1

External/Internal Route Number

Trunk Number