Deregistering a SAP (NDIS 5.1)

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.

A connection-oriented client deregisters a SAP with NdisClDeregisterSap.

The following figure shows a client of a call manager deregistering a SAP.

The following figure shows a client of an MCM driver deregistering a SAP.

The call to NdisClDeregisterSapcauses NDIS to call the call manager's or MCM driver's ProtocolCmDeregisterSap function. In ProtocolCmDeregisterSap, the call manager or MCM driver might communicate with network control devices or other media-specific agents to deregister the SAP on the network. In addition, ProtocolCmDeregisterSap must free any resources that it dynamically allocated for the SAP.

ProtocolCmDeregisterSap can complete synchronously or asynchronously. To complete asynchronously, the ProtocolCmDeregisterSap function of a call manager calls NdisCmDeregisterSapComplete. The ProtocolCmDeregisterSap function of an MCM driver calls NdisMCmDeregisterSapComplete. NdisMCmDeregisterSapComplete notifies both NDIS and the client that the call manager has completed the SAP-deregistration request for which its ProtocolCmDeregisterSap function previously returned NDIS_STATUS_PENDING.

A call to NdisMCmDeregisterSapComplete causes NDIS to call the client's ProtocolClDeregisterSapComplete function. A call to ProtocolCmDeregisterSap indicates that the client's preceding call to NdisClDeregisterSaphas been processed by the call manager or MCM driver.

Note that a client can deregister a SAP without affecting an incoming call that has already been received on that SAP and without affecting the VC for that incoming call.

 

 

Send comments about this topic to Microsoft