Printer SCU assocation rejected

[Jordan]

Hello,

I have a problem of rejected association when I try to send a dcm file to a dicom printer.

My scu log are :

01062017-100452: [0884] ***** Connection wanted  Thursday, June 01, 2017  at 10h04mn52s
[ASSOCIATION NEGOTIATION BEGIN]
    Calling AE Title    : PRINTOR
    Called AE Title     : PRINTSCP
    Responding AE Title : PS Print Server
    Application Context : StandardApplicationContext
01062017-100452: [0884] >> Calling AE Title is <PRINTOR>
01062017-100452: [0884]     Presentation Context 1 : BasicFilmSessionSOPClass
01062017-100452: [0884]       Transfer Syntax        : LittleEndianExplicit
01062017-100452: [0884]       Transfer Syntax        : LittleEndianImplicit
01062017-100452: [0884]     REJECTED - Abstract Syntax not Supported
01062017-100452: [0884]     Presentation Context 3 : BasicFilmBoxSOPClass
01062017-100452: [0884]       Transfer Syntax        : LittleEndianExplicit
01062017-100452: [0884]       Transfer Syntax        : LittleEndianImplicit
01062017-100452: [0884]     REJECTED - Abstract Syntax not Supported
01062017-100452: [0884]     Presentation Context 5 : BasicGrayscaleImageBoxSOPClass
01062017-100452: [0884]       Transfer Syntax        : LittleEndianExplicit
01062017-100452: [0884]       Transfer Syntax        : LittleEndianImplicit
01062017-100452: [0884]     REJECTED - Abstract Syntax not Supported
01062017-100452: [0884] >> Settings set used: <default>
  REJECTING ASSOCIATION - INAPPROPRIATE SET OF PRESENTATION CONTEXTS
[ASSOCIATION NEGOTIATION END]
01062017-100452: [0884] ***** Connection closed

I use fo dicom 3.0.2 with c#.

Can someone help me ?

Thank you !

[Anders Gustafsson Cureos AB]

Hi Jordan,

can you please send an example log from when using version 2 or earlier?

Regards,

Anders @ Cureos

[Jordan]

Hi Anders,

I can't use v2 because it will be necessary to change many things ( addorupdate function -> add , managing exception..;)

I'm not sure it worked with v2, probably not.

My code throw an exception - ServiceUser permanent nonreason.

Have you some ideas ?

Thank you Anders,

[Jordan]

Sorry to double post,

I tried with example PRINT SCU from Samples,it doesn't work with my server even in version 2.0.2 and 3.0.2

In console I've got this (v2.0.2) :

Applying display format STANDARD\1,1 for film box SOP Instance UID [1.3.6.1.4.1.30071.8.167746770843512.5496412470199663]
Applying display format STANDARD\1,1 for film box SOP Instance UID [1.3.6.1.4.1.30071.8.167746770843512.5496412471100230]
PRINTSCP -> Association request:
Calling AE Title:       PRINTSCU
Called AE Title:        PRINTSCP
Implementation Class:   Implementation Class UID [1.3.6.1.4.1.30071.8]
Implementation Version: fo-dicom 2.0.2
Maximum PDU Length:     16384
Async Ops Invoked:      1
Async Ops Performed:    1
Presentation Contexts:  3
  Presentation Context:  1 [Proposed]
       Abstract Syntax:  Basic Film Session SOP Class
       Transfer Syntax:  Explicit VR Little Endian
       Transfer Syntax:  Implicit VR Little Endian: Default Transfer Syntax for DICOM
  Presentation Context:  3 [Proposed]
       Abstract Syntax:  Basic Film Box SOP Class
       Transfer Syntax:  Explicit VR Little Endian
       Transfer Syntax:  Implicit VR Little Endian: Default Transfer Syntax for DICOM
  Presentation Context:  5 [Proposed]
       Abstract Syntax:  Basic Grayscale Image Box SOP Class
       Transfer Syntax:  Explicit VR Little Endian
       Transfer Syntax:  Implicit VR Little Endian: Default Transfer Syntax for DICOM
