Specifications

System Does Not Answer Immediately
Possible Cause 1: Automated Attendant Service is programmed for Delayed call handling.
What to do: If you do not want Delayed call handling, program the communications
system’s VMS Hunt Delay feature for Immediate call handling.
Possible Cause 2: The PARTNER MAIL VS extensions may be busy.
What to do: There are a number of ways to reduce the amount of time a PARTNER MAIL
VS extension is busy. For example, you can recommend that users access the Tutor
feature during non-peak calling hours, you can reduce the number of options in the
Automated Attendant Service menu, or you can reduce the length of the Automated
Attendant Service menu prompt.
System Cuts Off Part of Greeting
Possible Cause 1: You may have begun recording the greeting too soon.
What to do: Re-record the greeting. After the prompt to record, pause a moment before
speaking.
Possible Cause 2: A touchtone signal may have been recorded accidentally with the
greeting.
What to do: Re-record the greeting.
System Transfers Call to Receptionist Before
Playing the Menu Prompt
Possible Cause: The extensions associated with the PARTNER MAIL VS module were not
assigned to Hunt Group 7.
.
What to do: Refer to Figure 2-1 in Chapter 2 to determine the extension numbers that are
associated with the PARTNER MAIL VS module. Then use Hunt Group Extensions (#505)
to verify that the VMS extensions are assigned to Hunt Group 7.
System Does Not Transfer Calls Properlv
Possible Cause 1: If this occurs when the Automated Attendant Service answers calls, the
Menu Definition may be programmed incorrectly.
What to do: Follow the steps for “Verifying System Operation” in Chapter 4 to test
Automated Attendant Service.
■ If outside calls are not transferred to the correct extension or group, follow the
instructions for “Menu Definition and Day Menu Prompt” as appropriate for
Monolingual or Bilingual Mode in Chapter 4 to reprogram the Menu Definition.
■ If outside calls are transferred to the correct extension or group, go to Possible
Cause 2.
Troubleshooting 6-3