NdisMCmDeleteVc (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.

NdisMCmDeleteVc destroys a caller-created VC.

Syntax

NDIS_STATUS NdisMCmDeleteVc(
  _In_ NDIS_HANDLE NdisVcHandle
);

Parameters

• NdisVcHandle [in]
  Specifies the handle identifying the VC to be deleted. The caller originally obtained this handle from NdisMCmCreateVc.

Return value

NdisMCmDeleteVc can return one of the following:

Remarks

When an MCM driver calls NdisMCmDeleteVc, there must be no outstanding calls on the given VC and that VC must have been deactivated. To meet these requirements implies that the MCM driver has already called NdisMCmDeactivateVc with the given NdisVcHandle successfully.

Only the driver that created a particular VC can delete that VC. A call to NdisMCmDeleteVc causes NDIS to call the ProtocolCoDeleteVc function of the client with which the caller shares the NdisVcHandle.

When NdisMCmDeleteVc returns control, the NdisVcHandle is no longer valid. The MCM driver can release the resources it allocated to maintain state about the deleted VC or prepare them for reuse in a subsequent incoming-call notification after it calls NdisMCmCreateVc.

The driver writer determines whether an MCM driver has an (internal) MiniportCoDeleteVc function that the driver calls in the context of tearing down connections for outgoing and incoming calls.

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

Requirements

See also

MiniportCoDeleteVc

NdisClCloseCall

NdisCoDeleteVc

NdisMCmDeactivateVc

NdisMCmCreateVc

ProtocolCoDeleteVc

Send comments about this topic to Microsoft