LINEADDRESSSHARING
A version of this page is also available for
4/8/2010
These bit-flag constants describe various ways an address can be shared between lines.
The following table shows the LINEADDRESSSHARING constants.
| Value | Description |
|---|---|
LINEADDRESSSHARING_PRIVATE = 0x00000001 |
The address is private to the user's line. It is not assigned to any other station. |
LINEADDRESSSHARING_BRIDGEDEXCL = 0x00000002 |
The address is bridged to one or more other stations. The first line to activate a call on the line will have exclusive access to the address and calls that may exist on it. Other lines will not be able to use the bridged address while it is in use. |
LINEADDRESSSHARING_BRIDGEDNEW = 0x00000004 |
The address is bridged with one or more other stations. The first line to activate a call on the line will have exclusive access to only the corresponding call. Other applications that use the address will result in new and separate call appearances. |
LINEADDRESSSHARING_BRIDGEDSHARED = 0x00000008 |
The address is bridged with one or more other lines. All bridged parties can share in calls on the address, which then functions as a conference. |
LINEADDRESSSHARING_MONITORED= 0x00000010 |
This is an address whose idle/busy status is made available to this line. |
Remarks
These constants cannot be extended. All 32 bits are reserved.
The way in which an address is shared across lines can affect the behavior of that address. LINE_CALLSTATE and LINE_ADDRESSSTATE messages are sent to the application in response to activities by the bridging stations. It is through these messages that an application can track the status of the address.
Requirements
| Header | tapi.h |
| Windows Embedded CE | Windows CE 3.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |