C-GET SCU to Conquest SCP: No presentation context accepted for the SCP role

[wusiping333]

How does SCU use C-GET to receive dcm images from ConQuest DICOM server?
I tried to use getscu to receive dcm images, but failed.Here is the logging:

D: getscu.py v0.4.0
D: 
I: Requesting Association
D: Request Parameters:
D: ======================= OUTGOING A-ASSOCIATE-RQ PDU ========================
D: Our Implementation Class UID:      1.2.826.0.1.3680043.9.3811.1.5.6
D: Our Implementation Version Name:   PYNETDICOM_156
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    GETSCU          
D: Called Application Name:     ANY-SCP         
D: Our Max PDU Receive Size:    16382

D: Requested Extended Negotiation: None
D: Requested Common Extended Negotiation: None
D: Requested Asynchronous Operations Window Negotiation: None
D: Requested User Identity Negotiation: None
D: ========================== END A-ASSOCIATE-RQ PDU ==========================
D: Accept Parameters:
D: ======================= INCOMING A-ASSOCIATE-AC PDU ========================
D: Their Implementation Class UID:    1.2.826.0.1.3680043.2.135.1066.101
D: Their Implementation Version Name: 1.5.0/WIN32
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    GETSCU          
D: Called Application Name:     ANY-SCP         
D: Their Max PDU Receive Size:  32768

D: Accepted Extended Negotiation: None
D: Accepted Asynchronous Operations Window Negotiation: None
D: User Identity Negotiation Response: None
D: ========================== END A-ASSOCIATE-AC PDU ==========================
I: Association Accepted
I: Sending Get Request: MsgID 1
I: 
I: # Request Identifier
I: (0010,0010) PN [other]                                  # 1 PatientName
I: 
D: ========================== OUTGOING DIMSE MESSAGE ==========================
D: Message Type                  : C-GET RQ
D: Message ID                    : 1
D: Affected SOP Class UID        : Patient Root Query/Retrieve Information Model - GET
D: Identifier                    : Present
D: Priority                      : Low
D: ============================ END DIMSE MESSAGE =============================
D: pydicom.read_dataset() TransferSyntax="Little Endian Implicit"
I: Received Store Request
D: ========================== INCOMING DIMSE MESSAGE ==========================
D: Message Type                  : C-STORE RQ
D: Presentation Context ID       : 151
D: Message ID                    : 4037
D: Affected SOP Class UID        : Secondary Capture Image Storage
D: Affected SOP Instance UID     : 1.3.6.1.4.1.25403.44883564280220.2140.20210411100801.14
D: Move Originator               : GETSCU
D: Data Set                      : Present
D: Priority                      : Medium
D: ============================ END DIMSE MESSAGE =============================
E: No presentation context for 'Secondary Capture Image Storage' has been accepted by the peer for the SCP role
D: pydicom.read_dataset() TransferSyntax="Little Endian Implicit"
D: ========================== INCOMING DIMSE MESSAGE ==========================
D: Message Type                  : C-GET RSP
D: Presentation Context ID       : 1
D: Message ID Being Responded To : 1
D: Affected SOP Class UID        : Patient Root Query/Retrieve Information Model - GET
D: Remaining Sub-operations      : 0
D: Completed Sub-operations      : 0
D: Failed Sub-operations         : 1
D: Warning Sub-operations        : 0
D: Identifier                    : None
D: Status                        : 0xFE00
D: ============================ END DIMSE MESSAGE =============================
D: 
I: Get SCP Result: 0xFE00 (Cancel)
I: Sub-Operations Remaining: 0, Completed: 0, Failed: 1, Warning: 0
D: pydicom.read_dataset() TransferSyntax="Little Endian Implicit"
I: Releasing Association

[scaramallion]

Could you post the full log please?

[edmcdonagh]

It's a shame that converting to a discussion just has an abrupt "issue closed" message on the email notification.

[scaramallion]

Ah, I didn't realise that. Maybe I should just stick to leaving them as issues...

I really should add a set of QR tutorials...

[wusiping333]

I am so sorry to trouble you，and thank you very much!

…

---Original--- From: ***@***.***> Date: Sat, Apr 17, 2021 06:26 AM To: ***@***.***>; Cc: ***@***.******@***.***>; Subject: Re: [pydicom/pynetdicom] How does SCU use C-GET to receive dcm images from ConQuest DICOM server? (#605) Ah, I didn't realise that. Maybe I should just stick to leaving them as issues, but I do get a bit tired of answering the same old QR issues over and over and figured this might help. I really should add a set of QR tutorials... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[scaramallion]

Hey it's no trouble, I'm happy to help.

[scaramallion]

This seems to be similar to this issue, the problem likely lies with Conquest.

Since Conquest is sending the datasets anyway, you can override the negotiated context roles by adding the following on this line of the getscu app:

for cx in assoc.accepted_contexts:
    cx._as_scp = True