Поделиться через

Non-WAN-Specific Extensions to Support Telephonic Services Over Connection-Oriented NDIS (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 topic describes non-WAN-specific extensions for TAPI support over connection-oriented NDIS. These extensions are the NDIS/TAPI translation OIDs. These extensions allow non-WAN-specific call managers and integrated miniport call manager (MCM) drivers to translate TAPI parameters to NDIS parameters or TAPI parameters to NDIS parameters. These extensions allow call managers and MCMs that support ATM, for example, to provide TAPI access over connection-oriented media. For information about WAN-specific extensions for TAPI support over connection-oriented NDIS, see CoNDIS WAN Operations that Support Telephonic Services.

The NDIS/TAPI translation OIDs should not be used for call managers or MCMs that respectively register CO_ADDRESS_FAMILY_TAPI_PROXY with NdisCmRegisterAddressFamilyor NdisMCmRegisterAddressFamily. Instead, such call managers and MCMs, as well as their TAPI clients, should encapsulate TAPI parameters inside connection-oriented structures, as described in CoNDIS WAN Operations that Support Telephonic Services.

The NDIS/TAPI translation OIDs are as follows:

  • OID_CO_TAPI_TRANSLATE_TAPI_CALLPARAMS

    This OID requests a call manager or MCM to translate TAPI call parameters supplied by the client to NDIS call parameters. The client typically uses the NDIS call parameters returned by the call manager or MCM as an input (formatted as a CO_CALL_PARAMETERS structure) to NdisClMakeCall. The client uses NdisClMakeCall to initiate a connection-oriented call.

  • OID_CO_TAPI_TRANSLATE_NDIS_CALLPARAMS

    This OID requests a call manager or MCM to translate NDIS call parameters for an incoming call (passed in a CO_CALL_PARAMETERS structure to the client's ProtocolClIncomingCall function) to TAPI call parameters. The client uses the translated TAPI call parameters returned by the call manager or MCM to determine whether to accept or reject the incoming call.

  • OID_CO_TAPI_TRANSLATE_SAP

    This OID requests a call manager or MCM to prepare one or more NDIS SAPs from TAPI call parameters that are supplied by the client. The client typically uses an NDIS SAP returned by the call manager or MCM as an input (formatted as a CO_SAP structure) to NdisClRegisterSap, with which the client registers a SAP on which to receive incoming calls.

 

 

Send comments about this topic to Microsoft