N-Action module - affected sop instance value issue

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
Chinna Durai
Posts: 2
Joined: Thu, 2020-08-06, 07:31

N-Action module - affected sop instance value issue

#1 Post by Chinna Durai » Thu, 2020-11-12, 09:42

Hi Jörg Riesmeier/DCMTK Support Team ,

We have Some query regarding N-Action module, please confirm with affected sop instance value is 1st two character is getting trim.

We are using DCMTK version 3.6.0
DIMSE_receiveCommand function called to received command field for N-Action request and N-Action Response.
In N-Action Response , AffectedSOPInstanceUID is ".840.10008.1.20.1.1" Output
But our expectation is "1.2.840.10008.1.20.1.1"

Please clear this query, why this is happening

Please find attachment https://drive.google.com/file/d/1qjn3C5 ... sp=sharing

Marco Eichelberg
OFFIS DICOM Team
OFFIS DICOM Team
Posts: 1280
Joined: Tue, 2004-11-02, 17:22
Location: Oldenburg, Germany
Contact:

Re: N-Action module - affected sop instance value issue

#2 Post by Marco Eichelberg » Mon, 2021-02-01, 14:00

Sorry for the late reply. ".840.10008.1.20.1.1" is not a valid UID, and, presuming that you refer to Storage Commitment, "1.2.840.10008.1.20.1.1" would be the correct SOP Instance UID.
I would suggest that you take a network capture with Wireshark and check whether the incorrect UID is sent by the Storage Commitment SCP, or if the Storage Commitment SCU incorrectly interprets the message sent by the SCP.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest