IPP/IPPS job delivery

ippPrinterConnectionTimeout

• Configurable globally in the management interface and can be overridden locally in the spooler.config file.
  

• Defined in seconds, the default value is 120 seconds.

• This property specifies the maximum time in seconds that the spooler waits for the socket to become available - the socket is used for data transfer. The socket becomes available once the TCP handshake (IPP and IPPS) or TLS handshake (IPPS) is completed. If the socket does not become available before this timeout expires, the job delivery will be terminated and the job will go to the "Printer Error" state. In the case of a batch print, all jobs from the same batch will immediately get the same status. This helps to prevent situations where the serious network packet loss or printer malfunction in the handshake phase leads to print job upload being stuck. If the printer is completely unavailable, this timeout is not utilized and the printing is terminated based on TCP/IP stack error detection mechanisms.

• Example: configure it in the management interface or locally: "ippPrinterConnectionTimeout":"120"

ippPrinterResponseTimeout

• Configurable globally in the management interface and can be overridden locally in the spooler.config file.
  

• Defined in seconds, the default value is 300 seconds.

• This property specifies the maximum time in seconds that the spooler waits for the MFD to respond to an IPP request or to confirm the job reception after upload. It applies to IPP as well to IPPS delivery backend. If the printer doesn't respond before this timeout, the job will be terminated and the job will go to the "Printer Error" state. In the case of a batch print, all jobs from the same batch will immediately get the same status. The timeout is reset with every new IPP request.

• Example: configure it in the management interface or locally: "ippPrinterResponseTimeout":"300"