Filter
Top Products
EXTENSIONEVTBLK structure which in turn contains a GC_PARM_BLK that includes all of the
data in the message.
See Section 9.2.14, “IPSET_MSG_Q931”, on page 523 and Section 9.2.18,
“IPSET_NONSTANDARDDATA”, on page 526 for more information.
The following code shows how to set up and send a Q.931 nonstandard facility message.
char ObjId[]= "1 22 333 4444";
char NSData[]= "DataField_Facility";
GC_PARM_BLKP gcParmBlk = NULL;
gc_util_insert_parm_val(&gcParmBlk,
IPSET_MSG_Q931,
IPPARM_MSGTYPE,
sizeof(int),
IP_MSGTYPE_Q931_FACILITY);
gc_util_insert_parm_ref(&gcParmBlk,
IPSET_NONSTANDARDDATA,
IPPARM_NONSTANDARDDATA_OBJID,
sizeof(ObjId),
ObjId);
gc_util_insert_parm_ref_ex(&gcParmBlk,
IPSET_NONSTANDARDDATA,
IPPARM_NONSTANDARDDATA_DATA,
sizeof(NSData),
NSData);
gc_Extension( GCTGT_GCLIB_CRN,
crn,
IPEXTID_SENDMSG,
gcParmBlk,
NULL,
EV_ASYNC);
gc_util_delete_parm_blk(gcParmBlk);
4.17.3 Nonstandard Registration Message
To send a nonstandard registration message, use the gc_Extension( ) function in asynchronous
mode with an ext_id (extension ID) of IPEXTID_SENDMSG. The target_type should be
GCTGT_CCLIB_NETIF and the target_id should be the board device handle, since the message
destination is the Gatekeeper. The GC_PARM_BLK must contain parameter elements that identify
H.323 protocol, the message type, the nonstandard data, and the nonstandard data identifier. The
application receives a GCEV_EXTENSIONCMPLT event to indicate that the message has been
sent.
The following parameter element sets the protocol to be H.323:
IPSET_PROTOCOL
IPPARM_PROTOCOL_BITMASK
• value = IP_PROTOCOL_H323