C-Echo Behavior (wrong AET, wrong Port)

General
1

Hello, just inquiring about the behavior of C-ECHO. The echo is sent from a Orthanc to another Orthanc. Each one being a kubernetes pod.

Our team uses v1.11.0 of Orthanc.

image
image1669×203 9.98 KB

Here I’ve registered two modalities, and one of them, orthanc-customer-2, is an incorrect AE title however, when I C-ECHO it returns success. Is this expected behavior for Orthanc? (Ignores AET match given IP and PORT are correct)

Additionally, I’ve noticed that when I registered two modalities with the same AET, and IP but different Ports. I can only see one in the Orthanc UI which is as expected. However, when I do C-Echo using the wrong port (i.e. not 4242), most of the times I get a failure but sometimes I get a success (rare). I don’t understand this behavior.

Here’s the Python code being used for testing the connection

OrthancInterface.put(
    path=f"modalities/{local_aet}",
    data={
        "AET": PACS_CONFIGURATION["aet_name"],
        "Host": PACS_CONFIGURATION["ip_address"],
        "Port": PACS_CONFIGURATION["port"],
        "Timeout": 60,
        "UseDicomTls": False,
    },
)

if echo:
    OrthancInterface.post(
        path=f"modalities/{local_aet}/echo",
        data={},
        timeout=5,
    )
return True

Thank you very much for your help! Let me know if more details are needed.

2

Hi

On the receiving Orthanc, this configuration has an impact on this behaviour:

  // Check whether the called AET corresponds to the AET of Orthanc
  // during an incoming DICOM SCU request
  "DicomCheckCalledAet" : false,

By default, Orthanc does not check the called AET.

Me neither :wink: Could you provide a sample docker-compose file that would allow us to reproduce this ?

HTH,

Alain