PFNBTHPORT_INDICATION_CALLBACK callback function (bthddi.h)

Profile drivers implement a L2CAP callback function to provide the Bluetooth driver stack with a mechanism to notify the profile driver about incoming L2CAP connection requests from remote devices, and any changes to the status of a currently open L2CAP connection.



void PfnbthportIndicationCallback(
  [in] PVOID Context,
  [in] INDICATION_CODE Indication,


[in] Context

For incoming remote connection request indications, this is the context specified by the profile driver in the IndicationCallbackContext member of the _BRB_L2CA_REGISTER_SERVER structure when the profile driver registered the callback function. For changes to existing L2CAP connections, this is the CallbackContext member specified by the profile driver when it built and sent a _BRB_L2CA_OPEN_CHANNEL BRB.

[in] Indication

An INDICATION_CODE value that indicates the type of L2CAP event.

[in] Parameters

An INDICATION_PARAMETERS structure that contains event-specific parameters.

Return value



A profile driver registers its L2CAP callback function in the following two scenarios:

  1. When a profile driver acts as a server, it registers a L2CAP callback function using the IndicationCallback member of the _BRB_L2CA_REGISTER_SERVER structure. The Bluetooth driver stack can then notify the profile driver when a remote device attempts to contact it.
  2. When the profile driver acts as a client and attempts to connect to a remote device using the BRB_L2CA_OPEN_CHANNEL BRB, the profile driver registers its L2CAP callback function using the Callback member of the _BRB_L2CA_OPEN_CHANNEL structure that is passed when the profile driver builds and sends a BRB_L2CA_OPEN_CHANNEL or BRB_L2CA_OPEN_CHANNEL_RESPONSE request.
After the profile driver registers its L2CAP callback function, the callback function is only associated with the channel that the BRB opened. The Bluetooth driver stack can call the L2CAP callback function to notify the profile driver of actions that occur over the open channel to the remote device. Profile drivers can register a single callback function to handle channel notifications as a client and connection notifications as a server.

The INDICATION_PARAMETERS structure held in the Parameters parameter is interpreted according to the value of the INDICATION_CODE enumeration that the Bluetooth driver stack passes to the profile driver's L2CAP callback function through the Indication parameter. For most notifications, there is an INDICATION_PARAMETERS union member that corresponds to the event and contains event-specific parameters.


Minimum supported client Versions:_Supported in Windows Vista, and later.
Target Platform Desktop
Header bthddi.h (include Bthddi.h)
IRQL Developers should code this function to operate at either IRQL = DISPATCH_LEVEL (if the callback function does not access paged memory), or IRQL = PASSIVE_LEVEL (if the callback function must access paged memory)

See also