Avaya Interaction Center Programmer's Manual page 113

# -----Phone type
# This affects the information needed for Login, and the Login Dialog shown. While
# this shows the phone's capabilities, a non-agent may still login to an ACD
# oriented Dialog. Typically, ACD applies to Aspect, EAS to Definity, and MRD to
# Meridian.
# PhoneType Direct
# PhoneType ACD
# PhoneType EAS
# PhoneType MRD
PhoneType
# Type of Dial Directory that will be displayed with the Directory
# button.
DirectoryGuiType
#DirectoryGuiType
# -----Background color selection
# The following two assignments determine dialog
# background colors. The first sets the color of the
# main dialog. The second sets the color of all other
# dialogs. The values are specified as hexadecimal COLORREFs.
# You may select the system defaults by either omitting the
# assignments or by specifying a value of FFFFFFFF (8 'F's).
# For more information on COLORREFs, please consult the
# Windows API Reference.
MainBackground FFFFFFFF
OtherBackground FFFFFFFF
# -----Custom Options
##Custom0 IVR
##Custom0 callinfo
# If True, Call History Search will display VDUs from the entire
# WAN. Otherwise, only VDUs from the local VDU Object Store will
# be displayed.
WANCallHistory
# -----Associated program execution
The behavior of the WinExec command corresponds to the behavior of the Windows Run
command. That is, the entries that follow the WinExec command in the VTEL.INI file are
treated in exactly the same way as if you had inserted these same entries after a Run
command executed from your terminal.
# When VTel starts, WinExec is called for the following. Any
# number of lines may be added to start many programs.
#WinExec <program_name>
# -----Server Failure Processing
EAS
DirStandard
DirSortable
# IVR prefix info needed for Call History;
# uncomment when Call History in use.
# Generates CallInfo event when uncommented.
n
Annotated vtel.ini file
Issue 2.1 August 2003 113