Mercurial > hg > orthanc-book

comparison Sphinx/source/users/support.rst @ 454:a983d7c639dd

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
fix links
author Sebastien Jodogne <s.jodogne@gmail.com>
date Tue, 07 Jul 2020 12:32:40 +0200
parents 74fc0203d882
children eb60d014765b
comparison
equal deleted inserted replaced
450:235a5541e06e 454:a983d7c639dd
9 ---------------------- 9 ----------------------
10 10
11 When you face a problem, you should first check out the following 11 When you face a problem, you should first check out the following
12 resources: 12 resources:
13 13
14 1. Make sure to :ref:`check all the content of the Orthanc Book 14 1. Make sure that you use the `latest version of Orthanc
15 <http://www.orthanc-server.com/download.php>`__.
16 2. Make sure to :ref:`check all the content of the Orthanc Book
15 <orthanc-book>`, and notably to :ref:`understand the basics of 17 <orthanc-book>`, and notably to :ref:`understand the basics of
16 DICOM <dicom-guide>`. 18 DICOM <dicom-guide>`.
17 2. Carefully read your :ref:`log files in verbose mode <log>`. 19 3. Carefully read your :ref:`log files in verbose mode <log>`.
18 3. In the case of DICOM networking problems, carefully read the log 20 4. In the case of DICOM networking problems, carefully read the log
19 files from your remote modality. If you are :ref:`using Orthanc 21 files from your remote modality. If you are :ref:`using Orthanc
20 against a proprietary system <proprietary>`, contact the support 22 against a proprietary system <proprietary>`, contact the support
21 team from the vendor of this system: You pay them to solve your 23 team from the vendor of this system: You pay them to solve your
22 setup issues. 24 setup issues.
23 4. Follow the :ref:`general troubleshooting guide <troubleshooting>`. 25 5. Follow the :ref:`general troubleshooting guide <troubleshooting>`.
24 5. If the problem is related to the DICOM network protocol, follow 26 6. If the problem is related to the DICOM network protocol, follow
25 the :ref:`DICOM troubleshooting guide <dicom>`. 27 the :ref:`DICOM troubleshooting guide <dicom>`.
26 6. Have a look at **all** the :ref:`frequently asked questions (FAQs) 28 7. Have a look at **all** the :ref:`frequently asked questions (FAQs)
27 <faq>` that are already available in the Orthanc Book. 29 <faq>` that are already available in the Orthanc Book.
28 7. Make a search for similar problem previously discussed in the 30 8. Make a search for similar problem previously discussed in the
29 `Orthanc Users discussion forum 31 `Orthanc Users discussion forum
30 <https://groups.google.com/forum/#!forum/orthanc-users>`__. 32 <https://groups.google.com/forum/#!forum/orthanc-users>`__.
31 8. Check out the ``Pending changes in the mainline`` section of the 33 9. Check out the ``Pending changes in the mainline`` section of the
32 `NEWS file 34 `NEWS file
33 <https://hg.orthanc-server.com/orthanc/file/default/NEWS>`__, as 35 <https://hg.orthanc-server.com/orthanc/file/default/NEWS>`__, as
34 your issue might already be solved in the mainline of Orthanc (i.e. 36 your issue might already be solved in the mainline of Orthanc (i.e.
35 in the cutting-edge version of Orthanc since the last stable 37 in the cutting-edge version of Orthanc since the last stable
36 official release). 38 official release).
37 9. Carefully read the `TODO file 39 10. Carefully read the `TODO file
38 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that 40 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that
39 contains our roadmap, as you might be requesting a feature that is 41 contains our roadmap, as you might be requesting a feature that is
40 currently pending in our backlog (i.e. not implemented yet). 42 currently pending in our backlog (i.e. not implemented yet).
41 10. Look for similar issue in the `official bug tracker 43 11. Look for similar issue in the `official bug tracker
42 <https://bugs.orthanc-server.com/query.cgi>`__ (make sure to 44 <https://bugs.orthanc-server.com/query.cgi>`__ (make sure to
43 select ``All`` in the ``Status`` field, as your issue might 45 select ``All`` in the ``Status`` field, as your issue might
44 already have been solved). 46 already have been solved).
45 47
46 48
47 Importantly, for all the features that are pending in the ``TODO`` 49 Importantly, for all the features that are pending in the ``TODO``
48 file, if you are a company, please consider `buying professional 50 file, if you are a company, please consider `buying professional
49 services <https://www.orthanc-server.com/orthanc-pro.php>`__ in order 51 services <https://www.osimis.io/en/services.html>`__ in order to get
50 to get the feature implemented faster. 52 the feature implemented faster.
51 53
52 54
53 .. _support-mwe: 55 .. _support-mwe:
54 56
55 Discussing a minimal working example 57 Discussing a minimal working example