Reject study from non-configured AET / Source

139 views
Skip to first unread message

nutun

unread,
Jan 7, 2020, 3:29:52 AM1/7/20
to dcm4che
Hi,

I have deployed dcm4chee-arc-psql:5.20.0-secure (dockerized). I did not added / configured any modality, workstation and remote server in devices / AE list of dcm4chee but whenever any data sent from any of the modality, workstation or remote server, dcm4chee accepts and archives the data.

Where as I want dcm4chee to accept and archive data only from that sources which are configured / added in devices / AE list of dcm4chee. If AET of any modality, workstation or server is not configured in dcm4chee it should reject by default data archival from that any sending AET.

Need guideline in this.

Gunter Zeilinger

unread,
Jan 7, 2020, 4:11:24 AM1/7/20
to dcm...@googlegroups.com
https://dcm4chee-arc-cs.readthedocs.io/en/latest/networking/config/dcmNetworkAE.html#dcmacceptedcallingaetitle

Adding external AEs by the UI provides an option to implicitly add the new AE Title to the  Accepted Calling AE titles of the Archive (Storage) AE.Screenshot from 2020-01-07 10-10-27.png


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
--
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.

nutun

unread,
Jan 8, 2020, 2:25:58 AM1/8/20
to dcm4che
Thank you Gunterze for your response. It helped me a lot. I want to discuss another scenario.

Let me explain what I want to do:

I have my PACS (dcm4chee-arc-psql:5.20.0-secure - dockerized). There are some modalities and workstations configured with PACS. All modalities can send data to PACS and all workstations can send data to PACS & can receive data from PACS as well (two way communication between PACS and workstations).

1. By applying configuration suggested by you, only AETs of modalities and workstations which are configured as Accepted Calling AE Title to the selected AET can communicate with PACS. And PACS is rejecting all other AETs either it is configured in PACS AE list or not.

2. I have also configured Validate Calling AE Hostname as True at dcm4chee-arc device level (Screenshot attached). As a result of this setting any AET which is not configured in PACS AE list can not communicate with PACS.

3. Now my requirement is as follow:

3.1 - Only those modalities which are configured with PACS / added in PACS AE list should allow to send data to PACS.
3.2 - Only those workstation can receive data from PACS which are configured with PACS / added in PACS AE list and these workstations should not allow to send data to PACS. I need one way communication between PACS and workstation. i.e only data retrieval from PACS to workstation.
3.3 - Any modality or workstation which is not configured with PACS / added in PACS AE list should not allowed to communicate with PACS.




On Tuesday, January 7, 2020 at 2:11:24 PM UTC+5, gunterze wrote:
https://dcm4chee-arc-cs.readthedocs.io/en/latest/networking/config/dcmNetworkAE.html#dcmacceptedcallingaetitle

Adding external AEs by the UI provides an option to implicitly add the new AE Title to the  Accepted Calling AE titles of the Archive (Storage) AE.Screenshot from 2020-01-07 10-10-27.png


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, January 7, 2020 9:29 AM, nutun <nutun...@gmail.com> wrote:

Hi,

I have deployed dcm4chee-arc-psql:5.20.0-secure (dockerized). I did not added / configured any modality, workstation and remote server in devices / AE list of dcm4chee but whenever any data sent from any of the modality, workstation or remote server, dcm4chee accepts and archives the data.

Where as I want dcm4chee to accept and archive data only from that sources which are configured / added in devices / AE list of dcm4chee. If AET of any modality, workstation or server is not configured in dcm4chee it should reject by default data archival from that any sending AET.

Need guideline in this.


--
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 dcm...@googlegroups.com.
Validate Calling AE.JPG

Gunter Zeilinger

unread,
Jan 8, 2020, 3:34:55 AM1/8/20
to dcm...@googlegroups.com
Configure (at least) two different Archive AEs used by modalities and workstation:

First contains AETs of modalities in its list of Accepted Calling AE Title, and provides Transfer Capabilities for all Storage SOP Classes provided by the modalities as SCP.

Second contains AETs of modalities in its list of Accepted Calling AE Title and only provides Transfer Capabilities necessary for Query/Retrieve SOP Classes as SCP and Storage SOP Classes as SCU - but not as SCP.  You may also configure to restrict C-MOVE Destinations to a configurable list of AE Titles for that Archive AE.

By default configuration, only Archive AE "DCM4CHE" provides Transfer Capabilities for Storage SOP Classes as SCP, all other Archive AEs only provides Transfer Capabilities for Query/Retrieve SOP Classes as SCP and Storage SOP Classes as SCU. But they also varies in its configured Query/Retrieve View ID, which would not the case in your setting.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

Reply all
Reply to author
Forward
0 new messages