Called AET and Verification SOP Class

[tburba]

PacsOne requires a correct Called AET when accepting associations for storage SOP classes. However in case of Verification SOP class, only Calling AET must match.

Here PacsOne 6.4.1 has the default "MyAeTitle" assigned, but reports success even if the client calls it "PACS77":

Code: Select all

dcm4che\bin>dcmecho.bat PACS77@172.16.16.4:104 -L DCMSND
12:02:14,621 INFO   - Association(1) initiated Socket[addr=/172.16.16.4,port=104,localport=52269]
12:02:14,636 INFO   - PACS77(1): A-ASSOCIATE-RQ PACS77 << DCMSND
12:02:14,690 INFO   - PACS77(1): A-ASSOCIATE-AC DCMSND >> PACS77
Connected to PACS77@172.16.16.4:104 in 0.307s
12:02:14,875 INFO   - PACS77(1) << 1:C-ECHO-RQ[pcid=1
        cuid=1.2.840.10008.1.1/Verification SOP Class]
12:02:14,895 INFO   - PACS77(1) >> 1:C-ECHO-RSP[pcid=1, status=0H
        cuid=1.2.840.10008.1.1/Verification SOP Class]
Perform Verification in -0.206s
12:02:14,901 INFO   - PACS77(1) << A-RELEASE-RQ
12:02:14,905 INFO   - PACS77(1) >> A-RELEASE-RP
Released connection to PACS77@172.16.16.4:104
12:02:14,908 INFO   - PACS77(1): close Socket[addr=/172.16.16.4,port=104,localport=52269]

A bit inconvenient for our application as Echo is used there to verify configuration before sending the images.

[pacsone]

PacsOne Server validates only the Calling AE Title, but not the Called AE Title in the incoming Dicom association requests, so it does not matter what AE Title the clients refer to PacsOne Server, as long as the hostname/IP address and TCP port information are correct.

[tburba]

I was mistaken. Just checked: indeed PacsOne accepts any Called AET also when images are sent, therefore Echo is an adequate test.