Filter
Top Products
350 Dialogic
®
Global Call IP Technology Guide — November 2007
Dialogic Corporation
Third Party Call Control (3PCC) Operations and Multimedia Support
GC_SINGLECALL and GC_ALLCALLS duration defines imply that the data set is valid for the
entire length of the call.
Refer to Section 4.3, “Setting Call-Related Information”, on page 121 for an overview of the
GC_SINGLECALL and GC_ALLCALLS duration defines.
Note: If the host application needs to set a CRN's or a device's parameters with different duration defines,
then the application must call gc_SetUserInfo( ) multiple times. All parameters set within a single
gc_SetUserInfo( ) function call have the same duration value.
5.2.2.6 Events
Table 23 provides information about the events that have been added to the Dialogic
®
Global Call
API library to support third party call control mode. The application must use the
gc_SetConfigData( ) function to register for the events in Table 23. These events are only valid
when the Dialogic
®
Global Call API library is initialized in 3PCC mode:
5.2.2.7 Error Codes
Table 24 provides information about the error codes that have been added to the library to support
third party call control mode. These error codes are only valid when the Dialogic
®
Global Call API
library is initialized in 3PCC mode:
Table 23. Global Call Third Party Call Control Mode Events
Global Call Event Description
Third Party Call Control
Mode Notes
GCEV_SIP_200OK Unsolicited event posted to application upon
reception of a SIP 200 OK message on an
active dialog (not in received responses to BYE
or OPTIONS messages).
The application must register for this event.
Application should call
gc_SipAck( ) in response
to this event.
GCEV_SIP_ACK Unsolicited event posted to application upon
reception of a SIP ACK message on an active
dialog (not posted during BYE or OPTIONS
transactions).
The application must register for this event.
This event may include
IPSET_SDP in attached
parameter block.
GCEV_SIP_ACK_FAILED Failure completion termination event,
associated with the gc_SipAck( ) function.
This event may indicate a
message transport failure.
GCEV_SIP_ACK_OK Successful completion termination event,
associated with the gc_SipAck( ) function.
Indicates that the SIP ACK
message was sent. It does
not mean the SDP content,
if any, was valid.