Lucent Technologies MERLIN LEGEND Release 5.0 Maintenance And Troubleshooting Manual page 232

Communications system
Hide thumbs Also See for MERLIN LEGEND Release 5.0:
Table of Contents

Advertisement

MERLIN LEGEND Communications System Release 5.0
Maintenance and Troubleshooting 555-650-140
Central Office Problems
Trunk Errors
Table 5-1. Troubleshooting Trunk Symptoms
Symptom
Incoming calls not being received
Cannot make outgoing calls
General trunk problems
NOTE:
If the customer reports echoes during conversations on T1 trunks with GS
emulation to a toll office, check the system programming for T1 trunks.
The system is not intended to work with GS emulation to a toll office. Tie
trunk emulation must be programmed. Program the module to emulate tie
trunks to the central office.
Manual Correction of Trunk Problems
If the system cannot seize a trunk even after repeated attempts, you may have
to replace the module.
To identify the trunk problem, follow the steps below.
Check for dial tone at the control unit.


If you do not hear dial tone, check the error logs and make a trunk


test call.
Check for dial tone at the network interface.


It is sometimes difficult for the customer to detect trunk troubles. If a trunk
is down, the system records an error in the error log and takes the trunk
out of service. However, if an incoming-only trunk is down, the only sign
of trouble is customer complaints that incoming calls are not being
received.
Check the error logs for messages about trunk type (such as DID, tie,
and T1). Also check the wiring and the system parameters (for example,
touch-tone/rotary, toll restriction, and disconnect time interval).
Section
Incoming Trunk Problems
Outgoing Trunk Problems
Manual Correction of Trunk Problems
Issue 1
June 1997
Page 5-2

Advertisement

Table of Contents
loading

Table of Contents