Thank you for the quick reply.
I'll try to contact the PACS brand and see if it's a known issue on their side.
Search found 4 matches
- Tue, 2019-01-22, 13:26
- Forum: DCMTK - General
- Topic: Movescu 65536 remaining suboperations
- Replies: 2
- Views: 1601
- Mon, 2019-01-21, 15:58
- Forum: DCMTK - General
- Topic: Movescu 65536 remaining suboperations
- Replies: 2
- Views: 1601
Movescu 65536 remaining suboperations
Hello, By querying some PACS, the move operation works well for a study containing about 700 files. The number of completed suboperations is correct but the number of remaining suboperations is very large (starting at 65536, and decreasing as it should). I use the movescu command line tool, version ...
- Wed, 2018-01-24, 14:14
- Forum: DCMTK - General
- Topic: Movescu - no A-RELEASE sent
- Replies: 2
- Views: 2639
Re: Movescu - no A-RELEASE sent
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 sta...
- Wed, 2017-11-08, 11:45
- Forum: DCMTK - General
- Topic: Movescu - no A-RELEASE sent
- Replies: 2
- Views: 2639
Movescu - no A-RELEASE sent
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 so...