dcmtk Movescp problems :(
Justin Burger
I'm trying to use the movescu function to retrieve images from an
EFilms :\ Dicom server. but when I send the command all i get is this
message:
./movescu -v -P -k '0010,0010=*' --call DEEP1 10.0.1.1 104
Requesting Association
Association Accepted (Max Send PDV: 16372)
================================
Sending query
Move SCU RQ: MsgID 1
Request:
# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0010,0010) PN [*] # 2, 1
PatientsName
C-Move RSP: MsgID: 1 [Status=Failed: UnableToProcess]
AffectedSOPClassUID: =MOVEPatientRootQueryRetrieveInformationModel
Data Set: Not Present
NumberOfRemainingSubOperations: 0
NumberOfCompletedSubOperations: 0
NumberOfFailedSubOperations: 0
NumberOfWarningSubOperations: 0
Status Detail:
# Dicom-Data-Set
# Used TransferSyntax: LittleEndianImplicit
(0000,0110) US 1 # 2, 1
MessageID
(0000,0700) US 0 # 2, 1
Priority
Releasing Association
And efilms que has an empty entry with '0' in the series and nothing
else.
I could not find ANY thing on how to use this function other then the
txt that comes with it, but there are no examples, can some one point
me in the right direction or give me a few tips, I would like to be
able to retrieve all dicoms from a certain date.. :)
Thanks in advance.
Justin Burger.
Joerg Riesmeier
> ../movescu -v -P -k '0010,0010=*' --call DEEP1 10.0.1.1 104
[...]
> I would like to be able to retrieve all dicoms from a certain date..
this is not a movescu issue but a question of the DICOM query/retrieve
model. Before retrieving particular SOP instances you need to query
them (e.g. using findscu from the DCMTK).
According to the DICOM standard the Move request must contain only unique
keys, and that for all levels up to the retrieve level. PS3.4-2003 states
in section C.4.2.2.1 (C-MOVE / Baseline Behavior of SCU):
"The SCU shall supply a single value in the Unique Key Attribute for each
level above the Query/Retrieve level. For the level of retrieve, the SCU
shall supply one unique key if the level of retrieve is above the STUDY
level and shall supply one UID, or a list of UIDs if a retrieval of several
items is desired and the retrieve level is STUDY, SERIES or [I]MAGE. The
SCU shall also supply a move destination. The move destination shall be the
DICOM Application Entity Title of a DICOM Application Entity capable of
serving as the SCP of the Storage Service Class."
Examples for the findscu and movescu tools are provided in the docs files.
Regards,
Joerg Riesmeier
OFFIS
Justin Burger
Joerg Riesmeier <ne...@riesmeier.de> wrote in message news:<b18d70$l...@news.Informatik.Uni-Oldenburg.DE>...
anilk...@mwebware.com
D:
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name: OFFIS_DCMTK_360
D: Their Implementation Class UID:
D: Their Implementation Version Name:
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: DicomListener
D: Called Application Name: KPServer
D: Responding Application Name: resp. AP Title
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 0
D: Presentation Contexts:
D: Context ID: 1 (Proposed)
D: Abstract Syntax: =FINDPatientRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianExplicit
D: =BigEndianExplicit
D: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: Constructing Associate RQ PDU
D: PDU Type: Associate Accept, PDU Length: 184 + 6 bytes PDU header
D: 02 00 00 00 00 b8 00 01 00 00 4b 50 53 65 72 76
D: 65 72 20 20 20 20 20 20 20 20 44 69 63 6f 6d 4c
D: 69 73 74 65 6e 65 72 20 20 20 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
D: 31 2e 31 21 00 00 19 01 00 03 00 40 00 00 11 31
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
D: 50 00 00 3a 51 00 00 04 00 00 40 00 52 00 00 1b
D: 31 2e 32 2e 32 37 36 2e 30 2e 37 32 33 30 30 31
D: 30 2e 33 2e 30 2e 33 2e 36 2e 30 55 00 00 0f 4f
D: 46 46 49 53 5f 44 43 4d 54 4b 5f 33 36 30
D: Parsing an A-ASSOCIATE PDU
D: Association Parameters Negotiated:
D: ====================== BEGIN A-ASSOCIATE-AC =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name: OFFIS_DCMTK_360
D: Their Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Their Implementation Version Name: OFFIS_DCMTK_360
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: DicomListener
D: Called Application Name: KPServer
D: Responding Application Name: KPServer
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 16384
D: Presentation Contexts:
D: Context ID: 1 (Abstract Syntax Not Supported)
D: Abstract Syntax: =FINDPatientRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-AC ======================
E: No Acceptable Presentation Contexts
E: 0006:0208 DIMSE No valid Presentation Context ID
Unable to retrieve Images from DicomServer.Above error is coming.
Jörg Riesmeier
> D: Context ID: 1 (Abstract Syntax Not Supported)
> D: Abstract Syntax: =FINDPatientRootQueryRetrieveInformationModel
> E: 0006:0208 DIMSE No valid Presentation Context ID
> Unable to retrieve Images from DicomServer.Above error is coming.
Regards,
Jörg