Lucent Technologies MERLIN LEGEND 6 - Manual (Page 374)

MERLIN LEGEND Communications System Release 6.0
System Manager’s Guide
555-660-118
Issue 1
February 1998
Troubleshooting the System
Page 8-28 Secondary Announcements Not Playing as Programmed
8
Consult the Feature Reference and System Programming as you
troubleshoot announcement delays.
To analyze a problem with secondary announcements, follow these preliminary
steps:
1. The Calls In Queue Alarm Threshold setting should determine when an
alarm is signalled. Set the overflow threshold time to 0.
2. Set up primary and secondary announcements of durations that seem
appropriate for your needs.
3. Specify a reasonable announcement interval (for example, 30 seconds).
4. Refer to Table 8-1 and divide the announcement interval (Y) by the length
of the secondary announcement (Z).
5. Round off the result and use this value as an alarm threshold when a
Calls-in-Queue Alarm button signals a problem.
Table 8–1. Checking the Effectiveness of Delay Announcements
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.
Table 8–1 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
announcements’ durations 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).
Possible Cause 1: The announcement interval may be too short or the
secondary announcement may be too long.
Calls Waiting for
Secondary
Announcement
(N)
Length of
Secondary
Announcement in
Seconds (Z)
Announcement
Interval in
Seconds (Y) N * Z Is N * Z > Y?
3 10 30 30 No
3 20 30 60 Yes
5 15 90 75 No
10 15 90 150 Yes