findscu fetch image problem

[uril]

Hi Users,

Thank you for help!!!

I installed dcmtk-3.5.4 on the client that located on the same local area as Conquest server. On the server I created the next Line

BAYCREST 172.18.0.98 50082 un

Now I am getting error both on findscu and movescu.

./findscu -v -d --study -k 0008,0052=STUDY -k 0010,0010="LastName^FirstName" -k 0010,0030=19290301 -k 0010,0020 -k 0020,000D 172.24.1.24 50082
Request Parameters:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: FINDSCU
Called Application Name: ANY-SCP
Responding Application Name: resp AP Title
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 0
Presentation Contexts:
Context ID: 1 (Proposed)
Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Requesting Association
findscu: Association Request Failed:
0006:031b Failed to establish association
0006:0317 Peer aborted Association (or never connected)
0006:031c TCP Initialization Error: Operation timed out


./movescu -v -d --move BAYCREST +P 50082 --study -k 0008,0052=SERIES -k 0010,0020=1350922 -k 0020,000D=1.2.124.113532.205.210.25.75.20071016.132506.3272648 -k 0020,000E=2.16.840.1.113662.4.1961541835284.1192557890.166720156771448 172.24.1.24 50082
Request Parameters:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: MOVESCU
Called Application Name: ANY-SCP
Responding Application Name: resp AP Title
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 0
Presentation Contexts:
Context ID: 1 (Proposed)
Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit
Context ID: 3 (Proposed)
Abstract Syntax: =MOVEStudyRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Requesting Association
movescu: Association Request Failed:
0006:031b Failed to establish association
0006:0317 Peer aborted Association (or never connected)
0006:031c TCP Initialization Error: Operation timed out

Any hint?

And I didn't get any error message on conquest server usually located on serverstatus.log

Thanks,

Uril.

[uril]

Hi Users,

Thank you very much!!!
You were right!!! Firewall on my linux client machime has been installed by default. I have turned it off and now can fetch images from the server. Finally it is working. I have another question. My DCMTK client installed on the directory /home/uril/DICOM/bin and I would like to fetch images to the /home/uril/image. Can I fetch to the different directory by one command movescy? If yes , what should I add to the client DCMT program movescu.


Thank you.

Uril.

[Michael Onken]

Hi,

there is no option for that. You may call movescu from another directory to accomplish that.

Regards,
Michael

[uril]

Hi Users,

I have installed DCMTK on FreeBSD and tried some test to fetch images from Conquest Pacs server. It is acting the same way how was acting linux client. Last time, how you told me I turn off firewall on linux and problem was solved. But on FreeBSD it seems to me that firewall is off. After running comand movescu I went to the PACS server and got the next error:

Called Application Title : "ANY-SCP "
Wed Sep 10 17:43:12 2008 Application Context : "1.2.840.10008.3.1.1.1"
Wed Sep 10 17:43:12 2008 Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.1"
Wed Sep 10 17:43:12 2008 Presentation Context 1 "1.2.840.10008.5.1.4.1.2.2.2"
Wed Sep 10 17:43:12 2008 C-Move Destination: "ROTMAN1 "
Wed Sep 10 17:43:12 2008 Number of Images to send: 27
Wed Sep 10 17:43:12 2008 Host 'ROTMAN1' did not accept the connection
Wed Sep 10 17:43:12 2008 C-Move (StudyRoot)
Wed Sep 10 17:43:12 2008 UPACS THREAD 488: ENDED AT: Wed Sep 10 17:43:12 2008
Wed Sep 10 17:43:12 2008 UPACS THREAD 488: TOTAL RUNNING TIME: 0 SECONDS

Thank you for help!!!

Uril.

[Michael Onken]

Hi,

Wed Sep 10 17:43:12 2008 Host 'ROTMAN1' did not accept the connection

The server tried to send to AETitle ROTMAN1 but the host did not accept the connection - that is a very clear error message.

Check whether ROTMAN1 is configured with IP adress and port at the PACS and be sure that at this IP address and port someone listens.

Regards,
Michael

[uril]

Hi Michael,

Pacs server has been configured with Rotman1 ip address and port number.
My client is FreeBSD 5.3-RELEASE. How to check if someone listens to specific IP address and port? Do you mean on client side?

Thanks,

Uril.

[uril]

Hi Michael,

I have the same problem with the new fedora 7 Dicom client. I have installed wireshark on fedora 7. I got the next strange message from wireshark :


No. Time Source Destination Protocol Info
728 4.666883 172.24.11.174 172.24.1.24 DCM DCM Data[Packet size limited during capture]

Frame 728 (78 bytes on wire, 78 bytes captured)
Ethernet II, Src: Xensourc_22:19:1e (00:16:3e:22:19:1e), Dst: TyanComp_05:c3:d1 (00:e0:81:05:c3:d1)
Internet Protocol, Src: 172.24.11.174 (172.24.11.174), Dst: 172.24.1.24 (172.24.1.24)
Transmission Control Protocol, Src Port: 39113 (39113), Dst Port: 50082 (50082), Seq: 374, Ack: 228, Len: 12
DICOM
[Packet size limited during capture: dicom truncated]

No. Time Source Destination Protocol Info
729 4.666900 172.24.11.174 172.24.1.24 DCM DCM Continuation[Unreassembled Packet [incorrect TCP checksum]]

