Package: dcmtk Version: 3.6.1~20121102-3 Severity: wishlist For some reason the FSM seems to be incomplete in a dcmqrscp handling of C-ECHO.
Steps: $ dcmqrscp --log-level trace -c dcmqrscp.cfg >& out.log [from another shell] $ echoscu --log-level trace --call BLA --aetitle FOO localhost 5678 Then upon inspection: $ grep FSM out.log T: DUL FSM Table: State: 1 Event: 4 T: DUL FSM Table: State: 2 Event: 5 T: DUL FSM Table: State: 3 Event: 6 T: DUL FSM Table: State: 6 Event: 9 T: DUL FSM Table: State: 6 Event: 8 T: DUL FSM Table: State: 6 Event: 11 T: DUL FSM Table: State: 8 Event: 13 technically echoscu should have closed the Transport connection, and thus a step is missing: T: DUL FSM Table: State: 13 Event: 16 -> Action AR5 Which makes sure the SCP goes back to Idle state (Sta1). I guess this is an issue in the logger, rather than the implementation, since dcmqrscp seems to handle multiple association gracefully -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
