NdisMCmModifyCallQoSComplete - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ndis.h
void NdisMCmModifyCallQoSComplete(
_S_,
_H_,
_P_
);
View the official Windows Driver Kit DDI referenceNo description available.
NdisMCmModifyCallQoSComplete indicates the completion of the client's request, for which the MCM driver previously returned NDIS_STATUS_PENDING, to modify the quality of service on a VC.
_S_Specifies the final status of the client's request to modify the QoS on this VC, either NDIS_STATUS_SUCCESS or any caller-determined NDIS_STATUS_XXXexcept NDIS_STATUS_PENDING.
_H_Specifies the handle to the VC, obtained from the per-VC state designated by the CallMgrVcContext passed in to the MCM driver's ProtocolCmModifyCallQoS function for this request.
_P_Pointer to a structure of type CO_CALL_PARAMETERS specifying a QoS acceptable to the MCM driver if Status is set to NDIS_STATUS_SUCCESS.
A call to NdisMCmModifyCallQoSComplete causes NDIS to call the client's ProtocolClModifyCallQoSComplete function.
The MCM driver should call NdisMCmActivateVc whenever it makes changes in the call parameters on an active VC.
Because the MCM driver can modify the client-supplied call parameters that were input to its ProtocolCmModifyCallQoS function before it calls NdisMCmModifyCallQoSComplete, the client's ProtocolClModifyCallQoSComplete function examines the QoS to determine whether it is acceptable to the client. ProtocolClModifyCallQoSComplete simply returns control if the client accepts the given call parameters. Otherwise, the client tears down the call.
Only connection-oriented miniport drivers that provide integrated call-management support can call NdisMCmModifyCallQoSComplete. Stand-alone call managers, which register themselves with NDIS as protocol drivers, call NdisCmModifyCallQoSComplete instead.
ProtocolClModifyCallQoSComplete