1echoscu(1)                        OFFIS DCMTK                       echoscu(1)
2
3
4

NAME

6       echoscu - DICOM verification (C-ECHO) SCU
7

SYNOPSIS

9       echoscu [options] peer port
10

DESCRIPTION

12       The  echoscu  application implements a Service Class User (SCU) for the
13       Verification SOP Class. It sends a DICOM C-ECHO message  to  a  Service
14       Class  Provider  (SCP) and waits for a response. The application can be
15       used to verify basic DICOM connectivity.
16

PARAMETERS

18       peer  hostname of DICOM peer
19
20       port  tcp/ip port number of peer
21

OPTIONS

23   general options
24         -h    --help
25                 print this help text and exit
26
27               --version
28                 print version information and exit
29
30               --arguments
31                 print expanded command line arguments
32
33         -q    --quiet
34                 quiet mode, print no warnings and errors
35
36         -v    --verbose
37                 verbose mode, print processing details
38
39         -d    --debug
40                 debug mode, print debug information
41
42         -ll   --log-level  [l]evel: string constant
43                 (fatal, error, warn, info, debug, trace)
44                 use level l for the logger
45
46         -lc   --log-config  [f]ilename: string
47                 use config file f for the logger
48
49   network options
50       application entity titles:
51
52         -aet  --aetitle  [a]etitle: string
53                 set my calling AE title (default: ECHOSCU)
54
55         -aec  --call  [a]etitle: string
56                 set called AE title of peer (default: ANY-SCP)
57
58       association negotiation debugging:
59
60         -pts  --propose-ts  [n]umber: integer (1..28)
61                 propose n transfer syntaxes
62
63         -ppc  --propose-pc  [n]umber: integer (1..128)
64                 propose n presentation contexts
65
66       other network options:
67
68         -to   --timeout  [s]econds: integer (default: unlimited)
69                 timeout for connection requests
70
71         -ta   --acse-timeout  [s]econds: integer (default: 30)
72                 timeout for ACSE messages
73
74         -td   --dimse-timeout  [s]econds: integer (default: unlimited)
75                 timeout for DIMSE messages
76
77         -pdu  --max-pdu  [n]umber of bytes: integer (4096..131072)
78                 set max receive pdu to n bytes (default: 16384)
79
80               --repeat  [n]umber: integer
81                 repeat n times
82
83               --abort
84                 abort association instead of releasing it
85
86   transport layer security (TLS) options
87       transport protocol stack:
88
89         -tls  --disable-tls
90                 use normal TCP/IP connection (default)
91
92         +tls  --enable-tls  [p]rivate key file, [c]ertificate file: string
93                 use authenticated secure TLS connection
94
95         +tla  --anonymous-tls
96                 use secure TLS connection without certificate
97
98       private key password (only with --enable-tls):
99
100         +ps   --std-passwd
101                 prompt user to type password on stdin (default)
102
103         +pw   --use-passwd  [p]assword: string
104                 use specified password
105
106         -pw   --null-passwd
107                 use empty string as password
108
109       key and certificate file format:
110
111         -pem  --pem-keys
112                 read keys and certificates as PEM file (default)
113
114         -der  --der-keys
115                 read keys and certificates as DER file
116
117       certification authority:
118         +cf   --add-cert-file  [c]ertificate filename: string
119                 add certificate file to list of certificates
120
121         +cd   --add-cert-dir  [c]ertificate directory: string
122                 add certificates in d to list of certificates
123
124       ciphersuite:
125
126         +cs   --cipher  [c]iphersuite name: string
127                 add ciphersuite to list of negotiated suites
128
129         +dp   --dhparam  [f]ilename: string
130                 read DH parameters for DH/DSS ciphersuites
131
132       pseudo random generator:
133
134         +rs   --seed  [f]ilename: string
135                 seed random generator with contents of f
136
137         +ws   --write-seed
138                 write back modified seed (only with --seed)
139
140         +wf   --write-seed-file  [f]ilename: string (only with --seed)
141                 write modified seed to file f
142
143       peer authentication:
144
145         -rc   --require-peer-cert
146                 verify peer certificate, fail if absent (default)
147
148         -vc   --verify-peer-cert
149                 verify peer certificate if present
150
151         -ic   --ignore-peer-cert
152                 don't verify peer certificate
153

