The LINEDISCONNECTMODE_ bit-flag constants 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
This is a normal disconnect request by the remote party. The call was
The reason for the disconnect request is unknown but may become known later.
The remote user has rejected the call.
The call was picked up from elsewhere.
The call was forwarded by the switch.
The remote user's station is busy.
The remote user's station does not answer.
The destination address is invalid.
The remote user could not be reached.
The network is congested.
The remote user's station equipment is incompatible with the type of call
The reason for the disconnect is unavailable and will not become known later.
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). This can also occur without a service-provider-defined timeout period or
without a value specified in the dwWaitForDialTone
member of the LINEDIALPARAMS
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).
The call could not be connected or was disconnected because of a temporary
failure in the network; the call can be reattempted later and will eventually
The call could not be connected or was disconnected because the minimum
quality of service could not be obtained or sustained. This differs from
LINEDISCONNECTMODE_INCOMPATIBLE in that the lack of resources may be a temporary condition
at the destination.
The call could not be connected because calls from the origination address are
not being accepted at the destination address. This differs from
LINEDISCONNECTMODE_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 may 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).
The call could not be connected because the destination has invoked the Do Not
The high-order 16 bits can be assigned for device-specific extensions. The
low-order 16 bits are reserved.
A remote disconnect request for a given call results in the call state
transitioning to the disconnected
state and a LINE_CALLSTATE
message is sent to the application. The LINEDISCONNECTMODE_ information
provides details about the remote disconnect request. It is available in the call's LINECALLSTATUS
structure when the call is in the disconnected
state. While a call is in this state, the application is still allowed to
query the call's information and status. For example, user-to-user information
that is received as part of the remote disconnect is available then. The
application can clear a disconnected
call by dropping the call.
For backward compatibility, it is the responsibility of the service provider
to examine the negotiated API version on the line, and to not use this
LINEDISCONNECTMODE_ value if it is not supported on the negotiated version
(LINEDISCONNECTMODE_NORMAL or _UNKNOWN could be used instead).
- Software for developers
Software for Android Developers
- More information resources
Unix Manual Pages