PRINTSCP <- Association reject [result: Permanent; source: ServiceUser; reason: ProtocolVersionNotSupported]

And with 3.0.2 I've got this :

Applying display format STANDARD\1,1 for film box SOP Instance UID [1.3.6.1.4.1.30071.8.167746770843512.5496414111432516]
Applying display format STANDARD\1,1 for film box SOP Instance UID [1.3.6.1.4.1.30071.8.167746770843512.5496414112703537]
PRINTSCP -> Association request:
Calling AE Title:       PRINTSCU
Called AE Title:        PRINTSCP
Remote host:            10.XXXXXX
Remote port:            3100
Implementation Class:   Implementation Class UID [1.3.6.1.4.1.30071.8]
Implementation Version: fo-dicom 3.0.2
Maximum PDU Length:     16384
Async Ops Invoked:      1
Async Ops Performed:    1
Presentation Contexts:  3
  Presentation Context:  1 [Proposed]
       Abstract Syntax:  Basic Film Session SOP Class
       Transfer Syntax:  Explicit VR Little Endian
       Transfer Syntax:  Implicit VR Little Endian: Default Transfer Syntax for DICOM
  Presentation Context:  3 [Proposed]
       Abstract Syntax:  Basic Film Box SOP Class
       Transfer Syntax:  Explicit VR Little Endian
       Transfer Syntax:  Implicit VR Little Endian: Default Transfer Syntax for DICOM
  Presentation Context:  5 [Proposed]
       Abstract Syntax:  Basic Grayscale Image Box SOP Class
       Transfer Syntax:  Explicit VR Little Endian
       Transfer Syntax:  Implicit VR Little Endian: Default Transfer Syntax for DICOM
PRINTSCP <- Association reject [result: Permanent; source: ServiceUser; reason: NoReasonGiven]

My project it's little bit urgent..

Thank you !

[Anders Gustafsson Cureos AB]

Are you using a fo-dicom based print server?

[Jordan]

No, it's an other print server and I found the problem, the server can't accept film session ( I've got an restricted edition of my server...),

Can I send to printer since film session?

Thank you,

Jordan

[Anders Gustafsson Cureos AB]

Good that you found the problem.

Not sure if I understand your question correctly, but if you mean that printing should work once the server restrictions have been removed, then I think it should work. If you need to do something non-standard, I am not an expert on printing per se, so perhaps someone else in the forum might be able to provide a more informed answer in that case.

Regards,

Anders

[Jordan]

Thank you Anders,

Just a last question, send a dicom file on dicom printer server without using film session is non-standard ?

Jordan,

[Anders Gustafsson Cureos AB]

I am sorry, but I don't know enough about DICOM printing to answer that question. Anyone else in the community willing and able to answer? Hesham? Chris?

[Jordan]

Hi Anders,

May be my suggestion of limited server is bad if film session is standard,

In debug mode, I can see my presentationLUT throwing an exception, can you tell me how to use this tag ?

Thank you,

[Anders Gustafsson Cureos AB]

Please post the stack trace of the exception.

[Jordan]

As you can see PresentationLut is not ok,

But with print scp in samples it doesn't create problem, may be my server need a presentionlut ok ? How I can make that ?

Thank you,

[Anders Gustafsson Cureos AB]

You are correct that the PresentationLut property is corrupted, thanks for spotting this error. However, currently this property is never used externally, so what you are seeing is only the debugger failing to parse the DICOM object for Presentation LUT data.

I will add this error to the issue list for fo-dicom, but I seriously doubt that it has any influence on your failure to send the print job to the printer.

[Jordan]

ok then I'll look server side to solve my problem..

Thank you for your help !

[Chris Horn]

I suspect there is another problem here as I get the same error trying to use the fo-Dicom based SCU with Kodac codac and Fuji printers.
It's no something that I've ever got round to looking at as my production print SCU is a hybrid of fo-dicom v1 for image processing and the network side of things was pulled from mdcm

However when I tried the fo-dicom client I get the same errors as Jordan.