A DICOM Network handle.
Presentation ID. The presentation ID provides information about both the class type of the data and the transfer syntax to use when transferring the data.
Message ID. Each message sent by a member of a connection should have a unique ID. Since a member of a connection may send several messages, this ID allows that member to identify when a specific request has been completed.
Class affected by the request. This will be an SOP Class or an SOP MetaClass.
The status of the original request. For a list of possible values, refer to Status Constants.
Void pointer that you can use to access a variable or structure containing data that your callback function needs. This gives you a way to receive data indirectly from the function that uses this callback function.
Keep in mind that this is a void pointer, which must be cast to the appropriate data type within your callback function.
A call to this function is generated on a peer member of a connection when L_DicomSendCEchoResponse is called.
To use this callback function, RECEIVECECHORESPONSECALLBACK must be set using L_DicomSetCallback.
Required DLLs and Libraries
static HWND hList; /* handle to list box */
L_VOID EXT_CALLBACK OnReceiveCEchoResponse (HDICOMNET hNet, L_UCHAR nPresentationID, L_UINT16 nMessageID, L_TCHAR *pszClass, L_UINT16 nStatus, L_VOID *pUserData)
ListBox_AddString(hList, TEXT("Command Set - C-ECHO-RESPONSE"));
wsprintf(szMsg, TEXT(" Presentation ID: %d"), nPresentationID);
wsprintf(szMsg, TEXT(" Message ID: %d"), nMessageID);
wsprintf(szMsg, TEXT(" Affected SOP Class: %s"), pszClass);
wsprintf(szMsg, TEXT(" Status: %d"), nStatus);
Medical Web Viewer .NET
.NET, Java, Android, and iOS/macOS Assemblies
C API/C++ Class Libraries