If the client originally created this VC for an outgoing call, It is the responsibility of the call manager to destroy or reuse any VC that it ProtocolClIncomingCloseCall should return control after it calls Whether the given VC is a single-point or multipoint connection,Ĭlient will neither attempt to send nor expect to receive data on this particular VC. Only a single party remains on its multipoint VC. The client's own client(s) that the connection is being broken. ProtocolClIncomingCloseCall should carry out any protocol-determined operations, such as notifying The call manager has detected that network problems will prevent further data transfers on the NdisVcHandle that the client stored in its per-VC context area at The call manager has received a request over the network to close an established connection, ProtocolClIncomingCloseCall indicates that the one of the following has occurred: Specifies the size in bytes of the buffer at However, any particular call manager mightĭefine a structure to pass additional diagnostic information to its clients on call teardowns caused by Not support transfers of data when closing a connection. Remote client that the call manager received over the network, or this parameter can be NULL.ĬloseStatus is NDIS_STATUS_SUCCESS, this parameter is NULL if the underlying network medium does Pointer to a buffer containing a protocol-specific close message, possibly one supplied by the NdisVcHandle that it stored in this context area. Specifies the handle to the client's per-VC context area for the VC on which the connection isĬloseStatus, the client can neither send nor receive data on the VC designated by the Any other value indicates that problems on the network caused the call manager to terminate the NDIS_STATUS_SUCCESS to indicate that the remote party to the call requested that the connection beĬlosed. Specifies the status that indicates the cause of the connection teardown, which is usually Syntax PROTOCOL_CL_INCOMING_CLOSE_CALL ProtocolClIncomingCloseCall
0 kommentar(er)
