4. ROUTINE DIAGNOSIS
For confirming its own servicing status, the system automatically executes self diagnosis every day, and
displays the result of the diagnosis as a system message. By this function, possible causes for trouble can be
discovered in an early stage and possible trouble can be prevented from remaining undetected.
4.1
Related System Data
•
ASYD, SYS1, INDEX86,
b0 –
b1 –
b3, b2 – Processing at the time when Trunk Ineffective Hold is detected. Note 1
The trunks being held at present are forcibly
BIT
released, except the trunks being held on two-
way calls (station-to-station call, station-to-
b3
b2
trunk, external trunk-to-external trunk call).
0
0
0
1
1
0
Trunk Ineffective Hold is a continuous state other than idle state within a predetermined duration while
Note 1:
routine diagnosis is in progress. Whether it is detected/not detected, it is assigned by ASYD, SYS1, IN-
DEX 89.
When Trunk Ineffective Hold on the FCCS Network is detected, setting of ASYD, SYS1, INDEX 86,
Note 2:
b2·b3 and SYS1, INDEX 89, b4·b5 must be the same at all nodes on the network.
•
SYS1, INDEX 87, 88 - Routine Diagnosis Start Time
Start time should be such a time which the traffic of the office is the lowest.
To stop the routine diagnosis, set FF respectively to INDEX87, 88.
When routine diagnosis starts, and the result of the routine diagnosis is normal, the result
displays as System Message [
0/1: Not displayed/Displayed
When the result of the routine diagnosis is abnormal, it displays as System Message [
0/1: Not displayed/To display
X
—
—
INDEX 87 0
2
INDEX 88 0
0
CHAPTER 2
].
7-O
All trunks being held at
the present are forcibly
released
—
—
X
(Hour)
2:00 a.m. is the start time.
(Minute)
– 53 –
Operations of SV8500 Server
LENS of the trunk detected
display as System Message
[7-P]
X
X
X
].
7-P