MERLIN LEGEND Communications System Release 6.1
Maintenance and Troubleshooting
555-661-140
Issue 1
August 1998
Page 1-21
Maintenance Strategy
Maintenance Strategy
The maintenance strategy presented in this section is only a guideline, not a
fixed procedure. Refer to Figure 1–7 on page 1–22 whenever you are uncertain
about how to proceed. It provides guidelines for analyzing problems in
non-networked systems.
For private networked systems (Release 6.0 and later, Hybrid/PBX mode), call
completion problems are usually caused by incorrect programming, although
alarms and error logs should be checked initially. The source of the trouble may
be the originating system or any system over which the call is conveyed. Fault
isolation is required to identify one or more misprogrammed switches, because
the problem may not originate at the system where it is reported. For this
reason, technicians should attempt to log into each private networked system,
preferably simultaneously, and originate test calls with traces to verify the
messages, states, and activities associated with the facilities and switches. If
the problem is indeed incorrect programming, a technician can correct it
remotely without going to the customers’ site(s). If test calling does not reveal
the source of the problem, then hardware should be checked as with
non-networked systems. More information about analyzing private network
calling problems is included in “Network Calling Problems” on page 5–40.
As you become more experienced with maintaining and troubleshooting
systems, you will most likely develop your own strategy.
To Next Page
Loading...
Need help?
General
