Hello!
This is my first post and since I'm also pretty much a DICOM newbie I hope you will be gentle with me. Thank you!
Ok, I am trying to store DICOM RT files on a server running a MINT (Medical Imaging Network Transport) service.
I have successfully achieved this for imaging data using storescu using a command line such as
storescu.exe -aec "VG3SCP" --scan-directories "servername.local.acme.com" 3002 "C:\directory\of\dicom\files\to\upload"
And then I can access the data/metadata through the MINT API.
I would like to do the same for DICOM RT files. Unfortunately when I do this I get the following error messages.
“E: No presentation context: (RE) 1.2.840.10008.5.1.4.1.1.481.3”
“E: Store SCU Failed: 0006:0208 DIMSE No valid Presentation Context ID”
Now that UID corresponds to the RTStructureSetStorage SOP Class.
I have tried to explicitly add the storescu.cfg file to the command line with the Default profile - which as far as I understand includes a presentation context for that SOP class, but I get the same problem.
I have been told that DICOM RT can be pushed to this server - using another tool, which I don't have access to.
Does anyone have any hints as to where I might be going wrong?
Thanks,
Paul
Storing DICOM RT Data
Moderator: Moderator Team
-
- DCMTK Developer
- Posts: 2506
- Joined: Tue, 2011-05-03, 14:38
- Location: Oldenburg, Germany
- Contact:
Re: Storing DICOM RT Data
You should check which Presentation Contexts are actually proposed by storescu and which of them are accepted by the storage SCP. On the SCU side, you could use option "+v" in addition to "-v" to see this information.
Btw, you might also be interested in dcmsend, which is much easier to use when sending a whole bunch of DICOM files to a remote peer.
Btw, you might also be interested in dcmsend, which is much easier to use when sending a whole bunch of DICOM files to a remote peer.
-
- DCMTK Developer
- Posts: 2506
- Joined: Tue, 2011-05-03, 14:38
- Location: Oldenburg, Germany
- Contact:
Re: Storing DICOM RT Data
Btw, where is the modality shortcut "RE" coming from? That's not the one I would have expected (rather "RS" instead).
Which version of the DCMTK are you using?
Which version of the DCMTK are you using?
-
- Posts: 5
- Joined: Fri, 2014-06-13, 11:01
Re: Storing DICOM RT Data
Thanks for the info.
I'm using version 3.6.0, and my apologies about the RE short cut it is in fact RS.
Using those flags I get the following for the RT classes - I don't know if that helps.
I: Context ID: 229 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTBeamsTreatmentRecordStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 231 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTBrachyTreatmentRecordStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 233 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTDoseStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 235 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTPlanStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 237 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTStructureSetStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 239 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTTreatmentSummaryRecordStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I'll certainly take a look at dcmsend.
I'm using version 3.6.0, and my apologies about the RE short cut it is in fact RS.
Using those flags I get the following for the RT classes - I don't know if that helps.
I: Context ID: 229 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTBeamsTreatmentRecordStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 231 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTBrachyTreatmentRecordStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 233 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTDoseStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 235 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTPlanStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 237 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTStructureSetStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Context ID: 239 (Abstract Syntax Not Supported)
I: Abstract Syntax: =RTTreatmentSummaryRecordStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I'll certainly take a look at dcmsend.
-
- DCMTK Developer
- Posts: 2506
- Joined: Tue, 2011-05-03, 14:38
- Location: Oldenburg, Germany
- Contact:
Re: Storing DICOM RT Data
Yes, it helps. The SCP does not accept your proposed SOP Classes - so it's not the the SCU's fault
-
- Posts: 5
- Joined: Fri, 2014-06-13, 11:01
Re: Storing DICOM RT Data
Yes, pretty much what I suspected. I shall dig further at the other end.
Thanks for your help.
Thanks for your help.
Who is online
Users browsing this forum: Semrush [Bot] and 1 guest