LINECALLREASON_
Constants
The LINECALLREASON_
bit-flag constants describe the reason for a call.
LINECALLREASON_DIRECT
This is a
direct inbound or outbound call.
LINECALLREASON_FWDBUSY
This call was
forwarded from another extension that was busy at the time of the call.
LINECALLREASON_FWDNOANSWER
The call was
forwarded from another extension that didn't answer the call after some number
of rings.
LINECALLREASON_FWDUNCOND
The call was
forwarded unconditionally from another number.
LINECALLREASON_PICKUP
The call was
picked up from another extension.
LINECALLREASON_UNPARK
The call was
retrieved as a parked call.
LINECALLREASON_REDIRECT
The call was
redirected to this station.
LINECALLREASON_CALLCOMPLETION
The call was
the result of a call completion request.
LINECALLREASON_TRANSFER
The call has
been transferred from another number.
LINECALLREASON_REMINDER
The call is a
reminder (or "recall") that the user has a call parked or on hold for
(potentially) a long time.
LINECALLREASON_UNKNOWN
The reason
for the call is currently unknown but may become known later.
LINECALLREASON_UNAVAIL
The reason
for the call is unavailable and will not become known later.
LINECALLREASON_INTRUDE
The call
intruded onto the line, either by a call completion action invoked by another
station or by operator action. Depending on switch implementation, the call may
appear either in the connected state, or conferenced with an
existing active call on the line.
LINECALLREASON_PARKED
The call was
parked on the address. Usually, it appears initially in the onhold
state.
LINECALLREASON_CAMPEDON
The call was
camped on the address. Usually, it appears initially in the onhold
state, and can be switched to using lineSwapHold
LINECALLREASON_ROUTEREQUEST
The call
appears on the address because the switch needs routing instructions from the
application. The application should examine the CalledID member in LINECALLINFO
No
extensibility. All 32 bits are reserved.
The
LINECALLREASON_ constants are used in the dwReason field of the LINECALLINFO
data structure.
For backward
compatibility, it is the responsibility of the service provider to examine the
negotiated API version on the line, and to not use these LINECALLREASON_ values
if not supported on the negotiated version (LINECALLREASON_UNAVAIL may be
substituted).