Table of Contents
Advertisement
C H A P T E R
7 :
O P T I O N S
7.2.2 Constructing or Modifying a CAS Protocol Table
The protocol table text file is a textual file containing the protocol's state
machine that defines the whole protocol process. It is constructed of States,
pre-defined Actions/Events, and pre-defined Functions.
Thus, the user has full control of the CAS protocol by a relatively simple
textual tool. The user is capable of defining or changing any CAS protocol by
writing the protocol state machine in a text file with a few simple rules.
The user procedure to generate the protocol file is as follows:
Learn the protocol text file rules which are explained in the
following sections. Rules detailed in this manual and syntax are
based on C pre-processor commands.
Get example files provided by Opticom. These files can be found in
the directory ~\E1_T1 Protocols where "~" represents the OPERA™
installation directory. For instance, you might want to have a look at
the directory ~\E1_T1 Protocols\T1_CAS\E_M_WinkStart.
Build the specific protocol table text file (xxx.txt) and its related
numerical value header file (xxx.h).
Compile the xxx.txt with the
produce the xxx.dat file. Refer to Section 7.4 for a detailed
description of the utility usage.
Re-initialize the E1/T1 interface using OptiConf™.
7.2.3 Table Elements
The file CASSetup.h includes all the pre-defined tools needed to build a new
protocol text file or modifying an existing one. The protocol table text file is
composed of the following elements:
INIT variables
The user can change the numeric values of INIT variables in
UserProt_defines_xxx.h. For example, INIT_RC_IDLE_CAS defines the
ABCD bits expected to be received in the IDLE state, INIT_DTMF_DIAL
defines the on-time and off-time for the DTMF digits generated towards the
PSTN. See the detailed list in CASSetup.h and in the sample protocol text
file. Please refer to the ST_INIT detailed explanation below.
Actions
Actions (i.e. protocol table events) are protocol table events activated either
by the DSP (e.g. EV_CAS_01) or by the user (e.g., EV_PLACE_CALL,
EV_TIMER_EXPIRED1). The full list of the possible pre-defined events list
can be found in the CASSetup.h file.
F O R
A D V A N C E D
U S E R S
Downloadable Conversion Utility
35
to
Advertisement
Table of Contents
