annotate Sphinx/source/faq/dicom.rst @ 1113:a588960a72e5 default tip

spelling
author Alain Mazy <am@orthanc.team>
date Mon, 28 Oct 2024 09:23:08 +0100
parents 46e2941b57dd
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
0
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
1 .. _dicom:
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
2
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
3 Troubleshooting DICOM communications
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
4 ====================================
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
5
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
6 In general, communication problems between two DICOM modalities over a
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
7 computer network are related to the configuration of these
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
8 modalities. As preliminary debugging actions, you should:
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
9
541
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 528
diff changeset
10 * Make sure you use the `most recent version
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 528
diff changeset
11 <https://www.orthanc-server.com/download.php>`_ of Orthanc.
0
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
12 * Make sure the two computers can "ping" each other.
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
13 * Turn off all the firewalls on the two computers (especially on Microsoft Windows).
242
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 23
diff changeset
14 * Make sure the remote computer has `DICOM TLS encryption
607
eaa6cdfa7ba6 Orthanc 1.9.0
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 568
diff changeset
15 <https://www.dicomstandard.org/using/security/>`__ turned off.
0
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
16 * Write down on a paper the following information about each modality:
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
17
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
18 * its IP address (avoid using symbolic names if possible to troubleshot any DNS problem),
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
19 * its TCP port for DICOM communications (for Orthanc, cf. the ``DicomPort`` option), and
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
20 * its AET (Application Entity Title - for Orthanc, cf. the ``DicomAet`` option).
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
21
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
22 * Carefully re-read all your configuration files. As far as Orthanc is
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
23 concerned, the most important section is ``DicomModalities``: Make
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
24 sure its content matches what you wrote on the paper at the step
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
25 above.
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
26 * In the ``DicomModalities`` configuration section of Orthanc, have a
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
27 look at the fourth parameter that can activate some patches for
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
28 specific vendors.
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
29 * Have a look at the following options of Orthanc to enable the more fault-tolerant DICOM support:
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
30
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
31 * ``DicomServerEnabled`` must be set to ``true``.
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
32 * ``DicomCheckCalledAet`` should be set to ``false``.
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
33 * All the transfer syntaxes should be set to ``true`` (see the
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
34 options with a ``TransferSyntaxAccepted`` suffix).
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
35 * Temporarily disable any Lua script and any plugin, i.e. set the
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
36 options ``LuaScripts`` and ``Plugins`` both to the empty list.
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
37 * ``DicomAssociationCloseDelay`` should be set to ``0``.
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
38
541
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 528
diff changeset
39 * Restart Orthanc with the ``--verbose --trace-dicom`` options at
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 528
diff changeset
40 command line, and carefully inspect the log (the ``trace-dicom``
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 528
diff changeset
41 option is new in Orthanc 1.8.1 and provides low-level information
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 528
diff changeset
42 from DCMTK). This might provide immediate debugging
23
f99aa6a6f0c9 Generating an Exploitable Log
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 0
diff changeset
43 information. Make sure to read :ref:`how to generate an exploitable
f99aa6a6f0c9 Generating an Exploitable Log
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 0
diff changeset
44 log <log>`.
0
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
45 * Issue a :ref:`DICOM C-Echo <dicom-echo>` from each modality to make
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
46 sure the DICOM protocol is properly configured (sending a C-Echo
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
47 from Orthanc Explorer is possible starting with Orthanc 0.9.3, in
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
48 the "Query/Retrieve" page).
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
49 * If the two modalities succeed with C-Echo, but query/retrieve does not
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
50 succeed, please carefully read the :ref:`dicom-move` section.
654
e66534972166 dciodvfy
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 607
diff changeset
51 * Check out the :ref:`more generic troubleshooting guide
e66534972166 dciodvfy
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 607
diff changeset
52 <troubleshooting>`.
0
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
53
984
46e2941b57dd replace link to google users group by link to discourse
Alain Mazy <am@osimis.io>
parents: 654
diff changeset
54 As a last resort, please contact the `Orthanc Users discussion forum
46e2941b57dd replace link to google users group by link to discourse
Alain Mazy <am@osimis.io>
parents: 654
diff changeset
55 <https://discourse.orthanc-server.org>`__ by sending a
0
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
56 detailed description of your problem, notably:
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
57
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
58 * What fails: The sending of a file (aka. C-Store SCU), the searching
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
59 of a patient/study (aka. C-Find SCU), or the retrieve of a file
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
60 (aka. C-Move SCU)? Is Orthanc acting as a client or as a server?
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
61 * Describe your network topology, as written above on your paper (IP
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
62 address, port number, and AET for both modalities).
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
63 * Specify the operating system, the vendor, the DICOM software, and
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
64 the version of each modality.
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
65 * Attach sample DICOM files, possibly anonymized.
23
f99aa6a6f0c9 Generating an Exploitable Log
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 0
diff changeset
66 * Attach the log of the two modalities. The :ref:`log must be
f99aa6a6f0c9 Generating an Exploitable Log
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 0
diff changeset
67 generated <log>` with the ``--trace`` command-line option as far as
f99aa6a6f0c9 Generating an Exploitable Log
Sebastien Jodogne <s.jodogne@gmail.com>
parents: 0
diff changeset
68 Orthanc is concerned.
0
901e8961f46e initial commit
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
diff changeset
69 * Attach any screenshot that is useful to understand the problem.