[BitBucket user: Sébastien Jodogne]
[BitBucket date: 2018-01-10.15:19:05]

Hello, if I configure Orthanc 1.3.1 with the following configuration:

```
  "DicomModalities" : {
    "movescu" : [ "MOVESCU", "127.0.0.1", 11112 ],
    "target" : [ "BREWERY", "127.0.0.1", 2000 ]
  }
```

Then, if I start a sample C-Store server as follows:

```
$ storescp 2000 -d -aet BREWERY
```

And if I trigger a C-Move as follows (note the **MessageID=10** argument):

```
$ movescu -v -S -aec ORTHANC -aet MOVESCU -aem BREWERY --port 11112 -od . localhost 4242 -k QueryRetrieveLevel=INSTANCE -k SOPInstanceUID=1.3.12.2.1107.5.2.33.37097.2012041613043195815872177 -k MessageID=10
```

Then, I observe the following log in the C-Store server:

```
: ===================== INCOMING DIMSE MESSAGE ====================
D: Message Type                  : C-STORE RQ
D: Presentation Context ID       : 85
D: Message ID                    : 1
D: Affected SOP Class UID        : MRImageStorage
D: Affected SOP Instance UID     : 1.3.12.2.1107.5.2.33.37097.2012041613043195815872177
D: Data Set                      : present
D: Priority                      : medium
D: Move Originator AE Title      : MOVESCU
D: Move Originator ID            : 10
D: ======================= END DIMSE MESSAGE =======================
```

The "Move Originator ID" value thus seems properly set. The "0" you observe comes from the fact that Orthanc assumes "0" if the tag "MessageID" is not available.

I am however unsure of whether this is the proper way of handling "Move Originator ID". If you have any reference to better match with the DICOM standard, this would be extremely useful.