echoscu configuration file?

[bnoeafk]

<tl; dr>
Where's the default config file that echoscu uses?


Hello all,
Hopefully an easy one to answer, but I just can't seem to find exactly what I'm looking for! I understand that various config files (storescu.cfg, dcmqrscp.cfg) are used to control transfer syntaxes, presentation contexts and those can be loaded at run time. However I can't seem to find the file that echoscu uses, by default.

Permit me to explain in full. I run echoscu -d -ppc 128 -aet LOCALAET -aec REMOTEAET ip.ad.dr.ess PortNumber and I get a ton of information back.

Diagnosing the request (using 223 as an example):

Code: Select all

      D:   Context ID:        223 (Proposed)
      D:     Abstract Syntax: =VerificationSOPClass
      D:     Proposed SCP/SCU Role: Default
      D:     Proposed Transfer Syntax(es):
      D:       =LittleEndianImplicit

I appear to get the accepted response:

Code: Select all

      D:   Context ID:        223 (Accepted)
      D:     Abstract Syntax: =VerificationSOPClass
      D:     Proposed SCP/SCU Role: Default
      D:     Accepted SCP/SCU Role: Default
      D:     Accepted Transfer Syntax: =LittleEndianImplicit

But what I'm after is, without specifying a config file, how do I know which Context ID# 223 is? I'm sure it's listed in a file somewhere that echoscu is using, but it's location isn't listed (unlike the general DICOM data dictionary, which is: D: DcmDataDictionary: Loading file: /usr/local/share/dcmtk-3.6.8/dicom.dic)

[J. Riesmeier]

The echoscu command line tool does not allow for specifying the list of proposed Presentation Contexts. Instead, when you use option -pts the list of Presentation Contexts is created from the hard-coded list of Transfer Syntaxes that can be found in the source file echoscu.cc starting with line 67.
As you use option -ppc with the maximum value of 128 but not option -pts, echoscu proposes 128 times the same Presentation Context: the Verification SOP Class with Implicit VR Little Endian Transfer Syntax

[Marco Eichelberg]

The -ppc option allows you to build very large A-ASSOCIATE-RQ packets for debugging purposes, i.e. for checking whether an association acceptor is able to handle such large packets. Other than that, negotiating more than one presentation context and any specific transfer syntax makes no sense for the Verification SOP Class, since the C-ECHO messages use no dataset (i.e. the negotiated transfer syntax does not matter, it is not used anyway).