CO_SPECIFIC_PARAMETERS structure
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.
Depending on the type of structure that contains it, the CO_SPECIFIC_PARAMETERS structure passes call manager-specific parameters between a connection-oriented client and a call manager (or MCM driver), passes medium-specific parameters between a call manager (or connection-oriented client) and a connection-oriented miniport driver and its NIC, or passes PVC-specific parameters to a call manager from a connection-oriented client.
Syntax
typedef struct _CO_SPECIFIC_PARAMETERS {
ULONG ParamType;
ULONG Length;
UCHAR Parameters[1];
} CO_SPECIFIC_PARAMETERS, *PCO_SPECIFIC_PARAMETERS;
Members
ParamType
Specifies the type of parameters at Parameters:CALLMGR_SPECIFIC_Q2931
The buffer at Parameters contains Q.2931 call manager-specific parameters.ATM_MEDIA_SPECIFIC
The buffer at Parameters contains ATM medium-specific parameters.
Length
Specifies the size in bytes of the buffer at Parameters.Parameters
Specifies a variable-length array that contains call manager-specific parameters, media-specific parameters, or protocol-specific parameters that describe a PVC. The number and type of elements in the array depend on the particular task for which CO_SPECIFIC_PARAMETERS is being used.
Remarks
CO_SPECIFIC_PARAMETERS is a variable-sized structure that can be extended with any array that contains protocol-specific parameters. CO_SPECIFIC_PARAMETERS includes type and length members that allow vendors to specify various implementations of the structure.
The address of a buffered CO_SPECIFIC_PARAMETERS structure is a member of the following structures:
CO_MEDIA_SPECIFIC PARAMETERS
CO_PVC
When referenced by a CO_CALL_MANAGER_PARAMETERS structure, the CO_SPECIFIC_PARAMETERS structure contains call manager-specific parameters. For example, the CO_SPECIFIC_PARAMETERS structure could contain parameters specific to the Q.2931 signaling protocol. In this case, the ParamType would be CALLMGR_SPECIFIC_Q2931 and Parameters would be an array that contains Q.2931-specific parameters.
When referenced by a CO_MEDIA_PARAMETERS structure, the CO_SPECIFIC_PARAMETERS structure contains medium-specific parameters. For example, the CO_SPECIFIC_PARAMETERS structure could contain ATM media-specific parameters. In this case, the ParamType would be ATM_MEDIA_SPECIFIC and Parameters would be an array that contains the ATM media-specific parameters.
When referenced by a CO_PVC structure, CO_SPECIFIC_PARAMETERS contains protocol-specific parameters that describe a PVC. A client passes an OID_CO_ADD_PVC and a buffered CO_PVC structure or an OID_CO_DELETE_PVC and a buffered CO_PVC structure with NdisCoRequest. This client call requests that the call manager's ProtocolCoRequest function add the specified PVC to its list of configured PVCs. In this case, the ParamType is ignored, and Parameters is an array that contains the protocol-specific parameters that describe the PVC.
ParamType is meaningful only to a connection-oriented client and to the call manager or integrated miniport call manager (MCM) driver with which the client has opened an address family. A driver can therefore set ParamType to a driver-defined value that is recognized by the call manager or MCM driver.
Requirements
Header |
Ndis.h (include Ndis.h) |
See also