ClientPortUsageType Enumeration

Summary

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

Syntax

C++/CLI

[SerializableAttribute()] 
public enum ClientPortUsageType

public: 
   [SerializableAttribute] 
   enum class ClientPortUsageType sealed

Members

Value	Member	Description
0	None	Not specified.
1	Unsecure	Client (SCU) expects SCP to reconnect unsecurely.
2	Secure	Client (SCU) expects SCP to reconnect securely.
3	SameAsServer	Client (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

Reference

Leadtools.Dicom Namespace

Leadtools.Dicom.AddIn.Common.AeInfo.ClientPortUsage

Download our FREE evaluation

Help Version 23.0.2024.8.20

Leadtools.Dicom Assembly

Introduction

Getting Started

Namespaces

Leadtools.Dicom Namespace

Assemblies