Movescu - no A-RELEASE sent

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
Cyril_S
Posts: 4
Joined: Tue, 2017-11-07, 16:24

Movescu - no A-RELEASE sent

#1 Post by Cyril_S »

Hi everybody,

I try to perform some query retrieve against a PACS (brand of PACS is Medidok) with movescu and everything works well... Except that after having received the last C-MOVE-RSP containing a 0x00 status, movescu does not send the A-RELEASE message.

In order to debug, I tried to perform some query retrieve against the HOROS app and everything works. Thus, I started to analyze the network traffic from both Q/R sequences and got following lead:

- MediDOK C-MOVE-RSP does not provide 0000,1021 (Number of Completed Sub-operations), 0000,1022 (Number of Failed Sub-operations) and 0000,1023 Number of Warning Sub-operations).

Is it possible that movescu needs these fields to release the association ?

Best regards,

Cyril

EDIT:

In trace log level, the last output I get before a 180sec freeze is following:
T: Read PDU HEAD TCP: 05 00 00 00 00 04
T: Read PDU HEAD TCP: type: 05, length: 4 (04)
T: DUL FSM Table: State: 6 Event: 11
T: DUL Event: A-RELEASE-RQ PDU (on transport)
T: DUL Action: AR 2 Indicate Release
T: DUL FSM Table: State: 8 Event: 13
T: DUL Event: A-RELEASE response primitive
T: DUL Action: AR 4 Send Release RP
Does it mean that the Association release request is sent and we're waiting the A_RELEASE_RSP from the PACS ?

J. Riesmeier
DCMTK Developer
Posts: 2501
Joined: Tue, 2011-05-03, 14:38
Location: Oldenburg, Germany
Contact:

Re: Movescu - no A-RELEASE sent

#2 Post by J. Riesmeier »

The state transitions can be found in part 8 of the DICOM standard: http://dicom.nema.org/medical/dicom/cur ... 9.2.3.html

What is the debug/trace output before and after the lines you've cited.

Cyril_S
Posts: 4
Joined: Tue, 2017-11-07, 16:24

Re: Movescu - no A-RELEASE sent

#3 Post by Cyril_S »

Sorry, I forgot to subscribe to the topic and have therefore not been notified of your response...

Thank you for your help. If I understand right, the transitions sequence I quoted is following:
- Being in state 6, I get an event 11, which is synonym of AR 2 and A-RELEASE-RQ PDU
- This moves the state machine to state 8 -> Association release group
- I send an event 13, which is synonym of AR 4 and A-RELEASE response primitive
- This moves the state machine to state 13 -> Wait for Tp Close

This means that the freeze I get after this is because the peer should close the transport (and send me an AR-5 message)?

Sadly, I no longer have access to the PACS to perform more queries... But I can say that nothing comes after the lines.

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot], Google [Bot] and 1 guest