Feature description "speed dial"
--------------------------------

A new MIB table pabxSpeedDialTable was introduced to allow for arbitrary quick
access of lengthy phone numbers via abbreviation numbers, what is usually called
speed dialling.
The table consists of the three fields "ShortCut", "Number" and "Ctrl".
"ShortCut" contains the abbreviation number for the actual phone number stored
in field "Number". The field "Ctrl" on one hand indicates whether an entry is
currently valid (value "on") or invalid (value "off") and on the other hand
allows to delete an existing entry via SNMP shell (value "delete").
It is possible to store complete numbers in Number field just as storing only
prefixes so that additional digits can be supplied by manual dialling
afterwards.
Field "Ctrl" provides the possibility to temporarily disable table entries by
setting it to "off" without actually removing them from the table.
Currently "speed dialling" has some shortcomings:
 - it is not configurable by setup tool (though shown by Dial Plan)
 - speed dial numbers cannot be used recursively (most likely irrelevant)
 - auto dialout numbers - if used - are not taken into account
The last item means that in a mixed configuration where part of users has an
autodialout number configured and the other part has not, one speed dial entry
(for an external number) will only work for one part depending on how Number is
set (i.e. with or without a trunk prefix in the beginning).

Examples:

1) Shortcut="*09110"  Number="091196730"  Ctrl="on"

Assuming an autodialout number is configured the above example will dial
BinTec's operator from anywhere within germany by just dialling "*09110".

2) Shortcut="*0911"  Number="09119673"  Ctrl="on"

Again assuming autodialout being configured in this example you call BinTec's
subscriber number by dialling "*0911". You have to supply digits for desired
extension manually afterward, e.g. "0" for operator.

Without active autodialout and a valid trunk prefix of "0" "Number" in above
examples would have to be "0091196730" for example 1) and "009119673" for
example 2).

BTW:
It doesn't make sense to configure both of the above examples while shortcut
"*0911" will always match and, hence, "*09110" will never be processed by
XCentric, independently from what digits are dialled beyond the shortcut (sure
enough acting identically for a dialstring of "*09110").

CAUTION:
You have to bear in mind already used commands (for analog ports and globally
ones like call pickup) when configuring shortcuts beginning with '*'.
Global commands might be disabled due to shadowing (like "*09110" in case
both examples ablove were configured at a time), others might require additional
digits; shortcut "*030" for example would have to be used by dialling "**030"
from an analog port as an initial '*' is not really dialled but indicates a
command to follow and must therefore be followed by another '*' to cause one
'*' to be dialled.