Orthanc responses C-MOVE with zero Move Originator Message ID

When I make a simple C-Move request to Orthanc from a workstation Orthanc establishes back an association and makes C-Store responce with a zero Move Originator Message ID (0000, 1031) value. According to DICOM NEMA Move Originator Message ID contains the Message ID (0000,0110) of the C-MOVE-RQ Message from which this C-STORE sub-operation is being performed. But Orthanc always returns zero and it causes errors when user tries to view images directly from Orthanc in Philips Portal. Here is an example DICOM output

movescu -v -S -aec ORTHANC -aet BREWERY -aem BREWERY --port 11112 -od . pacs.viveya.local 4242 -k QueryRetrieveLevel=STUDY -k StudyInstanceUID=1.2.276.0.54.2017.12.17.404800

Workstation → Orthanc C-MOVE-RQ

PDV, C-MOVE-RQ ID=1
PDV Length: 106
Context: 0x03 (Explicit VR Little Endian, Study Root Query/Retrieve Information Model - MOVE)
Flags: 0x03 (Command, Last Fragment)
(0000,0000) 4 Command Group Length 92
(0000,0002) 28 Affected SOP Class UID 1.2.840.10008.5.1.4.1.2.2.2 (Study Root Query/Retrieve Information Model - MOVE)
(0000,0100) 2 Command Field C-MOVE-RQ
(0000,0110) 2 Message ID 1
(0000,0600) 8 Move Destination BREWERY
(0000,0700) 2 Priority 0
(0000,0800) 2 Data Set Type 1

Orthanc → Workstation C-STORE-RQ

PDV, C-STORE-RQ ID=1
PDV Length: 182
Context: 0x19 (Implicit VR Little Endian, Digital X-Ray Image Storage - For Presentation)
Flags: 0x03 (Command, Last Fragment)
(0000,0000) 4 Command Group Length 168
(0000,0002) 28 Affected SOP Class UID 1.2.840.10008.5.1.4.1.1.1.1 (Digital X-Ray Image Storage - For Presentation)
(0000,0100) 2 Command Field C-STORE-RQ
(0000,0110) 2 Message ID 1
(0000,0700) 2 Priority 0
(0000,0800) 2 Data Set Type 1
(0000,1000) 58 Affected SOP Instance UID 1.2.156.112536.2.560.172241223131065181.1246169967187.381
(0000,1030) 8 Move Originator Application Entity Title BREWERY
(0000,1031) 2 Move Originator Message ID 0

Hello,

Hello,

Thanks for advice. Opened an issue #66 on bitbucket.

Hello!

Can you be so kind to check issue 66 status on bitbucket? I added some arguments from NEMA about wrong implementation of Move Originator Message ID in Orthanc.

Of course, as soon as we have the human resources to do so.

For the moment, my personal development focus is set on the Stone of Orthanc, as we managed to gather financial support from the industry to extend this particular part of the free and open-source Orthanc ecosystem, to the benefit of the entire community.

As always, feel free to contribute if you want things to go faster:
http://book.orthanc-server.com/contributing.html

Regards,
Sébastien-