PrintSCU is there dicom conformace? (Real World communication is failing)

Regards,

We have long time ago implemented PrintSCU class for communication with DICOM Printers, and everything was working flawlessly until few days ago.
Some new company of SW Virtual Printer that is using High Resolution Paper Printer is failing to communicate and connection timeouts.
They have said we are incorrectly sending N-ACTION command while we are unable to reply to this remark since our implementation pretty much looks like your example at following page:
- https://www.leadtools.com/help/leadtools/v19/dh/di/dicomprintscu-associate(string,int,string,string,dicomprintscuprintmanagementclassflags).html

Remark from theirs dev team: "My colleague from the development department said that it could help to do the N-ACTION command on the filmbox instead of the filmsession."

We would like to know is there anything we could do to change/fix this behavior without resulting to low level communication?
We could do low level, but it will require time to properly test all scenarios and we are tide with time since all this is happening at some client site.
Best would be if we could "stimulate" this communication to proceed normally for this N-ACTION that was sent to early - problem is that I do not know when is sent since this is High Level class?

Or at least to provide us with some Real World Activities so we could examine does comply to dicom standard or not, or what actually is happening behind the scenes.

Please notice this printer code is working on the top of LT version 17.0

thank you for your support
best regards.

Hello,

Before we can answer your question regarding if there's anything you can change to fix this, we must first understand exactly what the problem is here.

You've noted that the SCU is failing to communicate and timing out. Are these two different things or one in the same? Is the SCU failing to connect or associate at times and also timing out due to the printer SCP failing to receive an N-ACTION command that it is expecting?

In regards to figuring out what is happening here, are you overriding any of the OnStatus(), OnPrinterReport() or OnPrintJobReport() methods which would provide more information on what's happening internally with the communication?

Does the printer SCP have a communication log that can be referred to?

You also bring up conformance statements. LEADTOOLS does not provide any conformance statements for any of our demos or high-level classes as we cannot be sure how they will be used or in what mannor they will be used. Conformance statements are designed to indicate exactly what will be supported by the application, what services will be provided, etc. Since we are a tool provider and do not dictate this, it does not make much sense for us to provide these type of documents. However, if the printer SCP provides a conformance statement, this could help us better understand what it wants.