📄 ch32.htm
字号:
<html>
<head>
<title>Chapter 32 -- Part IV Summary-The Telephony API</title>
<meta NAME="GENERATOR" CONTENT="Microsoft FrontPage 3.0">
</head>
<body TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000EE" VLINK="#551A8B" ALINK="#CE2910">
<!-- Spidersoft WebZIP Ad Banner Insert -->
<!-- End of Spidersoft WebZIP Ad Banner Insert-->
<h1><font COLOR="#FF0000">Chapter 32</font></h1>
<h1><b><font SIZE="5" COLOR="#FF0000">Part IV Summary-The Telephony API</font></b> </h1>
<hr WIDTH="100%">
<h3 ALIGN="CENTER"><font SIZE="+2" COLOR="#000000">CONTENTS<a NAME="CONTENTS"></a> </font></h3>
<ul>
<li><a HREF="#Chapter22WhatIsTAPI">Chapter 22, "What Is TAPI?"</a> </li>
<li><a HREF="#Chapter23TAPIArchitecture">Chapter 23, "TAPI Architecture"</a> </li>
<li><a HREF="#Chapter24TAPIBasics">Chapter 24, "TAPI Basics"</a> </li>
<li><a HREF="#Chapter25TAPIHardwareConsideration">Chapter 25, "TAPI Hardware
Considerations"</a> </li>
<li><a HREF="#Chapter26TAPIToolsUsingtheTAPILI">Chapter 26, "TAPI Tools-Using the
TAPILINE Control"</a> </li>
<li><a HREF="#Chapter27TAPIBehindtheScenesThe">Chapter 27, "TAPI Behind the Scenes-The
TELEPHON.INI File"</a> </li>
<li><a HREF="#Chapter28UsingTAPItoHandleIncomi">Chapter 28, "Using TAPI to Handle
Incoming Calls"</a> </li>
<li><a HREF="#Chapter29WritingTAPIAssistedAppli">Chapter 29, "Writing TAPI-Assisted
Applications"</a> </li>
<li><a HREF="#Chapter30CreatingTAPIEnabledAppli">Chapter 30, "Creating TAPI-Enabled
Applications"</a> </li>
<li><a HREF="#Chapter31ThirdPartyTAPITools">Chapter 31, "Third-Party TAPI Tools"</a>
</li>
<li><a HREF="#TheFutureofTelephonyandTAPI">The Future of Telephony and TAPI</a> </li>
</ul>
<hr>
<h2><a NAME="Chapter22WhatIsTAPI"></a><b><a HREF="ch22.htm">Chapter 22</a><font SIZE="5"
COLOR="#FF0000">, "What Is TAPI?"</font></b></h2>
<p>In the first chapter of this section you learned the general outline of the TAPI model
including the use and meaning of two devices defined within the TAPI model:
<ul>
<li><i>Line devices</i> are used to model physical telephone lines. </li>
<li><i>Phone devices</i> are used to model physical telephone handsets. </li>
</ul>
<p>You also discovered the relative advantages and disadvantages of the four main types of
TAPI hardware configurations:
<ul>
<li><i>Phone-based</i>-for use in mostly voice-oriented calling </li>
<li><i>pc based</i>-for use in mostly pc-oriented calling </li>
<li><i>Shared</i> or <i>unified line</i>-for use when both voice and data share the phone
use equally </li>
<li><i>Multiline</i>-for use as a voice server (for voice-mail) or as a PBX server (for
computerized switchboards) </li>
</ul>
<p>Finally, you learned how to identify the four main types of telephone service used to
transmit voice and data signals:
<ul>
<li><i>Analog POTS</i> (<i>Plain Old Telephone Service</i>)-for general voice-grade
transmissions and for data transmission up to 28.8kbps speed </li>
<li><i>Digital T1</i>-for dedicated high-speed voice and/or data services (56kbps and above)
</li>
<li><i>ISDN</i> (<i>Integrated Services Digital Network</i>)-for high-speed multichannel
simultaneous voice and data services </li>
<li><i>PBX</i> (<i>Private Branch Exchange</i>)-for use within proprietary switchboard
hardware in an office setting </li>
</ul>
<h2><a NAME="Chapter23TAPIArchitecture"></a><b><a HREF="ch23.htm">Chapter 23</a><font
SIZE="5" COLOR="#FF0000">, "TAPI Architecture"</font></b></h2>
<p>In <a HREF="ch23.htm">Chapter 23</a> you learned how the TAPI service model is
implemented as a set of API calls. You learned there are four levels of TAPI services:
<ul>
<li><i>Assisted Telephony</i> provides the simplest form of TAPI service. </li>
<li><i>Basic Telephony</i> provides basic in- and outbound telephony services for a
single-line phone. </li>
<li><i>Supplemental Telephony</i> provides advanced telephone services such as hold, park,
conference, and so on, to single and multiline phones. </li>
<li><i>Extended Telephony</i> provides a direct interface between Windows programs and
vendor-specific TAPI services. </li>
</ul>
<p>You also learned that the TAPI function set defines two different devices to handle
telephony services:
<ul>
<li><i>Line devices</i> are used to control the connection between a data source and the
physical telephone line. </li>
<li><i>Phone devices</i> are used to control the connection between a desktop handset and a
line device. </li>
</ul>
<p>Finally, you reviewed the API calls, data structures, and Windows messages defined for
each level of TAPI service. </p>
<h2><a NAME="Chapter24TAPIBasics"></a><b><a HREF="ch24.htm">Chapter 24</a><font SIZE="5"
COLOR="#FF0000">, "TAPI Basics"</font></b></h2>
<p>In this chapter you learned how to build a simple TAPI dialer application in C using
the Basic Telephony level of service. This application was used to highlight the basic
operations required to build TAPI applications (in any language). </p>
<p>You learned how to perform line initialization, locate a usable outbound line, and open
the line in preparation for dialing. You also learned how to place an outbound call and
use the TAPI line callback function to monitor call progress. Finally, you learned how to
close safely down a line after the call has been completed. </p>
<p>You learned the following key steps to placing outbound calls using Basic TAPI
services:
<ul>
<li><font COLOR="#000000">Call </font><tt><font FACE="Courier">lineInitialize</font></tt> to
start the TAPI session. </li>
<li><font COLOR="#000000">Call </font><tt><font FACE="Courier">lineNegotiateAPIVersion</font></tt>
to make sure you can use the installed TAPI services. </li>
<li><font COLOR="#000000">Call </font><tt><font FACE="Courier">lineOpen</font></tt> to get a
line that is appropriate for your needs (data, fax, voice, and so on). </li>
<li><font COLOR="#000000">Use the </font><tt><font FACE="Courier">LINECALLPARAMS</font></tt>
structure to set up calling parameters before you place your call. </li>
<li><font COLOR="#000000">Call </font><tt><font FACE="Courier">lineMakeCall</font></tt> to
actually attempt to place a TAPI call. </li>
</ul>
<p>You also learned how to write a callback function to handle messages sent while the
TAPI services are in action. </p>
<h2><a NAME="Chapter25TAPIHardwareConsideration"></a><b><a HREF="ch25.htm">Chapter 25</a><font
SIZE="5" COLOR="#FF0000">, "TAPI Hardware Considerations"</font></b></h2>
<p><a HREF="ch25.htm">Chapter 25</a> showed you the differences between the three types of
hardware options and how they rate in offering support for TAPI services on pc
workstations.
<ul>
<li><i>Basic data modems</i> support Assisted Telephony services (outbound dialing) and can
support only limited inbound call handling. Use this type of hardware if you are building
simple outbound dialing applications. </li>
<li><i>Voice-data modems</i> are capable of supporting the Assisted Telephony and Basic
Telephony services, and many of the Supplemental services. Use this type of hardware if
you want to provide both inbound and outbound services on a single-line phone. </li>
<li><i>Telephony cards</i> support all of the Basic Telephony and all of the Supplemental
Telephony services, including phone device control. Most telephony cards also offer
multiple lines on a single card. This makes them ideal for supporting commercial-grade
telephony applications. </li>
</ul>
<p>You also got a quick review of modems and modem drivers. You learned that Win95 and
WinNT rely on the UniModem or UniModemV modem drivers to communicate between the telephony
hardware and your program. You also learned that, no matter what hardware you purchase,
you will need a TAPI-compliant <i>TSPI</i> (<i>Telephony Service Provider Interface</i>)
that matches the hardware you purchased. Hardware vendors can recognize the UniModem or
UniModemV drivers, or ship their own TSPI drivers with their hardware. </p>
<h2><a NAME="Chapter26TAPIToolsUsingtheTAPILI"></a><b><a HREF="ch26.htm">Chapter 26</a><font
SIZE="5" COLOR="#FF0000">, "TAPI Tools-Using the </font><tt><font SIZE="5"
COLOR="#FF0000" FACE="Courier">TAPILINE</font></tt><font SIZE="5" COLOR="#FF0000">
Control"</font></b></h2>
<p>In this chapter you learned the properties, methods, and events of the <tt><font
FACE="Courier">TAPILINE</font></tt> control that ships on the CD-ROM that accompanies this
book. You also learned how to use this control to gain access to TAPI services from within
Visual Basic programs. </p>
<p>You learned how to perform the following TAPI service requests:
<ul>
<li><font COLOR="#000000">Initialize a TAPI session.</font> </li>
<li><font COLOR="#000000">Confirm the TAPI version you are using.</font> </li>
<li><font COLOR="#000000">Get a list of device capabilities.</font> </li>
<li><font COLOR="#000000">Open a line for outbound calling.</font> </li>
<li><font COLOR="#000000">Place an outbound call.</font> </li>
<li><font COLOR="#000000">Drop an active call.</font> </li>
<li><font COLOR="#000000">De-allocate the idle call.</font> </li>
<li><font COLOR="#000000">Close an open line device.</font> </li>
</ul>
<p>You also learned how to monitor call progress using TAPI messages and the <tt><font
FACE="Courier">lineGetCallInfo</font></tt> and <tt><font FACE="Courier">lineGetAddress</font></tt>
methods. Finally, you learned how to call the four TAPI dialog boxes to gain access to
configuration dialogs to customize your TAPI interface. </p>
<h2><a NAME="Chapter27TAPIBehindtheScenesThe"></a><b><a HREF="ch27.htm">Chapter 27</a><font
SIZE="5" COLOR="#FF0000">, "TAPI Behind the ScenesThe</font><tt><font SIZE="5"
COLOR="#FF0000" FACE="Courier">TELEPHON.INI</font></tt><font SIZE="5" COLOR="#FF0000">
File"</font></b></h2>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -