I use DicomScope as print SCP, which communicate with my application.
In association:
Accepted Presentation Contexts:
BasicGrayscalePrintManagementMetaSOPClass
PresentationLUTSOPClass
Abstract Syntax Not Supported:
PrintJobSOPClass
BasicColorPrintManagementMetaSOPClass
The result is:
1. Association can be built btween my App and DcmScope.
2. But when my app issue N-GET-RQ and DcmScope response N-GET-RSP, the
error occured:
Attribute Identifier List : (2110,0030) (0008,0070)
(0018,1020) are not supported.
3. Association Aborted.
So I'm afraid that it can not be used for my App.
And DcmScope only support (2110,0010) (2110,0020) by its CS?
Used as print SCP?
Moderator: Moderator Team
-
- OFFIS DICOM Team
- Posts: 1445
- Joined: Tue, 2004-11-02, 17:22
- Location: Oldenburg, Germany
- Contact:
These are optional attributes that an SCP may or may not support. DICOMscope does not. If the SCU aborts the association because of the N-GET-RSP, then this is a protocol violation on the side of the SCU.Attribute Identifier List : (2110,0030) (0008,0070) (0018,1020) are not supported.
In that case your "App" does not correctly implement the DICOM Print Management Service Class. That said, many SCUs are not 100% correct, and the SCP component in DICOMscope has deliberately been developed to be very strict - within IHE (Integrating the Healthcare Enterprise) it is used as a test tool to check DICOM print implementations.So I'm afraid that it can not be used for my App.
Correct.And DcmScope only support (2110,0010) (2110,0020) by its CS?
Who is online
Users browsing this forum: No registered users and 1 guest