[BitBucket user: Денис Смирнов]
[BitBucket date: 2018-02-14.07:25:52]

When making a C-MOVE request SCU produces two dicom packets: C-MOVE-RQ and C-MOVE-RQ-DATA. With "-k MessageID=xxx" argument you change MessageID only in C-MOVE-RQ-DATA packet but not in C-MOVE-RQ.

```
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 -k MessageID=666
```
```
DICOM, C-MOVE-RQ ID=1
    PDU Type 0x4 (Data)
    PDU Length: 110
    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
DICOM, C-MOVE-RQ-DATA
    PDU Type 0x4 (Data)
    PDU Length: 68
    PDV, C-MOVE-RQ-DATA
        PDV Length: 64
        Context: 0x03 (Explicit VR Little Endian, Study Root Query/Retrieve Information Model - MOVE)
        Flags: 0x02 (Data, Last Fragment)
        (0000,0110)          2 Message ID                                    [US] 666
        (0008,0052)          6 Query/Retrieve Level                          [CS] STUDY 
        (0020,000d)         30 Study Instance UID                            [UI] 1.2.276.0.54.2017.12.17.404800
```
In an example above you can see MessageID = 1 in C-MOVE-RQ and MessageID=666 in C-MOVE-RQ-DATA. According to [NEMA](http://dicom.nema.org/dicom/2013/output/chtml/part07/chapter_E.html) (0000,1031) 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". So from my point of view (and from the point of view Philips technical support) Orthanc should return  Originator Message ID from C-MOVE-RQ and it shouldn't be zero.

P.S. I can't make c-move from Philips' Portal to Orthanc because of this DICOM discrepancy...