CoNDIS TAPI Registration (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.
This section discusses how a CoNDIS WAN miniport driver indicates that it supports TAPI services and how it sets up TAPI-specific communications with the NDISWAN and NDPROXY drivers.
After a CoNDIS WAN miniport driver has registered its miniport driver entry points for one or more NICs, the following operations cause the NDISWAN and NDPROXY drivers to become associated, in a TAPI-specific way, with those NICs.
The CoNDIS WAN miniport driver calls the NdisMCmRegisterAddressFamily function from within its MiniportInitialize function to register its call manager entry points and the address family type CO_ADDRESS_FAMILY_TAPI_PROXY. By doing so, the miniport driver advertises that it provides TAPI services.
NDIS calls NDPROXY's ProtocolCoAfRegisterNotify function to notify NDPROXY of the newly registered address family. NDPROXY's ProtocolCoAfRegisterNotify examines the address-family data and determines that it can use the TAPI services provided by the call manager that is integrated into the CoNDIS WAN miniport driver. A TAPI-capable CoNDIS WAN miniport driver is an integrated miniport call manager (MCM) driver.
NDPROXY calls the NdisClOpenAddressFamily function to open the TAPI-proxy address family that is associated with the CoNDIS WAN miniport driver. NdisClOpenAddressFamily registers NDPROXY's connection-oriented entry points with NDIS. These entry points are used to communicate with a TAPI-capable CoNDIS WAN miniport driver.
NDPROXY calls NdisCmRegisterAddressFamily to register its call manager entry points and the address family type CO_ADDRESS_FAMILY_TAPI. By doing so, NDPROXY advertises that it implements TAPI services.
NDIS calls NDISWAN's ProtocolCoAfRegisterNotify function to notify NDISWAN of the newly registered address family. NDISWAN's ProtocolCoAfRegisterNotify examines the address-family data and determines that NDISWAN can use the TAPI services provided by NDPROXY.
NDISWAN calls the NdisClOpenAddressFamily function to open the TAPI address family that is associated with NDPROXY. NdisClOpenAddressFamily registers NDISWAN's connection-oriented entry points with NDIS. These entry points are used to communicate with NDPROXY.
NDISWAN calls the NdisClRegisterSap function to inform NDPROXY that NDISWAN can accept incoming calls on a particular Service Access Point (SAP). In this call, NDISWAN passes a CO_SAP structure that describes the SAP. NDISWAN sets the SapType member of CO_SAP to AF_TAPI_SAP_TYPE to specify that the SAP will be used for TAPI calls. NDISWAN sets the Sap member of CO_SAP to a string for a particular TAPI device class. A TAPI application provides this string when the application calls the TAPI lineGetID function. NDPROXY should notify NDISWAN about all incoming calls addressed to the SAP.