TAPI Extensions for Connection-Oriented NDIS

The following chart 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.

LengthQSName

Varies

O

OID_CO_TAPI_ADDRESS_CAPS
Requests the telephony capabilities for a specified address on a specified line

Sizeof (CO_TAPI_CM_CAPS)

O

OID_CO_TAPI_CM_CAPS
Requests the telephony capabilities of a call manager's or MCM driver's device

Varies

O

OID_CO_TAPI_GET_CALL_DIAGNOSTICS
Requests information about a failed call or a call torn down by the remote TAPI party

Varies

O

OID_CO_TAPI_LINE_CAPS
Requests the telephony capabilities for a specified line and whether addresses on that line have dissimilar telephony capabilities

Varies

O

OID_CO_TAPI_TRANSLATE_NDIS_CALLPARAMS
Requests a call manager or MCM driver to translate NDIS call parameters into TAPI call parameters

Varies

O

OID_CO_TAPI_TRANSLATE_TAPI_CALLPARAMS
Requests a call manager or MCM driver to translate TAPI call parameters into NDIS call parameters

Varies

O

OID_CO_TAPI_TRANSLATE_TAPI_SAP
Requests a call manager or MCM driver to use TAPI call parameters to prepare one or more SAPs

 

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.

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft