2.1 Maintenance
2.1.1 Maintenance
This section does not deal with failures caused by configuration errors nor with those caused
by errors in the telephone features.
In either of these cases, refer to the sections on MMC-Station and Telephone Features.
In all cases, a thorough knowledge of the system (architecture, distribution of function
processing, etc.) and of its telephone features is essential, and in particular the limits of these
features.
Errors concerning distribution must be eliminated first.
To avoid taking a wrong track when determining faults, it is vital to define the source of the
fault from the outset:
- operating error by the user
- programming error by the user or operator
- programming error in implementation
- genuine system failure
2.1.2 Troubleshooting Procedure
For any system failure, it is essential to make visual checks (LEDs for the various boards, data
testing, automatic set testing), to check the power supply voltage (electrical and battery) and to
read the system messages.
The procedure is as follows:
- locate the terminal(s) affected by the fault. If several terminals are affected by the same
fault, determine the common link which might be the cause (logical numbers of the same
board, geographical distribution, same type of programming, etc.)
- determine at what level the error is occurring (internal or external call, etc.).
2.1.3 Extent of Failure
A failure may be characterized by various aspects:
- Total system failure:
10/62
! "#$ ! % $& !
To Next Page
Loading...
Need help?
General
