TAPI extension OIDs for connection-oriented NDIS
The following table summarizes OIDs that allow TAPI calls to be made over connection-oriented media. Connection-oriented clients send these OIDs to call managers or integrated miniport call manager (MCM) drivers.
In this table, M indicates an OID is mandatory, while O indicates it is optional.
| Length | Query | Set | Name |
|---|---|---|---|
| Varies | O | OID_CO_TAPI_ADDRESS_CAPS | |
| Sizeof(CO_TAPI_CM_CAPS) | O | OID_CO_TAPI_CM_CAPS | |
| Varies | O | OID_CO_TAPI_GET_CALL_DIAGNOSTICS | |
| Varies | O | OID_CO_TAPI_LINE_CAPS | |
| Varies | O | OID_CO_TAPI_TRANSLATE_NDIS_CALLPARAMS | |
| Varies | O | OID_CO_TAPI_TRANSLATE_TAPI_CALLPARAMS | |
| Varies | O | OID_CO_TAPI_TRANSLATE_TAPI_SAP |
In its call to NdisCoRequest, the client that queries any of the TAPI extension OIDs must specify an NdisAfHandle that identifies the address family to which the request applies. The client can specify an NdisVcHandle that identifies the virtual connection (VC) to which the request applies. From this VC handle, the call manager or MCM driver may be able to derive the particular line and perhaps the address to which the request applies.