Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid A-ASSOCIATE RQ on retrieve/export to C-STORE SCP with configured Restricted Transfer Capabilities #2324

Closed
gunterze opened this issue Dec 17, 2019 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@gunterze
Copy link
Member

gunterze commented Dec 17, 2019

If none of the SOP Classes of requested objects is provided by the C-STORE SCP by its configured Transfer Capabilities, an Association to the C-STORE SCP is still established, sending an A-ASSOCIATE RQ

09:05:50,020 DEBUG - A-ASSOCIATE-RQ[
  calledAET: STORESCP
  callingAET: DCM4CHEE
  applicationContext: 1.2.840.10008.3.1.1.1 - DICOM Application Context Name
  implClassUID: 1.2.40.0.13.1.3
  implVersionName: dcm4che-5.20.0
  maxPDULength: 16378
  maxOpsInvoked/maxOpsPerformed: 0/0
]

without any Presentation Context Item, which is invalid according DICOM PS 3.8:

This variable field shall contain the following items: one Application Context Item, one or more Presentation Context Items and one User Information Item.

Replace Archive Device or Archive Network AE attribute:

Name Type Description (LDAP Attribute)
Restrict Retrieve According Transfer Capabilities string Indicates if the set of requested objects to retrieve shall be restricted according the Transfer Capabilities of the Retrieve Destination. Enumerated values: NO, YES, CONFIGURATION (= consider configured Transfer Capabilities of the Destination AE, but treat a non accepted Presentation Context as failure). If absent, CONFIGURATION will be applied. (dcmRestrictRetrieveAccordingTransferCapabilities)

by

Name Type Description (LDAP Attribute)
Restrict Retrieve Silently boolean Indicates if the set of requested objects to retrieve shall be silently (=without counting not transferred object as failures) restricted according the Transfer Capabilities of the Retrieve Destination. Otherwise the number of requested objects for which no Transfer Capability is configured for the Retrieve Destination and therefore are not retrieved is counted as failures. Only effective, if the Retrieve Destination has configured at least one Transfer Capability with SCP role. (dcmRestrictRetrieveSilently)

Related #1836, #2178, #2304
Requires dcm4che/dcm4che#601

@gunterze gunterze added the bug Something isn't working label Dec 17, 2019
@gunterze gunterze added this to the 5.20.0 milestone Dec 17, 2019
@gunterze gunterze self-assigned this Dec 17, 2019
gunterze added a commit to dcm4che/dcm4chee-arc-cs that referenced this issue Dec 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant