Mercurial > hg > orthanc-book
comparison 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 |
comparison
equal
deleted
inserted
replaced
41:1c8aaaea72b2 | 42:a52f1dc48ebc |
---|---|
382 HTTPS and SSH protocols are enabled by default). Furthermore, the | 382 HTTPS and SSH protocols are enabled by default). Furthermore, the |
383 firewalls that are installed on the clients or on the servers might | 383 firewalls that are installed on the clients or on the servers might |
384 also block the DICOM protocol. This is especially true for the | 384 also block the DICOM protocol. This is especially true for the |
385 `Microsoft Windows firewall | 385 `Microsoft Windows firewall |
386 <https://en.wikipedia.org/wiki/Windows_Firewall>`__ and for | 386 <https://en.wikipedia.org/wiki/Windows_Firewall>`__ and for |
387 :ref:`RedHat-based Linux boxes <redhat>`. As a consequence, after any | 387 :ref:`RedHat-based GNU/Linux boxes <redhat>`. As a consequence, after |
388 change in the DICOM topology of an hospital (notably when connecting | 388 any change in the DICOM topology of an hospital (notably when |
389 two imaging devices), one should always check whether the DICOM | 389 connecting two imaging devices), one should always check whether the |
390 protocol can travel from end to end, i.e. between the DICOM client | 390 DICOM protocol can travel from end to end, i.e. between the DICOM |
391 and the DICOM server. | 391 client and the DICOM server. |
392 | 392 |
393 This is where the **DICOM Echo service** comes into play. This service | 393 This is where the **DICOM Echo service** comes into play. This service |
394 is triggered when the client sends a so-called ``C-Echo`` command to | 394 is triggered when the client sends a so-called ``C-Echo`` command to |
395 the server as its DICOM query. The server answers with an empty DICOM | 395 the server as its DICOM query. The server answers with an empty DICOM |
396 answer. In practice, to test the connectivity between two devices, you | 396 answer. In practice, to test the connectivity between two devices, you |