Discussion:
CAPI Disconnect
(too old to reply)
Kinfe Tadesse
2006-04-28 08:35:31 UTC
Permalink
Hi All,

My understanding so far is that it is the application that initiates
Disconnect with DISCONNECT_B3_REQ. It then waits for DISCONNECT_B3_CONF. The
communication between CAPI and the App. continues with DISCONNECT_B3_IND,
.... until a disconnect is handled with DISCONNECT_RESP.

I have written some functions to do these sequences of operations to handle
disconnect, but I get something like "Disconnect B3 Request Fail..."
message.

On the other hand, I think it should be CAPI that initiates Disconnect
because it is the first one to detect a hung up. I am confused. Any
explanation is highly appreciated.

Best regards,

KT
mm
2006-04-29 14:09:52 UTC
Permalink
Hi KT;

You might want to have a look at CAPI Spec Part 1 page 137. Call
Clearing.
If the peer hangs up it is a passive disconnect. Your application
receives a DisconnectB3Ind.
If your application hangs up it is an active disconnect. Your
application issues a DisconnectB3Req.

Bye
Michael

Loading...