Compartir a través de


NdisMCmDispatchIncomingCallQoSChange (NDIS 5.1) function

Note   NDIS 5. x has been deprecated and is superseded by NDIS 6. x. For new NDIS driver development, see Network Drivers Starting with Windows Vista. For information about porting NDIS 5. x drivers to NDIS 6. x, see Porting NDIS 5.x Drivers to NDIS 6.0.

NdisMCmDispatchIncomingCallQoSChange notifies a client that a request to change the quality of service on that client's active connection has been received over the network.

Syntax

VOID NdisMCmDispatchIncomingCallQoSChange(
  _In_ NDIS_HANDLE         NdisVcHandle,
  _In_ PCO_CALL_PARAMETERS CallParameters
);

Parameters

  • NdisVcHandle [in]
    Specifies the handle to the VC for which the change in QoS is being requested. The MCM driver obtained this handle either when it called NdisMCmCreateVc to set up this connection for an incoming call or as an input parameter to its ProtocolCoCreateVc function.

  • CallParameters [in]
    Pointer to a structure of type CO_CALL_PARAMETERS that specifies the new QoS, requested by the client on the remote node, for this connection.

Return value

None

Remarks

An MCM driver calls NdisMCmDispatchIncomingCallQoSChange to notify the client that it has received a request to modify the QoS on an active connection. Such an MCM driver supports dynamic QoS changes on active calls, which is a feature like QoS itself that depends on the signaling protocol. For example, ATM networks do not support dynamic QoS changes on active connections.

The MCM driver should call NdisMCmActivateVc whenever it makes changes in the call parameters for an active VC.

A call to NdisMCmDispatchIncomingCallQoSChange causes NDIS to call the client's ProtocolClIncomingCallQosChange function. The client accepts the proposed modifications to the call parameters for the VC by doing nothing, except possibly updating any state it maintains about the QoS for the VC, and returning control. Otherwise, the client rejects the proposed QoS change by tearing down the call.

Only connection-oriented miniport drivers that provide integrated call-management support can call NdisMCmDispatchIncomingCallQoSChange. Stand-alone call managers, which register themselves with NDIS as protocols, call NdisCmDispatchIncomingCallQoSChange instead.

Requirements

Target platform

Desktop

Version

See NdisMCmDispatchIncomingCallQoSChange.

Header

Ndis.h (include Ndis.h)

IRQL

<= DISPATCH_LEVEL

See also

CO_CALL_PARAMETERS

NdisClCloseCall

NdisClModifyCallQoS

NdisCmDispatchIncomingCallQoSChange

NdisMCmActivateVc

NdisMCmCreateVc

ProtocolClIncomingCallQosChange

ProtocolCoCreateVc

 

 

Send comments about this topic to Microsoft