TAPIEx ActiveX Control v3.6


The OnDisConnected event is fired when the remote party hang up the call.

Event OnDisConnected(
m_Call As TAPICall,


Reference to ITAPICALL.
describe different reasons for a remote disconnect request. A disconnect mode is available as call status to the application after the call state transitions to disconnected.

Value Meaning
DISCONNECTMODE_BADADDRESS The destination address is invalid.
The call could not be connected because calls from the origination address are not being accepted at the destination address. This differs from DISCONNECTMODE_REJECT in that blocking is implemented in the network (a passive reject) while a rejection is implemented in the destination equipment (an active reject). The blocking can be due to a specific exclusion of the origination address, or because the destination accepts calls from only a selected set of origination address (closed user group).
DISCONNECTMODE_BUSY The remote user's station is busy.
The call was cancelled.
DISCONNECTMODE_CONGESTION The network is congested.
DISCONNECTMODE_DONOTDISTURB The call could not be connected because the destination has invoked the Do Not Disturb feature.
DISCONNECTMODE_FORWARDED The call was forwarded by the switch.
DISCONNECTMODE_INCOMPATIBLE The remote user's station equipment is incompatible with the type of call requested.
DISCONNECTMODE_NOANSWER The remote user's station does not answer.
A dial tone was not detected within a service-provider defined timeout, at a point during dialing when one was expected (such as at a "W" in the dialable string).
DISCONNECTMODE_NORMAL This is a normal disconnect request by the remote party. The call was terminated normally.
DISCONNECTMODE_NUMBERCHANGED The call could not be connected because the destination number has been changed, but automatic redirection to the new number is not provided.
The call could not be connected or was disconnected because the destination device is out of order (hardware failure).
DISCONNECTMODE_PICKUP The call was picked up from elsewhere.
The call could not be connected or was disconnected because the minimum quality of service could not be obtained or sustained. This differs from DISCONNECTMODE_INCOMPATIBLE in that the lack of resources may be a temporary condition at the destination.
The remote user has rejected the call.
The call could not be connected or was disconnected because of a temporary failure in the network; the call can be reattempted later and is expected to eventually complete. (TAPI versions 2.0 and later)
DISCONNECTMODE_TEMPFAILURE is appropriate as a delayed response. For example, a modem getting a busy signal or equivalent too many times in a particular time period concludes that the number should not be called again until a defined time has elapsed and issues a 'delayed' response.
The reason for the disconnect is unavailable and will not become known later.
The reason for the disconnect request is unknown but may become known later.
The remote user could not be reached.



See Also