Aastra OpenAttendant 210 User Guide OpenAttendant 205 - Page 7

Creating a Voice Portal, Configurator, System: Licences, OpenAttendant, system, action, Audio

Page 7 highlights

OpenAttendant - Internet access to generate the activation key on the Aastra licensing server using these details. 2. You can find notes on how to proceed when generating the activation key in the licence confirmation. 3. In the Configurator's System: Licences menu, enter the activation key for the OpenAttendant programme package. This activates the package. Then save the OpenCom 100 / Aastra 800 configuration. The activation key is then also saved in the configuration file. In the event of servicing, you can reimport this configuration file and the OpenAttendant programme package is then reactivated. Creating a Voice Portal You create a voice portal on the OpenCom 100 / Aastra 800 Web console in the Configurator's OpenAttendant menu. The OpenAttendant programme manages a voice portal in a system. Each system consists of at least one menu. The menu contains definitions about which information a caller receives with which key on this telephone (= action) or with which employees, voiceboxes and other switching systems it can be connected (= reaction of the voice portal). The OpenAttendant manages up to 10 systems and a total of 50 menus in which you can define up to 500 actions. Text, music and sounds you want to use in the voice portal are saved in audio files. You assign these audio files to the menus of a voice portal. The OpenAttendant is not supplied with any systems, menus or audio files, so proceed as follows when configuring it for the first time: 1. In the Audio menu, load the audio files you will need or record them (see also Recording and Editing Audio Files starting on page 4). Use the KDA Manager programme to do this. 2. In the Menu menu, configure the menus required for user guidance in the voice portal. The appendix contains a template with which you can plan and document the individual menus and their actions and reactions (see Menu Template starting on page 9). The chapter Tips for Planning a Voice Portal starting on page 4 contains some points you should pay attention to with regard to user guidance. 3. In the Systems menu, configure at least one system (voice portal) and assign the menus to it. 3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16

OpenAttendant
3
– Internet access to generate the activation key on the Aastra licensing server
using these details.
2.
You can find notes on how to proceed when generating the activation key in
the licence confirmation.
3.
In the
Configurator
’s
System: Licences
menu, enter the activation key for the
OpenAttendant programme package. This activates the package.
Then save the OpenCom 100 / Aastra 800 configuration. The activation key is then
also saved in the configuration file. In the event of servicing, you can reimport this
configuration file and the OpenAttendant programme package is then reacti-
vated.
Creating a Voice Portal
You create a voice portal on the OpenCom 100 / Aastra 800 Web console in the
Configurator
’s
OpenAttendant
menu.
The OpenAttendant programme manages a voice portal in a
system
. Each system
consists of at least one
menu
. The menu contains definitions about which infor-
mation a caller receives with which key on this telephone (=
action
) or with which
employees, voiceboxes and other switching systems it can be connected (=
reaction of the voice portal).
The OpenAttendant manages up to 10 systems and a total of 50 menus in which
you can define up to 500 actions.
Text, music and sounds you want to use in the voice portal are saved in audio files.
You assign these audio files to the menus of a voice portal.
The OpenAttendant is not supplied with any systems, menus or audio files, so
proceed as follows when configuring it for the first time:
1.
In the
Audio
menu, load the audio files you will need or record them (see also
Recording and Editing Audio Files starting on page 4). Use the KDA Manager
programme to do this.
2.
In the
Menu
menu, configure the menus required for user guidance in the
voice portal. The appendix contains a template with which you can plan and
document the individual menus and their actions and reactions (see Menu
Template starting on page 9). The chapter Tips for Planning a Voice Portal
starting on page 4 contains some points you should pay attention to with
regard to user guidance.
3.
In the
Systems
menu, configure at least one system (voice portal) and assign
the menus to it.