Telephony API Client Test (Windows Embedded CE 6.0)
1/6/2010
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.
To complete a null modem connection, you must set the bearer mode to 3 and set the baud parameters in the Device Properties dialog box.
If you maximize logging verbosity, the test logs data from the LINEDEVCAPS structure for the device being tested. Verbose logging provides important information such as the name of the device and the bearer as well as the supported media modes.
You can enter Hayes AT modem commands using the Extra Settings box in the Device Properties dialog box. Type commands without the leading "AT" string. For example, to turn off the modem speaker (Hayes command "ATM0"), type M0.
In This Section
- Prerequisites for the Telephony API Client Test
Provides a list of hardware and software for the test.
- Hardware Setup for the Telephony API Client Test
Provides hardware setup instructions for this test
- Test Cases for the Telephony API Client Test
Provides a list of test cases within the overall test, and a description for each test case.
- Command Line Parameters for the Telephony API Client Test
Specifies the command line parameters for this test.
- Troubleshooting the Telephony API Client Test
Provides troubleshooting information for this test