Registering 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.
If a client accepts incoming calls, its ProtocolClOpenAfCompletefunction (see Registering and Opening an Address Family) usually registers one or more SAPs with the call manager by calling NdisClRegisterSap.
The following figure shows a client of a call manager registering a SAP.
.png)
The following figure shows a client of an MCM driver registering a SAP.
.png)
With the call to NdisClRegisterSap, a client requests notifications of incoming calls on a particular SAP. NDIS forwards the SAP information supplied by the client to the call manager's or MCM driver's ProtocolCmRegisterSapfunction for validation. If the given SAP is already in use or if the call manager or MCM driver does not recognize the client-supplied SAP specification, the call manager or MCM driver fails this request.
In ProtocolCmRegisterSap, the call manager or MCM driver might communicate with network control devices or other media-specific agents to register the SAP on the network for a connection-oriented client. ProtocolCmRegisterSap also stores an NDIS-supplied NdisSapHandlethat represents the SAP.
ProtocolCmRegisterSap can complete synchronously or asynchronously. To complete asynchronously, the ProtocolCmRegisterSap function of a call manager calls NdisCmRegisterSapComplete. The ProtocolCmRegisterSap function of an MCM driver calls NdisMCmRegisterSapComplete. The call to Ndis(M)CmRegisterSapComplete causes NDIS to call the client's ProtocolClRegisterSapCompletefunction.
If the client's call to NdisClRegisterSapis successful, NDIS returns to the client an NdisSapHandle that represents the SAP.
After a call manager registers a SAP on behalf of a connection-oriented client, it notifies that client of an incoming call offer directed to that SAP by calling NdisCmDispatchIncomingCall. An MCM driver calls NdisMCmDispatchIncomingCall(see Indicating an Incoming Call). A client can receive incoming calls on a SAP even while SAP registration is still pending; that is, before its ProtocolClRegisterSapComplete function is called.