Once an ISCL connection has been established, the client and the server are ready to start transferring messages and data. The data transferred may be secured or unsecured. To send unsecured messages, the user should use the L_DicomSendNonSecureISCL function.
Use the L_DicomSetMaxMessageLengthISCL function to set the maximum message length that can be processed.
For information about confidentiality and data integrity associated with sending secured messages, refer to Adding Security to a DICOM Connection.
Since encryption modes, message authentication codes, authorization data and message length must all match between a sender and a receiver, occasionally, a sender will send a message that is not received properly by the receiver. When this happens, the receiver, not the sender, can get information about the problems that caused the failure. LEADTOOLS provides the following functions to help the user locate the cause of the problem:
L_DicomGetPeerRequestedMessageLengthISCL
In addition, when errors occur, the L_DicomGetErrorSecure and L_DicomGetStatusISCL can be used to help determine the location of the problem.
Help Collections
Raster .NET | C API | C++ Class Library | HTML5 JavaScript
Document .NET | C API | C++ Class Library | HTML5 JavaScript
Medical .NET | C API | C++ Class Library | HTML5 JavaScript
Medical Web Viewer .NET
Multimedia
Direct Show .NET | C API | Filters
Media Foundation .NET | C API | Transforms
Supported Platforms
.NET, Java, Android, and iOS/macOS Assemblies
Imaging, Medical, and Document
C API/C++ Class Libraries
Imaging, Medical, and Document
HTML5 JavaScript Libraries
Imaging, Medical, and Document