Telephony API Server Test (Compact 7)
3/12/2014
The Telephony API (TAPI) Server Test verifies that a peripheral device supports TAPI functionality, particularly the ability to complete inbound calls. The test initializes TAPI and monitors one or more lines for incoming calls. If a call is offered, the test connects the call using the lineAnswer function and then drops the call.
Test Prerequisites
Your device must meet the following requirements before you run this test.
The following table shows the hardware requirements for the TAPI Server Test.
| Requirement | Description |
|---|---|
Two TAPI devices |
One TAPI device must be installed on the server to receive calls. The second TAPI device makes calls. You can use an external modem, null modem, or IR modem as a TAPI device. |
The following table shows the software requirements for the TAPI Server Test.
Requirements Description
| Tux.exe | Test harness, required for executing the test |
|---|---|
Kato.dll |
Logging engine, required for logging test data |
Tapiserver.dll |
Library containing test cases |
TAPI client application |
A TAPI client application that makes calls |
Important:
The TAPI Client and TAPI Server tests both require a client and server to be run, as noted in the Hardware Requirements section. Additionally, these tests are best run together so the TAPI Client test is exercising the TAPI Server test.
Subtests
The table below lists the subtests included in this test.
| SubTest ID | Description |
|---|---|
100 |
Run the Default Test Opens the device specified by the command line and listens for incoming calls. When a call is detected, the test answers the call and then drops the call. This test fails if the TAPI client application, TAPI, or service provider are incompatible with one another. |
Setting Up the Test
The Telephony API (TAPI) Server Test requires one or two Windows Embedded Compact-based devices with TAPI functionality, depending on the testing desired, and a remote access server (RAS). Setup is straightforward, and entails configuring a modem (i.e. Serial) on the device and then configuring a modem on the RAS machine enabled with a user account.
Boot the Windows Embedded Compact-based device and attach and configure the modem. Run case 100 in the TAPIclient Tux suite to get the device identifier of the attached modem you wish to use. For example: s tux -o -d tapiclient -x 100.
Then run the TAPIclient suite with the "-d device_identifier" switch, using the device ID found previously.
Running the Test
The TAPI Server Test executes the tux -o -d tapiserver -c "-d0 -x3" command line on default execution. You can modify the test by editing the command line. The following table shows the command line parameters for the Telephony API Server Test.
| Command line parameter | Description |
|---|---|
-d identifier |
Specifies the device identifier of the line that you want to test. You can obtain a list of device identifiers by following the steps in the Setting Up the Test section. The default value for the device identifier is 0, which corresponds to the external modem in most Windows Embedded Compact run-time images. |
-x minutes |
Quits the test after a specified number of minutes. If you do not specify this option, the test does not stop. |
-t seconds |
Drops a call after a specified number of seconds. If you do not specify this option, the test waits until the caller drops |
-m mode |
Sets the media mode. The default value is 0. You can specify one of the following media modes: 0: Data modem, 1: Interactive voice, 2: Automated voice, 3: Group 3 FAX, 4: Group 4 FAX, 5: Digital data, 6: TDD, 7: Teletex, 8: Videotex, 9: Telex, 10: ISDN mixed, 11: ADSI, 12: VoiceView, 13: Unclassified. |
-h |
Displays information about the test |
Verifying the Test
When the test completes running, verify that "PASS" appears in the test log for all sub-tests.
Troubleshooting the Test
* Get the TAPI device names by following the steps in Setting Up the Test section.
* Ensure the modems on both devices are configured correctly.
* The TAPI client application must be TAPI-compliant.
For additional platform specific issues, consult the CTK articles on the TechNet wiki.