DICOM @ OFFIS

it is very strange that SCU generates dynamic SOPClassUID :) 9.1.1.1.4 Affected SOP instance UID For the request/indication, this parameter specifies the SOP Instance to be stored. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equa...

# storescu --help | grep max -pdu --max-pdu [n]umber of bytes: integer (4096..131072) set max receive pdu to n bytes (default: 16384) --max-send-pdu [n]umber of bytes: integer (4096..131072) restrict max send pdu to n bytes # storescp --help | grep max -pdu --max-pdu [n]umber of bytes: integer (4096...

just to remember one ticket for dcmnet, i am not sure if you fixed it (i really think it is a bug)

viewtopic.php?t=2159

no, nothing special for dcmnet. the application is built on base dcmtk/ofstd libs, so, as i can remember I changed mutexes initialization to allow "recursive" mode, it is important in some applications. think it is better to add "be recursive" as option for OFMutex but, it is oka...

seems you are trying to dump image stored as DICOM Implicit VR. In this case dcmtk can get VR only from own private dictionary (if you built dcmtk with this option).

try to use DICOM Explicit VR syntax to store objects from Leadtools and dcmdump it again.

per developers it is not thread safe because of gethostbyname/gethostbyaddr but, it is easy to change to getaddrinfo.

i have good experience with dcmnet in big multithread application.

ahh sorry forgot about secure transport connection patch: new lines is started with "+" file dcmtls/libsrc/tlstrans.cc DcmTLSConnection::~DcmTLSConnection() { + close(); if (tlsConnection) SSL_free(tlsConnection); } void DcmTLSConnection::close() { + if (getSocket()>=0) { if (tlsConnection...

latest snapshot (dcmtk-3.5.5_20090818) look for several calls : destroyAssociationKey(association); in some bad conditions DUL_RequestAssociation (and may be other routines) calls destroyAssociationKey and it freeing connection by if (*key && (*key)->connection) delete (*key)->connection; BU...

agree, i decided to replace RT with valid VR from the dcmtk dictionary or, if tag can't be detected, reject object.

thank you very much!

latest from snapshots...

it is just request, not a bug report. some CTN based devices send RT VR and RT was okay for the CTN but not for dcmtk and it skips that object (or even can fail if we'll enable dcmAcceptUnexpectedImplicitEncoding and gods will send bytes of destiny after RT

sent...

thanks! btw RT is almost "standard" VR from list of strange VRs sent from old modalities but i even don't want to scary you

just small patch for reagTagAndLength if someone is interesting: /* read 2 bytes */ inStream.read(vrstr, 2); /* create a corresponding DcmVR object */ DcmVR vr(vrstr); /* fix for malincrodt ctn 'RT' VR */ if (*vrstr == 'R' && *(vrstr+1) == 'T') { vr.setVR(newTag.getVR().getValidEVR()); strnc...

or even better convert it to UN on fly in the readTagAndLength

some of old (based on malincrodt ctn etc) modalities still sends objects with "RT" value representation. that caused fail in DcmItem::readTagAndLength and, possible, crash or memory exhausted exception.

add RT if it possible and i think we need to interpretate it as UN.

use set of dcmtk tools: dcmmodify, dcm2XXX and XXX2dcm to create any desired object and send it by storescu.