Forwarding dicom files
Moderator: Moderator Team
Forwarding dicom files
Hello all,
I would like to foward some dicom studies located in a folder to a viewing station.
I wonder is “storescu” the correct sample app that can allow me to specify the AE title, IP address and port number?
If this is the correct sample app, how to specify the IP address to the destination AE Title?
Thanks in advance.
Regards,
John
I would like to foward some dicom studies located in a folder to a viewing station.
I wonder is “storescu” the correct sample app that can allow me to specify the AE title, IP address and port number?
If this is the correct sample app, how to specify the IP address to the destination AE Title?
Thanks in advance.
Regards,
John
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
Did you check the documentation of storescu?
Jorg,
I did check the documentation.
First things first: Was I correct in assuming storescu is the sample app I am looking for?
Second: In the doc for storescu, the usage is
storescu [options] peer port dcmfile...
Suppose the viewing station has this info
AE-Title: ABCDEFG
AE Name: Viewing station
Port #: 404
IP Address: 192.0.0.1
The input argument would be
storescu -ace ABCDEFG "Viewing station" 404 sampledicom.dcm
No IP address in the above command line because there are about 45 options available, but I cannot see which option pertains to the destination IP address. Any suggestion?
Regards,
John
I did check the documentation.
First things first: Was I correct in assuming storescu is the sample app I am looking for?
Second: In the doc for storescu, the usage is
storescu [options] peer port dcmfile...
Suppose the viewing station has this info
AE-Title: ABCDEFG
AE Name: Viewing station
Port #: 404
IP Address: 192.0.0.1
The input argument would be
storescu -ace ABCDEFG "Viewing station" 404 sampledicom.dcm
No IP address in the above command line because there are about 45 options available, but I cannot see which option pertains to the destination IP address. Any suggestion?
Regards,
John
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
Yes, the storescu seems to be the appropriate tool for your purposes.
I don't know what you mean by "AE Name" but this information is not relevant for the DICOM communication. Of course, Instead of the hostname you can also use the IP address of the peer -- so it's the second parameter when calling storescu:
I don't know what you mean by "AE Name" but this information is not relevant for the DICOM communication. Of course, Instead of the hostname you can also use the IP address of the peer -- so it's the second parameter when calling storescu:
Code: Select all
PARAMETERS
peer hostname of DICOM peer
port tcp/ip port number of peer
dcmfile_in DICOM file(s) to be transmitted
Hello Jorg,
Thanks for the info.
Sorry about the confusion. AE Name is just the description of the AE (application entity) Title. It is an entry for just about every modality equipment to describe a bit more about the machine.
I misunderstood what storescu document meant about "peer", I thought it want me to enter the description of the modality.
Please correct me if I am wrong. Using the above senario, the correct entry at the command line will be
storescu -ace ABCDEFG 192.0.0.1 404 sampledicom.dcm
Is this correct?
Regards,
John
Thanks for the info.
Sorry about the confusion. AE Name is just the description of the AE (application entity) Title. It is an entry for just about every modality equipment to describe a bit more about the machine.
I misunderstood what storescu document meant about "peer", I thought it want me to enter the description of the modality.
Please correct me if I am wrong. Using the above senario, the correct entry at the command line will be
storescu -ace ABCDEFG 192.0.0.1 404 sampledicom.dcm
Is this correct?
Regards,
John
Hello,
Encountered some problems using storescu. Testing storescu usage with Digital Jacket. Both Offis project and Digital Jacket app reside in the same desktop.
In the command line, I used
storescu.exe 192.x.x.x 104 somedicom.dcm
where 192.x.x.x is the IP address for Digital Jacket; 104 is the port number for this app
The result was
storescu: Association Rejected:
Result: Rejected Permanent, Source: Service User
Reason: Called AE Title Not Recognized
Alternatively, I tried this
storescu.exe -aec DIGITAL_JACKET 192.x.x.x 104 somedicom.dcm
The result was
storescu: No representation context for: (DPm) 1.2.840.10008.5.1.4.1.1.1.2.1
storescu: SCU Failed:
0006:0208 DIMSE No valid Presentation Context ID
The above UID is pointed to the Media Storage SOP class UID for tag (0002,0002). But I do no understand what does it mean by no representation context.
Just a note: In the firewall, I have opened a tunnel for the above ip address.
Does it mean that Digital Jacket is not able to receive the association request or the above command line usage were wrong?
Thanks in advance.
Encountered some problems using storescu. Testing storescu usage with Digital Jacket. Both Offis project and Digital Jacket app reside in the same desktop.
In the command line, I used
storescu.exe 192.x.x.x 104 somedicom.dcm
where 192.x.x.x is the IP address for Digital Jacket; 104 is the port number for this app
The result was
storescu: Association Rejected:
Result: Rejected Permanent, Source: Service User
Reason: Called AE Title Not Recognized
Alternatively, I tried this
storescu.exe -aec DIGITAL_JACKET 192.x.x.x 104 somedicom.dcm
The result was
storescu: No representation context for: (DPm) 1.2.840.10008.5.1.4.1.1.1.2.1
storescu: SCU Failed:
0006:0208 DIMSE No valid Presentation Context ID
The above UID is pointed to the Media Storage SOP class UID for tag (0002,0002). But I do no understand what does it mean by no representation context.
Just a note: In the firewall, I have opened a tunnel for the above ip address.
Does it mean that Digital Jacket is not able to receive the association request or the above command line usage were wrong?
Thanks in advance.
-
- DCMTK Developer
- Posts: 2072
- Joined: Fri, 2004-11-05, 13:47
- Location: Oldenburg, Germany
- Contact:
Hi,
that means that you try to send some images and/or compression variants that the server does not support.
What kind of images you like to send? (SOP Class + Transfer Syntax)?
Be sure storescu proposes Presentation Contexts for that. You get a list of proposed (and accepted) contexts when running storescu with log level DEBUG, i.e. calling it with options -v -d.
Best regards,
Michael
that means that you try to send some images and/or compression variants that the server does not support.
What kind of images you like to send? (SOP Class + Transfer Syntax)?
Be sure storescu proposes Presentation Contexts for that. You get a list of proposed (and accepted) contexts when running storescu with log level DEBUG, i.e. calling it with options -v -d.
Best regards,
Michael
Hello Mike,
The SOP Class UID is 1.2.840.10008.5.1.4.1.1.1.2.1 which is Digital Mammography X-ray for processing
The transfer syntax UID is 1.2.840.10008.1.2.1 which is Explicit VR Little Endian
I installed KPacs and I was able to forward the file to KPacs using storescu sample app. So I interpreted that as a problem with Digital Jacket. Which was a possibility you suggested.
However, I was able to import the above MG study into someone's Digital Jacket. I tried to export the file from this Digital Jacket back to the Digital Jacket on my desktop and it was successful.
As a control test, I also send the same file to someone's Digital Jacket using storescu sample app. This time, the program executed with no error. However, the Digital Jacket never receive anything in the inbox.
Do you think this is a problem with Digital Jacket? or it is something else? Ultimately, I want to send files within a folder to a viewing station on the network using storescu sample app. I want to identify what the limitations and problems associated with storescu are.
Thanks in advance.
Regards,
John
The SOP Class UID is 1.2.840.10008.5.1.4.1.1.1.2.1 which is Digital Mammography X-ray for processing
The transfer syntax UID is 1.2.840.10008.1.2.1 which is Explicit VR Little Endian
I installed KPacs and I was able to forward the file to KPacs using storescu sample app. So I interpreted that as a problem with Digital Jacket. Which was a possibility you suggested.
However, I was able to import the above MG study into someone's Digital Jacket. I tried to export the file from this Digital Jacket back to the Digital Jacket on my desktop and it was successful.
As a control test, I also send the same file to someone's Digital Jacket using storescu sample app. This time, the program executed with no error. However, the Digital Jacket never receive anything in the inbox.
Do you think this is a problem with Digital Jacket? or it is something else? Ultimately, I want to send files within a folder to a viewing station on the network using storescu sample app. I want to identify what the limitations and problems associated with storescu are.
Thanks in advance.
Regards,
John
-
- DCMTK Developer
- Posts: 2072
- Joined: Fri, 2004-11-05, 13:47
- Location: Oldenburg, Germany
- Contact:
Hi John,
basically storescu should be able to store any images to any PACS if the PACS works correctly. So there might be a problem with Digital Jacket. However, this may only be a problem of the association negotiation between both which is a configuration issue. Without seeing the details of the association negotiation, I cannot tell you, unfortunately.
Best regards,
Michael
basically storescu should be able to store any images to any PACS if the PACS works correctly. So there might be a problem with Digital Jacket. However, this may only be a problem of the association negotiation between both which is a configuration issue. Without seeing the details of the association negotiation, I cannot tell you, unfortunately.
Best regards,
Michael
Who is online
Users browsing this forum: Ahrefs [Bot], Bing [Bot], Google [Bot] and 0 guests