Filter
Top Products
release all internal resources cc_ReleaseCall( )
183
Name:
int cc_ReleaseCall(crn)
Inputs:
CRN crn
• call reference number
Returns:
0 on success
< 0 on failure
Includes:
cclib.h
Category:
Call control
Mode:
synchronous
Technology:
BRI/2; BRI/SC; PRI (all protocols)
!
! !
!
Description
The cc_ReleaseCall( ) function instructs the driver and firmware to release all
internal resources for the specified call. An inbound call will be rejected after
cc_DropCall( ) is used. Every issue of cc_DropCall( ) must be followed by
cc_ReleaseCall( ).
When cc_WaitCall( ) is used in synchronous mode and cc_ReleaseCall( ) is
issued subsequently, the next inbound call on the same channel will be pending
until the cc_WaitCall( ) function is issued again. If cc_WaitCall( ) is used in
asynchronous mode, the inbound call notification can be received immediately
after cc_ReleaseCall( ).
Parameter Description
crn:
The call reference number. Each call needs a CRN.
!
! !
!
Cautions
• Windows only: For new applications, it is recommended that the
cc_ReleaseCallEx( ) function be used instead of the cc_ReleaseCall( )
function. Under load conditions, or if the remote end delays transmitting the
RELEASE COMPLETE message, an application could experience a
significant delay while the cc_ReleaseCall( ) function unblocks and returns
control to the application. This delay can be up to 8 seconds long if the
RELEASE COMPLETE message is never returned. The cc_ReleaseCall( )
function is supported only in synchronous mode; therefore, this problem
occurs only in applications that use the asynchronous single-threaded
programming model. In this case, when this blocking function is called within
a handler processing the CCEV_DROPCALL event, it could create a