BusinessPhone Communication Platform 4.0
Fault Tracing ASB 150 02 > Fault locating

## General checks on start and completion of service

Start by identifying the type of fault by collecting as much information about the fault as possible, from the relevant customer, then (if possible) connect RASC and check the configuration of the PBX with regard to revision states (see Translation and verification of revision states) as soon as this is possible.

The majority of faults can probably be eliminated from the O&M-centre by means of reprogramming or via telephone contact with the respective customer (operational faults).

Consider to which one of the following main fault categories best describes your fault:

Type Of Fault | Go to
Indication of LEDs on board(s) | Indication of LEDs on board(s)
No call procedures possible in the PBX | Flow chart: No possibility to make calls in PBX
Individual board not working | Flow chart: Individual board not working
A single individual does not work at all, e.g. an extension is "dead". The individual is not able to either initiate or receive calls | Flow chart: Individual does not work at all
Digital trunk (BTU-D) does not work at all | Flow chart: Digital trunk does not work at all
Individual malfunctions partly, intermittent faults, e.g. one connection case is successful and another fails. The fault can be traced to an individual | Flow chart: Part of individual function not working
A certain facility never functions. A certain facility is inaccessible, e.g. intrusion is never possible | Flow chart: Individual facility does not work
A certain facility functions intermittently, that is a certain connection case succeeds on one occasion, not on another, and where the fault cannot be traced to an individual | Flow chart: Individual facility works intermittently
An individual has no access to a certain facility | Flow chart: Individual does not work for certain facilities
Transmission fault (one way speech, line scratching, etc.) | Flow chart: Transmission faults
PBX unstable (repeated restarts) | Flow chart: PBX is unstable
Faults related to Cordless | Flow Charts for Cordless

Use the following flow charts describing a methodical path for checks and tests to help locate and eliminate the fault. When the flow charts lead to a possible cause, this is indicated by a statement giving the name of the defective part or the cause of the problem, e.g. a defective BTU-_ board is indicated by the statement `BTU-_ board defect'. When there are more possible items, they are listed in order of decreasing probability.

#### Description of flow chart symbols

Question |  | This symbol contains a question with two or three possible answers being YES (Y), NO (N) or text. Inputs are points 1 or 4 and outputs are points 2,3 or 4.
Instruction |  | This symbol contains an instruction for the maintenance engineer.
References |  | This symbol is used as: starting point for a procedure (e.g. START), as a reference to another flowchart, to end a procedure (END).
| This symbol is used as a reference point within a flowchart. This can be to a part of the flowchart on another page (e.g. B or C) or at a part of the flowchart on the same page (e.g.1).
Flow |  | Lines indicate the normal flow. The normal flow is always "down" and "to the right" and in exceptional cases "to the left".
| Arrows are used to indicate flows going "up" or left.

Revision: F © Ericsson Enterprise 2003