PACS to PACS Data Transfer

[Michael Onken]

Hi Simon,

in the destination PACS configuration above you quoted:

==============================================
NetworkTCPPort = 11112
MaxPDUSize = 16384
MaxAssociations = 16
HostTable BEGIN
simon_pc = (SIMON_PC, HARTFORD, 12340) //this is PC where DcmSCU is running...
freeport_pc = (FREEPORT_PC, FREEPORT, 104) //this is PACS FROM PC
FSSDicomImagingCompany = simon_pc, freeport_pc
HostTable END
VendorTable BEGIN
"FSS CT Company" = FSSCTCompany
VendorTable END
AETable BEGIN
FSS_TO_STORE "tmp/database2" RW (100, 16384mb) FSSCTCompany
AETable END
==============================================

In the end the storage area FSS_TO_STORE is defined and you allow access to FSSCTCompany. However, SIMON_PC is only part of the vendor definition FSSDicomImagingCompany. Thus, correct the vendor identifier!

(For debugging, you can also try to put the SIMON_PC instead of FSSCTCompany directly into the FSS_TO_STORE, but I am not 100% sure that that configuration variant works)

Best,
Michael

[SIMONP]

Michael....

Just discovered your reply on the second page
Thank you very much by the way...
Vendor identifier is just a type: everything is configured correctly....
Now I am trying to simplify the scenario and send DICOM's from
dcmqrscp running on FREEPORT (this is hostname) and listening on port 104 , where SIMON_PC AETitle is referenced as
(SIMON_PC,HARTFORD,104)

to dcmqrscp on HARTFORD, which is listening on port 104.
in HARTFORD configuration FREEPORT is referenced as
(FREEPORT_PC, FREEPORT,104)

from DcmSCU (on HARTFORD) I create assosiation with FREEPORT (this works)
the send Move request specifying AETitle "SIMON_PC"
SIMON_PC should be referenced on HARTFORD configuration as well becuase
HARTFORD is a recipient (PACS-TO).
is it right ?
Also is it allowed to run several DCMQRSP on the same Network listening on the same port ?
I don't think why not bu I can be wrong....
I thought that with your help I understand more, but I am starting getting lost

Thanks for your help.
Always look forward to hearing from you

Simon

[Michael Onken]

Hi,

I got lost too

HARTFORD is sending the C-MOVE request (DcmSCU) to FREEPORT, port 104, (dcmqrscp) which should send the images to HARTFORD where a second dcmqrscp is listening on port 104.

In one of your previous setups you already were able to receive storage request at the final receiver PACS (Here: HARDFORD), which have been rejected with error "Called AE Title unknown". So that unknown AE Title is missing in the configuration of HARTFORD's dcmqrscp.

dcmqrscp on HARTFORD, btw, does not need to know anything about the DcmSCU host or AE Titles, it just listens to FREEPORT's dcmqrscp.

If you like send your dcmqrscp configuration files and your DcmSCU code to onken at open-connections de and I'll have a look as time permits.

Best,
Michael

[SIMONP]

Michael,

thanks for your offer.
Just sent you an email...

Looking forward to hearing from you

SImon

[SIMONP]

Michael...

Did you have a chance to look at configs + client code I emailed to you ?
I've got to make it working by Monday...
Thanks in advance

Simon

[Michael Onken]

(This has been resolved via email, inconsistent dcmqrscp configurations)