|
Value (Hex)
|
Constant
|
Description
|
|
00000001
|
LINECALLSTATE_IDLE
|
The call exists but has not been connected. No activity exists on the
call, which means that no call is currently active. A call can never transition
out of the idle state.
|
|
00000002
|
LINECALLSTATE_OFFERING
|
The call is being offered to the station, signaling the arrival of a
new call. The offering state is not the same as causing a phone or computer
to ring. In some environments, a call in the offering state does not ring
the user until the switch instructs the line to ring. An example use might
be where an incoming call appears on several station sets but only the
primary address rings. The instruction to ring does not affect any call
states.
|
|
00000004
|
LINECALLSTATE_ACCEPTED
|
The call was in the offering state and has been accepted. This indicates
to other (monitoring) applications that the current owner application
has claimed responsibility for answering the call. In ISDN, the accepted
state is entered when the called-party equipment sends a message to the
switch indicating that it is willing to present the call to the called
person. This has the side effect of alerting (ringing) the users at both
ends of the call. An incoming call can always be immediately answered
without first being separately accepted.
|
|
00000008
|
LINECALLSTATE_DIALTONE
|
The call is receiving a dial tone from the switch, which means that the
switch is ready to receive a dialed number. See LINEDIALTONEMODE_ Constants
for identifiers of special dial tones, such as a stutter tone of normal
voice mail.
|
|
00000010
|
LINECALLSTATE_DIALING
|
The originator is dialing digits on the call. The dialed digits are collected
by the switch. Note that neither lineGenerateDigits nor TSPI_lineGenerateDigits
will place the line into the dialing state.
|
|
00000020
|
LINECALLSTATE_RINGBACK
|
The station to be called has been reached, and the destination's switch
is generating a ring tone back to the originator. A ringback means that
the destination address is being alerted to the call.
|
|
00000040
|
LINECALLSTATE_BUSY
|
The call is receiving a busy tone. A busy tone indicates that the call
cannot be completed—either a circuit (trunk) or the remote party's station
are in use. See LINEBUSYMODE_ Constants.
|
|
00000080
|
LINECALLSTATE_SPECIALINFO
|
The call is receiving a special information signal, which precedes a
prerecorded announcement indicating why a call cannot be completed. See
LINESPECIALINFO_ Constants.
|
|
00000100
|
LINECALLSTATE_CONNECTED
|
The call has been established and the connection is made. Information
is able to flow over the call between the originating address and the
destination address.
|
|
00000200
|
LINECALLSTATE_PROCEEDING
|
Dialing has completed and the call is proceeding through the switch or
telephone network. This occurs after dialing is complete and before the
call reaches the dialed party, as indicated by ringback, busy, or answer.
|
|
00000400
|
LINECALLSTATE_ONHOLD
|
The call is on hold by the switch. This frees the physical line, which
allows another call to use the line.
|
|
00000800
|
LINECALLSTATE_CONFERENCED
|
The call is a member of a conference call and is logically in the connected
state.
|
|
00001000
|
LINECALLSTATE_ONHOLDPENDCONF
|
The call is currently on hold while it is being added to a conference.
|
|
00002000
|
LINECALLSTATE_ONHOLDPENDTRANSFER
|
The call is currently on hold awaiting transfer to another number.
|
|
00004000
|
LINECALLSTATE_DISCONNECTED
|
The remote party has disconnected from the call.
|
|
00008000
|
LINECALLSTATE_UNKNOWN
|
The call exists, but its state is currently unknown. This may be the
result of poor call progress detection by the service provider. A call
state message with the call state set to unknown may also be generated
to inform the TAPI DLL about a new call at a time when the actual call
state of the call is not exactly known.
|