We are running the orthancs server in docker-compose, Now we want to listen the Pacs through a script. When we try to send the dicom modalities we are getting the below error:

General
1

DicomAssociation.cpp:279] (dicom) Opening a DICOM SCU connection without DICOM TLS from AET “HELLO” to AET “ORTHANC” on host 127.0.0.1:11112 (manufacturer: Generic, timeout: 60s)
manentia_mpacs-orthanc-1 | E0922 09:36:24.142476 OrthancException.cpp:61] Error in the network protocol: DicomAssociation - connecting to AET “ORTHANC”: TCP Initialization Error: Connection refused

what is solution

2

Hi ! (word used as a friendly greeting or to attract attention)

You are not providing much relevant information about your setup.

As the log says, the “ORTHANC” servers refuses the connection. This can happen because the “HELLO” AET has not been declared in the DicomModalities configuration in “ORTHANC” or is not allowed to perform this operation (from the same configuration).

Best regards

Alain

3

Hi

Am trying to deploy the Orthanc in the cloud and want to save the uploaded dicom files to S3 so I used the docker solution from Orthanc and have to actively listen to the DCOM server if any studies are sent to the dicom modality for that I wrote a Python script (thanks to Pynetdicom) that acts as middleware to trigger my image processing backend server

From normal installation (no docker), everything is working fine to the dicom port using the script jobs are successful, but using the docker solution gives a TCP initialization error
am using the same config that I used in normal installation

We are running the orthancs server in docker-compose, Now we want to listen the Pacs through a script. When we try to send the dicom modalities we get the below error:

DicomAssociation.cpp:279] (dicom) Opening a DICOM SCU connection without DICOM TLS from AET “HELLO” to AET “ORTHANC” on host 127.0.0.1:11112 (manufacturer: Generic, timeout: 60s)
manentia_mpacs-orthanc-1 | E0922 09:36:24.142476 OrthancException.cpp:61] Error in the network protocol: DicomAssociation - connecting to AET “ORTHANC”: TCP Initialization Error: Connection refused

4

You didn’t mention whether you are using your own docker images, Sebastien’s images, Osimis images or some other. I agree with Alain. My first guess would involve the DicomModalities configuration.

I would docker exec into the Orthanc container and confirm that the existing configuration json file is what you intend. Some of the docker images start with their own assumptions about default configuration values. If you are providing your own external configuration.json file, you want to make sure it is not being modified during the docker spinup.

You should also be able to get the details of the running modalities with a call to the /modalities URL.

Alternatively, you can access the configuration with the GetConfiguration() call. I know this works with the python plugin and I believe there is a similar Lua version of the call.

John.