CO_CALL_MANAGER_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.

The CO_CALL_MANAGER_PARAMETERS structure specifies parameters that a call manager uses to set up an outgoing call and that a connection-oriented client uses to determine whether to accept an incoming call. Connection-oriented clients and call managers can also use CO_CALL_MANAGER_PARAMETERS to request a change of call parameters for a VC. In addition, when adding a party to a multipoint call, a connection-oriented client uses CO_CALL_MANAGER_PARAMETERS to specify the address of the new party.

Syntax

typedef struct _CO_CALL_MANAGER_PARAMETERS {
  FLOWSPEC               Transmit;
  FLOWSPEC               Receive;
  CO_SPECIFIC_PARAMETERS CallMgrSpecific;
} CO_CALL_MANAGER_PARAMETERS, *PCO_CALL_MANAGER_PARAMETERS;

Members

  • Transmit
    Pointer to a FLOWSPEC structure that specifies generic quality of service (QoS) parameters such as token rate, latency, and bandwidth, for packet transmission. For more information about the FLOWSPEC structure, see the Microsoft Windows SDK.

  • Receive
    Pointer to a FLOWSPEC structure that specifies generic QoS parameters such as token rate, latency, and bandwidth, for packet reception. For more information about the FLOWSPEC structure, see the Windows SDK.

  • CallMgrSpecific
    Pointer to a CO_SPECIFIC_PARAMETERS structure that contains information specific to the signaling protocol used by the call manager and that can be specific to the call manager, as well.

Remarks

The address of a buffered CO_CALL_MANAGER_PARAMETERS structure is a member of a CO_CALL_PARAMETERS structure. The CO_CALL_MANAGER_PARAMETERS structure specifies generic transmit and receive parameters that are of interest to all connection-oriented miniport drivers. The CO_CALL_MANAGER_PARAMETERS structure also contains call manager-specific parameters that are specific to a signaling protocol and possibly to a particular call manager that supports the protocol.

The following sections describe the role of the CO_CALL_MANAGER_PARAMETERS structure in connection-oriented operations:

Making an Outgoing Call

Before making an outgoing call with NdisClMakeCall, a client must fill in the portions of the CO_CALL_MANAGER_PARAMETERS structure that the call manager needs to set up the call. Typically, the client fills in the structures at Transmit and Receive to specify the quality of service (QoS) for the call. The client can also fill in the structure at CallMgrSpecific with any protocol-specific information, such as the destination address, needed to set up the call. The call manager typically interprets values in the buffers at Transmit and Receive to set up any protocol-specific state needed in its call setup messages and to set up media-specific parameters needed to activate the VC after establishing a connection through the network.

The mix of generic and specific parameters that a client supplies to the call manager depends on the requirements and capabilities of both the client and call manager. Note that call manager-specific parameters override any conflicting generic call manager parameters. The client can specify media-specific information at MediaParameters in the CO_CALL_PARAMETERS structure, but the call manager can overwrite these parameters if the call parameters for the call are changed through negotiation.

Indicating an Incoming Call

On an incoming call, the call manager extracts call parameters from a signaling message and maps these values to call-manager parameters at CallMgrParameters and media parameters at MediaParameters of the CO_CALL_PARAMETERS structure. Before calling NdisCmDispatchIncomingCall or NdisMCmDispatchIncomingCall, the call manager must fill in the call manager-specific parameters in the CO_CALL_MANAGER_PARAMETERS structure that the client requires to determine whether to accept the call. These parameters might include the destination SAP and the source SAP of the incoming call. The call manager can also supply generic (FLOWSPEC) parameters that the client can inspect to determine whether to accept the call, reject the call, or request a change in QoS, depending on the signaling protocol.

Requesting a Change in Call Parameters for a VC

Before requesting a change in call parameters on a VC by calling NdisClModifyCallQoS, the client must fill in the appropriate generic and/or call manager-specific parameters in the CO_CALL_MANAGER_PARAMETERS structure. The call manager must do the same before calling NdisCmDispatchIncomingCallQoSChange or NdisMCmDispatchIncomingCallQoSChange to indicate an incoming request to change the call parameters on a VC. The signaling protocol determines which parameters, if any, can be changed. The client's and call manager's capabilities determine the possible mix of generic and specific call manager parameters. Note that call manager-specific parameters override any conflicting generic call manager parameters.

Adding a Party to a Multipoint VC

Before calling NdisClAddParty, a client must specify the address of the new party in the call manager-specific parameters at CallMgrSpecific of the CO_CALL_MANAGER_PARAMETERS structure. The underlying network medium determines whether a client can specify per-party traffic parameters on a multipoint VC for an outgoing call.

Requirements

Header

Ndis.h (include Ndis.h)

See also

CO_CALL_PARAMETERS

CO_MEDIA_PARAMETERS

CO_SPECIFIC_PARAMETERS

NdisClAddParty

NdisClMakeCall

NdisClModifyCallQoS

NdisCmDispatchIncomingCallQoSChange

NdisMCmDispatchIncomingCallQoSChange

Send comments about this topic to Microsoft