Hello,

I try to validate my DICOM implementation with DVT, I am facing the following problem:

I try to execute that scripts

RECEIVE ASSOCIATE-RQ (
PRESENTATION-CONTEXT-ITEMS
("Verification SOP Class",
"Explicit VR Little Endian",
"Implicit VR Little Endian")
)

SEND RELEASE-RQ

RECEIVE ABORT-RQ ( SOURCE 0 REASON 0 )

To simulate the transition betwen sta5-sta13 executing an AA-8 action regarding DICOM Standard Part 8 table 9-10.

From Dvt it seems working :

----------------------------------------------------
Received: A_ASSOCIATE_RQ Message
Protocol Version: 1
Called AE Title: SCP
Calling AE Title: SCU
Application Context: 1.2.840.10008.3.1.1.1
Presentation Context Item(s):
Presentation Context ID: ID: 1
> Abstract Syntax: 1.2.840.10008.1.1
> Transfer Syntax: 1.2.840.10008.1.2.1
> Transfer Syntax: 1.2.840.10008.1.2
User Information:
> Maximum Length: 132072
> Implementation Class UID: 123.456.789
> Implementation Version Name: Seb 0.1


VALIDATE ASSOCIATE-RQ
Validate: A_ASSOCIATE_RQ Message
Protocol Version: 1
Called AE Title: SCP
Calling AE Title: SCU
Application Context: 1.2.840.10008.3.1.1.1
Presentation Context Item(s):
Presentation Context: ID: 1
> Abstract Syntax: 1.2.840.10008.1.1(Verification SOP Class)
> Transfer Syntax: 1.2.840.10008.1.2.1 (Explicit VR Little Endian)
> Transfer Syntax: 1.2.840.10008.1.2 (Implicit VR Little Endian)
User Information:
> Maximum Length: 132072
> Implementation Class UID: 123.456.789
> Implementation Version Name: Seb 0.1


SEND RELEASE-RQ (09:45:34)

RECEIVE ABORT-RQ (09:45:34)
Error: TCP/IP - Socket read error (error code 10054)
Error: Can't read from TCP/IP socket - connection has been closed.
Error: DULP - trying to confirm transport.
Error: Failed to receive ABORT-RQ - as expected in DICOMScript.
Association open 139.56 seconds
----------------------------------------------------


I ran it with the network sniffer and obtain that log:


----------------------------------------------------
New : 146.254.103.90(4569)-146.254.103.109(104)
PDU logged to file 20061021_103017\0000_146.254.103.90(4569)-146.254.103.109(104)\PDUs\0_IN.pdu at 21.10.2006 10:37:14
146.254.103.90(4569)-146.254.103.109(104) Type 1 PDU : Length = 218 : Direction = OUT
Association Request
From SCP
To SCU
DICOM UID: 1.2.840.10008.3.1.1.1
Outer Type 20
Presentation Context 1
Type 30 : 1.2.840.10008.1.1
Type 40 : 1.2.840.10008.1.2.1
Type 40 : 1.2.840.10008.1.2
Outer Type 50
Max PDU : 132072
Type 52 : 123.456.789
Type 55 : Seb 0.1
End : 146.254.103.90(4569)-146.254.103.109(104)RST Seen (146.254.103.90(4569)-146.254.103.109(104))
RST Seen (146.254.103.90(4569)-146.254.103.109(104))
TCP Connection closed prematurely
----------------------------------------------------

The release request does not seems to be sent over the network. Is it possible to send wrong DICOM protocols from DVT ?

If yes is it also possible to have an API to send Unrecognized PDU ?

Cheers
Seb

Hi

Sorry I did not found the Bugs reporting forum....

The use case is the following (Inactivity Time out):
RECEIVE ASSOCIATE-RQ (
PRESENTATION-CONTEXT-ITEMS
("Verification SOP Class", "Explicit VR Little Endian")

)

SEND ASSOCIATE-AC (
PRESENTATION-CONTEXT-ITEMS
("Verification SOP Class", 0, "Explicit VR Little Endian" )
)

RECEIVE C-ECHO-RQ

DELAY 60

RECEIVE ABORT-RQ (
SOURCE 0
REASON 0
)

From the client point of view I send the abort RQ and just after I close the socket.

It seems that a decoupling is missing in Dvtk between Network and script validation. In my scenario dvt prints an error "TCP/IP error socket was closed ...". If I just wait 2s between Abort Request and Close Socket , it makes Dvtk happy :)


Thanks in advance for your feed back

Seb

PS: my version is Dvtk 2.1.4