|
Address-Related Functions and Messages
Different line devices can have different capabilities and so can their
addresses. Additionally, switching features and capabilities can be different for
different addresses. An application calls the function lineGetAddressCaps to determine the telephony capabilities of each address and then receives
this information in a data structure of the type LINEADDRESSCAPS. In a similar way, an application can call lineGetDevCaps for a line device to determine the number of addresses assigned to the line,
as well as other information.
TAPI's device-query capability and status and event reporting mechanisms give
an application the information it needs to manage the different kinds of
bridged-address arrangements. For example, the application can determine whether a
bridged station has answered a call by tracking the status changes and call-state
event changes on the address. (For more information about call states, see
Call States and Events.)
Normally, addresses on a line device are identified by their address IDs.
However, TAPI lets applications that make outgoing calls use alternate address
types for the originating address, such as dialable format (see the following
section), or naming mechanisms specific to a given service provider. This can be
accomplished through API extensions that are based on switch-assigned station IDs.
A useful function for this purpose is lineGetAddressID, which retrieves the ID of an address specified in an alternate format.
Related Links
Software for Delphi and C++ Builder developers
Software for Visual Studio .NET developers
Software for Visual Basic 6 developers
Delphi Tips&Tricks
MegaDetailed.NET
More Online Helps
Win32 Programmer's Reference (win32.hlp)
Win32 Multimedia Programmer's Reference (mmedia.hlp)
OLE Programmer's Reference (ole.hlp)
Microsoft Windows Pen API Programmer's Reference (penapi.hlp)
Microsoft Windows Sockets 2 Reference (sock2.hlp)
Unix Manual Pages
|
