Lucent Technologies MERLIN LEGEND Release 6.1 Maintenance And Troubleshooting Manual page 74

MERLIN LEGEND Communications System Release 6.1
Maintenance and Troubleshooting 555-661-140
Error Logs
Table 2–2. Error Codes (Continued)
Error
Codes Description
The system needed to use a TTR
but one was not available for any
and all reasons including: in use, not
physically present, and out of
service.
Two consecutive messages to
update Message Waiting lights have
been sent across the private
network on the same tandem trunk
and have not been acknowledged.
When this happens three times, the
error becomes permanent. The
alarm remains in the log until a
message for the facility is
acknowledged or five days pass.
Action
Check count and first and last
occurrences to determine if error occurs
too frequently. If so, check to see if you
can add TTRs to the system.
If you have prompt out of queue active,
you may want to shorten the delay
announcement message length.
If you have the prompt out of queue
feature and secondary announcement(s)
active, you may want to increase the
interval between the announcements.
If you reprogram the delay announcement
unit, recheck it to verify that the problem
no longer exists.
Check to see if you can add TTRs to the
system.
Check the error log for additional error
codes. If the error log contains errors
indicating problems with the 100D
module, trouble shoot the 100D module
using instructions in Chapter 4 of this
guide. If the error log also contains errors
indicating problems with the 400EM
module, troubleshoot the 400EM module
using instructions in Chapter 4 of this
guide.
If the 100D and/or the 400EM modules
are functioning properly, troubleshoot the
trunks using instructions in Chapter 5 of
this guide.
Continued on next page
Issue 1
August 1998
Page 2-10