Frame 729 (166 bytes on wire, 166 bytes captured)
Ethernet II, Src: Xensourc_22:19:1e (00:16:3e:22:19:1e), Dst: TyanComp_05:c3:d1 (00:e0:81:05:c3:d1)
Internet Protocol, Src: 172.24.11.174 (172.24.11.174), Dst: 172.24.1.24 (172.24.1.24)
Transmission Control Protocol, Src Port: 39113 (39113), Dst Port: 50082 (50082), Seq: 386, Ack: 228, Len: 100
DICOM
[Unreassembled Packet [incorrect TCP checksum]: dicom]


Thank you,

Uril.

[Michael Onken]

Hi Michael,

Pacs server has been configured with Rotman1 ip address and port number.
My client is FreeBSD 5.3-RELEASE. How to check if someone listens to specific IP address and port? Do you mean on client side?

Thanks,

Uril.

Yes, on client side, be sure to use the +P parameter for specifying an incoming port for movescu.

Regards,
Michael

[uril]

Hi Michael,

I am using the same command on two different clents: URI which is fedora 6 and TON is fedora 7. On both clients I turned of firewall. On fedora 6 I can fetch images and on fefora 7 I can't.

./movescu -v -d --move URI +P 50082 --study -k 0008,0052=SERIES -k 0010,0020=1350922 -k 0020,000D=2.16.840.1.113662.4.1961541835284.1191349291.388510345264450 -k 0020,000E=2.16.840.1.113662.4.1961541835284.1191350119.390990377848662 172.24.1.24 50082

./movescu -v -d --move TON +P 50082 --study -k 0008,0052=SERIES -k 0010,0020=1350922 -k 0020,000D=2.16.840.1.113662.4.1961541835284.1191349291.388510345264450 -k 0020,000E=2.16.840.1.113662.4.1961541835284.1191350119.390990377848662 172.24.1.24 50082

I have the next two associated lines in the PACS configuration file:

URI 172.24.11.85 50082 un
TON 172.24.11.174 50082 un

Any clue?

Thank you,

Uril.

[uril]

Hi Michael,

I am analyzing two reports from the command movescu and first difference that I found :

fedora 6 (working)

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0008,0052) CS [SERIES] # 6, 1 QueryRetrieveLevel
(0010,0020) LO [1350922] # 8, 1 PatientID
(0020,000d) UI [2.16.840.1.113662.4.1961541835284.1191349291.388510345264450] # 60, 1 StudyInstanceUID
(0020,000e) UI [2.16.840.1.113662.4.1961541835284.1191350119.390990377848662] # 60, 1 SeriesInstanceUID
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0000,0000) UL 0 # 4, 1 CommandGroupLength
(0000,0002) UI =MOVEStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 33 # 2, 1 CommandField
(0000,0110) US 1 # 2, 1 MessageID
(0000,0600) AE [URI] # 4, 1 MoveDestination
(0000,0700) US 0 # 2, 1 Priority
(0000,0800) US 1 # 2, 1 DataSetType
DIMSE sendDcmDataset: sending 100 bytes
DIMSE sendDcmDataset: sending 166 bytes
PDU Type: Associate Request, PDU Length: 217 + 6 bytes PDU header
01 00 00 00 00 d9 00 01 00 00 55 52 49 20 20 20
20 20 20 20 20 20 20 20 20 20 41 44 49 6c 61 62
5f 70 61 63 73 20 20 20 20 20 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
31 2e 31 20 00 00 36 a9 00 00 00 30 00 00 19 31
2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 35 2e 31
2e 34 2e 31 2e 31 2e 34 40 00 00 11 31 2e 32 2e
38 34 30 2e 31 30 30 30 38 2e 31 2e 32 50 00 00
3e 51 00 00 04 00 00 40 00 52 00 00 22 31 2e 32
2e 38 32 36 2e 30 2e 31 2e 33 36 38 30 30 34 33
2e 32 2e 31 33 35 2e 31 30 36 36 2e 31 30 31 55
00 00 0c 31 2e 34 2e 31 33 2f 4f 54 48 45 52
Constructing Associate AC PDU
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (180 bytes), presID=169
DIMSE Command Received:


fedora 7 (not working)

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0008,0052) CS [SERIES] # 6, 1 QueryRetrieveLevel
(0010,0020) LO [1350922] # 8, 1 PatientID
(0020,000d) UI [2.16.840.1.113662.4.1961541835284.1191349291.388510345264450] # 60, 1 StudyInstanceUID
(0020,000e) UI [2.16.840.1.113662.4.1961541835284.1191350119.390990377848662] # 60, 1 SeriesInstanceUID
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0000,0000) UL 0 # 4, 1 CommandGroupLength
(0000,0002) UI =MOVEStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 33 # 2, 1 CommandField
(0000,0110) US 1 # 2, 1 MessageID
(0000,0600) AE [TON] # 4, 1 MoveDestination
(0000,0700) US 0 # 2, 1 Priority
(0000,0800) US 1 # 2, 1 DataSetType
DIMSE sendDcmDataset: sending 100 bytes
DIMSE sendDcmDataset: sending 166 bytes
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (128 bytes), presID=3
DIMSE Command Received:

Any clue?

Thanks,

Uril.

[uril]

Hi Michael,

Actually, I don't need movescu. I now PatientID, StudyInstanceUID and SeriesInstanceUID from findscu. With these parameters I can go to the PACS server and get DICOM files.
Using MAGDevice0 field from dicom.ini I can get dicom directory.

Using command rsync host MAGDevice0/PatientID/StudyInstanceUID/SeriesInstanceUID/* to source directory I can get all series dicom files.

Is it right?

Thank you for your help!!!

Uril.

[Michael Onken]

Hi,

you cannot use findscu for downloading DICOM files. You can only use findscu for querying, ie see which DICOM files are on the PACS server.

Regards,
Michael