Edit

Share via

Incoming Request to Drop a Party from a Multipoint Call

  • Article

A call manager or MCM driver is alerted to an incoming request from a remote party to drop that party from a multipoint call by signaling messages from the network. A call manager or MCM driver can also signal an incoming request to drop a party if it detects network problems that prevent further data transfers on the VC.

If the party that is being dropped from the call is not the last party on the VC, a call manager calls NdisCmDispatchIncomingDropParty. An MCM driver calls NdisMCmDispatchIncomingDropParty. If the party that is being dropped is the last party on the VC, a call manager calls NdisCmDispatchIncomingCloseCall, and an MCM driver calls NdisMCmDispatchIncomingCloseCall(see Incoming Request to Close a Call).

A call to Ndis(M)CmDispatchIncomingDropParty causes NDIS to call the client's ProtocolClIncomingDropParty function.

The following shows an incoming request through a call manager to drop a party through a multipoint call.

Diagram illustrating an incoming request to drop a party through a multipoint call via a call manager.

The next figure shows an incoming request through an MCM driver to drop a party through a multipoint call.

Diagram illustrating an incoming request to drop a party through a multipoint call via an MCM driver.

ProtocolClIncomingDropParty should carry out any protocol-determined operations for dropping the party from the client's multipoint VC. If the party that is being dropped is not the last party on the VC, ProtocolClIncomingDropParty must call NdisClDropParty(see Dropping a Party from a Multipoint Call). If the party being dropped is the last party on the VC, ProtocolClIncomingDropParty must call NdisClCloseCall(see Client-Initiated Request to Close a Call).