RTPlan send for Halcyon from eclipse is aborting

General
1

Hey guys,
I am using using Orthanc 1.10.1 for storing patient DICOM from TPS. I got into an issue that when I send RTplan.dicom for Halcyon machine to orthanc directly from Eclipse TPS v17, .
TransferSyntaxUID has little Endian explicit: 1.2.840.10008.1.2.1

I used Dicomtoolkit ( to simulate the issue with more verbose) to transfer the data, CTs, Doses, Structure files go through with no issue. Only the RTPlans causes a crash and the error I see is:
E: No presentation context found for sending C-STORE with SOP Class / Transfer Syntax: 1.2.246.352.70.1.70 / Little Endian Explicit
F: cannot sent SOP instance: DIMSE No valid Presentation Context ID
I: Aborting Association

Can you please tell me what am I doing wrong here?
Thanks

2

Hi Umar,

I have seen some issues in Orthanc when trying to perform this kind of mixed transfers of a CT whose Transfer Syntax is 1.2.246.352.70.1.70 and a RTPlan/RTStruct/SEG files that can actually not be transferred with the same Transfer Syntax since they can not be compressed.

The workaround was to transfer the CT and these files in 2 different DICOM connections.

HTH,

Alain

3

Hi Alain,
Thank you for your reply. I have tried to send only RTplan and RTdose files, I got the following error:
C:\Users\Admin\Desktop\Dicom Test Kit (1)\Dicom Test Kit>dcmsend --verbose --call “ORTHANC” localhost 4242 --scan-directories TB01
I: determining input files …
I: checking input files …
I: starting association #1
I: initializing network …
I: negotiating network association …
I: Requesting Association
I: Association Accepted (Max Send PDV: 16372)
I: sending SOP instances …
I: Sending C-STORE Request (MsgID 1, RD)
I: Received C-STORE Response (Success)
E: No presentation context found for sending C-STORE with SOP Class / Transfer Syntax: 1.2.246.352.70.1.70 / Little Endian Explicit
F: cannot send SOP instance: DIMSE No valid Presentation Context ID
I: Aborting Association

And, when I try to send only RTplan file I get this error:
C:\Users\Admin\Desktop\Dicom Test Kit (1)\Dicom Test Kit>dcmsend --verbose --call “ORTHANC” localhost 4242 --scan-directories TB01
I: determining input files …
I: checking input files …
I: starting association #1
I: initializing network …
I: negotiating network association …
I: Requesting Association
E: No Acceptable Presentation Contexts
E: cannot negotiate network association: No acceptable Presentation Contexts
I: Releasing Association
I:
I: Status Summary
I: --------------
I: Number of associations : 1
I: Number of pres. contexts : 1
I: Number of SOP instances : 1
I: - NOT sent to the peer : 1
I: * no acceptable pres. : 1

The workaround did not work so far.
Anything else I can try?

4

Could you share your files (possibly anonymized) ?

Alain

5

Hi,
Thank you Alain for the response. Unfortunately, as a new user I cannot attach a file here. I try to send it to you via some other means.
regards

6

Hi Umar,

I have received your file; thanks !

The file SOP Class UID is 1.2.246.352.70.1.70 which is a “private” SOP Class UID that is not recognized neither by Orthanc nor by Dicomtoolkit.

For Orthanc you should set the UnknownSopClassAccepted configuration to true. For Dicomtoolkit, I don’t know but this page explains how to do it for DCMTK - storescu.

HTH,

Alain

7

Hi Alain, This worked!
thank you very much for your help
mfg
Umar