Hello,
I am using the option
"DicomCheckCalledAet": true
but I want it active on certain Modalities only. I have some Modalities in which I can’t configure the AE title and I would like to make an exception to them. I tried checking the option LocalAet
of Modalities but it only works when Orthanc acts as an SCU and not an SCP.
Is this something which would be possible using some other method? Moreover, would it be possible to live-change the value of DicomCheckCalledAet
as Orthanc is running, e.g., via a REST API call?
Thank you!
Hi Guillem,
I can image 2 workarounds:
- deploy multiple Orthancs connected to the same DB and storage. One with
"DicomCheckCalledAet":
true
and one with "DicomCheckCalledAet":
false
. These modalities would connect to the second one
- use the new Multitenant DICOM plugin and declare new servers with a specific port and the AET expected by these modalities and just skip the
labels
configuration. disclaimer: I’ve never tried this solution
Concerning changing DicomCheckCalledAet
dynamicaly through the REST Api: there is no plan to do so and this makes no sens to do it only for this configuration → that would need a rewrite of all the configurations in Orthanc to store them in DB and this is not in our plans.
HTH,
Alain.
1 Like
Hi Alain,
Thank you very much for your proposal! I think the first makes most sense. I tested it and it works.
For context, though, we also wanted to have a functionality to dynamically change the AE title to which responses would be fulfilled. This is tricky in Orthanc because AE title is statically loaded at startup and can only be changed in the config file (afaik). So we ended up building a simple an independent SCP which takes care of that functionality.
Thank you very much for your help!
Best,
Guillem.
Hi Guillem
For what it’s worth, this Orthanc setup sample demonstrates how to modify the configuration dynamically and restart Orthanc.
Depending on your use case and the frequency at which you need to change the AET, this could perhaps help? (your dedicated SCP sounds better, though)
Yes, we also looked into that possibility, but unfortunately now suitable for our setup (we have other callbacks at startup that we don’t want to be often triggered). The dedicated SCP was indeed the best choice. Thanks for the suggestion