Telephony API Client Test
The Telephony API (TAPI) Client Test verifies that a peripheral device supports basic TAPI functionality, particularly the ability to complete an outbound call. This test repeatedly sets up and dials a call on a TAPI-enabled device. The test does not attempt to communicate over the connection after establishing the connection. You can use this test as a build verification test (BVT). You can also use the test as a breadth test by varying command-line settings or as a stress test by setting the test to dial multiple times.
The following table shows the hardware requirements for the TAPI Client Test.
| Requirements | Description |
|---|---|
| A TAPI device | A TAPI device such as an external modem, PCMCIA modem, null modem, or infrared (IR) modem. |
| A remote access server (RAS) | Server that the test attempts to call. You can also use the TAPI Server Test as a server. For more information about the TAPI Server Test, see Telephony API Server Test. |
The following table shows the software requirements for the TAPI Client Test.
| Requirements | Description |
|---|---|
| Tux.exe | Tux test harness, which is required for executing the test. |
| Kato.dll | Kato logging engine, which is required for logging test data. |
| Tooltalk.dll | Application required by Tux.exe and Kato.dll. Handles the transport between the target device and the development workstation. |
| Tapiclient.dll | Test .dll file |
| Common library files | Common library files located in the Netlib directory. |
Note When you run the TAPI Client Test, the CETK temporarily copies files to the root directory of the target device. Before running the test, verify that there is at least 0.4 megabytes (MB) of free space in the root directory of the target device. If there is not sufficient space in the root directory of the target device, the test cannot run.
See Also
Modifying the Telephony API Client Test
Last updated on Friday, October 08, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.