NdisMCmDispatchIncomingCall macro (ndis.h)

  • Article

NdisMCmDispatchIncomingCall informs the client of an incoming call on a SAP previously registered by that client with the MCM driver.

Syntax

void NdisMCmDispatchIncomingCall(
   _SH_,
   _VH_,
   _CP_
);

Parameters

_SH_

Specifies the handle identifying the SAP. NDIS set up this handle when the client originally called NdisClRegisterSap, and the MCM driver obtained this handle as an input parameter to its ProtocolCmRegisterSap function.

_VH_

Specifies the handle identifying the VC, created with NdisMCmCreateVc when the MCM driver processes the incoming call offer directed to this registered SAP.

_CP_

Pointer to a structure of type CO_CALL_PARAMETERS that specifies the call and media parameters for the VC.

Return value

None

Remarks

Before calling NdisMCmDispatchIncomingCall, an MCM driver has already done the following:

  • Identified the target SAP, previously registered by a particular client, for the call (actually, a request to make a connection) that it received over the network
  • Created a VC for the incoming call with NdisMCmCreateVc
  • Possibly negotiated about acceptable call parameters over the network, or accepted the call parameters sent from the remote node
  • Activated the VC with NdisMCmActivateVc to notify NDIS that it is ready for transfers on the VC in accord with the negotiated or accepted call parameters
The MCM driver's call to NdisMCmDispatchIncomingCall causes NDIS to call the client's ProtocolClIncomingCall function, within which the client either accepts or rejects the requested connection. After deciding whether to accept the connection, the client calls NdisClIncomingCallComplete, which, in turn, calls the MCM driver's ProtocolCmIncomingCallComplete function. If the client accepted the call, the MCM driver next calls NdisMCmDispatchCallConnected. Otherwise, it deactivates (and possibly deletes) the VC it created, after notifying the remote node that the offered call was rejected.

Only connection-oriented miniport drivers that provide integrated call-management support call NdisMCmDispatchIncomingCall. Stand-alone call managers, which register themselves with NDIS as protocol drivers, call NdisCmDispatchIncomingCall instead.

Requirements

Requirement Value
Minimum supported client Supported for NDIS 6.0 and NDIS 5.1 drivers (see NdisMCmDispatchIncomingCall (NDIS 5.1)) in Windows Vista. Supported for NDIS 5.1 drivers (see NdisMCmDispatchIncomingCall (NDIS 5.1)) in Windows XP.
Target Platform Desktop
Header ndis.h (include Ndis.h)
IRQL <= DISPATCH_LEVEL
DDI compliance rules Irql_MCM_Function(ndis)

See also

CO_CALL_PARAMETERS

MiniportInterruptDPC

NdisClIncomingCallComplete

NdisClRegisterSap

NdisCmDispatchIncomingCall

NdisMCmActivateVc

NdisMCmCreateVc

NdisMCmDeactivateVc

NdisMCmDeleteVc

NdisMCmDispatchCallConnected

ProtocolClIncomingCall

ProtocolCmIncomingCallComplete

ProtocolCmRegisterSap