User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 98
Dialogic Corporation
1.32.1 Feature Description
To test the various tones from various countries, the Tone-On/Off Call Status Transition
(CST) event data have been modified to add a time stamp structure to the end of the
TN_INFO structure. The CST event data are obtained by calling sr_getdatalen( ) and
sr_getevtdatap( ). A new structure, TN_TIMESTAMP, is in the device header file,
dxxxlib.h. If the event is for Tone-On, then the time stamp represents the tone-on time, and
if the event is for Tone-Off, then it represents the tone-off time.
The Tone-On/Tone-Off messages are extended to add the “start time” and the “stop time,”
respectively. These time stamps are used by the customer application to calculate the
Tone-On/Tone-Off duration (cadence).
1.32.2 Supported Boards
The following boards support this feature:
• Dialogic
®
DM/V2400A Media Boards
1.32.3 Structure
TN_TIMESTAMP is as follows:
// Tone ON/OFF time stamp
typedef struct {
unsigned long tn_TimeStamp; /* Time stamp for tone on/off event. The time stamp is in
milliseconds from when the firmware was downloaded on the
board. There is no co-relation to the system time. It wraps
around every ~149 hours. */
} TN_TIMESTAMP;
Scenario
When a Tone-On CST event is received, the application gets the CST event data with the
sr_getdatalen( ) and sr_getevtdatap( ) functions, as usual. The application then applies
the TN_TIMESTAMP structure to the event data and obtains the time stamp of the tone-on
event or tone-off event. The TN_TIMESTAMP structure is appended to the end of the
TN_INFO structure. The CST event data comprises the DX_CST, TN_INFO, and
TN_TIMESTAMP structures.
Sample
The following is an example for Tone-On. Tone-Off is done the same way.
DX_CST *datap;
TN_INFO *tonep;
TN_TIMESTAMP *tsp;
long timestamp; // time stamp in ms units