dcm4che image import settings for Afga CR30X (NX software)

[Cahir King]

Hello.  Sorry to repeat this message, but I still haven't got to the bottom of how to configure DCM4CHE to accept dicom images from an Afga CR machine running Afga's NX software.

I have setup the dmc4chee to act as a PACs server on a local network.

The Afga machine is connected to the same IP range as the NX machine using a network card.  It also has a second network card on a different IP range (192.192.192.192) which enables it to communicate with the CR30-X developer.

I can both TCP/IP and dicom ping from the nx software to the dcm4chee server.

But I cannot send images.

Our service engineer was in today, and he reckons that there is a setting in the dcm4chee server that I haven't got quite right to enable it to accept images.

Can anyone tell me - do I need to add the Afga NX machine as an "AE Title" in the dcm4chee server, and if so, are there any other settings I need to be aware of?

Thanks.

[Damien Evans]

If you have AcceptedAETitles set to ANY (the default) in the StoreSCP service then you shouldn't have to do anything else.  If you have it set to CONFIGURED_AETS then you'll have to add it as an AE in the UI.  

Are you getting any specific errors when you try to send studies in?  Can you attach snippet of your server.log file from the time period when you attempt to send data from the AGFA device?

 -- Damien

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/groups/opt_out.

[Cahir King]

Thanks for replying Damien.

Have attached the server.log file from earlier today.  Sorry it is long, but I don't really know whaat I'm looking for.

Where can I find the StoreSCP service?  I couldn't locate in the web3 interface.  Is it in the JBOSS console?

Thank you.

cahir

[Wa]

Hello from the log, it looks like the association request is being rejected.

2013-09-05 14:12:51,459 INFO  NX_DEFAULTNX->DCM4CHEE (TCPServer-1) [org.dcm4cheri.net.FsmImpl] received AAssociateRQ
    appCtxName:    1.2.840.10008.3.1.1.1/DICOM Application Context Name
    implClass:    1.3.51.0.1.3
    implVersion:    AGFA DTF1.0.95
    calledAET:    DCM4CHEE
    callingAET:    NX_DEFAULTNX
    maxPDULen:    65542
    asyncOpsWindow:   
    pc-1:    as=1.2.840.10008.1.1/Verification SOP Class
        ts=1.2.840.10008.1.2/Implicit VR Little Endian
2013-09-05 14:12:51,477 INFO  NX_DEFAULTNX->DCM4CHEE (TCPServer-1) [org.dcm4cheri.net.FsmImpl] sending A-ASSOCIATE-RJ
    result=1 - rejected-permanent
    source=2 - service-provider (ACSE)
    reason=1 - no-reason-given
2013-09-05 14:12:51,527 INFO  NX_DEFAULTNX->DCM4CHEE (TCPServer-1) [org.dcm4cheri.net.FsmImpl] closing connection - Socket[addr=/192.168.11.26,port=56999,localport=11112]
2013-09-05 14:12:51,528 INFO  -> (TCPServer-1) [org.dcm4cheri.server.ServerImpl] finished - Socket[addr=/192.168.11.26,port=56999,localport=11112]


I see you also tried to dicom echo from the dcm4chee to NX_DEFAULTNX and that failed because it looks like the CR did not have DCM4CHEE AE title in its list of SCU which it wouldn't since the CR is not an SCP.

2013-09-05 14:09:23,227 INFO  -> (http-0.0.0.0-8080-3) [org.dcm4che2.net.PDUEncoder] NX_DEFAULTNX(3): A-ASSOCIATE-RQ NX_DEFAULTNX << DCM4CHEE
2013-09-05 14:09:23,229 INFO  -> (EchoService-3) [org.dcm4che2.net.Association] NX_DEFAULTNX(3) >> org.dcm4che2.net.pdu.AAssociateRJ: A-ASSOCIATE-RJ[result=1, source=1, reason=3]: permanent calling-AE-title-not-recognized
2013-09-05 14:09:23,230 ERROR -> (http-0.0.0.0-8080-3) [org.dcm4chee.web.service.echo.EchoService] Echo dicom://NX_DEF...@192.168.11.26:104 failed
org.dcm4che2.net.pdu.AAssociateRJ: A-ASSOCIATE-RJ[result=1, source=1, reason=3]: permanent calling-AE-title-not-recognized
    at org.dcm4che2.net.PDUDecoder.nextPDU(PDUDecoder.java:186)
    at org.dcm4che2.net.Association.run(Association.java:859)
    at java.lang.Thread.run(Thread.java:679)
2013-09-05 14:09:23,245 INFO  -> (EchoService-3) [org.dcm4che2.net.Association] NX_DEFAULTNX(3): close Socket[addr=/192.168.11.26,port=104,localport=56415]

So check the service=storeSCP, it is in the jmx-console under dcm4chee.archive near the bottom. Although I am not sure this is your problem

[Cahir King]

Thanks for your reply.

I found the store=SCP settings in the jmx-console.

I set the "called AE titles" and "calling AE titles" to "ANY"

I also set the "accept storage of images without patient ID or name" to "true".

Will test later today.  You are correct - the dicom ping from the dcm4chee server to the nx machine failed.

Cahir.

[Cahir King]

Update - changing the SCP settings did not work either.

Now the dicom ping from the Afga CR30X to dcm4che fails to.  Has anyone got this to work successfully?  If so does anyone have a beginner tip?

Thanks.

[Wa]

Leave the CalledAE Title as DCM4CHEE and upload another log file. Are you hosting DCM4CHEE on a Window server?