User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 102
Dialogic Corporation
1.34.2 Enabling/Disabling GCEV_Extension Event
For the gc_SetConfigData( ) function, the bit mask (EXTENSIONEVT_RAWEEM) is
saved for use later during GCEV_EXTENSION event generation. The
gc_SetConfigData( ) is set on a channel basis and has the target type set as
GCTGT_CCLIB_CHAN. The general procedure is to call the gc_SetConfigData( )
function to implement the change as follows:
gc_SetConfigData(GCTGT_CCLIB_CHAN.EXTENSIONEVT_RAWEEM)
1.34.3 Successfully Sending and Receiving Raw DPNSS EEM
The gc_SndMsg(MsgType, GC_IE_BLK) is used to send the raw DPNSS EEM like other
DPNSS Supplementary Services (for example, Intrusion(SndMsg_Intrude),
Diversion(SndMsg_Divert), NSI (SndMsg_NSI), etc.). The general procedures are as
follows:
• To send an End to End Complete message, call the gc_SndMsg( ) function with the
msg_type parameter set to SndMsg_RawEEM. The first byte of the data portion (i.e.,
ie_Blk.data[0]) must contain 0x22 to indicate that it is an EEM(C) message. To receive
the message, enable the GCEV_EXTENSION event.
• To send an End to End Incomplete message, call the gc_SndMsg( ) function, with the
msg_type parameter set to SndMsg_RawEEM. The first byte of the data portion (i.e.,
ie_Blk.data[0]) must contain 0x23 to indicate that it is an EEM(I) message. To receive
the message, enable the GCEV_EXTENSION event.
The message is successfully received if no GCEV_TASKFAIL event is received at the user
application.
Notes:1. The first byte in the GC_IE_BLK is the spec defined Message ID for an EEM(I) or
EEM(C) message.
2. Certain supplementary information strings that may affect the firmware call state are not
allowed in the raw EEM payload. Specifically not allowed are the HOLD-REQ string or
60B, and the RECON string or 61. If either of these strings is present, the application
will receive a GCEV_TASKFAIL event.
3. The total length of the raw EEM payload allowed is 45 bytes: 1 byte specifies the EEM
type, which is EEM(C) or EEM(I), and 44 bytes are allowed for supplementary
information strings encoded using the Backus Naur format and conforming to the
DPNSS standard BTNR 188.
1.34.4 Sample Code
The following are samples of code for sending raw EEM and receiving raw EEM.
To Send Raw EEM
int send_message(CRN crn)
{