Calculating Ttr Requirements; Touch Tone Receiver Test - Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual

Maintenance and Troubleshooting

Calculating TTR Requirements

If symptoms indicate more TTRs are required, use the following steps to calculate the system
requirements for TTRs.
1. Determine the number of TTRs required for the voice messaging system, if one is present.
See Table 3-4, ''TTRs Required by VMS/AA,''
2. Estimate the hourly call volume for calls originating from single-line telephones, incoming calls
(including private network tandem tie trunks) on remote access and Direct Inward Dial (DID)
lines, all calls on tie lines, and calls routed to the voice messaging system.
3. Determine the number of TTRs required by the system. See
Tone Receivers''
4. Use Column 2 if account codes are not being used.
5. Use Column 3 if account codes are being used.
6. Add the number of TTRs obtained in Steps 1 and 3. If the Group Calling Prompt-Based
Overflow setting is not being used, go to Step 8.
7. If the Group Calling Prompt-Based Overflow setting is being used by calling groups, first add
the number of TTRs needed for the primary delay announcement devices assigned to those
calling groups, then add the number of TTRs needed for the secondary delay announcement
devices assigned to those calling groups. See Table
Announcement Devices When Using Prompt-Based Overflow,''
''TTRs Required for Secondary Delay Announcement Devices When Using Prompt-Based
Overflow,'' on page 11.
If no announcement is used on a primary or secondary delay announcement device,
no TTRs are needed.
8. Determine the number of TTRs already supplied. See Table
on page 8.
9. Compare the total TTRs needed to the total TTRs already supplied to determined if additional
TTRs are required.
10. Add a new module if more TTRs are needed.

Touch Tone Receiver Test

The Touch-Tone Receiver Test runs as an audit on the system. It is not a demand test but runs
continuously in the background as a maintenance check. This test checks every Touch Tone
Receiver (TTR) in the system modules, including those in the MERLIN Messaging System.
If a TTR fails the test, a permanent error is logged and the TTR becomes maintenance busy. If
50% or more TTRs become maintenance busy at the same time, another permanent error is
logged. See Error Codes 1C06 and 1C07 in Table
itself does not maintenance busy out 50% or more TTRs.
Touch Tone Receiver Problems
3-12
on page 3-9.
3
on page 9.
''System Requirements for Touch
3-6, ''TTRs Required for Primary Delay
on page
3-3, ''Modules that Supply TTRs,''
3
2-2 on page 2-3. The Touch Tone Receiver Test
10 and Table 3-7,