DICOM authorization rejected

Google Groups archive
1

hi

I ran orthanc through docker, and the following error pops up when I search through the viewer to retrieve data in the server. What is the problem?

스크린샷 2023-01-06 오후 2.10.44.png

2

Hi,

Check the documentation on how to connect another modality/DICOM node to Orthanc.

Alain

스크린샷 2023-01-06 오후 2.10.44.png

3

Ok, thanks.

The problem has been solved, and the success of C-ECHO is confirmed in RADIANT, but the failure of C-ECHO in RADIANT appears in ORTHANC web. What is the reason?

image.png

2023년 1월 6일 (금) 오후 8:22, Alain Mazy am@orthanc.team님이 작성:

스크린샷 2023-01-06 오후 2.10.44.png

4

Hello,

Have you properly configured Radiant? What message appears in the Radiant logs?

What appears in the verbose logs of Orthanc?
https://book.orthanc-server.com/users/support.html#discussing-a-minimal-working-example

Sébastien-

스크린샷 2023-01-06 오후 2.10.44.png

image.png

5

Hi everyone, I am discovering Orthanc that I am starting to configure. A problem that I can’t solve and have a Canfield tool access to download the worklists I get the following messages

W1211 01:17:39.607616 main.cpp:405] DICOM authorization rejected for AET CanfieldDICOM on IP 93.xxx.186.xxx: This AET is not listed in configuration option “DicomModalities”
W1211 01:17:39.607692 CommandDispatcher.cpp:830] Rejected FindWorklist request from remote DICOM modality with AET “CanfieldDICOM” and hostname “94.xxx.188.xxx”

With these parameters it doesn’t work

/ The list of the known DICOM modalities
“DicomModalities” : {
“echo1” : [ “CanfieldDICOM”, “94.xxx.188.xxx”, 105 ]
},

Thanks Corrado

screenshot_4178
screenshot_41781788×1256 87.4 KB

6

Hi,

Well, it seems that the modality is contacting Orthanc with another IP than the one you have declared.

Also note that this parameter can enable/disable IP checks:

  // Whether Orthanc checks the IP/hostname address of the remote
  // modality initiating a DICOM connection (as listed in the
  // "DicomModalities" option above). If this option is set to
  // "false", Orthanc only checks the AET of the remote modality.
  "DicomCheckModalityHost" : false

Last option, make sure that your configuration file is taken into account by e.g, opening http://localhost:8042/modalities?expand

HTH,

Alain

7

Hi I tried but it doesn’t work yet. I still study and then rewrite. Thanks Corrado

8

Hi I succeeded.
I studied here the configuration file is explained very well and divided by blocks which helped me to become aware which parts to analyze.
https://src.fedoraproject.org/rpms/orthanc/c/2d8a991b6833e360ef5fe8e73650e85fdbf10c51?branch=rawhide
System some parameters and rewritten this part in this way everything worked.

“CanfieldDICOM” : [ “CanfieldDICOM”, “94.xx.188.xxx”, 4042 ]

IP of the machine it calls, name of the machine it calls, data that appeared on the log, communication door defined on my server

Thanks Corrado