comparison Sphinx/source/faq/dicom.rst @ 541:d70347eecb91

cont
author Sebastien Jodogne <s.jodogne@gmail.com>
date Thu, 05 Nov 2020 15:17:15 +0100
parents 50bdd7c7e9b9
children 4f3a6145ae34
comparison
equal deleted inserted replaced
538:d18496f166b8 541:d70347eecb91
5 5
6 In general, communication problems between two DICOM modalities over a 6 In general, communication problems between two DICOM modalities over a
7 computer network are related to the configuration of these 7 computer network are related to the configuration of these
8 modalities. As preliminary debugging actions, you should: 8 modalities. As preliminary debugging actions, you should:
9 9
10 * Make sure you use the `most recent version <https://www.orthanc-server.com/download.php>`_ of Orthanc. 10 * Make sure you use the `most recent version
11 <https://www.orthanc-server.com/download.php>`_ of Orthanc.
11 * Make sure the two computers can "ping" each other. 12 * Make sure the two computers can "ping" each other.
12 * Turn off all the firewalls on the two computers (especially on Microsoft Windows). 13 * Turn off all the firewalls on the two computers (especially on Microsoft Windows).
13 * Make sure the remote computer has `DICOM TLS encryption 14 * Make sure the remote computer has `DICOM TLS encryption
14 <https://www.dicomstandard.org/using/security/>`__ turned off (this 15 <https://www.dicomstandard.org/using/security/>`__ turned off (this
15 feature is not supported yet as of Orthanc 1.8.0). 16 feature is not supported yet as of Orthanc 1.8.0).
34 options with a ``TransferSyntaxAccepted`` suffix). 35 options with a ``TransferSyntaxAccepted`` suffix).
35 * Temporarily disable any Lua script and any plugin, i.e. set the 36 * Temporarily disable any Lua script and any plugin, i.e. set the
36 options ``LuaScripts`` and ``Plugins`` both to the empty list. 37 options ``LuaScripts`` and ``Plugins`` both to the empty list.
37 * ``DicomAssociationCloseDelay`` should be set to ``0``. 38 * ``DicomAssociationCloseDelay`` should be set to ``0``.
38 39
39 * Restart Orthanc with the ``--verbose`` option at command line, and 40 * Restart Orthanc with the ``--verbose --trace-dicom`` options at
40 carefully inspect the log. This might provide immediate debugging 41 command line, and carefully inspect the log (the ``trace-dicom``
42 option is new in Orthanc 1.8.1 and provides low-level information
43 from DCMTK). This might provide immediate debugging
41 information. Make sure to read :ref:`how to generate an exploitable 44 information. Make sure to read :ref:`how to generate an exploitable
42 log <log>`. 45 log <log>`.
43 * Issue a :ref:`DICOM C-Echo <dicom-echo>` from each modality to make 46 * Issue a :ref:`DICOM C-Echo <dicom-echo>` from each modality to make
44 sure the DICOM protocol is properly configured (sending a C-Echo 47 sure the DICOM protocol is properly configured (sending a C-Echo
45 from Orthanc Explorer is possible starting with Orthanc 0.9.3, in 48 from Orthanc Explorer is possible starting with Orthanc 0.9.3, in