Modifying the Telephony API Server Test (Windows CE 5.0)
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. 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 Server Test
To | Add this command-line parameter |
---|---|
Specify the device identifier of the line that you want to test. 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 in most Microsoft® Windows® CE run-time images. |
|
Quit the test after a specified number of minutes.
If you do not specify this option, the test does not stop. |
|
Drop a call after a specified number of seconds.
If you do not specify this option, the test waits until the caller drops. |
|
Set the media mode.
The default value is 0. You can specify one of the following media modes:
|
|
Display information about the test. |
|
The following table shows the test cases for the TAPI Server Test.
Test case | 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. |
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