Mercurial > hg > orthanc-book

comparison Sphinx/source/faq/dicom.rst @ 0:901e8961f46e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
initial commit
author Sebastien Jodogne <s.jodogne@gmail.com>
date Fri, 22 Apr 2016 12:57:38 +0200
parents
children f99aa6a6f0c9
comparison
equal deleted inserted replaced
-1:000000000000 0:901e8961f46e
1 .. _dicom:
2
3 Troubleshooting DICOM communications
4 ====================================
5
6 In general, communication problems between two DICOM modalities over a
7 computer network are related to the configuration of these
8 modalities. As preliminary debugging actions, you should:
9
10 * Make sure you use the `most recent version <http://www.orthanc-server.com/download.php>`_ of Orthanc.
11 * Make sure the two computers can "ping" each other.
12 * Turn off all the firewalls on the two computers (especially on Microsoft Windows).
13 * Write down on a paper the following information about each modality:
14
15 * its IP address (avoid using symbolic names if possible to troubleshot any DNS problem),
16 * its TCP port for DICOM communications (for Orthanc, cf. the ``DicomPort`` option), and
17 * its AET (Application Entity Title - for Orthanc, cf. the ``DicomAet`` option).
18
19 * Carefully re-read all your configuration files. As far as Orthanc is
20 concerned, the most important section is ``DicomModalities``: Make
21 sure its content matches what you wrote on the paper at the step
22 above.
23 * In the ``DicomModalities`` configuration section of Orthanc, have a
24 look at the fourth parameter that can activate some patches for
25 specific vendors.
26 * Have a look at the following options of Orthanc to enable the more fault-tolerant DICOM support:
27
28 * ``DicomServerEnabled`` must be set to ``true``.
29 * ``DicomCheckCalledAet`` should be set to ``false``.
30 * All the transfer syntaxes should be set to ``true`` (see the
31 options with a ``TransferSyntaxAccepted`` suffix).
32 * Temporarily disable any Lua script and any plugin, i.e. set the
33 options ``LuaScripts`` and ``Plugins`` both to the empty list.
34 * ``DicomAssociationCloseDelay`` should be set to ``0``.
35
36 * Restart Orthanc with the ``--verbose`` option at command line, and
37 carefully inspect the log. This might provide immediate debugging
38 information.
39 * Issue a :ref:`DICOM C-Echo <dicom-echo>` from each modality to make
40 sure the DICOM protocol is properly configured (sending a C-Echo
41 from Orthanc Explorer is possible starting with Orthanc 0.9.3, in
42 the "Query/Retrieve" page).
43 * If the two modalities succeed with C-Echo, but query/retrieve does not
44 succeed, please carefully read the :ref:`dicom-move` section.
45
46 As a last resort, please contact the `mailing list
47 <https://groups.google.com/forum/#!forum/orthanc-users>`_ by sending a
48 detailed description of your problem, notably:
49
50 * What fails: The sending of a file (aka. C-Store SCU), the searching
51 of a patient/study (aka. C-Find SCU), or the retrieve of a file
52 (aka. C-Move SCU)? Is Orthanc acting as a client or as a server?
53 * Describe your network topology, as written above on your paper (IP
54 address, port number, and AET for both modalities).
55 * Specify the operating system, the vendor, the DICOM software, and
56 the version of each modality.
57 * Attach sample DICOM files, possibly anonymized.
58 * Attach the log of the two modalities. The log must be generated with
59 the ``--trace`` command-line option as far as Orthanc is concerned.
60 * Attach any screenshot that is useful to understand the problem.