←Select platform

ClientPortUsageType Enumeration


Specifies if a DICOM Client (SCU) will use secure DICOM TLS communication when an SCP reconnects to the client.

public enum ClientPortUsageType 
   enum class ClientPortUsageType sealed 
0NoneNot specified.
1UnsecureClient (SCU) expects SCP to reconnect unsecurely.
2SecureClient (SCU) expects SCP to reconnect securely.
3SameAsServerClient (SCU) expects SCP to reconnect securely only if the SCU initially connected to the SCP securely. Otherwise, the client (SCU) expects SCP to reconnect unsecurely.

When a DICOM Client (SCU) retrieves a DICOM instance using the C-MOVE operation, the server (SCP) reconnects to the client and stores instances to the SCU using C-STORE operations. This involves two DICOM connections: the initial connection from the SCU to the SCP, and then a second connection from the SCP back to the SCU. In the second connection, the client (SCU) acts as a server, listening for connections.

Each of the two connections can be unsecure, or secure. This enumeration is used to specify if the second connection will be secure or unsecure.

This enumeration is useful for specifying DICOM security when configuring a DICOM client to communicate with an SCP. To see how this is used, view the configuration settings of the LEAD DICOM demos below.(for example, run DicomHighlevelClientDemo_Original.exe and click the Options button)


For example usage of the ClientPortUsageType, see any of the following demos:

  • DicomHighlevelClientDemo_Original.exe
  • MedicalWorkstationMainDemo_Original.exe
  • StorageServerManagerDemo_Original.exe

Target Platforms

Help Version 23.0.2024.2.29
Products | Support | Contact Us | Intellectual Property Notices
© 1991-2024 LEAD Technologies, Inc. All Rights Reserved.

Leadtools.Dicom Assembly