1echoscu(1) OFFIS DCMTK echoscu(1)
2
6 echoscu - DICOM verification (C-ECHO) SCU
7
10 echoscu [options] peer port
11
13 The echoscu application implements a Service Class User (SCU) for the
14 Verification SOP Class. It sends a DICOM C-ECHO message to a Service
15 Class Provider (SCP) and waits for a response. The application can be
16 used to verify basic DICOM connectivity.
17
19 peer hostname of DICOM peer
20 port tcp/ip port number of peer
22
24 general options
25 -h --help
26 print this help text and exit
27 --version
29 print version information and exit
30 --arguments
32 print expanded command line arguments
33 -q --quiet
35 quiet mode, print no warnings and errors
36 -v --verbose
38 verbose mode, print processing details
39 -d --debug
41 debug mode, print debug information
42 -ll --log-level [l]evel: string constant
44 (fatal, error, warn, info, debug, trace)
45 use level l for the logger
46 -lc --log-config [f]ilename: string
48 use config file f for the logger
49 network options
51 application entity titles:
52 -aet --aetitle [a]etitle: string
54 set my calling AE title (default: ECHOSCU)
55 -aec --call [a]etitle: string
57 set called AE title of peer (default: ANY-SCP)
58 association negotiation debugging:
60 -pts --propose-ts [n]umber: integer (1..38)
62 propose n transfer syntaxes
63 -ppc --propose-pc [n]umber: integer (1..128)
65 propose n presentation contexts
66 other network options:
68 -to --timeout [s]econds: integer (default: unlimited)
70 timeout for connection requests
71 -ta --acse-timeout [s]econds: integer (default: 30)
73 timeout for ACSE messages
74 -td --dimse-timeout [s]econds: integer (default: unlimited)
76 timeout for DIMSE messages
77 -pdu --max-pdu [n]umber of bytes: integer (4096..131072)
79 set max receive pdu to n bytes (default: 16384)
80 --repeat [n]umber: integer
82 repeat n times
83 --abort
85 abort association instead of releasing it
86 transport layer security (TLS) options
88 transport protocol stack:
89 -tls --disable-tls
91 use normal TCP/IP connection (default)
92 +tls --enable-tls [p]rivate key file, [c]ertificate file: string
94 use authenticated secure TLS connection
95 +tla --anonymous-tls
97 use secure TLS connection without certificate
98 private key password (only with --enable-tls):
100 +ps --std-passwd
102 prompt user to type password on stdin (default)
103 +pw --use-passwd [p]assword: string
105 use specified password
106 -pw --null-passwd
108 use empty string as password
109 key and certificate file format:
111 -pem --pem-keys
113 read keys and certificates as PEM file (default)
114 -der --der-keys
116 read keys and certificates as DER file
117 certification authority:
119 +cf --add-cert-file [c]ertificate filename: string
121 add certificate file to list of certificates
122 +cd --add-cert-dir [c]ertificate directory: string
124 add certificates in d to list of certificates
125 ciphersuite:
127 +cs --cipher [c]iphersuite name: string
129 add ciphersuite to list of negotiated suites
130 +dp --dhparam [f]ilename: string
132 read DH parameters for DH/DSS ciphersuites
133 pseudo random generator:
135 +rs --seed [f]ilename: string
137 seed random generator with contents of f
138 +ws --write-seed
140 write back modified seed (only with --seed)
141 +wf --write-seed-file [f]ilename: string (only with --seed)
143 write modified seed to file f
144 peer authentication:
146 -rc --require-peer-cert
148 verify peer certificate, fail if absent (default)
149 -vc --verify-peer-cert
151 verify peer certificate if present
152 -ic --ignore-peer-cert
154 don't verify peer certificate
155
157 DICOM Conformance
158 The echoscu application supports the following SOP Classes as an SCU:
159 VerificationSOPClass 1.2.840.10008.1.1
161 Unless the --propose-ts option is used, the echoscu application will
163 only propose the transfer syntax
164 LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
166
168 The level of logging output of the various command line tools and
169 underlying libraries can be specified by the user. By default, only
170 errors and warnings are written to the standard error stream. Using
171 option --verbose also informational messages like processing details
172 are reported. Option --debug can be used to get more details on the
173 internal activity, e.g. for debugging purposes. Other logging levels
174 can be selected using option --log-level. In --quiet mode only fatal
175 errors are reported. In such very severe error events, the application
176 will usually terminate. For more details on the different logging
177 levels, see documentation of module 'oflog'.
178 In case the logging output should be written to file (optionally with
180 logfile rotation), to syslog (Unix) or the event log (Windows) option
181 --log-config can be used. This configuration file also allows for
182 directing only certain messages to a particular output stream and for
183 filtering certain messages based on the module or application where
184 they are generated. An example configuration file is provided in
185 <etcdir>/logger.cfg.
186
188 All command line tools use the following notation for parameters:
189 square brackets enclose optional values (0-1), three trailing dots
190 indicate that multiple values are allowed (1-n), a combination of both
191 means 0 to n values.
192 Command line options are distinguished from parameters by a leading '+'
194 or '-' sign, respectively. Usually, order and position of command line
195 options are arbitrary (i.e. they can appear anywhere). However, if
196 options are mutually exclusive the rightmost appearance is used. This
197 behavior conforms to the standard evaluation rules of common Unix
198 shells.
199 In addition, one or more command files can be specified using an '@'
201 sign as a prefix to the filename (e.g. @command.txt). Such a command
202 argument is replaced by the content of the corresponding text file
203 (multiple whitespaces are treated as a single separator unless they
204 appear between two quotation marks) prior to any further evaluation.
205 Please note that a command file cannot contain another command file.
206 This simple but effective approach allows one to summarize common
207 combinations of options/parameters and avoids longish and confusing
208 command lines (an example is provided in file <datadir>/dumppat.txt).
209
211 The echoscu utility will attempt to load DICOM data dictionaries
212 specified in the DCMDICTPATH environment variable. By default, i.e. if
213 the DCMDICTPATH environment variable is not set, the file
214 <datadir>/dicom.dic will be loaded unless the dictionary is built into
215 the application (default for Windows).
216 The default behavior should be preferred and the DCMDICTPATH
218 environment variable only used when alternative data dictionaries are
219 required. The DCMDICTPATH environment variable has the same format as
220 the Unix shell PATH variable in that a colon (':') separates entries.
221 On Windows systems, a semicolon (';') is used as a separator. The data
222 dictionary code will attempt to load each file specified in the
223 DCMDICTPATH environment variable. It is an error if no data dictionary
224 can be loaded.
225
227 Copyright (C) 1994-2017 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
228 Germany.
229Version 3.6.2 Fri Jul 14 2017 echoscu(1)