Connection-Oriented Operations Performed by Call Managers (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 call manager performs the following connection-oriented operations:

• Registers and deregisters one or more address families

  A call manager registers one or more address families with NDIS (see Registering and Opening an Address Family). By registering an address family, a call manager registers the entry points of its call manager functions with NDIS and also advertises its call manager services (specifically, a signaling protocol) to bound connection-oriented clients.

• Registers and deregisters SAPs at the request of a connection-oriented client

  A call manager receives a bound connection-oriented client's requests to register SAPs (see Registering a SAP) and to deregister SAPs (see Deregistering a SAP). The call manager sends signaling messages over the network to register or deregister SAPs on behalf of clients.

• Sets up an outgoing call at the request of a connection-oriented client

  When a connection-oriented client makes an outgoing call, the call manager communicates (exchanges signaling messages) with network control devices, as necessary, to make a connection (see Making a Call). If the call is accepted by the remote party, the call manager activates the VC created for the call (see Activating a Call).

• Sets up and indicates an incoming call to a connection-oriented client

  A call manager indicates to a bound connection-oriented client all calls addressed to a SAP registered by that client (see Indicating an Incoming Call). Before indicating the incoming call to the client, the call manager initiates creation of a VC for the call (see Creating a VC) and then initiates activation of the VC (see Activating a VC).

• Communicates requests for a change in QoS

  Depending on the signaling protocol, the call manager can communicate a request from the local client to change the QoS for an outgoing or incoming call (see Client-Initiated Request to Change Call Parameters) or a request from the remote party to change the QoS for a call (see Incoming Request to Change Call Parameters).

• Communicates requests to add and drop parties

  A call manager communicates a local client's request to add a party to or drop a party from a point-to-multipoint call (see Adding a Party to a Multipoint Call and Dropping a Party from a Multipoint Call). A call manager also communicates a remote party's incoming request to drop itself from a point-to-multipoint call (see Incoming Request to Drop a Party from a Multipoint Call).

• Tears down a call

  At the request of a connection-oriented client, a call manager closes a call by communicating with network control devices to terminate a connection (see Client-Initiated Request to Close a Call). At the request of a remote party, a call manager indicates to a local connection-oriented client a remote party's request to close a call (see Incoming Request to Close a Call). In the process of tearing down a call, the call manager deactivates the VC used for the call (see Deactivating a VC). If the call manager created the VC (for an incoming call), the call manager can also delete the VC (see Deleting a VC).

• Queries or sets information

  A call manager can query or set information maintained by a bound connection-oriented client (see Querying or Setting Information). A call manager can also respond to query and set operations from a bound connection-oriented client.

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

• Inputs miniport driver status indications

  A call manager inputs status indications from a bound connection-oriented miniport driver (see Indicating Miniport Driver Status).

• Resets a NIC

  A call manager can cause a connection-oriented miniport driver to reset its NIC (see Reset).

Send comments about this topic to Microsoft