Avaya Interaction Center, Руководство программиста

Страница: 106 / 138

The vtel.ini configuration file
106 VTel Programmer Guide
Annotated
vtel.ini
file
The reproduced
vtel.ini
file presented here contains additional comments, explanatory
notes, and references to the VTel documentation that expand on the function described.
!
Important:
!
Important:
Important:
The file reproduced here is used with the stand-alone VTel application. The
vtel.ini
file used with Avaya Agent has different settings than those
described here.
# ----------------------------------------------------------------
# VTEL.INI
#
# VTel configuration file
# Syntactic rules:
# Arguments are delimited by one-or-more spaces and/or tabs
# Pound sign is a comment marker (#)
# Comment markers hold to end of line
# Blank lines are always ignored
# Multiple spaces ignored unless within label arguments
# Names are not case sensitive
# Order of items within a section does not matter
# Items not entered are given default values
# True or False can be any of:
# t true yes y on 1
# f false no n off 0
# ACD Phone States:
# We use simple and generic terms here, which will probably differ
# in some respect from those used at any specific customer site.
For additional discussion of terminology, see Definition of terms and concepts on page 13
.
# Ready The phone is available to receive an ACD call from a
# queue.
# Synonym: Available
#
# Busy The phone is not available for ACD calls; the queue
# will not send a call to a phone that is Busy. In most
# cases, however, direct calls can still arrive.
# Synonym: Auxiliary Work, Idle
#
# WrapUp The previous call has ended, but the operator is busy
# and working on items related to that call. The phone is
# effectively Busy, but separate time statistics are
# maintained here by the PBX and/or VTel.
# Synonym: After call work
#
# direct A call that is direct to the operator's station or
# logical phone number, and is not distributed by a phone
# queue. These calls have a separate set of rules from