Lucent Technologies MERLIN LEGEND Release 7.0 System Manager's Quick Reference page 159

MERLIN LEGEND Communications System R7.0
System Manager's Quick Reference 555-670-119
Troubleshooting the System
Secondary Announcements Not Playing as Programmed
To analyze a problem with secondary announcements, follow these preliminary
steps:
The Calls-In-Queue Alarm Threshold setting should determine when an
1
alarm is signalled. Set the overflow threshold time to 0.
Set up primary and secondary announcements of durations that seem
2
appropriate for your needs.
Specify a reasonable announcement interval (for example, 30 seconds).
3
Refer to the following table and divide the announcement interval (Y) by the
4
length of the secondary announcement (Z).
Round off the result, and use this value as an alarm threshold when a
5
Calls-in-Queue Alarm button signals a problem.
Checking the Effectiveness of Delay Announcements
Calls Waiting
for Secondary
Announcement (N)
3
3
5
10
When the number of calls waiting for a secondary announcement multiplied by
the length of that announcement is greater than the announcement interval, an
alarm is triggered. The preceding table illustrates situations where a
programmed Calls-in-Queue Alarm button would or would not indicate a
problem.
If problems arise, use the display at the calling group supervisor DLC console to
monitor the situation while the problem is most severe. Try to adjust the
announcement duration and the interval setting so that the announcement
interval is greater than or equal to the length of the secondary announcement
multiplied by the number of calls waiting for the secondary announcement
(Y >= N * Z).
Length of
Secondary
Announcement
in Seconds (Z)
10
20
15
15
Announcement
Interval in
Seconds (Y)
30
30
90
90 150
Issue 1
April 1999
N * Z Is N * Z > Y?
30 No
60 Yes
75 No
Yes
147