Hi everyone,
I am looking to setup an intermediary between modalities we have in a lab and an external PACS. I tried to set up the non-Orthanc PACS as a modality, however, I am not sure if I am entering the PACS data wrongly but the Orthanc Server I set up does not recognize the other PACS (I sent a screenshot when I tried to do C-Echo). The communication between the server that I raised by the HTTP port and the PACS works without any problem.
I attach the screenshots. Thank you very much for your time.
Carlos,
There is a long form for orthanc.json to configure modalities, like:
{
// “AET” : “ORTHANC”,
// “Port” : 104,
// “Host” : “127.0.0.1”,
// “Manufacturer” : “Generic”,
// “AllowEcho” : true,
// “AllowFind” : true,
// “AllowFindWorklist” : true, // new in 1.10.0
// “AllowGet” : true,
// “AllowMove” : true,
// “AllowStore” : true,
// “AllowStorageCommitment” : false, // new in 1.6.0
// “AllowTranscoding” : true, // new in 1.7.0
// “UseDicomTls” : false // new in 1.9.0
// “LocalAet” : “HELLO” // new in 1.9.0
// “Timeout” : 60 // new in 1.9.1
//}
and you can store those in a DB as well. In my limited experience with that, the problem could be a number of things.
-
The ports that you are using for DICOM are blocked somewhere (Windows, Router, Firewall, etc.). Make sure you have connectivity by just pinging through the CLI.
-
You are using TLS and do not have that setup correctly. TLS is nice to have, but when you are first setting things up it helps to not throw that into the mix.
There is a page in the Orthanc Book that talks about how to go about troubleshooting:
https://book.orthanc-server.com/faq/dicom.html
It is a long list, but you might have to check each one.
It also helps to turn on verbose or trace for the orthanc.log. There might be something in the log files or in the log files on the other device that will point you in the right direction.
Stephen D. Scotti