The test client can be started with the following commands:
Command |
Description |
tty_test <tty_nr> <CPN> <protocol> [-l<frame_length> -s<rate>] [- a<at_command>] [-y] [-m<packets>] |
This command starts a test client on your console. |
tty_test <tty_nr> <CPN> <protocol> [-l<frame_length> -s<rate>] [- a<at_command>] [-mpackets] -x& |
This command starts a test client in the background. In this mode, the test client detaches from your console and does not display any output. It generates a file named |
Note: The tty_test updates the log files after 64 KBytes of data have been transferred. Therefore, please be patient if you use, e.g., the V.110 protocol with 9600 bps.
To get information about the test client started in the background, type: ps ax | grep tty_test.
To safely stop the test client running in the background, use the "HUP" signal (kill -HUP process_number or killall -HUP tty_test). The tty_test utility understands the commands HUP, TERM, ABRT and INT. These commands terminate the tty_test utility.
Parameters for the tty_test in client mode
Parameter |
Level |
Description |
|
tty_nr |
Mandatory |
Dialogic® Diva® TTY number that should be used by this test server. It should range between 1 and N, where N is the sum of B-channels of the Dialogic® Diva® Media Board installed in the system. |
|
CPN |
Mandatory |
Called Party Number (any number can be used in back-to-back mode) |
|
protocol |
Mandatory |
Value |
Description |
|
|
hdlc |
HDLC/Transparent/Transparent. This protocol stack is widely used by RAS. |
|
|
x75 |
HDLC/X.75/Transparent. This protocol stack provides reliable data transfer. V.42bis compression is detected automatically. |
|
|
x75v42 |
HDLC/X.75 with V.42bis data compression/Transparent. This protocol is not used on the server side because x75 automatically detects X.75 with V.42bis. |
|
|
v120 |
HDLC/V.120/Transparent V.120 with V.42bis is possible. |
|
|
v110 |
V.110/Transparent/Transparent |
|
|
mdm |
Modem with full negotiation/V.42+V.42bis/Transparent. |
-l<frame_length> |
Optional |
Length of the test frame. It is normally not used by the test server but it should be provided if the -s option follows |
|
-s<rate> |
Optional |
Speed adaptation rate. This parameter should be indicated if the v110 B-channel protocol is used without auto detection. It should range between 2 and 9 (5-9600, 9-56000). If this option is selected, the "-l" option should also be used. |
|
-a<at_command> |
Optional |
Allows to provide additional AT-command strings used for client initialization. |
|
-y |
Optional |
Does not display any messages except call progress and data transfer status. |
|
-m<packets> |
Optional |
Exits after "packets" data packets were sent. Displays the transfer status on the screen (standard out) and prints it to the |
|
Example 2. Start tty_test server with protocol auto-detection
To start the test server at TTY number 10 and use protocol auto-detection execute: tty_test 10 s auto.
Example 3. Start the test server using the V.110 protocol
To start the test server at TTY number 21 using the V.110 protocol with 9600 bps in the background execute: tty_test 21 sv v110 -l2048 -s5&
Example 4. Start the test client using the X.75 protocol and specify the frame length
To start the test client at TTY 1 using the X.75 protocol, the called party number 800, and a test frame length of 514 bytes, execute: tty_test 1 800 x75 -l514.
Example 5. Start the test client using the V.110 protocol
To start the test client at TTY 1 running in the background using the V.110 protocol, called party number 800, a test frame length of 128 bytes, a rate adaptation speed of 9600 bps, and rate adaptation indication in the , execute: tty_test 1 800 v110 -l128 -s5 -a+iu="<8890214800bb>" -x&
Example 6. Start 30 test server and 30 test client sessions
Start 30 test server and 30 test client sessions using this sample shell script. It uses B-channel protocol auto-detection on the server side and V.110 with 9600 bps on the client side.
|