Modifying the Telephony API Client Test (Windows CE 5.0)
The TAPI Client Test executes the tux –o –d tapiclient –c "-d0 -pT9,5551212 -nl"
command line on default execution. You can modify the test by editing the command line. For information about how to edit the command line for a test, see Editing the Command Line for a Test. The following table shows the modifications you can make to the test.
To modify the Telephony API Client Test
To | Add this command-line parameter |
---|---|
List all TAPI devices and then exit without making any calls. |
|
Set the number of calls to be made.
The default value for number of calls is 1. |
|
Set the telephone number to be dialed.
The default value is set to NULL. You can specify a phone number using any one of the following formats:
|
|
Specify the device identifier of the line to be tested. You can obtain a list of device identifiers by using the –l parameter.
The default value for the device identifier is 0, which corresponds to the external modem on most Microsoft® Windows® CE run-time images. |
|
Set the dialing timeout, in seconds. A call disconnects if it does not complete in the specified number of seconds.
The default value for dialing timeout is 30 seconds. |
|
Set the connection delay in seconds. The test waits for the specified number of seconds after a call completes prior to disconnecting the call.
The default value for connection delay is 10 seconds. |
|
Set the hang-up command timeout interval in seconds. The test waits for the specified number of seconds prior to discontinuing a hang-up attempt.
The default value is 5 seconds. |
|
Set the deallocation delay interval in seconds. The test waits for the specified number of seconds after a call is disconnected prior to deallocating the call handle.
The default value is 1 second. |
|
Display the following dialog boxes, with which you can configure the device and edit the current location:
|
|
Display information about the test. |
|
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.
The following table shows the test cases for the TAPI Client Test.
Test case | Description |
---|---|
100: List all TAPI device names | Lists all TAPI devices and exits without making any calls. This test fails if the TAPI client application, TAPI, or service provider are incompatible with one another. |
200: Voice – Data Modem | Sets the bearer mode to LINEBEARERMODE_VOICE and the media mode to LINEMEDIAMODE_DATAMODEM. This test case fails if the service provider does not support 3.1-kHz analog voice as the bearer mode and data modem as the media mode. |
201: Data – Data Modem | Sets the bearer mode to LINEBEARERMODE_DATA and the media mode to LINEMEDIAMODE_DATAMODEM. This test case fails if the service provider does not support data transfer as the bearer mode and data modem as the media mode. |
Remarks
This test library can have one or more optional command-line entries to change the behavior of the test. To specify one or more optional command-line entries to the test library, you must use the –c
command-line option. This option forces Tux to pass the specified string into the test library.
See Also
Send Feedback on this topic to the authors