Binary file Sphinx/source/images/ConfigureModality1.png has changed

Binary file Sphinx/source/images/ConfigureModality2.png has changed

--- a/Sphinx/source/integrations.rst	Thu Nov 14 10:28:31 2019 +0100
+++ b/Sphinx/source/integrations.rst	Mon Dec 16 10:09:42 2019 +0100
@@ -6,6 +6,7 @@
 .. toctree::
    :maxdepth: 1
 
+   integrations/modality.rst
    integrations/ginkgo-cadx.rst
    integrations/integrate-horos-using-dicom.rst
    integrations/integrate-osirix-using-dicom.rst

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Sphinx/source/integrations/modality.rst	Mon Dec 16 10:09:42 2019 +0100
@@ -0,0 +1,58 @@
+.. _configure-modality:
+.. highlight:: json
+
+
+Connect your modality to Orthanc
+================================
+
+This section explains how to connect a modality to an Orthanc server.
+
+First, retrieve the IP address of your Orthanc Server.  Make sure
+to retrieve the IP address of the correct network interface
+(in this case ``123.124.125.126``).
+You should also make sure that your firewall enables incoming traffic
+on the DICOM port for that network interface (``4242`` by default).
+
+Then, start Orthanc without specifying a
+configuration file (i.e. using its default configuration).  On your modality, 
+search for "settings/network settings" (exact naming is platform dependent).
+You should find this kind of information
+
+.. image:: ../images/ConfigureModality1.png
+           :align: center
+           :width: 500px
+
+
+Write down the AET, IP and DICOM port of the modality (in this case,
+respectively ``ECHO1``, ``123.124.125.10`` and ``104``). 
+
+Then, still in your modality network settings, you should find a panel
+in which you can configure a PACS or a target DICOM Server.  Enter
+the following information (adapt it with the IP address of your
+Orthanc Server):
+
+.. image:: ../images/ConfigureModality2.png
+           :align: center
+           :width: 500px
+
+
+Once you've entered this configuration in your modality, you might
+have access to a "*Test connection/C-ECHO*" button to validate that
+the modality can reach the Orthanc Server.
+
+Then, stop Orthanc, update you :ref:`configuration file
+<configuration>`, and declare your modality in the ``DicomModalities``
+section, given the parameters you wrote down above::
+
+  // The list of the known DICOM modalities
+  "DicomModalities" : {
+    "echo1" : [ "ECHO1", "123.124.125.10", 104 ]
+  },
+
+Restart Orthanc using this newly created configuration file, and
+you will be able to send data from your modality to your Orthanc Server.
+
+Further readings:
+
+* :ref:`dicom`
+* :ref:`troubleshooting`

--- a/Sphinx/source/users/cookbook.rst	Thu Nov 14 10:28:31 2019 +0100
+++ b/Sphinx/source/users/cookbook.rst	Mon Dec 16 10:09:42 2019 +0100
@@ -15,9 +15,9 @@
 
 To obtain the Orthanc binaries, you have several possibilities:
 
-* :ref:`Compile Orthanc by yourself <compiling>`.
 * `Download pre-compiled packages <http://www.orthanc-server.com/download.php>`__.
 * :ref:`Use Docker <docker>`.
+* :ref:`Compile Orthanc by yourself <compiling>`.
 * External contributors are also maintaining `Vagrant VM for Orthanc
   <https://github.com/jodogne/OrthancContributed/blob/master/Links.md#vagrant>`__.
 
@@ -62,9 +62,10 @@
 
 Once Orthanc is up and running, any imaging modality can send
 instances to Orthanc through the DICOM protocol (with the C-Store
-command).
+command).  Check :ref:`this tutorial <configure-modality>` to 
+connect your modality to Orthanc.
 
-You can use the standard command-line tool ``storescu`` from the
+You can also use the standard command-line tool ``storescu`` from the
 `DCMTK software <http://dicom.offis.de/dcmtk.php.en>`__ to 
 manually send DICOM images to Orthanc, for instance::