Mercurial > hg > orthanc-book
annotate Sphinx/source/faq/dicom.rst @ 681:9c23356b9464
typo: replaced "CheckRevision" by "CheckRevisions"
| author | Sebastien Jodogne <s.jodogne@gmail.com> |
|---|---|
| date | Mon, 10 May 2021 12:30:57 +0200 |
| parents | e66534972166 |
| children | 46e2941b57dd |
| rev | line source |
|---|---|
| 0 | 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 | |
| 541 | 10 * Make sure you use the `most recent version |
| 11 <https://www.orthanc-server.com/download.php>`_ of Orthanc. | |
| 0 | 12 * Make sure the two computers can "ping" each other. |
| 13 * Turn off all the firewalls on the two computers (especially on Microsoft Windows). | |
| 242 | 14 * Make sure the remote computer has `DICOM TLS encryption |
| 607 | 15 <https://www.dicomstandard.org/using/security/>`__ turned off. |
| 0 | 16 * Write down on a paper the following information about each modality: |
| 17 | |
| 18 * its IP address (avoid using symbolic names if possible to troubleshot any DNS problem), | |
| 19 * its TCP port for DICOM communications (for Orthanc, cf. the ``DicomPort`` option), and | |
| 20 * its AET (Application Entity Title - for Orthanc, cf. the ``DicomAet`` option). | |
| 21 | |
| 22 * Carefully re-read all your configuration files. As far as Orthanc is | |
| 23 concerned, the most important section is ``DicomModalities``: Make | |
| 24 sure its content matches what you wrote on the paper at the step | |
| 25 above. | |
| 26 * In the ``DicomModalities`` configuration section of Orthanc, have a | |
| 27 look at the fourth parameter that can activate some patches for | |
| 28 specific vendors. | |
| 29 * Have a look at the following options of Orthanc to enable the more fault-tolerant DICOM support: | |
| 30 | |
| 31 * ``DicomServerEnabled`` must be set to ``true``. | |
| 32 * ``DicomCheckCalledAet`` should be set to ``false``. | |
| 33 * All the transfer syntaxes should be set to ``true`` (see the | |
| 34 options with a ``TransferSyntaxAccepted`` suffix). | |
| 35 * Temporarily disable any Lua script and any plugin, i.e. set the | |
| 36 options ``LuaScripts`` and ``Plugins`` both to the empty list. | |
| 37 * ``DicomAssociationCloseDelay`` should be set to ``0``. | |
| 38 | |
| 541 | 39 * Restart Orthanc with the ``--verbose --trace-dicom`` options at |
| 40 command line, and carefully inspect the log (the ``trace-dicom`` | |
| 41 option is new in Orthanc 1.8.1 and provides low-level information | |
| 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 | 45 * Issue a :ref:`DICOM C-Echo <dicom-echo>` from each modality to make |
| 46 sure the DICOM protocol is properly configured (sending a C-Echo | |
| 47 from Orthanc Explorer is possible starting with Orthanc 0.9.3, in | |
| 48 the "Query/Retrieve" page). | |
| 49 * If the two modalities succeed with C-Echo, but query/retrieve does not | |
| 50 succeed, please carefully read the :ref:`dicom-move` section. | |
| 654 | 51 * Check out the :ref:`more generic troubleshooting guide |
| 52 <troubleshooting>`. | |
| 0 | 53 |
| 54 As a last resort, please contact the `mailing list | |
| 55 <https://groups.google.com/forum/#!forum/orthanc-users>`_ by sending a | |
| 56 detailed description of your problem, notably: | |
| 57 | |
| 58 * What fails: The sending of a file (aka. C-Store SCU), the searching | |
| 59 of a patient/study (aka. C-Find SCU), or the retrieve of a file | |
| 60 (aka. C-Move SCU)? Is Orthanc acting as a client or as a server? | |
| 61 * Describe your network topology, as written above on your paper (IP | |
| 62 address, port number, and AET for both modalities). | |
| 63 * Specify the operating system, the vendor, the DICOM software, and | |
| 64 the version of each modality. | |
| 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 | 69 * Attach any screenshot that is useful to understand the problem. |