Compartir a través de


Connection-Oriented Operations Performed by Clients (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.

A connection-oriented client performs the following connection-oriented operations:

  • Opens and closes an address family

    On receiving notification from NDIS that a call manager or MCM driver has registered an address family, a connection-oriented driver can open that address family with the call manager or MCM driver (see Registering and Opening an Address Family). The client can then use the call manager services provided by the call manager or MCM driver. A client releases the association between itself and a call manager or MCM driver by closing the address family (see Closing an Address Family).

  • Registers and deregisters SAPs

    After opening an address family with a call manager or an MCM driver, a connection-oriented client can register one or more SAPs with the call manager or MCM driver (see Registering a SAP). The call manager or MCM driver will then indicate to the client any incoming calls addressed to the registered SAP(s). A client releases a SAP by deregistering it (see Deregistering a SAP).

  • Adds and deletes PVCs

    A connection-oriented client can monitor when an operator manually configures or deconfigures a permanent VC (PVC). In response to such an action, the client can request a call manager or MCM driver to add a PVC to its list of configured PVCs or to delete a PVC from such a list (see OID_CO_ADD_PVC and OID_CO_DELETE_PVC).

  • Makes outgoing calls

    Before making an outgoing call, a client must initiate the creation of a VC for the call (see Creating a VC). A client can then make an outgoing call (see Making a Call). To make a point-to-multipoint call, a client specifies a party when making the call.

  • Adds a party to or drops a party from a point-to-multipoint call

    A client can add a party to a point-to-multipoint call (see Adding a Party to a Multipoint Call) and delete a party from a point-to-multipoint call (see Dropping a Party from a Multipoint Call). A client can also respond to an incoming request to drop a party from a point-to-multipoint call (see Request to Drop a Party from a Multipoint Call).

  • Accepts or rejects an incoming call

    A client can accept or reject an incoming call addressed to a SAP that the client previously registered with a call manager or MCM driver (see Indicating an Incoming Call).

  • Negotiates the call parameters for an active VC

    Depending on what is allowed by the signaling protocol, a client can negotiate the call parameters for an active VC. A client can request a change in quality of service (QoS) (see Client-Initiated Request to Change Call Parameters) and respond to an incoming request to change the QoS for an active VC. A client can also respond to a request from the remote party to change the QoS for a call (see Incoming Request to Change Call Parameters).

  • Sends and receives packets

    A client can send packets through a connection-oriented miniport driver or MCM driver (see Sending Packets on a VC). A client can also receive packets through a connection-oriented miniport driver or MCM driver (see Receiving Packets on a VC).

  • Initiates the deletion of a VC

    A client can initiate the deletion of a VC that it created (see Deleting a VC).

  • Initiates the tear-down of a call

    A client can initiate the tear-down of a outgoing call that it made or an incoming call that it accepted (see Client-Initiated Request to Close a Call).

  • Queries or sets information

    A client can query or set information maintained by a bound call manager or the call manager portion of an MCM driver. A client can also respond to queries and sets from a bound call manager or MCM driver (see Querying or Setting Information).

    In addition, a client can query or set information maintained by a bound miniport driver or the miniport driver portion of a bound MCM driver (see Querying or Setting Information).

  • Inputs miniport driver status indications

    A client can input status indicated by a connection-oriented miniport driver or an MCM driver (see Indicating Miniport Driver Status).

  • Resets a NIC

    A connection-oriented client can cause a connection-oriented miniport driver or MCM driver to reset its NIC (see Reset).

 

 

Send comments about this topic to Microsoft