listening on multiple AE titles

Google Groups archive
1

Can Orthanc listen on multiple AE titles, in a single instance? I would like to liseten on 10 or so AE titles at once.

Thanks
K

2

Hello,

Can Orthanc listen on multiple AE titles, in a single instance? I
would like to liseten on 10 or so AE titles at once.

Yes, by default it doesn't care what other modalities call it. Only
when the DicomCheckCalledAet setting is set to true will it block
associations so:

foo_1 | E0810 10:01:21.653097 DicomUserConnection.cpp:168]
DicomUserConnection: DUL Association Rejected
foo_1 | E0810 10:01:21.654826 ServerScheduler.cpp:123] Job has failed
(HTTP request: Store-SCU to peer "baz")

baz_1 | W0810 10:01:21.652117 CommandDispatcher.cpp:633] Rejected
association, because of a bad called AET in the request (BAR)

I've uploaded a quick sample setup here:
https://bitbucket.org/osimis/orthanc-setup-samples/src/d1e0017863db/doc
ker/aet-check/?at=master

3

Thibault,

Thank you for the reply. Yes, I did see in the documentation that it is by default promiscuous, but can be locked down to known senders. What I am trying to do is have Orthanc receive or listen on several AE titles. I am trying to mimic a production system where each of my modalities, (clinics) sends into a different AE. in PROD that AE relates to a specific storage, but for this they can go into the default storage. Can I have my modalities store to AE ORTHANC, ORTHANC2 and ORTHANC3 all running on the same instance, or do I need to run multiple instances of Orthanc on my server?

Thank you,
Kyle

4

I do this by running multiple Orthanc docker containers, each listening on different ports/AETITLES, but all writing to the same postgres database and disk space. As I recall, the the only thing I had to do was add an option in the config to tell orthanc not to lock the db table while it is in use.

Derek-

5

Thank you Derek!

6

I just double checked my config, Kyle. I think that at the time, "Lock" was an undocumented parameter that I dug up in an old post of Sebastien's. Hopefully it is in the documentation now.

"PostgreSQL" : {
    "EnableIndex" : true,
    "EnableStorage" : false,
--> "Lock" : false, <--
    "Host" : "db",
    "Port" : 123,
    "Database" : "my_db",
    "Username" : "user",
    "Password" : "p455w*rd"
  }

(Don't tell anyone my p455w*rd!)