Windows Mobile 6.5
A version of this page is also available for

This function removes the specified call from the conference call to which it currently belongs. The remaining calls in the conference call are unaffected.

LONG WINAPI lineRemoveFromConference(
  HCALL hCall 


Handle to the call to be removed from the conference. The application must be an owner of this call. The call state of hCall must be conferenced.

Returns a positive request identifier if the function is completed asynchronously, or a negative error number if an error occurs. The dwParam2 parameter of the corresponding LINE_REPLY message is zero if the function succeeds or it is a negative error number if an error occurs. The following table shows the return values for this function.

Value Description


The handle to the call to be removed is invalid.


The operation is unavailable.


The call state is something other than conferenced.


The operation failed.


Not enough memory is available.


The resources are unavailable.


The application is not an owner of this call.


A parameter is uninitialized.

This operation removes a party that currently belongs to a conference call. After the call has been successfully removed, it may be possible to further manipulate it using its handle. The availability of this operation and its result are likely to be limited in many implementations. For example, in many implementations, only the most recently added party can be removed from a conference, and the removed call can be automatically dropped (becomes idle). Consult the line's device capabilities to determine the available effects of removing a call from a conference.

If the removal of a participant from a conference is supported, the participant call, after it is removed from the conference, enters the call-state listed in the dwRemoveFromConfState member in LINEADDRESSCAPS.

This function is for TAPI version 2.0 and later.

Windows Embedded CEWindows CE 1.0 and later
Windows MobileWindows Mobile Version 5.0 and later

Community Additions