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:
Does it mean that the Association release request is sent and we're waiting the A_RELEASE_RSP from the PACS ?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