DICOM @ OFFIS

If you really want to use TLS based security, read the OpenSSL documentation. The topic is too complicated to explain everything to you in this forum. A seed file is just a file containing random information and is used in OpenSSL to initialize the status of the pseudo random generator (PRNG). If yo...

No, something like this is not supported in DICOMscope. The main reason for this is that we have another tool named DCMPRINT that implements a DICOM print server for PostScript printers, i.e. the "core" component of a typical DICOM paperprint server. This tool is not available for free, ho...

All of that can be done with OpenSSL, documentation should be plenty on the internet. DCMTK contains a perl script dcmtls/tests/dcmtk_ca.pl that allows to easily set-up a certification authority and create key pairs (private keys and certificates), but only for RSA keys, not for DH. As long as you w...

It is a common misconception that meta-data could be unimportant. In DICOM, meta-data is never unimportant because you need to fill in certain sets of attributes to make a DICOM object valid, and creating invalid object is the source of all evil, or at least of many problems in the DICOM field. In y...

To respond to your questions, There is no function that would automatically delete images received or remove the pixel data. Harddisks are cheap these days :wink: DICOM images contain unique identifiers identifying the study, series and instance they belong to. The database in DICOMscope will not al...

Re 1: Yes. Re 2: You cannot switch this sound off. The sound is played whenever DICOMscope discoveres that some other process (i.e. the DICOM receiver, dcmpsrcv) has modified the index.dat file of the underlying image database. The problem you describe has not been reported before, and sounds like a...

The Print SCP is also active by default, accepting associations on port 10005 and 10006 (with different configurations, see DICOMscope.cfg for details). There is no MPPS in DICOMscope.

That depends on the SOP class you choose and on the properties of the image. Bite the bullet and consult part 3 of the DICOM standard, which is the only definitive reference.

There is nothing to configure. After a default installation of DICOMscope you should be able to send images to the machine on which DICOMscope is installed, port 10004. The Storage SCP ignores the application entity title so there is nothing to configure either. Use a Verification SCU (echoscu) to c...

Not in DCMTK.

Yes of course. Look at dcmdjpeg.cc to learn how to do this with DCMTK.

It works for me, so you must be doing something wrong
Command line correct? storescp -xf storescp.cfg default <port>

You can use either DcmItem::getElement() or DcmItem::nextObject() for this purpose. See dcmdata/include/dcitem.h for declaration, parameters etc.

DICOMDIRs don't contain pixel data. Actually a few "variants" (application profiles) do, but those are only icon images. If you want to build a volume dataset, you have to do that from the image files referenced in the DICOMDIR.

No. DICOM does not support that. As a recipient you neither know how many images (or messages) will be sent, nor how large each image or message is.