StorageSCP, how to accept Unrecognized SOPClasses?

283 views
Skip to first unread message

Kevin Hahn

unread,
Apr 15, 2014, 3:30:10 PM4/15/14
to pynet...@googlegroups.com
Hello,

I'm trying to migrate to using pynetdicom; away from using dcmtk.  However, I am having trouble using pynetdicom as a Query/Retrieve SCU to receive DICOMS that have a Siemens private class (1.3.12.2.1107.5.9.1) as the SOP Class UID.

I am able to receive these files using dcmtk storescp with the "promiscuous" flag, which allows all presentation contexts not known to be Storage SOP Classes to be accepted. 

Is there a way to get similar "promiscuous" behavior with pynetdicom?

Thank you!

-Kevin

Patrice Munger

unread,
Apr 15, 2014, 7:35:38 PM4/15/14
to pynet...@googlegroups.com
Hi Kevin, 

There is no such thing as the "promiscuous" mode in pynetdicom (yet). Is it the query or the retrieve that fails? Do you get a stacktrace or just no response? Tell me more and I'll be happy to help you.

Regards,

Patrice


--
Vous recevez ce message, car vous êtes abonné au groupe Google Groupes "pynetdicom".
Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse pynetdicom+...@googlegroups.com.
Pour obtenir davantage d'options, consultez la page https://groups.google.com/d/optout.



--
Patrice Munger

Kevin Hahn

unread,
Apr 16, 2014, 7:50:29 PM4/16/14
to pynet...@googlegroups.com
Hi Patrice,

I wouldn't say that anything is "failing".  The C-MOVE gets a response with status 0xb000, "sub-operation complete - with one or more failures". I do not get a stack trace.  When I use dcmtk `movescu` to perform the C-MOVE, it gives an identical message.  

I can fix the problem for the specific SOP Class by adding it to SOPclass.py. 

I'm looking for a more flexible solution to be able to retrieve any DICOM, regardless of its SOP Class. I'm still trying to figure out how to do this...

Thanks again for all your help,
-kevin
Reply all
Reply to author
Forward
0 new messages