Mercurial > hg > orthanc-book
annotate Sphinx/source/users/support.rst @ 616:1a0313342e17
oliver tsai
| author | Sebastien Jodogne <s.jodogne@gmail.com> |
|---|---|
| date | Mon, 15 Feb 2021 08:24:38 +0100 |
| parents | da558cda9de8 |
| children | 88432d03b56a |
| rev | line source |
|---|---|
| 271 | 1 .. _support: |
| 2 | |
| 3 Asking for support | |
| 4 ================== | |
| 5 | |
| 6 .. _support-resources: | |
| 7 | |
| 8 Analyzing your problem | |
| 9 ---------------------- | |
| 10 | |
| 11 When you face a problem, you should first check out the following | |
| 12 resources: | |
| 13 | |
| 454 | 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 | |
| 277 | 17 <orthanc-book>`, and notably to :ref:`understand the basics of |
| 18 DICOM <dicom-guide>`. | |
| 454 | 19 3. Carefully read your :ref:`log files in verbose mode <log>`. |
| 20 4. In the case of DICOM networking problems, carefully read the log | |
|
388
a3288fe6f84e
proprietary-support
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
360
diff
changeset
|
21 files from your remote modality. If you are :ref:`using Orthanc |
|
a3288fe6f84e
proprietary-support
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
360
diff
changeset
|
22 against a proprietary system <proprietary>`, contact the support |
|
a3288fe6f84e
proprietary-support
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
360
diff
changeset
|
23 team from the vendor of this system: You pay them to solve your |
|
a3288fe6f84e
proprietary-support
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
360
diff
changeset
|
24 setup issues. |
| 454 | 25 5. Follow the :ref:`general troubleshooting guide <troubleshooting>`. |
| 26 6. If the problem is related to the DICOM network protocol, follow | |
| 271 | 27 the :ref:`DICOM troubleshooting guide <dicom>`. |
| 454 | 28 7. Have a look at **all** the :ref:`frequently asked questions (FAQs) |
| 271 | 29 <faq>` that are already available in the Orthanc Book. |
| 454 | 30 8. Make a search for similar problem previously discussed in the |
| 271 | 31 `Orthanc Users discussion forum |
| 32 <https://groups.google.com/forum/#!forum/orthanc-users>`__. | |
| 454 | 33 9. Check out the ``Pending changes in the mainline`` section of the |
| 271 | 34 `NEWS file |
| 360 | 35 <https://hg.orthanc-server.com/orthanc/file/default/NEWS>`__, as |
| 271 | 36 your issue might already be solved in the mainline of Orthanc (i.e. |
| 37 in the cutting-edge version of Orthanc since the last stable | |
| 38 official release). | |
| 454 | 39 10. Carefully read the `TODO file |
| 40 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that | |
| 41 contains our roadmap, as you might be requesting a feature that is | |
| 42 currently pending in our backlog (i.e. not implemented yet). | |
| 43 11. Look for similar issue in the `official bug tracker | |
|
445
987fbbc2b59e
leaving bitbucket wrt. bug tracker
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
389
diff
changeset
|
44 <https://bugs.orthanc-server.com/query.cgi>`__ (make sure to |
|
987fbbc2b59e
leaving bitbucket wrt. bug tracker
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
389
diff
changeset
|
45 select ``All`` in the ``Status`` field, as your issue might |
|
987fbbc2b59e
leaving bitbucket wrt. bug tracker
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
389
diff
changeset
|
46 already have been solved). |
| 271 | 47 |
| 48 | |
| 49 Importantly, for all the features that are pending in the ``TODO`` | |
| 50 file, if you are a company, please consider `buying professional | |
| 454 | 51 services <https://www.osimis.io/en/services.html>`__ in order to get |
| 52 the feature implemented faster. | |
| 271 | 53 |
| 54 | |
| 55 .. _support-mwe: | |
| 56 | |
| 57 Discussing a minimal working example | |
| 58 ------------------------------------ | |
| 59 | |
| 60 If none of these resources help, you can consider sending a message to | |
| 61 the `Orthanc Users discussion forum | |
| 62 <https://groups.google.com/forum/#!forum/orthanc-users>`__. In such a | |
| 63 situation, you **must** provide a `minimal working example | |
| 64 <https://en.wikipedia.org/wiki/Minimal_working_example>`__, which means that | |
| 65 you must provide all the following information: | |
| 66 | |
| 67 * Context and full textual description of your issue. When talking | |
| 68 about DICOM networking issues, carefully describe the imaging | |
| 69 modalities into play (including their manufacturers) and your | |
| 70 network topology. | |
| 446 | 71 * The observed vs. expected results. |
| 271 | 72 * Full :ref:`configuration files <configuration>`. |
| 73 * Full logs as produced by Orthanc in :ref:`verbose mode <log>`. | |
| 74 * Sample DICOM files. | |
| 75 * A sequence of command lines that lead to your problem. These command | |
| 321 | 76 lines must only use commands that are available as free and |
| 77 open-source software, that are cross-platform (:ref:`proprietary | |
| 78 software does not help <proprietary>`), and that are preferably | |
| 79 calls the :ref:`REST API of Orthanc <rest>`. The most useful | |
| 80 commands are `cURL <https://en.wikipedia.org/wiki/CURL>`__, `DCMTK | |
| 271 | 81 <https://dicom.offis.de/dcmtk.php.en>`__, `dicom3tools |
| 82 <https://www.dclunie.com/dicom3tools.html>`__, `dcm4che command-line | |
| 83 tools <https://www.dcm4che.org/>`__, or Python scripts. | |
|
388
a3288fe6f84e
proprietary-support
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
360
diff
changeset
|
84 * In the case of DICOM networking problems, the logs from the remote |
|
a3288fe6f84e
proprietary-support
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
360
diff
changeset
|
85 modality. |
| 389 | 86 * If applicable, a screenshot is worth a thousand words. |
| 271 | 87 * If you report a crash, if applicable, a :ref:`core file <crash>`. |
| 88 | |
| 89 All this information is mandatory, as it allows other members of the | |
| 90 Orthanc community to **reproduce your problem independently of your | |
| 91 setup**. If we can't reproduce your issue, we can't provide any | |
| 92 support! | |
| 93 | |
| 330 | 94 In addition, please note that the original author of Orthanc |
| 95 (Sébastien Jodogne), as a free software advocate, will only personally | |
| 96 deal with issues that are reproducible on recent GNU/Linux | |
| 97 distributions (typically, on Ubuntu 18.04 LTS or through Docker). | |
| 98 | |
| 271 | 99 |
| 100 .. _support-tracker: | |
| 101 | |
| 102 Using the bug tracker | |
| 103 --------------------- | |
| 104 | |
| 105 If you are **sure** that you are reporting a yet unknown bug, you can | |
| 106 consider directly introducing a `bug report on our issue tracker | |
|
445
987fbbc2b59e
leaving bitbucket wrt. bug tracker
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
389
diff
changeset
|
107 <https://bugs.orthanc-server.com/enter_bug.cgi>`__. Beware however |
| 271 | 108 that your issue might be closed if too vague or if not reproducible. |
| 109 As a consequence, it is advised to first use the discussion forum. | |
| 613 | 110 |
| 111 | |
| 112 .. _support-freelancers: | |
| 113 | |
| 114 Finding professional assistance | |
| 115 ------------------------------- | |
| 116 | |
| 117 If you face a problem you cannot solve by yourself, please follow this | |
| 118 decision chart: | |
| 119 | |
| 120 1. If you have a **reproducible issue** for which you can provide a | |
| 121 :ref:`minimal working example <support-mwe>` using only free and | |
| 122 open-source tools, use the `Orthanc Users discussion forum | |
| 123 <https://groups.google.com/forum/#!forum/orthanc-users>`__. | |
| 124 | |
| 125 2. If you need an **additional feature or a dedicated development**, | |
| 126 and if you are ready to pay, `get in touch with Osimis | |
| 127 <mailto:orthanc-support@osimis.io>`__, the commercial partner of | |
| 128 the Orthanc project. | |
| 129 | |
| 130 3. If you are not able to reproduce an issue by yourself, if you are | |
| 131 looking for personalized help related to deployments/training/..., | |
| 132 or if you need **proximity support in your language/timezone**, | |
| 133 here is a list of freelancers: | |
| 134 | |
| 135 * **Europe** : | |
| 136 | |
| 137 * `Adrian Schiopu <sc.callisto.srl@gmail.com>`__ (Romania) | |
| 138 * `Krzysztof Turkiewicz <http://www.deeveeloop.pl/>`__ (Polish/English, Poland) | |
| 139 * `Salim Kanoun <https://github.com/salimkanoun>`__ (French/English/Arabic, France) | |
| 140 | |
| 141 * **North America**: | |
| 142 | |
| 143 * `Gabriel Couture <https://github.com/gacou54/>`__ (French/English, Canada) | |
| 144 * `Mohannad Hussain <https://www.linkedin.com/in/mohannadhussain/>`__ (English, Canada) | |
| 616 | 145 * `Oliver Tsai <mailto:oliver@futurepacs.com>`__ (English/Spanish/French, Toronto) |
| 146 | |
| 613 | 147 |
| 148 * **South America**: | |
| 149 | |
| 150 * `Claudio Arenas <mailto:dentista.arenas@gmail.com>`__ (Spanish/English, Chile) | |
| 151 * `Gustavo Fernandez <https://www.linkedin.com/in/gfernandezguirland/>`__ (Spanish/Portuguese, Uruguay) | |
| 152 * `Luiz Eduardo Guida Valmont <https://www.linkedin.com/in/luizvalmont/>`__ (English/Portuguese, Brazil) | |
| 153 * `William Sanchez Luis <mailto:williamsanchezluis@gmail.com>`__ (English/Spanish, Venezuela) | |
| 154 | |
| 155 * **Asia**: | |
| 156 | |
| 157 * `Phong Tran Duc <http://www.itechcorp.com.vn/>`__ (English/Vietnamese, Vietnam) | |
| 158 * `Rana Asim Wajid <http://ethosmed.com/>`__ (English/Urdu/Punjabi, Pakistan) | |
| 159 | |
| 160 * **Oceania**: | |
| 161 | |
| 162 * `James Manner <https://binary.com.au/>`__ (English, Australia) | |
| 163 | |
| 614 | 164 Get in touch with `Sébastien Jodogne |
| 165 <mailto:s.jodogne@orthanc-labs.com>`__ if you want to be included | |
| 166 in this list. | |
| 167 |