| TAPIEx ActiveX Control v3.6 |
The OnCallStateChange event is fired when the status of the specified call has changed. Typically, several such messages are received during the lifetime of a call. Applications are notified of new incoming calls with this message; the new call is in the offering state.
Event OnCallStateChange( m_Call As TAPICall, NewState As TAPI_CALLSTATE);
Constant |
Value |
Description |
|---|---|---|
| CALLSTATE_ACCEPTED | 4 |
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. |
| CALLSTATE_BUSY | 64 |
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. |
| CALLSTATE_CONFERENCED | 2048 |
The call is a member of a conference call and is logically in the connected state. |
| CALLSTATE_CONNECTED | 256 |
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. |
| CALLSTATE_DIALING | 16 |
The originator is dialing digits on the call. The dialed digits are collected by the switch. |
| CALLSTATE_DIALTONE | 8 |
The call is receiving a dial tone from the switch, which means that the switch is ready to receive a dialed number. |
| CALLSTATE_DISCONNECTED | 16384 | The remote party has disconnected from the call. |
| CALLSTATE_IDLE | 1 |
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. |
| CALLSTATE_OFFERING | 2 |
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. |
| CALLSTATE_ONHOLD | 1024 |
The call is on hold by the switch. This frees the physical line, which allows another call to use the line. |
| CALLSTATE_ONHOLDPENDCONF | 4096 |
The call is currently on hold while it is being added to a conference. |
| CALLSTATE_ONHOLDPENDTRANSFER | 8192 |
The call is currently on hold awaiting transfer to another number. |
| CALLSTATE_PROCEEDING | 512 |
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. |
| CALLSTATE_RINGBACK | 32 |
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. |
| CALLSTATE_SPECIALINFO | 128 |
The call is receiving a special information signal, which precedes a prerecorded announcement indicating why a call cannot be completed. |
| CALLSTATE_UNKNOWN | 32768 |
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. |
If the method succeeds, the return value is TRUE.
None.
None.