corrupt Action Type ID in N-ACTION-RQ (stgcmt)

[tburba]

I was investigating why dcm4chee-arc 4.3.0 throws an exception when processing a Storage Commitment Request from PacsOne 6.4.3, and found this:

Code: Select all

Transmission Control Protocol, Src Port: 49293 (49293), Dst Port: dicom (11112), Seq: 212, Ack: 177, Len: 122
DICOM
    PDU Type 0x4 (Data)
    PDU Length: 116
    PDV
        PDV Length: 112
        Context: 0x13 (Implicit VR Little Endian, Storage Commitment Push Model SOP Class)
        Flags: 0x03 (Command, Last Fragment)
        (0000,0000)          4 Command Group Length                          98
        (0000,0003)         20 Requested SOP Class UID                       1.2.840.10008.1.20.1 (Storage Commitment Push Model SOP Class)
        (0000,0100)          2 Command Field                                 N-ACTION-RQ
        (0000,0110)          2 Message ID                                    9
        (0000,0800)          2 Data Set Type                                 0
        (0000,1001)         22 Requested SOP Instance UID                    1.2.840.10008.1.20.1.1 (Storage Commitment Push Model SOP Instance)
        (0000,0000)          2 Command Group Length                         
[Malformed Packet: DICOM]
    [Expert Info (Error/Malformed): Malformed Packet (Exception occurred)]
        [Message: Malformed Packet (Exception occurred)]
        [Severity level: Error]
        [Group: Malformed]

(network traffic was decoded by Wireshark which also found some elements suspicious).

In the receiver source code I found that it expects (0000,1008) Action Type ID in the request, and its value must be 1. The DIMSE-N specification (PS3.7 2013, Table 10.1-4) defines the tag as mandatory and the value of 1 is mentioned in PS3.4, Table J.3-1.

The second occurence of Group Length is obviously the missing tag which somehow was damaged. The actual dump of this tag is "0000 0000 02000000 0100"; length of 2 corresponds to the "US" VR, and even the value is already 1 as expected by the receiver.

[pacsone]

This is confirmed to be a bug in the Dicom Server component of PacsOne Server, where the ActionTypeID data element was initialized with the wrong (group, element) tag, i.e., (0000,0000) instead of (0000,1008). We'll fix this bug in the next release (6.4.5) of PacsOne Server, and thank you so much for reporting this bug.