Table of Contents
Advertisement
3 &Conference
4 &Directory
5 &Ready
6 Re&lease
7 &WrapUp
#7 DT&MF
8 &Answer
#8 &Messages
# ----------------------------------------------------------------
# Enabling rules for buttons
# These control the actions taken and conditions enabled. For any
# desired action or state destination, follow this with states
# that will allow this action (qualifiers). If none are given,
# then the state transition or action is always available. Up to
# four qualifiers may be given for each entry.
#
# If there is no entry for a button, that button will have no
# effect. Entries that do not appear in a particular GUI design
# are ignored.
#
# Rule# to_state_or_action_code from_state1 from_state2...
#
# Additional rules may be given for the "down" state of a button.
# When these appear, the button is shown in the "down" state and
# its rule changes to that for this state. This allows any button
# to function as a "toggle", where the button picture shows the
# current state. A good example is a Hold button. It is available
# if in the InCall state. When pressed, the Hold button shows as a
# depressed button and, when pressed again, it uses the "down"
# state rule to return to the InCall state.
#
# Example:
## Rule1 Available InCall WrapUp
#
It moves you to the Available state.
#
It is only enabled if you are in the InCall or WrapUp state.
#
Annotated vtel.ini file
Issue 2.1 August 2003
117
Advertisement
Table of Contents
