Same AE Titles, same ports but different IP addresses

Is is possible to have two or more dicom modalities with same AE Titles, same ports but different IP addresses ?

If you use DICOM SEND and DICOM WORKLIST, yes.
Bit, if you use QUERY/RETRIVE, do not work.

But* not Bit.
With c-move.

Actually I believe it's working fine.

https://bitbucket.org/osimis/orthanc-setup-samples/src/5bf7579bfcde72f1
854012db4404b49044f853d7/docker/duplicate-aet/docker-compose.yml (https
://bitbucket.org/osimis/orthanc-setup-
samples/src/master/docker/duplicate-aet/docker-compose.yml)

$ cat docker-compose.yml
version: "2"

services:
    foo:
        image: osimis/orthanc
        ports: ["80:8042"]
        environment:
            NAME: Foo
            DICOM_AET: FOOBAR
            DICOM_MODALITIES: |
                {
                    "bar": ["FOOBAR", "bar", 4242]
                }

    bar:
        image: osimis/orthanc
        ports: ["81:8042"]
        environment:
            NAME: Bar
            DICOM_AET: FOOBAR
            DICOM_MODALITIES: |
                {
                    "foo": ["FOOBAR", "foo", 4242]
                }
$ host=${DOCKER_HOST%:*}
$ http POST $host/modalities/bar/echo
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 22
Content-Type: application/json

{}

$ http POST $host/modalities/bar/query Level=Study
Query:='{"PatientID": "vAD7q3"}'
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 93
Content-Type: application/json; charset=utf-8

{
    "ID": "4c8e5b25-0693-4aa2-86d7-f6fe411689ca",
    "Path": "/queries/4c8e5b25-0693-4aa2-86d7-f6fe411689ca"
}

$ http GET $host/queries/4c8e5b25-0693-4aa2-86d7-f6fe411689ca
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 67
Content-Type: application/json; charset=utf-8

[
    "answers",
    "level",
    "modality",
    "query",
    "retrieve"
]

$ http GET $host/queries/4c8e5b25-0693-4aa2-86d7-f6fe411689ca/answers
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 28
Content-Type: application/json; charset=utf-8

[
    "0"
]

$ http GET $host/queries/4c8e5b25-0693-4aa2-86d7-f6fe411689ca/answers/0
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 46
Content-Type: application/json; charset=utf-8

[
    "content",
    "retrieve"
]

$ http POST $host/queries/4c8e5b25-0693-4aa2-86d7-
f6fe411689ca/answers/0/retrieve
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 22
Content-Type: application/json

{}

$ http $host/tools/find Level=Patients Query:='{"PatientID": "vAD7q3"}'
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 71
Content-Type: application/json; charset=utf-8

[
    "a8d72883-45661eab-168bafbf-d799b4dc-4fc83a26"
]

So it works?

Commit with 20' Ago! Rsrs

?

As you can see, yes.

Feel free to try it out by yourself using the sample setup I provided.

(That commit just added the sample setup I created to test it, I don't
think the behavior of Orthanc ever changed with regard to how it
handles duplicate AETs.)

Tried it out in a live svenario and I can confirm that it does indeed work. Thanks !!!