// ndis.h
void NdisMCmDispatchIncomingCall(
_SH_,
_VH_,
_CP_
);
View the official Windows Driver Kit DDI referenceNo description available.
NdisMCmDispatchIncomingCall informs the client of an incoming call on a SAP previously registered by that client with the MCM driver.
_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.
Before calling NdisMCmDispatchIncomingCall, an MCM driver has already done the following:
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.
ProtocolCmIncomingCallComplete