NOTES

155   DICOM Conformance
156       The echoscu application supports the following SOP Classes as an SCU:
157
158       VerificationSOPClass                1.2.840.10008.1.1
159
160       Unless the --propose-ts option is used, the  echoscu  application  will
161       only propose the transfer syntax
162
163       LittleEndianImplicitTransferSyntax  1.2.840.10008.1.2
164

LOGGING

166       The  level  of  logging  output  of  the various command line tools and
167       underlying libraries can be specified by the  user.  By  default,  only
168       errors  and  warnings  are  written to the standard error stream. Using
169       option --verbose also informational messages  like  processing  details
170       are  reported.  Option  --debug  can be used to get more details on the
171       internal activity, e.g. for debugging purposes.  Other  logging  levels
172       can  be  selected  using option --log-level. In --quiet mode only fatal
173       errors are reported. In such very severe error events, the  application
174       will  usually  terminate.  For  more  details  on the different logging
175       levels, see documentation of module 'oflog'.
176
177       In case the logging output should be written to file  (optionally  with
178       logfile  rotation),  to syslog (Unix) or the event log (Windows) option
179       --log-config can be used.  This  configuration  file  also  allows  for
180       directing  only  certain messages to a particular output stream and for
181       filtering certain messages based on the  module  or  application  where
182       they  are  generated.  An  example  configuration  file  is provided in
183       <etcdir>/logger.cfg).
184

COMMAND LINE

186       All command line tools  use  the  following  notation  for  parameters:
187       square  brackets  enclose  optional  values  (0-1), three trailing dots
188       indicate that multiple values are allowed (1-n), a combination of  both
189       means 0 to n values.
190
191       Command line options are distinguished from parameters by a leading '+'
192       or '-' sign, respectively. Usually, order and position of command  line
193       options  are  arbitrary  (i.e.  they  can appear anywhere). However, if
194       options are mutually exclusive the rightmost appearance is  used.  This
195       behaviour  conforms  to  the  standard  evaluation rules of common Unix
196       shells.
197
198       In addition, one or more command files can be specified  using  an  '@'
199       sign  as  a  prefix to the filename (e.g. @command.txt). Such a command
200       argument is replaced by the content  of  the  corresponding  text  file
201       (multiple  whitespaces  are  treated  as a single separator unless they
202       appear between two quotation marks) prior to  any  further  evaluation.
203       Please  note  that  a command file cannot contain another command file.
204       This  simple  but  effective  approach  allows  to   summarize   common
205       combinations  of  options/parameters  and  avoids longish and confusing
206       command lines (an example is provided in file <datadir>/dumppat.txt).
207

ENVIRONMENT

209       The echoscu utility  will  attempt  to  load  DICOM  data  dictionaries
210       specified  in the DCMDICTPATH environment variable. By default, i.e. if
211       the  DCMDICTPATH  environment   variable   is   not   set,   the   file
212       <datadir>/dicom.dic  will be loaded unless the dictionary is built into
213       the application (default for Windows).
214
215       The  default  behaviour  should  be  preferred  and   the   DCMDICTPATH
216       environment  variable  only used when alternative data dictionaries are
217       required. The DCMDICTPATH environment variable has the same  format  as
218       the  Unix  shell PATH variable in that a colon (':') separates entries.
219       On Windows systems, a semicolon (';') is used as a separator. The  data
220       dictionary  code  will  attempt  to  load  each  file  specified in the
221       DCMDICTPATH environment variable. It is an error if no data  dictionary
222       can be loaded.
223
225       Copyright  (C)  1994-2010  by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
226       Germany.
227
228
229
230Version 3.6.0                     6 Jan 2011                        echoscu(1)
Impressum