Previous PageTable Of Contents../index.htmlIndexNext Page

cl_ReleaseTransaction( )

Description | Termination Events | Cautions | Example | Errors | See Also

Name:

int cl_ReleaseTransaction(hDevice, idTransaction)

Inputs:

long hDevice

  call logging device handle

 

long idTransaction

  call logging transaction ID

Returns:

0 on success
-1 on failure

-2 if call logging transaction already released

Includes:

cllib.h

Mode:

synchronous

Top Of PageDescription

The cl_ReleaseTransaction( ) function releases a call logging transaction. Once a transaction has been released, information about that particular call logging transaction can no longer be queried. Because a call logging system has no impact on a digital line and only observes the activity on the line, the cl_ReleaseTransaction( ) function does not drop the monitored call. Rather, the purpose of the function is to instruct the Call Logging API to release the internal resources allocated for the specified call logging transaction.

The cl_ReleaseTransaction( ) function is usually called from the call logging event handler when a CLEV_MESSAGE event is received and the event has the ECL_LAST_MESSAGE bit set in the iResult field of its call logging event data block (see 1.5.2. Retrieving Event Data for more information). If the cl_ReleaseTransaction( ) function is called before this specific event is received, the application will not receive any additional call logging events related to the specified call logging transaction.

Parameter

Description

hDevice:

The device handle of the call logging device.

idTransaction:

The call logging transaction ID to be released.

Top Of PageTermination Events

None

Top Of PageCautions

Top Of PageExample

Top Of PageErrors

If the function returns a value < 0, use the SRL Standard Attribute function ATDV_LASTERR( ) to obtain the error code or use ATDV_ERRMSGP( ) to obtain a descriptive error message. The error codes that can be returned by ATDV_LASTERR( ) are:

Error Code Value

Returned When

ECL_TRANSACTIONRELEASED

transaction already released

ECL_INTERNAL

internal Call Logging error; cause unknown

See 2.2 Error Handling for more information about what kinds of errors can cause these codes to be returned

Top Of PageSee Also


Previous PageTable Of ContentsTop Of PageIndexNext Page

Click here to contact Dialogic Customer Engineering

Copyright 2001, Dialogic Corporation
All rights reserved
This page generated February, 2002