DicomUserConnection: No acceptable presentation context for modality

[ozp...@gmail.com]

Have had Orthanc humming along nicely for >12months as a DICOM router.  Suddenly seeing this from one US machine: DicomUserConnection: No acceptable presentation context for modality

Nothing has changed at the Orthanc end, so it has to be the modality........but which tag am i looking at?  SOPClassUID looks fine to me.

• 0008,0008 (ImageType): ORIGINAL\PRIMARY\GYNECOLOGY
• 0008,0012 (InstanceCreationDate): 20180122
• 0008,0013 (InstanceCreationTime): 092113
• 0008,0016 (SOPClassUID): 1.2.840.10008.5.1.4.1.1.6.1
• 
  

W0122 11:18:22.949418 main.cpp:656] Orthanc has started

E0122 11:24:01.229977 DicomUserConnection.cpp:168] DicomUserConnection: DUL Association Rejected

E0122 11:24:01.429865 ServerScheduler.cpp:123] Job has failed (Lua script: OnStoredInstance)

E0122 11:24:01.609003 StoreScuCommand.cpp:87] Unable to forward to a modality in a Lua script (instance a422cbbb-3b673f36-e78d6a53-a9399c37-c4a7e1b1): DicomUserConnection: No acceptable presentation context for modality

E0122 11:24:01.802148 StoreScuCommand.cpp:87] Unable to forward to a modality in a Lua script (instance 625e97f5-0f14ca6d-77cccc01-24d6e3ee-18f436c9): DicomUserConnection: No acceptable presentation context for modality

The thing i don't get about the error above is it's OnStoredInstance - it's errored, but has been successfully stored in Orthanc (as i can view it).

If it's happily storing in Orthanc anyway, can ignore this tag & just run my LUA over what we do have?

[Alain Mazy]

Could you define your workflow a bit more ?  What modality sends studies to Orthanc; where does Orthanc tries to forward the study ?

From what I understand, you are trying to send a study to your US modality ...  And I can assume that some US modality are not accepting C-Store ...

--

Alain Mazy / CTO 
a...@osimis.io / +32 494 31 67 27

	OSIMIS S.A.  Rue bois Saint-Jean 15/1BE-4102 Seraing  www.osimis.io

[ozp...@gmail.com]

anyone know how to get the (lengthy) reply i just posted to this un-deleted?  I think it got flagged as spam :(

[ozp...@gmail.com]

admin??

[Alain Mazy]

Forwarding from a lua script or from the GUI should give exactly the same result.  

When forwarding from the GUI, are you sure you're forwarding one of the instance that failed to forward with the lua script ?

To me, it looks like certain instance types can not be pushed to the PACS because it does not support this type of image.  So, that might be useful to analyze which image can be transmitted and which image can not.

On Mon, Jan 22, 2018 at 10:27 PM, <ozp...@gmail.com> wrote:

Sorry, should've been clearer.....

Using Orthanc as a DICOM router (local storage and GUI is also enabled).

US modalities send to Orthanc.  Orthanc reads the DICOM header (namely the StudyDescription) for a particular string.  Orthanc will then forward to one PACS destination if that string is found, another PACS destination if not.  Orthanc is also storing to itself on the way through.

LUA script is called OnStoredInstance.....

function OnStoredInstance(instanceId, tags, metadata, origin)

         --bunch of scripting here to direct traffic

               --if StudyDescription = something then

                      --sendtodestinationA

              --else

                      --sendtodestinationB

              --end

end

We have multiple US modalities sending via Orthanc.  All have been without issue until two days ago, when one machine started not forwarding - it however does store to Othanc.  I'm not sure how it's storing to itself with the error it's producing (E0122 11:24:01.609003 StoreScuCommand.cpp:87] Unable to forward to a modality in a Lua script (instance a422cbbb-3b673f36-e78d6a53-a9399c37-c4a7e1b1): DicomUserConnection: No acceptable presentation context for modality), but not forwarding.

Images can be manually sent from Orthanc to the destination using the GUI without issue.

I'm certain that this is a modality issue, but not exactly sure where i'm looking to troubleshoot.  Or is this an issue between Orthanc -> Destination perhaps?

On Tuesday, January 23, 2018 at 6:49:41 AM UTC+11, Alain Mazy wrote: