DTEV_CASTEVTThis event type is sent for all unsolicited CAS DTI messages sent to the application. The sr_getevtdatap( ) function must be used to return a pointer to the associated DTCAS_DETECTED_MSG message block. The typedef for the DTCAS_DETECTED_MSG structure is as follows:
typedef struct t_detected_msg {
unsigned char msg_code;
unsigned char flags;
unsigned short template_id;
unsigned short result;
unsigned short count;
unsigned int timestamp;
} DTCAS_DETECTED_MSG;
Parameter |
Description |
msg_code |
identifies the message type and must be set to NTT_CAS_TEMPLATE_MATCH |
flags |
is reserved and must be set to zero for future compatibility |
template_id |
identifies the template detected |
count |
identifies the number of pulse detected |
timestamp |
identifies the time of occurrence of this event, and it is a value of the VTRX system clock; each tick represents 1 millisecond, and the granularity of the timestamp is 10; since this is VTRX system clock, this could be used by the application as a relative time |
DTEV_CASSENDENDEVTThis event type is sent to the application after an application initiated signal pattern transmission is complete. The sr_getevtdatap( ) function must be used to return a pointer to the associated DTCAS_END_TRANSMIT_MSG message block. The typedef for the DTCAS_END_TRANSMIT_MSG structure is as follows:
typedef struct t_detected_msg {
unsigned char msg_code;
unsigned char rfu;
unsigned short template_id;
unsigned short pulse_count;
unsigned short sequence_count;
unsigned int timestamp;
} DTCAS_DETECTED_MSG;
Parameter |
Description |
msg_code |
identifies the message type and must be set to NTT_CAS_TEMPLATE_SEND_END |
rfu |
is reserved and must be set to zero for future compatibility |
template_id |
identifies the template detected |
pulse_count |
identifies the number of pulse detected |
sequence_count |
is reserved for future use and should be ignored by the application |
timestamp |
identifies the time of occurrence of this event, and it is a value of the VTRX system clock; each tick represents 1 millisecond, and the granularity of the timestamp is 10; since this is VTRX system clock, this could be used by the application as a relative time |
Click here to contact Dialogic Customer Engineering
Copyright 2001, Dialogic Corporation