←Select platform

ClientPortUsageType Enumeration

Summary

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

Syntax
C#
VB
C++
[SerializableAttribute()] 
public enum ClientPortUsageType 
<SerializableAttribute()>  
Public Enum ClientPortUsageType 
public: 
   [SerializableAttribute] 
   enum class ClientPortUsageType sealed 
Members
ValueMemberDescription
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.
Remarks

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)

Example

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

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

Target Platforms

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

Leadtools.Dicom Assembly