Manager: Configuration Settings
|
Manager: Configuration Settings
|
|
Auto Attendant Settings |
|
The IP Office Small Office Edition, IP406 V2 and IP500 control units support embedded voicemail. This is setup by adding an Avaya embedded voicemail memory card to the control unit and then selecting Embedded Voicemail as the Voicemail Type on the System | Voicemail tab.
|
The IP406 V2 and IP500 support up to 4 simultaneous calls to embedded voicemail services. The Small Office Edition supports up to 10 simultaneous calls to embedded voicemail depending on available voice compression channels. A call from an IP device to voicemail uses two voice compression channels on the Small Office Edition.
| • | For pre-IP Office 4.1 systems up to 4 auto-attendant services are supported. |
| • | For IP Office 4.1 and higher systems up to 40 auto-attendant services are supported. Due to this increase in the number of possible auto attendant, the method of automatic short code creation for recording prompts has been amended. |
In addition to basic mailbox functionality, embedded voicemail can also provide auto-attendant operation. Each auto attendant can use existing time profiles to select the greeting given to callers and then provide follow on actions relating to the key presses 0 to 9, * and #.
| • | Time Profiles Each auto attendant can use up to three existing time profiles, on each for Morning, Afternoon and Evening. These are used to decide which greeting is played to callers. They do not change the actions selectable by callers within the auto attendant. If the time profiles overlap or create gaps, then the order of precedence used is morning, afternoon, evening. |
| • | Greetings Four different greetings are used for each auto attendant. One for each time profile period. This is then always followed by the greeting for the auto-attendant actions. By default a number of system short codes are automatically created to allow the recording of these greetings from an IP Office extension. See below. |
| • | Actions Separate actions can be defined for the DTMF keys 0 to 9, * and #. Actions include transfer to a specified destination, transfer to another auto-attendant transfer to a user extension specified by the caller (dial by number) and replaying the greetings. |
| • | IP Office 4.0+ supports the Fax action. This can be used to reroute fax calls when fax tone is detected by the auto-attendant. |
| • | IP Office 5.0+ supports the Dial by Name action. |
| • | Short Codes Adding an auto attendant automatically adds a number of system short codes. These use the Auto Attend short code feature. These short codes are used to provide dialing access to record the auto attendant greetings. |
| • | For pre-IP Office 4.1 systems, 4 system short codes are added for each auto attendant. These use a telephone number of the form AA:Name.1 where Name is replaced by the Auto Attendant name. |
| • | For IP Office 4.1+ systems, 4 system short codes (*81XX, *82XX, *83XX and *84XX) are added for use use with all auto attendants, one each for the morning, afternoon, evening and menu options greetings. These use a telephone number of the form AA:N.1 where N is the replaced with the auto attendant number when dialing. |
| • | You can add additional short codes using either form of telephone number to suit the customer requirements. |
| • | Routing Calls to the Auto Attendant The telephone number format AA:Name can be used to route callers to an auto attendant. It can be used in the destination field of incoming call routes and telephone number field of short codes set to the Auto Attend feature. |
|
© 2009 AVAYA 15-601011 Issue 23.p.- 07:06, 30 October 2009 (auto_attendant_settings.htm) Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners. Last Modified: 29/01/2009 |
