Section 10 ADVANCED PROBLEM SOLVING
178
GENERAL
Thinking About Problem Solving
Despite best intentions, something could always go wrong. Sometimes troubleshooting
a balky set- up can make even the toughest engineer a Maalox and Rogaine addict.
You can't fix any system without the right world view; a zeitgeist of suspicion tempered
by trust in the laws of physics, curiosity dulled only by the determination to stay focused
on a single problem, and a zealot's regard for the scientific method. Perhaps these are
successful characteristics of all who pursue the truth.
In a world where we are surrounded by complexity, where we deal daily with equipment
and systems only half- understood, it seems wise to follow understanding by an iterative
loop of focus, hypothesis, and experiment.
The notions here apply whether you are solving problems at the system level or at the
component level. At the system level, the actions you might take would be very different
– checking cables, trying different menu settings – but the thinking is the same.
Too many times, we fall in love with our suppositions. We are quick to overtly or
subconsciously assume the problem being chased is due to lousy design, the stupid
phone company, or the manager’s latest memo.
Armed with a healthy skeptical attitude, the basic philosophy of troubleshooting any
system is to follow these steps:
1.
Observe the behavior to find the apparent problem;
2.
Observe collateral behavior to gain as much information as possible about the
problem;
3.
Round up the usual suspects;
4.
Generate a hypothesis;
5.
Generate an experiment to test the hypothesis (repeat steps three through five, if
necessary);
6.
Fix the problem;
Then, repeat, if necessary, to attack additional problems.
Let's cover each step of the troubleshooting sequence in detail.
•
Step 1.
Observe the behavior to find the apparent bug. In other words, determine
the bug's symptoms. Remember always that many problems are subtle and exhibit
themselves via a confusing set of symptoms. Remember depending on the nature of
the problem, the system you are troubleshooting may include your data circuits,
your’s or the calling party’s long distance carrier , and the data circuit and
equipment at the other end.
Summary of Contents for Zephyr
Page 13: ...Table of Contents 13 SECTION 1 QUICK RESULTS ...
Page 26: ...Section 2 INTRODUCTION 26 This page intentially left blank ...
Page 27: ...Section 2 INTRODUCTION 27 SECTION 2 INTRODUCTION ...
Page 38: ...Section 2 INTRODUCTION 38 This page intentionally left blank ...
Page 39: ...39 SECTION 3 ZEPHYR AT A GLANCE ...
Page 52: ...Section 4 INSTALLATION BASIC OPERATION 52 This page intentionally left blank ...
Page 53: ...Section 4 INSTALLATION BASIC OP 53 SECTION 4 INSTALLATION BASIC OPERATION ...
Page 84: ...Section 4 INSTALLATION BASIC OPERATION 84 ...
Page 85: ...Section 5 ISDN 85 SECTION 5 ISDN ...
Page 105: ...Section 6 NON ISDN NETWORKS 105 SECTION 7 AUDIO CODING ...
Page 118: ...Section 7 AUDIO CODING PRINCIPLES 118 This page intentionally left blank ...
Page 119: ...Section 8 DETAILED MENU REFERENCE 119 SECTION 8 DETAILED MENU REFERENCE ...
Page 157: ...Section 9 REMOTE CONTROL 157 SECTION 9 REMOTE CONTROL ...
Page 176: ...Section 9 REMOTE CONTROL 176 This page intentionally left blank ...
Page 177: ...Section 10 ADVANCED PROBLEM SOLVING 177 SECTION 10 ADVANCED PROBLEM SOLVING ...
Page 196: ...Section 10 ADVANCED PROBLEM SOLVING 196 This page intentionally left blank ...
Page 197: ...Section 11 TECHNICAL INFORMATION 197 SECTION 11 DETAILED TECHNICAL INFORMATION ...
Page 219: ...Section 12 SCHEMATICS 219 SECTION 12 SCHEMATICS ...
Page 221: ...Section 13 MANUFACTURER S DATA SHEETS 221 SECTION 13 MANUFACTURER S DATA SHEETS ...
Page 223: ...Section 14 SPECIFICATIONS WARRANTY 223 SECTION 14 SPECIFICATIONS AND WARRANTY ...
Page 228: ...228 This page intentionally left blank ...
Page 229: ...Section 15 APPENDICES 229 SECTION 15 APPENDICES ...