Negotiation error is Reject Abstract Syntax instead of Transfer Syntax

Google Groups archive
1

Hello,

When Orthanc receives a C-STORE acting as SCP, and no transfer syntax is specified by the SCU, Orthanc is returning Result code 3 (abstract-syntax-not-supported). However, according to the documentation, it should return code 4 (transfer-syntaxes-not-supported). The SOP class included in the abstract syntax is accepted because when I send a valid transfer syntax the Result code is 0 (acceptance).

Presentation Context ID: ID: 3

Result: 0
Abstract Syntax: 1.2.840.10008.5.1.4.1.1.2
Transfer Syntax: 1.2.840.10008.1.2.1
Presentation Context ID: ID: 5
> Result: 3
> Abstract Syntax: 1.2.840.10008.5.1.4.1.1.2
> Transfer Syntax:
Presentation Context ID: ID: 7
Result: 0
Abstract Syntax: 1.2.840.10008.5.1.4.1.1.2
Transfer Syntax: 1.2.840.10008.1.2.1.99

Is there a way of forcing Orthanc to return the correct Result code?

Best regards and thanks in advance,
Carlos

2

Hi Carlos,

Thanks for reporting this. In order for us to investigate and not spend hours trying to reproduce your problem, could you share a minimal working example demonstrating the issue ?

Thanks

Alain.

3

Hi Alain,

Sorry for the late response. Please find attached the Orthanc configuration file.

In order to reproduce the error, the SCU should send a DICOM association request to Orthanc using several Presentation Context items, each Presentation Context item proposing a single Transfer Syntax (either supported or unsupported Transfer Syntax) for one and the same supported Abstract Syntax (Storage SOP class).

Now for the Presentation Context items that propose only an unsupported Transfer Syntax, Orthanc responds with result code 3 (Unsupported Abstract Syntax) instead of result code 4 (Unsupported Transfer Syntax).

Best regards and thanks in advance,

Carlos

orthanc.json (39.6 KB)

4

any reason DicomServerEnabled is commented out?

5

Hi Carlos,

Thanks for the input but why don’t you provide a sample file and a sample scu command from dcmtk such that I can reproduce the issue directly ?

Best regards,

Alain

6

Hi Alain,

Please find attached the DVTk/DVT script used for reproducing this error. This script should be run using DVT (ref. www.dvtk.org), acting as DICOM Storage SCU.

Thanks,
Carlos

orthanc_TS.ds (5.7 KB)