The Dtmfint Table - Avaya Octel 200 Installation And Maintenance Manual

3-6 Integration Volume
3.4

THE DTMFINT TABLE

The DTMFINT Table interprets an incoming DTMF call record by identifying the type of call, matching
it with a suitable call action by the Octelt200/300 message server, and collecting the called and calling
party ID.
Individual PBX manufacturers send proprietary DTMF codes to identify call types and will send the
various items of information in the order they choose. The DTMFINT Table is very flexible to
accommodate the great variety of call record formats encountered.
The Octel 200/300 configures a default DTMFINT Table for a specific PBX model when System
Parameter 3 — PBX TYPE, is modified. Changes can be made using the detailed configuration
information contained in this section.
The key to understanding the DTMFINT Table is to recognize that the order of elements in a call record
format specified by the PBX manufacturer is the pattern that the DTMFINT Table must reproduce. The
string of DTMF digits sent by the PBX to the Octel 200/300 contains some or all of the following items:
Call type code
-
Called party ID
-
Calling party ID
-
Miscellaneous separators
-
Configuring the DTMFINT Table requires identifying all the possible call record formats (20 maximum)
that will be sent as DTMF digits and making entries in the DTMFINT Table to match them. The types of
calls that a particular PBX can support depends on the PBX's own capabilities.
The first set of DTMF digits in a call record identifies the call type and must be a unique DTMF digit
string. For each call type (See Table 3-1 for possible call types), the Octel 200/300 determines which
prompt the message server plays and what action it takes. The message server interprets the remaining
DTMF digits in a call record according to the specific call record type.
The following is an example of a DTMFINT Table.
Octel 200/300 S.4.1 PB60019-01