 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
These bit-flag constants describe different busy signals that the switch or network can generate. These busy signals typically indicate that a different resource that is required to make a call is currently in use.
The following table shows the LINEBUSYMODE constants.
| Value | Description |
|---|---|
|
LINEBUSYMODE_STATION = 0x00000001 |
The busy signal indicates that the called party's station is busy. This is usually signaled with a normal busy tone. |
|
LINEBUSYMODE_TRUNK = 0x00000002 |
The busy signal indicates that a trunk or circuit is busy. This is usually signaled with a fast busy tone. |
|
LINEBUSYMODE_UNKNOWN = 0x00000004 |
The busy signal's specific mode is currently unknown but may become known later. |
|
LINEBUSYMODE_UNAVAIL = 0x00000008 |
The busy signal's specific mode is unavailable and will not become known. |
Remarks
The high-order 16 bits can be assigned for device-specific extensions. The low-order 16 bits are reserved.
 Note: |
|---|
| Busy signals can be sent as inband tones or out-of-band messages. TAPI makes no assumption about the specific signaling mechanism. |
Requirements
| Header | tapi.h |
| Windows Embedded CE | Windows CE 3.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |