Mercurial > hg > orthanc-book
diff Sphinx/source/dicom-guide.rst @ 42:a52f1dc48ebc
GNU/Linux
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Fri, 16 Sep 2016 09:14:59 +0200 |
parents | dc235678897c |
children | 83c0a6556e6c |
line wrap: on
line diff
--- a/Sphinx/source/dicom-guide.rst Fri Sep 16 08:57:28 2016 +0200 +++ b/Sphinx/source/dicom-guide.rst Fri Sep 16 09:14:59 2016 +0200 @@ -384,11 +384,11 @@ also block the DICOM protocol. This is especially true for the `Microsoft Windows firewall <https://en.wikipedia.org/wiki/Windows_Firewall>`__ and for -:ref:`RedHat-based Linux boxes <redhat>`. As a consequence, after any -change in the DICOM topology of an hospital (notably when connecting -two imaging devices), one should always check whether the DICOM -protocol can travel from end to end, i.e. between the DICOM client -and the DICOM server. +:ref:`RedHat-based GNU/Linux boxes <redhat>`. As a consequence, after +any change in the DICOM topology of an hospital (notably when +connecting two imaging devices), one should always check whether the +DICOM protocol can travel from end to end, i.e. between the DICOM +client and the DICOM server. This is where the **DICOM Echo service** comes into play. This service is triggered when the client sends a so-called ``C-Echo`` command to