Mercurial > hg > orthanc-book

comparison Sphinx/source/users/support.rst @ 388:a3288fe6f84e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
proprietary-support
author Sebastien Jodogne <s.jodogne@gmail.com>
date Mon, 20 Apr 2020 07:41:44 +0200
parents d217af5e6cb3
children deee9da91633
comparison
equal deleted inserted replaced
387:1974913fd28a 388:a3288fe6f84e
13 13
14 1. Make sure to :ref:`check all the content of the Orthanc Book 14 1. Make sure to :ref:`check all the content of the Orthanc Book
15 <orthanc-book>`, and notably to :ref:`understand the basics of 15 <orthanc-book>`, and notably to :ref:`understand the basics of
16 DICOM <dicom-guide>`. 16 DICOM <dicom-guide>`.
17 2. Carefully read your :ref:`log files in verbose mode <log>`. 17 2. Carefully read your :ref:`log files in verbose mode <log>`.
18 3. Follow the :ref:`general troubleshooting guide <troubleshooting>`. 18 3. In the case of DICOM networking problems, carefully read the log
19 4. If the problem is related to the DICOM network protocol, follow 19 files from your remote modality. If you are :ref:`using Orthanc
20 against a proprietary system <proprietary>`, contact the support
21 team from the vendor of this system: You pay them to solve your
22 setup issues.
23 4. Follow the :ref:`general troubleshooting guide <troubleshooting>`.
24 5. If the problem is related to the DICOM network protocol, follow
20 the :ref:`DICOM troubleshooting guide <dicom>`. 25 the :ref:`DICOM troubleshooting guide <dicom>`.
21 5. Have a look at **all** the :ref:`frequently asked questions (FAQs) 26 6. Have a look at **all** the :ref:`frequently asked questions (FAQs)
22 <faq>` that are already available in the Orthanc Book. 27 <faq>` that are already available in the Orthanc Book.
23 6. Make a search for similar problem previously discussed in the 28 7. Make a search for similar problem previously discussed in the
24 `Orthanc Users discussion forum 29 `Orthanc Users discussion forum
25 <https://groups.google.com/forum/#!forum/orthanc-users>`__. 30 <https://groups.google.com/forum/#!forum/orthanc-users>`__.
26 7. Check out the ``Pending changes in the mainline`` section of the 31 8. Check out the ``Pending changes in the mainline`` section of the
27 `NEWS file 32 `NEWS file
28 <https://hg.orthanc-server.com/orthanc/file/default/NEWS>`__, as 33 <https://hg.orthanc-server.com/orthanc/file/default/NEWS>`__, as
29 your issue might already be solved in the mainline of Orthanc (i.e. 34 your issue might already be solved in the mainline of Orthanc (i.e.
30 in the cutting-edge version of Orthanc since the last stable 35 in the cutting-edge version of Orthanc since the last stable
31 official release). 36 official release).
32 8. Carefully read the `TODO file 37 9. Carefully read the `TODO file
33 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that 38 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that
34 contains our roadmap, as you might be requesting a feature that is 39 contains our roadmap, as you might be requesting a feature that is
35 currently pending in our backlog (i.e. not implemented yet). 40 currently pending in our backlog (i.e. not implemented yet).
36 9. Have a look for the issue in the `official bug tracker 41 10. Have a look for the issue in the `official bug tracker
37 <https://bitbucket.org/sjodogne/orthanc/issues?status=new&status=open>`__ 42 <https://bitbucket.org/sjodogne/orthanc/issues?status=new&status=open>`__
38 (click on the ``All`` button, as your issue might already been solved). 43 (click on the ``All`` button, as your issue might already been
44 solved).
39 45
40 46
41 Importantly, for all the features that are pending in the ``TODO`` 47 Importantly, for all the features that are pending in the ``TODO``
42 file, if you are a company, please consider `buying professional 48 file, if you are a company, please consider `buying professional
43 services <https://www.orthanc-server.com/orthanc-pro.php>`__ in order 49 services <https://www.orthanc-server.com/orthanc-pro.php>`__ in order
70 calls the :ref:`REST API of Orthanc <rest>`. The most useful 76 calls the :ref:`REST API of Orthanc <rest>`. The most useful
71 commands are `cURL <https://en.wikipedia.org/wiki/CURL>`__, `DCMTK 77 commands are `cURL <https://en.wikipedia.org/wiki/CURL>`__, `DCMTK
72 <https://dicom.offis.de/dcmtk.php.en>`__, `dicom3tools 78 <https://dicom.offis.de/dcmtk.php.en>`__, `dicom3tools
73 <https://www.dclunie.com/dicom3tools.html>`__, `dcm4che command-line 79 <https://www.dclunie.com/dicom3tools.html>`__, `dcm4che command-line
74 tools <https://www.dcm4che.org/>`__, or Python scripts. 80 tools <https://www.dcm4che.org/>`__, or Python scripts.
81 * In the case of DICOM networking problems, the logs from the remote
82 modality.
75 * If applicable, a screenshot is worth a thousands word. 83 * If applicable, a screenshot is worth a thousands word.
76 * If you report a crash, if applicable, a :ref:`core file <crash>`. 84 * If you report a crash, if applicable, a :ref:`core file <crash>`.
77 85
78 All this information is mandatory, as it allows other members of the 86 All this information is mandatory, as it allows other members of the
79 Orthanc community to **reproduce your problem independently of your 87 Orthanc community to **reproduce your problem independently of your